Windows Legacy OS forum

General discussion

Running DOS programs after SP2 update

by vtrop / October 16, 2004 4:39 AM PDT

Hello. I am having a problem running a DOS program for videotape labels after I have installed Windows XP Service Pack 2. Before the install, I had no problem running this DOS program (Labels Unlimited). I did not need any special setup or to run it under Windows 98 emulation. I have a Dell 8300 3.0 GHZ Pentium 4 processor with 512 RAM.
Now when I run the program, first I get a full black screen with the blinking cursor and my mouse is a typical DOS mouse cursor (grey square that moves around the screen). If I press Alt + Enter I get a window with a title that reads "ntvdm-928.8cc.2f0001"
If I run the program file directly I get another error: C:\Labels\Labels.exe C:\Windows\System32\autoexec.NT The system file is not suitable for running MS-DOS and Microsoft Windows applications. Press 'Close' to terminate the application.
I think it is referring to the fact that a DOS program is not a secure program to run, but I can't believe this is the end of DOS as we know it. Is this the end of DOS? I can still run a command prompt and I can still type CD\Labels but I still get the same error. Any ideas anyone? I would really appreciate any help someone could suggest. Thanks for reading.

Discussion is locked
You are posting a reply to: Running DOS programs after SP2 update
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: Running DOS programs after SP2 update
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
Re: Running DOS programs after SP2 update
by R. Proffitt Forum moderator / October 16, 2004 4:53 AM PDT
Collapse -
Re: Running DOS programs after SP2 update
by sandy7m / October 23, 2004 8:11 PM PDT

Having the same problem with XP. In my case it is preventing my hanheld computer's application from opening. All I have found out so far is that the file C:\WINNT\SYSTEM32\AUTOEXEC.NT. is something to do with XP running old 16 bit applications (DOS based)

I have hit M$ and a few forums I belong to for an answer.

One thing to note when I did a search for that file there was nothing there.

By the way, I think that SP2 resolved a lot of XP problems and opened a whole new can of worms. Will M$ ever get it right Sad

Collapse -
Re: Running DOS programs after SP2 update
by sandy7m / October 23, 2004 9:53 PM PDT

think I got the answer(s)

The one that worked for me was is to copy the AUTOEXEC.NT file from c:\winnt\repair to c:\winnt\system32.

The other solution that might work is a program called DOSBox0.62
However I have not tried it as I was put off by the fact it is clearly aimed at games rather than applications.

Hope one of these works for you
Sandy McEwan

Collapse -
Re: Running DOS programs after SP2 update
by Cursorcowboy / October 23, 2004 11:21 PM PDT

1. The article [Q324767] explains error messages you may receive and the repair procedures for extracting the files "Config.nt" and "Autoexec.nt" from the Windows media into the "%SYSTEMROOT%\System32 folder" should they become missing or damaged. Also, please note the hyperlinks contained in the section "MORE INFORMATION" for additional troubleshooting.

2. Since Windows allocates resources according to its settings and manages devices accordingly, users can change performance options that control how programs use memory, including paging file size, or environment variables - a string consisting of environment information, such as a drive, path, or file name, associated with a symbolic name that can be used by Windows. A user may also use the SET command from the command prompt to define environment variables.

a. Verify that the default items contained in the Config.nt and Autoexec.nt files are present and in the proper order. Example:

dos=high, umb

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

b. Users can add (new), modify, or remove an environment variable (right-click My Computer, Properties, Advanced, Environment variables) which is established during Setup by some programs, and those by users. Changes are written to the registry (Global Environment Variables) and are usually effective immediately. However, after a change to user environment variables is made, any open software programs should be restarted to force them to read the new values.

3. Running some MS-DOS programs properly might require that you change the system configuration used by the MS-DOS virtual machine, [Microsoft

Popular Forums
Computer Newbies 10,686 discussions
Computer Help 54,365 discussions
Laptops 21,181 discussions
Networking & Wireless 16,313 discussions
Phones 17,137 discussions
Security 31,287 discussions
TVs & Home Theaters 22,101 discussions
Windows 7 8,164 discussions
Windows 10 2,657 discussions


Help, my PC with Windows 10 won't shut down properly

Since upgrading to Windows 10 my computer won't shut down properly. I use the menu button shutdown and the screen goes blank, but the system does not fully shut down. The only way to get it to shut down is to hold the physical power button down till it shuts down. Any suggestions?