🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.msdos.misc
Article #3851

Re: RAMDRIVE as E not D:

#3851
From: John Savage
Date: Fri, 29 Mar 1996 00:00
47 lines
3168 bytes
 || I have just noticed that the server seems to have jettisoned some of  ||
 || my posts over the last 10 days. So here follows a few repeated posts. ||

>On 6 Mar 96 16:40:49 CST, milleret@falcon.cc.ukans.edu (Andy Milleret) wrote:
>
>>>}>: My CD is on D:
>>>}>: RAMDRIVE wants to go to D:
>>>}>: I want it to go to E:
>>
>>}>You need to create a small D: ramdrive and then your E:
>>}>ramdrive.  As far as I know RAMDRIVE does not allow you
>>}>to specify a parameter for the drive letter.

I tried this basic idea of loading RAMDRIVE twice and it does
create both D: and E: but would the RAM memory allocated to
that small D: drive will be tied up and lost when/if the CD
claims the letter D: for itself?

>>hm.. are you saying I create the D: ramdrive BEFORE the CD gets assigned
>>to D: so it gets overwritten? if that works, why doesn't it know the
>>CD is there and jump to E: by itself???
>>thabks much
>>
>I am having this same problem.  I don't know how to solve it either.  If I
>could load ramdrive later (such as in a small batch file called from the
>autoexec, that would be fine also.)  I don't believe that a cd driver will
>"overwrite" the ramdrive, so if anyone has a solution that works, I would love
>to hear it.

Well, how about trying it and letting us know ...

ftp ftp.coast.net /SimTel/msdos/sysutil/
comp.zip      B    5086  880829  Load and unload device drivers after bootup
devic104.zip  B    7250  920530  Load and unload device drivers after bootup
devlod.zip    B   18240  911230  Dynamic load of device drivers after boot-up
dmc35.zip     B   74710  931129  Allows loading/unloading of dev. drivers/TSR's
drvins11.zip  B   12298  901206  Load and unload device drivers after bootup
idrv01.zip    B   16369  920410  Install/uninstall device drivers after bootup

Otherwise, create a dummy drive D: in config.sys before ramdrive.sys
so that the ramdrive must then become E: and with any luck the CD will
then cleanly take over and appropriate the letter D:

ftp ftp.coast.net /SimTel/msdos/diskutil/
notready.zip  1505  940930  Dummy disk device driver for never ready drive
--
John Savage               koala@sydney.dialix.com.au
Technical Details
Message-ID: <4jgche$2j7$1@sydney.DIALix.oz.au>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <4h7fdj$aee@dorsai.dorsai.org> <4hcogq$4g4@news4.digex.net> <4hctar$e4r@dorsai.dorsai.org> <1996Mar6.164051.115500@kuhub.cc.ukans.edu> <313e537a.1461596@news2.new-york.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10d683,11565f65ebd12311,start
X-Google-Attributes: gid10d683,public
X-Google-Thread: f53ba,11565f65ebd12311,start
X-Google-Attributes: gidf53ba,public
X-Google-Thread: 111d31,11565f65ebd12311,start
X-Google-Attributes: gid111d31,public
X-Google-Thread: f71eb,11565f65ebd12311,start
X-Google-Attributes: gidf71eb,public
From: John Savage <koala@sydney.dialix.com.au>
Subject: Re: RAMDRIVE as E not D:
Date: 1996/03/29
Message-ID: <4jgche$2j7$1@sydney.DIALix.oz.au>
X-Deja-AN: 144821578
sender: koala@sydney.DIALix.oz.au
references: <4h7fdj$aee@dorsai.dorsai.org> <4hcogq$4g4@news4.digex.net> <4hctar$e4r@dorsai.dorsai.org> <1996Mar6.164051.115500@kuhub.cc.ukans.edu> <313e537a.1461596@news2.new-york.net>
followup-to: comp.os.msdos.misc
organization: Gumleaf Smoke Signals Telegraph Co.
newsgroups: comp.os.msdos.misc,comp.archives.msdos.d,comp.sys.ibm.pc.misc,aus.computers.ibm-pc