16 bit MS-DOS Subsystem

When I am logged on as Administrator, I can run my DOS program without a hitch.....

When I am logged on as the user, I get the following error:

c:\winnt\system32\config.nt. The system file is not sutable for running MS_DOS and Microsoft Windows Applications. Choose 'Close' to terminate the application.

The user has rights to the folder and rights to read system32 folder....when I change the user to a administrator, of course it works...

Help a old DOS gal out!

 

Every reference I can find for that error from NT4 thru XP says it indicates either a bad copy of command.com or problems with config.nt or autoexec.nt.

But that can't be the case for you since the admin user can run it fine. Hmmmm. And the files should all be in system32 unless you have custom copies to deal with the app. You might try a search to see if you have other copies around. If so, the one(s) that actually deal with the app may be located where the user doesn't have rights.

Also a good idea to make sure the user has sufficient rights to the folder where the app is located (including all contents) and if it's being run from a shortcut, check security/permissions for the shortcut as well.

Other things to check if no help there are

- run the app directly from the application file (.exe, .com, .bat, whatever) and check to top of the DOS screen. It should tell you for sure if command.com is running the thing or if cmd.exe is doing the deed. It may be that the app will run fine from cmd.exe but not from command.com since they use very different sets of system resources.

- open a command.com window and try to run the app. Then open a cmd.exe window and try to run the app. See how it behaves.

 

I verified that I have only 2 files, config.nt located on ALL of my 2000 machines. One is in the winnt\system32 directory and the other is in the winnt\repair directory.

I never thought of that.....that was a good idea to check out....

I verified the shortcut, and security/permission is fine.

Makes no diffrence if ran from cmd or command.com. (same result)

so, I tried this:

I gave permission to user for the

winnt\
winnt\system32
winnt\command

and config.nt and autoexec.nt and command.com files (read and view)

and it worked.

I removed the permissions to try out your command and the cmd idea...and did not have any troubles....

puzzling, I rebooted, verified that no "extra" permissions were given and tried again...and it worked....

I am at a loss as to how this problem was fixed.....but, hey....it works, on to the the next problem!

Thank you for your time.

 

Robin - I can't explain the fix either but like you, am happy to say "well, it works so lets move along ".

That 16bit stuff is going to get harder and harder to support so if you have options .....