
     
                                   
                                   
                                   
     
                          Installation Guide
                                   
                                  DOS
                             Windows 3.1x
                              Windows 95
                              Windows NT
                                 OS/2
                            Novell NetWare
     
     
     
     
                                   
     All product names referenced herein are trademarks or registered
     trademarks of their respective companies. Data Fellows Ltd.
     disclaims proprietary interest in the marks and names of others.
     Although Data Fellows Ltd. makes every effort to ensure that this
     information is accurate, Data Fellows Ltd. will not be liable for
     any errors or omission of facts contained herein. Data Fellows
     Ltd. reserves the right to modify specifications cited in this
     document without prior notice.
     Companies, names, and data used in examples herein are fictitious
     unless otherwise noted. No part of this document may be
     reproduced or transmitted in any form or by any means, electronic
     or mechanical, for any purpose, without the express written
     permission of Data Fellows Ltd.
     Copyright  1995 Data Fellows Ltd. All rights reserved.
     September 1995

Table of Contents
1. General                                  1-1
2. What's in the package                    2-2
     2.1 F-PROT Professional for DOS & Windows2-2
     2.2 F-PROT Professional for Windows NT2-2
     2.3 F-PROT Professional for OS/2      2-3
     2.4 F-PROT Professional for NetWare   2-3
3. Quick start                              3-4
     3.1 F-PROT for DOS installation       3-4
     3.2 F-PROT for OS/2 16-bit installation3-4
     3.3 F-PROT for Windows or OS/2 standalone installation 3-4
4. F-PROT Professional for DOS installation 4-6
     4.1 Minimum configuration             4-6
     4.2 Installation on the hard disk     4-6
     4.3 Installation on a network        4-10
     4.4 Using INSTALL to reconfigure VIRSTOP4-13
5. Installing F-CHECK                      5-15
6. F-PROT for OS/2 16-bit installation     6-18
     6.1 Installing F-PROT for OS/2 16-bit on the local  hard disk
     6-18
     6.2 Creating an F-PROT for OS/2 icon on the desktop    6-18
7. F-PROT for Novell NetWare installation  7-19
     7.1 Installation prompts             7-19
8. F-PROT for Windows and OS/2 installation8-21
     8.1 Standalone installation          8-21
     8.2 Network installation             8-24
9. Updating                                9-27
     9.1 Updating F-PROT for DOS          9-27
     9.2 Updating F-PROT for OS/2 16-bit  9-27
     9.3 Updating F-CHECK                 9-27
     9.4 Updating F-PROT for NetWare      9-28
     9.5 Updating F-PROT for Windows  or OS/2 32-bit   9-28
     9.6 Updating just F-PROT Gatekeeper  9-29
10. Administering the network installation10-30
     10.1 Selecting the installation options10-31
     10.2 Communication and system management  in a network 10-31
     10.3 Creating a task base           10-34
     10.4 Modifying the toolbar          10-34
     10.5 Editing the preferences        10-34
     10.6 Creating an installation diskette or directory    10-36
     10.7 Adding tasks to the installation directory   10-38
     10.8 Updating F-PROT for Windows    10-38
11. AUTOINST                              11-40
     11.1 General                        11-40
     11.2 Invoking the program           11-40
     11.3 Installing the files           11-42
     11.4 Finding the local Windows directory11-43
     11.5 Administration features        11-44
     11.6 Forcing preferences            11-45
     11.7 Settings for AUTOINST          11-47
     11.8 Gatekeeper's preferences       11-48
     11.9 F-Agent                        11-49
     11.10 FPW                           11-50
     11.11 The Windows version of AUTOINST11-51
     11.12 Installing TSRs (VIRSTOP etc) 11-52
     
     
     
     General
     This Installation Guide contains installation instructions for
     all major F-PROT Professional versions.
     The guide starts with Quick Start, which is meant for those who
     are familiar with software installations in general. Quick Start
     describes how F-PROT can be installed as a standalone
     installation without network features.
     F-PROT Professional for DOS installation tells you how to install
     F-PROT for DOS to a standalone machine, and how to operate F-PROT
     from a network drive.
     The F-PROT Professional for OS/2 16-bit section covers the
     installation of the command line version of F-PROT for OS/2.
     F-PROT for NetWare describes the installation of F-PROT for
     NetWare to a workstation and from there to the network server.
     The F-PROT Professional for Windows and OS/2 section covers
     standalone and network installations for Windows 3.1x, Windows
     95, Windows NT and OS/2 32-bit F-PROT versions.
     The Autoinst section describes how AUTOINST can be used to
     installing and updating F-PROT automatically.

What's in the package

F-PROT Professional for DOS & Windows
     The basic F-PROT package of contains the DOS, Windows 3.1x and
     Windows 95 versions of the program.
     Documentation consists of the F-PROT Professional for DOS and
     Windows manual, License Agreement / Registration card and 3
     diskettes.
     F-PROT Professional for DOS
     -    F-PROT.EXE
     -    VIRSTOP.EXE
     -    F-CHECK.EXE
     -    F-TEST.COM
     -    F-AUTO.EXE
-    F-ARC.EXE
-    FIXBOOT.EXE
-    AUTOINST.EXE
     F-PROT Professional for Windows 3.1x
     -    F-PROT Professional for Windows 3.1x
     -    F-PROT Gatekeeper
-    F-Agent
-    AUTOINST.EXE
     F-PROT Professional for Windows 95
     -    F-PROT Professional for Windows 95
     -    F-Agent

F-PROT Professional for Windows NT
     The F-PROT Professional for Windows NT package contains F-PROT
     Professional for DOS and F-PROT Professional for Windows NT.
     Documentation consists of the F-PROT Professional for DOS and
     Windows NT manual, License Agreement / Registration card and 2
     diskettes.
     -    F-PROT Professional for DOS
     -    F-PROT Professional for Windows NT
-    F-Agent

F-PROT Professional for OS/2
     The F-PROT Professional for OS/2 package contains F-PROT
     Professional for DOS and F-PROT Professional for OS/2 (both 16-
     bit and 32-bit versions).
     Documentation consists of the F-PROT Professional for DOS and
     OS/2 manual, License Agreement / Registration card and 3
     diskettes.
     -    F-PROT Professional for DOS
     -    F-PROT Professional for OS/2 (32-bit)
-    F-PROT Professional for OS/2 (16-bit)
-    F-Agent

F-PROT Professional for NetWare
     The F-PROT Professional for NetWare package contains F-PROT
     Professional for DOS and F-PROT Professional for NetWare.
     Documentation consists of the F-PROT Professional for DOS and
     NetWare manual, License Agreement / Registration card and 2
     diskettes.
     -    F-PROT Professional for DOS
     -    F-PROT Professional for NetWare
     
     
     
     

Quick start

F-PROT for DOS installation
     1.   Boot your PC from a clean write protected system diskette. This is
       not absolutely necessary but it is a good safety measure when you
       install F-PROT Professional for DOS - the hard disk will be scanned for
       viruses at the end of the installation.
     2.   Insert the F-PROT for DOS diskette in drive A:
3.   Type A:\INSTALL <enter>
4.   Press <enter> to start installation with the default settings
     5.   Before the installation is complete you will be asked whether you
       want to change the message VIRSTOP displays whenever it intercepts a
       virus. Answer <Y> if you wish to enter a customized message. Write the
       message on the message line and press <enter>.
     6.   When installation is complete you will be asked whether you want
       to scan your hard disk immediately. We recommend that you allow your
       disks to be scanned.

F-PROT for OS/2 16-bit installation
     1.   Insert the F-PROT for OS/2 16-bit diskette in drive A:
     2.   Create a new directory for the program. A suitable directory is,
       for instance,
         C:\F-PROT
     Copy all the files on the installation diskette to this
     directory. The program is now ready for use.

F-PROT for Windows or OS/2 standalone installation
     To install F-PROT for Windows 3.1 or Windows NT
     1.   Start Windows 3.1x or Windows NT
     2.   Insert the installation diskette in drive A.
     3.   Choose the command Run from Program Manager's File menu.
     4.   Type A:\Setup and click OK.
5.   Follow the Setup instructions on the screen.
     To install F-PROT for Windows 95
     1.   Start Windows 95
     2.   Insert the installation diskette in drive A.
     3.   Choose the command Run from the Start menu.
     4.   Type A:\Setup and click OK
5.   Follow the Setup instructions on the screen.
     To install F-PROT for OS/2
     1.   Start OS/2 2.x or Warp
     2.   Insert the installation diskette in drive A.
     3.   Open the folder OS/2 System, Drives, Drive A: or click drive A: in
         the Launchpad (in Warp) or double-click the drive A: icon (in OS/2
         2.x).
     4.   Double-click SETUP.EXE
5.   Follow the Setup instructions on the screen.

F-PROT Professional for DOS installation

Minimum configuration
     F-PROT Professional takes up less than two megabytes of hard disk
     space. If even this poses a problem, some of the files can be
     omitted to save storage space. The files that are essential for
     the normal operation of F-PROT are:
         -    F-PROT.EXE
         -    SIGN.DEF
         -    ENGLISH.TX0 or some other TX0 language file
     If you choose to use this minimum configuration, you won't be
     able to change the program's language or view virus descriptions.
     The program will work normally in all other respects, however.
     In addition to these three files F-PROT will create a file called
     SETUP.F2 where it will store configuration information.

Installation on the hard disk
     1. Boot your PC from a clean write-protected diskette. This is
       not absolutely necessary but it is a good safety measure when
       you install F-PROT Professional for DOS - the hard disk will be
       scanned for viruses at the end of the installation.
     2. Insert the write-protected F-PROT Professional for DOS
       diskette into the appropriate drive and switch to that drive.
       The drive is usually drive A:
     3. Type INSTALL <enter>
     If the version you are installing has more than one available
     language, you will first be asked to specify the installation
     language. The installation program modifies VIRSTOP and F-PROT to
     use the selected language.
     
     Full installation requires about 1.5 MB of hard disk space.
     After you have selected the language, the main installation
     screen appears:
     This screen shows the command line switches that will be set when
     VIRSTOP is installed and running. VIRSTOP takes 4kB memory when
     used with the /DISK parameter and 38kB without it. If your PC is
     not short of memory, de-select /DISK by using the arrow keys to
     move to VIRSTOP and pressing <enter>. The installation program
     will then display the following screen: Press the space bar to
     toggle the switch setting to No, and <enter> to confirm the
     changes. Press <Esc> twice to get back to the main menu and move
     tothe Start installation option.
     Press <enter> to start installation.
     4. Before the installation is complete you'll be given the
       opportunity to change the message VIRSTOP displays whenever it
       intercepts a virus:
     
     Answer <Y> if you wish to enter a customized message and write
     the message on the message line. Press <enter>.
     5. When the installation is complete, you'll be shown the
       following message:
     
     We recommend that you type <Y>
     Once the hard disk has been scanned and found to be clean, the
     program displays the following message:
         No viruses or suspicious files/boot sectors were found
     F-PROT Professional is now installed on your computer.
     6. The virus interception program, VIRSTOP, can be activated at
       once by restarting the PC.
     To do this:
          Remove the diskette from drive A: and
          press <Ctrl> <Alt> <Del> simultaneously.
     From  now on, the background virus interceptor, VIRSTOP, will
     actively check program files and diskettes for viruses whenever
     you use them.
     If VIRSTOP finds a problem that might indicate a virus, it will
     display a message and a warning on the screen. Follow the
     programs advice. You can refer to F-PROT for DOS User's Guide
     Section 3.4 for further information.
     7. We recommend that you check that VIRSTOP is properly installed
       and working. To do this you need to run the program F-TEST from
       the F-PROT directory. F-TEST contains a test search string will
       be recognise. If VIRSTOP is functional, an attempt to execute
       F-TEST will result in the following message:
         VIRSTOP is installed and active.
     If VIRSTOP is not loaded or if it has been damaged, F-TEST will
     display the following warning:
         VIRSTOP is not installed or not working!
     If you receive this message, try the command line parameters
     /NOTRACE and /REHOOK or move the VIRSTOP command line to the end
     of AUTOEXEC.BAT or CONFIG.SYS. You can also reinstall VIRSTOP
     immediately by repeating the installation procedure.

Renaming F-PROT.EXE
     Since some viruses target specific antivirus programs by name,
     you may want to rename F-PROT.EXE. With the exception of
     PUT-MBBS.EXE, all executable files in the F-PROT package can be
     renamed. After renaming, they will continue working normally.

Installation on a network
     If the F-PROT Professional license bought by your company is a
     site license and you have a local area network, F-PROT
     Professional can be installed on the file server and
     workstations. When an updated version is released, it will be
     possible to update all copies from the network server.
     To install F-PROT Professional on the file server the system
     administrator needs to run the INSTALL program from the
     distribution diskette, as described in section 3.1.
     It is possible for workstations to run F-PROT Professional from
     the file server, but we recommend that workstations with local
     hard disks should run F-PROT Professional locally. That way,
     they'll have access to F-PROT even if they are not logged on to
     the server.
     After F-PROT Professional has been installed to the workstations,
     it may prove necessary to make changes to CONFIG.SYS or
     AUTOEXEC.BAT in order to find the correct place for loading
     VIRSTOP relative to the network drivers. See Section 4.3.3 for
     further details.

Installing F-PROT on local hard disks
     There are two utilities which can be used for automating the
     installation of F-PROT to the workstations. These are called
     AUTOINST.EXE and FPUPDATE.BAT. Both utilities can be used for
     installing and automatically updating F-PROT.
     The installation diskette contains the files AUTOINST.EXE and
     FPUPDATE.BAT. Either file can be placed on a shared disk, for
     example, Z:\LOGON and then run by adding the appropriate command
     to the LOGON script or batch file.
     Place AUTOINST.EXE and AUTOINST.INI or FPUPDATE.BAT in one
     subdirectory and the necessary F-PROT files plus UPDATE.INI to
     another subdirectory. Modify AUTOINST.INI or FPUPDATE.BAT  so
     that the source and destination paths are correct.
     Modify network logon batch or script to run AUTOINST or FPUPDATE
     every time a user logs in. Both utilities will check whether
     F-PROT Professional is installed on the local hard disk. If not,
     F-PROT Professional will be installed in the C:\F-PROT directory.
     If the program has already been installed, the utility will check
     the F-PROT Professional version number and update the program if
     necessary.
     Installation or updating will happen every time a user logs on as
     a network user. This way installation will happen automatically
     the first time a particular workstation logs on to the network.
     Subsequently, when an updated version of F-PROT Professional for
     DOS is copied to the network server, each workstation will
     automatically receive the updated version the next time the
     workstation logs on to the network.
     If you use FPUPDATE the version checking and updating is based on
     a file named VERSIO_n.nnn, where n.nnn stands for the version
     number of F-PROT. The source directory should contain only one
     such version file at a time.
     If you use AUTOINST the version checking and updating is based on
     a file named UPDATE.INI. This is an ASCII file which contains a
     date. As long as the UPDATE.INI files in the source directory and
     the destination directory contain the same dates, AUTOINST will
     not perform updating.
     FPUPDATE.BAT and AUTOINST.INI files can easily be modified by the
     system administrator. For example, if you want the workstations
     to scan their local hard disks whenever users log on to the
     network, you can handle the matter by adding the appropriate call
     to FP.BAT at the point indicated in FPUPDATE.BAT. Other
     modifications can be made to suit the paths in your system.

Installing F-PROT on the file server
     In the INSTALL program, it is possible to specify the
     installation type as Workstation. In that case VIRSTOP will
     remain active at all times, but F-PROT will not be copied to the
     local hard disk. You may wish to use this option if you are short
     of local disk space.
     The \F-PROT directory in the file server should be write-
     protected. This will make it impossible to save the default
     settings in this directory, so the environment variable FPSETUP
     should be set to point to another directory where the program
     keeps the SETUP.F2 file. This only applies if you wish to allow
     the users to change F-PROT settings. You can, for instance, add
     the following line to the AUTOEXEC.BAT in all workstations in the
     network.
         SET FPSETUP=C:\SETTINGS\SETUP.F2 <enter>
     This makes it possible to save personal settings for each
     workstation on the local hard disk and still load F-PROT from the
     file server. You can use whatever directory you wish instead of
     SETTING but it must be an existing directory.

Finding the correct place for VIRSTOP
     Depending on which method is used, installation of F-PROT
     Professional for DOS adds the VIRSTOP command line either to
     AUTOEXEC.BAT or CONFIG.SYS. With some network drivers, it may
     prove necessary to change the position of this command line. If
     your network uses Novell NetWare or IBM AS/400 see the network
     specific notes below. Otherwise, you can do a test installation.
     Reboot the workstation so that VIRSTOP becomes active. Run F-TEST
     to check that VIRSTOP is functioning properly. If you get the
     warning:
         VIRSTOP is not installed or not working!
     edit AUTOEXEC.BAT or CONFIG.SYS, moving the command line so that
     VIRSTOP is run after the network drivers.
     Network Specific Notes
     Novell NetWare:
        VIRSTOP has to be loaded after the NETX
        loader. If VIRSTOP is loaded before NETX, you
        must use the command VIRSTOP /REHOOK after NETX
     IBM AS/400:
        VIRSTOP has to be loaded from CONFIG.SYS
        using either DEVICE or DEVICEHIGH command. The
        correct loading order of drivers is:
     i.   DEVICE=DXMA0MOD.SYS,DXME0MOD.SYS,DXMT0MOD.SYS and other DXMA-
         drivers.
     ii.  DEVICE=VIRSTOP.EXE
iii. DEVICE=EIMPCS.SYS and also ECYDDX.SYS if it is needed.

Using INSTALL to reconfigure VIRSTOP
     The primary function of the INSTALL program is to install F-PROT
     Professional for DOS on the hard disk. However, INSTALL can also
     be used for changing the settings of the command line switches
     supported by VIRSTOP or the language used by VIRSTOP. These
     switches are explained in detail in Section 4.2.
     When INSTALL is run subsequent to the first time the following
     screen is displayed:
     The assumed installation type is Configure Setup. The active
     switches are listed alongside VIRSTOP.
     Select VIRSTOP to change the switch selection. The program will
     then display the following screen:
     Select the options you require and start installation. This will
     reconfigure VIRSTOP's setup with the switches you have selected.
     Use <space> to toggle settings and <enter> to confirm the
     changes.


     
     Installing F-CHECK
     After F-PROT has been installed, F-CHECK is copied to the same
     directory with F-PROT. F-CHECK can also be copied to the hard
     disk manually, but since both F-PROT and F-CHECK share the same
     language file, we recommend that they are installed together. You
     need at least F-CHECK.EXE, PUT-MBBS.EXE and one of the TX0
     language files to run the program. F-CHECK will create a setup
     file called SETUP.C2.
     Before you run F-CHECK, you should make sure that the system is
     clean. This can be done by booting the computer from a clean
     diskette and running F-PROT.
     The next step after the installation is to create a checksum
     database. This is done with the command:
         F-CHECK CREATE <enter>
     F-CHECK will create a checksum database file named _CHK.CHK
     unless you decide to change the name.
     The database can be protected by a password. This password will
     be requested when a check is executed and when the checksums are
     being updated.
     Files included in the check process can be split up into groups.
     The separation into groups speeds up daily checks without any
     significant loss of security. Since F-CHECK distributes the data
     on the hard disk evenly into different groups, the checking of
     one group will probably reveal a virus infection if there is one.
     The optimum number of groups depends on the overall number of
     files. We recommend that you use 5 groups with a 500 megabyte
     hard disk. Boot sectors, DOS hidden files, the command
     interpreter and F-CHECK itself are checked every time regardless
     of the division into groups. When programs have been added to the
     database, the groupings can be viewed by choosing the option List
     all files in database from F-CHECK's Maintain menu.
     The Main Menu of F-CHECK is now displayed:
     
     Installing F-CHECK in command line mode
     F-CHECK can also be run in command line mode.
         F-CHECK CREATE /DBFILE=SECRET.DAT
     creates the file SECRET.DAT by using the parameter
     /DBFILE=[name]. F-CHECK saves the database file name to SETUP.C2
     so you do not have to give it every time you use F-CHECK. If you
     decide to create several databases with different names, you
     should use the parameter /DBFILE= on the command line when
     starting F-CHECK. That way, you can be sure of which database to
     use.
     The command
         F-CHECK CREATE /PASSWORD=ANGELA
     creates the file _CHK.CHK with the password Angela. Once set, a
     password can be changed only by creating a new checksum file.
         F-CHECK CREATE /GROUP=5
     creates a database with the default file name and specifies that
     the data should be split into 5 groups.
     You can combine various command line options in the following
     way:
         F-CHECK CREATE /DBFILE=SECRET.DAT
         /PASSWORD=ANGELA /GROUP=5
     This command creates the database file automatically and returns
     to the command prompt without asking any questions.
     F-CHECK automatically adds checksum information of hard disk boot
     sectors, the command intepreter, DOS hidden system files and of
     F-CHECK itself to the database.
     After the checksum database has been created, the files that are
     to be included in the check list must be added to it. See the
     F-PROT for DOS User's Guide Section 3.9.2.

F-PROT for OS/2 16-bit installation

Installing F-PROT for OS/2 16-bit on the local  hard disk
     Since there is no installation program for F-PROT for OS/2, it
     must in all cases be installed manually.
     Create a new directory for the program. It can, for instance, be
         C:\F-PROT2
     Copy all the files on the installation diskette to this
     directory. The program is now ready for use.

Creating an F-PROT for OS/2 icon on the desktop
     After you have copied the program files to the computer's hard
     disk, you can enable F-PROT for OS/2 to be used directly from
     Desktop.
     Open the Templates folder on the Desktop by double-clicking it.
     Point the mouse at the Program template, press the right-hand
     button down, and drag the template to Desktop or to a selected
     folder. In the following dialog, enter the program's file name
     (F-PROT2.EXE with its directory path and the parameters you want
     to execute the program with - for example, /HARD for scanning the
     hard disk. See the F-PROT for OS/2 manual for other command line
     parameters. If you wish, you can define a working directory for
     F-PROT for OS/2. That is not required by the program, however.
     Open the Session settings by clicking the SESSION tab on the
     settings window. Remove the mark from the Close Window On Exit
     checkbox. If you leave the mark in place, the operating system
     will close the program's window before you have a chance to view
     the scan results.
     Open the General settings by clicking the tab GENERAL. Enter the
     program's name and close the window. The F-PROT for OS/2 icon
     appears on Desktop. The program can now be started by double-
     clicking the icon.

F-PROT for Novell NetWare installation
     This section will guide you through the installation of F-PROT
     for NetWare onto your network drive.
     Installation requires you to be logged in to your NetWare server
     with supervisory rights. You must choose the primary server drive
     that contains the \SYSTEM subdirectory and AUTOEXEC.NCF.
     Under DOS, switch to the drive that contains the F-PROT for
     NetWare distribution diskette and start the installation program.
     For example:
         C>A:
         A>INSTALL
     The installation program does the following:
     -    Creates a F-PROT for NetWare (NET-PROT) directory under the SYSTEM
         directory and copies the F-PROT for NetWare files to it. It also
         creates a directory to which infected files will be moved.
     -    Offers to modify your AUTOEXEC.NCF so that F-PROT for NetWare is
         loaded automatically when the server is booted.

Installation prompts
     Prompts help you select the drive to which of F-PROT for NetWare
     will be installed, and offer to modify your AUTOEXEC.NCF so that
     F-PROT for NetWare will be loaded automatically when the server
     is booted. Press <enter> after each command to install F-PROT for
     NetWare.
         Which drive is your network system drive?
     Select your network system drive (the one with the SYS volume)
     from the list of network drives. This will create a F-PROT for
     NetWare directory under the SYSTEM directory. The F-PROT for
     NetWare files will be copied to this directory. The installation
     also creates an INFECTED directory to which infected files will
     be moved.
         Would you like to modify your AUTOEXEC.NCF file to
         automatically execute F-PROT for NetWare when you load the
         server?
     If you want F-PROT for NetWare to be loaded automatically when
     the server is booted, select "Yes". The line "Load NET-PROT.NLM"
     will be added to your AUTOEXEC.NCF file.
     The installation program copies SETUP.EXE to the NET-PROT
     directory during the installation. SETUP can be used for changing
     the settings of F-PROT Professional for NetWare. SETUP can be run
     from a DOS prompt or directly from Windows.

F-PROT for Windows and OS/2 installation

Standalone installation
     To install F-PROT for Windows 3.1 or Windows NT
     1.   Start Windows 3.1x or Windows NT
     2.   Insert the installation diskette in drive A
     3.   Choose the command Run from Program Manager's File menu
     4.   Type A:\Setup and click OK
5.   Follow the Setup instructions on the screen.
     To install F-PROT for Windows 95
     1.   Start Windows 95
     2.   Insert the installation diskette in drive A
     3.   Choose the command Run from the Start menu
     4.   Type A:\Setup and click OK
5.   Follow the Setup instructions on the screen.
     To install F-PROT for OS/2
     1.   Start OS/2 2.x or Warp
     2.   Insert the installation diskette in drive A.
     3.   Open the Drive A: folder from the Launchpad (in Warp) or from the
         Drives folder
     4.   Double-click SETUP.EXE
5.   Follow the Setup instructions on the screen.
     After Setuphas initialised, you will see the following:
     
     If your computer is not connected to a network or if you do not
     want the network communication features installed, choose the
     Standalone option. You will still be able to run virus scans on
     the network drives in the single-user mode.
     
     You can choose to install both F-PROT Professional and F-PROT
     Gatekeeper or only F-PROT Gatekeeper. Select the directory to
     which you want to install F-PROT Professional. The default
     directories are F-PROTW, F-PROTNT and F-PROT95 under the Windows
     directory, or \F-PROT2G in OS/2. Leave at least the Enable F-PROT
     Gatekeeper option checked, so you'll have background protection
     active at all times. F-Agent is needed for scheduled F-PROT scans
     and it can also be used for changing F-PROT Gatekeeper's settings
     if needed.
     NOTE! F-PROT Gatekeeper is not available for all platforms.
     Choose Start Installation to install F-PROT Professional. You can
     quit the installation by choosing Exit. Cancel returns you to the
     previous screen.
     
     When the installation is otherwise complete, the program will ask
     your name, your organisation's name and your workstation's name.
     After you have entered them and clicked OK, the installation
     program will complete the installation and exit. If you included
     F-PROT Gatekeeper in the installation, the following message will
     be displayed:
     
     The F-PROT Professional program folder with icons for F-PROT
     Professional, Scan diskette in drive A: and Scan Hard Disk will
     be added to the desktop. If F-Agent was specified to be loaded at
     startup, setup will add its icon to the Startup group.

Network installation
     If your organisation's workstations are networked, F-PROT
     Professional should be installed by the network administrator
     using the Network option. After completing the Network
     installation, the administrator should prepare an AUTOINST
     configuration file for all the workstations in order to install
     F-PROT centrally to the workstations. The installations to
     workstations can also be made by preparing an installation
     directory and running SETUP. For further information, see section
     10. If you select the Network Administration Installation, the
     program displays the following screen:
     
     Choose the directory in which you want to install F-PROT
     Professional. The default directories are F-PROTW, F-PROTNT and
     F-PROT95 under Windows and \F-PROT2G under OS/2. You must
     establish a shared communication directory for F-PROT
     Professional users. The communication directory should locate on
     a shared drive so that all F-PROT users will be able to access
     it. Enter an administrator's password and leave the options
     Enable F-PROT Gatekeeper and Load F-Agent checked. We recommend
     that you endeavour to keep F-Agent active at all times - it runs
     the scheduled tasks, i.e. predefined scans, and notifies you of
     messages reveiced from other workstations..
     NOTE! F-PROT Gatekeeper is not available for all platforms.
     Choose Start Installation to install F-PROT Professional. You can
     quit the installation by choosing Exit. Cancel returns you to the
     previous screen.
     
     When the installation is otherwose complete, the program will ask
     your name, your organisation's name and your workstation's name.
     After you have entered them and clicked OK, the installation
     program will complete the installation and exit. If you have
     included F-PROT Gatekeeper in the installation the following
     message will be displayed:
     
     The F-PROT Professional program folder with icons for F-PROT
     Professional, Scan diskette in drive A: and Scan Hard Disk will
     be added to F-PROT folder. If F-Agent was specified to be loaded
     at startup, setup will add its icon to the Startup group.
     
     
     Updating

Updating F-PROT for DOS
     F-PROT Professional for DOS can be updated by running INSTALL.
     Read the section Updating From A Diskette.
     If F-PROT installation was initially done with FPUPDATE or
     AUTOINST, read Network Updating.
     Updating From a Diskette
     F-PROT Professional can be updated from a diskette by simply
     running INSTALL  from the installation diskette. INSTALL will
     copy the new files over the old ones.
     Network Updating
     New versions of F-PROT can be automatically updated to individual
     workstations through the network. Users don't even need to know
     that the updating takes place.
     If the initial installation has been done by using FPUPDATE or
     AUTOINST the F-PROT files should be copied from the installation
     diskette to the network installation source directory. If you use
     FPUPDATE for updating, you must remove all the old VERSIO_?.???
     version files from the source directory, and leave only the
     latest version file there. If you use AUTOINST, you must change
     the date inside UPDATE.INI in source directory to current date.
     When a user logs in to the network, both FPUPDATE and AUTOINST
     check automatically whether a new update is available and copy
     the new program version to the workstation.

Updating F-PROT for OS/2 16-bit
     Copy the new files from the installation diskette to your F-PROT2
     directory over the older files.

Updating F-CHECK
     F-CHECK is updated together with F-PROT Professional for DOS. It
     is also possible to update F-CHECK by copying F-CHECK.EXE,
     PUT-MBBS.EXE and the selected TX0 file over the older files.

Updating F-PROT for NetWare
     First, you must unload NET-PROT so that it will not keep any
     files open during installation. You can then run INSTALL from the
     installation diskette and install the new programs over the older
     version. Do not let INSTALL write over the existing configuration
     file when it asks about that, unless you really want to change
     the configuration.

Updating F-PROT for Windows
     or OS/2 32-bit
     If F-PROT Professional has been installed without network
     communication features, read the section Single User
     Installation. For remote installations or complete installations
     read the respective sections.
     Single User Installation
     You can update F-PROT by running SETUP from the installation
     diskette and selecting Update. If Gatekeeper has been installed,
     it will also be updated.
     If F-PROT has been installed to workstations by using AUTOINST,
     you must copy all the files from your F-PROT directory to the
     AUTOINST source directory and change the date inside UPDATE.INI
     in the source directory to current date. AUTOINST will update
     workstations automatically the next time they log in to the
     network provided that the AUTOINST command has been added to the
     network logon batch or script.
     Remote Installation
     Workstations must unload both F-PROT and F-Agent before F-PROT
     can be updated to the server. Updating cannot take place if the
     programs keep files open.
     Run SETUP from the installation diskette and select Update to
     update F-PROT that has originally been installed on a network
     drive.
     Nothing needs to be done in the workstations - they will
     automatically use the only installed copy of F-PROT.
     If both F-PROT Professional and F-PROT Gatekeeper have been
     installed, this update procedure will take care of updating F-
     PROT Gatekeeper also.
     Complete Installation
     If all workstations have their own copies of F-PROT, run SETUP
     from the installation diskette  and select Update to update your
     own workstation's F-PROT. After your program has been updated,
     select Send Update from the Administaration menu. This will copy
     all  the program files in your F-PROT directory to the UPDATE
     directory in the network communication directory. Remember that
     the update directory in Windows NT is UPDATE\WINNT_UP, in Windows
     95 it is UPDATE\WIN95_UP and in OS/2 it is UPDATE\OS2_UP.
     If both F-PROT Professional and F-PROT Gatekeeper have been
     installed, this update procedure will take care of updating F-
     PROT Gatekeeper also.

Updating just F-PROT Gatekeeper
     If you have done the initial installation from the installation
     diskette, run SETUP from the update diskette and select Update to
     update F-PROT Gatekeeper.
     If F-PROT Gatekeeper has been installed by using AUTOINST, you
     must first update your own F-PROT Gatekeeper and then copy the
     F-PROT Gatekeeper files to the AUTOINST source directory. Change
     the date inside UPDATE.INI in source directory to current date.
     The next time a user logs in to the network or runs  AUTOINST,
     AUTOINST updates F-PROT Gatekeeper files automatically to the
     workstation.
     
     
     Administering the network installation
     F-PROT Professional for Windows and OS/2 are primarily multi-user
     applications and need an administrator to keep them functioning
     smoothly. The program is automated to a great extent, but some
     jobs, such as updating and modifying the application, need human
     intervention.
     There is more to being the system administrator than just
     maintenance. You can determine how the program will actually
     function and how the system works when F-PROT Professional is
     installed on all workstations.
     First you must decide whether to do complete or remote
     installations to the workstations. Complete installation means
     that F-PROT is installed locally to all workstations. Remote
     installation means that only one installed copy of F-PROT exists
     in the network drive and all workstations run the same copy.
     You must first install F-PROT Professional as an administrator.
     You can then modify the program before you distribute it to
     users. The steps involved in setting up F-PROT Professional for
     your organisation are:
     1. Install the program on your own workstation
     If your computer is connected to network, the installation will
     also create the communication directory structures on the server
     disk.
     2. Create a task base.
     Add, remove, modify and schedule the tasks on your Task list to
     create a task base suitable for your organisation.
     3. Modify the Toolbar.
     Add, remove and modify the buttons on the Toolbar. The Toolbar
     should correspond to the task base and to the specific needs
     arising from your system.
     4. Modify the Preferences.
     Edit the Preferences so that they are suitable for users. Hide at
     least the Network and Administration Preferences.
     5. Create an installation diskette or directory.
     Use the Distribute F-PROT Installations function in the
     Administration menu to create a suitable installation diskette or
     directory. This will add your current tasks to the installation
     directory.
     6. Add tasks to the installation directory.
     Use the Distribute Task function in the Administration menu to
     add suitable tasks to the installation directory. You can protect
     these tasks from being edited or deleted.
     If you want to customise the program differently for different
     user groups, go over the steps 2 to 6 once for every
     customisation.
     The following table contains suggestions which can help you
     decide the best setup for your organisation. Take into account
     the resources of the server and workstation and the general level
     of user expertise.

Selecting the installation options
     The Situation  Suitable Option
The preferred        Install F-PROT Gatekeeper
installation.        or if not available,
                     F-PROT to run on
                     workstations. Let SETUP
                     create the Communication
                     Directory on the server.
There's a shortage   Install the program to
of disk space on     run on the server.
workstations.
The workstations do  Install the program to
not have hard        run on the server in the
drives.              single-user
                     configuration.
Network does not     Install the program to
exist.               run on workstations in
                     the single-user
                     configuration.

Communication and system management
     in a network
     Before installing the software on a network, you should
     understand how F-PROT communicates and what kinds of
     communication are possible.
     The program is not dependent on some specific brands of network
     software. Its communication system works as long as all the
     workstations in a network can treat a part of the server's hard
     disk as a shared logical disk. Practically all PC network systems
     support this, including Banyan Vines, IBM AS/400 PC Support, LAN
     Manager, LANtastic, Novell NetWare, Pathworks, PC LAN, PC-NFS and
     PC/TCP.
     What kinds of communication the program supports?
     F-PROT Professional is designed for communication between users
     and the administrator. This has been done on order to facilitate
     the administration and management of the F-PROT system. The
     program does not support communication between individual users -
     F-PROT Professional is an anti-virus software, not a forum or
     mail system application.
     Direct information exchange between the users and the
     administrator is made possible in the form of messages and
     bulletins. Messages are notes the users can send to the
     administrator. Bulletins are general announcements you can send
     to all users at the same time.
     You can send tasks to user workstations through the network. This
     feature can be used for developing uniform scanning practices for
     the organisation and for designing and distributing scans
     targeted at specific threats, such as new viruses. When the
     distributed tasks are no longer needed, they can be removed from
     the system simultaneously.
     The results of tasks can be set to be sent from user workstations
     to your own, along with any infected files found by F-PROT.
     F-PROT Professional allows you to automatically update the
     program across the network. When you install a new version to the
     server, the program will be updated in all workstations connected
     to the network.
     The Communication Method
     When F-PROT is installed, the communication structures are
     created in a directory on the shared drive.
     When you send an update to users, it is copied to the shared
     drive. F-PROT on user workstations will copy the new files from
     the communication directory to the appropriate F-PROT directories
     on local hard disks.
     Likewise, when F-PROT on a user workstation sends files to the
     shared directory, your program will copy them to the appropriate
     local F-PROT directory.
     Access Rights
     F-PROT Professional creates the Communication Directory and
     associated subdirectories on a shared drive.
     
     You need read and write access rights to all the directories.
     User access to these directories can be limited to prevent them
     from accidentally corrupting the F-PROT communication system.
     Suggested access right are:
     Directory      Suggested Access Rights
     Communication Directory  Read and Write Access Rights
     BULLETIN       Read Access Rights
     INFECT         Write Access Rights
     MESSAGES       Write Access Rights
     REPORTS        Write Access Rights
     SUSPECT        Write Access Rights
     TASK           Read Access Rights
     UPDATE         Read Access Rights
     UPDATE\WIN95_UPRead Access Rights
     UPDATE\WINNT_UPRead Access Rights
     UPDATE\OS2_UP  Read Access Rights
     Access rights policies are necessarily different in different
     networks. Here, "write access" means that any user can also
     create new files and delete files that have created by the user
     himself or any other user.
     Users must have both read and write access rights to the
     Communication Directory to enable the communication system to
     function. The directory contains the file COMM.INF, which keeps
     track of the files transferred over the network.
     More information about the various directories can be found in
     the F-PROT for Windows and OS/2 Manual, section Files and
     Directories.

Creating a task base
     You can create the task base by modifying the Task list of your
     own program. The tasks can be modified, added, removed and
     scheduled as described in the F-PROT Manual.
     You must think about the needs of your organisation and study the
     F-PROT Manual to find out the available options. Decide what
     kinds of tasks are required and whether they should be scheduled.
     Your current tasks will be copied to the installation directory
     and they will become the base tasks of users. You can create more
     tasks suitable for yourself after the workstation installation is
     done.
     Users are able to modify or delete tasks unless you protect the
     task base from modifications by setting appropriate restrictions
     in preferences. You can also disable modifications to tasks if
     you use the Distribute Task function from the Administration
     menu.

Modifying the toolbar
     The toolbar buttons should correspond to the task base you have
     created, as well as to the specific needs of your organisation.
     Ideally, the users should need only the toolbar to manage their
     own copies of F-PROT Professional for Windows. While this is not
     always possible, the most often needed functions should be linked
     to the toolbar. Your current toolbar will become the base toolbar
     for users. You can modify your own toolbar to suit your own needs
     after the workstation installation is done.

Editing the preferences
     Before you distribute the program to users, you can edit the
     Preferences to be suitable for them. Instructions on how the
     different Preferences affect the program and how they can be
     modified can be found in the F-PROT for Windows and OS/2 Manual,
     section 5.3 Setting Up Preferences.
     However, there are four Preferences not mentioned in the F-PROT
     Manual: Restrictions, Updating, Network and Administration.
     In the Restriction preference you can prevent user from seeing
     the program main window. Then they still can start scans from the
     program's desktop icons. You can also disable the modification of
     tasks and scanning the network.
     In the Update preference it is possible to specify whether the
     programs on workstations should be updated automatically or after
     asking permission to start the update process.
     In the Network Preference, you can see the name of the F-PROT
     WorkGroup.
     
     If you check Inform Administrator with Results, F-PROT will send
     the task results from local workstations directly to you.
     Similarly any infected files found in local workstations can be
     sent to you. In this Preference you can also change F-Agent's
     polling frequency.
     In the Administration Preference, there are three general
     settings:
     Enable Network Usage. If this is not selected, all network
     related functions will be disabled.
     Ask Workstation Prefs on First Startup. If this is checked, the
     program will ask the workstation and user IDs the first time it
     is started. F-PROT will not start until this information is
     entered.
     Administration Workstation. This is used for defining whether or
     not the workstation is the administration workstation.
     
     You can hide Preferences from users. If a Preference is hidden,
     it means that the users cannot edit it, and the choices you have
     made will stay in force. You should hide at least the Network and
     Administration Preferences.
     The Administration Preference is also used for changing the
     Administrator's password. You will need to know the current
     password in order to change it.

Creating an installation diskette or directory
     It is generally advisable for you to perform the installation to
     workstations, either from a diskette or from a shared directory
     in the network. However you can distribute the system for
     installation and let the end users carry out the actual
     installation.
     Standalone Installation
     If F-PROT is going to be used on standalone systems and has to be
     installed from a diskette, run first a standalone installation on
     your PC, set up any tasks you want to make available to the
     users, and create a distribution diskette by selecting Distribute
     F-PROT Installations command from the Administration menu.
     1.   Perform a standalone installation
     2.   Do the desired modifications to the task settings, toolbar and
       preferences
     3.   Make a copy of the installation diskette
     4.   Select the Distribute F-PROT Installations command from the
       Administration menu. Choose  By Modifying the Installation Directory
       and select the diskette from the file dialog
     Workstation installations can then be done by running SETUP from
     the prepared installation diskette.
     Complete installation from a SETUP directory
     If the workstations are connected to a network, you can start by
     doing a Complete Installation with Administration functionality
     on your own workstation and establish a suitable shared
     directory. After that, copy all the files from the installation
     diskette to an empty directory on the server. Set up any tasks
     you want to have available on the workstations and use the
     Distribute F-PROT Installations function to copy the
     configuration and task files to the same location. The
     workstations can then run the SETUP program from that shared
     location.
     1.   Perform a Complete installation with the network functionality
       enabled
     2.   Do the desired modifications to the task settings, toolbar and
       preferences
     3.   Create an installation directory on the server
4.   Copy the contents of the installation diskette to that directory
     5.   Select Distribute F-PROT Installations from the Administration
       menu, choose  By Modifying the Installation Directory and select the
       installation directory from the file dialog
     Workstation installatiosn can then be done by running SETUP from
     the prepared installation directory.
     Complete installation from an AUTOINST directory
     If the workstations are connected to a network, you can start by
     doing a Complete Installation with Administration functionality
     on your own workstation and establish a suitable shared
     directory. Set up any tasks you want to make available to the
     users, and use the Distribute F-PROT Installations function to
     copy all necessary files to an installation directory. The
     workstations can then run the AUTOINST program from that shared
     location.
     1.   Perform a Complete installation with the network functionality
       enabled
     2.   Do the desired modifications to the task settings, toolbar and
       preferences
     3.   Select Distribute F-PROT Installations from the Administration
       menu, choose  By Creating Installation Directory for Autoinst and
       select the installation directory in the file dialog.
     F-PROT will create the installation directory and copy
     AUTOINST.EXE and AUTOINST.INI there. Workstation installations
     can then be done by running AUTOINST from the prepared
     installation directory.

Adding tasks to the installation directory
     You can use the Distribute Task function in the Administration
     menu to set up tasks and send them to the distribution directory.
     Refer to F-PROT for Windows and OS/2 Manual section 10.2
     Distributing Tasks Through the Network for further details.

Updating F-PROT for Windows
     The easiest way to update F-PROT Professional is via the network.
     The best way to handle updating is to first update your own
     program and use it as the source, as the updating function uses
     the F-PROT root directory as the source directory.
     Updating Your Own Program
     The easiest way to update a new version to your own workstation,
     or to the server if F-PROT is installed to run there, is to
     update it from the new installation diskette. Use the Update
     installation option. The installation will replace the old
     program files on your hard disk, and you can use those files when
     you send the update to users. If the program is installed to run
     on the server, the individual workstations do not hold programs
     that would need to be updated. Make sure that there aren't any
     active users of F-PROT at the time, for the update procedure
     cannot copy the necessary files if they are open.
     Sending Updates To Users
     After you have installed a new version to your own workstation,
     you can send it to users via the network. This can be done by
     choosing the Send Update option from the Administration menu. The
     program will copy all files and directories under the F-PROT root
     directory to the UPDATE directory on the shared disk.
     
     When you send an update to users, all programs installed under
     the F-PROT root directory will be copied to the shared disk. If
     you have installed programs like F-CHECK or F-PROT for DOS into
     their own directories under the root directory, they will also be
     copied to the local workstations. As you can see, you can use
     this feature to update or distribute programs which are unrelated
     to F-PROT Professional for Windows.
     On workstations F-PROT will check the UPDATE directory when it is
     started. If a new version has become available, it will update
     itself. If the UPDATE directory contains other programs, F-PROT
     Professional for Windows will copy them to the local hard disk as
     well. Refer to F-PROT for Windows and OS/2 Manual section 11.2,
     Files and Directories on the Network Server, for further details
     of how the F-PROT update process is executed.

AUTOINST

General
     AUTOINST is a utility program that enables system administrators
     to have any version of F-PROT installed or updated automatically
     on workstations that log on to a network. The workstations
     normally call a login batch script (LOGIN.BAT, for instance) when
     they log on to the network. This script is modified to invoke
     AUTOINST. AUTOINST then performs the installation according to
     the instructions listed in its parameter file.
     The administrator must place the program files and configuration
     files on a network drive; Autoinst will copy them to local
     workstations and make the necessary changes to the users' WIN.INI
     and  SYSTEM.INI files. It will also take care of the necessary
     registrations. AUTOINST also handles updating and uninstallation,
     and can be used for changing the configuration (preferences) in
     workstations throughout the network.
     Please note that these instructions apply to DOS and Windows
     3.1x.
     Security issues:
     -    AUTOINST and its initialisation file should be write protected by
         the administrator so that workstations will have only read access to
         them.
     -    The source directory should be write protected by the
         administrator.
     -    AUTOINST is checksum-protected, which means that it can detect all
         changes to its own code.

Invoking the program
     The installation parameters for AUTOINST are stored in an
     inifile. The file's name can be specified on the command line:
         AUTOINST [switches] [inifile]
     If no name is specified, AUTOINST will use the file AUTOINST.INI
     located in the same subdirectory. Throughout this document,
     AUTOINST's inifile will be referred to as AUTOINST.INI.
     There are five sample INI files in the AUTOINST directory under
     the F-PROT directory. An INI file for installing F-PROT
     Gatekeeper (COLO.INI) might look like this:
     ; This INI file for AUTOINST can be used for installing F-PROT
     Gatekeeper
     ; locally to workstations. Communication between F-PROT
     Gatekeeper
     ; and F-PROT Professional for Windows is installed.
     ;
     ; Modify drive letters and directories to suit your system.
     ;
     ; Sections [Administration] and [F-Agent] are not needed if F-
     PROT
     ; Professional for Windows is already installed at users'
     workstations.
     [Autoinst]
     ShowErrorMessages=1
     ShowProgress=0
     ContactAdmin=AUTOINST error! Please contact your network
     administrator!
     StopAtExit=0
     NoVersionInfoDisplay=0
     WindowMode=0
     WindowTitle=F-PROT Gatekeeper Installation
     WriteAtStartup=
     WriteAtStartup=Performing F-PROT Gatekeeper Automatic
     Installation...
     WriteAtStartup=
     WriteAtInstall=Installing F-PROT Gatekeeper files on your hard
     drive,
     WriteAtInstall=please wait while the files are being copied...
     WriteAtInstall=
     WriteAtExit=F-PROT for Gatekeeper installation is complete.
     WriteAtExit=
     WriteAtExit=If you experience any problems, contact your network
     admistrator!
     WriteAtExit=
     [Local]
     WindowsDirectory=C:\WINWG
     WindowsDirectory=C:\WINDOWS
     WindowsDirectory=C:\WIN3
     WindowsDirectory=C:\WIN31
     WindowsDirectory=C:\WFW
     [Install]
     SoftwareID=FPW
     InstallFrom=V:\F-PROTW\SOURCE
     InstallToWin=F-PROTW
     [Administration]
     AdministrationEnabled=
     CommunicationDirectory=V:\F-PROTW\COMM
     UserName=%USER%
     WorkstationName=%USER%'s PC
     [Preferences]
     LastChange=95-03-22
     [Gatekeeper]
     Enable=Always
     AccessSettings=1
     [F-Agent]
     Load=Always

Installing the files
     The [Install] section of AUTOINST.INI specifies the source
     directory (the directory on a network drive from which the files
     will be copied) and the destination directory (the directory on a
     local drive where the files will be installed), eg:
         [Install]
         InstallFrom=V:\GATEKEEP
         InstallTo=C:\WINDOWS\GATEKEEP
     Alternatively, "InstallToWin" can be used instead of "InstallTo".
     It specifies a destination path relative to the user's Windows
     directory, e.g.:
         InstallToWin=GATEKEEP
     This will install the program files to C:\WINDOWS\GATEKEEP if the
     workstation's Windows directory is C:\WINDOWS. If both
     "InstallTo=" and "InstallToWin=" are specified, "InstallTo=" will
     be used.
     If the destination directory does not exist, it will be created.
     The source directory should be write-protected by the
     administrator.
     If the "InstallFrom=" entry is not present or if it is left
     empty, no error message will be produced. If it is not empty, an
     error message will be produced if the specified directory does
     not exist, or if the specified destination directory is invalid
     (does not exist and creation fails).
     AUTOINST does would not necessarily have to copy files from the
     source to the destination directory each time it is invoked. The
     administrator can create a file named UPDATE.INI in the source
     directory and write the following entry:
         [LastChange]
         LastChange=YY-MM-DD
     This specifies the creation date or last change date of the
     source files. AUTOINST will copy UPDATE.INI to the destination
     directory; therefore, the UPDATE.INIs in both the source and
     destination directories will be identical after the installation.
     When AUTOINST gets invoked again, it will perform the copying
     only if the dates in the source and destination directories'
     UPDATE.INIs don't match (or if either of them is missing, of
     course).
     AUTOINST can also be used for remote installations. In such
     installations, AUTOINST will not copy the files from a network
     drive to a local drive: the installed application will be run
     straight from the network drive. In order to change inifiles
     appropriately, AUTOINST has to know where the application
     resides; the location is specified in the [Install] section as
     e.g.:
         InstallRemote=V:\GATEKEEP
     "InstallFrom=" takes precedence over "InstallRemote=".
     "InstallTo=" and "InstallToWin=" will be ignored if
     "InstallFrom=" is not given.
     For keeping track of installed software, AUTOINST will store the
     installed software's ID and location in the [DFAPPS] section of
     user's WIN.INI, e.g.:
         [DFAPPS]
         FPW=C:\WINDOWS\GATEKEEP
     AUTOINST assumes that either F-PROT or Gatekeeper or both are
     installed. If you wish to install other software, you should
     specify its ID in the [Install] section, as e.g.:
         SoftwareID=MySoftware
     No entry will be written to WIN.INI if a "null" software ID is
     specified:
         SoftwareID=0
     IMPORTANT: Do NOT use a different ID when you install Gatekeeper
     or FPW;
     Either set "SoftwareID=FPW", or leave the "SoftwareID=" entry
     out.

Finding the local Windows directory
     AUTOINST will normally have to alter the workstation's local
     WIN.INI and SYSTEM.INI files; for that, it needs to know the
     location of the workstation's Windows directory. The
     "WindowsDirectory=" entry in the [Local] section of AUTOINST.INI
     will determine that. It is possible that different PCs in the
     network keep their Windows directories in different locations, so
     multiple paths may be given, e.g.:
         [Local]
         WindowsDirectory=C:\WINDOWS
         WindowsDirectory=C:\WINWG
     AUTOINST will search these paths for certain Windows files to
     make sure which path is the proper Windows directory, if any.

Administration features
     Note that none of the settings here will have any effect if the
     preferences are not otherwise changed.
     Gatekeeper and/or FPW can be set up in a networked environment so
     that information about infected files will be sent to the
     administrator (in FPW, there are also other admin-user
     communication features, see the documentation for FPW). However,
     this works only if the communication directory has been
     established on a shared drive. The administrator will have to
     properly install F-PROT on his system to set up the
     communications directory and to manage the information.
     Once this has been done, the administrator can specify the
     communication parameters in the [Administration] section of
     AUTOINST.INI, as e.g.:
         [Administration]
         AdministrationEnabled=1
         CommunicationDirectory=V:\GATEKEEP\SHARED
         SpoolDirectory=C:\WINDOWS\GATEKEEP\SHARED
         UserName=%USER%
         WorkstationName=%USER%'s PC
     The rest of the settings in the [Administration] section will
     only take effect if the "AdministrationEnabled=" entry has a
     value that is other than zero.
     The "UserName=" and "WorkstationName=" entries specify the names
     of the environment variables that hold the user and workstation
     names for the local workstation, respectively. The administrator
     needs these names in order to identify the infected computer:
     upon finding an infected file, Gatekeeper (FPW) will send a
     message to the administrator, including the user and workstation
     names in the message. AUTOINST will fetch the values of the
     specified environment variables and store them in F-PROTW.CFG.
     The environment variables must be entered between the "%"
     characters; the rest of the text will be stored in F-PROTW.CFG as
     given.
     The user and workstation names can also be obtained from the
     initialisation files instead of from the environment variables.
     The "UserNameFromIni=" and "WorkstationNameFromIni=" entries can
     be specified for this purpose. The syntax of these entries is
     "inifile|section|entry". For example, if the entry
         UserNameFromIni=C:\TOOLS\PCTCP\PCTCP.INI|pctcp general|full-
         name
     means that the user name can be obtained from
     C:\TOOLS\PCTCP\PCTCP.INI, from the "full-name=" entry in the
     [pctcp general] section. If the full pathname of the
     initialisation file is not specified, it is assumed that the file
     is in the user's Windows directory.
     Note: Upon activation, Gatekeeper will prompt for user for the
     username and workstation name in case one of them is not
     specified, if administration has been enabled.
     All these parameters are actually stored in the FPW and
     Gatekeeper configuration file, F-PROTW.CFG. AUTOINST will simply
     take the values specified in AUTOINST.INI, perform the
     substitutions of environment variables, and store them in
     F-PROTW.CFG.
     If administration is to be enabled, AUTOINST will create an
     appropriate subdirectory structure on the local workstation.
     Gatekeeper and FPW will use these directories as a temporary
     storage locationbefore the data gets sent to the shared directory
     created by the administrator. These subdirectories will be
     created under the directory specified in the "SpoolDirectory="
     entry.
     If no such entry is present, a directory named "SHARED" under the
     program files directory will be used. The directories created
     under the specified directory are:
     INFECT   (used for storing infected files)
     REPORTS  (used for storing reports and messages)
     SUSPECT  (used for storing suspectedly infected files)
     The "SpoolDirectory=" entry should always be specified if remote
     installations are made, AUTOINST will give an error message if
     the entry is not present with a remote installation.
     If administration is to be enabled, AUTOINST will make the
     following changes to the settings of the installed FPW: (1)
     Enable network features,
     (2) Switch to user mode, (3) Disable single installation setting.

Forcing preferences
     The settings for FPW and Gatekeeper are stored mainly in
     F-PROTW.CFG, and partially in some other files, such as
     DFAPPS.INI and F-PROTW.INI.
     AUTOINST will copy the files from the directory given in the
     "PreferencesFrom=" entry in the [Preferences] section to the
     local workstation's Windows directory, but the files previously
     residing there will not be overwritten. This ensures that the
     changes users have made to the settings will be retained. For
     example:
         [Preferences]
         PreferencesFrom=V:\GATEKEEP\USERS
     The administrator may thereby create different configurations for
     different user groups by specifying different AUTOINST.INI
     configuration files with pointers to different preferences
     directories.
     If the "PreferencesFrom=" entry is not specified, the following
     files, if present, will be copied from the directory specified in
     the "InstallFrom=" (or "InstallRemote=", if applicable) entry of
     the [Install] section: F-PROTW.CFG, F-PROTW.INI, DFAPPS.INI.
     The administrator may force certain settings to be set to certain
     values each time AUTOINST is run. This is done by specifying
     these values in the [Preferences] section of AUTOINST.INI. The
     entry format is:
         set=filename|section|entry|value
     <filename> refers to a file in the local workstation's Windows
     directory. Note that this feature also enables system
     administrators to change settings in files like WIN.INI,
     SYSTEM.INI etc.
     The administrator can specify that the changes to preferences are
     to be made only at certain times. This is done by adding the
     entry
         LastChange=YY-MM-DD
     in the [Preferences] section. The specified date will be written
     into WIN.INI as
         [DFAPPS]
         SOFTWARE_ID|PrefsLastChange=YY-MM-DD
     If AUTOINST is run, and the respective dates in AUTOINST.INI and
     WIN.INI match, no changes will be made to the settings. If the
     "LastChange=" entry is not present, the changes will be made
     every time.
     AUTOINST can be used for adding groups to Program Manager. To do
     that, the administrator has to prepare a groupfile and store it
     in a directory specified in the "PreferencesFrom=" entry:
     AUTOINST will then copy it to the user's Windows directory. To
     add this group to Program Manager's groups, the administrator has
     to write its name in an "AddGroup=" entry in the [Preference]
     section, as eg
         AddGroup=F-PROTW.GRP
     Certain initialization files, such as F-PROTW.CFG, are encrypted
     to prevent users from changing the settings manually. AUTOINST
     decrypts such files before making changes there, and re-encrypt
     them afterwards.

Settings for AUTOINST
     The [Autoinst] section of AUTOINST.INI specifies the settings for
     the AUTOINST program itself:
         [Autoinst]
         ShowErrorMessages=1
         ContactAdmin=Please contact your network administrators!
         ShowProgress=1
     The "ShowErrorMessages=" entry specifies whether AUTOINST should
     show error messages when it encounters problems with creating
     directories, copying files etc. In an error, AUTOINST displays a
     message describing the error, along with the text specified in
     the "ContactAdmin=" entry.
     The "ShowProgress=" entry determines whether AUTOINST will
     display information about its actions (copying files etc).
     The "ErrorIfNoWinDir=" entry specifies whether an error message
     will be shown if no Windows directory is found; the default value
     is 1.
     The "InstallIfWinOnly=" entry specifies whether the software
     should be installed always, or only if Windows is found on the
     system.  The default value is "0" (always install). Any
     combination of the following values may be used, separated by
     spaces, eg "InstallIfWinOnly=Win31 Win95":
     Win31 _ install if Windows 3.1x installed
         Win95 _ install if Windows 95 installed
         WinNT _ install if Windows NT installed
     With any other value except "0", installation will be made if any
     version of Windows is found.
     The "InstallIfWinOnly=" entry specifies whether the software
     should be installed always, or only if the Windows directory is
     found in the system;
         the default value is 0.
     The "StopAtExit=" entry specifies whether AUTOINST will stop
     execution after performing all its actions; the default value is
     0. If the entry value is not zero, AUTOINST will stop and show
     the message:
         "AUTOINST has terminated. Press ENTER to continue."
     AUTOINST can be forced to show special messages, specified in the
     inifile. Texts specified in "WriteAtStartup=" entries will be
     shown at startup; texts specified in "WriteAtInstall=" entries
     will be shown before program files are copied; texts specified in
     "WriteAtExit=" entries will be shown at the end. Multiple entries
     may be written, the messages get shown in the order of appearance
     in the inifile; empty lines will be shown for empty entries will
     be shown as empty lines.
     If "WriteAtExit=" is specified, the default exit message in will
     not be shown.
     If the "NoVersionInfoDisplay=" entry is set to zero, no copyright
     and version information for AUTOINST will be shown.

Gatekeeper's preferences
     The administrator may force some of the Gatekeeper's preferences
     to be set in the [Gatekeeper] section of AUTOINST.INI. The
     settings that are not specified there will retain the values
     stored in F-PROTW.CFG.
     Note that none of the settings here will have any effect if the
     preferences are not otherwise changed.
     Enabling Gatekeeper
     The "Enable=" entry determines whether Gatekeeper will be enabled
     upon Windows startup. If Gatekeeper is to be enabled, AUTOINST
     will add A-PROT.EXE to the "RUN=" line of WIN.INI and add the
     line "device=d:\path\F-PROTW.386" to the [386Enh] section of
     SYSTEM.INI. If Gatekeeper is not to be enabled, AUTOINST will
     make sure these changes are removed from WIN.INI and SYSTEM.INI.
     The following options are available:
         "Enable=Always" will always enable Gatekeeper
         "Enable=Never" will always disable Gatekeeper
         "Enable=OnInstall" will enable Gatekeeper only if an
         installation is performed (see section [3] about intallation
         and updating).
         "Enable=OnUpdate" will enable Gatekeeper only if an
         installation or update is performed.
         "Enable=NotOnInstall" will disable Gatekeeper only if an
         installation is performed.
         "Enable=NotOnUpdate" will disable Gatekeeper only if an
         installation or update is performed.
     NOTE: AUTOINST assumes that an update is being performed if any
     files exist in the destination ("InstallTo=" or "InstallToWin=")
     directory.
     Uninstalling Gatekeeper
     AUTOINST can also be used for uninstalling the software: if
     "Uninstall=1" has been specified, AUTOINST will remove all the
     Gatekeeper's files from the local workstations. It will also
     remove references to Gatekeeper from WIN.INI and SYSTEM.INI
     files.
     The "Uninstall=" option has precedence over other options: if it
     has been specified, the other options will be ignored.
     Other options
     The "AccessSettings=" entry specifies whether the user can access
     the Gatekeeper Settings dialog to enable/disable Gatekeeper or
     otherwise change its settings.
     The "ConfirmDosSessionKill=" and "ConfirmWinDenyAccess=" entries
     will specify the values for the respective settings.
     The "F-PROTw.386=" entry can be used for specifying an
     alternative path to the device driver. If the "F-PROTW.386="
     entry has been specified, the "device=" entry written into
     SYSTEM.INI will not determine the installation destination, but
     the entry will be written exactly as specified in this entry.
     This enables the VxD to be loaded from a different location than
     the rest of Gatekeeper. Example:
         F-PROTw.386=c:\F-PROTw.386
     An appropriate entry will also be written to F-PROTW.INI: F-Agent
     will use it when it enables Gatekeeper.

F-Agent
     Note that none of the settings here will have any effect if the
     preferences are not otherwise changed.
     The "Load=" entry in the [F-Agent] section determines whether F-
     Agent will be loaded upon Windows startup. WIN.INI will be
     appropriately changed.
     As with enabling Gatekeeper (see section [8]), there are six
     options:
         "Always", "Never", "OnInstall", "OnUpdate", "NotOnInstall",
         "NotOnUpdate".

FPW
     The settings for F-PROT for Windows 3.1, 95, NT and OS/2 Warp are
     specified in the [FPW] section. Note that none of the settings
     here will have any effect if the preferences are not otherwise
     changed.
     If "Uninstall=1" is specified, AUTOINST will remove all the FPW's
     files from the local workstations, and remove references to these
     files from the workstations' WIN.INI and SYSTEM.INI files .
     The "LocalDirectory=" entry specifies the root of FPW's local
     data directories. These directories are used for storing task
     files, reports, bulletins and other items. If no
     "LocalDirectory=" entry is present and if FPW is installed, a
     directory named "LOCAL" under the program files directory will be
     used. The data directories created under the specified directory
     are:
         -    BULLETIN
         -    INFECT
-    MESSAGES
-    REPORTS
-    REPUSER
-    SUSPECT
-    TASKS
     The "LocalDirectory=" entry should always be specified when
     remote installations are made, because the user's data files must
     reside on the local workstation. AUTOINST will give an error
     message if it cannot find the entry during a remote installation.
     Note: AUTOINST will assume that FPW is being installed if the
     Software ID is "FPW" (the default value). Therefore, the local
     data directories will be created even if Gatekeeper is installed
     without FPW.
     The "TasksFrom=" entry specifies the directory from which the
     task files are copied during the installation of FPW. Since the
     tasks must be in sync with a user's F-PROTW.CFG, these tasks may
     not be copied over previously installed tasks. Therefore, they
     will be copied only if there are no tasks in the local
     workstation's tasks directory.
     If the "LocalDirectory=" entry is missing and if the local
     programs directory is unknown, the tasks will not be copied
     because AUTOINST does not know the location of the local tasks
     directory.
     The Windows version of Autoinst supports the creation of a
     Program Manager groupfile for F-PROT for Windows. The parameters
     for the group to be created are given in the [FPW] section:
     The "GroupName=" entry specifies the name of the Program Manager
     group to be created or updated, eg
         GroupName=F-PROT for Windows
     The "IconX=" entries specify the program items to be created or
     updated: X denotes a number from 0 to 15. The entries have the
     format:
         IconX=ICON_TYPE, DRIVE_ID, TASK_NAME, ICON_TITLE
     ICON_TYPE can be one of the following:
         0  : start F-PROT for Windows
         1  : start F-Agent
         2  : execute a task with FPW
     DRIVE_ID specifies the drive to be scanned by the task (0==A:,
     1==B etc); it is used only if ICON_TYPE is 2. If the target
     system does not have the specified drive, the icon will not be
     created (this feature has not been implemented yet). 1000 denotes
     "All HDDs", 1001 denotes "All Network Drives".
     TASK_NAME specifies the name of the task to be launched when the
     icon is doubleclicked; it is used only if the ICON_TYPE is 2.
     ICON_TITLE is the text that appears below the icon in Program
     Manager.
     An example of the group parameters:
         GroupName=F-PROT Professional for Windows
         Icon0=0,0,0,F-PROT for Windows
         Icon1=2,0,scana.fpt,Scan Drive A:
         Icon2=2,1,scanb.fpt,Scan Drive B:
         Icon3=2,1000,scanallh.fpt,Scan All Hard Drives
         Icon4=2,1001,scannetw.fpt,Scan Network

The Windows version of AUTOINST
     Aside from the following exceptions, the Windows version of
     AUTOINST behaves exactly, and accepts the same parameters.
     The "WindowMode=" entry in the [Autoinst] section determines the
     visibility of the AUTOINST window:
         0   : The window is shown normally (the default)
         1   : The window is shown minimized (iconized)
         2   : The window will not be shown
     In any case, the window will be shown is an error occurs, or if a
     stop at exit is required.
     The local Windows directory is obtained from Windows; the
     "WindowsDirectory=" entries in the [Local] section will be
     ignored.
     If FPW/Gatekeeper is being installed (ie, the software ID is
     "F-PROT for Windows"), F-PROT for Windows, F-Agent and Gatekeeper
     will be unloaded upon installation. After the installation, F-
     Agent and Gatekeeper will be reloaded.
     The title (on the caption) of the AUTOINST window can be
     specified in the "WindowTitle=" entry of the [Autoinst] section.
     If it is not given, the window will be titled "AUTOINST".

Installing TSRs (VIRSTOP etc)
     The [TSRLoad] section specifies the load options of TSR programs
     like VIRSTOP. These programs can be installed on a workstation
     with AUTOINST like any other software.
     The "ID=" entry defines the program's identifier. This identifier
     will be used in subsequent entries for specifying the load
     options for that program. Multiple TSRs may be installed by using
     multiple "ID=" entries and their options. Example:
         [TSRLoad]
         ID=VIRSTOP
     The "<id>=" entry (where <id> stands for the ID as defined by the
     "ID=" entry) specifies the name of the TSR's program file, eg:
         VIRSTOP=virstop.exe
     Neither the drive nor the path need to be specified, since they
     will be determined by the location of installation, as specified
     in the [Install] section. However, full pathname may be given
     here if the installation of a file already present on the system
     is desired. In any case, an error will occur if the file is not
     found in the system.
     This entry is required; an error will occur if it is not present.
     The "<id>|LoadFrom=" entry specifies the full pathname of the
     file from which the TSR is loaded (this file will hereafter be
     called "load file"), eg:
         VIRSTOP|LoadFrom=C:\AUTOEXEC.BAT
     The specified file should already exist; otherwise, an error will
     occur.
     This entry is required; error will occur if it is not present.
     The "<id>|LoadPos=" entry specifies the position of the TSR's
     load command inside the load file. The following options are
     available:
     BeginFile:     the command will be written at the beginning of
                     the file (default)
     EndFile:       the command will be written at the end of the
                     file
     LineNumber,<n>:the command will be inserted before line number
                     <n>, negative line numbers denote lines from the
                     end of file (-1 for the last line, -2 for the
                     previous etc)
     RelativeToLineWith, <increment>, <substring>:
                     the command will be inserted <increment> lines
                     after the first line containing <substring>;
                     <increment> may be negative for inserting the
                     command before the line
     BeforeLineWith, <substring>:
                     same as "RelativeToLineWith, -1, <substring>"
     AfterLineWith, <substring>:   same as "RelativeToLineWith, 1,
                     <substring>"
     For example, the following entry will cause the command to be
     written immediately before the line with "win.com":
         VIRSTOP|LoadPos=RelativeToLineWith, -1, win.com
     The <substring> parameter is case insensitive.
     The "<id>|LoadPrefix=" entry, if present, causes a string to be
     inserted before the command. It is useful for making drivers to
     be loaded from CONFIG.SYS, or for specifying the LOADHIGH option.
     Examples:
         VIRSTOP|LoadPrefix="LH "
         VIRSTOP|LoadPrefix="device="
     Note that the quotation marks are required. The prefix will be
     inserted immediately before the command without any spaces in
     between.
     The "<id>|LoadSuffix=" entry, if present, causes a string to be
     appended to the command. It is useful for specifying load options
     for programs, eg:
         VIRSTOP|LoadSuffix=" /COPY"
     Note that the quotation marks are required. The suffix will be
     appended to the command immediately without any spaces in
     between.
     The "<id>|ReplaceOption=" entry specifies what action should be
     taken if there already is a command that loads the executable
     specified in the "<id>=" entry. The following options are
     available:
     RetainOld:     the old command will always be retained, no
                     change will be made to the load file
     RetainOldIfSame:    the old command will be retained only if it
                     exactly matches the new command (same paths,
                     prefixes and suffixes)
     ReplaceOld:    the old command will always be replaced
     The default is "RetainOldIfSame=".
     Note that unless the "<id>|ReplaceAtOldPos=" entry is present and
     its value is other than zero, the new command will not
     necessarily be placed at the same position as the old: the new
     position will be determined by the "<id>|LoadPos=" entry.
     The "<id>|ReplaceAtOldPos=" entry, if not zero, will force the
     new command to be inserted at the location of an old command if
     such an old command exists in the load file. In that case, the
     "<id>|LoadPos=" entry will be ignored.
     
  
