Problem with Command Interpreter

[Rob van Albada]

Hi,

The Command Interpreter (which I use very often) appears to have a
bug;
When I install DOSKEY with the /HISTORY parameter, it works fine for a
certain time, and after that suddenly it loses its history, i.e. does
not 'remember' the commands which I had entered.
DOSKEY /REINSTALL /HISTORY does not help.
The 'memory' has disappeared forever. All I can do is exit and open a
new instance of the command interpreter.

Can anything be done to circumvent this strange behavior?
I encountered this on two computers, both under Vista Home Premium.

Kind regards,

Rob in Amsterdam.

 

[propman]

Hi,

The Command Interpreter (which I use very often) appears to have a
bug;
When I install DOSKEY with the /HISTORY parameter, it works fine for a
certain time, and after that suddenly it loses its history, i.e. does
not 'remember' the commands which I had entered.
DOSKEY /REINSTALL /HISTORY does not help.
The 'memory' has disappeared forever. All I can do is exit and open a
new instance of the command interpreter.

Can anything be done to circumvent this strange behavior?
I encountered this on two computers, both under Vista Home Premium.

Sounds like it might be a buffer overflow problem....try experimenting
with buffer size.


/LISTSIZE=size
Sets size of command history buffer.

 

[propman]

Hi,

The Command Interpreter (which I use very often) appears to have a
bug;
When I install DOSKEY with the /HISTORY parameter, it works fine for a
certain time, and after that suddenly it loses its history, i.e. does
not 'remember' the commands which I had entered.
DOSKEY /REINSTALL /HISTORY does not help.
The 'memory' has disappeared forever. All I can do is exit and open a
new instance of the command interpreter.

Can anything be done to circumvent this strange behavior?
I encountered this on two computers, both under Vista Home Premium.

Kind regards,

Rob in Amsterdam.

Hmmmm....did a bit of further searching and ran across the following:

<quote on>

CMD.exe is a newer pgm in the \SYSTEM32 folder of XP and 2000 (possibly
ME, too, but I don't have it available to test). COMMAND.com is in all
OS's (Since 95) and does not have this DOSKEY "history buffer" feature.

<quote off>


You might want to check the "Properties" setup for a commandline
session.....should be available in Panel Manager somewhere.....see if
there is buffer size allocation.


Sheesh.......more basic thought just crossed my mind.... you stated
"install doskey".......are you sure that installing Doskey for a
commandline session is even needed? IIRC, the commandline (terminal
session) for the last few Windows automatically includes automatic
command recall (history)....not on my windows machine right now so I
can't confirm this.

 

[the wharf rat]

Can anything be done to circumvent this strange behavior?

Well, it's not DOS but it's a cli with history and such. Try
cygwin bash, from www.cygwin.com. You might have to install a cygwin
"environment", that's not a big deal.

 

[Rob van Albada]

Thanks for your comments.
Indeed, the DOSKEY command seems to be built-in.
I deleted DOSKEY from the ae.bat file (which I run on startup of the
CLI, as a replacement for good old autoexec.bat).
Now ae.bat only contains the PATH command, and everything appears to
run well. The history does not disappear.

Kind regards,

Rob.


NB
I will also look into CYGWIN when I will have the time.