doug-merritt@cup.portal.com (05/17/88)
I just noticed that "RAM Disk:" is flawed; if you do (e.g.)
dir "RAM Disk:"
it hangs (forever, I think). It turns out that the DeviceList
entry for "RAM Disk" has a lock pointer of 1, which sounds like
a no-no to me.
Is this old news? I didn't remember hearing about it before. Had
to add a special case to my filetype program to keep it from hanging
if that volume was specified.
Doing "dir ram:" works fine, of course. Device != volume.
Doug
---
Doug Merritt ucbvax!sun.com!cup.portal.com!doug-merritt
or ucbvax!eris!doug (doug@eris.berkeley.edu)
or ucbvax!unisoft!certes!dougcarolyn@cbmvax.UUCP (Carolyn Scheppner CATS) (05/18/88)
In article <5512@cup.portal.com> doug-merritt@cup.portal.com writes: >I just noticed that "RAM Disk:" is flawed; if you do (e.g.) > dir "RAM Disk:" > >it hangs (forever, I think). It turns out that the DeviceList >entry for "RAM Disk" has a lock pointer of 1, which sounds like >a no-no to me. > >Is this old news? I didn't remember hearing about it before. It is old news. 1.2 ram-handler will probably always cause these problems. The problem seems fixed in 1.3 ram-handler which has a real volume node with the name "RAM Disk". -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Carolyn Scheppner -- CATS >>Commodore Amiga Technical Support<< UUCP ...{allegra,ihnp4,rutgers}!cbmvax!carolyn PHONE 215-431-9180 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
peter@sugar.UUCP (Peter da Silva) (05/19/88)
In article <5512@cup.portal.com>, doug-merritt@cup.portal.com writes: > dir "RAM Disk:" hangs. It turns out that the DeviceList > entry for "RAM Disk" has a lock pointer of 1, which sounds like > a no-no to me. I ran into this, and I do what's probably a similar special case to fix it in Browser. You may notice that if you open "RAM Disk:" the window is labelled "RAM:". -- -- Peter da Silva `-_-' ...!hoptoad!academ!uhnix1!sugar!peter -- "Have you hugged your U wolf today?" ...!bellcore!tness1!sugar!peter -- Disclaimer: These may be the official opinions of Hackercorp.
carolyn@cbmvax.UUCP (Carolyn Scheppner CATS) (05/24/88)
In article <5645@cup.portal.com> doug-merritt@cup.portal.com writes: >>Carolyn Scheppner writes: >>[ Re: "RAM Disk:" hangup, lock == 1: ] >>The problem seems fixed in 1.3 ram-handler which has a real volume node >>with the name "RAM Disk". >[] >I'm a little confused about the latter part of the statement, though... >there's already a volume node with the name "RAM Disk" in the >DeviceList. I've looked. It's just that its dl_Lock field is equal >to 1. Perhaps I'm just misunderstanding? What version of the ram-handler are you using ? I believe the 1.2 ram-handler had volume that was really pointing at a device node. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Carolyn Scheppner -- CATS >>Commodore Amiga Technical Support<< UUCP ...{allegra,ihnp4,rutgers}!cbmvax!carolyn PHONE 215-431-9180 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=