Can't get DOS based programs to run in Windows!!
Can't get DOS based programs to run in Windows!!
(OP)
Hi,
I am trying to run a DOS based program on Windows XP. When I try to open a window to run DOS, I get th following error message:
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.
Not sure if i deleted something i shoudn't have or what.
Any help on how to fix is greatly appreciated. Thanks
Warren
I am trying to run a DOS based program on Windows XP. When I try to open a window to run DOS, I get th following error message:
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.
Not sure if i deleted something i shoudn't have or what.
Any help on how to fix is greatly appreciated. Thanks
Warren





RE: Can't get DOS based programs to run in Windows!!
RE: Can't get DOS based programs to run in Windows!!
Regards
Steven van Els
SAvanEls@cq-link.sr
RE: Can't get DOS based programs to run in Windows!!
RE: Can't get DOS based programs to run in Windows!!
Steven van Els
SAvanEls@cq-link.sr
RE: Can't get DOS based programs to run in Windows!!
Thanks for the help!
Warren
RE: Can't get DOS based programs to run in Windows!!
Where did the desktop icon come from? I am guessing that you did an install of something you got somewhere, and either it was built earlier for a Windows NT or 2000 installation or you copied the program's files and .PIF file for the desktop icon from another PC, or something like that.
Now my inexperience with XP will show. AUTOEXEC.NT was a Windows NT equivalent of the old DOS AUTOEXEC.BAT, which set up a PC's running environment with custom settings, PATH, etc. Since Microsoft has been trying to wean us all away from DOS things (even though NT and 2K, with their CMD.EXE replacement for COMMAND.COM really did give "a better DOS than DOS"), it would not surprise me if with XP they either did away with AUTOEXEC.NT or created a new equivalent for XP. What you might try is building a new desktop icon for the program (rename the old one to preserve whatever might be in it, for reference). In the Windows Explorer, find the program you want to run, right-click on it, and build a shortcut to it. Move the shortcut to the desktop, if that is where you want it. You didn't say just *how* the DOS program was not running properly with the borrowed AUTOEXEC.NT. Perhaps the copy is not compatible with the version of XP you have. Did the error message in your first post result from a borrowed AUTOEXEC.NT? The missing file, after a reboot, could conceivably be XP's way of cleaning up (renaming, moving?) after detecting an incompatible AUTOEXEC.NT. Perhaps the one it prefers to use is a hidden file somewhere.
Another thing to try is just running a DOS command shell, changing directories to where you have the program, and executing it directly. If it fails that way, then perhaps there is indeed something specified in the older AUTOEXEC.NT file that sets up a PATH or some other environment variable needed by the app. Most folks don't go fiddling with AUTOEXEC.NT; I have, but I created a copy called AUTOEXEC.DOS modified that copy, and changed the .PIF file (via Properties/Program/Advanced for the icon - this was for Windows 2000). Do you have the thing running correctly on another (older) PC? Let us know how you make out.
RE: Can't get DOS based programs to run in Windows!!
I believe the key elements toward solving your DOS problem are going to be found in "config.nt" rather than autoexec.nt. Also, the command
"setver" may be needed. (C:\WINDOWS\SYSTEM32\setver.exe
I'll paste the highlights of the "setver" command first. All this is excerpted from the "help and support files" in XP.
Highlight 1.Examples
To run Myprog.exe, a file that runs with MS-DOS version 3.30, create an entry in the version table (explained below) that enables Myprog.exe to
interpret the MS-DOS subsystem as version 3.30 by typing:
setver myprog.exe 3.30
To delete the Myprog.exe entry from the version table, without otherwise affecting the Myprog.exe file, type:
setver myprog.exe /delete
(further details posted in full text after hightlight 2.)
Highlight 2
Windows XP does not use this command. It is accepted only for compatibility with MS-DOS files.
This tool is not available on Windows XP 64-Bit Edition.
Using the version table Many programs designed to run with a previous version of MS-DOS run
correctly with Windows XP. In some cases, however, a program might not
run correctly unless its name is included in the version table. The
table indicates to the program that it is running with the MS-DOS
version for which it was designed, even though it is running in the
MS-DOS subsystem. By interpreting MS-DOS version 5.0 as the earlier
version, the program should run correctly, however, setver does not
solve the problem if the program is not compatible with Windows XP.
Full Text Pasted Below:
setver c: SetverSets the MS-DOS version number that the MS-DOS
subsystem reports to a program. Used without parameters, setver
displays the current version table.
Syntax
setver [Drive:Path] [FileName n.nn]
setver [Drive:Path] [FileName [/delete [/quiet]]
To display the current version table, use the following syntax:
setver [Drive:Path]
Parameters
[Drive:Path]
Specifies the location of the Setver.exe file.
FileName
Specifies the name of the program file (.exe or .com) that you want to
add to the version table. You cannot use a wildcard (* or ?).
n.nn
Specifies the MS-DOS version (for example, 3.3 or 4.01) that the MS-DOS
subsystem reports to the specified program file.
/delete
Deletes the version table entry for the specified program file. You can
also use /d.
/quiet
Hides the message that is usually displayed when you delete an entry
from the version table.
/?
Displays help at the command prompt.
Remarks
Windows XP does not use this command. It is accepted only for
compatibility with MS-DOS files.
This tool is not available on Windows XP 64-Bit Edition.
Using the version table
Many programs designed to run with a previous version of MS-DOS run
correctly with Windows XP. In some cases, however, a program might not
run correctly unless its name is included in the version table. The
table indicates to the program that it is running with the MS-DOS
version for which it was designed, even though it is running in the
MS-DOS subsystem. By interpreting MS-DOS version 5.0 as the earlier
version, the program should run correctly, however, setver does not
solve the problem if the program is not compatible with Windows XP.
Loading the version table into memory
Before you can use setver, the version table must be loaded into memory
by inserting a device command in your Config.nt file.
Restarting after updating the version table
When you update the version table by adding or deleting entries, you
must start a new command prompt session to reread the version table.
Updating existing entries
If you specify a file name that is already in the version table, the
new entry replaces the existing entry.
Understanding setver exit codes
To process exit codes returned by setver, use the errorlevel parameter
on the if command line in a batch program. For an example of a batch
program that processes exit codes using if, see Related Topics. The
following table lists each exit code and a description.
Exit code Description
0 Setver successfully completed its task.
1 The user specified an invalid command-line option.
2 The user specified an invalid file name.
3 There is insufficient system memory to carry out the command.
4 The user specified an invalid version number format.
5 Setver cannot find the specified entry in the version table.
6 Setver cannot find the Setver.exe file.
7 The user specified an invalid drive.
8 The user specified too many command-line options.
9 Setver detected missing command-line options.
10 Setver detected an error while reading the Setver.exe file.
11 The Setver.exe file is corrupt.
12 The specified Setver.exe file does not support a version table.
13 There is insufficient space in the version table for a new entry.
14 Setver detected an error while writing to the Setver.exe file.
Examples
To run Myprog.exe, a file that runs with MS-DOS version 3.30, create an
entry in the version table that enables Myprog.exe to interpret the
MS-DOS subsystem as version 3.30 by typing:
setver myprog.exe 3.30
To delete the Myprog.exe entry from the version table, without
otherwise affecting the Myprog.exe file, type:
setver myprog.exe /delete
To list the contents of the version table on drive C, type:
setver c:
Formatting legend
Format Meaning
Italic Information that the user must supply
Bold Elements that the user must type exactly as shown
Ellipsis (...) Parameter that can be repeated several times in a
command line
Between brackets ([]) Optional items
Between braces ({}); choices separated by pipe (|). Example: {even|odd}
Set of choices from which the user must choose only one
Courier font Code or program output
RE: Can't get DOS based programs to run in Windows!!
There is no real excuse in a professional environment to be running a 10 year old version!
All the hacks and workarounds are intended for short term use while you get the new version sorted - not as a permanent solution
Good Luck
johnwm
________________________________________________________
To get the best from these forums read FAQ731-376 before posting
UK steam enthusiasts: www.essexsteam.co.uk
RE: Can't get DOS based programs to run in Windows!!
RE: Can't get DOS based programs to run in Windows!!
From the Run prompt, type COMMAND and run you program from the command prompt window that pops up.
RE: Can't get DOS based programs to run in Windows!!
RE: Can't get DOS based programs to run in Windows!!
RE: Can't get DOS based programs to run in Windows!!
It's difficult to believe that I'm seeing professional engineers recommending theft of intellectual property.
Good Luck
johnwm
________________________________________________________
To get the best from these forums read FAQ731-376 before posting
UK steam enthusiasts: www.essexsteam.co.uk
RE: Can't get DOS based programs to run in Windows!!