guard
April 18th 03, 12:11 AM
Mr. Helsby:
Many of our customers use our scripting enhancement products instead of
third party utilities because they require ONLY the base operating system
and there is NO BINARY CODE involved (it's a script, so you automatically
get the source code). Others use them because they provide an
UNDERSTANDABLE and CONSISTENT syntax as compared to the arcane "make the %
sign stand on it's head" syntax of the builtin scripting commands.
End-users get hundreds of commands that MS "forgot" to include without
adding any new software. System Integrators, Consultants and Corporate IT
Depts get to deploy scripts with EXTREMELY ADVANCED features that can
actually be understood and used by less experienced SysAdmins.
Although there are countless "FREE" resources available to help with windows
shell scripting, it is often a time-consuming way to solve the problem when
XYZ "free" utility already does the job. Even for those who are experienced
script writers, it is a "frustrating pursuit", as Mr. Bednarek indicated
earlier in this thread.
Taking the part of an "average" system administrator
(http://TheSystemGuard.com/SAProfiles.htm),
the frustration level in just "finding" a solution is
hard enough. Not to mention "choosing" between multiple
ways to solve the problem when you don't fully understand
the answers.
Even though most SysAdmins want to do "the right thing"
and learn scripting, time constraints make this
difficult and they usually need an answer today.
*******
What we provide is a solution to the following:
1. Must work on ANY system "out of the box"
2. Must not add software to the system that
is not part of the "standard build"
3. Must not be so cumbersome to use that the
solution is worse than the problem
#3 is particularly important if you are writing scripts for customers that
will then maintain those scripts themselves. Even if you are the
experienced script writer in a large organization and then send your scripts
out to "local sysadmins" to run, those "local sysadmins" are often not as
experienced as yourself and will either:
a. try to modify your script and break it
b. constantly ask you questions about how the
line containing <insert-magic-code-here> works
c. Both a and b
Using Mount/\Commands in your scripts allows those who don't write scripts
every day to follow the logic of the code and to make minor changes WITHOUT
causing problems.
*****
In essence, we provide a standardized method to perform common tasks WITHOUT
additional software and WITH understandable syntax. We have a COMPLETELY
FREE (Personal or Commercial Use) sampler (http://ntlib.com).
Our "Almost Free" products are extremely inexpensive ($9 down to as low as
$1 per system) and SAVE ENORMOUS AMOUNTS OF TIME.
See (http://MountCommands.com) or (http://NTCmdLib.com)
*******
Think of these as APIs (Application Programming Interfaces) for Windows
Shell Scripts.
Knowledge is built on other knowledge. Very few would write a program to
copy a file sector by sector instead of using the COPY command. The COPY
command is easier to use and self-documenting.
Why write a multiline script to get free disk space when you can just use
"GetFree"?
Why write special code or add utilities so the server-only part of your
script runs only on servers when you can use GetRole?
Or even better than that, just use
ifServer Command [ELSE Command]
*******
For a partial list of available Mount/\Commands, see
(http://TheSystemGuard.com/NTCmdLib/MountCommands)
*******
-tsg
__________________________________________________ __________
TheSystemGuard.com | BoomingOrFuming.com | MountCommands.com
Free and "Almost Free" Knowledge for Windows System Admins!
"Andy Helsby" > wrote in message
m...
> Some of our customers have problems where the source code is not
> available so they can't check for known vulnerabilities or spyware
> (blat source code is available and dtail could be removed (in this
> case it speeds up the processing of the files in the for loop).
>
> There are issues adding third party applications to a customers box -
> namely support, licencing/costs etc etc.
>
> Andy
Many of our customers use our scripting enhancement products instead of
third party utilities because they require ONLY the base operating system
and there is NO BINARY CODE involved (it's a script, so you automatically
get the source code). Others use them because they provide an
UNDERSTANDABLE and CONSISTENT syntax as compared to the arcane "make the %
sign stand on it's head" syntax of the builtin scripting commands.
End-users get hundreds of commands that MS "forgot" to include without
adding any new software. System Integrators, Consultants and Corporate IT
Depts get to deploy scripts with EXTREMELY ADVANCED features that can
actually be understood and used by less experienced SysAdmins.
Although there are countless "FREE" resources available to help with windows
shell scripting, it is often a time-consuming way to solve the problem when
XYZ "free" utility already does the job. Even for those who are experienced
script writers, it is a "frustrating pursuit", as Mr. Bednarek indicated
earlier in this thread.
Taking the part of an "average" system administrator
(http://TheSystemGuard.com/SAProfiles.htm),
the frustration level in just "finding" a solution is
hard enough. Not to mention "choosing" between multiple
ways to solve the problem when you don't fully understand
the answers.
Even though most SysAdmins want to do "the right thing"
and learn scripting, time constraints make this
difficult and they usually need an answer today.
*******
What we provide is a solution to the following:
1. Must work on ANY system "out of the box"
2. Must not add software to the system that
is not part of the "standard build"
3. Must not be so cumbersome to use that the
solution is worse than the problem
#3 is particularly important if you are writing scripts for customers that
will then maintain those scripts themselves. Even if you are the
experienced script writer in a large organization and then send your scripts
out to "local sysadmins" to run, those "local sysadmins" are often not as
experienced as yourself and will either:
a. try to modify your script and break it
b. constantly ask you questions about how the
line containing <insert-magic-code-here> works
c. Both a and b
Using Mount/\Commands in your scripts allows those who don't write scripts
every day to follow the logic of the code and to make minor changes WITHOUT
causing problems.
*****
In essence, we provide a standardized method to perform common tasks WITHOUT
additional software and WITH understandable syntax. We have a COMPLETELY
FREE (Personal or Commercial Use) sampler (http://ntlib.com).
Our "Almost Free" products are extremely inexpensive ($9 down to as low as
$1 per system) and SAVE ENORMOUS AMOUNTS OF TIME.
See (http://MountCommands.com) or (http://NTCmdLib.com)
*******
Think of these as APIs (Application Programming Interfaces) for Windows
Shell Scripts.
Knowledge is built on other knowledge. Very few would write a program to
copy a file sector by sector instead of using the COPY command. The COPY
command is easier to use and self-documenting.
Why write a multiline script to get free disk space when you can just use
"GetFree"?
Why write special code or add utilities so the server-only part of your
script runs only on servers when you can use GetRole?
Or even better than that, just use
ifServer Command [ELSE Command]
*******
For a partial list of available Mount/\Commands, see
(http://TheSystemGuard.com/NTCmdLib/MountCommands)
*******
-tsg
__________________________________________________ __________
TheSystemGuard.com | BoomingOrFuming.com | MountCommands.com
Free and "Almost Free" Knowledge for Windows System Admins!
"Andy Helsby" > wrote in message
m...
> Some of our customers have problems where the source code is not
> available so they can't check for known vulnerabilities or spyware
> (blat source code is available and dtail could be removed (in this
> case it speeds up the processing of the files in the for loop).
>
> There are issues adding third party applications to a customers box -
> namely support, licencing/costs etc etc.
>
> Andy