G
guard
This post is about what constitutes a third party utility
as it relates to the administration of Servers and Clients
running a Windows NT-based operating system.
*******
In my experience with "third party software" restrictions,
this has always referred to running an executable (i.e., a
binary) program. The restriction has NOT applied to any
interpreted scripts, unless the script's processor was itself
a binary executable (Perl.exe, for instance). But...
ANYTHING that the SysAdmin doesn't FULLY
understand might as well be binary code!
These same "restricted systems" usually allow batch/shell
scripts to be run by the SysAdmin regardless of skill level.
Many are made "responsible" for System Administration, but
not given adequate time or training to do the job.
Unlike other coding projects, writing a "little batch file"
is often done by those with little or no experience in
good programming methods.
They come to newsgroups, forums, user groups, etc. to get
some free or low-cost help. Their need is immediate, and
cut-and-paste to solve today's specific problem is the rule.
Even if an explanation of the code is given, it is soon
forgotten as long as today's crisis has been resolved.
*******
The success of our products is based on feeding someone a good
hot meal WHILE we teach them to plant, harvest and prepare
their own food (it's hard to learn when you're starving).
We use:
COMPATIBILITY first..Solve the complete problem--ONCE.
CLARITY second.......Make the code UNDERSTANDABLE--to ALL.
SPEED third..........Optimize that Understandable code.
Our Command Libraries and MountCommands strike a balance
between the need for solutions that can be understood by
the less experienced SysAdmin, and the restrictions on using
any "third party software". The actual complexity of writing
shell scripts is still there, it's just "friendlier".
It's easier to understand and remember a one-word
"sounds like what it does" command than the several
lines of "FOR loops in FOR loops" that are required
for the "old way".
Before our Command Libraries were publicly released,
the world of NT-based shell scripts was, comparatively,
in the age when you had to have a different Laserjet
Print Driver for each DOS application.
(remember the WordPerfect "Printers Disk"?)
Unlike almost every other language, there was not a
standardized method to stop "re-inventing the wheel"
every time you needed to write a script. You either
build up your own "library" of code, or you "search
the Internet" and get 1000 answers to choose from.
Since our Command Library was released, there
is an option with MUCH LESS FUMING involved.
The library is implemented as a SINGLE FILE containing
all resources (currently 400 and growing) including a
complete help catalog that is expandable and editable
without affecting the operation or performance of
the main library.
Even if third party software is allowed, the
Command Library replaces dozens of small utilities
in your toolbox and gives you, whether you are a
programmer or not, the ability to "create" your
own new commands using our "Pattern Scripts".
*******
The Entire Body of Knowledge relating to
NT-based shell scripts is now MOVING FORWARD
as each new standardized solution is added
to the Expert NT/2K/XP/K3 Command Library
by way of COMPATIBILITY, CLARITY and SPEED!
This is what we mean when we say to
those that have made the change,
Congratulations On Your Decision To
Rise Above
The Rest!
*******
The answers area at TheSystemGuard.com. You can try
the Advanced Command Library for free, and when you
roll out the solution, it's going to cost you less
than $9 per machine (down to as low as $2/system).
There are still many new scripting problems to solve
and there always will be. Working on challenging
"new problems" is a great task for people.
Working on well-defined, "old problems"
is a great job for a Command Library.
Whether you're new to scripting, or an experienced
"set in your ways" SysAdmin, take a look at the
Cmd Source link off of the Snapshot Page and see for
yourself how easy it is to write self-documenting
cross-platform shell scripting code.
(http://TheSystemGuard.com/Scripts/Snapshot)
UP
Come on /\ with us!
*******
-tsg
/-----------------+---------------+----------------------\
| COMPATIBILITY | CLARITY | SPEED |
| Write code ONCE | Make it clear | THEN...Make it fast! |
\-----------------+---------------+----------------------/
400+ command-line resources using ONLY native NT commands!
(http://TheSystemGuard.com/default.asp#MasterCommandList)
as it relates to the administration of Servers and Clients
running a Windows NT-based operating system.
*******
In my experience with "third party software" restrictions,
this has always referred to running an executable (i.e., a
binary) program. The restriction has NOT applied to any
interpreted scripts, unless the script's processor was itself
a binary executable (Perl.exe, for instance). But...
ANYTHING that the SysAdmin doesn't FULLY
understand might as well be binary code!
These same "restricted systems" usually allow batch/shell
scripts to be run by the SysAdmin regardless of skill level.
Many are made "responsible" for System Administration, but
not given adequate time or training to do the job.
Unlike other coding projects, writing a "little batch file"
is often done by those with little or no experience in
good programming methods.
They come to newsgroups, forums, user groups, etc. to get
some free or low-cost help. Their need is immediate, and
cut-and-paste to solve today's specific problem is the rule.
Even if an explanation of the code is given, it is soon
forgotten as long as today's crisis has been resolved.
*******
The success of our products is based on feeding someone a good
hot meal WHILE we teach them to plant, harvest and prepare
their own food (it's hard to learn when you're starving).
We use:
COMPATIBILITY first..Solve the complete problem--ONCE.
CLARITY second.......Make the code UNDERSTANDABLE--to ALL.
SPEED third..........Optimize that Understandable code.
Our Command Libraries and MountCommands strike a balance
between the need for solutions that can be understood by
the less experienced SysAdmin, and the restrictions on using
any "third party software". The actual complexity of writing
shell scripts is still there, it's just "friendlier".
It's easier to understand and remember a one-word
"sounds like what it does" command than the several
lines of "FOR loops in FOR loops" that are required
for the "old way".
Before our Command Libraries were publicly released,
the world of NT-based shell scripts was, comparatively,
in the age when you had to have a different Laserjet
Print Driver for each DOS application.
(remember the WordPerfect "Printers Disk"?)
Unlike almost every other language, there was not a
standardized method to stop "re-inventing the wheel"
every time you needed to write a script. You either
build up your own "library" of code, or you "search
the Internet" and get 1000 answers to choose from.
Since our Command Library was released, there
is an option with MUCH LESS FUMING involved.
The library is implemented as a SINGLE FILE containing
all resources (currently 400 and growing) including a
complete help catalog that is expandable and editable
without affecting the operation or performance of
the main library.
Even if third party software is allowed, the
Command Library replaces dozens of small utilities
in your toolbox and gives you, whether you are a
programmer or not, the ability to "create" your
own new commands using our "Pattern Scripts".
*******
The Entire Body of Knowledge relating to
NT-based shell scripts is now MOVING FORWARD
as each new standardized solution is added
to the Expert NT/2K/XP/K3 Command Library
by way of COMPATIBILITY, CLARITY and SPEED!
This is what we mean when we say to
those that have made the change,
Congratulations On Your Decision To
Rise Above
The Rest!
*******
The answers area at TheSystemGuard.com. You can try
the Advanced Command Library for free, and when you
roll out the solution, it's going to cost you less
than $9 per machine (down to as low as $2/system).
There are still many new scripting problems to solve
and there always will be. Working on challenging
"new problems" is a great task for people.
Working on well-defined, "old problems"
is a great job for a Command Library.
Whether you're new to scripting, or an experienced
"set in your ways" SysAdmin, take a look at the
Cmd Source link off of the Snapshot Page and see for
yourself how easy it is to write self-documenting
cross-platform shell scripting code.
(http://TheSystemGuard.com/Scripts/Snapshot)
UP
Come on /\ with us!
*******
-tsg
/-----------------+---------------+----------------------\
| COMPATIBILITY | CLARITY | SPEED |
| Write code ONCE | Make it clear | THEN...Make it fast! |
\-----------------+---------------+----------------------/
400+ command-line resources using ONLY native NT commands!
(http://TheSystemGuard.com/default.asp#MasterCommandList)