Hi there!
For some things I use the Command line because it's a lot faster than the gui.
I have a website, and most of the times I use the command line FTP to upload the files instead of Windows Explorer because it ends up being faster...
I also like the option on the command line to filter files. Yes, the old dir command... =)
If I want to see files containing "home" on their name, I just do dir *home*... You can't do that with Windows Explorer (though you can on the Open dialog).
I'll just wait and see what the new Longhorn command line will be like! =)

I have used both the command line and "Start>Run" in both Windows 98 and 2K. Almost always by direction of Tech Support while setting up a new ISP internet connection.

Ping, DHSC configurations, etc. should be on the control panel as a tool. You could also include Tweak in this tool and probably several other useful routines like download speed.

The object of GUI is to do away with DOS and command lines. If we are stuck with having to use command lines, how-about a cheat sheet listing the major commands with a brief description.

Cecil

This post is already gathering dust, but what the hell.
I use it occasionally. What I do on it is test connections, for instance, if I'm having trouble with email I'll bring up the command line to pin point where in the heirarchy things are going awry, is it the email program or configuration, if so I'll be able to connect at the command line, if I'm not able to connect at the command line and I know there to be no trouble with the server, then the fault lies in the user's connection, ISP or intermediate. So yeah its useful for troubleshooting and tech support.

I've used it to compile C#.

I feel the command line is still a useful tool, its real nuts and bolts stuff the basics! What I have done on the command line has been trial and error, or I'll have a loose idea of how to pass the arguments.. I would appreciate a reference on it personally! Still useful from a programming standpoint, a programmer designing an application to call on the command line would still need a reference.

I think a reference would be a good idea, but perhaps bundled with something else useful and current, like compiling .NET applications from the command line, for those of us too poor to afford Visual Basic! And include the rest of it as a reference.

: )
Rich

:::::::::::::::::::::::::::::::::
Smiling Souls
http://www.smilingsouls.net
:::::::::::::::::::::::::::::::::

I do not use the command line too often (hardly ever). I think most people learn and teach using the GUI interface. I do use the command line sometimes, and then I just go by memory. I hope this information has been helpful for you! :)

I grew up using the command line in Dos so obviously there are some commands that I feel more at ease using on the command line, it also gives you a greater feeling of control.

I think the command line is being left behind but there are still some commands that require a command prompt.

PING and Tracer can be used through windows but you get an easier non-nonsense list of the information you called. Windows loves giving you list of things to look at which can complicate the results and, at least distract you from what you really want.

Programmers and IT specialist are the ones that would use the command prompt most. People who use other operating systems, such as Linux, may be using the command prompt there so may like a eqivalent way to manipulate windows.

I think if there is a need for a book that it may lie in the Network support arena.

The windows command line should be very well retained. See its an easy access to all programs, esp those who use the keyboard well. Also many compilers work in DOS mode and I personally feel its convinient to use CMD to compile and edit my codes.

I actually use the GUI. I feel that the command line is best left hidden since the GUI makes it so much easier to get stuff done

Ben Horne
Madison Area Technical College student
-------------------------
http://community.webshots.com/user/valerian114

Go there. I have a lot of awesome photos that I rendered myself

I must disagree with majora. The GUI does NOT make things "so much easier to get stuff done"

For example - I find it much easier to hit WindowsKey+R and type mspaint or notepad or winword or excel.
Especially using WinNT (which I'm forced to use here), because the Start Menu dies so often.

Also - there are often times when the GUI just doesn't cut it (for example, opening up a program such as Microsoft Access with startup parameters)
There's no way you can specify a version, workgroup, username, password, macro to run, sharing mode, decompile mode etc in Access without using command line arguments.

Using the command line to delete and rename files also generally gets around any file locks.


I am a loud man with a very large hat. This means I am in charge

I think that the windows command shell kinda sucks, though I use a command line for a LOT of things on my win2k machine.

Check out Cygwin, if you're interested. It provides you with a Bash shell in Windows, using a layer of abstraction over the Win32 API, and also allows you to install many applications that would otherwise be restricted to linux.

You also get a lot of useful linux tools, such as tar, find, grep, gcc, make, etc...

  http://www.cygwin.com/


Take care,

Nik
http://www.bigaction.org/

I use the command line at everytime, though not nearly as much as the GUI. I'm a programmer and use it registering/unregistering and all database applications controls. it is easyway easier than selecting files via the GUI) or for the occasional batch file I may write.
comand line is better than any other option it is user friendly.isuggest this
 with shinu.r
prograamer