WELCOME TO WINGUARD (V.2) !!! Please note: This "readme" file (winguard.txt) is an abbreviated version of WinGuard's regular documentation file (winguard.wri), and is intended simply to provide enough information for the authorized user to get started. For security purposes, the longer winguard.wri is not copied to the hard disk, as it describes WinGuard features of which the guest user should not be aware. Please refer to winguard.wri (still on the WinGuard program disk, or in the unzipped winguard.zip file's directory), or to WinGuard's help file (while running the program) for a fuller description of WinGuard's functions. PRODUCT LEGAL INFORMATION First, the necessary legal statements: WinGuard (V. 2.1) Copyright 1992, 1994 by Frederick Wasti. All rights are reserved. CETUS SOFTWARE AND FREDERICK WASTI DISCLAIM ALL WARRANTIES RELATING TO THIS SOFTWARE, WHETHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND ALL SUCH WARRANTIES ARE EXPRESSLY AND SPECIFICALLY DISCLAIMED. NEITHER CETUS SOFTWARE NOR FREDERICK WASTI SHALL BE LIABLE FOR ANY INDIRECT, CONSEQUENTIAL, OR INCIDENTAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE SUCH SOFTWARE EVEN IF CETUS SOFTWARE OR FREDERICK WASTI HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR CLAIMS. IN NO EVENT SHALL THE LIABILITY OF CETUS SOFTWARE OR FREDERICK WASTI EVER EXCEED THE PRICE PAID FOR THE LICENSE TO USE THE SOFTWARE, REGARDLESS OF THE FORM OF THE CLAIM. THE PERSON USING THE SOFTWARE BEARS ALL RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE. This agreement shall be governed by the laws of the Commonwealth of Massachusetts and shall inure to the benefit of 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. The user may use this software on his/her/its own computer(s) only. For further information, please contact: Cetus Software Post Office Box 700 Carver, MA 02330 USA OVERVIEW OF WINGUARD WinGuard can protect a personal computer running Windows 3.1 from having any of its Program Manager groups or items (icons) rearranged or damaged (accidentally or intentionally). These protections would probably be 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 provides for the automatic setting of any one of seven different protection levels (eight, actually, including a "zero protection" setting), as well as allowing the hiding of "sensitive" programs, such as Windows Setup, Control Panel, or File Manager, behind its password-protected shell. WinGuard also allows the hiding of selected Program Manager groups and Control Panel icons, restricting access to them to the authorized user only. Thus, it can be seen that WinGuard enables the authorized user to configure the Program Manager interface to allow the guest user easy access to selected applications, while minimizing the chances of damage (accidental or intentional) to Windows and the programs accessible through it. INSTALLING WINGUARD NOTE: WinGuard requires the file VBRUN300.DLL to run. While vbrun300.dll IS provided on the WinGuard program disk, it is NOT routinely distributed with the compressed version of WinGuard (winguard.zip) that is carried on bulletin board systems. If you have obtained this shareware copy of WinGuard 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 winguard.zip. 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 WinGuard is to run the installation utility, install.exe, located on the WinGuard program disk or in the directory in which winguard.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 WinGuard manually), a list of events that occur during normal installation now follows: 1. Install.exe checks for the version of Windows that is installed; since WinGuard will not work properly with Windows versions earlier than V.3.1, install.exe will terminate (with a message) if the installed Windows version is older. 2. 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. 3. 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 WinGuard 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 winguard.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 WinGuard 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. 4. Install.exe looks for a previous installation of WinGuard on the hard disk. If one is found, it is removed before the newer installation may proceed. 5. Install.exe makes backup copies of three Windows .ini files (copying progman.ini to progman.wgd, control.ini to control.wgd, and win.ini to win.wgd). 6. 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): winguard.exe, winguard.hlp, winguard.dll, winguard.txt, wngrdpwd.txt, educator.txt, whatsnew.txt, regform.txt, and vbrun300.txt. Wngrd.dll and vbrun300.dll will also be copied there, if not already present. Cmdialog.vbx will be copied there, as well, unless a newer version of this file is already present. Install.exe will terminate with a message if any file is not copied properly. 7. Install.exe gives the user the chance to create a WinGuard group in the Program Manager window (strongly recommended, unless one is already present, as this is the easiest way to become familiar with WinGuard'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 WinGuard 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 WinGuard program diskette, or in the winguard.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 winguard.grp (on the WinGuard program diskette, or in the winguard.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 WinGuard for the Description, and winguard.grp for the Group File. Click on OK, and you should see a complete WinGuard 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. Winguard.wri, the expanded version of winguard.txt, is not copied there, either, for security reasons, as it contains details of WinGuard's functions of which a guest user should not be aware. WinGuard may be run from winguard.exe, which should be in the Windows directory (on a networked computer) or in the Windows System directory (on a non-networked computer). Once WinGuard is up and running, you may explore the following various features: PROTECTION LEVELS WinGuard may be utilized by the authorized user to configure Program Manager for any one of seven increasingly restrictive protection levels, or to return it to its default zero- protection setting. These safeguards may run from merely preventing spatial changes from being made by the guest user to bringing about the total inactivation of virtually all Program Manager file functions. Each protection level change is accomplished by first activating the appropriate WinGuard protection level command button (or menu item), and then restarting Windows (which may also be done from within WinGuard). PROTECTION LEVEL 0 Protection Level 0 provides no protection against changes made to Program Manager. (This, of course, is Program Manager's normal, default state, which WinGuard was designed to modify.) Although one of the other protection levels would be more suitable for most security purposes, Level 0 must still temporarily be invoked for those Program Manager changes that the authorized user must occasionally make. Protection Level 0 may be applied by using either the Level 0 command button or the Unprotect button (or by using either of the corresponding menu items). Windows must be restarted before the level change will take effect. PROTECTION LEVEL 1 Protection Level 1 will "dim" the Save Settings on Exit command in the Program Manager Options Menu, preventing the desktop from being permanently rearranged. Under this protection level, spatial modifications to Program Manager may still be temporarily made, but it becomes impossible to save those changes. Therefore, the next time that Windows is started, Program Manager will come up with the original desktop layout intact. It should be noted, though, that Level 1 does not protect against either the creation or deletion of groups, nor does it protect against the creation, deletion, or moving of individual items, or against changes to their properties. Protection Level 1 may be applied by using the Level 1 command button (or by using the corresponding menu item). Windows must be restarted before the level change will take effect. PROTECTION LEVEL 2 Protection Level 2 will prevent the deletion of existing Program Manager groups, or the creation of new groups, as well as maintaining the protections offered by Level 1. When an attempt is made to use the File Menu's New, Move, Copy, or Delete commands while the focus is on a group, it will be found that they are "dimmed", as will be the entire Properties box. Note, however, that no protection is provided against any changes to individual program items or to their properties under Level 2. Protection Level 2 may be applied by using the Level 2 command button (or by using the corresponding menu item). Windows must be restarted before the level change will take effect. PROTECTION LEVEL 3 Protection Level 3 incorporates the safeguards of Levels 1 and 2, plus it will also prevent the deletion or creation of Program Manager items. If an attempt is made to use the File Menu's New, Move, Copy, or Delete commands, it will be found that they are "dimmed". It should be noted, however, that Level 3 does not prevent the changing of any item's properties. Protection Level 3 may be applied by using the Level 3 command button (or by using the corresponding menu item). Windows must be restarted before the level change will take effect. PROTECTION LEVEL 4 Protection Level 4 prevents modifications to the command line (which will be "dimmed") for any program item in the File Menu's Properties dialog box. Level 4 carries over all of the protection features of Levels 1, 2, and 3, as well. Protection Level 4 may be applied by using the Level 4 command button (or by using the corresponding menu item). Windows must be restarted before the level change will take effect. PROTECTION LEVEL 5 Protection Level 5, besides maintaining the safeguards of Levels 1 through 4, will protect against the changing of any program item's properties, by "dimming" the New, Move, Copy, and Delete commands in the File Menu, as well as all of the entry fields in its Properties dialog box. Protection Level 5 may be applied by using the Level 5 command button (or by using the corresponding menu item). Windows must be restarted before the level change will take effect. PROTECTION LEVEL 6 Protection Level 6 will "dim" the Run line in the File Menu, thus preventing one from starting a program not already present as an icon in Program Manager. Since Level 6 carries over all of the protections provided up through Level 5, the only functional commands in the File Menu will be Open, Properties, and Exit Windows (and the Properties option will only be informational in function, since the entire Properties dialog box will be "dimmed"). Protection Level 6 may be applied by using the Level 6 command button (or by using the corresponding menu item). Windows must be restarted before the level change will take effect. PROTECTION LEVEL 7 Protection Level 7 removes the entire File Menu from Program Manager, as well as "dimming" the Save Settings on Exit command in the Options Menu. Protection Level 7 does provide the maximum level of protection against Program Manager changes, but it also creates one potential problem: Since the entire File Menu will have been removed, it becomes impossible to exit from Windows by the normal means, and it is not a good practice to simply turn off or to reboot the computer while still in Windows, especially if any programs with unsaved information are running. However, WinGuard provides its own "Exit Windows" command buttons (and menu item), so that it would still be possible to exit from Windows safely, via WinGuard. Protection Level 7 may be applied by using the Level 7 command button (or by using the corresponding menu item). Windows must be restarted before the level change will take effect. PROGRAM MANAGER GROUPS WinGuard provides the opportunity for the authorized user to hide one or more of the program groups (such as Main, Accessories, Applications, etc.) shown in the Program Manager window, preventing the guest user from accessing (or perhaps even knowing about) any such groups, once protected. If the authorized user needs to redisplay any hidden group, this may be done easily from within WinGuard, although this does require restarting Windows (but this may also easily be done from within WinGuard). If it is desired merely to hide a few selected icons that are present in several different groups, it might be advantageous to create a Program Manager group just for them, and then to move each of them to the new group (by dragging and dropping with the mouse), before hiding the group with WinGuard. If you elected to have a WinGuard group created for you during installation, you may use that group for the one to hide (after copying or moving WinGuard's own icon to another group, of course, in order to access WinGuard after the WinGuard group has been hidden). By the way, if you are not yet familiar with drag-and-drop procedures, you should know that you may copy or move Program Manager icons from one program group to another with the use of just the mouse. For example, if you point at an icon, and then click on it with the left mouse button, you may drag it (by continuing to hold the button down) to another group, and then drop it there (by releasing the button), in order to move it. If you hold down the Ctrl key while performing the above procedure, you will copy the icon, instead of moving it. Note that Windows must be restarted before any program group display change (either hiding a visible group or redisplaying a hidden group) will take effect. Of course, WinGuard's companion security program, ProGuard, allows password-protecting one or several individual icons, without having to remove them from sight, still allowing for quick access to them by the authorized user. (See the section further below on ProGuard Introduction for more information on this related security program from Cetus Software.) CONTROL PANEL ICONS WinGuard provides the opportunity for the authorized user to hide one or more of the icons in the Control Panel window, preventing the guest user from accessing the Program Manager settings for such features as colors, drivers, fonts, printers, virtual memory, and desktop details (such as wallpaper or screen savers). In order that the authorized user may still obtain access to any Control Panel icons that are hidden, WinGuard's Control Panel Icons Window provides command buttons for all of the regular Control Panel functions, whether hidden or otherwise. Note that any changes made in Control Panel icon display will already be in effect the very next time Control Panel is opened (unlike WinGuard's other protections, which require restarting Windows before taking effect). REPLACING TASK LIST Ordinarily, Windows Task List (Task Manager) may be started by double-clicking on the Windows desktop, as well as by activating the Switch To command in the Control Menu of many Windows applications. However, the authorized user has the option of replacing such access to Task List with easy access to WinGuard, instead. That is, double-clicking on the desktop would bring up WinGuard rather than Task List. (WinGuard would still require the proper password, of course.) Besides increasing the ease of accessing WinGuard, this change would be most useful on a computer with a third-party task manager (with window and file functions) installed, which the authorized user might wish to shield from the guest user. Task List may be replaced by clicking on the Replace Task List command in WinGuard's Main Window Options Menu, and the change may be negated by clicking on it once again. If WinGuard has been so set to replace Task List, a checkmark will appear next to the menu item, which will disappear when normal access to Task List has been restored. Note that Windows must be restarted for the actual change to take effect. Even after making this change, the authorized user would still be able to invoke Task List (or a task manager) from within WinGuard, by activating the Switch To command button in WinGuard's Main Window (or the corresponding menu item). (Technically, Task List is not actually replaced, as it is only the access to it that has been changed, having been switched to WinGuard instead.) It is a simple matter at any time for the authorized user to have WinGuard restore normal access to Task List, and even to certain custom task manager installations. However, if WinGuard detected that a third-party task manager was installed on the computer in such a way that WinGuard would not have been able to restore it, then the Replace Task List menu command would have been disabled. WINGUARD SECURITY In order to restrict access to WinGuard and the programs that it protects, it is necessary for the authorized user to use a password. For the shareware version of WinGuard, 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. A registered user of WinGuard is given the opportunity to choose his/her own private default password at the time of installation. (Note, for security purposes, most security measures are not covered in winguard.txt; please refer to winguard.wri, on the WinGuard program diskette, or in the winguard.zip directory, for more information on password security.) EXITING WINGUARD WinGuard provides several way to close itself, depending upon the circumstance. It is possible to close WinGuard and then return to Windows, either with or without saving any protection level changes that may have just been made. It is also possible to close WinGuard and then to either exit or restart Windows, to bring about desired Program Manager protection level and/or group changes immediately. The Protect Now command will restart Windows with the currently selected protection level in place. The Unprotect Now command will restart Windows with Level 0 in place, regardless of the current protection level setting. The Cancel Changes command will close WinGuard and then return to Windows, after first undoing any protection level changes made during that running of WinGuard. Note, however, that the Cancel Changes button will undo only protection level changes, not program group changes or Control Panel icon changes (which must be undone individually, using the Program Manager Groups Window or the Control Panel Icons Window). The Exit Windows command will close WinGuard and then exit Windows, activating the currently selected protection level. The Exit WinGuard command will close WinGuard and then return to Windows, to have any changes made in Program Manager groups or protection level take place the next time that Windows is started. WINGUARD'S WINDOWS WinGuard involves five windows, as follows: The center of the WinGuard program is the Main WinGuard Window. One of the other windows is an opening window that leads to the Main Window, and the other three windows are accessed from within the Main Window. The opening window is the Password Entry Window, which must be gotten past by the proper entry of a password before reaching the Main Window. The principal functions of WinGuard's Main Window include setting the Program Manager protection level, accessing "sensitive" Windows programs that may be hidden within WinGuard, reaching other WinGuard windows, and exiting from WinGuard. Accessible from the Main Window are windows for controlling the visibility of Program Manager program groups, controlling the visibility of Control Panel icons, and changing the WinGuard working password. You should explore the features and functions of each window, referring to both the on-line help file and winguard.wri for assistance. Some experimentation will be necessary before you will be able to have your computer configured with exactly the protections it needs for your particular situation. ABOUT CETUS SOFTWARE Cetus Software is the creator of several Windows utilities, including ProGuard, Reveille, and Seasons, as well as WinGuard. 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 inquiries regarding Cetus Software products to: Cetus Software Post Office Box 700 Carver, MA 02330 USA Cetus Software thanks you for trying out WinGuard !!! STOREWINDOWS INTRODUCTION In addition to WinGuard, Cetus Software offers a similar security program, StoreWindows, offering essentially the same functions as WinGuard, but depending on an entirely different means of security. Like WinGuard, StoreWindows can protect a Windows 3.1 computer from having any of its Program Manager groups or icons rearranged or damaged. StoreWindows 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. StoreWindows' protections would probably be the most useful to someone in charge of a number of computers at a business or at a school. For security purposes, StoreWindows is designed to perform its functions directly from a diskette, kept in the possession of the authorized user, and thus StoreWindows can conveniently provide ideal protection to any number of Windows computers on display in a store, without requiring installation onto any of their hard disks. The shareware version of StoreWindows is available on several bulletin board systems, or may be obtained on diskette in uncompressed form, directly from Cetus Software (P.O. Box 700, Carver MA 02330 USA), for a nominal charge ($5.00, postpaid). PROGUARD INTRODUCTION In addition to WinGuard, Cetus Software offers a related security program, ProGuard. Unlike WinGuard, which is intended to protect Program Manager itself, ProGuard is designed to password-protect individual Program Manager icons. Thus, while WinGuard is more "global" in its protections, ProGuard is more application-specific. ProGuard is designed to make it more difficult for a guest user to run selected programs 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 attempting to run the program will cause ProGuard to run instead, and that a password will be needed before the actual program can be made to start. Logical programs to protect might include Windows Setup, Control Panel, PIF Editor, System Editor, and File Manager (and most users will have other programs that they would wish to protect, as well). When ProGuard is installed, the setup program provides icons for the above programs, already protected by ProGuard (and it's a simple matter to add ProGuard's protection to any other application's Program Manager icon, as well). The shareware version of ProGuard is available as proguard.zip on several bulletin boards systems, or may be obtained on diskette in uncompressed form directly from Cetus Software (PO Box 700, Carver MA 02330 USA) for $5.00 (postpaid). REGISTERING WINGUARD If you are trying out the shareware version of WinGuard, then you must be aware of the following legal aspects of shareware evaluation: You are entitled to install WinGuard on ONE computer, and to "test-drive" the program for a 30-day (MAXIMUM) trial period. IF you wish to give WinGuard a more permanent home on your computer's hard disk, OR if you wish to install WinGuard on more than one computer, then you MUST register your use of WinGuard. You would then be provided with a copy of the latest version of the program (without any "reminder screens"). INDIVIDUAL USER REGISTRATION WinGuard may be registered to an individual user for $14.95 (including shipping and handling). An individual who has registered a previous version of WinGuard may upgrade to Version 2 for $9.95 (including shipping and handling). You may use the registration form in this document (or you may simply print out the separate regform.txt document); if you prefer, you may provide ALL of the registration information in a separate letter or purchase order. An Individual License for WinGuard entitles the registered individual user to install the program on any computer(s) that he/she personally owns, but he/she must NOT allow his/her registered copy of the program to be installed or used on any other computer(s). SITE LICENSE REGISTRATION A Site License for WinGuard entitles the registered institution (school building, business location, organization headquarters, etc.) to install the program on any computer(s) belonging to that institution at that particular location, but registered copies of the program may NOT be distributed beyond the boundaries of that particular location. Furthermore, a copy of WinGuard that is registered to an individual user may be installed on his/her own computer at an institution, but that individually licensed copy of WinGuard man NOT be installed on any other computer(s) at that institution (for which a Site License would be required). WinGuard may be registered to an institution for $74.95 (including shipping and handling). An institution that has registered a previous version may upgrade for $49.95 (including shipping and handling). You may use the registration form at the end of this document (or you may simply print out the separate regform.txt document); if you prefer, you may provide ALL of the registration information in a separate letter or purchase order. PROGRAM DISTRIBUTION While registered copies of WinGuard may NOT be used by any other than the registered individual or institution, any person is permitted (and, in fact, ENCOURAGED) to distribute the UNregistered, shareware version of WinGuard to others, as long as ALL of its files are distributed together. CETUS SOFTWARE THANKS YOU FOR TRYING OUT WINGUARD !!! ***************************************************************** WINGUARD V.2 REGISTRATION FORM - PLEASE TYPE OR PRINT CLEARLY Date ___________________________ Name of Registered User (for Individual License): _________________________________________________ (or) Name of Registered Institution (for Site License): _________________________________________________ (If multiple, 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 enclosed: 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.) (All of the above prices include shipping and handling costs.) Please send this form, along with payment (or purchase order) to: Cetus Software Post Office Box 700 Carver, MA 02330 USA CETUS SOFTWARE THANKS YOU FOR YOUR WINGUARD REGISTRATION !!!