Computing.Net > Forums > Disk Operating System > Weird problems in DOS under Win2k

Weird problems in DOS under Win2k

Reply to Message Icon

Original Message
Name: PipersRob
Date: November 15, 2004 at 09:15:36 Pacific
Subject: Weird problems in DOS under Win2k
OS: Windows 2000 Server
CPU/Ram: Opteron 3400/1 Gig DDR 40
Comment:

I'm experience two of the following issues in a DOS application i am running under windows 2000 server.

I have a DOS application that calls other batch scripts through it's menu system, when running a batch file I'm having problems with some commands.

When trying to do an "IF EXIST C:\DIRECTORY\nul echo directory exists"

it does not work for me, if I do the same command on a file in the directory it works fine. If i run the same command in a cmd shell it works fine as well, I don't why it is different under the enivronment for this dos program.

Also something else wierd that started happening is that the swith /Y (copy source destination /Y) no longer works for the copy command under the same situation described above. This command works fine if I enter it in a cmd shell but when executed in the script called by the dos application it gives an "invalid switch error"

These errors seem to have just started happening, they were not happening a week ago and I don't ever recall running into them before in the same environment/application i'm runing now. What could have changed to cause this wierd behavior. Something to do with the DOS version, syntax...?

If I do a ver command I get the following information.

from cmd shell: Microsoft Windows 2000 [Version 5.00.2195]

From dos app environment: MS-DOS Version 5.00.500

The ComSpec is set to cmd.exe, if I do a ver command within the script it shows the dos app using ComSpec command.com

Any help on this would be greatly appreciated. This has me so confused.



Report Offensive Message For Removal


Response Number 1
Name: Mechanix2Go
Date: November 15, 2004 at 10:57:10 Pacific
Subject: Weird problems in DOS under Win2k
Reply: (edit)

Hi,

The first thing I thought of was that your app was loading command.com and that made the difference.

But I tried a little batch test for nul and it 'works as expected.'

Inetrestingly, like you I get ver 5.00.2195 within cmd.exe but unlike you I get the same thing within command.com

Even if there was a DOS 5 command.com lying around and even if it somehow loaded, I would expect it to show ver 5.00 NOT 5.00.500

I think you've got one for the record books here.

Please let us know what you find out; or don't find out.

FWIW here are the MD5s:

7f220b10a441a4fcc6cb67f9127d9f4d cmd.exe
3d420efce68036721814af3e6c8fedec command.com


M2


Report Offensive Follow Up For Removal

Response Number 2
Name: rogerashley
Date: November 15, 2004 at 12:00:51 Pacific
Subject: Weird problems in DOS under Win2k
Reply: (edit)

This is not a DOS question is in reference to running software under emulation in Windows 2000.

Please repost in the W2K forum.

Mechanix2Go FYI the Version of MSDOS 5 is correct, that is a special emulation version of MSDOS 5 written for the NTVDM, it is in fact an update to the NTVDM in NT4, which was updated again in XP.


EMULATION EMULATION EMULATION EMULATION


Report Offensive Follow Up For Removal

Response Number 3
Name: Mechanix2Go
Date: November 15, 2004 at 12:09:03 Pacific
Subject: Weird problems in DOS under Win2k
Reply: (edit)

Hi Roger,

Thanks for the info.

I don't know why mine shows ver 5.00.2195 for cmd.exe and command.com.

M2


Report Offensive Follow Up For Removal







Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Weird problems in DOS under Win2k

Comments:

 


  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 
Data Recovery Software




How often do you use Computing.Net?

Every Day
Once a Week
Once a Month
This Is My First Time!


View Results

Poll Finishes In 3 Days.
Discuss in The Lounge