I have a dos bookkeeping program. When I click on the icon to open it up it keeps telling me the files in my config.sys must be at least 65 plus any programs used by simultaneous programs. You should increase the number of files by three. Press enter to automatically update your config.sys file and
reboot your computer.

I have done this several times and still cannot get into the program.
The config.nt file and autoexec.nt file are LOCATED in the
directory folder called Easy. I created a pif file on my desktop that REFERENCES these files in the Easy directory.

The files in the config.nt are equal to 60. Even if I CHANGED them to a
higher number it still doesn't work. Can anyone help me out on
this?

Thanks


"DOS" on NT machines is initialized by the autoexec.nt and config.nt files in the %systemroot%\system32 directory. It's doubtful your files in the Easy directory are even being read.

Try changing the files= parameter in the config.nt file found in the Windows system directory.

Good luck. 8-)Thanks so much. I got back in the program. Sometimes, the computer
freezes when this program is opened. This normally happens after being in the DOS program for about 25 minutes. The computer never freezes when any
of the other programs are opened. Does this have to to with expanded or extended memory that is being allocated to the DOS program.

Any tips on how to fix the freeze or memory allocation for the DOS program? Again thanks. I spent hours trying to research this an fix this on my own and your help fixed this problem in two seconds.

Thanks againYou didn't mention what product we're talking about so I can't give you any specifics. If the program has requirements for extended or expanded memory, do not put the parameters in the config.nt file. Instead right click the icon you use to launch the program and make any changes to the Memory tab. This MAKES the change specific to your program, not global to your system.

Normally DOS programs do not have any special memory requirements and the default values are fine. I have a few legacy programs running on XP and have never needed to make memory changes. If the freezing continues, try checking out your logs in the event VIEWER. You might find a trail that leads to the problem.

Good luck. 8-)