Subj : Re: How to detect RAM disks (Was: how to detect cdrom?)
To   : Steve
From : Charles Dye
Date : Thu Feb 28 2002 04:27 am

From: Charles.Dye@f3.n342.z1.cereal.mv.com (Charles Dye)
Subject: Re: How to detect RAM disks (Was: how to detect cdrom?)

From: raster@highfiber.com (Charles Dye)

On Wed, 27 Feb 2002 05:07:13 GMT, "E. S. (Steve) Fabian"
<ESFabian@BellAtlantic.net> wrote:

>Charles Dye wrote:
>>
>> MEM picks up the name in the arena header, *usually* the base
>> part of the filename.  For grins, you might try renaming DOSKEY.COM
>> as RAMDRIVE.COM and loading it.
>
>Tried it (copied DOSKEY.COM into %temp\RAMDRIVE.COM). The report looks
>similar, but the critical line does NOT contain "Installed device=XYZ",
>it just contains "Program". NOTE: the sizes below are fake.

Right; a CONFIG.SYS block driver hooks into the system differently than a
command-line TSR does.  I just wanted to demonstrate where the name reported by
MEM comes from.  (Note, however, that some RAMdisks *do* load as TSRs from the
command line.  MEM's report of XMSDSK looks very similar to the DOSKEY / fake
RAMDRIVE report you supplied.)

--
Charles Dye     raster@highfiber.com
--
|Fidonet:  Charles Dye 1:342/3
|
| 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)

.