Subj : How to detect RAM disks (Was: how to detect cdrom?)
To   : Gerald Miller
From : Jasen Betts
Date : Thu Feb 28 2002 05:59 am

From: Jasen.Betts@p42.f531.n640.z3.cereal.mv.com (Jasen Betts)
Subject: How to detect RAM disks (Was: how to detect cdrom?)

Hi Gerald.

25-Feb-02 14:07:44, Gerald Miller wrote to Gerald Miller

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

 GM>     MS-RAMDRIVE
 GM>     RAMDRIVE
 GM>     RDV
 GM>     VDISK
 GM>     NOVELL
 GM>     DRDOS
 GM>     RAM
 GM>     NEWLDR
 GM>     RxVDISK
 GM>     BDSK
 GM>     TDSK
 GM>     TF

how'd you pick those names?

 GM> MS-RAMDRIVE is not currently in memory.

 GM> RAMDRIVE is using the following memory:
     ~~~~~~~~
   [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)
                                         ~~~~~~~~
well, that's the problem. MEM responds to the _filename_ of the driver.
if you rename ramdrive.sys to a different name mem will 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...

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

 -=> Bye <=-
--
|Fidonet:  Jasen Betts 3:640/531.42
|
| Origin: The Cereal Port BBS (603)899-3335 199.125.78.133 (1:132/152)


---
 # Origin:  (1:132/152.4)
 * Origin: Baddog BBS (1:218/903)

.