Windows XP Pro Compatability Mode

[Andrew]

I just upgraded a client PC to Windows XP Pro from 98.
Now when we run one of the legacy DOS applications from a
shared drive it gives me 'not enough memory error 824'.
When I used the program compatabilit wizard to try and
fix it it runs perfect through the wizard. I then click
next and finish up the wizard but informs me it cannot be
set due to the fact it is not an executable (its a .bat
file that calls another bat file which then calls and
executable).

How come it works when doing it through the wizard? I've
tried creating the command.com shortcut, and editing it
with all the information i need, but it still give me the
memory error. I removed the dosx ine from loading in the
autoexec.nt file and have nothing loading in the
config.nt file either.....thanks!

 

[Alex Nichol]

I just upgraded a client PC to Windows XP Pro from 98.
Now when we run one of the legacy DOS applications from a
shared drive it gives me 'not enough memory error 824'.
When I used the program compatabilit wizard to try and
fix it it runs perfect through the wizard. I then click
next and finish up the wizard but informs me it cannot be
set due to the fact it is not an executable (its a .bat
file that calls another bat file which then calls and
executable).

The wizard will set up a different environment. For best DOS
conventional memory, edit the windows\system32\config.nt and autoexec.nt
files.

In config.nt have (apart from the large number of REM lines) just
EMM = B=4000 RAM
(note the exact spaces - either side of the first = and before RAM,
none next to the second =) and

dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=40
(or higher files= if needed)

and in autoexec.nt have

REM Install DPMI support
lh %SystemRoot%\system32\dosx

with other earlier lh lines REM ed out, and then any SET or PATH lines
that may already be present at the end.

This should give about 612K for a program, run from a shortcut made to
its .exe file. R-click the shortcut, Properties and on the Memory page
you can set an explicit value - rather than Auto - for any EMM or XMS
memory it may need, and for initial environment space

Unfortunately a shortcut made directly to a bat file is a 'Windows'
shortcut (a .lnk file) not a DOS one (.pif). You can work around this
by making a shortcut to a DOS executable - r-drag to somewhere
convenient, Create Shortcut here . Then r-click that, properties, and
adjust the command line so it points to the .bat file instead.