|
|
|
re: Question about 'Load DosKey in a DOS box automatically'
Thursday, April 4, 2002 at 4:55 pm
Posted by Bob Cerelli
(2137 messages posted)
If you want to start a program (like DOSKEY) or set an environment variable each
time you open a command prompt:
1. Start Regedit
2. Go to HKEY_CURRENT_USER\Software\Microsoft\Command Processor
3. Create a String key called Autorun
4. Give it the value of the command you want to run
5. Multiple commands need to be separated by a double ampersand (&&)
Bob Cerelli
http://www.onecomputerguy.com
On Thursday, April 4, 2002 at 3:15 pm, RAJ SINGHAL wrote:
>I have a question about Load
>DosKey in a DOS box automatically:
>
>
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Tuesday, May 21, 2002 at 10:25 pm
Posted by Oafah
(1 messages posted)
To Whom It May Concern,
You can also add a line to your autoexec.bat file that activates doskey each time
you start windows. It is as follows:
C:\WINDOWS\COMMAND\doskey.com
It should now be active with every activation of a DOS command window.
Oafah
On Thursday, April 4, 2002 at 4:55 pm, Bob Cerelli wrote:
>If you want to start a program (like DOSKEY) or set an environment variable each
>time you open a command prompt:
>
>1. Start Regedit
>2. Go to HKEY_CURRENT_USER\Software\Microsoft\Command Processor
>3. Create a String key called Autorun
>4. Give it the value of the command you want to run
>5. Multiple commands need to be separated by a double ampersand (&&)
>
>Bob Cerelli
>http://www.onecomputerguy.com
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Wednesday, October 16, 2002 at 2:09 am
Posted by CR
(1 messages posted)
Will this work in Windows XP? I tried to run doskey in my Win XP but it doesn't work.
I can't go back to the command I just type after numerous tries.
On Tuesday, May 21, 2002 at 10:25 pm, Oafah wrote:
>To Whom It May Concern,
>
>You can also add a line to your autoexec.bat file that activates doskey each time
>you start windows. It is as follows:
>
>C:\WINDOWS\COMMAND\doskey.com
>
>It should now be active with every activation of a DOS command window.
>
>Oafah
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Thursday, November 14, 2002 at 2:22 pm
Posted by rob chamberlin
(3 messages posted)
In WinXP Professionsl the command is:
C:\WINDOWS\SYSTEM32\DOSKEY /LISTFILE=512
Note - the LISTFILE option is not required, but I use it to ensure I have enough
command buffer space.
You can find the options using the traditional --
DOSKEY /?
I don't know if the Home edition uses the same path.
HTH,
rob
On Wednesday, October 16, 2002 at 2:09 am, CR wrote:
>
>Will this work in Windows XP? I tried to run doskey in my Win XP but it doesn't
work.
>I can't go back to the command I just type after numerous tries.
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Tuesday, January 28, 2003 at 5:33 pm
Posted by Rob
(1 messages posted)
In WinXP It's automatic if you run CMD.exe rather than COMMAND.com
--Rob
On Tuesday, May 21, 2002 at 10:25 pm, Oafah wrote:
>To Whom It May Concern,
>
>You can also add a line to your autoexec.bat file that activates doskey each time
>you start windows. It is as follows:
>
>C:\WINDOWS\COMMAND\doskey.com
>
>It should now be active with every activation of a DOS command window.
>
>Oafah
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Thursday, April 3, 2003 at 2:02 am
Posted by Tom
(38 messages posted)
When I make these modifications, any commands are executed at every moment I give
a command inside a dosbox, and "in it self" without influencing the environment of
the dosbox itself. In short: it does not work.
Using cmd in stead of command does work (without modifications) but has other disadvantages
and only works with doskey and not other commands.
Altering autoexec.nt does not work: bad command or file name (???????????????????)
On Thursday, April 4, 2002 at 4:55 pm, Bob Cerelli wrote:
>If you want to start a program (like DOSKEY) or set an environment variable each
>time you open a command prompt:
>
>1. Start Regedit
>2. Go to HKEY_CURRENT_USER\Software\Microsoft\Command Processor
>3. Create a String key called Autorun
>4. Give it the value of the command you want to run
>5. Multiple commands need to be separated by a double ampersand (&&)
>
>Bob Cerelli
>http://www.onecomputerguy.com
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Tuesday, April 8, 2003 at 10:42 pm
Posted by KenAlcock
(13 messages posted)
As I understand this thread, you want control over how the Command
Prompt initially opens. (Get used to “Command Prompt” or Command
Line,” because it’s no longer a DOS prompt in Windows NT/2000/XP.)
This is intended for Windows XP. I believe it will work on NT and
2000; but, I’m not so sure about DOS based Windows versions 3.x - ME).
I extensively use Command Line in my work. Here’s what I use to make
my life easier. Everything you see here should be part of the basic
Windows XP installation.
1. Find the Command Prompt icon, usually located in:
Start Menu -> Programs -> Accessories -> Command Prompt
2. Right-click this icon and select [Properties].
3. On the [Shortcut] tab make the following changes:
[Target:]
%SystemRoot%\system32\cmd.exe /k %SystemRoot%\system32\autoexec.bat
The /K switch carries out any command specified by the following
{path string} and forces cmd.exe to remain open after the command
completes.
You don’t actually have a file: “%SystemRoot%\system32\autoexec.bat.”
We’ll make it in a moment. I strongly suggest you make this file,
rather than use the one located at C:\.
[Shortcut Key:] Ctrl+Shift+C
This saves a lot of time; now we don’t have to hunt our icon each
Time we open a Command Line.
[Start in:] {Where ever your heart desires}
ALL your Commands lines will open here; C:\ works fine for me. You
can also use environmental variables like %SystemRoot% in this blank.
If you change this directory, make sure your %PATH% is updated so you
can find any command line programs you wish to make use of.
[Run:] Normal Window
This should be the default value.
4. On the [Options] tab make the following changes:
[Command History]
[Buffer Size] 50
This affects how many commands each Command Line buffer stores.
[Number of Buffers] 4
This affects how many Command Lines, open at the same time, can
have their own command history buffer.
[Discard Duplicates] OFF
You can turn this on, but it may be somewhat confusing to locate
commands you just ran a second ago, if you first ran the same
command a half hour ago. Only the FIRST instance of any command
(as typed) is stored with this option on. So this setting slightly
changes the overall order of all commands in the history buffer.
[Edit Options]
[Quick Edit Mode] On
This allows you to mouse click directly in the Command Line, and
Paste Windows clipboard text to it.
[Insert Mode] On
This allows you to click in the middle of a typed command string
and type new characters, inserting them without overstriking any
existing ones. This is a default setting for the Command Line
when it first opens. (You can toggle Insert and Overstrike mode
with the Insert key.)
4. After making your changes, click [Apply], then click [OK].
Now ALL Command Line Prompts opened from this icon (or by pressing
Ctrl+Shift+C) will inherit these settings. However, if you open a
command line from Start Menu -> Run, or any different icon, these
settings won’t take effect.
5. Create an Autoexec.bat file to initialize your Command Line Prompt
run from your modified icon (or by pressing Ctrl+Shift+C).
A. Click on Start Menu -> Run
B. Copy and paste the following line:
Notepad %SystemRoot%\system32\Autoexec.bat
C. Press Enter.
D. Click [Yes] to create a new file.
E. Copy and paste the example Autoexec.bat shown below
:: Start example Autoexec.bat to initialize a new Command Line.
@Echo Off
CLS
:SetVars
SET Greeting=It Works!
:Start
Echo.
Echo %Greeting%
Echo.
@Echo On
:End
:: End example Autoexec.bat file.
F. Save the file and exit Notepad.
6. Press Ctrl+Shift+C to test your work.
Now all you have to do is modify this Autoexec.bat with any settings
You want to include. (Here’s another tip, create a shortcut to this
file and put it next to your Command Prompt icon in the Start Menu.)
DS
On Thursday, April 3, 2003 at 2:02 am, HANSL wrote:
>When I make these modifications, any commands are executed at every moment I give
>a command inside a dosbox, and "in it self" without influencing the environment
of
>the dosbox itself. In short: it does not work.
>Using cmd in stead of command does work (without modifications) but has other disadvantages
>and only works with doskey and not other commands.
>Altering autoexec.nt does not work: bad command or file name (???????????????????)
>
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Wednesday, July 2, 2003 at 4:22 pm
Posted by Frank Tennant
(1 messages posted)
use start, run CMD not start, run COMMAND under XP, you will be a much happier camper
On Wednesday, October 16, 2002 at 2:09 am, CR wrote:
>
>Will this work in Windows XP? I tried to run doskey in my Win XP but it doesn't
work.
>I can't go back to the command I just type after numerous tries.
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Friday, February 4, 2005 at 4:30 pm
Posted by mario
(2 messages posted)
that is what I was looking for! CMD instead of COMAND. somebody knows whuy there
is 2 names for this function?
thx
Mario the floridian
On Tuesday, January 28, 2003 at 5:33 pm, Rob wrote:
>
>In WinXP It's automatic if you run CMD.exe rather than COMMAND.com
>
>--Rob
>
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Friday, February 4, 2005 at 7:41 pm
Posted by Matthew D. Healy
(1255 messages posted)
And you should not run
command.com anyway. They only include
command.com for backwards compatibilty with
Win9X. NT (from which XP is derived) has had
the dramatically better cmd.exe for many many
years.
On Tuesday, January 28, 2003 at 5:33 pm, Rob wrote:
>
>In WinXP It's automatic if you run CMD.exe rather than COMMAND.com
>
>--Rob
>
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Friday, February 4, 2005 at 7:45 pm
Posted by Matthew D. Healy
(1255 messages posted)
Welcome to the wonderful world of software history!
Windows XP represents the convergence of two
different histories. For over a decade, Microsoft
maintained two independent operating systems,
the consumer systems Win1.x-Win3.x, Win95,
Win98, WinMe
and the corporate systems WfW, WinNT1, WinNT2,
WinNT3.x, Win2K, etc.
The NT-derived systems were more powerful, stable,
and secure but also less compatible with oddball
hardware and many applications. The consumer
systems were much more compatible and
user-friendly -- setting up networking on NT3.x
was a ROYAL PAIN -- but also the consumer versions
were much less stable.
Of course, this led to a lot of wasted programming
effort for Microsoft maintaing two platforms. It also
led to a lot of wasted testing effort among developers
who had to test their stuff on both platforms.
For some years, Microsoft had the goal of joining
these two different streams of code, and XP
represents the result. Not perfect, still has its
quirks, but overall the best OS from Redmond by
far.
Command.com was the commandline in Win9X
because it was the commandline in DOS, from which
Win9X was derived. NT had no DOS heritage, so
it had its own command interpreter cmd.exe. With
XP, you get both -- cmd.exe because it's what the
serious professionals use, and command.com for
compatibilty reasons.
But GWBASIC is finally gone from XP! It came with
Windows through 95 for sure, and I think maybe
also 98 and ME. Actually, the GWBASIC
from my old 95 CD still seems to work fine under XP!
On Friday, February 4, 2005 at 4:30 pm, mario wrote:
>
>that is what I was looking for! CMD instead of COMAND. somebody knows whuy there
>is 2 names for this function?
>
>thx
>Mario the floridian
>
>
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Sunday, February 6, 2005 at 9:31 am
Posted by mario
(2 messages posted)
thx Matt for the detailed answer!
ciao
Mario the floridian...
On Friday, February 4, 2005 at 7:45 pm, Matthew D. Healy wrote:
>Welcome to the wonderful world of software history!
>
>Windows XP represents the convergence of two
>different histories. For over a decade, Microsoft
>maintained two independent operating systems,
>the consumer systems Win1.x-Win3.x, Win95,
>Win98, WinMe
>and the corporate systems WfW, WinNT1, WinNT2,
>WinNT3.x, Win2K, etc.
>
>The NT-derived systems were more powerful, stable,
>and secure but also less compatible with oddball
>hardware and many applications. The consumer
>systems were much more compatible and
>user-friendly -- setting up networking on NT3.x
>was a ROYAL PAIN -- but also the consumer versions
>were much less stable.
>
>Of course, this led to a lot of wasted programming
>effort for Microsoft maintaing two platforms. It also
>led to a lot of wasted testing effort among developers
>who had to test their stuff on both platforms.
>
>For some years, Microsoft had the goal of joining
>these two different streams of code, and XP
>represents the result. Not perfect, still has its
>quirks, but overall the best OS from Redmond by
>far.
>
>Command.com was the commandline in Win9X
>because it was the commandline in DOS, from which
>Win9X was derived. NT had no DOS heritage, so
>it had its own command interpreter cmd.exe. With
>XP, you get both -- cmd.exe because it's what the
>serious professionals use, and command.com for
>compatibilty reasons.
>
>But GWBASIC is finally gone from XP! It came with
>Windows through 95 for sure, and I think maybe
>also 98 and ME. Actually, the GWBASIC
>from my old 95 CD still seems to work fine under XP!
>
>
>
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Monday, August 22, 2005 at 7:03 pm
Posted by raj singhal
(2 messages posted)
Please explain.
On Thursday, April 4, 2002 at 3:15 pm, RAJ SINGHAL wrote:
>
>I have a question about Load
>DosKey in a DOS box automatically:
>
>
[Reply or follow-up to this message]
|
cmd.exe in Win XP
Friday, September 2, 2005 at 6:59 am
Posted by Joh Neo
(1 messages posted)
My cmd.exe does not recognize any commands except for exit. commands such as echo,
shutdown, ping, copy etc. give an error- not internal or external file name/unrecognized.
Question2: on my system @sch cmd.exe works fine but when i schedule tasks using:
AT \\Computer Name [id] [time] [Interactive] shutdown -s -c "comment" the cmd shedules
the task and give a task id but does not execute the task
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Tuesday, December 6, 2005 at 9:18 pm
Posted by Rich Camlin
(19 messages posted)
Ken,
Your solution was outstanding and extremely well presented.
Thank you for solving a problem that has been nagging me for over a year
rc
On Tuesday, April 8, 2003 at 10:42 pm, KenAlcock wrote:
>
>As I understand this thread, you want control over how the Command
>Prompt initially opens. (Get used to “Command Prompt” or Command
>Line,” because it’s no longer a DOS prompt in Windows NT/2000/XP.)
>
>This is intended for Windows XP. I believe it will work on NT and
>2000; but, I’m not so sure about DOS based Windows versions 3.x - ME).
>I extensively use Command Line in my work. Here’s what I use to make
>my life easier. Everything you see here should be part of the basic
>Windows XP installation.
>
>1. Find the Command Prompt icon, usually located in:
> Start Menu -> Programs -> Accessories -> Command Prompt
>
>2. Right-click this icon and select [Properties].
>
>3. On the [Shortcut] tab make the following changes:
>
>[Target:]
> %SystemRoot%\system32\cmd.exe /k %SystemRoot%\system32\autoexec.bat
>
> The /K switch carries out any command specified by the following
> {path string} and forces cmd.exe to remain open after the command
> completes.
>
> You don’t actually have a file: “%SystemRoot%\system32\autoexec.bat.”
> We’ll make it in a moment. I strongly suggest you make this file,
> rather than use the one located at C:\.
>
>[Shortcut Key:] Ctrl+Shift+C
> This saves a lot of time; now we don’t have to hunt our icon each
> Time we open a Command Line.
>
>[Start in:] {Where ever your heart desires}
> ALL your Commands lines will open here; C:\ works fine for me. You
> can also use environmental variables like %SystemRoot% in this blank.
> If you change this directory, make sure your %PATH% is updated so you
> can find any command line programs you wish to make use of.
>
>[Run:] Normal Window
> This should be the default value.
>
>4. On the [Options] tab make the following changes:
>
>[Command History]
>
> [Buffer Size] 50
> This affects how many commands each Command Line buffer stores.
>
> [Number of Buffers] 4
> This affects how many Command Lines, open at the same time, can
> have their own command history buffer.
>
> [Discard Duplicates] OFF
> You can turn this on, but it may be somewhat confusing to locate
> commands you just ran a second ago, if you first ran the same
> command a half hour ago. Only the FIRST instance of any command
> (as typed) is stored with this option on. So this setting slightly
> changes the overall order of all commands in the history buffer.
>
>[Edit Options]
>
> [Quick Edit Mode] On
> This allows you to mouse click directly in the Command Line, and
> Paste Windows clipboard text to it.
>
> [Insert Mode] On
> This allows you to click in the middle of a typed command string
> and type new characters, inserting them without overstriking any
> existing ones. This is a default setting for the Command Line
> when it first opens. (You can toggle Insert and Overstrike mode
> with the Insert key.)
>
>4. After making your changes, click [Apply], then click [OK].
>
> Now ALL Command Line Prompts opened from this icon (or by pressing
> Ctrl+Shift+C) will inherit these settings. However, if you open a
> command line from Start Menu -> Run, or any different icon, these
> settings won’t take effect.
>
>5. Create an Autoexec.bat file to initialize your Command Line Prompt
> run from your modified icon (or by pressing Ctrl+Shift+C).
>
>A. Click on Start Menu -> Run
>B. Copy and paste the following line:
> Notepad %SystemRoot%\system32\Autoexec.bat
>C. Press Enter.
>D. Click [Yes] to create a new file.
>E. Copy and paste the example Autoexec.bat shown below
>
>:: Start example Autoexec.bat to initialize a new Command Line.
> @Echo Off
> CLS
>:SetVars
> SET Greeting=It Works!
>:Start
> Echo.
> Echo %Greeting%
> Echo.
> @Echo On
>:End
>:: End example Autoexec.bat file.
>
>F. Save the file and exit Notepad.
>
>6. Press Ctrl+Shift+C to test your work.
>
>Now all you have to do is modify this Autoexec.bat with any settings
>You want to include. (Here’s another tip, create a shortcut to this
>file and put it next to your Command Prompt icon in the Start Menu.)
>
>DS
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Sunday, January 29, 2006 at 8:58 pm
Posted by Rich Camlin
(19 messages posted)
Ken,
Your solution was outstanding and extremely well presented.
Thank you for solving a problem that has been nagging me for over a year
rc
On Tuesday, April 8, 2003 at 10:42 pm, KenAlcock wrote:
>
>As I understand this thread, you want control over how the Command
>Prompt initially opens. (Get used to “Command Prompt” or Command
>Line,” because it’s no longer a DOS prompt in Windows NT/2000/XP.)
>
>This is intended for Windows XP. I believe it will work on NT and
>2000; but, I’m not so sure about DOS based Windows versions 3.x - ME).
>I extensively use Command Line in my work. Here’s what I use to make
>my life easier. Everything you see here should be part of the basic
>Windows XP installation.
>
>1. Find the Command Prompt icon, usually located in:
> Start Menu -> Programs -> Accessories -> Command Prompt
>
>2. Right-click this icon and select [Properties].
>
>3. On the [Shortcut] tab make the following changes:
>
>[Target:]
> %SystemRoot%\system32\cmd.exe /k %SystemRoot%\system32\autoexec.bat
>
> The /K switch carries out any command specified by the following
> {path string} and forces cmd.exe to remain open after the command
> completes.
>
> You don’t actually have a file: “%SystemRoot%\system32\autoexec.bat.”
> We’ll make it in a moment. I strongly suggest you make this file,
> rather than use the one located at C:\.
>
>[Shortcut Key:] Ctrl+Shift+C
> This saves a lot of time; now we don’t have to hunt our icon each
> Time we open a Command Line.
>
>[Start in:] {Where ever your heart desires}
> ALL your Commands lines will open here; C:\ works fine for me. You
> can also use environmental variables like %SystemRoot% in this blank.
> If you change this directory, make sure your %PATH% is updated so you
> can find any command line programs you wish to make use of.
>
>[Run:] Normal Window
> This should be the default value.
>
>4. On the [Options] tab make the following changes:
>
>[Command History]
>
> [Buffer Size] 50
> This affects how many commands each Command Line buffer stores.
>
> [Number of Buffers] 4
> This affects how many Command Lines, open at the same time, can
> have their own command history buffer.
>
> [Discard Duplicates] OFF
> You can turn this on, but it may be somewhat confusing to locate
> commands you just ran a second ago, if you first ran the same
> command a half hour ago. Only the FIRST instance of any command
> (as typed) is stored with this option on. So this setting slightly
> changes the overall order of all commands in the history buffer.
>
>[Edit Options]
>
> [Quick Edit Mode] On
> This allows you to mouse click directly in the Command Line, and
> Paste Windows clipboard text to it.
>
> [Insert Mode] On
> This allows you to click in the middle of a typed command string
> and type new characters, inserting them without overstriking any
> existing ones. This is a default setting for the Command Line
> when it first opens. (You can toggle Insert and Overstrike mode
> with the Insert key.)
>
>4. After making your changes, click [Apply], then click [OK].
>
> Now ALL Command Line Prompts opened from this icon (or by pressing
> Ctrl+Shift+C) will inherit these settings. However, if you open a
> command line from Start Menu -> Run, or any different icon, these
> settings won’t take effect.
>
>5. Create an Autoexec.bat file to initialize your Command Line Prompt
> run from your modified icon (or by pressing Ctrl+Shift+C).
>
>A. Click on Start Menu -> Run
>B. Copy and paste the following line:
> Notepad %SystemRoot%\system32\Autoexec.bat
>C. Press Enter.
>D. Click [Yes] to create a new file.
>E. Copy and paste the example Autoexec.bat shown below
>
>:: Start example Autoexec.bat to initialize a new Command Line.
> @Echo Off
> CLS
>:SetVars
> SET Greeting=It Works!
>:Start
> Echo.
> Echo %Greeting%
> Echo.
> @Echo On
>:End
>:: End example Autoexec.bat file.
>
>F. Save the file and exit Notepad.
>
>6. Press Ctrl+Shift+C to test your work.
>
>Now all you have to do is modify this Autoexec.bat with any settings
>You want to include. (Here’s another tip, create a shortcut to this
>file and put it next to your Command Prompt icon in the Start Menu.)
>
>DS
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Saturday, April 8, 2006 at 12:50 pm
Posted by Rich Camlin
(19 messages posted)
Ken,
Your solution was outstanding and extremely well presented.
Thank you for solving a problem that has been nagging me for over a year
rc
On Tuesday, April 8, 2003 at 10:42 pm, KenAlcock wrote:
>
>As I understand this thread, you want control over how the Command
>Prompt initially opens. (Get used to “Command Prompt” or Command
>Line,” because it’s no longer a DOS prompt in Windows NT/2000/XP.)
>
>This is intended for Windows XP. I believe it will work on NT and
>2000; but, I’m not so sure about DOS based Windows versions 3.x - ME).
>I extensively use Command Line in my work. Here’s what I use to make
>my life easier. Everything you see here should be part of the basic
>Windows XP installation.
>
>1. Find the Command Prompt icon, usually located in:
> Start Menu -> Programs -> Accessories -> Command Prompt
>
>2. Right-click this icon and select [Properties].
>
>3. On the [Shortcut] tab make the following changes:
>
>[Target:]
> %SystemRoot%\system32\cmd.exe /k %SystemRoot%\system32\autoexec.bat
>
> The /K switch carries out any command specified by the following
> {path string} and forces cmd.exe to remain open after the command
> completes.
>
> You don’t actually have a file: “%SystemRoot%\system32\autoexec.bat.”
> We’ll make it in a moment. I strongly suggest you make this file,
> rather than use the one located at C:\.
>
>[Shortcut Key:] Ctrl+Shift+C
> This saves a lot of time; now we don’t have to hunt our icon each
> Time we open a Command Line.
>
>[Start in:] {Where ever your heart desires}
> ALL your Commands lines will open here; C:\ works fine for me. You
> can also use environmental variables like %SystemRoot% in this blank.
> If you change this directory, make sure your %PATH% is updated so you
> can find any command line programs you wish to make use of.
>
>[Run:] Normal Window
> This should be the default value.
>
>4. On the [Options] tab make the following changes:
>
>[Command History]
>
> [Buffer Size] 50
> This affects how many commands each Command Line buffer stores.
>
> [Number of Buffers] 4
> This affects how many Command Lines, open at the same time, can
> have their own command history buffer.
>
> [Discard Duplicates] OFF
> You can turn this on, but it may be somewhat confusing to locate
> commands you just ran a second ago, if you first ran the same
> command a half hour ago. Only the FIRST instance of any command
> (as typed) is stored with this option on. So this setting slightly
> changes the overall order of all commands in the history buffer.
>
>[Edit Options]
>
> [Quick Edit Mode] On
> This allows you to mouse click directly in the Command Line, and
> Paste Windows clipboard text to it.
>
> [Insert Mode] On
> This allows you to click in the middle of a typed command string
> and type new characters, inserting them without overstriking any
> existing ones. This is a default setting for the Command Line
> when it first opens. (You can toggle Insert and Overstrike mode
> with the Insert key.)
>
>4. After making your changes, click [Apply], then click [OK].
>
> Now ALL Command Line Prompts opened from this icon (or by pressing
> Ctrl+Shift+C) will inherit these settings. However, if you open a
> command line from Start Menu -> Run, or any different icon, these
> settings won’t take effect.
>
>5. Create an Autoexec.bat file to initialize your Command Line Prompt
> run from your modified icon (or by pressing Ctrl+Shift+C).
>
>A. Click on Start Menu -> Run
>B. Copy and paste the following line:
> Notepad %SystemRoot%\system32\Autoexec.bat
>C. Press Enter.
>D. Click [Yes] to create a new file.
>E. Copy and paste the example Autoexec.bat shown below
>
>:: Start example Autoexec.bat to initialize a new Command Line.
> @Echo Off
> CLS
>:SetVars
> SET Greeting=It Works!
>:Start
> Echo.
> Echo %Greeting%
> Echo.
> @Echo On
>:End
>:: End example Autoexec.bat file.
>
>F. Save the file and exit Notepad.
>
>6. Press Ctrl+Shift+C to test your work.
>
>Now all you have to do is modify this Autoexec.bat with any settings
>You want to include. (Here’s another tip, create a shortcut to this
>file and put it next to your Command Prompt icon in the Start Menu.)
>
>DS
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Thursday, April 13, 2006 at 9:58 pm
Posted by Rich Camlin
(19 messages posted)
Ken,
Your solution was outstanding and extremely well presented.
Thank you for solving a problem that has been nagging me for over a year
rc
On Tuesday, April 8, 2003 at 10:42 pm, KenAlcock wrote:
>
>As I understand this thread, you want control over how the Command
>Prompt initially opens. (Get used to “Command Prompt” or Command
>Line,” because it’s no longer a DOS prompt in Windows NT/2000/XP.)
>
>This is intended for Windows XP. I believe it will work on NT and
>2000; but, I’m not so sure about DOS based Windows versions 3.x - ME).
>I extensively use Command Line in my work. Here’s what I use to make
>my life easier. Everything you see here should be part of the basic
>Windows XP installation.
>
>1. Find the Command Prompt icon, usually located in:
> Start Menu -> Programs -> Accessories -> Command Prompt
>
>2. Right-click this icon and select [Properties].
>
>3. On the [Shortcut] tab make the following changes:
>
>[Target:]
> %SystemRoot%\system32\cmd.exe /k %SystemRoot%\system32\autoexec.bat
>
> The /K switch carries out any command specified by the following
> {path string} and forces cmd.exe to remain open after the command
> completes.
>
> You don’t actually have a file: “%SystemRoot%\system32\autoexec.bat.”
> We’ll make it in a moment. I strongly suggest you make this file,
> rather than use the one located at C:\.
>
>[Shortcut Key:] Ctrl+Shift+C
> This saves a lot of time; now we don’t have to hunt our icon each
> Time we open a Command Line.
>
>[Start in:] {Where ever your heart desires}
> ALL your Commands lines will open here; C:\ works fine for me. You
> can also use environmental variables like %SystemRoot% in this blank.
> If you change this directory, make sure your %PATH% is updated so you
> can find any command line programs you wish to make use of.
>
>[Run:] Normal Window
> This should be the default value.
>
>4. On the [Options] tab make the following changes:
>
>[Command History]
>
> [Buffer Size] 50
> This affects how many commands each Command Line buffer stores.
>
> [Number of Buffers] 4
> This affects how many Command Lines, open at the same time, can
> have their own command history buffer.
>
> [Discard Duplicates] OFF
> You can turn this on, but it may be somewhat confusing to locate
> commands you just ran a second ago, if you first ran the same
> command a half hour ago. Only the FIRST instance of any command
> (as typed) is stored with this option on. So this setting slightly
> changes the overall order of all commands in the history buffer.
>
>[Edit Options]
>
> [Quick Edit Mode] On
> This allows you to mouse click directly in the Command Line, and
> Paste Windows clipboard text to it.
>
> [Insert Mode] On
> This allows you to click in the middle of a typed command string
> and type new characters, inserting them without overstriking any
> existing ones. This is a default setting for the Command Line
> when it first opens. (You can toggle Insert and Overstrike mode
> with the Insert key.)
>
>4. After making your changes, click [Apply], then click [OK].
>
> Now ALL Command Line Prompts opened from this icon (or by pressing
> Ctrl+Shift+C) will inherit these settings. However, if you open a
> command line from Start Menu -> Run, or any different icon, these
> settings won’t take effect.
>
>5. Create an Autoexec.bat file to initialize your Command Line Prompt
> run from your modified icon (or by pressing Ctrl+Shift+C).
>
>A. Click on Start Menu -> Run
>B. Copy and paste the following line:
> Notepad %SystemRoot%\system32\Autoexec.bat
>C. Press Enter.
>D. Click [Yes] to create a new file.
>E. Copy and paste the example Autoexec.bat shown below
>
>:: Start example Autoexec.bat to initialize a new Command Line.
> @Echo Off
> CLS
>:SetVars
> SET Greeting=It Works!
>:Start
> Echo.
> Echo %Greeting%
> Echo.
> @Echo On
>:End
>:: End example Autoexec.bat file.
>
>F. Save the file and exit Notepad.
>
>6. Press Ctrl+Shift+C to test your work.
>
>Now all you have to do is modify this Autoexec.bat with any settings
>You want to include. (Here’s another tip, create a shortcut to this
>file and put it next to your Command Prompt icon in the Start Menu.)
>
>DS
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Monday, August 25, 2008 at 9:42 am
Posted by rich namen
(1 messages posted)
Running "CMD" instead of "Command" worked perfectly.
Doskey is operational.
I wish I had seen your info earlier.
Thanks so much!!
Rich.
--
On Wednesday, July 2, 2003 at 4:22 pm, Frank Tennant wrote:
>use start, run CMD not start, run COMMAND under XP, you will be a much happier
camper
>
>
[Reply or follow-up to this message]
|
re: Question about 'Load DosKey in a DOS box automatically'
Thursday, February 5, 2009 at 7:06 am
Posted by sasi
(1 messages posted)
This is the most comprehensive information of cmd.exe someone can provide. Thanks
much ken, you saved my day
On Tuesday, April 8, 2003 at 10:42 pm, KenAlcock wrote:
>
>As I understand this thread, you want control over how the Command
>Prompt initially opens. (Get used to “Command Prompt” or Command
>Line,” because it’s no longer a DOS prompt in Windows NT/2000/XP.)
>
>This is intended for Windows XP. I believe it will work on NT and
>2000; but, I’m not so sure about DOS based Windows versions 3.x - ME).
>I extensively use Command Line in my work. Here’s what I use to make
>my life easier. Everything you see here should be part of the basic
>Windows XP installation.
>
>1. Find the Command Prompt icon, usually located in:
> Start Menu -> Programs -> Accessories -> Command Prompt
>
>2. Right-click this icon and select [Properties].
>
>3. On the [Shortcut] tab make the following changes:
>
>[Target:]
> %SystemRoot%\system32\cmd.exe /k %SystemRoot%\system32\autoexec.bat
>
> The /K switch carries out any command specified by the following
> {path string} and forces cmd.exe to remain open after the command
> completes.
>
> You don’t actually have a file: “%SystemRoot%\system32\autoexec.bat.”
> We’ll make it in a moment. I strongly suggest you make this file,
> rather than use the one located at C:\.
>
>[Shortcut Key:] Ctrl+Shift+C
> This saves a lot of time; now we don’t have to hunt our icon each
> Time we open a Command Line.
>
>[Start in:] {Where ever your heart desires}
> ALL your Commands lines will open here; C:\ works fine for me. You
> can also use environmental variables like %SystemRoot% in this blank.
> If you change this directory, make sure your %PATH% is updated so you
> can find any command line programs you wish to make use of.
>
>[Run:] Normal Window
> This should be the default value.
>
>4. On the [Options] tab make the following changes:
>
>[Command History]
>
> [Buffer Size] 50
> This affects how many commands each Command Line buffer stores.
>
> [Number of Buffers] 4
> This affects how many Command Lines, open at the same time, can
> have their own command history buffer.
>
> [Discard Duplicates] OFF
> You can turn this on, but it may be somewhat confusing to locate
> commands you just ran a second ago, if you first ran the same
> command a half hour ago. Only the FIRST instance of any command
> (as typed) is stored with this option on. So this setting slightly
> changes the overall order of all commands in the history buffer.
>
>[Edit Options]
>
> [Quick Edit Mode] On
> This allows you to mouse click directly in the Command Line, and
> Paste Windows clipboard text to it.
>
> [Insert Mode] On
> This allows you to click in the middle of a typed command string
> and type new characters, inserting them without overstriking any
> existing ones. This is a default setting for the Command Line
> when it first opens. (You can toggle Insert and Overstrike mode
> with the Insert key.)
>
>4. After making your changes, click [Apply], then click [OK].
>
> Now ALL Command Line Prompts opened from this icon (or by pressing
> Ctrl+Shift+C) will inherit these settings. However, if you open a
> command line from Start Menu -> Run, or any different icon, these
> settings won’t take effect.
>
>5. Create an Autoexec.bat file to initialize your Command Line Prompt
> run from your modified icon (or by pressing Ctrl+Shift+C).
>
>A. Click on Start Menu -> Run
>B. Copy and paste the following line:
> Notepad %SystemRoot%\system32\Autoexec.bat
>C. Press Enter.
>D. Click [Yes] to create a new file.
>E. Copy and paste the example Autoexec.bat shown below
>
>:: Start example Autoexec.bat to initialize a new Command Line.
> @Echo Off
> CLS
>:SetVars
> SET Greeting=It Works!
>:Start
> Echo.
> Echo %Greeting%
> Echo.
> @Echo On
>:End
>:: End example Autoexec.bat file.
>
>F. Save the file and exit Notepad.
>
>6. Press Ctrl+Shift+C to test your work.
>
>Now all you have to do is modify this Autoexec.bat with any settings
>You want to include. (Here’s another tip, create a shortcut to this
>file and put it next to your Command Prompt icon in the Start Menu.)
>
>DS
>
[Reply or follow-up to this message]
| |
Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread
| |
Return to the Windows XP Discussion Forum
|
|
|
|
