Friday, September 20, 2002

Getting to the Command Line in All Windows OS's

Do you have to support developers/users running on various Windows platforms? Ever need to tell them how to run some command line command or batch file, such as with the precompile.bat file I mentioned in my 8/24 post (used to compile CF programs without relying on CF to do it when the first user hits a new/changes template).

You may know that it's pretty easy to get to the command line in Nt 4, Win2k, and XP. Use Start>Run (or Windows key+r) and use "cmd". That opens a new window in which you can both enter commands and view their results. But that approach doesn't work on Windows 95, 98, or ME. In those cases, you may feel you have to tell them to use Start>Programs>Command? or might it be MS-Dos Command? Who can keep track of these things, darn it. Take comfort. They can use the Start>Run approach.

On 95/98/ME, it's just that they need to use "command" rather than "cmd".

Oh, and if you're new to this stuff yourself, when whatever you've run in the command window is done, use "exit" to close the window. By the way, if you haven't used the command line to run programs and instead type the command name in on the start>run prompt, just be aware that doing that won't let you see the response from the command, and may even make some other aspects of working with the command challenging. Consider using the "cmd" or "command" approach instead.

It's easy to presume that everyone knows these things, but often they don't.

No comments: