Old application memory issue

Microsoft Windows server 2003
February 20, 2011 at 05:02:01
Specs: Windows 2008 server R2, Xeon Hexa Core 2,2Ghz / 16GB
Hey guys,

I've recently replaced a customers old Windows 2000 server with a new 2008 server. They've got an old application running on the 2000 box (512MB memory) where it works just fine, but on the new 2008 box (12GB memory) it gives an error; "Memory error, please restart application". An educated guess would be it can't handle the large amount of memory.

This is an old DOS based software, at some point converted to work in 32 bit windows environment (the exe is called M6W32.exe). Unfortunally it doesn't contain an ini-file or such, so I can't seem to manipulate it. It crashes immediatly when I start up the exe, unless I setup compability mode for Windows 2000. After that it starts up, but gives the memory error instead.

Is there a way to set limit the amount of memory the application can see? I'm sure that would do it.

See More: Old application memory issue

Report •

February 20, 2011 at 06:07:23
Did you take in account to run that application inside a virtual machine under Win 2008?

You can install MS Virtual PC or Open Source VirtualBox for free but you need a legal copy of the guest operating system too (in your case Windows 2000 or another Windows environment). If the legacy application is a DOS one then FreeDOS may apply at no cost.

As far as I know to limit the amount of memory is possible, but it is a global setting not related to just a specific application.

Report •

February 20, 2011 at 09:50:30
I doubt that the problem is related to the amount of memory in the computer, although it is possible. There is no option to limit memory for an individual process. There are many possible compatibility issues with older applications on Server 2008. VirtualBox or VirtualPC should work.

Report •

February 21, 2011 at 02:41:51
I hear you... Since the 2008 servers are actually running on a vmware setup, I created a new vm with Windows XP SP2 on it, limiting memory to 512MB and disk space to lowest possible but it still didn't work. I'm just now trying to find out if there's anyone giving support for this software as we need to change the printer setup within the program as well.

I also recommended the customer to buy another software. This one is simply too friggin old... since '93!

Report •

Related Solutions

February 21, 2011 at 06:12:26
Although VMWare failure I still suggest you try to execute under Virtual PC or VirtualBox since I faced many cases where VMWare failed and other virtual environments worked fine.

Report •

Ask Question