From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Loading ramdrive.sys
Date: 26 Oct 2000 16:06:33 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 21
Message-ID: <8t9kq9$8d$1@nets3.rz.RWTH-Aachen.DE>
References: <39F7DEBC DOT 7938A452 AT ma DOT tum DOT de> <39f84c2f$1 AT news DOT gemsoft DOT net>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 972576393 269 137.226.32.75 (26 Oct 2000 16:06:33 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 26 Oct 2000 16:06:33 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

cat AT animal DOT u-net DOT com wrote:

>    There is one question however. If the original computer has
> several partitions on its hard disk the ram drive may not be drive D:.
> Is there a simple way of finding out which drive the ramdrive really
> is after installation ? A suitable DOS or BIOS interrupt call would be
> a very simple solution in this case.

A single interrrupt call most likely won't give you that information,
but a little program along the lines of what Eli already hinted at, in
this thread, should help: loop over all drives with getmntent() and
check each of them if it's the ramdrive. The check itself can be done
in various ways. You can check the volume label, e.g.. IIRC, it's
always something like "RAMDRIVE" or so for ramdrives.

It shouldn't be too hard to extract the DOS calls used by getmntent()
to see how to do the same outside the DJGPP runtime environment.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.