Member Avatar for cyclones

When i try to play the game or re-install it, i get a message that states:

16 Bit Windows Subsystem

C:\Windows\System32\

The system file is not suitable for running MS-DOS & Microsoft Windows applications. Choose 'close' to terminate the application.

When i try to put a software game CD in to install it, that pop's up.
Can anyone give me info on how to resolve this?!?

Thanks

  • 2 Contributors
  • 1 Reply
  • 217 Views
  • 6 Hours Discussion Span
  • Latest Post Latest Post by nightshade

Dani AI

Generated

A short expert note: the error reported by is the classic 16‑bit/NTVDM problem. ’s suggestion to restore the system’s legacy startup files is the standard first move for a corrupted-file case, but the underlying cause and the correct fix depend on the Windows platform and whether the installer/game actually requires real‑mode DOS or a 16‑bit installer.

Confirm platform first — 64‑bit Windows does not include the NT Virtual DOS Machine (NTVDM) and will not run 16‑bit installers or DOS programs natively; only x86 (32‑bit) Windows supports NTVDM. Guidance for checking the OS bitness and the NTVDM limitation is provided by Microsoft. (learn.microsoft.com)

If the system is 32‑bit, corrupt or missing system files are a common cause. A safe repair sequence is to run the Windows image repair tools and System File Checker (run sfc /scannow from an elevated prompt, and use DISM first when recommended) to restore protected files; also inspect AV/quarantine logs because some cleanup tools can remove legacy files. Microsoft documents these repair steps. (support.microsoft.com)

If the OS is 64‑bit (or repair isn’t practical), two reliable workarounds exist: run pure DOS games under DOSBox (emulator designed for old DOS titles), or create a small 32‑bit guest in a VM (VirtualBox/Hyper‑V/VMware) and install/run the game there — the VM method reliably handles 16‑bit installers as well. Always use official installation media and keep the VM network isolated when testing older software. (dosbox.com)

Summary: ’s file‑restore advice is the right first step for corrupted files on a 32‑bit system; add a platform check, run SFC/DISM where appropriate, and use DOSBox or a 32‑bit VM when the host OS cannot run 16‑bit code.

Member Avatar for nightshade

Hi,

The simplest method to resolve this common problem is to copy
from C:\Windows\repair to C:\Windows\system32 and overwrite the one that is
currently there.

Alternately, you can create a new file and save it to the
\windows\system32 folder to overwrite the corrupted one. Click start/run and
type notepad, then click ok. Copy/paste the below code into it (instead of
typing it in to prevent errors), then click file/"save as". Navigate to the
C:\Windows\system32 folder, change the "save as file" type to "all types"
and name the file , then click save (if prompted to overwrite the
existing one, do so).

@echo off
lh %SystemRoot%\system32\mscdexnt.exe
lh %SystemRoot%\system32\redir
lh %SystemRoot%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

Reboot when finished. This usually fixes it, but you will find further steps
here if it doesn't:

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

Basically, you will have to expand new copies of command.com, ,
and to the system32 folder from the WinXP CD or I386 folder on
your hard drive. Sometimes, you need to create new ones and overwrite the
existing ones - the method is described in the article.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.