[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 730
  • Last Modified:

Reducing DOSX Conventional Memory.

Hi, is everyone ok?

Ill keep it short and sweet.

Basically, i over look the operation of a business network at a company. The software they use to manage their finances and transactions is a DOS Program, run in XP. However, they have had a new machine installed, and they can not use the software correctly. During use, the software comes up with an error notifying the user that there is insufficient conventional memory to run the program properly.

Ive run 'mem /c' in cmd prompt on the computer that works and on one that does.

On the working PC, Conventional Memory for 'DOSX' is 0k, with an upper memory usage of 34K for DOSX.

On the machine that doesnt work, DOSX's conventional memory is 33.9K, and its Upper memory set at 0.1K.

I have tried fiddling with config.nt and autoexec.nt, but to no avail. I have spoken to the softwares technical department and they guided me in the direction that drivers could be interfering, taking up valuable memory, which, in dos, is limited to a conventional memory of 640K.

Ive just been doing more research, a possible solution is that if the network redirector loads before dosx, then that can affect where the dosx is loaded.Ive tried this on one machine and it seems to have worked maybe, however on another it hasnt. I also read that drivers loaded in BIOS stage could affect this, anyone heard anything about that??


Any suggestions are greatly appreciated as this has been doing my nut in for the past 3 days.

~Andy
0
williamvail
Asked:
williamvail
1 Solution
 
flubbsterCommented:
I had a similar issue when trying to run some old DOS games on my XP Pro system. The page linked below helped a great deal. Try following the steps, including making the shortcut, which will give you greater control to the DOS Memory allocations.

http://home.earthlink.net/~infernosadventures/configuringdosemulation.htm

You can obviously ignore the game specific stuff like audio settings.
0
 
williamvailAuthor Commented:
I have followed your link, and followed the procedures. However, when i run the shortcut the autoexec.nt location in the PIF Editor does not save and reverts to 'autoexe', missing off the 'c.nt' file type, as does the CONFIG.NT file. When i use the default AUTOEXEC and the created CONFIG, DOSX still uses 33.9K in conventional memory. This is driving me insane lol...

Andy
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Tackle projects and never again get stuck behind a technical roadblock.
Join Now