Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!nic.csu.net!beach.csulb.edu!csus.edu!decwrl!sdd.hp.com!caen!hellgate.utah.edu!fcom.cc.utah.edu!npd.novell.com!newsun!tporczyk
From: tporczyk@na.excelan.com (Tony Porczyk)
Newsgroups: comp.os.msdos.misc
Subject: Re: ramdrive.sys in extended memory
Message-ID: <1991Apr3.053618.27524@novell.com>
Date: 6 Apr 91 00:53:42 GMT
Sender: news@novell.com (
Lines: 19

The News Manager)
Nntp-Posting-Host: na
Reply-To: tporczyk@na.excelan.com (Tony Porczyk)
Organization: Standard Disclaimer
References: <1991Apr01.154431.3609@ecst.csuchico.edu> <1991Apr2.043333.2073@bradley.bradley.edu>
Distribution: na
Date: Wed, 3 Apr 1991 05:36:18 GMT

In article <1991Apr2.043333.2073@bradley.bradley.edu> sad@buhub.bradley.edu (Shrijay Dalal) writes:
>In <1991Apr01.154431.3609@ecst.csuchico.edu> rreid@ecst.csuchico.edu (Ralph Reid III) writes:
>>device=c:\dos\ramdrive.sys 1024 /e
>>I am attempting to set up a 1 MEG RAM disk in extended memory on a 386
>Do not use RamDisk.Sys.  The correct driver to use to set up extended
>memory as a RAM drive is VDISK.SYS.  The syntax you need to use is:

Why would that possibly matter?  I use ramdrive in exactly the way Ralph is
describing and have a 2Mb disk in extended memory in the _smallest_ of several
configuration I use.
Can you explain your recommendation - I am curious.

Tony