🚀 go-pugleaf

I have written a resizeable EMS and XMS RAM disk that is available in
Simtel20 ramdisk directory as SRDSK200.ZIP. 

Recently I noticed that it does not function under Windows 3.1
Enhanced mode and found out about two problems:

1. The EMS 4.0 supported by Windows VDM does not implement function 24
(Move Memory Region) correctly, but gives always an error (invalid
handle or too big expanded memory region or something).

2. Windows takes good care of freeing the memory allocated to a handle
when the VDM is finished. This causes the memory that the RAM disk
uses to be lost.

I give up on the first problem, but on the second I'd like to know if
there is any way to tell Windows not to free the handle allocated in
the VDM.

I use a DOS executable to allocate the memory for the RAM disk and the
executable modifies directly the structures in the device driver to
let the driver know which handle to use to access the memory.

I do not want to add any IOCTL code to the device driver, but am
interested if it would help to use IOCTL to make the driver allocate
the memory - if the Windows does not free the handle allocated "in
DOS" when the VDM is finished. 

If nothing more, an email address to someone in Microsoft and willing to
help would be good.

Thank you.
-- 
---
Marko Kohtala - INTERNET:Marko.Kohtala@hut.fi, mkohtala@otax.tky.hut.fi
Student at (not representative of) the Helsinki University of Technology