Windows XP COMMAND

B

BJ

DOS is dead, but I still want to do some things from the
COMMAND window. In DOS, I could expand the "path" to my
local utilities adding to my AUTOEXEC.BAT something like:

set path=%path%; c:\utltities

The new COMMAND window seesm to ignore AUTOEXEC.BAT and, while
I can use the above to expand the path if I type it out, it
doesn't seem to work in a '.BAT' file.
Also, "DOSKEY" runs in the COMMAND window, but does seem to
do anything.
Any guidance would be gratefully appreciated.

BJ
 
S

Smile Extender

Do not use "command" on windows xp or 2000 or nt or 2003. Use cmd.exe
instead. It's more flexible command shell.
 
R

Ron Martell

BJ said:
DOS is dead, but I still want to do some things from the
COMMAND window. In DOS, I could expand the "path" to my
local utilities adding to my AUTOEXEC.BAT something like:

set path=%path%; c:\utltities

The new COMMAND window seesm to ignore AUTOEXEC.BAT and, while
I can use the above to expand the path if I type it out, it
doesn't seem to work in a '.BAT' file.
Also, "DOSKEY" runs in the COMMAND window, but does seem to
do anything.
Any guidance would be gratefully appreciated.

BJ

Use Start - Run - CMD rather than COMMAND.

Or use Start - All Programs - Accessories - Command Prompt.

If you want to add startup items for your DOS apps or DOS windows then
add them to the autoexec.nt and/or config.nt files in the
c:\windows\system32 folder.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."
 
A

Alex Nichol

BJ said:
DOS is dead, but I still want to do some things from the
COMMAND window. In DOS, I could expand the "path" to my
local utilities adding to my AUTOEXEC.BAT something like:

set path=%path%; c:\utltities

The new COMMAND window seesm to ignore AUTOEXEC.BAT and, while
I can use the above to expand the path if I type it out, it
doesn't seem to work in a '.BAT' file.
Also, "DOSKEY" runs in the COMMAND window, but does seem to
do anything.

There are two command interpreters provided. One is command.com, which
is genuine 16 bit code (but from DOS 5.), the other, the one normally to
use is cmd.exe - at All Programs - Accessories - Command prompt. That
has DOSKey functionality inbuilt and although there is a 32 bit
'Doskey.exe' you do not need to run it: being 32 bit that will not work
with command.com.

You can to an extent put things in the windows\system32\autoexec.nt file
- this is where to put an extra set like that if you want it only to add
to the path for the command interpreter or DOS programs. On a wider
scale you can set PATH in Control Panel - System - Advanced and click
Environmental variables
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top