Try disabling memory relocaton in BIOS setup. As last resort you can have UMBs using the generic EMS 4.0 support of TLBMM, QRAM or Invisible RAM. I have used all of them successfully with my 286 mainboard and a SUNTAC Chipset.

I have a 386SX PC with a Headland HT18 chipset, but have not been able to locate any EMS driver for it.
In the BIOS, there is an option to allocate some memory as EMS, so I'm assuming there must be a driver for it as well.

Wait, there's an EMS driver ? I'm also having a Headland-based machine! Where can I find it ?

I am attaching the HT12MM.SYS driver , it's the hardware EMS driver for the HT12 chipset, don't know if it will work with others

supposedly there is also a "ht12-umb.lzh" but noone seems to be able to locate it...
http://www.vcfed.org/forum/showthread.php?275 … and-EMS-drivers

Thank you very much! ^^

The solution was here all along 🤣 according to this post:

With The Last Byte Memory Manager 2.11 version works the umb (i can get 62kb umb), only you should delete the frame=d000 options at the config.sys lastbyte.sys command line. The olny problem is the program is sharware (wait 30sec, works only 30days), and you couldn't use ems/umb at the same time (because the ems page frame uses as umb).

So I downloaded the older v2.11 version of TLB and it actually works! Apparently the latest v2.52 broke something - at least on the chipset program.

DOS 6.22 cannot recognize the UMBs that TLB creates, programs do load fine though in that region but you have to use TLB's HIGHTSR loader, LH does not work:

So unless that special HT12 UMB driver is found TLB is the only way that works and creates UMBs, at least on my systems.
Thanks everyone for their help!

edit:

turns out that the problematic part is the CHIPSET.EXE detection program that TLB v2.52 comes with... the driver is loading fine:

this is the config.sys command for the HT12 chipset: DEVICE=C:\TLBMM\LASTBYTE.SYS Physical=HT12,NOEMS,OVERRIDE

doing a full install of TLB v2.52 with "INSTALL HT12" (so that chipset.exe that is problematic does not run) takes care of the UMB integration in DOS, MEM reports UMBs and LH works.

Interesting, my TowerAT also had a HT Chipset, but no EMS was possible.
Someone told be that this chipset had no ems support.

HT12 has hardware EMS support, you set the size in BIOS and then use the driver I attached in a previous post.
EMS though won't give you UMBs, that's a different story and you need The Last Byte for that.

my machine had no bios-support for ems.

no idea what's the deal then... see my BIOS screen in the first post - both HT12 boards I own are the same

my bios looks like this https://www.flickr.com/photos/pato4sen/8558776321/ (not my photo, not my machine, but identical to mine)

what is this mention of "SETUP-RAM" at the bottom?

That's only the "save bios-configuration" if you choose "enter"

well is seems EMS function is disabled for some reason... no idea if there is a chance to work with any trick

dr.zeissler wrote:

Interesting, my TowerAT also had a HT Chipset, but no EMS was possible.

The Tower AT does not have a HT12 chipset. It's using the GC102, but EMS is only supported with the GC103.

ah da war doch was, danke!

Hi,

@keropi

I know it is an old post but where I can get all these memory management tools ?

FreddyV wrote on 2023-01-06, 16:07:

Hi,

@keropi

I know it is an old post but where I can get all these memory management tools ?

what tools are you referring to?

keropi wrote on 2023-01-06, 16:17:

FreddyV wrote on 2023-01-06, 16:07:

Hi,

@keropi

I know it is an old post but where I can get all these memory management tools ?

what tools are you referring to?

The Memory management / diagnostic tools, like Manifest