Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!cornell!batcomputer!itsgw!steinmetz!uunet!portal!cup.portal.com!doug-merritt
From: doug-merritt@cup.portal.com
Newsgroups: comp.sys.amiga.tech
Subject: "RAM Disk:" lock 1 bug
Message-ID: <5512@cup.portal.com>
Date: 16 May 88 23:37:37 GMT
References: <8805150351.AA19130@jade.berkeley.edu>
Organization: The Portal System (TM)
Lines: 17
XPortal-User-Id: 1.1001.4407

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!doug