Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!usc!jarthur!uunet!beartrk!cjp
From: cjp@beartrk.beartrack.com (CJ Pilzer)
Newsgroups: comp.os.msdos.misc
Subject: Re: Microsoft's XMS spec
Summary: Ramdisk for MS XMS
Message-ID: <430@beartrk.beartrack.com>
Date: 14 Jul 90 17:05:27 GMT
References: <15173@reed.UUCP>
Organization: Bear Track Computer Co., Takoma Park, MD.
Lines: 20

In article <15173@reed.UUCP>, minar@reed.bitnet (Nelson Minar,L08,x640,7776519) writes:
>
> [stuff deleted]  I am aware that 4DOS 3.0 will
> swap into XMS, and that this even works.. Any other programs take
> advantage of it?

I am not able to get my 4DOS to swap under MS HIMEN.SYS xms manager, although
it works great with 386MAX, but Windows 3.0 won't work with 386MAX and requires
HIMEM.SYS.

> 
> Is it possible to get XMS and vdisk.sys to coexist? The documentation
> says no. Is there a RAMdisk program out there for extended memory that
> will coexist with XMS?
> 
Microsoft recommends in the documentation that came with Windows 3.0, that
MS RAMDRIVE.SYS be used with HIMEM.SYS.  Both of these came with my ver 4.01
MS DOS, however, the versions which come with Windows 3.0 are later.

-- cj