Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!cbmvax!andy
From: andy@cbmvax.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: AmigaDOS:  How to know if a file is on RAM:
Message-ID: <1396@cbmvax.cbmvax.cbm.UUCP>
Date: Wed, 11-Feb-87 16:16:37 EST
Article-I.D.: cbmvax.1396
Posted: Wed Feb 11 16:16:37 1987
Date-Received: Thu, 12-Feb-87 19:56:54 EST
References: <157@batcomputer.tn.cornell.edu>
Reply-To: andy@cbmvax.UUCP (Andy Finkel)
Organization: Commodore Technology, West Chester, PA
Lines: 27
Keywords: AmigaDOS, RAM:, Lock(), ParentDir().

In article <157@batcomputer.tn.cornell.edu> hsgj@batcomputer.tn.cornell.edu (Dan Green) writes:
>	In summary, is there a guaranteed way of knowing whether a
>file you are examining is actually on the RAM: disk or not?
The way I use is to check the fib_FileName[0] and make sure that
it (the first character) is greater or equal than space.

>	I would like to point out that Perry's ASDG-RAM disk, along
>with the hard disk i have, are both very well behaved in this resect.
That RAM disk uses the standard file system.  The system RAM
disk uses its own.  (gives it some extra speed)
>	Just off-hand, does anyone know if a "lock" as returned
>from Lock() is either (a) a plain old "long", or (b) is really
>and truly a pointer to a FileLock struct.
its should be a pointer to a FileLock.  I'll have to check to be
sure, of course.  Maybe it doesn't like being tweaked. :-)
>-- Dan Green


-- 
andy finkel		{ihnp4|seismo|allegra}!cbmvax!andy 
Commodore/Amiga		 /or/ pyramid!amiga!andy }

"Do not meddle with the affairs of wizards, for it makes them soggy and hard 
to light."

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.