Subj : How to detect RAM disks (Was: how to detect cdrom?)
To   : Jasen Betts
From : Gerald Miller
Date : Fri Mar 01 2002 11:47 pm

Hello Jasen,

    Subject:  How to detect RAM disks (Was: how to detect cdrom?)
    On Thursday February 28 2002 at 05:59,
    Jasen Betts wrote to Gerald Miller:

 GM>> As a test, I created a e:\tmp\mod_name.sav:

 GM>>     MS-RAMDRIVE
 GM>>     RAMDRIVE
 GM>>     RDV

<snip>

 GM>>     TF

 JB> how'd you pick those names?

Most of the names were listed in a message posted by Matthias Paul.

 GM>> MS-RAMDRIVE is not currently in memory.

 GM>> RAMDRIVE is using the following memory:

 JB>      ~~~~~~~~
 JB>    [snip]

 GM>> TDSK is not currently in memory.
 GM>> TF is not currently in memory.
 GM>> === Cut End:   MEM.OUT ===

 GM>> Notice that "MS-RAMDRIVE" was #_NOT_# found (although I can
 GM>> assure you that I am loading C:\DOS\RAMDRIVE.SYS high)

 JB>                                          ~~~~~~~~
 JB> well, that's the problem. MEM responds to the _filename_ of the
 JB> driver. if you rename ramdrive.sys to a different name mem will
 JB> respond to the new name.

 GM>> and I would presume that MEM.EXE is not locating the device by a
 GM>> label, but rather a device name...

 JB> device name? only character devices have names, block devices have
 JB> letters, it's more of driver filename.

So people have been telling me, lately.

Forget that I brought up MEM.EXE and carry on with the
development of a utility "to detect RAM disks".....

           Cheers ... Gerald

--- GoldED+/386 1.1.5-1227
 * Origin: A lawyer's time and advice are all he has to sell. (1:342/512)

.