Category : Windows 3.X Files
Archive   : PRGRD-20.ZIP

Output of file : PROGUARD.WRI contained in archive : PRGRD-20.ZIP
1¾«‚dÎØØÙÚÚÛà=Ð/ÿÿ  2À!8¨9ÐÐ[ This is PROGUARD.WRI, the ProGuard documentation file. ]



Legal Information
Overview of ProGuard
Installing ProGuard
ProGuard's Windows
ProGuard Security
Protection Shield Settings
Password Protection
Uninstalling ProGuard
About Cetus Software
WinGuard Introduction
StormWindows Introduction
PadLock Introduction
Registering ProGuard
Registration Form

Product Legal Information

ProGuard V.2.0 Copyright 1994 Frederick Wasti. All Rights Reserved.


This agreement shall be governed by the laws of the Commonwealth of Massachusetts and shall inure to the benefit of Cetus Software and/or Frederick Wasti, and any successors, administrators, heirs, and assigns. Any action or proceeding brought by either party against the other arising out of or related to this agreement shall be brought only in a state or federal court of competent jurisdiction located in the Commonwealth of Massachusetts. The parties hereby consent to in personam jurisdiction of said courts.

This software and the disk on which it is obtained is licensed to an individual or institution user, for his/her/its own use. This is copyrighted software. The user is not obtaining title to the software or any copyright rights. The user may not sublicense, rent, lease, convey, modify, translate, convert to another programming language, decompile, or disassemble the software for any purpose. The user may make one copy of the software for back-up purposes only. The user may use this software on his/her/its own computer(s) only.

Overview of 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 is 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.

Installing ProGuard

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 ( 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 You may also obtain a copy of vbrun300.dll from Cetus Software (P.O. Box 700, Carver, Mass. 02330) for a nominal charge ($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 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 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 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 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, which you are now reading, 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.

ProGuard's Windows

ProGuard consists of three windows, a Password Entry Window (used to enter the correct ProGuard password), a Protection Shield Window (used to enable or disable ProGuard's Protection setting), and a New Password Window (used to change the working ProGuard password).

The Password Entry Window is accessed when ProGuard first runs. The Protection Shield and New Password Windows are reached from the Password Entry Window, to which they return when they are closed. The protected application starts up after the Password Entry Window is cleared.

ProGuard Security

When ProGuard is installed, the setup program gives the user the opportunity to create a Program Manager group for ProGuard, and within this group are icons for Windows Setup, Control Panel, PIF Editor, System Editor, and File Manager. The easiest way to implement protection for any one of these programs would be to simply delete the regular Program Manager icon for it and then drag the protected icon from the ProGuard group into its place.

It is a simple matter to add ProGuard's protection to any icon by adding "run " (including the trailing space) before the program's filename in the File Properties dialog box. Then, when the icon is activated by the user, run.exe (ProGuard's executable program filename) will run first, and only after getting past a password hurdle will the guest user be able to get the actual program to start.

When you do the above, please note that you will have to change the icon back to that of the protected application, since Program Manager will have replaced its icon with ProGuard's (unless, of course, you might wish to use ProGuard's own icon). Single-click on the icon to highlight it, click on the File menu, then on Properties, and then on Change Icon. Enter the path for the protected program in the Filename box, and then click on OK, and OK again. The protected application's icon should now be visible again in Program Manager.

Of course, the ProGuard Protection setting must be "Exposed", in order to change any Properties box entries, but then it should be set to "Shielded", and Windows restarted, in order to prevent a guest user from undoing this icon protection; please see the section on Protection Shield settings, below, for more information on this.

If it is desired to prevent the guest user from obtain access to any program that is not present as an icon in Program Manager, or is not password-protected by ProGuard, then the DOS-Prompt and File Manager icons should be password-protected by ProGuard.

(By the way, "run.exe" was given its name in order to make it less obvious to a curious guest user exactly why a desired program does not start; it was felt that "run" before a Properties filename might just look to a less-than-expert guest user like some sort of DOS or Windows command.)

ProGuard actually comes with two help files. One is named proguard.hlp, and is the file that may be accessed (by using the F1 key) before the correct password has been entered, when ProGuard first starts. However, for security purposes, proguard.hlp is a very small help file with only one window, warning the guest user about ProGuard's password protection. However, once the correct password has been typed in by the authorized user, the regular help file (which is actually named proguard.dll) comes up instead, whenever Windows help is invoked.

Protection Shield Settings

ProGuard V.2 allows the authorized user to protect Windows Program Manager against most of the damages that might be caused by a guest user. There are two Protection Shield settings available, accessed from the Protection Shield Window.

The Shielded setting prevents guest users (and, in fact, the authorized user) from employing the New, Move, Copy, Delete, and Run commands in Program Manager's File Menu, as ProGuard will cause each of them to be "dimmed". The Properties command is still functional, but the Properties dialog box becomes a read-only control, as all of its fields will be "dimmed", as well.

The Exposed setting provides no protection to damages done by a guest user (which is, of course, the default Windows condition). The Exposed setting must be used by the authorized user whenever he/she wishes to change which icons are to be protected, or wishes to modify many other aspects of Program Manager's configuration.

While it is possible to utilize ProGuard's command line protection (password-protecting individual icons) without the Shielded setting, this is not recommended, since a more knowledgeable Windows user would be able to remove the "run" before an application's filename, and thus work around ProGuard's protection.

Note that Windows must be restarted before any change in the ProGuard Protection setting will take place.

Note also that, if the authorized user is also using either WinGuard or StormWindows (two other Windows security programs available from Cetus Software), it is recommended that protection settings be changed using one of those programs, since they provide finer control over the types and degree of Windows protection than does ProGuard.

Password Protection

In order to restrict access to ProGuard and the programs that it protects, it is necessary for the authorized user to use a password. For the shareware version of ProGuard, the default password at the time of initial installation is "shield", but this should be changed to one of the authorized user's own choosing as soon as possible. The actual password is stored in a file, prgrd.dll, in coded form.

If the authorized user ever forgets the password, or if the password file becomes corrupted, then prgrd.dll should be deleted; ProGuard may then be started by using the default password of "shield", and the working password may then be chosen once again. (Note that the registered version of ProGuard comes with a private default password individually chosen at the time of registration.)

The password may be changed at any time after the correct password has been entered. The password must consist entirely of letters (not case-sensitive) and/or numbers, with no spaces or punctuation, and is limited to a maximum of twenty characters.

To make it more difficult for someone else to see the password as the authorized user enters it, the password itself does not appear on the screen (except when the working password is actually being changed, which should be done in private). Furthermore, if either a period or comma is typed at the end of the actual password, several "decoy" characters may be entered immediately afterward (as ProGuard will only read the characters up to the period or comma), so that someone watching the password being entered would have trouble even counting how long the password actually is.

Uninstalling ProGuard

ProGuard may be easily uninstalled with the use of its uninstallation program, uninstal.exe. For the purpose of security, uninstal.exe is not present along with run.exe and its support files in the Windows directory (on a networked computer) or in the Windows System directory (on a non-networked PC). Instead, uninstal.exe may be found on the original installation diskette, or in the directory in which the original file was "unzipped".

Please ENSURE that the following is true BEFORE attempting to uninstall ProGuard: FIRST-The Protection Shield setting MUST be set to "Exposed". SECOND- ProGuard itself must NOT be running. THIRD- Ideally, NO other program (besides Program Manager or File Manager) should be running.

Uninstal.exe will remove most of ProGuard's files. However, some of the uninstallation must still be done manually, as uninstal.exe will not be able to tell exactly which icons have been protected. Any icon protected with "run [filename]" should have the "run" manually deleted from its command line.

Furthermore, uninstal.exe will not delete vbrun300.dll, located in either the Windows directory (on a networked computer) or in the Windows System directory (on a non-networked PC), as some other application (any other program written in Visual Basic V.3.0) might also need that file. It must be left up to the authorized user to decide if vbrun300.dll may be safely deleted.

Registering ProGuard

ProGuard is NOT "freeware" !!!

The shareware version of ProGuard is being distributed on a trial basis for evaluation purposes, and is not "crippled" in any way, so that you may fairly judge ProGuard thoroughly. You may install the unregistered, shareware version of ProGuard on any one computer, and then try it out for 30 days. After this trial period you MUST either register your use of ProGuard, OR uninstall it, removing it from that computer. If you do indeed find ProGuard to be a useful addition to your computer's hard disk, then you MUST register your use of the program; in doing so you will be entitled to receive on disk a copy of the latest registered version of ProGuard, without any "reminder screens".

(Please note: A registration form may be found at the end of this file, or you may simply print out the separate regform.txt file.)

On the registration form you are given the opportunity to choose your own private default password (the password that may be used to access ProGuard if the password file, prgrd.dll, is deleted). Selecting a private default password will prevent even other knowledgeable ProGuard owners from being able to access your ProGuard program. Note that the password must consist of no more than twenty letters (not case-sensitive) and/or numbers, with no spaces or punctuation. Note also that, if you do not choose a private default password, then the default password on your registered copy of ProGuard will remain as "shield". (Of course, the "regular" current password, coded into the prgrd.dll file, may be changed from within ProGuard by you at any time.)

A single-user Individual License for ProGuard may be obtained for $14.95. A Site License for the use of ProGuard on any number of computers at ONE specific institutional location may be obtained for $74.95. (Note that each of the above prices includes shipping costs.) Please contact Cetus Software if you wish to discuss other licensing arrangements.

An Individual License entitles one individual registered user to install and use ProGuard on any computer(s) that he/she personally owns, but he/she must NOT allow his/her registered copy of ProGuard to be installed or used on any other computer(s). A copy of ProGuard registered to an individual user may be installed and used on his/her own personal computer(s) at an institution, but that personal copy of ProGuard must NOT be installed or used on any other computer at that institution, whether belonging to another individual or to that institution.

A Site License entitles the registered institution (school building, business office, organization headquarters, etc.) to install and use ProGuard on any number of computers belonging to that institution at that specific location. Any institution with multiple locations MUST obtain a separate site license for EACH location. Any copy of ProGuard registered to a particular institution location may NOT be distributed beyond the boundaries of that institutional site.

However, any person is permitted (and, in fact, ENCOURAGED) to distribute the UNregistered, shareware version of ProGuard to others, as long as ALL of its files are distributed together. For further information on ProGuard registration, or to obtain a copy on disk of the shareware version of ProGuard for free distribution and evaluation, please contact Cetus Software.

About Cetus Software

Cetus Software is the creator of several Windows utilities, including WinGuard, StormWindows, Reveille, PadLock, and Seasons, as well as ProGuard. Shareware versions of these products may be found on several bulletin board systems, or may be obtained on diskette directly from Cetus Software for a nominal charge ($5.00 each, postpaid).

Please direct all inquiries regarding Cetus Software's products to:

Cetus Software, P.O. Box 700, Carver, Mass. 02330 USA

( Internet E-Mail Address: [email protected] )

WinGuard Introduction

In addition to ProGuard, Cetus Software offers a related security program, WinGuard, offering protection on a more "global" scale than ProGuard. WinGuard is designed to shield Program Manager itself, unlike ProGuard (which is primarily intended to password-protect individual Program Manager icons).

WinGuard can protect a Windows 3.1 computer from having any of its Program Manager groups or icons rearranged or damaged. This protection would probably be the most useful to someone in charge of a number of computers at a school or business, though a parent might wish to prevent little fingers on a mouse from dragging all of the Program Manager icons into a (not so) nice "happy face"!

WinGuard can also hide "sensitive" programs (such as Windows Setup, Control Panel, or File Manager), as well as selected Program Manager groups and Control Panel icons, behind its password-protected shell, restricting access to them to the authorized user only. WinGuard can even hide from sight entire Program Manager program groups.

Thus, it can be seen that WinGuard may be used to configure the Program Manager interface to allow easy access to selected applications for a guest user, while minimizing the chances of damage (accidental or intentional) to Windows and the programs accessed through it.

The shareware version of WinGuard is available on bulletin board systems, or may be obtained on diskette in uncompressed form, directly from Cetus Software, for $5.00 postpaid.

StormWindows Introduction

In addition to ProGuard, Cetus Software offers a related security program, StormWindows, offering protection on a more "global" scale than ProGuard. Unlike ProGuard, but like WinGuard, StormWindows is designed to shield Program Manager itself.
Unlike WinGuard, which is designed to perform from a hard disk installation, StormWindows is designed to function from a diskette, kept in the possession of the authorized user.
StormWindows can protect a Windows 3.1 computer from having any of its Program Manager groups or icons rearranged or damaged. This protection would probably be the most useful to someone in charge of a number of computers at a school or business, and StormWindows can provide ideal protection to Windows PCs on display in a store.

Unlike WinGuard, which is designed to perform from a hard disk installation, StormWindows is designed to function from a diskette, kept in the possession of the authorized user.

The shareware version of StormWindows is available on bulletin board systems, or may be obtained on diskette in uncompressed form, directly from Cetus Software, for $5.00 postpaid.

PadLock Introduction

PadLock may be used to "lock out" unauthorized users from accessing Windows or any Windows application. While PadLock is running, no keyboard or mouse command will have any effect outside of the PadLock window itself. Entry of the proper password (chosen by the authorized user) is required to access any of PadLock's controls or to end its protection.

PadLock may be configured to "lock up" Windows automatically at startup, or PadLock may simply be run whenever the authorized user desires to "freeze" Windows (such as when leaving the computer unattended), preventing any access by unauthorized users. PadLock even provides the authorized user with the means to edit system files, and to exit Windows, restart Windows, or reboot the computer from within itself.

The shareware version of PadLock is available on bulletin board systems, or may be obtained on diskette in uncompressed form, directly from Cetus Software, for $5.00 postpaid.

ProGuard Registration Form :

PLEASE TYPE OR PRINT CLEARLY : Date ___________________________ Name of User (for Individual License) ________________________________________ (or) Name of Institution (for Site License) ________________________________________ (If multiple Site Licenses are being obtained, please list on the back of this form.) Mailing Address _________________________________________________ Mailing Address _________________________________________________ Mailing Address _________________________________________________ Daytime Telephone Number (with Area Code) ____________________________ Default Password Choice __________________________________ (Maximum of 20 letters or numbers, with no spaces or punctuation) Please circle size of diskette desired: 3-1/2" 5-1/4" Please fill in the appropriate line with the amount you are enclosing: One Individual License @ $14.95 = $____.95

_____ Site License(s) @ 74.95 = $_____.___

One Individual License Upgrade @ $9.95 = $___.95

_____ Site License Upgrade(s) @ $49.95 = $_____.___
(Massachusetts residents: Please include 5% state sales tax.) (Please note that the above prices include shipping and handling costs.) Please send this Registration Form, along with payment (or purchase order) to:

Cetus Software, P.O. Box 700, Carver, Mass. 02330 USA

Cetus Software thanks you for your ProGuard registration !!!

Y>USQÜ M Ü ð w#s#o#k.#gB.c^._5[(5W“;Sª;OEAK EA[Aw]As}ApNl³NhQPdºPa¼P]ÓPY¥VUÀVQ&[M &[:[w÷^s_o dk‚dh€¼ÿÿ¾ÿÿ‘ÿÿ“ÿÿªÿÿ¬ÿÿ¿ÿÿÕÿÿêÿÿþÿÿÿÿ-ÿÿBÿÿYÿÿoÿÿ†ÿÿ¡ÿÿ·ÿÿÍÿÿàÿÿàâÿÿýÿÿÿÿÿEÿÿGÿÿÿÿÿÿ•ÿÿ—ÿÿ²
ÿÿ<ÿÿ>ÿÿSÿÿUÿÿ'ÿÿ')ÿÿÎÿÿÐÿÿ2ÿÿ4ÿÿÿÿÿÿÿ•ÿÿ—ÿÿÿÿÿÿ÷ÿÿùÿÿáÿÿãÿÿ‰ÿÿ‹ÿÿáÿÿãÿÿÚ ÿÿÚ Ü ÿÿð ÿÿò ÿÿþ!ÿÿ"ÿÿ#ÿÿ#ÿÿ.#ÿÿ0#ÿÿï$ÿÿñ$ÿÿ€&ÿÿ‚&ÿÿž(ÿÿ (ÿÿî)ÿÿð)ÿÿð*ÿÿò*ÿÿ,ÿÿ,,ÿÿ@.ÿÿB.ÿÿ^.ÿÿ`.sO/ÿÿQ/ÿÿÉ0ÿÿË0ÿÿ2ÿÿ2ÿÿO3ÿÿQ3ÿÿ¼3ÿÿ¾3ÿÿ5ÿÿ5kú´ú´5(5ÿÿ*5ÿÿÀ6ÿÿÂ6ÿÿJ8ÿÿL8ÿÿG9ÿÿI9ÿÿ‘;ÿÿ“;ÿÿª;ÿÿ¬;ÿÿs=ÿÿu=ÿÿ•>ÿÿ—>ÿÿÇ?ÿÿÉ?ÿÿCAÿÿEAÿÿEA[Aÿÿ]Aÿÿ}AÿÿAÿÿ5Dÿÿ7Dÿÿ½Dÿÿ¿Dÿÿ¶Gÿÿ¸GÿÿIÿÿIÿÿKKÿÿMKÿÿ$Mÿÿ&Mÿÿ›NÿÿNÿÿ³NÿÿµNÿÿµNPÿÿ
PÿÿOPÿÿQPÿÿˆPÿÿŠPÿÿºPÿÿ¼PÿÿÓPÿÿÕPÿÿRÿÿRÿÿ‹SÿÿSÿÿÞTÿÿàTÿÿïUÿÿñUÿÿ£Vÿÿ¥Vÿÿ¥VÀVÿÿÂVÿÿ¸WÿÿkXÿÿ·Yÿÿ¹YÿÿlZÿÿnZÿÿ$[ÿÿ&[ÿÿ<[ÿÿ>[ÿÿ¢\ÿÿ¤\ÿÿB^ÿÿD^ÿÿõ^ÿÿ÷^ÿÿ_ÿÿ_ÿÿ_•bÿÿ—bÿÿÃbÿÿÅbÿÿ÷bÿÿùbÿÿ.cÿÿ dÿÿ dÿÿBdÿÿDdÿÿ‚dÿÿƒdÿÿ
à=Ð/ÿÿ  2À!Ð;ÐÐÈ(ÿÿ—bÿÿÃbÿÿÅbÿÿ÷bÿÿùbÿÿ.cÿÿ dÿÿ dÿÿBdÿÿDdÿÿ‚dÿÿƒdÿÿï/Ÿ 2dldÿÿÿÿÿÿ—bÿÿÃbÿÿÅbÿÿ÷bÿÿùbÿÿ.cÿÿ dÿÿ dÿÿBdÿÿDdÿÿ‚dÿÿƒdÿÿï/Ÿ 26n
D3Times New Roman Arialÿÿ—bÿÿÃbÿÿÅbÿÿ÷bÿÿùbÿÿ.cÿÿ dÿÿ dÿÿBdÿÿDdÿÿ‚dÿÿƒdÿÿï/Ÿ 2

  3 Responses to “Category : Windows 3.X Files
Archive   : PRGRD-20.ZIP

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: