XP support for Expanded Memory? And Config.sys??

[Kurt Erichsen]

Does XP oprovide support for Expanded Memory? I mean LIM
4.0 EMS used by DOS applications before Extended Memory
(XMS) became widely supported. In the past this support
could be by loading EMM386.exe in config.sys.

And on that subject, does XP give you a way of manually
customizing config.sys? My brief experience in ME
indicates that the OS overwrites c:\config.sys with each
boot, but I didn't dig to see if there was another config
file elsewhere.

Any help is appreciated. I'm currently using 98 and NT2000
and not sure whether I want to jump into XP. I use a
couple DOS apps that definitely need EMS.

 

[Timothy]

Does XP oprovide support for Expanded Memory? I mean LIM
4.0 EMS used by DOS applications before Extended Memory
(XMS) became widely supported. In the past this support
could be by loading EMM386.exe in config.sys.

And on that subject, does XP give you a way of manually
customizing config.sys? My brief experience in ME
indicates that the OS overwrites c:\config.sys with each
boot, but I didn't dig to see if there was another config
file elsewhere.

Any help is appreciated. I'm currently using 98 and NT2000
and not sure whether I want to jump into XP. I use a
couple DOS apps that definitely need EMS.

use msconfig

 

[Donald Link]

NO, NO, XP does not use the config.sys period.

 

[Sharon F]

Does XP oprovide support for Expanded Memory? I mean LIM
4.0 EMS used by DOS applications before Extended Memory
(XMS) became widely supported. In the past this support
could be by loading EMM386.exe in config.sys.

And on that subject, does XP give you a way of manually
customizing config.sys? My brief experience in ME
indicates that the OS overwrites c:\config.sys with each
boot, but I didn't dig to see if there was another config
file elsewhere.

Any help is appreciated. I'm currently using 98 and NT2000
and not sure whether I want to jump into XP. I use a
couple DOS apps that definitely need EMS.

Two areas where you can tweak memory settings for DOS programs are the
properties of the DOS program's shortcut and autoexec.nt. The following
"recipe" is courtesy of MVP Alex Nichol:

"...One that I always suggest for DOS programs (not in a games context)
is an edit to config.nt to *enable* EMM and hence allow the LH items to
work, and for that matter the pif settings. What seems best is the line
EMM = B=4000 RAM It seems to need the B=4000 explicitly, even though
that value is the default, and the exact spacing round the first =, not
the second.

Then you get around 612 K conventional memory on running the DOS program
(eg mem.exe) from a shortcut; and I suggest also using explicit values
(generous ones) in the PIF for EMM etc."

Sharon F
MS MVP
[Windows XP - Shell/User]