Contents

1. Introduction

1.1 Setup
1.2 The update wizard
1.3 Specially for Windows NT/2000/XP: the update service

2. Setup for Windows (initial installation)

2.1 Command line parameters of Setup
2.2 The file SETUP.INF (autom. update installation)
2.3 The commands in SETUP.INF

3. The Intranet update wizard

3.1 General
3.2 Configuration of clients
3.3 The control files

3.3.1 The file SETUP.VER
3.3.2 The file SETUP.FU1
3.3.3 The file SETUP.FU2
3.3.4 The file SETUP.ADM

3.4 Tree structure of the update wizard (Windows 95 and greater)
3.5 Installation of updates
3.6 Advice on problems

---

1. Introduction

1.1 Setup

1.2 The update wizard

1.3 Specially for Windows NT/2000/XP: the update service

2. Setup for Windows (installation)

For this purpose, generate a text file with the name SETUP.INF (you will find an example in the \DISK_1\ADMIN directory of the relevant program package on the CD-ROM). In this file, you can enter all the settings you would normally enter yourself via dialog boxes in the Setup program. 

To start the Setup program with this control file, you need to load Setup with the parameter /INF or incorporate it in your login script as follows: 

SETUP /INFC:\AVWIN/DISK_1/ADMIN/SETUP.INF

The reason for this peculiarity of Setup for AVWin/31 is as follows: 
if you incorporate the Setup program in the login script of Novell, for example, you may not be able to start the Setup program on logging in as you have not yet reached the DOS level. 

With the program PATCHINI.EXE (directory \DISK_1\ADMIN), you can insert the command "load=c:\avwin\setup.exe" in the "[Windows]" section of the file WIN.INI. 

PatchINI /A c:\windows\win.ini [Windows] load=c:\avwin\disk_1\setup.exe

Next time you start Windows 3.1x, the program SETUP.EXE will now be loaded, the script processed and AVWin/31 installed. The script of the 3.1 version allows you to start an application after successful installation, e.g. in order to delete the command "load=..." again: 

PatchINI /D c:\windows\win.ini [Windows] load=c:\avwin\disk_1\setup.exe

2.1 Command line parameters of Setup

The Setup programm is started with the specified command script. In this case, Setup does not display any dialog boxes, but takes all the required parameters from this file instead. Please note that, under Windows 3.1, you must copy the file SETUP.INF to the same directory as the Setup program. Example: 

SETUP /INFC:\AVWIN/DISK_1/ADMIN/SETUP.INF

If you select this parameter, the system files MSVCRT.DLL and MSVC40.DLL will never be replaced on your system. This can be useful if an older version of these files happens to be indispensable to other programs on the target computer. For example: 

SETUP.EXE /NOSYSFILES

2.2 The file SETUP.INF

SETUP /INFe:\disks\setup.inf

2.3 The commands in SETUP.INF

ReadmeNew=1/0

This allows the user to view the file README.NEW containing the latest information. 1 = display file, 0 = do not display file. The default value is 1. Example: 

ReadmeNew=1

This parameter enables you to activate or deactivate the virus scan on all local disks before the actual setup routine. 1 = Activate, 0 = Deactivate. The default value is 1. Example: 

Scan=0

This parameter can be used to prevent the scan activated with Scan=1 from being cancelled by the user. 0 = Cancelling not allowed, 1 = Cancelling allowed. The default value is 1. Example: 

CancelScanAllowed=0

This parameter defines the source path of the directory for the 1st floppy disk (DISK_1). This path entry MUST end in "DISK_1", All other disk images must have the same name as DISK_1, but ending in the number of the relevant disk. The simplest solution is to copy all disk directories from the relevant product directory on the CD-ROM. This parameter must be included! Example: 

SourcePathDisk1=\\SERVERNAME\Vol\INST\AVWINNT\DISK_1

This must be used to enter the target path on the target computer. This parameter must be entered in the script! Example: 

DestinationPath=C:\Programme\AVWinNT

This parameter specifies whether or not only new files are to be installed. This is useful when installing over an existing AntiVir. When this function is activated (1), the following rule applies: if an older version of a file exists on the local computer , it will be overwritten. If the same or a more recent version of this file exists on the local computer, it will not be reinstalled.  When this function is deactivated (i.e. parameter set to 0), the user is asked how to proceed if the file to be copied already exists on the hard disk and version information is already available. The default value is 1. Example: 

OnlyNewFiles=1

This allows you to specify whether or not Setup is to create an AntiVir/NT program group. 1 = Generate program group, 0 = Do not generate program group. The default value is 1. Example: 

AVGroup=1

This parameter specifies whether Setup is to overwrite an existing installation logfile SETUP.LOG or append it to the existing file. 0 = Append, 1 = Generate new logfile. The default value is 1. Example: 

OverwriteLog=1

The shell extension of AntiVir/NT is logged on in the registry and allows you to scan a file or folder for viruses in the Explorer using the right mouse key. This extension is only operational from Windows 95 and ab  Windows NT 4.0 onwards! 0 = Do not log on, 1 = Log on. The default value is 1. Example: 

ShellExtension=1

This parameter enables you to specify whether or not Setup is to install the resident virus shield AVGuard. If the shield already exists and you specify "do not install" here, it will be uninstalled. 0 = Do not install AVGuard, 1 = Install AVGuard. The current default value is 0 for Windows NT and 1 for Windows 9x. Example: 

Guard=0

The update wizard is required for the automatic installation of updates. With this parameter, you can specify whether or not you wish to install the wizard. 0 =  Do not install, 1 = Install. The default value is 1. Example: 

UpdateWizard=1

This enables you to specify whether the user at the local PC should be able to cancel the installation routine or whether the whole thing should take place automatically. 0 = Do not allow cancellation by user, 1 = Allow cancellation. The default value is 1. Example: 

CancelCopyAllowed=0

With this parameter, you can specify whether or not a licence file is to be transferred during installation. This parameter only applies in conjunction with "KeyFilePath". 0 = Do not transfer licence file, 1 = Transfer licence file. The default value is 1. Example: 

CopyKeyFile=0

This allows you to specify the location of the licence file to be copied. This should normally be a directory on the server. By default, the path of the directory "A:\" is assumed. Example: 

KeyFilePath=\\SERVERNAME\Vol\INST\AVWINNT\LICENSE\

This enables you to specify whether or not Setup is to create an icon on the desktop. This icon represents a link to the AntiVir program file. This function is only operational under Windows 95 and higher, and from Windows NT 4.0 onwards. 0 = Do not create link 1 = Create link. The default value is 1. Example: 

DesktopIcon=1

This parameter states the name of the icon to be created on the desktop. This parameter is only permitted in conjunction with "DesktopIcon". The following characters may not be included in the name: \ / : * ? " < > | . This function is only operational under Windows 95 and higher and from Windows NT 4.0 onwards. By default, the name "AntiVir NT" is used under NT and "AntiVir 9x" under Windows 9x. If you change this default setting, Unsetup will be unable to find this icon and it will remain on the desktop once you have uninstalled the program. Example: 

NameOfDesktopIcon=AntiVir NT

This enables you to specify whether or not the file README is to be displayed during installation. 0 = Do not display, 1 = Display README. The default value is 1. Example: 

ShowReadMe=0

This parameter enables you to specify the name of an executable file to be executed after successful installation. You can copy a ready-made configuration file of AVWin here, for example, or even make changes to the INI file with PATCHINI.EXE. By default, no file is executed. Example: 

ExeName1=c:\winnt40\system32\command.com /c copy c:\avwinnt.ini c:\avwinnt

This parameter enables you to specify whether or not the local computer is to be restarted automatically after installation (if necessary). 0 = Do not restart automatically, 1 = Reboot automatically. The default value is 1. Example: 

RestartWindows=0

Here you can enter the fully qualified path to a predefined INI file to be automatically transferred during installation. This allows the administrator to create a configuration locally and then transfer it to his users' computers, for example. By default, the search for an INI file is omitted. Example: 

IniFile=\\SERVERNAME\DATEN\AVWINNT\AVWINNT.INI

With this parameter, you can retain the configuration of an existing installation in terms of the components to be installed. In other words, if you have entered '0' here, the old components are retained, particularly in relation to AVGuard. If you have entered a '1', only the instructions in SETUP.INF are executed regardless of the components or programs already installed. 1 = Retain old components, 0 = Install according to SETUP.INF only. The default setting is 1. Example: 

KeepOldSettings=0

(Under Windows 9x only) With this parameter, the command line scanner AVE32 is entered in the AUTOEXEC.BAT, so that the hard disk is scanned once for viruses each time you start the computer. 1 = Enter AVE32, 0 = Do not enter AVE32. The default value is 0. Example: 

AddAVE32ToAutoexec=1

(Under Windows 9x only) With this parameter, you can enter AntiVir in the menu of the File Manager. 1 = Enter, 0 = Do not enter. The default value is 1. Example 

FileManager=1

---

3. The Intranet update wizard (autom. update installation)

3.1 General

The Intranet update wizard has been fully revised in version 1.11 of AntiVir/Win and is now equipped with script capability. This means that you can make various settings in a control file which are then processed by the wizard. The binary SETUP.DAT previously used has now been replaced by the text-based control file SETUP.VER. Besides the version information of the files, this also contains the installation instructions for the wizard and for the resident virus shield AVGuard. Please note that the wizard needs to have been installed with Setup for this purpose (this takes place automatically on the default setting anyway). Another new feature is the fact that the Wizard is no longer started by the main program AVWINxx.EXE, but via the RUN key of the Windows registry: 

(HKEY_LOCAC_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\AVWUpd32)

This means that the wizard is started briefly every time a user logs in, and checks, depending on the chosen settings, whether a version comparison needs to be performed. Unfortunately, we were compelled to install the new Wizard in two stages. This means that, when the (old) wizard is first called, it only copies and installs the files of the new one and, if applicable, the files of the update service. After a restart, the new functions are available and the next wizard operation uses the new control file SETUP.VER. This next operation can be delayed by several days, however, depending on the chosen update interval. In order to force the wizard to start immediately, you should delete the file DATETIME.INI from the start directory of AntiVir, e.g. via a DELETE command in the login script. This tells the update wizard that an update has not yet been performed and should be initiated immediately. The command in the file DATETIME.INI is automatically re-entered and updated by the wizard.

3.2 Configuration of clients

In order to use the wizard, you must configure it first for each client. To do this, start AntiVir and select the register card "Intranet Update" under "Options". 

Activate the wizard here by specifying how frequently it is to search for new files. We recommend an interval of between one and seven days, depending on the relevant FUP level. For the actual comparison, only the appropriate control files are loaded from the server (unless an update has to be performed). These range from 0.5 (SETUP.FU3) to 14KB (SETUP.VER) in size, and do not therefore burden the network unnecessarily. 

In the next field, you should specify the path to the update directory \DISK_1 on the server, e.g. \\SERVSERNAME\VOLUME\UPDATES\AVWINNT\DISK_1.  Please note that different path entries are required (logically enough!) for different operating systems. 

In the next field, you can enter the path to a directory on the server via which the new licence files are to be distributed. In other words, if the update wizard finds a new licence file (internal creation date) in the specified directory, it will automatically be installed first and used for the subsequent update routine. This method thus provides an easy way of changing the FUP level. 

Now click on OK and close AntiVir. At the next system start, the wizard will automatically check the target directory for new software and will then install it if appropriate. Please make sure that the environment TEMP (or TMP) refers to a valid local directory with sufficient free capacity. Alternatively, you can also transfer a predefined INI file to each workstation as part of the installation process. 

3.3 The control files

3.3.1 The file SETUP.VER

3.3.2 The file SETUP.FU1

2.3.3 The file SETUP.FU2

3.3.4 The file SETUP.ADM

INSTALLGUARD=TRUE

This determines whether or not the AVGuard of the relevant application is to be installed. TRUE = Install, FALSE = Do not install. This causes the settings of the file SETUP.VER to be overwritten.

This parameter specifies whether the update wizard is to be installed. The default value is TRUE. You should always leave this setting on TRUE, otherwise you will no longer be able to perform automatic updates.TRUE = Install, FALSE = Do not install. This causes the settings of the file SETUP.VER to be overwritten.

This parameter determines whether the update wizard is to retain the previously installed parts of the program on the target computer or whether the program should proceed according to the presettings of SETUP.VER/SETUP.ADM. In other words, if TRUE is selected here and the Guard is not already installed on the target computer, it will still not be installed if the relevant parameter INSTALLGUARD is also set to TRUE (default setting) in SETUP.ADM. If FALSE is selected, the settings on the target computer are ignored and only the settings in SETUP.ADM are used. The Guard may also be uninstalled if appropriate.

This parameter (optional) specifies the basic directory for new licence files on the server.

This parameter specifies a new INI file to be transferred containing the applicable settings for AntiVir. (Optional)

If you set this value to FALSE, the system files MSVCRT.DLL and MSVC40.DLL will never be replaced by the files supplied on the CD-ROM. This can be useful if you are using software for which the Dll's contained in the system are indispensable. In most cases, AntiVir should still work with the old Dll's.

This is the absolute "mega-parameter" of SETUP.ADM. If you set this value to TRUE, the Intranet update wizard will update your software after every version comparison and without exception!! FORCEUPDATE has a higher priority than all other parameters, and should therefore be used with the utmost care!

3.4 Tree structure of the update wizard

Server
  |
  +-- ANTIVIR --+-- AVWINNT -----+-- DISK_1\SETUP.VER
  |             |                +-- DISK_2
  |             |                +-- DISK_3
  |             |                +-- DISK_4
  |             |                +-- ADMIN\SETUP.ADM
  |             |                    ADMIN\SETUP.INF
  |             |                    ADMIN\AVWINNT.INI
  |             |
  |             +-- AVWIN9X -----+-- DISK_1\SETUP.VER
  |             |                +-- DISK_2
  |             |                +-- DISK_3
  |             |                +-- DISK_4
  |             |                +-- ADMIN\SETUP.ADM
  |             |                    ADMIN\SETUP.INF
  |             |                    ADMIN\AVWIN9X.INI
  |             |
  |             +-- AVUPDATE ----+-- FUP_1\SETUP.FU1
  |             |                |        \ANTIVIR.VDF
  |             |                +-- FUP_2\SETUP.FU2
  |             |                |        \ANTIVIR.VDF
  |             |
  |             +-- KEYFILE -----+-- LICENSE\HBEDV.KEY   *)
  |                              +-- FUP_1\HBEDV.KEY     *)
  |                              +-- FUP_2\HBEDV.KEY     *)
  :

*) This path may also be located elsewhere - specify in SETUP.ADM (control file for 
      Intranet update wizard with highest priority) or SETUP.INF (control file for Setup) 

3.5 Installation of updates

It's as simple as this: First check which FUP type the received update is for. Software on CD-ROM is always for FUP type 0, i.e. a fully registered version. Now also check which clients need to be updated: Windows 9x/Me, Windows NT/2000/XP or perhaps both? 

Let's assume you have received a new CD from us and use AntiVir in a mixed environment including some Windows 9x clients and some Windows NT workstations. Now simply copy the entire product directory (\EN\PRODUCTS\WIN9X\SETUP\) of AntiVir/9x including all subdirectories from the CD-ROM to the appropriate directory ANTIVIR\AVWIN9x\ on the update server. It is recommended to delete all old files on the server before copying the new ones to avoid a mixture of old and new installation files. Then copy the entire product directory of AntiVir/NT (\EN\PRODUCTS\WINNT\WORKSTAT\SETUP\) including all subdirectories  from the CD-ROM to the directory ANTIVIR\AVWINNT\ on the server. That's all there is to it! The updates will now be installed automatically without further intervention by the update wizard after the next version comparison. 

If you have received an update of the virus definition file ANTIVIR.VDF as part of an FUP-II update, simply copy the following files from the disk or from the relevant ZIP file to the target directory ANTIVIR\AVUPDATE\FUP_2 on the server: 

SETUP.FU2
ANTIVIR.VDF

You can proceed in the same way with special updates in the context of FUSE 6 (= FUP1) or FUSE 6/wi (=FUP2). All you need to do in each case is to copy the latest virus definition file and the corresponding control file SETUP.FUx to the relevant directory!

Important note:

3.6 Advice on problems

• Before the update, the wizard carries out a plausibility check on the licence file, search engine and virus definition file to make sure they are not likely to mess up the installation routines accidentally. If these 3 parts are not mutually compatible, the update will not be performed.
• If you have any problems, you should take a look at the generated logfile AVWUPD32.LOG, which you will find in the AntiVir installation directory (normally C:\Programs\AVWinXX) on the workstation computer. This contains more detailed information on the actions performed and the problems encountered. Please send us this file when requesting support.
• Check the update path of the clients: for the software, this should always point to the directory DISK_1 of the relevant product, or to the directory containing the corresponding SETUP.VER file. The update path for the licence file must point to the directory containing the new licence file HBEDV.KEY.
• Make sure the file structure on the update server is correct. If necessary, you can let the batch file MKTREE.BAT create this structure for you. erstellen.
• Make sure you always copy the new software to the right directory on the update server. The easiest way is to remember that updates with a SETUP.FU1 belong in the directory FUP_1 and updates with a SETUP.FU2 in the directory FUP_2. Software on CD-ROM is always FUP0 and belongs in the product directory.
• With Windows XP, there's a somehow strange behaviour restoring network connections. If local user name and remote user name are different, XP refuses to restore the network connection automatically as Windows NT or Windows 2000 do. This may cause the Update-Wizard to fail since the network connection is not available system startup. We are working on a solution to this problem. In case of questions about restoring network drives please contact the vendor of your operating system.