WinXp prof. is installed (or Win 2000). Now I am trying to run a DOS-
program.  Therefore it needs the command files=40 in
%systemroot%\system32\config.nt. It
seems to me there is no result. Even a value of 255 has 
no effect (program interrupts with "not enough handles"). What can I do ?

Next problem is to get enough memory. the commands  I use 
are:
device=%SystemRoot%\system32\himem.sys noems (same effect when not using noems)
dos=high,umb
files=255

Same problem as above: no effect.

I am using the same config.nt and autoexec.nt with WinNT,   everything
works correctly.
What`s wrong in XP and 2000? Hope some one can help me.

---

Request for Question Clarification by endo-ga on 26 Dec 2003 07:21 PST

Hi,

Can you please try the following:

1-) Add the line PerVMFiles=255 in system.ini in the WINNT folder for
Windows 2000, under the [386enh] section. So system.ini looks
something like this:

; for 16-bit app support
[drivers]
[mci]
[driver32]
[386enh]
PerVMFiles=100

Hopefully that should solve your files problem.

2-) Can you right click on your DOS executable and choose properties
please, then go to the "memory" tab and change the memory settings
there.

Please let me know how this goes.

Thanks.
endo

---

Request for Question Clarification by endo-ga on 26 Dec 2003 07:24 PST

Sorry the maximum setting for PerVMFiles is 225, each DOS program
already gets 30 by default, and PerVMFiles adds a maximum of 225 to
reach 255.

Thanks.
endo

---

Request for Question Clarification by endo-ga on 06 Jan 2004 09:16 PST

Hi,

Have you had any luck with any of these settings?

Thanks.
endo

Another option may be to use a tool like VMware to emulate a DOS-based
computer, and run the DOS application through the emulator.

Give 16-bit apps their own separate processes 

[HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ WOW]
"DefaultSeparateVDM"="Yes" 

By default, Windows XP will only open one 16-bit process and cram all
16-bit apps running on the system at a given time into that process.
This simulates how MS-DOS based systems viewed systems and is
necessary for some older applications that run together and share
resources. However, most 16-bit applications work perfectly well by
themselves and would benefit from the added performance and stability
of their own dedicated resources. To force Windows XP to give each
16-bit application it's own resources, browse to HKEY_LOCAL_MACHINE \
SYSTEM \ CurrentControlSet \ Control \ WOW and find the String
"DefaultSeparateVDM". If it is not there, you may need to create it.
Set the value of this to Yes to give each 16-bit application its own
process, and No to have the 16-bit application all run in the same
memory space.


HOW TO: Identify a 16-bit Program in Windows XP
 
http://support.microsoft.com/default.aspx?scid=kb;en-us;320127

How to Troubleshoot 16-Bit Windows Programs in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;314495