DOS ain't dead

Can I ask about patchne NE binary with parameter-r for Borland 16 bit dpmi
binars with rtm.exe ? I use hdpmi16 -r dpmild16.exe binary borland exe
hdpmi16 -u but runtime error 216 or not enought memory continues :( Can I
change borland binary for hdpmi16 server in different way??

> Can I ask about patchne NE binary with parameter-r for Borland 16 bit dpmi
> binars with rtm.exe ? I use hdpmi16 -r dpmild16.exe binary borland exe
> hdpmi16 -u but runtime error 216 or not enought memory continues :( Can I
> change borland binary for hdpmi16 server in different way??

Probably I don't fully understand what you want to do: running a Borland 16-bit app under hdpmi16 should work without further actions - are you sure you need the HX dpmi loader dpmild16.exe to launch the Borland app?

"Not enough memory" errors could also occur because the dpmi host offers too much memory - hdpmi16 may supply up to 4 GB. You can try to reduce free mem with the -x option.

---
MS-DOS forever!

Japheth, You are great! Thank You much :)

dpmi16.exe -x -r
dpmild16.exe borlanddpmi16.exe
hdpmi16.exe -u

work well
the borland binary are patdhed for emulation rtm.exe and
DPMI16BIN.OVL

Japheth You wrote me
"My guess is: the Borland extender uses a 16-bit version of LGDT or LIDT that only works with 24-bit addresses. If you find occurrences of these instructions in the extender, a fix is possible. However, the fix can be tricky because the 32-bit versions of these instructions require an extra byte (66h)."
Patchne changes two bytes in NE section, both exe borland and extender borland, but I think that dynamic link to extender is broken and therefore
extender is improper

I enclose extender dll for borland 16bit dpmi