16 bit Windows Subsystem

"Rock" wrote:

Chris wrote:
For some reason, I get a warning stating that
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application. when i try to open certain programs that used to work on my
computer or work on other computers with windows xp. If someone has any idea
as to how i could fix this it'd be greatly appreciated.

Thankyou






I'm having trouble opening up a program from a cd rom . I never used to
have trouble. I am getting an error message.
"16 bit windows subsystem
config.nt The system file is not suitable for running MS-Dos or
Microsoft Window applications.Choose close to terminate this application."
Anybody know how I can fix this? DO I NEED TO COPY MY CONFIG.NT FROM THE
WINDOWS XP SOFTWARE THAT CAME FROM MY SYSTEM ? HOW DO I DO THIS?
CHORD


THE FOLLOWING WAS A CUT AND PASTE FROM MICROSOFT. LOOK AT MY QUESTION
CHORD

16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Winnt\System32\config.nt The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
config.nt The system file is not suitable for running MS-DOS and Microsoft
Windows applications. Choose 'Close' to terminate the application.
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Windows\System32\Autoexec.nt The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
Although you may be prompted to quit the program or ignore the error
message, either selection makes the program quit.
CAUSE
This issue may occur if one or more of the following files are missing or
damaged: • Config.nt
• Autoexec.nt
• Command.com



RESOLUTION MY QUESTION DO I USE MY WINDOWS XP SOFTWARE AND COPY THE
CONFIG.NT FROM THERE? Chord



To resolve this issue: 1. Insert the CD into the CD drive or DVD drive.
2. Click Start, and then click Run.
3. In the Open box, type cmd, and then click OK.
4. At the command prompt, type the following commands, pressing ENTER after
each command:


expand CD-ROM Drive Letter:\i386\config.nt_ c:\windows\system32\config.nt
expand CD-ROM Drive Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt
expand CD-ROM Drive Letter:\i386\command.co_ c:\windows\system32\command.com
exit
5. Start or install the program. If the issue is resolved, do not complete
the remaining steps. If the issue is not resolved, go to the next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from your
Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close the
Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close the
Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and then
click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
18. Locate the Command.com file, right-click the expanded Command.com file,
and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt files
from the Repair folder in Windows to the System folder. To do so, follow
these steps: 1. Click Start, click Run, type c:\windows\repair, and then
click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then click
Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be removed
after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft Knowledge
Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS Subsystem"
error message when you run an MS-DOS or 16-Bit Windows program in Windows
Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

--------------------------------------------------------------------------------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.
http://groups.google.com/groups?selm...g. google.com

AVAST (free antivirus software) can be the cause if SP2 is installed:
http://groups.google.com/groups?selm...%40comcast.com

You can put back the standard version of autoexec.nt by copying a
backup copy held in windows\repair to windows\system32.

Seems to be an epidemic lately....

This can be caused by a trojan/virus/worm.

Get rid of the trojan/virus/worm.

Update your antivirus software and run a full system scan.

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

Copy the autoexec.nt file from C:\Windows\Repair to C:\Windows\System32
And set Attributes for autoexec.nt to Read-only.

Or %systemroot%\Repair to %systemroot%\System32

Read-only
[[Specifies whether this file is read-only, which means that it cannot be
changed or accidentally deleted.]]

1. Right click the file.
2. Properties.
3. Select: Read-only.
4. Click: Apply.
5. Click: OK.

16-bit MS-DOS Subsystem error while installing or running a DOS application
http://windowsxp.mvps.org/16bit.htm

MS-DOS or 16-bit Windows-based program Error Message
http://www.kellys-korner-xp.com/xp_m.htm#16bit

Error message when you install or start an MS-DOS or 16-bit Windows-based
program
http://support.microsoft.com/default...b;en-us;324767

"16 Bit MS-DOS Subsystem" Error Message When You Install a Program
http://support.microsoft.com/default...b;en-us;314452

Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default...b;en-us;314106

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Rock" wrote:

Chris wrote:
For some reason, I get a warning stating that
C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for
running MS-DOS and Microsoft Windows applications. Choose 'Close' to
terminate the application. when i try to open certain programs that
used to work on my computer or work on other computers with windows xp.
If someone has any idea as to how i could fix this it'd be greatly
appreciated.

Thankyou






I'm having trouble opening up a program from a cd rom . I never used to
have trouble. I am getting an error message.
"16 bit windows subsystem
config.nt The system file is not suitable for running MS-Dos or
Microsoft Window applications.Choose close to terminate this application."
Anybody know how I can fix this? DO I NEED TO COPY MY CONFIG.NT FROM THE
WINDOWS XP SOFTWARE THAT CAME FROM MY SYSTEM ? HOW DO I DO THIS?
CHORD


THE FOLLOWING WAS A CUT AND PASTE FROM MICROSOFT. LOOK AT MY QUESTION
CHORD

16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Winnt\System32\config.nt The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
config.nt The system file is not suitable for running MS-DOS and Microsoft
Windows applications. Choose 'Close' to terminate the application.
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Windows\System32\Autoexec.nt The system file is not suitable for
running MS-DOS and Microsoft Windows applications. Choose 'Close' to
terminate the application.
Although you may be prompted to quit the program or ignore the error
message, either selection makes the program quit.
CAUSE
This issue may occur if one or more of the following files are missing or
damaged: • Config.nt
• Autoexec.nt
• Command.com



RESOLUTION MY QUESTION DO I USE MY WINDOWS XP SOFTWARE AND COPY THE
CONFIG.NT FROM THERE? Chord



To resolve this issue: 1. Insert the CD into the CD drive or DVD drive.
2. Click Start, and then click Run.
3. In the Open box, type cmd, and then click OK.
4. At the command prompt, type the following commands, pressing ENTER
after each command:


expand CD-ROM Drive Letter:\i386\config.nt_ c:\windows\system32\config.nt
expand CD-ROM Drive Letter:\i386\autoexec.nt_
c:\windows\system32\autoexec.nt expand CD-ROM Drive
Letter:\i386\command.co_ c:\windows\system32\command.com exit
5. Start or install the program. If the issue is resolved, do not complete
the remaining steps. If the issue is not resolved, go to the next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from your
Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close the
Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close the
Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt files
from the Repair folder in Windows to the System folder. To do so, follow
these steps: 1. Click Start, click Run, type c:\windows\repair, and then
click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then click
Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be removed
after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft Knowledge
Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS Subsystem"
error message when you run an MS-DOS or 16-Bit Windows program in Windows
Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

--------------------------------------------------------------------------
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.

http://groups.google.com/groups?selm...g. google.com

AVAST (free antivirus software) can be the cause if SP2 is installed:
http://groups.google.com/groups?selm...%40comcast.com

You can put back the standard version of autoexec.nt by copying a
backup copy held in windows\repair to windows\system32.

"Wesley Vogel" wrote:

Seems to be an epidemic lately....

This can be caused by a trojan/virus/worm.

Get rid of the trojan/virus/worm.

Update your antivirus software and run a full system scan.

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

Copy the autoexec.nt file from C:\Windows\Repair to C:\Windows\System32
And set Attributes for autoexec.nt to Read-only.

Or %systemroot%\Repair to %systemroot%\System32

Read-only
[[Specifies whether this file is read-only, which means that it cannot be
changed or accidentally deleted.]]

1. Right click the file.
2. Properties.
3. Select: Read-only.
4. Click: Apply.
5. Click: OK.

16-bit MS-DOS Subsystem error while installing or running a DOS application
http://windowsxp.mvps.org/16bit.htm

MS-DOS or 16-bit Windows-based program Error Message
http://www.kellys-korner-xp.com/xp_m.htm#16bit

Error message when you install or start an MS-DOS or 16-bit Windows-based
program
http://support.microsoft.com/default...b;en-us;324767

"16 Bit MS-DOS Subsystem" Error Message When You Install a Program
http://support.microsoft.com/default...b;en-us;314452

Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default...b;en-us;314106

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Rock" wrote:
Thankyou






I'm having trouble opening up a program from a cd rom . I never used to
have trouble. I am getting an error message.
"16 bit windows subsystem
config.nt The system file is not suitable for running MS-Dos or
Microsoft Window applications.Choose close to terminate this application."
Anybody know how I can fix this? DO I NEED TO COPY MY CONFIG.NT FROM THE
WINDOWS XP SOFTWARE THAT CAME FROM MY SYSTEM ? HOW DO I DO THIS?
CHORD


THE FOLLOWING WAS A CUT AND PASTE FROM MICROSOFT. LOOK AT MY QUESTION
CHORD

16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Winnt\System32\config.nt The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the
application.
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
config.nt The system file is not suitable for running MS-DOS and Microsoft
Windows applications. Choose 'Close' to terminate the application.
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Windows\System32\Autoexec.nt The system file is not suitable for
running MS-DOS and Microsoft Windows applications. Choose 'Close' to
terminate the application.
Although you may be prompted to quit the program or ignore the error
message, either selection makes the program quit.
CAUSE
This issue may occur if one or more of the following files are missing or
damaged: • Config.nt
• Autoexec.nt
• Command.com



RESOLUTION MY QUESTION DO I USE MY WINDOWS XP SOFTWARE AND COPY THE
CONFIG.NT FROM THERE? Chord



To resolve this issue: 1. Insert the CD into the CD drive or DVD drive.
2. Click Start, and then click Run.
3. In the Open box, type cmd, and then click OK.
4. At the command prompt, type the following commands, pressing ENTER
after each command:


expand CD-ROM Drive Letter:\i386\config.nt_ c:\windows\system32\config.nt
expand CD-ROM Drive Letter:\i386\autoexec.nt_
c:\windows\system32\autoexec.nt expand CD-ROM Drive
Letter:\i386\command.co_ c:\windows\system32\command.com exit
5. Start or install the program. If the issue is resolved, do not complete
the remaining steps. If the issue is not resolved, go to the next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from your
Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close the
Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close the
Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt files
from the Repair folder in Windows to the System folder. To do so, follow
these steps: 1. Click Start, click Run, type c:\windows\repair, and then
click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then click
Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be removed
after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft Knowledge
Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS Subsystem"
error message when you run an MS-DOS or 16-Bit Windows program in Windows
Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

--------------------------------------------------------------------------
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.

http://groups.google.com/groups?selm...g. google.com

AVAST (free antivirus software) can be the cause if SP2 is installed:
http://groups.google.com/groups?selm...%40comcast.com

You can put back the standard version of autoexec.nt by copying a
backup copy held in windows\repair to windows\system32.

If there was a reply in there, I couldn't decipher it.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Wesley Vogel" wrote:

Seems to be an epidemic lately....

This can be caused by a trojan/virus/worm.

Get rid of the trojan/virus/worm.

Update your antivirus software and run a full system scan.

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

Copy the autoexec.nt file from C:\Windows\Repair to C:\Windows\System32
And set Attributes for autoexec.nt to Read-only.

Or %systemroot%\Repair to %systemroot%\System32

Read-only
[[Specifies whether this file is read-only, which means that it cannot be
changed or accidentally deleted.]]

1. Right click the file.
2. Properties.
3. Select: Read-only.
4. Click: Apply.
5. Click: OK.

16-bit MS-DOS Subsystem error while installing or running a DOS
application http://windowsxp.mvps.org/16bit.htm

MS-DOS or 16-bit Windows-based program Error Message
http://www.kellys-korner-xp.com/xp_m.htm#16bit

Error message when you install or start an MS-DOS or 16-bit Windows-based
program
http://support.microsoft.com/default...b;en-us;324767

"16 Bit MS-DOS Subsystem" Error Message When You Install a Program
http://support.microsoft.com/default...b;en-us;314452

Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default...b;en-us;314106

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Rock" wrote:
Thankyou






I'm having trouble opening up a program from a cd rom . I never used
to have trouble. I am getting an error message.
"16 bit windows subsystem
config.nt The system file is not suitable for running MS-Dos or
Microsoft Window applications.Choose close to terminate this
application." Anybody know how I can fix this? DO I NEED TO COPY MY
CONFIG.NT FROM THE WINDOWS XP SOFTWARE THAT CAME FROM MY SYSTEM ? HOW
DO I DO THIS? CHORD


THE FOLLOWING WAS A CUT AND PASTE FROM MICROSOFT. LOOK AT MY QUESTION
CHORD

16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Winnt\System32\config.nt The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate
the application.
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
config.nt The system file is not suitable for running MS-DOS and
Microsoft Windows applications. Choose 'Close' to terminate the
application. 16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Windows\System32\Autoexec.nt The system file is not suitable for
running MS-DOS and Microsoft Windows applications. Choose 'Close' to
terminate the application.
Although you may be prompted to quit the program or ignore the error
message, either selection makes the program quit.
CAUSE
This issue may occur if one or more of the following files are missing
or damaged: • Config.nt
• Autoexec.nt
• Command.com



RESOLUTION MY QUESTION DO I USE MY WINDOWS XP SOFTWARE AND COPY THE
CONFIG.NT FROM THERE? Chord



To resolve this issue: 1. Insert the CD into the CD drive or DVD drive.
2. Click Start, and then click Run.
3. In the Open box, type cmd, and then click OK.
4. At the command prompt, type the following commands, pressing ENTER
after each command:


expand CD-ROM Drive Letter:\i386\config.nt_
c:\windows\system32\config.nt expand CD-ROM Drive
Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt expand CD-ROM
Drive Letter:\i386\command.co_ c:\windows\system32\command.com exit
5. Start or install the program. If the issue is resolved, do not
complete the remaining steps. If the issue is not resolved, go to the
next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from your
Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close the
Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close
the Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt
files from the Repair folder in Windows to the System folder. To do so,
follow these steps: 1. Click Start, click Run, type c:\windows\repair,
and then click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then
click Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be removed
after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft
Knowledge Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS
Subsystem" error message when you run an MS-DOS or 16-Bit Windows
program in Windows Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

------------------------------------------------------------------------
--
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.


http://groups.google.com/groups?selm...g. google.com

AVAST (free antivirus software) can be the cause if SP2 is installed:

http://groups.google.com/groups?selm...%40comcast.com

You can put back the standard version of autoexec.nt by copying a
backup copy held in windows\repair to windows\system32.

"Wesley Vogel" wrote:

If there was a reply in there, I couldn't decipher it.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

I got rid of the old error message. Now I have a new one, NTVDM KERNAL
missing 16 bit system module. What I did was download the
autoexec.nt,command.nt and config.nt. and unzipped them and extracted them to
windows folder. Seems like the only file copied was auto.exe. Tell me what do
to. I want to be able to run my programs.
Chord









In ,
chord hunted and pecked:
"Wesley Vogel" wrote:

Seems to be an epidemic lately....

This can be caused by a trojan/virus/worm.

Get rid of the trojan/virus/worm.

Update your antivirus software and run a full system scan.

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

Copy the autoexec.nt file from C:\Windows\Repair to C:\Windows\System32
And set Attributes for autoexec.nt to Read-only.

Or %systemroot%\Repair to %systemroot%\System32

Read-only
[[Specifies whether this file is read-only, which means that it cannot be
changed or accidentally deleted.]]

1. Right click the file.
2. Properties.
3. Select: Read-only.
4. Click: Apply.
5. Click: OK.

16-bit MS-DOS Subsystem error while installing or running a DOS
application http://windowsxp.mvps.org/16bit.htm

MS-DOS or 16-bit Windows-based program Error Message
http://www.kellys-korner-xp.com/xp_m.htm#16bit

Error message when you install or start an MS-DOS or 16-bit Windows-based
program
http://support.microsoft.com/default...b;en-us;324767

"16 Bit MS-DOS Subsystem" Error Message When You Install a Program
http://support.microsoft.com/default...b;en-us;314452

Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default...b;en-us;314106

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Rock" wrote:
Thankyou






I'm having trouble opening up a program from a cd rom . I never used
to have trouble. I am getting an error message.
"16 bit windows subsystem
config.nt The system file is not suitable for running MS-Dos or
Microsoft Window applications.Choose close to terminate this
application." Anybody know how I can fix this? DO I NEED TO COPY MY
CONFIG.NT FROM THE WINDOWS XP SOFTWARE THAT CAME FROM MY SYSTEM ? HOW
DO I DO THIS? CHORD


THE FOLLOWING WAS A CUT AND PASTE FROM MICROSOFT. LOOK AT MY QUESTION
CHORD

16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Winnt\System32\config.nt The system file is not suitable for running
MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate
the application.
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
config.nt The system file is not suitable for running MS-DOS and
Microsoft Windows applications. Choose 'Close' to terminate the
application. 16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Windows\System32\Autoexec.nt The system file is not suitable for
running MS-DOS and Microsoft Windows applications. Choose 'Close' to
terminate the application.
Although you may be prompted to quit the program or ignore the error
message, either selection makes the program quit.
CAUSE
This issue may occur if one or more of the following files are missing
or damaged: • Config.nt
• Autoexec.nt
• Command.com



RESOLUTION MY QUESTION DO I USE MY WINDOWS XP SOFTWARE AND COPY THE
CONFIG.NT FROM THERE? Chord



To resolve this issue: 1. Insert the CD into the CD drive or DVD drive.
2. Click Start, and then click Run.
3. In the Open box, type cmd, and then click OK.
4. At the command prompt, type the following commands, pressing ENTER
after each command:


expand CD-ROM Drive Letter:\i386\config.nt_
c:\windows\system32\config.nt expand CD-ROM Drive
Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt expand CD-ROM
Drive Letter:\i386\command.co_ c:\windows\system32\command.com exit
5. Start or install the program. If the issue is resolved, do not
complete the remaining steps. If the issue is not resolved, go to the
next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from your
Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close the
Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close
the Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click Paste.
Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt
files from the Repair folder in Windows to the System folder. To do so,
follow these steps: 1. Click Start, click Run, type c:\windows\repair,
and then click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then
click Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be removed
after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft
Knowledge Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS
Subsystem" error message when you run an MS-DOS or 16-Bit Windows
program in Windows Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

------------------------------------------------------------------------
--
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.


http://groups.google.com/groups?selm...g. google.com

AVAST (free antivirus software) can be the cause if SP2 is installed:

http://groups.google.com/groups?selm...%40comcast.com

You can put back the standard version of autoexec.nt by copying a
backup copy held in windows\repair to windows\system32.

Chord,

The first thing that you want to do is get rid of any malware that you might
have on your machine.

Update your antivirus software and run a full system scan.

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

NTVDM KERNEL: missing 16-bit system module
please re-install the following module to your system32
directory: name of missing file

What is the name of the missing file or module in the NTVDM KERNEL error
message?

NTVDM is NTVDM.exe it is the NT Virtual DOS Machine. NTVDM.exe runs old
16-bit applications.

What is the name of the program that you are trying to run from your CD? Is
it an old MS-DOS program?

None of these 16-bit error messages should be popping up if you are trying
to run a modern program.

You should run the System File Checker (sfc.exe) it replaces screwed up
system files.

Load your XP CD in your CD drive.

Start | Run | Type or paste: sfc /scannow | Click OK

If you have XP Home and it asks for your XP Pro CD, see this KB article...

You may be prompted to insert a Windows XP Professional CD when you run the
System File Checker tool in Windows XP Home Edition
http://support.microsoft.com/default...b;en-us;897128

If SFC.EXE did anything it will be in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Click System | Look at any Windows File Protection
entries

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)
http://www.updatexp.com/scannow-sfc.html

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Wesley Vogel" wrote:

If there was a reply in there, I couldn't decipher it.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

I got rid of the old error message. Now I have a new one, NTVDM KERNAL
missing 16 bit system module. What I did was download the
autoexec.nt,command.nt and config.nt. and unzipped them and extracted
them to windows folder. Seems like the only file copied was auto.exe.
Tell me what do to. I want to be able to run my programs.
Chord









In ,
chord hunted and pecked:
"Wesley Vogel" wrote:

Seems to be an epidemic lately....

This can be caused by a trojan/virus/worm.

Get rid of the trojan/virus/worm.

Update your antivirus software and run a full system scan.

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

Copy the autoexec.nt file from C:\Windows\Repair to C:\Windows\System32
And set Attributes for autoexec.nt to Read-only.

Or %systemroot%\Repair to %systemroot%\System32

Read-only
[[Specifies whether this file is read-only, which means that it cannot
be changed or accidentally deleted.]]

1. Right click the file.
2. Properties.
3. Select: Read-only.
4. Click: Apply.
5. Click: OK.

16-bit MS-DOS Subsystem error while installing or running a DOS
application http://windowsxp.mvps.org/16bit.htm

MS-DOS or 16-bit Windows-based program Error Message
http://www.kellys-korner-xp.com/xp_m.htm#16bit

Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/default...b;en-us;324767

"16 Bit MS-DOS Subsystem" Error Message When You Install a Program
http://support.microsoft.com/default...b;en-us;314452

Troubleshooting MS-DOS-based programs in Windows XP
http://support.microsoft.com/default...b;en-us;314106

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Rock" wrote:
Thankyou






I'm having trouble opening up a program from a cd rom . I never
used to have trouble. I am getting an error message.
"16 bit windows subsystem
config.nt The system file is not suitable for running MS-Dos or
Microsoft Window applications.Choose close to terminate this
application." Anybody know how I can fix this? DO I NEED TO COPY MY
CONFIG.NT FROM THE WINDOWS XP SOFTWARE THAT CAME FROM MY SYSTEM ? HOW
DO I DO THIS? CHORD


THE FOLLOWING WAS A CUT AND PASTE FROM MICROSOFT. LOOK AT MY QUESTION
CHORD

16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Winnt\System32\config.nt The system file is not suitable for
running MS-DOS and Microsoft Windows applications. Choose 'Close' to
terminate the application.
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
config.nt The system file is not suitable for running MS-DOS and
Microsoft Windows applications. Choose 'Close' to terminate the
application. 16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Windows\System32\Autoexec.nt The system file is not suitable for
running MS-DOS and Microsoft Windows applications. Choose 'Close' to
terminate the application.
Although you may be prompted to quit the program or ignore the error
message, either selection makes the program quit.
CAUSE
This issue may occur if one or more of the following files are missing
or damaged: • Config.nt
• Autoexec.nt
• Command.com



RESOLUTION MY QUESTION DO I USE MY WINDOWS XP SOFTWARE AND COPY THE
CONFIG.NT FROM THERE? Chord



To resolve this issue: 1. Insert the CD into the CD drive or DVD
drive.
2. Click Start, and then click Run.
3. In the Open box, type cmd, and then click OK.
4. At the command prompt, type the following commands, pressing ENTER
after each command:


expand CD-ROM Drive Letter:\i386\config.nt_
c:\windows\system32\config.nt expand CD-ROM Drive
Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt expand
CD-ROM Drive Letter:\i386\command.co_ c:\windows\system32\command.com
exit
5. Start or install the program. If the issue is resolved, do not
complete the remaining steps. If the issue is not resolved, go to the
next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from
your Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close
the Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close
the Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste. Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt
files from the Repair folder in Windows to the System folder. To do
so, follow these steps: 1. Click Start, click Run, type
c:\windows\repair, and then click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click
OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then
click Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be
removed after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft
Knowledge Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS
Subsystem" error message when you run an MS-DOS or 16-Bit Windows
program in Windows Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

----------------------------------------------------------------------
--
--
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.



http://groups.google.com/groups?selm...g. google.com

AVAST (free antivirus software) can be the cause if SP2 is installed:

http://groups.google.com/groups?selm...%40comcast.com

You can put back the standard version of autoexec.nt by copying a
backup copy held in windows\repair to windows\system32.

"To Wesley Vogel"

From Chord

The first thing that you want to do is get rid of any malware that you might
have on your machine.

Update your antivirus software and run a full system scan. "I did this. No virus"

Chord

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

NTVDM KERNEL: missing 16-bit system module
please re-install the following module to your system32
directory: name of missing file

What is the name of the missing file or module in the NTVDM KERNEL error
message?

NTVDM is NTVDM.exe it is the NT Virtual DOS Machine. NTVDM.exe runs old
16-bit applications.

What is the name of the program that you are trying to run from your CD? Is
it an old MS-DOS program? " BAND IN THE BOX 2001"

Chord


None of these 16-bit error messages should be popping up if you are trying
to run a modern program.

You should run the System File Checker (sfc.exe) it replaces screwed up
system files. "I ran This"

Chord

Load your XP CD in your CD drive." " I did this"
Start | Run | Type or paste: sfc /scannow | Click OK

If you have XP Home and it asks for your XP Pro CD, see this KB article...

You may be prompted to insert a Windows XP Professional CD when you run the
System File Checker tool in Windows XP Home Edition
http://support.microsoft.com/default...b;en-us;897128
"Wes, I was prompted to insert Windows XP Professional CD. The message was Files that are required to run properly must be copied to the dll cache. Insert you windows xp professional cd-rom -now. I keep hitting retry when this message comes up. Seems i'm going around in circles. Nothing is being done."

Chord


If SFC.EXE did anything it will be in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Click System | Look at any Windows File Protection
entries. " I did this. Just said Windows file protection started"

Chord

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)
http://www.updatexp.com/scannow-sfc.html

"Wes, I made a copy of Fp40ext.inf and Ims.inf in the service pak
386 folder. Still getting errormessage please reinstall following module to
your systemn 32 directory COMM.DRIVE What do I do next? anybody can help
me?"

Chord
--







Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Wesley Vogel" wrote:

If there was a reply in there, I couldn't decipher it.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

I got rid of the old error message. Now I have a new one, NTVDM KERNAL
missing 16 bit system module. What I did was download the
autoexec.nt,command.nt and config.nt. and unzipped them and extracted
them to windows folder. Seems like the only file copied was auto.exe.
Tell me what do to. I want to be able to run my programs.
Chord









expand CD-ROM Drive Letter:\i386\config.nt_
c:\windows\system32\config.nt expand CD-ROM Drive
Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt expand
CD-ROM Drive Letter:\i386\command.co_ c:\windows\system32\command.com
exit
5. Start or install the program. If the issue is resolved, do not
complete the remaining steps. If the issue is not resolved, go to the
next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from
your Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close
the Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close
the Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste. Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt
files from the Repair folder in Windows to the System folder. To do
so, follow these steps: 1. Click Start, click Run, type
c:\windows\repair, and then click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click
OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then
click Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be
removed after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft
Knowledge Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS
Subsystem" error message when you run an MS-DOS or 16-Bit Windows
program in Windows Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

----------------------------------------------------------------------
--
--
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.



http://groups.google.com/groups?selm...g. google.com

"chord" wrote:



"To Wesley Vogel"
Never received a reply from anybody.

From Chord

The first thing that you want to do is get rid of any malware that you might
have on your machine.

Update your antivirus software and run a full system scan. "I did this. No virus"

Chord

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

NTVDM KERNEL: missing 16-bit system module
please re-install the following module to your system32
directory: name of missing file

What is the name of the missing file or module in the NTVDM KERNEL error
message?

NTVDM is NTVDM.exe it is the NT Virtual DOS Machine. NTVDM.exe runs old
16-bit applications.

What is the name of the program that you are trying to run from your CD? Is
it an old MS-DOS program? " BAND IN THE BOX 2001"

Chord


None of these 16-bit error messages should be popping up if you are trying
to run a modern program.

You should run the System File Checker (sfc.exe) it replaces screwed up
system files. "I ran This"

Chord

Load your XP CD in your CD drive." " I did this"
Start | Run | Type or paste: sfc /scannow | Click OK

If you have XP Home and it asks for your XP Pro CD, see this KB article...

You may be prompted to insert a Windows XP Professional CD when you run the
System File Checker tool in Windows XP Home Edition
http://support.microsoft.com/default...b;en-us;897128
"Wes, I was prompted to insert Windows XP Professional CD. The message was Files that are required to run properly must be copied to the dll cache. Insert you windows xp professional cd-rom -now. I keep hitting retry when this message comes up. Seems i'm going around in circles. Nothing is being done."

Chord


If SFC.EXE did anything it will be in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Click System | Look at any Windows File Protection
entries. " I did this. Just said Windows file protection started"

Chord

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)
http://www.updatexp.com/scannow-sfc.html

"Wes, I made a copy of Fp40ext.inf and Ims.inf in the service pak
386 folder. Still getting errormessage please reinstall following module to
your systemn 32 directory COMM.DRIVE What do I do next? anybody can help
me?"

Chord
--


To Wesley Vogel"

From Chord

The first thing that you want to do is get rid of any malware that you might
have on your machine.

Update your antivirus software and run a full system scan. "I did this. No virus"

Chord

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

NTVDM KERNEL: missing 16-bit system module
please re-install the following module to your system32
directory: name of missing file

What is the name of the missing file or module in the NTVDM KERNEL error
message?

NTVDM is NTVDM.exe it is the NT Virtual DOS Machine. NTVDM.exe runs old
16-bit applications.

What is the name of the program that you are trying to run from your CD? Is
it an old MS-DOS program? " BAND IN THE BOX 2001"

Chord


None of these 16-bit error messages should be popping up if you are trying
to run a modern program.

You should run the System File Checker (sfc.exe) it replaces screwed up
system files. "I ran This"

Chord

Load your XP CD in your CD drive." " I did this"
Start | Run | Type or paste: sfc /scannow | Click OK

If you have XP Home and it asks for your XP Pro CD, see this KB article...

You may be prompted to insert a Windows XP Professional CD when you run the
System File Checker tool in Windows XP Home Edition
http://support.microsoft.com/default...b;en-us;897128
"Wes, I was prompted to insert Windows XP Professional CD. The message was Files that are required to run properly must be copied to the dll cache. Insert you windows xp professional cd-rom -now. I keep hitting retry when this message comes up. Seems i'm going around in circles. Nothing is being done."

Chord


If SFC.EXE did anything it will be in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Click System | Look at any Windows File Protection
entries. " I did this. Just said Windows file protection started"

Chord

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)
http://www.updatexp.com/scannow-sfc.html

"Wes, I made a copy of Fp40ext.inf and Ims.inf in the service pak
386 folder. Still getting errormessage please reinstall following module to
your systemn 32 directory COMM.DRIVE What do I do next? anybody can help
me?"

Chord
--







Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Wesley Vogel" wrote:

If there was a reply in there, I couldn't decipher it.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

I got rid of the old error message. Now I have a new one, NTVDM KERNAL
missing 16 bit system module. What I did was download the
autoexec.nt,command.nt and config.nt. and unzipped them and extracted
them to windows folder. Seems like the only file copied was auto.exe.
Tell me what do to. I want to be able to run my programs.
Chord









expand CD-ROM Drive Letter:\i386\config.nt_
c:\windows\system32\config.nt expand CD-ROM Drive
Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt expand
CD-ROM Drive Letter:\i386\command.co_ c:\windows\system32\command.com
exit
5. Start or install the program. If the issue is resolved, do not
complete the remaining steps. If the issue is not resolved, go to the
next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from
your Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close
the Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close
the Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste. Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt
files from the Repair folder in Windows to the System folder. To do
so, follow these steps: 1. Click Start, click Run, type
c:\windows\repair, and then click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click
OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then
click Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be
removed after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft
Knowledge Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS
Subsystem" error message when you run an MS-DOS or 16-Bit Windows
program in Windows Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

----------------------------------------------------------------------
--
--
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.



http://groups.google.com/groups?selm...g. google.com







Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Wesley Vogel" wrote:

If there was a reply in there, I couldn't decipher it.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

I got rid of the old error message. Now I have a new one, NTVDM KERNAL
missing 16 bit system module. What I did was download the
autoexec.nt,command.nt and config.nt. and unzipped them and extracted
them to windows folder. Seems like the only file copied was auto.exe.
Tell me what do to. I want to be able to run my programs.
Chord









expand CD-ROM Drive Letter:\i386\config.nt_
c:\windows\system32\config.nt expand CD-ROM Drive
Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt expand
CD-ROM Drive Letter:\i386\command.co_ c:\windows\system32\command.com
exit
5. Start or install the program. If the issue is resolved, do not
complete the remaining steps. If the issue is not resolved, go to the
next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from
your Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close
the Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close
the Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste. Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt
files from the Repair folder in Windows to the System folder. To do
so, follow these steps: 1. Click Start, click Run, type
c:\windows\repair, and then click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click
OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then
click Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be
removed after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft
Knowledge Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS
Subsystem" error message when you run an MS-DOS or 16-Bit Windows
program in Windows Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

----------------------------------------------------------------------
--
--
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.



http://groups.google.com/groups?selm...g. google.com

chord" wrote:



"To Wesley Vogel"
Never received a reply from anybody.

From Chord

The first thing that you want to do is get rid of any malware that you might
have on your machine.

Update your antivirus software and run a full system scan. "I did this. No virus"

Chord

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

NTVDM KERNEL: missing 16-bit system module
please re-install the following module to your system32
directory: name of missing file

What is the name of the missing file or module in the NTVDM KERNEL error
message?

NTVDM is NTVDM.exe it is the NT Virtual DOS Machine. NTVDM.exe runs old
16-bit applications.

What is the name of the program that you are trying to run from your CD? Is
it an old MS-DOS program? " BAND IN THE BOX 2001"

Chord


None of these 16-bit error messages should be popping up if you are trying
to run a modern program.

You should run the System File Checker (sfc.exe) it replaces screwed up
system files. "I ran This"

Chord

Load your XP CD in your CD drive." " I did this"
Start | Run | Type or paste: sfc /scannow | Click OK

If you have XP Home and it asks for your XP Pro CD, see this KB article...

You may be prompted to insert a Windows XP Professional CD when you run the
System File Checker tool in Windows XP Home Edition
http://support.microsoft.com/default...b;en-us;897128
"Wes, I was prompted to insert Windows XP Professional CD. The message was Files that are required to run properly must be copied to the dll cache. Insert you windows xp professional cd-rom -now. I keep hitting retry when this message comes up. Seems i'm going around in circles. Nothing is being done."

Chord


If SFC.EXE did anything it will be in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Click System | Look at any Windows File Protection
entries. " I did this. Just said Windows file protection started"

Chord

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)
http://www.updatexp.com/scannow-sfc.html

"Wes, I made a copy of Fp40ext.inf and Ims.inf in the service pak
386 folder. Still getting errormessage please reinstall following module to
your systemn 32 directory COMM.DRIVE What do I do next? anybody can help
me?"

Chord
--


To Wesley Vogel"

From Chord

The first thing that you want to do is get rid of any malware that you might
have on your machine.

Update your antivirus software and run a full system scan. "I did this. No virus"

Chord

Update whatever anti-spyware applications that you have and run a full
system scan with each one.

NTVDM KERNEL: missing 16-bit system module
please re-install the following module to your system32
directory: name of missing file

What is the name of the missing file or module in the NTVDM KERNEL error
message?

NTVDM is NTVDM.exe it is the NT Virtual DOS Machine. NTVDM.exe runs old
16-bit applications.

What is the name of the program that you are trying to run from your CD? Is
it an old MS-DOS program? " BAND IN THE BOX 2001"

Chord


None of these 16-bit error messages should be popping up if you are trying
to run a modern program.

You should run the System File Checker (sfc.exe) it replaces screwed up
system files. "I ran This"

Chord

Load your XP CD in your CD drive." " I did this"
Start | Run | Type or paste: sfc /scannow | Click OK

If you have XP Home and it asks for your XP Pro CD, see this KB article...

You may be prompted to insert a Windows XP Professional CD when you run the
System File Checker tool in Windows XP Home Edition
http://support.microsoft.com/default...b;en-us;897128
"Wes, I was prompted to insert Windows XP Professional CD. The message was Files that are required to run properly must be copied to the dll cache. Insert you windows xp professional cd-rom -now. I keep hitting retry when this message comes up. Seems i'm going around in circles. Nothing is being done."

Chord


If SFC.EXE did anything it will be in the Event Viewer.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Click System | Look at any Windows File Protection
entries. " I did this. Just said Windows file protection started"

Chord

Explains a whole bunch about sfc.exe.
scannow sfc (sfc.exe)
http://www.updatexp.com/scannow-sfc.html

"Wes, I made a copy of Fp40ext.inf and Ims.inf in the service pak
386 folder. Still getting errormessage please reinstall following module to
your systemn 32 directory COMM.DRIVE What do I do next? anybody can help
me?"

Chord
--







Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Wesley Vogel" wrote:

If there was a reply in there, I couldn't decipher it.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

I got rid of the old error message. Now I have a new one, NTVDM KERNAL
missing 16 bit system module. What I did was download the
autoexec.nt,command.nt and config.nt. and unzipped them and extracted
them to windows folder. Seems like the only file copied was auto.exe.
Tell me what do to. I want to be able to run my programs.
Chord









expand CD-ROM Drive Letter:\i386\config.nt_
c:\windows\system32\config.nt expand CD-ROM Drive
Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt expand
CD-ROM Drive Letter:\i386\command.co_ c:\windows\system32\command.com
exit
5. Start or install the program. If the issue is resolved, do not
complete the remaining steps. If the issue is not resolved, go to the
next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from
your Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close
the Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close
the Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste. Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt
files from the Repair folder in Windows to the System folder. To do
so, follow these steps: 1. Click Start, click Run, type
c:\windows\repair, and then click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click
OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then
click Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be
removed after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft
Knowledge Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS
Subsystem" error message when you run an MS-DOS or 16-Bit Windows
program in Windows Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

----------------------------------------------------------------------
--
--
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.



http://groups.google.com/groups?selm...g. google.com







Wes
MS-MVP Windows Shell/User

In ,
chord hunted and pecked:
"Wesley Vogel" wrote:

If there was a reply in there, I couldn't decipher it.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

I got rid of the old error message. Now I have a new one, NTVDM KERNAL
missing 16 bit system module. What I did was download the
autoexec.nt,command.nt and config.nt. and unzipped them and extracted
them to windows folder. Seems like the only file copied was auto.exe.
Tell me what do to. I want to be able to run my programs.
Chord









expand CD-ROM Drive Letter:\i386\config.nt_
c:\windows\system32\config.nt expand CD-ROM Drive
Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt expand
CD-ROM Drive Letter:\i386\command.co_ c:\windows\system32\command.com
exit
5. Start or install the program. If the issue is resolved, do not
complete the remaining steps. If the issue is not resolved, go to the
next step.
6. Note: The Command.com file is not edited or created in this in the
following process. Because of this, you may have to expand it from
your Windows XP CD-ROM.

Start Notepad.
7. In Notepad, type the following entries: dos=high, umb
device=%SYSTEMROOT%\system32\himem.sys
files=40

8. On the File menu, click Save As.
9. In the File Name box, type Config.nt, and then click Save. Close
the Config.nt file.
10. On the File menu, click New.
11. In the new blank document, type the following entries: @echo off
lh %SYSTEMROOT%\system32\mscdexnt.exe
lh %SYSTEMROOT%\system32\redir
lh %SYSTEMROOT%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

12. On the File menu, click Save As.
13. In the File Name box, type Autoexec.nt, and then click Save. Close
the Autoexec.nt file.
14. Start Windows Explorer. Locate the Config.nt file, right-click the
Config.nt file, and then click Copy.
15. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
16. Locate the Autoexec.nt file, right-click the Autoexec.nt file, and
then click Copy.
17. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste.
18. Locate the Command.com file, right-click the expanded Command.com
file, and then click Copy.
19. Right-click the %SYSTEMROOT%\System32 folder, and then click
Paste. Restart your computer.
If the issue continues to occur, copy the Autoexec.nt and Config.nt
files from the Repair folder in Windows to the System folder. To do
so, follow these steps: 1. Click Start, click Run, type
c:\windows\repair, and then click OK.
2. Right-click autoexec.nt, and then click Copy.
3. Click Start, click Run, type c:\windows\system32, and then click
OK.
4. Right-click anywhere in that folder, and then click Paste.
5. Right-click the Autoexect.nt file that you just copied, and then
click Properties.
6. Click to select Read-Only, and then click OK.
7. Repeat steps 1 through 6 to copy the Config.nt file.
Note You must enable Read-Only permissions or the files will be
removed after you restart Windows.
MORE INFORMATION
For more information about MS-DOS-based programs in Windows, click the
following article numbers to view the articles in the Microsoft
Knowledge Base:
305521 (http://support.microsoft.com/kb/305521/) "16-bit MS-DOS
Subsystem" error message when you run an MS-DOS or 16-Bit Windows
program in Windows Server 2003 or Windows 2000 Server
314106 (http://support.microsoft.com/kb/314106/) Troubleshooting
MS-DOS-based programs in Windows XP

----------------------------------------------------------------------
--
--
------

APPLIES TO
• Microsoft Windows XP Professional
• Microsoft Windows XP Home Edition

Back to the top

From Chord
















Error message when you install or start an MS-DOS or 16-bit
Windows-based program
http://support.microsoft.com/?id=324767

Also can be caused by a Trojan installing a file windupdater.exe and
creating registry entries for that file.



http://groups.google.com/groups?selm...g. google.com

Was this post helpful to you?