Win2000 DOSKEY Doesn't Work

[GO]

Try running both CMD and COMMAND. Same problem?

Rick

And to add to that...

"cmd" is the desired command interpreter to use, and there is no need to
load the "doskey" command as there is a command history built into by
default. I'm not sure of any resason to use "command" and I believe it is
only available to provide some backward compatibility with some older DOS
programs.

 

[Fred]

Hello -

From what (little) MS KB info I could find on DOSKEY, all
info indicates it should work on a Win2K unit.

When I type 'DOSKEY' at the cmd prompt, I don't get
any 'DOSKEY loaded' type of response. Cursor skips a line
and I get a normal prompt.

But no commands are apparently stored or recallable
(up/down arrow keys).

Any suggestions on why this isn't working?

Much Grass (Southern Spanish) for any help!

Fred

 

[Rick]

Hello -

From what (little) MS KB info I could find on DOSKEY, all
info indicates it should work on a Win2K unit.

When I type 'DOSKEY' at the cmd prompt, I don't get
any 'DOSKEY loaded' type of response. Cursor skips a line
and I get a normal prompt.

But no commands are apparently stored or recallable
(up/down arrow keys).

Any suggestions on why this isn't working?

Much Grass (Southern Spanish) for any help!

Try running both CMD and COMMAND. Same problem?

Rick

 

[Fred]

-----Original Message-----


Try running both CMD and COMMAND. Same problem?

Rick


.

Rick -

Thx much for the reply. Almost missed what you said. Is
it proper protocol to add the response at the bottom of
the thread (I'm a newbie at this)? The '>' symbol
structure would seem to imply such.

Well, Doggies. The 'cmd' option works! I always thought
to two were 'synonyms' and did the same thing, but
obiously it tain't so!

Now, then, just exactly what is the freakin' difference?

Fred

 

[GO]

Rick -

Thx much for the reply. Almost missed what you said. Is
it proper protocol to add the response at the bottom of
the thread (I'm a newbie at this)? The '>' symbol
structure would seem to imply such.

Well, Doggies. The 'cmd' option works! I always thought
to two were 'synonyms' and did the same thing, but
obiously it tain't so!

Now, then, just exactly what is the freakin' difference?

Fred

Hi Fred,

Glad you got the doskey issue straightened out!

As for proper protocol when responding to messages, there are basically two
methods and almost always big arguments from either side on which is the
best. There is either "top posting" or "bottom posting". Bottom posting is
what you see here, which is where the "replier" posts his reply at the
bottom of the message. Most newsgroups seem to prefer this method. Top
posting is where you reply at the top of the original post. And for me this
makes the most sense as you don't have to scroll all the way to the bottom
of the message to see the new content. Typically when I reply to an ongoing
thread I will follow suit with whatever method is being used. There is also
"inline posting" which is where you make comments throughout the original
post but can tend to get very convoluted and hard to read quickly if not
down properly.

HTH,

Greg

 

[Fred]

-----Original Message-----



And to add to that...

"cmd" is the desired command interpreter to use, and there is no need to
load the "doskey" command as there is a command history built into by
default. I'm not sure of any resason to use "command" and I believe it is
only available to provide some backward compatibility with some older DOS
programs.


.

Ok, GO, more good info! And you're right - don't need the
DOSKEY entry. Buzz. I've used the 'cmd' cmd (pun
intended) before but didn't realize the difference in
function.

If I saw either entry there I'd just hit Enter & go.
Won't forget this one! Thanks to both of you.

Fred

 

[Rick]

Now, then, just exactly what is the freakin' difference?

COMMAND is the old DOS shell.

CMD is Win2K's command prompt. 32-bit with lots of
added features (such as a command buffer ;-)

Rick

 

[William W. Plummer]

COMMAND is the old DOS shell.

CMD is Win2K's command prompt. 32-bit with lots of
added features (such as a command buffer ;-)

Rick

CMD has a command history and you can go back through it with up-arrow,
etc. But, it does not allow macros to be defined as with DOSKEY (or
maybe I forgot the syntax). ie foo=dir $1 /q doesn't work.