16 Bit Windows Subsystem Error

[Eichhorn18]

Hello. I recently tried to install a game on my computer. It was made in 1999 from what I can read on the cd although I do not have the cd case or box it came in so I cannot check the sys requirments. When clicked on install on the auto load menu that poped up I was greeted with a "16 Bit Windows Subsystem" box the read as follows: "H:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application."

My options were close and ignor. I cant seem to install. Anyone know whats wrong?

Oh and for the record I am running XP home with sp2.

Thanks

[redduc900]

Error message when you install or start an MS-DOS or 16-bit Windows-based program
http://support.microsoft.com/default.aspx?scid=kb;en-us;324767&Product=winxp

This installaton program will reinstall the missing or corrupt WinXP system files command.com, autoexec.nt and config.nt. The absence or corruption of one or more of these files causes a "16 Bit Subsystem" error.

XP_Fix.EXE by TRF Systems, Inc.
http://www.visualtour.com/downloads/xp_fix.exe

[Athlonight]

you cant use 16bit proggies in XP, sorry boss.

[redduc900]

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

Taken from the above article...
Most Windows 16-bit programs run without problems in Microsoft Windows XP
How to Troubleshoot 16-Bit Windows Programs in Windows XP
http://support.microsoft.com/kb/314495/EN-US/

Also, this is taken from the above troubleshooting article...
Many different 16-bit programs designed to run under Microsoft Windows 3.1 have been tested with Windows XP
In addition, programs that were originally designed for the older OS's like Win95, 98, etc. can be run in XP by using Windows Program Compatibility Mode...

HOW TO: Use Windows Program Compatibility Mode in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;292533
This mode provides an environment for running programs that closely reflects the behavior of earlier Windows operating systems.

[Slackfumasta]

this is what should be in your autoexec.nt file:

@echo off

REM AUTOEXEC.BAT is not used to initialize the MS-DOS environment.
REM AUTOEXEC.NT is used to initialize the MS-DOS environment unless a
REM different startup file is specified in an application's PIF.

REM Install CD ROM extensions
lh %SystemRoot%\system32\mscdexnt.exe

REM Install network redirector (load before dosx.exe)
lh %SystemRoot%\system32\redir

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

REM The following line enables Sound Blaster 2.0 support on NTVDM.
REM The command for setting the BLASTER environment is as follows:
REM SET BLASTER=A220 I5 D1 P330
REM where:
REM A specifies the sound blaster's base I/O port
REM I specifies the interrupt request line
REM D specifies the 8-bit DMA channel
REM P specifies the MPU-401 base I/O port
REM T specifies the type of sound blaster card
REM 1 - Sound Blaster 1.5
REM 2 - Sound Blaster Pro I
REM 3 - Sound Blaster 2.0
REM 4 - Sound Blaster Pro II
REM 6 - SOund Blaster 16/AWE 32/32/64
REM
REM The default value is A220 I5 D1 T3 and P330. If any of the switches is
REM left unspecified, the default value will be used. (NOTE, since all the
REM ports are virtualized, the information provided here does not have to
REM match the real hardware setting.) NTVDM supports Sound Blaster 2.0 only.
REM The T switch must be set to 3, if specified.
SET BLASTER=A220 I5 D1 P330 T3

REM To disable the sound blaster 2.0 support on NTVDM, specify an invalid
REM SB base I/O port address. For example:
REM SET BLASTER=A0


Copy and paste that into your file and problem solved! That is, if you didn't go through the links that redduc posted (which would also fix the problem, probably better).