[thomson9]

The update worked fine but unfortunately didn't solve my problem which is kind of weird to begin with.

The client has an old DOS application compiled in Clipper that they won't give up. It does what they need and is pretty straight forward but not easily recoded and they don't have source code anyway.

The program is giving them a low memory warning which interrupts their workflow and so is very annoying.

This machine will not load anything into the High Memory Area in a DOS box so the largest executable program size (mem /d) is around 575K. Older machines that do load DOS drivers into the HMA don't have the problem and get anywhere from 605K to 630K available.

To further compound the issue this machine, although being a newer machine (2011), is running Windows XP.

I've been through the System Info on this machine and don't see anything out of the ordinary about the HMA and there appears to be quite a bit unused but the LoadHigh command in the AutoExec.nt file will not load anything there.

So far all I can come up with is that there is something incompatible between the XP mobo drivers and either the hardware or the BIOS that won't let the DOS box use the HMA.

I have Win 2K, XP, and Win7 and it works OK on Win7 with my ASUS mobo. I guess they'll have to update the machine to Win7 but that also involves updating a bunch of their application software to Win7 versions so they are trying to avoid it.

Out of roughly 150 machines, they are having the problem on about 20 of them.

I don't find anything on the web about this particular problem and was wondering if anyone else has seen anything that might be related.

Comparison data between a working machine and this machine is in the attachment.

Thanks for your replies.