replacement command prompt?

  • Thread starter Thread starter Sam Marrocco
  • Start date Start date
S

Sam Marrocco

I'm looking for a (better) replacement for the standard windows command
prompt.....although there seem to be a million "shell replacements" out
there, they all seem to be glitter for the windows *desktop*, not really
replacing the command prompt shell itself. I'm looking for a shell what
is still totally DOS compatible (no Korn, bash, etc) yet allows more
standard cut/paste (no silly "mark" three-step process) and fully
supports UNC filenames.....

Is there such an app out there?
 
I'm looking for a (better) replacement for the standard windows command
prompt.....although there seem to be a million "shell replacements" out
there, they all seem to be glitter for the windows *desktop*, not really
replacing the command prompt shell itself. I'm looking for a shell what
is still totally DOS compatible (no Korn, bash, etc) yet allows more
standard cut/paste (no silly "mark" three-step process) and fully
supports UNC filenames.....

Is there such an app out there?
Click to expand...

4dos/4nt?
 
foxidrive said:
4dos/4nt?
Click to expand...




I didn't see any support for unc filenames.....? Do you know if they are
supported by the apps? For example:

cd /WindowsBox7/c$/Mydir
 
I didn't see any support for unc filenames.....? Do you know if they are
supported by the apps? For example:

cd /WindowsBox7/c$/Mydir
Click to expand...

Provided you use the right syntax (\\WindowsBox7\C$\Mydir), 4NT does
indeed support UNC paths (unlike CMD, which does not).
 
Cmd does support UNC. What is doesn't do is allow the current directory to be a UNC directory as child processes may crash when cmd is closed (because the programs can't handle UNC).

DisableUNCCheck=0x1 at
HKEY_CURRENT_USER\Software\Microsoft\Command Processor
allows this potential crash causing behaviour. Note CD still doesn't change it, but if Cmd is spawned with a UNC CurDir it will take it (use a shortcut to set it).

C:\Program Files\Support Tools>dir \\serenity\c$
Volume in drive \\serenity\c$ has no label.
Volume Serial Number is 3845-690B

Directory of \\serenity\c$

30/08/2005 09:58 AM 24 autoexec.bat
29/10/2005 12:32 AM <DIR> Documents and Settings
18/10/2005 02:36 PM <DIR> Games
18/11/2005 11:19 AM <DIR> Program Files
16/11/2005 08:22 PM <DIR> TOWERS
28/11/2005 10:40 AM <DIR> WINDOWS
1 File(s) 24 bytes
5 Dir(s) 24,853,798,912 bytes free

[Started from a shortcut]
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

\\serenity\c$>dir
Volume in drive \\serenity\c$ has no label.
Volume Serial Number is 3845-690B

Directory of \\serenity\c$

30/08/2005 09:58 AM 24 autoexec.bat
29/10/2005 12:32 AM <DIR> Documents and Settings
18/10/2005 02:36 PM <DIR> Games
18/11/2005 11:19 AM <DIR> Program Files
16/11/2005 08:22 PM <DIR> TOWERS
28/11/2005 10:40 AM <DIR> WINDOWS
1 File(s) 24 bytes
5 Dir(s) 24,853,794,816 bytes free

Do you have Quick Edit turned on in CMD's properties?

Of course XP supports Unix shells as well. See http://66.102.7.104/search?q=cache:...+"unix+services+for+windows"&hl=en&lr=lang_en
 
[Please consider a line break every 72 characters or so, and/or
Content-Transfer-Encoding: 7bit; and don't put your signature in the
middle of the article.]
Cmd does support UNC. What is doesn't do is allow the current directory to be a UNC directory as child processes may crash when cmd is closed (because the programs can't handle UNC).

DisableUNCCheck=0x1 at
HKEY_CURRENT_USER\Software\Microsoft\Command Processor
allows this potential crash causing behaviour. Note CD still doesn't change it, but if Cmd is spawned with a UNC CurDir it will take it (use a shortcut to set it).
Click to expand...
[snip]

Hardly "out-of-the-box" behaviour.

How do you make CMD.EXE perform filename completion on UNC
shares/directories?
 
Please post at the top not the top and the middle. I won't be changing my encoding, it allows links to be clickable. Also it removes CRLF from the middle of paragraphs while your encoding destroys the data. If you type in Start Run

msimn

You'll be able to access these groups correctly.

It works for filename on the share

dir \\server\C$\w<TAB> fills in with windows.

I don't use unc (pretty much anywhere), remote reg or anything like it. I terminal server in to places. It may not be intuititive but it stops users crashing programs (probably line of business apps).

--
--------------------------------------------------------------------------------------------------
Read David defending the concept of violence.
http://margokingston.typepad.com/harry_version_2/2005/10/entering_the_ga.html#more
=================================================
Michael Bednarek said:
[Please consider a line break every 72 characters or so, and/or
Content-Transfer-Encoding: 7bit; and don't put your signature in the
middle of the article.]
Cmd does support UNC. What is doesn't do is allow the current directory to be a UNC directory as child processes may crash when cmd is closed (because the programs can't handle UNC).

DisableUNCCheck=0x1 at
HKEY_CURRENT_USER\Software\Microsoft\Command Processor
allows this potential crash causing behaviour. Note CD still doesn't change it, but if Cmd is spawned with a UNC CurDir it will take it (use a shortcut to set it).
Click to expand...
[snip]

Hardly "out-of-the-box" behaviour.

How do you make CMD.EXE perform filename completion on UNC
shares/directories?
Click to expand...
 
David said:
Cmd does support UNC. What is doesn't do is allow the current directory to be a UNC directory as child processes may crash when cmd is closed (because the programs can't handle UNC).
Click to expand...

Sorry, I should have been more specific. I want my shell to support UNC
filenames *everywhere* that MS filenames (C:\blah) are supported,
including being able to CD to them.

From what I've been able to tell so far, TakeCommand looks to meet all
these qualifications....
 
As far as cutting and pasting is concerned, you can make it a bit
simpler:

- right click on the title bar of the command window, choose
properties/options, then check QuickEdit Mode

- you can now simply highlight any text in the window and press return to copy
it into the buffer

Ed
 
Ed said:
As far as cutting and pasting is concerned, you can make it a bit
simpler:

- right click on the title bar of the command window, choose
properties/options, then check QuickEdit Mode

- you can now simply highlight any text in the window and press return to copy
it into the buffer
Click to expand...

You can also use Right click (instead of Enter) to copy highlighted text
to the buffer.

Right click also pastes from the buffer.
 
Back
Top