aland@infmx.UUCP (Dr. Scump) (06/15/88)
Has anybody experienced problems with extended memory RAM disks
using Zenith's VDISK (DOS 3.1 and 3.2, at least) ?
Apparently, There is a "standard" way (as established by IBM/MS DOS VDISK)
that DOS denotes how much extended memory is available; this "field" is
updated by VDISK to reflect extended memory consumed/remaining if
an extended memory RAM disk is built. (Purists, please forgive
the *technically* misworded problem statement). Apparently, Zenith's
VDISK does not "mark" its extended memory consumption in the same
manner. As a result, two packages that I have which use extended
memory trash any extended memory VDISK RAM disks (because they thought
those RAM addresses were "available"). If I have expanded memory RAM
disks (using Intel's driver), everything is OK.
Has anybody run into this before? Does it happen in DOS 3.3?
Please email, and I will summarize. Thanks in advance.
--
Alan S. Denney | Informix Software, Inc. | {pyramid|uunet}!infmx!aland
Disclaimer: These opinions are mine alone. If I am caught or killed,
the secretary will disavow any knowledge of my actions.
Santos' 4th Law: "Anything worth fighting for is worth fighting *dirty* for"