///////////////////////////////////////////////////////////////// // // Welcome to File Manager Guard! // // for Microsoft(R) Windows(R) 3.1, 3.11 // and Windows for Workgroups(tm) 3.11 // // Version 2.06 // // Last updated: June 3, 1995 // // Copyright (c) 1994-95, ChaoSoft. // All rights reserved. // // _______ // ____|__ | (R) // --| | |------------------- // | ____|__ | Association of // | | |_| Shareware // |__| o | Professionals // -----| | |--------------------- // |___|___| MEMBER // ///////////////////////////////////////////////////////////////// This file contains information regarding FM Guard. STOP! IMPORTANT NOTE 1: Before reading any further, please verify that you have a complete set of the files originally included in the FM Guard package. The list of the files may be found in the VENDINFO.DIZ file, supplied with the package. If any file listed in the VENDINFO.DIZ file, or the VENDINFO.DIZ file itself, is missing, then the package is not complete and its further use or distribution is PROHIBITED. Please contact us at the address at the end of this file to obtain a complete package of the software. IMPORTANT NOTE 2: Please read Chaosoft License Agreement, which may be found in the VENDINFO.DIZ file, supplied with the package, before using this software. By using FM Guard you are agreeing to be bound by the terms of that agreement. TABLE OF CONTENTS ----------------- 1. Introduction 1.1. About FM Guard 1.2. What's new in this version 1.3. This is Shareware - Try Before You Buy! 1.3.1. What is the difference between registered and unregistered versions 1.3.2. What do you get when you register FM Guard 1.3.3. How to register the program 1.3.4. How to order a site license 1.3.5. May I make a copy for a friend? 2. Installing/uninstalling FM Guard 3. Restricting Windows with FM Guard 3.1. General considerations 3.2. Setting up FMGUARD.SYS 3.3. Using PASSWORD.EXE utility 3.4. Restricting Common Dialogs 4. Getting updates to the software 5. Acknowledgements 6. Getting technical support Appendix A. Restricting Program Manager Appendix B. Restricting Control Panel /////////////////////////////////////////////////////////////// // // 1. INTRODUCTION // /////////////////////////////////////////////////////////////// _______________________________________________________________ 1.1 About File Manager Guard ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ File Manager Guard (or, for short, FM Guard) is a powerful utility for Microsoft(R) Windows(tm) 3.1, 3.11, and Windows for Workgroups (tm) 3.11, that allows one to selectively disable features and capabilities of File Manager and some other Windows components. You will find FM Guard indispensable if you share you computer with someone else and you don't want the other one to mess your system up (even if s/he is someone very special!). Or, if you allow your kids to play games on your system from time to time, and want to be sure that everything will be OK when they finish them. Or if you are a network administrator and your users give you a headache messing the files up all the time. Or ... After installing FM Guard, you will be able to prevent user(s) from performing any or all commands of File Manager, from running undesirable programs, browsing hidden files, changing file attributes, etc. FM Guard allows you to select which drives should NOT be accessible via File Manager and Common Dialogs ('Open', 'Save As', etc.). It even provides you with the possibility to keep the size and location of the File Manager window in the same place on the screen! And if you need to restore the capabilities of File Manager for your use, just enter a password and they are back. _______________________________________________________________ 1.2. What's new in this version : ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ver. 2.06: - The ability to setup user specific configuration files for FM Guard is implemented. If the command 'ProcessLocalFile=ON' is specified in the FMGUARD.SYS file, then after processing FMGUARD.SYS file in the WINDOWS\SYSTEM directory, the contents of an additional file with restricting commands is analized. The location of this additional file is specified with the command 'fmguard=' which should be added to the [windows] section of the WIN.INI file. The user specific configuration file may contain any restrictive commands, overriding the corresponding settings in the FMGUARD.SYS file, thus providing a way to make File Manager more or less restrictive depending on the user. Please see section 3.1 of this file and description of the command 'ProcessLocalFile' in the FMGUARD.SYS for details. - Functionality of the commands NoDeleteEdit, and other similar commands, restricting controls in dialog boxes, is extended: they now work with non-English versions of Windows; Ver. 2.05: - New restricting commands are introduced: NoDeleteEdit, NoRunEdit, NoMoveEdit, NoCopyEdit, NoRenameEdit, NoPrintEdit. They allow you to partially disable the corresponding commands by disabling the editing fields in the dialog boxes. This enables your users to manage their own files while preventing them from typing *any* file name in the editing fields of the dialog boxes. For example, you may want to allow the user to use the Delete command to delete his own files, by highlighting the files in File Manager and choosing File-Delete from main menu. To achive that, you would specify 'NoDelete = OFF' to enable access to the 'Delete' command, but also use 'NoDeleteEdit = ON' to prevent modifying the filename in the dialog box. In this way the user won't be able to delete files located on a 'restricted' disk, for instance. - New restricting commands are introduced: NoShowSystemHiddenFiles and NoAttributesEdit. Please see FMGUARD.SYS file for comments on their use. - the functionality of the NoMakeSystemDisk command is extended: if specified, this command not only disables the corresponding menu item in the 'Disk' submenu, but also disables the 'Make System Disk' check box in the 'Format Disk' dialog box. This allows your users to format disks while preventing them from making system disks. Ver. 2.04: - New restricting command, 'NoGrayedMenus', is introduced, which affects the execution of the commands NoFileMenu, NoDiskMenu, etc., used to disable the popup submenus of File Manager. If 'NoGrayedMenus=OFF' is specified in the FMGUARD.SYS file, or no such a command specified at all, then NoFileMenu, NoDiskMenu, and other similar commands will not delete corresponding submenus from the menu bar (as it used to be in the previous versions), but will only make them 'grayed'. While maintaining the original function of these commands (preventing access to the submenus), this allows one to restore access to the submenus by means of the 'Guard-Disable' command (in the previous versions it was impossible to restore deleted submenus in this way). If you still want to actually delete the submenus, specify 'NoGrayedMenus=ON' in the FMGUARD.SYS; this will restore the original effect of the NoFileMenu and other similar commands. Note: the 'NoGrayedMenus' command has no effect on the NoGuardMenu command; if 'NoGuardMenu=ON' is pecified, the 'Guard' submenu is always removed from the menu bar, no matter what value of the 'NoGrayedMenus' command is. - bug fixed: "No results of the 'File-Search' command are shown if the 'NoDrive' command is used to restrict access to drive S:." Ver. 2.03: - New restricting command, 'NoExecute', is introduced, to be used in place of the old command 'NoOpen'. NoExecute prevents running executable files via double-clicking in File Manager, but allows using double-clicking to open documents. The NoOpen command may still be used to disable both running executables and opening documents via double-clicking. Ver. 2.00: - FM Guard now restricts not only File Manager, but some other Windows components as well. In this version the ability to prevent access to certain drives via Common Dialogs is implemented: any Windows application which uses Common Dialogs ("Open", "Save As", etc.) will not be able to access the drives specified with the 'NoDrive' command. - functionality of the commands removing submenus from the menu bar (NoFileMenu, etc.) is extended: they are now language independent; - new restricting commands are introduced: NoStepUpMenu, NoToolbarMenu, and NoGuardMenu, allowing one to remove the Chaosoft Utilities submenus from the menu bar while maintaining their functionality; - documentation updated; Ver. 1.2x: - documentation updated; - SETUP utility is included in the package; - bug(s) fixed: "The 'Disable' command does not turn off the 'NoDragDrop' restriction" "Undefined function AllocPtr in module CSL*.DLL" "Cannot open file FMGUARD.SYS if Windows is installed into the root directory" Ver. 1.0x: - documentation updated - password protection of the command 'Disable/Enable FM Guard'; - new restricting options added; Ver. 1.00: - initial release (on the basis of successful experience with FM StepUp). _________________________________________________________________ 1.3. THIS IS SHAREWARE: TRY BEFORE YOU BUY ! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This is NOT free or public domain software. This is SHAREWARE, i.e. copyrighted software which you can "try before you buy". You may try the program for the evaluation period of up to 21 days. After that time, you are required to purchase the software through registration or else discontinue its use. (please read the complete text of License agreement in LICENSE.TXT for details). This program is produced by a member of the Association of Shareware Professionals (ASP). ASP wants to make sure that the shareware principle works for you. If you are unable to resolve a shareware-related problem with an ASP member by contacting the member directly, ASP may be able to help. The ASP Ombudsman can help you resolve a dispute or problem with an ASP member, but does not provide technical support for members' products. Please write to the ASP Ombudsman at 545 Grover Road, Muskegon, MI 49442-9427 USA, FAX 616-788-2765 or send a CompuServe message via CompuServe Mail to ASP Ombudsman 70007,3536. _________________________________________________________________ 1.3.1. What is the difference between registered and unregistered versions of FM Guard? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Unregistered copies of our products are 100% fully functional. We make them this way so that you can have a real look at them, and then decide whether they fit your needs or not. The only difference is that the password required to disable FM Guard is fixed in the unregistered version (and it's displayed in the dialog box that asks you for it, so that you can completely evaluate the power of FM Guard, but anyone can easily disable it). Also, the NoGuardMenu command has no effect in the unregistered version. When you register FM Guard with us, you get a Registration Code, allowing you to use the NoGuardMenu command, set up your own password and turn the 'unregistered' password off. _________________________________________________________________ 1.3.2. WHAT DO YOU GET WHEN YOU REGISTER File Manager Guard ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. A personal Registration Code, allowing you to choose your own password (and change it as frequently as you want to) disabling/enabling FM Guard. 2. Disk with the latest version of FM Guard and other Chaosoft products. 3. The privilege to be personally informed about new major releases of FM Guard and other software products from ChaoSoft. 4. FREE upgrading to new versions of FM Guard released for the same or similar operating system (for the purposes of this offer we consider Windows for Workgroups 3.11 as similar to Windows 3.1, whereas Windows 95 or Windows NT are NOT similar to Windows 3.1) 5. FREE 90-days customer support through electronic or regular mail. _________________________________________________________________ 1.3.3. How to register FM Guard ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You may register your copy of FM Guard software with a credit card (Visa, MC, Amex, or Discover), personal check, money order, or cash. You may also register via CompuServe (GO SWREG, ID# 3858). You may even make use of the 'bill me later' option - there is no need to send money right now! Just run file REGISTER.EXE supplied with the FM Guard package and it will guide your through the registration process and will print an order form out for you! _________________________________________________________________ 1.3.4. How to order site license ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you would like to use FM Guard on a number of computers (stand alone or connected to a network), you must purchase a site license from ChaoSoft for that number of computers. Please use one of the order forms from the REGISTER.TXT file. _________________________________________________________________ 1.3.5. May I make a copy for a friend? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Sure! This is shareware, that means - share it! As long as the FM Guard package is complete and unmodified in any way, and you don't sell it, you may make copies of the software and give them to others, upload them to your favorite BBSes or FTP sites, etc. Please read file VENDINFO.DIZ for a complete list of our distribution requirements. /////////////////////////////////////////////////////////////// // // 2. Installing/uninstalling FM Guard // /////////////////////////////////////////////////////////////// Unlike most other Windows applications, FM Guard is not a stand-alone program; there is no special executable file you would run to start FM Guard. To use FM Guard, all you need is to properly install it, and it will run automatically every time you run the File Manager. FM Guard comes with convenient and flexible SETUP utility. Use SETUP when you want to temporarily activate/deactivate the software or install it onto your hard disk or network drive for permament use. Installing over an older version ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you are installing FM Guard on a computer which already has an older version of the program installed, you may use the SETUP program, however be sure not to overwrite your customized configuration file FMGUARD.SYS in the WINDOWS\SYSTEM directory. SETUP prompts you before it replaces any of the old files. After the copying of the new files is completed, you may add the new restricting commands (they are listed in the end of the 'fresh' FMGUARD.SYS file) to your customized FMGUARD.SYS file manually. Installing on a hard disk or network drive ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you have already copied all the files from the FM Guard package onto your hard disk (for instance, you have extracted the files from an archive), copy FMGUARD.SYS into the WINDOWS\SYSTEM directory, run SETUP.EXE and choose 'Activate' option. If you don't have FM Guard files on the hard disk, choose the 'Install' option instead. Then enter the DOS path to the directory where you want FM Guard to be installed. In this case, SETUP.EXE will copy all files to the new location and then activate them. In addition, you will be prompted to create a separate program group for FM Guard. It's not essential to have such a group, but it may be convenient. Alternatively, you may install FM Guard manually: 1. Create a directory on a hard disk or network drive for FM Guard, say C:\FMGUARD, and copy all the files from the FM Guard installation disk into that directory. If you have obtained FM Guard compressed in an archive, extract all the files into the FMGUARD directory (or other directory of your choice). 2. Close File Manager. 3. Copy the FMGUARD.SYS file into the WINDOWS\SYSTEM directory on your hard disk (be sure not to overwrite the newer version of this file if you already have one!). The directory may have another name in your system, but you can identify it by the presence of the files USER.EXE and GDI.EXE (Windows system files) in it. 4. Open file WINFILE.INI for editing (using Notepad or any other text editor). This file is located in the WINDOWS directory on your hard disk (or other directory you specified when installing Windows). Please note: the file you need is WINFILE.INI, not WIN.INI. Find the section [AddOns] in this file and add the following line to it: FM Guard=C:\FMGUARD\FMGUARD.DLL (or specify the directory in which you copied FM Guard files, if other than C:\FMGUARD). The resulting portion of WINFILE.INI should look like this: ... [AddOns] FM Guard=C:\FMGUARD\FMGUARD.DLL ... (... means other lines). If there is no [AddOns] section in you WINFILE.INI file, you may create one, adding the lines shown above to the end of the WINFILE.INI file. Save the WINFILE.INI file. 5. Run File Manager. You should find a new menu item, "Guard", among other items of the File Manager's main menu. If you cannot see the "Guard" item in the main menu of File Manager, an error has occurred. Please verify that you have done all the steps above, and, in particular, specified the correct path in the [AddOns] section of the WINFILE.INI file. Also, make sure that file FMGUARD.SYS has been copied in the WINDOWS\SYSTEM directory, and that other files have not been corrupted when copying them into the FMGUARD directory. Uninstalling FM Guard: ~~~~~~~~~~~~~~~~~~~~~~ To prevent File Manager from loading and using FM Guard, choose 'Guard -Disable' from main menu of File Manager, then run SETUP.EXE and choose 'Deactivate'. If you decide to start using FM Guard later on, run SETUP.EXE and choose 'Activate'. Alternatively, you may uninstall FM Guard manually: 1. Choose 'Guard' command from main menu of File Manager and then choose 'Disable' from popup menu. When prompted for the password, type it in the dialog box. If you have not registered FM Guard yet, use the word 'FMGuard' as the password. Otherwise, use the password assigned with the PASSWORD.EXE utility (see below). 2. Close File Manger. 3. Remove the line 'FM Guard=...' from the [AddOns] section of WINFILE.INI (using Notepad, for example). You may also wish to comment this line out instead, by placing a semicolon ';' as the very first character of the line After that you can restart File Manager: FM Guard will not be loaded. If you decide later to start using FM Guard again, restore the string 'FM Guard=...', specifying the complete DOS path to FMGUARD.DLL, in the [AddOns] section of WINFILE.INI. The following steps should be completed only if you wish to remove the FM Guard from your system permanently: 4. Delete all the files from the directory on your hard disk where you installed FM Guard; 5. Delete file FMGUARD.SYS from the WINDOWS\SYSTEM directory; //////////////////////////////////////////////////////////////// // // 3. Restricting Windows with FM Guard // //////////////////////////////////////////////////////////////// ________________________________________________________________ 3.1. General considerations ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When you run File Manager with FM Guard installed, the contents of the file FMGUARD.SYS in your WINDOWS\SYSTEM directory is analyzed to decide which features of File Manager and Windows to restrict. FM Guard is supplied with a sample FMGUARD.SYS file, specifying some 'reasonable' restrictions. You can change the file to make it suitable for your needs. If you need to temporarily disable FM Guard while File Manager is running, choose 'Guard' command from main menu of File Manager and then choose 'Disable' from pop-up menu. When a dialog box shows up, enter the valid password. If you are using an unregistered version of FM Guard, the password is the word 'FMGuard'. It is fixed and cannot be changed. If you have registered FM Guard with Chaosoft and obtained your personal Registration Code, you may use the PASSWORD.EXE utility to setup a password of your choice. To enable FM Guard again, you can either issue the command 'Guard' and then 'Enable' from menu, or just restart File Manager. Recommended actions for preparing to use FM Guard. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Before activating FM Guard, decide which disks and drives your users should have access to. You may want, for example, to assign a directory on your hard disk or network drive as the 'working' directory for all users (i.e. allow them to save their files in that directory only and prevent them from accessing all the other directories and disks). To do that, create a logical drive associated with the working directory using DOS command SUBST, and then make all the other drives unaccessible (by listing them in the 'NoDrive=' line of the FMGUARD.SYS file). For more information on the SUBST command please type 'help subst' at the DOS prompt. 2. Set up the desired configuration of Windows in the way you would want the user to see it when s/he initially runs it. It includes the position and size of the Program Manager and File Manager main windows, their secondary windows (displaying icons, files and directories), options, etc. IMPORTANT: make sure that none of the File Manager child windows shows a drive you wish to prevent access to, otherwise after activating FM Guard such a window will show no files! If the latter happens, select 'View-By File Type' from menu and make sure that the 'Name' field in the dialog box reads '*.*', without quotes. 3. Choose 'Options' from main menu of File Manager. Make sure 'Save Settings on Exit' is not selected. Then press SHIFT+ALT+F4 keys simultaneously to save the current configuration of File Manager in WINFILE.INI. Repeat the same for Program Manager to save its configuration in the PROGMAN.INI file. 4. Add 'winfile.exe' to the list of files loaded automatically on Windows start-up by changing the line 'load=' in the section [windows] of the WIN.INI file to read: [windows] ... load=winfile.exe ... This will run File Manager automatically on Windows start up and FM Guard will be activated before the user receives control from Windows. Otherwise the user would be able to uninstall FM Guard by modifying WINFILE.INI before running File Manager. CAUTION: don't assume that placing File Manager's icon into 'Start Up' group of Program Manager will have the same effect: if you don't add winfile.exe to the 'load=' line as described above, the user will be able to disable the loading of all programs from the 'Start Up' group by simply keeping the key 'Shift' depressed while Windows is initializing. 5. Setup restrictions for Program Manager and Control Panel, if you wish (please see appendixes A and B at the end of this file for more information). 6. Create a private directory on your hard disk, for instance, C:\PRIVATE, and copy WINFILE.INI, PROGMAN.INI, CONTROL.INI, and all the other files which you want to be used as the 'fresh copies' when Windows starts up, into that directory. 7. To prevent users from uninstalling FM Guard, add the following lines to the end of AUTOEXEC.BAT file in your root directory: ----------------- cut here ---------------- @echo off :StartWin copy C:\PRIVATE\*.* C:\WINDOWS > NULL win goto StartWin ----------------- cut here ---------------- The line '@echo off' will suppress echoing the rest of the commands on the screen while executing them. The line ':StartWin' is not a command, it's just a label to mark the beginning of the command sequence to be executed each time user restarts Windows. The line 'copy ...' will copy your previously saved, 'fresh' copies of WINFILE.INI, PROGMAN.INI, etc., from the PRIVATE directory into the WINDOWS directory, overwriting the existing files (just in case the user has changed them or removed the 'FM Guard=...' line from WINFILE.INI!). The line 'win' starts Windows. The user may then do his/her work as usual. If s/he decides to change WINFILE.INI and restart Windows, the next line, 'goto StartWin' will transfer the execution to the 'StartWin' line. The original WINFILE.INI file will be restored and all the changes the user might have made will be lost. This protects your system from uninstalling FM Guard. 8. Copy FMGUARD.SYS into WINDOWS\SYSTEM directory, if you have not done so already, and modify it, if necessary. You may wish to assign the 'read-only' and 'hidden file' attributes to the file. 9. If you want to setup different levels of restrictions for different users, you may wish to put the most restrictive options in the 'common' file FMGUARD.SYS, which is kept in the WINDOWS\SYSTEM directory. It will be used by FM Guard as the 'default' configuration file. If you want to provide more capabilities of File Manager for some of the users, you need to prepare additional, less restrictive configuration file, and put it into a local directory. To force FM Guard to use the additional, 'local' configuration file, you need to do two things: 1. Add the line 'ProcessLocalFile=ON' to the 'common' file FMGUARD.SYS (the one in the WIONDOWS\SYSTEM directory). If you turn this option off, by specifying 'ProcessLocalFile=OFF' in the FMGUARD.SYS file, no local configuration files will be processed. 2. Add the line 'fmguard=...' specifying the location of the local configuration file to the [windows] section of WIN.INI. For example, if you want FM Guard to process the file FMGLOCAL.SET, located in the '\USER\OPTIONS' subdirectory on the disk D, you have to add to following entry to the [windows] section of WIN.INI: fmguard=D:\USER\OPTIONS\FMGLOCAL.SET If FM Guard cannot find the local file, it allows File Manager to run as usual, without any error message. The 'common' set of restrictions, as specified by the WINDOWS\SYSTEM\FMGUARD.SYS file, will be in effect in this case. BE AWARE that any command you specify in the local configuration file suppresses the corresponding command in the 'common' file FMGUARD.SYS. BE SURE to delete (or even better, to comment out by placing a semicolon at the beginning of a line) all commands in the local configuration file, which you don't want to be overdidden. For example, if you want a single common password to be used to disable FM Guard on any machine, be sure to comment out the line 'Password=' in all local configuration files, otherwise they would suppress the password specified in the 'common' configuration file. 10.Make all the other necessary changes to the system (like making the entire directory WINDOWS\SYSTEM read-only). 11.Activate FM Guard by adding the line 'FM Guard=...' to the end of [AddOns] section in the WINFILE.INI file (see section 2 of this file for details). If you have other File Manager extensions installed (such as MSTOOLS.DLL from MicroSoft, or FMSTEPUP.DLL from ChaoSoft), make sure that you have no more than 4 (in case of Windows 3.1) or 5 of them (in case of Windows for Workgroups 3.11) listed in the [AddOns] section, including FM Guard. Save the file and restart Windows. That's it! _________________________________________________________________ 3.2. Configuring FM Guard using file FMGUARD.SYS ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ File FMGUARD.SYS contains commands specifying which features of File Manager to restrict. This file should be placed in the WINDOWS\SYSTEM directory (the directory containing Windows system files such as USER.EXE, GDI.EXE, etc.) If FM Guard cannot find FMGUARD.SYS in the SYSTEM directory, it displays an error message and closes File Manager (to prevent users from using File Manager in the unrestricted mode). The name FMGUARD.SYS is hardcoded into FM Guard and cannot be changed. The format of the FMGUARD.SYS file is ordinary ASCII, so that it can be edited using any text editor (like Windows Notepad). Don't use word processors to modify this file! (since they may add formatting codes to the text, that are unrecognizable by FM Guard). It's NOT required to put the title [restrictions] at the beginning of the FMGUARD.SYS file. For the list of available restricting commands and comments on their usage please refer to the sample file FMGUARD.SYS supplied with the FM Guard package. Each restricting command should be written in a single line. Each line of the file should contain no more than one command. If a line contains only 'white spaces' (any combination of SPACE and TAB characters), it's skipped without processing or warning. If the first 'non-white-space' character in the line is a semicolon ';' this line is considered as a comment and the rest of it is ignored by FM Guard. Otherwise the line is treated as a restricting command. Each restricting command should be written using the following syntax: command = value where 'command' is the name of the restricting command, and 'value' is it's value. Both the name of the command and the value can be surrounded by an arbitrary number of 'white spaces' (characters SPACE and TAB). Both the name and value are case insensitive, so that, for example, names 'NoClose', 'NOCLOSE', and 'noclose' are all valid names for the command defining the ability of the user to close File Manager. If the specified name of the command is not one of the predefined names, the entire line containing that name is ignored without error message. If a restricting command is deleted from FMGUARD.SYS or commented out, no warning is issued, and the corresponding feature of File Manager is restored to its default. Most of the restricting commands in the FMGUARD.SYS file are Boolean commands. The value of such a command can be one of the following: 1, ON, TRUE, or YES - to turn the restriction on, 0, OFF, FALSE, or NO - to turn the restriction off. For example, any of the following commands can be used to prevent the user from closing File Manager: NoClose = 1 or NoClose = ON or NoClose = True or NoClose = Yes Note: For all Boolean commands, setting them to 0, OFF, FALSE, NO will produce the same effect: enabling the corresponding feature of File Manager (the default, including when they do not appear in FMGUARD.SYS at all). There are also non-Boolean commands, such as NoDrive, UserName, Password. The values for these commands are the whole strings rather than Boolean triggers. Please see FMGUARD.SYS for a complete list of all the available commands and explanations of their use. _________________________________________________________________ 3.3. Using PASSWORD.EXE utility ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ After you register FM Guard and obtain your Registration Code from Chaosoft, you can use the PASSWORD.EXE utility to change the password required to disable/enable FM Guard on-line. Just run PASSWORD.EXE, and when the dialog box pops up, enter the name FM Guard is registered to (EXACTLY as it appears on your Registration Acknowledgment!), your Registration Code, and the new password. If the registration information is entered correctly, the dialog box will display a line that should be added to your FMGUARD.SYS file. It has the form: Password = where contains the password in an encoded form. You may wish to enter the new password again to verify that the resulting is the same. After you add the required 'Password =...' command to FMGUARD.SYS (in the SYSTEM directory!), the new password can be used to disable/enable FM Guard. _________________________________________________________________ 3.4. Restricting Common Dialogs ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Starting from version 2.00, FM Guard is able to restrict not only File Manager, but also other Windows components. As of this writing, FM Guard is able to restrict user access to certain disks via Common Dialogs ('Open', 'Save As', etc.). To employ this feature, the 'NoDrive' command in the FMGUARD.SYS file should be used. If you have already set this command up to prevent access to some drives via File Manager, no additional actions are required: access to these drives via Common Dialogs will be restricted automatically as well. IMPORTANT: the Common Dialogs restrictions are in effect only if File Manager (with FM Guard activated) is running. If you close File Manager, full access to the drives via Common Dialogs will be restored. If you want the Common Dialogs restrictions to be in effect all the time, it's a good idea to load File Manager when Windows starts up (by specifying WINFILE.EXE in the 'load=' line of the WIN.INI file) and use the 'NoClose=ON' command in the FMGUARD.SYS file. This will keep File Manager active for the duration of the whole Windows session. Please note that not all applications use Common Dialogs. In spite of the fact that using Common Dialogs is encouraged by Microsoft and is even required for an application to qualify for the 'Windows Compatible' logo, some of the software vendors (including Microsoft itself!) don't use them. As a result, some applications (including MS Word and Excel) cannot be restricted by FM Guard in this way. /////////////////////////////////////////////////////////////// // // 4. Getting updates to the software // /////////////////////////////////////////////////////////////// If file FMGUARD.DLL from your copy of FM Guard is three or more months old, then there probably is a newer version of the program and you may obtain it directly from us. Please use an order form from REGISTER.TXT file. Alternatively, you may use the following channels to get the latest version of FM Guard (search for file FMGRD*.ZIP): FTP: ftp.std.com, directory /vendors/ChaoSoft CIS: forum WINSHARE, LIB 2 (File Apps/Utils) AOL: keyword Windows, choose Windows forum -> Software Libraries -> Utilities -> File & Disk Management We also upload the program to other on-line services, BBSes, and FTP sites, including: FTP site Directory garbo.uwasa.fi /windows/util oak.oakland.edu /pub/msdos/windows3 ftp.cica.indiana.edu /pub/pc/win3/util wuarchive.wustl.edu /pub/MSDOS_UPLOADS/win If you are a registered user, we will notify you personally about new *major* releases of the program. /////////////////////////////////////////////////////////////// // // 5. Acknowledgements // /////////////////////////////////////////////////////////////// I would like to thank Gerald B. Collins for helping to prepare the documentation for this utility. /////////////////////////////////////////////////////////////// // // 6. Getting customer support // /////////////////////////////////////////////////////////////// Please check out the documentation to FM Guard, including files README.TXT and FMGUARD.SYS, before requesting support from Chaosoft. Otherwise, if you cannot find the answer in the documentation, or have a suggestion regarding FM Guard, we will be glad to hear from you. You can reach us through Internet sending e-mail to: 74634.2173@compuserve.com or directly via CIS Mail: 74634,2173 or you may write to us: Technical Support ChaoSoft P.O.Box 43 Old Town, ME 04468-0043 Thank you for using Chaosoft products! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ChaoSoft(tm) and ChaoSoft's logo are trademarks of ChaoSoft. Microsoft(R) and Windows(R) are registered trademarks of Microsoft Corporation. All other product names may be registered or unregistered trademarks / tradenames of their respective owners. _________________________________________________________________ Appendix A. Restricting Program Manager ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You may also wish to restrict Program Manager in addition to File Manager. Please note that the ability to restrict Program Manager is built-in into Windows and is NOT a feature of FM Guard. The information below is provided only for reference purposes for your convenience. If you have any questions about restricting Program Manager, you should contact the customer support department of Microsoft, NOT Chaosoft. The [restrictions] section of PROGMAN.INI is intended to allow system administrators to restrict access to certain Program Manager functions, the settings within the section can consist of the following: [restrictions] NoRun= NoClose= NoSaveSettings= NoFileMenu= EditLevel= Description of Settings: Entry Value ----------------------------------------------------------- NoRun = 1 Disables the Run command line on the File menu. The Run command will be dimmed on the File menu and the user will not be able to run applications from Program Manager unless the applications are set up as icons. NoClose = 1 Disables the Exit Windows command on the File menu. Users will not be able to quit Program Manager (and thus Windows, assuming Program Manager is set up as the Windows SHELL). The File/Exit Windows command and the Control menu/Close command are dimmed. ALT-F4 is also disabled. NoSaveSettings=1 Disables the Save Settings on Exit command on the Options menu. The Save Settings on Exit command will appear dimmed on the Options menu and any changes that the user makes to the arrangement of windows and icons will not be saved on exiting Windows. This setting overrides the SaveSettings= entry in the [settings] section of PROGMAN.INI. NoFileMenu = 1 Removes the File menu from Program Manager. All of the commands on that menu are then unavailable. Users can start applications by using icons. Windows may still be exited via the System Menu or ALT-F4. Note: For all the No* settings, setting them =0 enables them (the default, including when they do not appear in PROGMAN.INI at all) EditLevel = Sets restrictions for what settings and features users can modify in Program manager. 0 -- Any changes may be made (default). 1 -- Prevents user from creating, deleting, or renaming GROUPS. The New, Move, Copy, and Delete commands on the File menu are dimmed when a group is selected. 2 -- All restrictions of level 1, plus prevents creating or deleting PROGRAM Items. The New, Move, Copy, and Delete commands on the File menu are always dimmed. 3 -- All restrictions of level 2, plus prevents changing command lines for PROGRAM Items. The text in the Command Line box in the Properties dialog cannot be changed. 4 -- All restrictions of level 3, plus prevents ANY changes to PROGRAM Item information. Prevents changes in any of the areas of the Properties dialog, it still may be viewed, though all of the areas are dimmed. _________________________________________________________________ Appendix B. Restricting Control Panel ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Below are step-by-step instructions on entries that can be made in the CONTROL.INI file to limit access to specific icons in the Control Panel, such as 386 Enhanced, International, Printers, and so on. Please note that the ability to restrict Control Panel is built-in into Windows and is NOT a feature of FM Guard. The information below is provided only for reference purposes for your convenience. If you have any questions about restricting Control Panel, you should contact the customer support department of Microsoft, NOT Chaosoft. Add a section called [Don't Load] to the CONTROL.INI file, then type the name of the icon that you don't want to be shown. The section should look as follows; however, only add the name of the item you want to limit. Example of All the Icons Turned Off ----------------------------------- [Don't Load] Printers=1 Color=1 Fonts=1 Ports=1 Mouse=1 Desktop=1 keyboard=1 Printers=1 International=1 Date/Time=1 Network=1 386 Enhanced=1 Drivers=1 Sound=1 Example of All the Icons Turned On ---------------------------------- [Don't Load] Printers= Color= Fonts= Ports= Mouse= Desktop= keyboard= Printers= International= Date/Time= Network= 386 Enhanced= Drivers= Sound= A "0" or "1" after the "=" sign (without quotation marks) will disable that icon.