WELCOME TO PROGUARD !!!
ProGuard is a Windows utility designed to make it impossible for
guest users to run selected programs simply by double-clicking on
their icons in Program Manager. Once a particular program's icon
has been protected by ProGuard, the guest user will find that
trying to run the program will cause ProGuard to run instead, and
that a password will be needed before the actual program will
start. Logical icons to protect might include those for Windows
Setup, Control Panel, PIF Editor, System Editor, File Manager,
and the MS-DOS Prompt, and it's a simple matter to add ProGuard's
protection to any other application's icon, as well.
ProGuard V.2 can also prevent the guest user from starting any
program that is not present as an icon in Program Manager, and
can prevent the guest user from creating, copying, moving, or
deleting icons, or changing any of their properties.
NOTE: ProGuard requires the file VBRUN300.DLL to run. While
vbrun300.dll IS provided on the ProGuard program disk, it is NOT
routinely distributed with the compressed version of ProGuard
(prgrd-20.zip) that is carried on bulletin board systems. If
you have obtained this shareware copy of ProGuard from an on-
line service, you also will need to have a copy of vbrun300.dll
installed in either the Windows directory or the Windows System
directory. If you do not have a copy of vbrun300.dll, you can
probably download one from the same BBS from which you obtained
proguard.zip. You may also obtain a copy of vbrun300.dll from
Cetus Software (P.O. Box 700, Carver, Mass. 02330) for a nominal
cost ($5.00, postpaid).
The easiest (and recommended) way to install ProGuard is to run
the installation utility, install.exe, located on the ProGuard
program disk or in the directory in which proguard.zip was
"unzipped". For those that wish to know what occurs during
installation, or for some reason are not able to use install.exe
(and wish to install ProGuard manually), a list of events that
occur during normal installation now follows:
1. Install.exe tries to detect three paths: the location of
the source files, the location of the Windows directory, and the
location of the Windows System directory. The user is asked to
confirm (or correct) the detected paths. Note that, on most
non-networked computers, the Windows directory will typically be
c:\windows, while the Windows System directory will typically be
c:\windows\system. However, a networked computer will likely
have a very different arrangement, with the Windows directory
being something like, say, q:\yourname, while the System
directory might be something like g:\windows.
2. Install.exe checks the three paths for the presence of
vbrun300.dll, a file needed by Visual Basic programs. It must
be found in the Windows or Windows System directory for ProGuard
to run, so if it is not already there, and is not found with the
source files (and vbrun300.dll is not routinely distributed as
part of proguard.zip over bulletin board systems), then
install.exe ends with a message pointing out that a copy of
vbrun300.dll must be placed there. Note that vbrun300.dll IS
found on the ProGuard program diskette, and will (if necessary)
be copied to either the Windows directory (on a networked
computer) or to the Windows System directory (on a non-networked
PC) later on in the installation.
3. Install.exe copies the following files to either the Windows
directory (on a networked computer) or to the Windows System
directory (on a non-networked PC): run.exe, proguard.hlp,
proguard.dll, proguard.txt, prgrdpwd.txt, and vbrun300.txt.
Prgrd.dll and vbrun300.dll will also be copied there, if not
already present. Install.exe will terminate with a message if any
file is not copied properly.
4. Install.exe gives the user the chance to create a ProGuard
group in the Program Manager window (strongly recommended,
unless one is already present, as this is the easiest way to
become familiar with ProGuard's features). If the "go ahead" is
given, install.exe will have makgroup.exe (also found among the
source files) create the new group, concluding the installation.
If the installation program was not able to automatically create
a ProGuard Program Manager group for you, or if you elected at the
time of installation not to create one (but wish to do so now),
here are steps you may follow:
First, you might try running makgroup.exe (on the ProGuard
program diskette, or in the proguard.zip directory); this is
the program that install.exe would call to create the program
group, and it may create the group for you now.
Or, you might try copying the file proguard.grp (on the ProGuard
program diskette, or in the proguard.zip directory) to the
Windows directory. Then, select the File Menu in Program
Manager, then New, and then Program Group. When you obtain a
Program Group Properties dialog box, enter ProGuard for the
Description, and proguard.grp for the Group File. Click on OK,
and you should see a complete ProGuard group appear.
Note that certain installation files, such as install.exe and
makgroup.exe, are not copied to the hard disk, nor is the
uninstallation program, uninstal.exe. Proguard.wri, the
expanded version of proguard.txt, is not copied there, either,
for security reasons, as it contains details of ProGuard's
functions of which a guest user should not be aware.
ProGuard may be run from run.exe, which should be in the Windows
directory (on a networked computer) or in the Windows System
directory (on a non-networked computer). Once ProGuard is up and
running, you may start exploring ProGuard's features.
Please refer to proguard.wri, or to the ProGuard help file
(accessible from within ProGuard only after the proper password
has been entered) for a description of ProGuard's functions.
FOR FURTHER INFORMATION
If you have questions not answered by ProGuard's text files or
its on-line help file, please feel free to contact me (Frederick
Wasti) at Cetus Software (P.O. Box 700, Carver, MA 02330 USA, or
Internet [email protected]
), and I'll try to help.
THANK-YOU FOR YOUR INTEREST IN PROGUARD !!!