Installation guide
OS/2 computers on a network
For networks with OS/2 servers and/or OS/2 workstations
Document date: February 2007
Sophos Anti-Virus installation guide
Contents
About this guide
3
1 Installing Sophos Anti-Virus
4
2 Using Sophos Anti-Virus via the GUI
12
3 Using Sophos Anti-Virus via the CLI
20
4 Updating Sophos Anti-Virus
23
5 Removing Sophos Anti-Virus
26
Appendix
2
Appendix 1 SETUP command line qualifiers
30
Technical support
36
OS/2 computers on a network
About this guide
This guide tells you how to
„ install Sophos Anti-Virus on networked OS/2 computers
„ scan the computers for viruses
„ eliminate viruses
„ update Sophos Anti-Virus
„ remove Sophos Anti-Virus.
You can find details of all other configuration options in the Sophos
Anti-Virus OS/2 user manual.
To install Sophos Anti-Virus on a single OS/2 computer refer to the Sophos
Anti-Virus OS/2 single user installation guide.
Sophos documentation is published on the Sophos Anti-Virus
Supplementary CD each month and at www.sophos.com/support/docs/
3
Sophos Anti-Virus installation guide
1 Installing Sophos Anti-Virus
To run Sophos Anti-Virus, your computers must
„ be running OS/2 Warp 3 or later
„ each have at least 11 MB of hard disk space if all options are active. This
requirement can increase considerably if Sophos Anti-Virus is scanning
complex archive files.
To run InterCheck on-access scanning, your computer must be running OS/2
Warp 4 or later (uniprocessor). InterCheck also works with eComStation
(uniprocessor) from Serenity Sytems International.
The examples in this guide assume you are using an IBM LAN Server
network. If you are using a different type of network, such as TCP/IP or
Novell NetWare, replace commands such as NET SEND with the
appropriate commands for your network.
You must uninstall any other anti-virus software before installing Sophos
Anti-Virus.
The installation process includes the following steps:
„ Create the central installation directory (CID) (section 1.1).
„ Determine which components of Sophos Anti-Virus to install (section 1.2).
„ Add the latest virus identity files (IDEs) (section 1.3).
„ Install Sophos Anti-Virus on networked computers (section 1.4).
1.1 Create the central installation directory (CID)
The central installation directory (CID) is the central copy of the Sophos
Anti-Virus files from which Sophos Anti-Virus is installed on the server and
workstations. Whenever you update the CID, Sophos Anti-Virus is updated
on workstations without affecting users.
1.1.1 Create the CID
Install the setup files in the CID as follows.
1. At the server, insert the Sophos Anti-Virus Supplementary CD in the CD
drive.
4
OS/2 computers on a network
2. At a command prompt, enter
F:\OS_2\SETUP -CENTRAL -INSTPATH=C:\SAVCID
where F: is the CD drive and C:\SAVCID will be the CID.
3. In the Install dialog box, click OK.
4. When the installation is complete, in the Installation and Maintenance
message box, click OK.
The following message is displayed in the command window
Creating central configuration ...
When the central configuration is complete, the message changes to
Creating central configuration ... Done.
Now create an alias for the CID (section 1.1.2).
5
Sophos Anti-Virus installation guide
1.1.2 Create an alias for the CID
Only the network administrator can do this.
At a command prompt, enter
NET ALIAS SAVCID \\[Servername] C:\SAVCID\OS2INST
where
SAVCID is the alias name, [Servername] is the name of the server and
C:\SAVCID\OS2INST is the CID.
You have created an alias for the CID. Now ensure users have the correct
access rights to the CID (section 1.1.3).
1.1.3 Set access rights for the CID
Check that users have only ‘read’ and ‘execute’ rights to the CID.
Now determine which components of Sophos Anti-Virus you would like to
install (section 1.2).
1.2 Determine which components of Sophos Anti-Virus to install
This section explains how to configure Sophos Anti-Virus to install the GUI
and/or InterCheck on-access scanning.
The GUI enables you to use and configure Sophos Anti-Virus by interacting
directly with it. The command line interface enables you to run Sophos
Anti-Virus under the control of a command procedure, without interacting
with it. This might be appropriate where the software on the workstations is
pre-configured by a company’s IT department, so that the interface allows
access to only an approved set of applications. You can configure Sophos
Anti-Virus from the command line.
If you choose to install InterCheck, this section also describes how to set up
central reporting.
If you do not wish to install either the Sophos Anti-Virus GUI or InterCheck
on-access scanning for OS/2, go straight to section 1.3 and add the latest
IDEs to the CID. You will be able to use Sophos Anti-Virus via the command
line.
You can use this section to change these settings at any time after
installation.
6
OS/2 computers on a network
If you choose to change either of the files described in this section at any
time after deploying Sophos Anti-Virus to your workstations, you must run
the following command when you have finished
SETUP -UPDATE
This will ensure that both the server and the workstations detect the new
files, and implement the changes you made.
1.2.1 Install on-access scanning and/or the Sophos Anti-Virus GUI
This section describes how to configure Sophos Anti-Virus to install the
Sophos Anti-Virus GUI and/or InterCheck.
InterCheck will not run under OS/2 Warp 3. If you want to install InterCheck
on a network that includes OS/2 Warp 3 and OS/2 Warp 4 computers, use a
separate action file for each type of computer. See the -ACTION qualifier in
appendix 1.1.
1. Go to the CID and open the file USERS.ACT using a text editor, for example
C:
CD \SAVCID\OS2INST
E USERS.ACT
2. To install the GUI: In the users.act window (below), in the line ‘Sophos
Anti-Virus for OS/2 GUI=No’, change ‘No’ to ‘Yes’.
To install InterCheck: In the users.act window (below), in the line
‘InterCheck On-Access Scanner for OS/2=No’, change ‘No’ to ‘Yes’.
On the File menu, click Save.
7
Sophos Anti-Virus installation guide
3. In the Save notification dialog box, click Type.
4. In the Type dialog box, click Plain Text, then click Set.
You can use this procedure to make the GUI or InterCheck available (or
unavailable) at any time.
If you chose to install InterCheck, set up central virus reporting (section
1.2.2).
1.2.2 Set up central virus reporting
This section describes how to ensure InterCheck sends a message to a
specified computer on the network whenever it finds a virus.
If you chose not to install InterCheck on-access scanning, go straight to
section 1.3 to add the latest IDEs to the CID.
When Sophos Anti-Virus is configured to notify a user of virus finds on
different computers, it is useful to include the name of the infected
computer in the virus notification. To do this, on each computer on the
network, in the file CONFIG.SYS, add
SET HOSTNAME=xxx
where xxx is a computer-specific name.
8
OS/2 computers on a network
This is normally done automatically on OS/2 computers using IBM LAN
Server or TCP/IP networking. It must be done manually on OS/2 NetWare
clients.
Set up central reporting as follows.
1. Open the file NTFY.CMD using a text editor. For example
C:
CD \SAVCID\OS2INST
E NTFY.CMD
The window below is displayed:
2. In the place of ‘machine_to_be_notified’ type the name of the computer to
which InterCheck should send virus notifications.
3. Save the file. When a workstation updates, the file is copied from the CID to
the workstation.
Most InterCheck configuration options are specified in the file
INTERCHK.CFG in the CID. For more information, see the Sophos
Anti-Virus OS/2 user manual.
Now add the latest IDEs to the CID (section 1.3).
1.3 Add the latest virus identity files (IDEs)
A virus identity file (IDE) enables Sophos Anti-Virus to detect a specific
virus. You need IDEs to protect your network against viruses discovered
since your version of Sophos Anti-Virus was compiled.
When, in future, you download, delete or change IDEs, you must run the
following command in the CID when you have finished:
SETUP -UPDATE
This ensures that the server and workstations detect the changes.
9
Sophos Anti-Virus installation guide
Download IDEs as follows:
1. At the server, go to the IDE download page of the Sophos website
(www.sophos.com/downloads/ide).
2. Download the compressed IDEs file for your version of Sophos Anti-Virus.
3. Extract the IDEs to
C:\SAVCID\OS2INST
If you prefer, scroll down the page and download the IDEs one by one, to
the location above.
Help with downloading IDEs is available in the Sophos support
knowledgebase (www.sophos.com/support/knowledgebase).
If you need further help with downloading IDEs, please contact Sophos
technical support.
Now install Sophos Anti-Virus on the OS/2 computers (section 1.4).
1.4 Install Sophos Anti-Virus on networked computers
The easiest way to install Sophos Anti-Virus on networked OS/2 computers
is to place a command in each computer’s login script to run the setup
program from the CID.
Sophos recommends that you do not install InterCheck on the server,
because it can affect server performance. If you chose to install InterCheck
on the workstations, install and update Sophos Anti-Virus on the server
using the Sophos Anti-Virus OS/2 single user installation guide, and install
Sophos Anti-Virus on the workstations using the instructions below.
1. In the login script, enter this line to map a drive
NET USE S: SAVCID
2. Then enter this setup command in the script
S:\SETUP -A -START -COE
This will run setup from the CID automatically.
Between ten minutes and one hour after the script runs, Sophos Anti-Virus is
installed to C:\SAV on the computers and, if the GUI is installed, starts
automatically. This period of time is configurable; see the -MINDELAY and
-MAXDELAY qualifiers in appendix 1.3.
Setup activity is logged in SAVSETUP.LOG in \OS2\INSTALL on the drive
from which OS/2 was started (usually C:).
10
OS/2 computers on a network
If you installed InterCheck, users must restart their workstations in order for
it to become active. InterCheck scans files for viruses as they are accessed
by users. If a virus is found, a message box is displayed at the workstation,
and, if you set up central reporting, an alert is sent to a named computer.
For information about disinfection, go to section 2.4 (GUI) or section 3.2
(CLI).
You have completed installation of Sophos Anti-Virus on an OS/2 network.
Now go to section 2 to find out how to use Sophos Anti-Virus via the GUI, or
section 3 to find out how to use Sophos Anti-Virus via the CLI.
11
Sophos Anti-Virus installation guide
2 Using Sophos Anti-Virus via the GUI
The sections that follow assume you installed Sophos Anti-Virus with the
GUI. If you chose to install the command-line version of Sophos Anti-Virus
only, go straight to section 3.
This section explains how to
„ open the Sophos Anti-Virus GUI (section 2.1)
„ scan your computer for viruses now (section 2.2)
„ schedule virus scanning (section 2.3)
„ set up automatic virus disinfection (section 2.4).
For more detailed information about using Sophos Anti-Virus via the GUI,
refer to the Sophos Anti-Virus OS/2 user manual.
2.1 To open the Sophos Anti-Virus GUI
1. On the desktop, double-click the Sophos Anti-Virus for OS/2 icon.
2. In the Sophos Anti-Virus for OS/2 folder, double-click the Show Sophos
Anti-Virus window icon.
The Sophos Anti-Virus window is opened, displaying the Immediate tabbed
page.
12
OS/2 computers on a network
2.2 To scan your computer for viruses now
This is also known as an ‘on-demand’ virus scan, or ‘on-demand scanning’.
1. In the Sophos Anti-Virus window, by default the Path list contains one item:
Local Hard Drives. This includes all hard drives and CD drives on your
computer.
2. Click GO.
When the scan is complete, the results are displayed in the on-screen log at
the bottom of the window.
13
Sophos Anti-Virus installation guide
2.2.1 What happens if a virus is found?
If Sophos Anti-Virus finds a virus, it displays a message box like this:
You also see details in the on-screen log at the bottom of the Sophos
Anti-Virus window. Double-click the name of the virus to view its analysis
on the Sophos website.
To find out how to set up Sophos Anti-Virus to disinfect files automatically,
go to section 2.4.
You have now completed an on-demand virus scan. To find out how to
schedule a virus scan, go to section 2.3.
14
OS/2 computers on a network
2.3 To schedule a virus scan
1. In the Sophos Anti-Virus window, click the Scheduled tab.
By default, there is a job named Default, which scans all local hard drives.
2. To add a new scheduled job, click Add.
3. In the Enter new job name dialog box, add a name and click OK.
15
Sophos Anti-Virus installation guide
4. In the Job Configuration dialog box, click Add or Remove to select the files
and drives you wish to scan.
5. Click the Time tab. Enter the time and the days of the week when the scan
should occur, and click OK.
You can use the other tabs to customise the scheduled scan, and you can
also copy scheduled jobs to other computers on the network. Refer to the
Sophos Anti-Virus OS/2 user manual for more information. Go to section
16
OS/2 computers on a network
2.4 to find out how to configure Sophos Anti-Virus to attempt to disinfect
files.
2.4 To set up disinfection
This section describes how to configure Sophos Anti-Virus to disinfect boot
sectors, documents and programs automatically, and to delete or shred files
that cannot be disinfected.
1. In the Sophos Anti-Virus window, click Configuration.
2. In the Job configuration - Immediate dialog box, click the Action tab.
17
Sophos Anti-Virus installation guide
3. To set up automatic disinfection of boot sectors and/or documents and
programs, select Disinfect boot sectors and/or Disinfect documents and
programs. To set up deletion or shredding of files, select Infected files, then
click either the Delete or the Shred option. Sophos recommends that you
select Request confirmation.
If you choose to delete or shred files, Sophos Anti-Virus does not attempt
to disinfect them first, even if you select disinfection as well. However,
Sophos Anti-Virus does not delete or shred infected mailboxes.
4. Click OK.
When you scan your computer for viruses, Sophos Anti-Virus will try to
perform the action you have specified on any files it finds to be infected with
a virus.
If you selected Request confirmation in step 3, a dialog box is displayed at
the start of the scan. Click Yes to confirm Sophos Anti-Virus should carry out
the requested actions on finding a virus.
18
OS/2 computers on a network
After the scan, the results are displayed in the on-screen log.
Check the contents of any disinfected documents carefully, as the virus
may have corrupted them.
Delete any disinfected programs and replace them from backups, as the
virus may have corrupted them.
If you need further help, contact Sophos technical support.
19
Sophos Anti-Virus installation guide
3 Using Sophos Anti-Virus via the CLI
This section explains how to
„ scan your computer for viruses now (section 3.1)
„ disinfect documents, boot sectors and programs (section 3.2)
from the command line.
For more detailed information about using Sophos Anti-Virus via the CLI,
refer to the Sophos Anti-Virus OS/2 user manual.
3.1 To scan your computer for viruses now
To scan the computer for viruses, enter
OSWEEP
This scans all local hard drives.
To scan particular hard drives, use their letters. For example
OSWEEP D: E:
3.1.1 What happens if Sophos Anti-Virus finds a virus?
If command-line Sophos Anti-Virus finds a virus, a message like this is
displayed:
Sophos Anti-Virus
Version 3.68, April 2003
Includes detection for 80962 viruses, trojans and worms
Copyright (c) 1989,2003 Sophos Plc, www.sophos.com
System time 11:34:41, System date 02 May 2003
Quick Sweeping
Press Esc to quit
>>> Virus 'EICAR-AV-Test' found in file F:\EICAR.COM
39 files swept in 0 minutes and 2 seconds.
For information on disinfection, see section 3.2.
20
OS/2 computers on a network
3.2 To disinfect from the command line
3.2.1 To disinfect a document
1. Close down the application in which the document was created, and enter
OSWEEP [FILE.DOC] -DI
where [FILE.DOC] is the file name.
2. Check the document carefully after disinfection. The virus may have
corrupted the contents.
3.2.2 To disinfect a boot sector on your hard disk
This procedure assumes that A: is the floppy disk and E: is the CD.
1. If OS/2 is already running, shut it down.
2. Boot OS/2 from the OS/2 Utility disk set. The disks should include a CD
driver and the following files: NLS.DLL, QUECALLS.DLL, and
VIOCALLS.DLL. Follow the on-screen instructions. When booting is finished,
the A: prompt appears.
3. Insert the Sophos Anti-Virus Supplementary CD.
4. At a command prompt, enter
SET BEGINLIBPATH=A:\;E:\OS_2
This tells OS/2 where to find the files mentioned in step 2.
5. Enter
E:\OS_2\OSWEEP -DI
The computer is scanned for boot sector and file viruses. Sophos Anti-Virus
disinfects infected boot sectors and some programs (see section 3.2.4). If
this procedure fails to disinfect a virus on your computer, contact Sophos
technical support.
3.2.3 To disinfect a boot sector on a floppy disk
This procedure assumes that A: is the floppy disk and E: is the CD.
1. If OS/2 is already running, shut it down.
2. Boot OS/2 from the OS/2 Utility disk set. The disks should include a CD
driver and the following files: NLS.DLL, QUECALLS.DLL, and
VIOCALLS.DLL. Follow the on-screen instructions. When booting is finished,
the A: prompt appears.
21
Sophos Anti-Virus installation guide
3. Insert the Sophos Anti-Virus Supplementary CD.
4. At a command prompt, enter
SET BEGINLIBPATH=A:\;E:\OS_2
This tells OS/2 where to find the files mentioned in step 2.
5. Enter
E:\OS_2\OSWEEP A: -DI -MU
6. When the computer prompts you, insert the floppy disks to be disinfected.
Infected boot sectors and programs are disinfected.
7. When disinfection is complete, scan the whole computer for remaining
infections.
If this procedure fails to disinfect a virus on your floppy disk, contact Sophos
technical support.
3.2.4 To disinfect a program
1. To disinfect an infected program, enter
OSWEEP [PROG.EXE] -DI
where [PROG.EXE] is the program name.
2. Scan the whole computer for remaining infections.
3. If the program cannot be disinfected, delete the program using
OSWEEP [PROG.EXE] -REMOVEF
4. Even if you have not deleted the program, replace it from original installation
disks, a clean computer, or sound backups. The virus may have corrupted it.
22
OS/2 computers on a network
4 Updating Sophos Anti-Virus
This section explains how to update Sophos Anti-Virus both when a new
virus is discovered, and when you receive the monthly update CD. It also
explains how to restore a previous version of Sophos Anti-Virus.
4.1 To update Sophos Anti-Virus between monthly updates
When a new virus is discovered, Sophos creates a virus identity file (IDE)
that enables Sophos Anti-Virus to detect the new virus should it infect your
network. To keep your copy of Sophos Anti-Virus up to date, download new
IDEs from the Sophos website as soon as they become available.
Register at www.sophos.com/virusinfo/notifications to receive an email
notification whenever a new IDE is made available.
Go to section 1.3 for instructions on how to download IDEs. You must run
the following command in the central installation directory (CID) when you
have finished:
SETUP -UPDATE
This ensures that the server and workstations detect the changes.
4.2 To update Sophos Anti-Virus from the monthly update CD
To update Sophos Anti-Virus, carry out the following steps:
„ Go to the central installation directory (CID) and delete all existing IDEs.
„ Download the latest compressed IDEs file (or individual IDEs if you
prefer) from the Sophos website to the CID (section 1.3).
„ Update the Sophos Anti-Virus files in the CID (section 4.2.1).
4.2.1 Update the Sophos Anti-Virus files in the CID
1. At the server, insert the Sophos Anti-Virus Supplementary CD in the CD
drive.
23
Sophos Anti-Virus installation guide
2. At a command prompt, enter
F:\OS_2\SETUP -CENTRAL
where F: is the CD drive.
If any workstations are currently updating from the CID, there will be a delay
before SETUP can modify the CID. Each time SETUP attempts to access the
CID, it will print a dot on the command line.
3. In the Update dialog box, you can choose to Save a backup version of the
installed product. A backup will enable you to restore the existing
configuration if the update goes wrong.
If the CID is on a computer that is not running OS/2 (e.g. a Windows 2000
server) you may be unable to use the backup option successfully.
You do not need to specify which directory will be updated. SETUP
automatically updates the existing CID.
Click Update.
If you have chosen not to save a backup, you will be prompted to confirm
your choice.
The CID is updated.
24
OS/2 computers on a network
4. When the update is complete, in the Installation and Maintenance dialog
box, click OK.
The workstations will automatically update themselves from the CID as soon
as they detect the updated files.
Occasionally, SETUP informs you that the workstations must be rebooted to
activate new features of InterCheck. You must reboot the workstations as
soon as convenient after they have updated. However, InterCheck still
detects new viruses on the workstations without rebooting.
The monthly update of Sophos Anti-Virus is complete.
4.3 To restore a previous version of Sophos Anti-Virus
Restoring a CID
To restore a previous version to the CID, update the CID from the Sophos
Anti-Virus Supplementary CD for the version you require. All the files
needed are copied from the source, regardless of their date and time.
As IDEs are added to the CID manually, they are not deleted automatically
when you restore a previous version. You should delete any IDEs in the CID
manually.
Deleted IDEs cannot be restored.
Restoring a workstation installation
To restore a previous version on a workstation that is configured to update
automatically from the CID, update the CID from the Sophos Anti-Virus
Supplementary CD for the version you require.
The next time the workstation updates from the CID, it downloads and uses
the restored files.
25
Sophos Anti-Virus installation guide
5 Removing Sophos Anti-Virus
You can remove Sophos Anti-Virus completely or only specific components.
In each case, removing Sophos Anti-Virus involves the following steps:
„ remove Sophos Anti-Virus from the workstations (section 5.1).
„ remove the central installation directory (CID) (section 5.2).
5.1 Remove Sophos Anti-Virus from the workstations
1. At the server, change to the CID and open the file USERS.ACT, for example
C:
CD \SAVCID\OS2INST
E USERS.ACT
2. In the file USERS.ACT, change the values of the components you want to
remove to ‘No’.
3. Save the file.
4. If you are using any other .ACT files, perform steps 2 and 3 for those files.
The -ACTION qualifier in appendix 1.1 explains what .ACT files are.
5. Run
SETUP -UPDATE
When workstations next check the CID for updates, they will remove the
installed components of Sophos Anti-Virus that you specified in step 2. If all
components are removed from a workstation, it will stop automatic
updating.
26
OS/2 computers on a network
Components of Sophos Anti-Virus have been removed from the workstations.
Now remove the CID, if required (section 5.2).
5.2 Remove the central installation directory (CID)
1. Delete all automatic updating commands from users’ login scripts.
2. At the server, insert the Sophos Anti-Virus Supplementary CD in the CD
drive.
3. At a command prompt, enter
F:\OS_2\SETUP -CENTRAL -REMOVE
where F: is the CD drive.
4. In the Delete dialog box, ensure Central Installation is selected, and click
Delete.
5. In the Installation and Maintenance dialog box, click OK.
6. Check the CID. If there are any files left in the directory or sub-directory
(e.g. WRITE.LOK) delete them. When the directory is empty, delete it.
27
Sophos Anti-Virus installation guide
28
Appendix
SETUP command line qualifiers
Sophos Anti-Virus installation guide
Appendix 1 SETUP command line qualifiers
You can prefix all qualifiers with a hyphen or a slash.
For help, use the -?, -H or -HELP qualifier.
There are qualifiers to specify:
„ Installation type (appendix 1.1).
„ Source and target directories (appendix 1.2).
„ Scheduling of installation and CID-locking (appendix 1.3).
„ Removal of Sophos Anti-Virus (appendix 1.4).
„ Error messages and reporting (appendix 1.5).
The levels of error message and the ways in which errors are reported are
described in appendix 1.6.
Appendix 1.1 Installation type
-A or -AUTO
Perform an automatic installation or update from a central installation
directory (CID).
-ACTION
Specify the ‘action file’ used when installing or updating Sophos Anti-Virus
on workstations from a central installation. This is a text file which
determines which components of Sophos Anti-Virus are installed.
The default action file created during central installation is USERS.ACT in
the central CID. It contains the lines
[Components]
Sophos Anti-Virus for OS/2 GUI=No
Sophos Anti-Virus for OS/2 Command Line=Yes
InterCheck On-Access Scanner for OS/2=No
To install a component, change ‘No’ to ‘Yes’.
Enter ‘No’ in all three lines if you want Sophos Anti-Virus to be removed
from workstations.
The -ACTION qualifier lets you make different kinds of installations for
different users.
30
OS/2 computers on a network
You can create different action files for different users, for example to specify
that a sub-set of users should have InterCheck while the remaining users do
not. When you put the SETUP command in users’ login scripts, simply use
a different -ACTION value for different users. For example
-ACTION=SPECIAL
specifies that a user's components are specified in the file SPECIAL.ACT in
the CID.
-CENTRAL
Perform the operation on the CID instead of the workstation. By default, this
creates or updates the CID.
-CLOSE
Close the currently running background (automatic) setup program.
-UPDATE
Marks the CID as updated, so that workstations will update from it.
Run SETUP with this qualifier in the CID when you add virus identity files
(IDEs) to it. See section 1.3.
You should not use this qualifier when updating the CID using the
-CENTRAL qualifier.
-FULL
Use the -FULL qualifier after updating any of the CID files except virus
identity files (IDEs) and configuration files. -FULL is intended primarily for
use under the supervision of Sophos technical support.
-FULL recreates the central installation directory’s configuration file,
SWEEPOS2.CFG. This ensures that the configuration file accurately reflects
the contents of the CID, and that workstations will transfer precisely the
files needed to update them. -FULL can be used only with -UPDATE.
-START
If the Sophos Anti-Virus GUI and scheduler are running when an update is
performed, they will stop. When updating is complete, Sophos Anti-Virus
restarts. If -START is used, Sophos Anti-Virus will be started even if it was
not running before.
31
Sophos Anti-Virus installation guide
Appendix 1.2 Source and target directories
-SRCPATH=directory
Specifies the source directory, i.e. the directory containing the files to be
installed. The default is the directory from which SETUP is run.
-INSTPATH=directory
Specifies the directory to which files are to be installed. This applies to new
installations, not to updates. The default directory for a workstation
installation is C:\SAV.
Appendix 1.3 Scheduling and CID locking
-MINDELAY=n
Sets the minimum delay for an automatic install or update to n minutes.
The install or update will take place at a random time between the
minimum and maximum delay times (see -MAXDELAY).
The default is 10 minutes.
-MAXDELAY=n
Sets the maximum delay for an automatic install or update to n minutes.
The install or update will take place at a random time between the
minimum delay time (see -MINDELAY) and the maximum delay time. The
random time is different on each workstation in order to spread the network
load of updating.
The default is 60 minutes.
-PERIOD=n
SETUP locks the CID when updating it or using it to update workstations. If
a lock cannot be placed immediately, SETUP retries at random intervals.
This qualifier sets the maximum interval to n minutes. The default is 1
minute.
-TIMEOUT=n
SETUP locks the CID when updating it or using it to update workstations. If
a lock cannot be placed immediately, SETUP retries repeatedly until it times
out. This qualifer sets the timeout to n minutes. The default is 10 minutes.
See also -PERIOD above.
32
OS/2 computers on a network
-ONCE
Configures SETUP to attempt an automatic installation or update only once.
Unless this qualifier is used, SETUP will repeatedly check the central
installation directory to see whether a further update is needed.
-LOCKLIMIT=n
Sets the maximum period for which SETUP can lock the central installation
directory. Zero means no limit. The default is 20 minutes.
Appendix 1.4 Removal of Sophos Anti-Virus
-REMOVE
Remove the product. The product removed is the workstation installation of
Sophos Anti-Virus unless the -CENTRAL qualifer is used.
-CLEAR
If Sophos Anti-Virus for OS/2 files are deleted, SETUP -REMOVE can fail.
The program will warn that the product cannot be deleted because it is not
installed. Settings can then be left in the user profile. SETUP -REMOVE
-CLEAR clears these settings. SETUP -CENTRAL -REMOVE -CLEAR clears
the settings for a central installation.
You will have to delete Workplace Shell objects (the icons and the entry in
Startup which starts SWEEP on system start) manually if they remain after
removing Sophos Anti-Virus. See the OS/2 documentation for instructions.
Appendix 1.5 Error messages and reporting
-LOG=filename
Specifies a file that SETUP will use to log messages. The default is
SAVSETUP.LOG in \OS2\INSTALL on the drive from which OS/2 was started
(usually C:) .
-LOGLVL=<Error level>
Sets the level of error and other messages written to the log file. See
appendix 1.6 for details.
The default setting is WARNING, which means that minor problems that do
not stop updating, as well as more serious errors, are written to the log file.
33
Sophos Anti-Virus installation guide
-REPORTER=filename
Specifies a command file to be used for reporting errors. This is useful for
automatic updates, which display no errors on screen. The command file
would usually e-mail a message to a system administrator.
There are seven parameters:
%1
%2
%3
%4
%5
%6
%7
Machine name (%HOSTNAME% or else "Unknown")
Date
Time
Message
SETUP log file
Installer error log file
Installer history log file
-REPLVL=<Error level>
Sets the level of error and other messages reported by a program called with
the -REPORTER qualifier. See appendix 1.6. The default is CORRECTED,
which means that corrected, uncorrected and fatal errors are reported.
-DMY, -MDY or -YMD
If an error-reporting command is used (see -REPORTER), the date will be
passed to it in the format specified
If you use -DMY, the format is dd/mm/yyyy.
If you use -MDY, the format is mm/dd/yyyy.
If you use -YMD, the format is yyyy/mm/dd.
-DISPLVL=<Error level>
Sets the level of error and other messages to be displayed on screen. See
appendix 1.6 for details. The default setting is ERROR, which means that
errors that can make an operation fail and more serious errors are displayed.
-ERRLOG=filename
Specifies the filename of the Installer’s error-logging file.
-HISTLOG=filename
Specifies the filename of the Installer’s history-logging file.
-COE or -CONTERR
Continue on error. An automatic installation or update will continue running
even if an error occurs (unless you use the -ONCE qualifier).
34
OS/2 computers on a network
Appendix 1.6 Error levels
This section lists the different levels of error messages and the methods used
for reporting.
Error messages and other messages are classified by level. Errors at or
above the level you specify are reported.
There are five error levels. In increasing order of severity, these are as follows:
INFO
Information. No action required.
WARNING
A small problem was detected but SETUP was able to
continue.
CORRECTED
An error was detected but has been corrected, at least for
the current operation. The condition causing the error
requires attention.
ERROR
The operation (install, update or remove) may not have
been completed successfully.
FATAL
The operation has not been completed successfully.
SETUP could not continue running, even if -COE (continue
on error) was specified.
Errors are reported in three ways.
On screen
If the SETUP information file can be found, the appropriate page is
displayed. Otherwise, a text message appears on screen. No messages are
displayed in automatic mode.
In a log file
You can use the -LOGLVL qualifier to set the level of messages that will be
logged. The default is WARNING.
By calling a reporting program
You can use the -REPORTER qualifier to specify a program to report errors.
You can set the level of messages reported by using the -REPLVL qualifier.
The default is CORRECTED.
35
Sophos Anti-Virus installation guide
Technical support
For technical support, visit www.sophos.com/support.
If you contact technical support, provide as much information as possible,
including the following:
„ Sophos software version number(s)
„ operating system(s) and patch level(s)
„ the exact text of any error messages.
Copyright © 2002–2007 Sophos Group. All rights reserved. No part of this
publication may be reproduced, stored in a retrieval system, or transmitted, in any
form or by any means, electronic, mechanical, photocopying, recording or otherwise
unless you are either a valid licensee where the documentation can be reproduced in
accordance with the licence terms or you otherwise have the prior permission in
writing of the copyright owner.
Sophos and Sophos Anti-Virus are registered trademarks of Sophos Plc and Sophos
Group. All other product and company names mentioned are trademarks or registered
trademarks of their respective owners.
36