Have you seen the new 'monad' shell that was at one point supposed to ship with Vista?
It actually looks like M$ may have finally tapped their talent, though the commands are somewhat verbose (you can use aliases though)...
Actually, I copied this post from the python forum. It was aimed at those who call scripts from the command line often. I still believe that sys admin should be done using GUI tools. So, as people create tools and publish them, I add them to my toolbox (like WEVE for setting environment variables using tree widgets).
Yeah this is cool, nice link barton, I have seen the software before, the one I particularly liked was integrated into every explorer window and would show you the entire tree of where you were looking. I used it when I was working at the Boys and Girls Club of America but people would always think that I am hacking and so I got rid of it.
I actually think MS have actually provided a very powerful command line system.
GUI is fine for standard usage, but command line is best for scripting and scheduling.
I often want to save myself the bother of repeating tasks laboriously, so I use CMD.Exe to create automation.
I actually think MS have actually provided a very powerful command line system.
GUI is fine for standard usage, but command line is best for scripting and scheduling.
I often want to save myself the bother of repeating tasks laboriously, so I use CMD.Exe to create automation.
I've got two partitions on my system. I've tried to
>> cd d:\
but nothing happened. With a nicer interface, I've been able to set the working directory without typing in the name_which_coul d_be_very_long_ and_cumbersone_ to_type. It just seems so archaic to expect a mere mortal to type in directory names_which_cou ld_be_very_long _and_cumbersone _to_type.
But that's not its strength (Although I never do anyway. If long and cumbersome (created by someone else!) then I copy/paste from Win Explorer).
I use it for running command scripts mainly. Preparing scripts and automating things is where it is strong. It's never been particularly intuitive, I'll grant you, but - especially since the advent of the Cmd.Exe version - it's quite flexible and powerful.
Actually, forget about especially since ... ONLY since.
But that's not its strength (Although I never do anyway. If long and cumbersome (created by someone else!) then I copy/paste from Win Explorer).
I use it for running command scripts mainly. Preparing scripts and automating things is where it is strong. It's never been particularly intuitive, I'll grant you, but - especially since the advent of the Cmd.Exe version - it's quite flexible and powerful.
Actually, forget about especially since ... ONLY since.
What about
> cd d:\
Trying to access another partition on the drive. It looks just like another drive to the rest of the world; why not cmd?
I'm sorry. I was a little inaccurate with my earlier comments.
cd d:\ will actually change the current directory FOR THE D: DRIVE, but without changing the current drive to D:.
To do the latter as well you need to use
cd /d d:\
This is because each drive letter remembers its own 'current directory' and you need the facility for changing this without necessarily changing to that drive.
Why the default is NOT to change the drive when setting the current directory I'm not sure. Probably historical.
Comment