Vista - Re: Problem with Command Interpreter

05-21-2008

Rob van Albada wrote:

Quote:

> 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.

05-21-2008	#1 (permalink)
propman n/a posts	Re: Problem with Command Interpreter Rob van Albada wrote: Quote: > 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.
My System Specs

Similar Threads
Thread	Forum
Re: Problem with Command Interpreter	Vista General
Re: Problem with Command Interpreter	Vista General
Real nested Powershell interpreter	PowerShell
Brainf*** Compiler and Interpreter in Powershell	PowerShell
Brain**** Compiler & Interpreter in Powershell	PowerShell