|
Site News | |
Our Black Friday section is now online! Click here to check it
out.
|
|
| Active Discussions
|
|
[an error occurred while processing this directive]
|
|
| |
Tutorial on Basic Windows 2000 DOS
Summary
That is all there is. Here are the things not to forget.
1. Use &:: whenever possible.
2. Never use spaces in filenames/directories and try not to use them in variables when possible.
3. Variables that will remain CONSTANT throughout the life of a script should be in UPPERCASE.
4. command_name /? brings up help on almost all DOS commands in win2k.
5. A lot of these commands I have presented are 2k ONLY. Dont try to run
them on anything older.
That's all I have to say about win2k scripting. If you read and did the
examples, you will, if not now,
come to a day where you can use this and use it ALOT. If you find that win2k
scripting is fun and you are
using it very often, jump ship over to a *nix platform like Linux or BSD. Scripting on these systems is
A LOT more versatile. You can do way way more on these platforms. One
particular shell on the *nix platforms
to use is BASH (Bourne Again Shell). It's written in C and pretty much all the scripting you can do in it
is C code, minus some of the OOP (Object Oriented Programming) features.
If you tried scripting on a *nix platform, you would understand why I
don't
even bother on windows.
There are actual scripting languages as well. Two that come to mind that
are very good are Perl and Python. Both
of these languages hold possibilites WAY beyond win2k. There is a Perl for windows too. Dunno about Python
though.
For more help and/or a real scripting enviroment refer to Google
Have a nice day!
Space Between,
09/09/03mdy
[email protected]
Questions? Ask in the
forum or
email me.
For the Privacy Policy, click
here. | |
| |
|
