First thing to do is verify that DOSX.EXE exists. Do a full C: drive search. It should be found in C:\Windows\System32. If it does not exist there, you can try SFC /SCANNOW. I'm not sure if SFC will replace the file or not, but it is worth a try.
If DOSX.EXE exists in C:\Windows\System32, the next thing to check is your system path. This can be checked by clicking on Start | Control Panel | Performance and Maintenance | System. In the System Properties dialog that appears, click on the Advanced tab, and then click on the Environment Variables button at the bottom to open the Environment Variables dialog. Under system variables, you should see the Path variable. Verify that C:\Windows\System32 exists in the path. If it doesn't, edit the Path variable and add %SystemRoot%\System32 (the system will replace %SystemRoot% with C:\Windows for you). Remember that each entry/path in the Path variable must be separated by a semicolon (;).
Oh, yeah ... and one other thing you might want to look into is if there is updated software/drivers for your printer that are designed specifically for XP. Software that perhaps would not require the Win16 subsystem to install. It may work out better for you in the long run.
Hope this helps.
Message Edited by BaldEaglePride on 01-15-2004 01:01 PM
Do you have your Control Panel set to classic view perhaps? If so, then simply click on the System icon and follow the rest of the steps in my previous post to get to the Path information. You can also get to the appropriate dialog by right-clicking on My Computer and selecting Properties.
Message Edited by BaldEaglePride on 01-15-2004 01:32 PM
BaldEaglePride
30 Posts
0
January 15th, 2004 16:00
Brew Guy -
First thing to do is verify that DOSX.EXE exists. Do a full C: drive search. It should be found in C:\Windows\System32. If it does not exist there, you can try SFC /SCANNOW. I'm not sure if SFC will replace the file or not, but it is worth a try.
If DOSX.EXE exists in C:\Windows\System32, the next thing to check is your system path. This can be checked by clicking on Start | Control Panel | Performance and Maintenance | System. In the System Properties dialog that appears, click on the Advanced tab, and then click on the Environment Variables button at the bottom to open the Environment Variables dialog. Under system variables, you should see the Path variable. Verify that C:\Windows\System32 exists in the path. If it doesn't, edit the Path variable and add %SystemRoot%\System32 (the system will replace %SystemRoot% with C:\Windows for you). Remember that each entry/path in the Path variable must be separated by a semicolon (;).
Oh, yeah ... and one other thing you might want to look into is if there is updated software/drivers for your printer that are designed specifically for XP. Software that perhaps would not require the Win16 subsystem to install. It may work out better for you in the long run.
Hope this helps.
Message Edited by BaldEaglePride on 01-15-2004 01:01 PM
Brew Guy
3 Posts
0
January 15th, 2004 17:00
I got as far as verifying that Autoexec.nt is present on my system. I have one two: C:\WINDOWS\repair and another under C:\WINDOWS\system32
However, going on to the next step; I am not seeing Performance and Maintenance | System under the Control Panel
Don
JRosenfeld
2 Intern
•
4.4K Posts
0
January 15th, 2004 17:00
Whether you see 'performance and maintenance' depends on your view settings; Just double click the System icon in Control panel.
The file you were advised to check exists in C:Windows\System32 is dosx.exe;
BaldEaglePride
30 Posts
0
January 15th, 2004 17:00
Strange ...
Do you have your Control Panel set to classic view perhaps? If so, then simply click on the System icon and follow the rest of the steps in my previous post to get to the Path information. You can also get to the appropriate dialog by right-clicking on My Computer and selecting Properties.
Message Edited by BaldEaglePride on 01-15-2004 01:32 PM
Brew Guy
3 Posts
0
January 15th, 2004 18:00
Thanks everyone, problem fixed.
BTW, I mistakenly said on original post:
I can find refrences to this on Microsoft support regarding Win2000 and Xp OS, but nothing for a fix on XP.
I should have typed: Windows 2000 and NT, (not XP)