Subj : Re: Windows 2000 and leg
To   : Alan Zisman
From : Dale Ross
Date : Sun Feb 25 2001 05:12 am

 DR>> This is odd...
>
>  Yep-- that works. And I just made a shortcut on the desktop pointing to:
>
> C:\WinNT\System32\Command.com
>
> and that works as well.

GOOD! That means that the problem is in your path!

> Typing COMMAND at the RUN line seems to be trying to use the (Win98)
> C:\Command.com rather than the WinNT version. (I suppose there's an 
environment
> statement looking there first-- where would I change that?)

Right Mouse Click "My Computer"
Choose "Properties"
Choose "Advanced"
Choose "Environment Variables"
Check for path statements in both User and System. Remove any that point to 
your Windows 98 directories.

> Now are there any reasons to prefer to use COMMAND.COM rather than CMD for a
> command line interface?

I RARELY use it. But if I had one DOS application needing to pass information 
such as error levels to another DOS application, it might be best to keep them 
in the same environment. I use very few DOS applications any more. WAY, WAY 
back in the Windows NT 3.1 beta I had some weird problems with Binkley and 
Maximus running from cmd.exe. I switched to command.com and no problems. 
However, that problem was resolved during the beta.

Maybe our DOS expert Tony can tell us if he knows of any problems executing a 
DOS application from cmd.exe. command.com is still called but I do not know 
what might happen in the middle of all that.

Dale

.... Bother! said Pooh, and inhaled.
--- FTNed v0.23h/Win32
 * Origin: Barktopia - BBS Style (1:379/1.99)

.