InterCheck version 3.12
Released 3rd June 1998
======================
This file updated 16th September 1998
-------------------------------------

Contents
--------

1.  Upgrade Procedure
2.  Modifications from Version 3.09
3.  Additional Notes
4.  Windows 95 Support
4.1    Installation
4.2    Loading from the login script
4.3    Loading from the command line
4.4    Command line qualifiers
4.5    Configuration
4.6    New Features
4.7    Additional Notes
5.  Windows for Workgroups Installation
5.1    Configuring the client
5.2    Installing automatically from a login script
5.3    Installing manually from the client
5.4    Interactive installation
5.5    ICSETUPW configuration file options
6.  Using the SWEEP VxD
6.1    System requirements
6.2    Windows 3.1 Installation
6.3    Windows 95 Installation
6.4    Operation
6.5    Configuration options
7.  Compatibility Issues
8.  Acknowledgments


1. Upgrade Procedure
--------------------

Before upgrading to InterCheck version 3.12, Sophos recommends that 
you upgrade to SWEEP version 3.12 or above. It is important that all 
the SWEEP components are upgraded. Please consult the appropriate SWEEP 
manual for a description of how to upgrade SWEEP.

Server Upgrade:
In order to upgrade the version of InterCheck on a file server, copy 
all the files on the InterCheck diskette into the directory on the 
server where InterCheck was originally installed. This will not 
affect the operation of any users currently connected and using 
InterCheck. Users will load the new version only after their 
workstation has been restarted.

Local Upgrade:
Copy the contents of the InterCheck diskette to the InterCheck 
directory on the fixed disk. The PC must be restarted in order to 
activate the new version of InterCheck. 


2. Modifications from version 3.09
----------------------------------

1.  The following new InterCheck configuration options have been 
introduced:

PreLoadStaticVxD=YES|NO                    (Windows 95 ONLY)

If set to YES, this will pre-load a new VxD (Virtual Device Driver)
that will be used by the next major release of InterCheck. Doing 
this will prevent a machine restart when upgrading to the next 
release of InterCheck, as the new VxD will already be resident in 
memory.

The new VxD will not be used by the current InterCheck and will 
remain inactive until the next major release is installed. 

The default setting is NO, i.e. the new VxD will not be pre-loaded.

Exercise caution when setting this option to YES.  Both versions of
InterCheck request "thread data slots" which are an extremely scarce
system resource.  Because the current InterCheck VxD is not aware of
the new VxD, it cannot "borrow" a thread data slot from it.  The
consequence of this is that if you pre-load the new VxD, you may
experience problems as these slots will not be available for other 
low-level system software.  These problems may include InterCheck 
being unable to load.

If you have this problem, you can run the ICLOAD95 program from the 
new version of InterCheck, specifying the -remove command line 
qualifier.  You should also remove the PreLoadStaticVxD=YES option
from INTERCHK.CFG.  You can then restart the Windows 95 client 
machine to complete the removal.  It may be necessary to start the 
machine in Safe Mode in order to do this.

UseProgramExtensionsForSweep=YES|NO

This option influences what files will be swept as InterCheck 
starts. By default, InterCheck now allows SWEEP to decide what 
file extensions represent files that need to be checked for 
viruses. Setting UseProgramExtensionsForSweep to YES forces SWEEP 
to use the list of extensions defined by the ProgramExtensions 
configuration option. Please note that this represents a change in 
default behaviour. 

2. When InterCheck is used in stand-alone mode on a Windows 95 
machine, it no longer unloads when a user logs out and logs in 
as a different user.


3. Additional Notes
-------------------

1. InterCheck contains support for the following languages:
English, French, German and Japanese. The appropriate language is
selected automatically. The automatic selection can be overridden
using the 'Language' option in the InterCheck configuration file
(interchk.cfg).

	Language=9	Selects English
	Language=7	Selects German
	Language=C	Selects French
	Language=11	Selects Japanese

When reading the configuration file InterCheck assumes that the file 
was created using a Windows editor (such as NOTEPAD) on the local 
system. When the configuration file has been created on another 
computer or using a DOS editor you may need to specify the code page 
which was in use when the file was created. An alternative code page
can be specified using the 'CFGCodePage' configuration option. For 
example, adding the following entry to the configuration file would 
indicate that the file was created using code page 850:

	CFGCodePage=850

Using an incorrect code page may cause the custom text message
defined with the 'PopupErrorText' option to be displayed incorrectly.

2. The configuration option 'ProgramExtensions' allows the 
specification of a list of file extensions. Any file whose extension 
matches an entry in the list will be considered by InterCheck to be a 
program and will be checked when ever it is accessed. The default 
extension list is:

        ProgramExtensions=COM,EXE,SYS,OV?,DLL,DRV,DOT,XL?

The '?' character can be used as a wildcard and '.' can be used to 
represent no extension. The option also modifies which files will be 
swept as InterCheck loads. Note, this option does not affect checking 
of files on execute, when all files will be checked, irrespective of 
extension.

3. The configuration option 'ScanNetPath=YES|NO' controls the 
scanning of remote programs when InterCheck is first installed. 
Enabling this option, causes InterCheck to search any remote 
directories specified in the PATH environment variable. Any program 
files discovered are swept for viruses. 

The default action depends on whether InterCheck can detect a central 
checksum file on the server. The ScanNetPath option is disabled when 
centralised checksumming is active.

4. The configuration file for a local installation of InterCheck can 
be automatically updated based on a central master copy. Including 
the following configuration option, in the server based configuration 
file, will force InterCheck to copy the server configuration file to 
the local machine as part of the auto update procedure:

        UpdateLocalCFG=YES

Please consult the manual for further information on the automatic 
updating of local installations.

5. InterCheck can record usage information in the server log file. 
This feature is controlled using the configuration option:

        ReportEvents=LOAD,UPDATE,INSTALL,ALL,NONE

InterCheck reports the current user and the network address of the 
workstation as well as the time and date whenever an event occurs. 

LOAD    - Records an entry every time InterCheck loads.
UPDATE  - Records an entry every time InterCheck or
          SWEEP is updated.
INSTALL - Records an entry when InterCheck is first 
          installed on a workstation.
ALL     - Records all of the above.
NONE    - Records nothing.

By default no events are reported to the server.

6. A number of sections, which are not yet described in the manual, 
can be used in the configuration file. These were introduced to 
enhance support for multiple workstation types. The following 
additional sections can now be used.

[InterCheckDOSGlobal] 
        The options in this section apply to all DOS/Windows
        workstations.

[InterCheckW95Global]
        The options in this section apply to all Windows 95 
        workstations.

[InterCheckDOSWorkstation]
        The options in this section apply to specific DOS/Windows
        workstations as specified by address.

[InterCheckW95Workstation]
        The options in this section apply to specific Windows 95
        workstations as specified by address.

Where conflicting options are encountered, the sections are assigned 
the following order of precedence (lowest first).

                   [InterCheckGlobal]        
     [InterCheckW95Global] or [InterCheckDOSGlobal]
                 [InterCheckWorkStation]
[InterCheckW95WorkStation] or [InterCheckDOSWorkStation]

The [InterCheckWorkStation], [InterCheckDOSWorkStation] and 
[InterCheckW95WorkStation] sections all require the use of the 
'Address=' command to specify to which workstations the options 
should be applied. Unlike earlier versions, multiple address options 
can be included in one section and the address option is not 
constrained to immediately follow the section header.

7. The use of wildcards is supported by the 'Exclude' configuration 
option. A '?' can be used to represent any character in a file name 
so that the statement 'Exclude=PROG?.EXE' would suppress the checking
of both PROGA.EXE and PROGB.EXE. 

There are number of default excludes: CONFIG.SYS, 386SPART.PAR, 
WIN386.SWP and ~$??????.DOT. The latter suppresses the checking of 
temporary template files used by Microsoft Word for Windows. The 
inclusion of the default exclusions can be disabled using the 
configuration option NoDefaultExcludes=YES.

The "Exclude" configuration option can also be used to prevent 
InterCheck from checking any files on a specified drive. For 
example, adding the command "Exclude=E:" to the configuration file 
would prevent InterCheck from checking any files on the E drive.

8.  The configuration option "AltCommsDir" can be used to define up 
to four alternative communication directories. For example:

	AltCommsDir=\\backup_server1\interchk\comms
	AltCommsDir=\\backup_server2\interchk\comms

The alternative directories are only used if InterCheck cannot 
contact the primary server, as defined by the CommsDirectory option, 
in order to log errors or check a file for viruses. When the primary 
server is not available InterCheck searches the list of alternatives 
until an active server is identified. Note: this option is only 
available on the DOS/Windows client.

9. The 'FileTypeDetection' configuration option modifies the method 
used by InterCheck to automatically determine if a file should be 
checked based on its contents instead of relying on the file 
extension. Currently InterCheck is able to automatically determine if 
a file is either a Windows Program or a Microsoft Word for Windows 
template containing macros. 

	FileTypeDetection=OFF		: Disables this feature
	FileTypeDetection=WINDOWS_EXE	: Detects Windows programs only
	FileTypeDetection=WORD_MACRO	: Detects Word macros only
	FileTypeDetection=ALL		: Enables all detection methods

By default all the 'FileTypeDetection' options are enabled (ALL).

Please note: This feature is only available in Windows 3.x and 
Windows 95. It is not supported in a DOS environment.

10. The ICLOGIN program supports the following command line 
qualifiers:

	-?	Displays the version number
	-a	Initiates the automatic Windows installation.
	-u	Uses UNC (Universal Naming Convention) when 
                running or installing InterCheck.

The use of the -a and -u options are described in more detail in the 
"Windows for Workgroups Installation" section later in this file.

11. Local checksum files are now automatically purged by default on 
updateif InterCheck is using the Sweep VxD and/or a central checksum 
list. The configuration option 'PurgeChecksumsOnUpdate' now has three 
values:

        PurgeChecksumsOnUpdate=YES     -> Always purge checksums
        PurgeChecksumsOnUpdate=NO      -> Never purge checksums
        PurgeChecksumsOnUpdate=DEFAULT -> Purge checksums if using
                                          the Sweep VxD or a central
                                          checksum list

12. If new Sweep IDE files are placed in the InterCheck directory, or 
if any existing files are changed, an update will be forced.

13. The configuration option 'AllowUnload' is now supported under 
Windows 95.


4. Windows 95 Support
---------------------

4.1 Installation
----------------
There are no additional installation instructions. All the required 
software is installed on the server as part of the server 
installation process as described in the manual.

4.2 Loading from the login script
---------------------------------
InterCheck for Windows 95 can be launched from the login script in a 
manner similar to that employed for the DOS/Windows version. When the 
system is configured in this manner InterCheck will be automatically 
started when the Windows 95 workstation logs into the network and 
unloaded when the user logs out. 

The commands required in the login script are identical to those used 
to launch the DOS/Windows version of InterCheck (please consult the 
manual appropriate to your network). The ICLOGIN command will 
determine the type of workstation and launch the appropriate version 
of InterCheck.

Please note that the workstation must be configured to log into the 
network in a manner which causes the login script to be executed. 
This is selected from the network control panel and depends on the 
network type in use:

Client for Microsoft networks:
Select 'Log on to Windows NT domain'

Client for NetWare networks:
Select 'Enable login script processing'

4.3 Loading from the Command Line
---------------------------------
InterCheck for Windows 95 can be started, at any time, by executing 
the program ICWIN95.EXE from the command prompt or as part of a batch 
file. 

4.4 Command Line Qualifiers
---------------------------
The following command line qualifiers are supported by ICWIN95.EXE:

-address   Specifies the workstation address.
-help      Displays help information.
-silent    Suppresses screen output.
-status    Displays InterCheck status.
-unload    Unloads InterCheck.
-verbose   Displays additional information.
-?         Displays help information.

For further information, please refer to the description of the 
equivalent command line qualifiers that are supported by the DOS 
version of InterCheck.

4.5 Configuration
-----------------
InterCheck for Windows 95 uses the same configuration file 
(INTERCHK.CFG) as InterCheck for DOS/Windows. All the configuration 
options supported by InterCheck for DOS/Windows will be accepted 
(please consult the manual for a full list). However, the following 
options are not relevant to the Windows 95 environment and therefore, 
perform no function:

AutoLoadWindowsDrivers
AutoUpdate
CriticalProgram
DisableVxDHooks
MaxAddressLength
MaxPathLength
MonoMonitor
NoStandardCriticalPrograms
Swap
SwapFlags
WarnCriticalProgramMissing

In addition, there are a number of further options, that are planned 
for inclusion in the next version, but are not currently implemented.

AllowDisable
HaltOnError
HaltOnVirus

4.6 New Features 
----------------
1. InterCheck for Windows 95 disables access to floppy disks which 
have been infected with a boot sector virus, whereas the DOS version 
issues repeated warnings.

4.7 Additional Notes
--------------------
1. InterCheck for Windows 95 does not intercept the renaming of 
program files. This means that files can be renamed or moved within
a logical drive without being checked.

2. InterCheck for Windows 95 uses the DOS version of SWEEP to 
initially check the PC for viruses. You do not need to install the 
SWEEP for Windows 95 product.

3. Under some circumstances there may be a delay before InterCheck 
can display a message indicating that it is working and checking a 
file. This is caused by restrictions in the design of Windows 95 
which does not allow the display to be updated while certain system 
functions are performed. 

4. InterCheck will currently intercept ALL access to program files. 
This includes accessing a program to extract its icon. Thus browsing 
the network, using Explorer, can initially be a slow process whilst 
InterCheck is active. As Explorer displays the icon associated with  
each file, InterCheck checks the file!


5. Windows for Workgroups Installation
--------------------------------------
The following section documents the new procedure for installing the 
InterCheck client software on Windows for Workgroups (WFWG) client 
workstations. It supplements the existing SWEEP user manuals, and 
replaces their sections on installing the InterCheck client on WFWG 
workstations.

The automated InterCheck client installation program is primarily 
intended for Windows for Workgroups client workstations which login 
to the network after starting Windows. Please consult the user 
manual for instructions on how to install InterCheck on workstations
that login to the network before starting Windows.

The installation program:

- Installs the InterCheck client files from the server onto the local 
  WFWG client workstations, requiring no user input when used with 
  its default settings.

- Uses either the default pre-set configuration options, or the 
  configuration options in the configuration file specified by the 
  system administrator on the server.

- Ensures that InterCheck is run every time the workstation is 
  started.

- Ensures that the local InterCheck files (including configuration 
  files) are kept up-to-date.

Before running the installation program, the latest InterCheck files 
should be installed on the server, the server itself should be 
activated, and any (optional) configuration options (described in the 
'Configuring the WFWG InterCheck client' section below) should be 
entered in the InterCheck configuration file.

There are two main ways that the installation program can be run:

1. Automatically from a login script, as described in the 'Installing 
automatically from a login script' section. This can be used to 
install the InterCheck client without having to visit each individual 
workstation.

2. Manually from each client, as described in the 'Installing 
manually from the client' section. This approach is generally used 
when no login script for the client is available.

In addition, both methods can be used interactively, as described in 
the 'Interactive installation' section. This might be necessary if an 
individual client configuration is non-standard, or if the users 
require more control over the installation and update process.

5.1 Configuring the client
--------------------------
The installation program will install the InterCheck client software 
using the default settings and configuration options. However, if any
changes to the configuration options are required, they must be made 
to the configuration file (INTERCHK.CFG in the directory from which 
the installation program is run) before the installation program is 
run. For example:

[InterCheckGlobal]
PopUpErrorText=Ring Tim on Ext 2534

in the configuration file would define a new virus alert message for 
all PCs.

Note that the server-based configuration file is the master copy used 
by all InterCheck WFWG installations - if different settings have to 
be made for individual workstations these should be defined with the 
Address configuration option. For example:

[InterCheckWorkstation]
Address=Tim
AllowDisable=YES

would allow the InterCheck client on the machine called Tim to be 
disabled.

The configuration file gives the system administrator full control 
over all the local InterCheck installations. Furthermore, if the 
server-based configuration file is changed after the InterCheck 
client has been installed locally, the next time that the client logs 
into the network its local configuration file will be automatically 
updated to reflect the changes made to the server-based copy.
See the 'Configuring the InterCheck client' chapter in the user 
manual for more information on the configuration options. See also 
the 'ICSETUPW configuration file options' section below for 
information on the ICSETUPW specific configuration options.

Note that the AutoUpdate and UpdateLocalCFG configuration options 
described in the 'Configuring the InterCheck client' chapter of the 
manual are not currently supported by the WFWG InterCheck client 
installation program.

5.2 Installing automatically from a login script
------------------------------------------------
Run ICLOGIN with the -A option from the workstation's login script. 
For example, the command line for Windows NT would be:

NET USE I: \\servername\directory
I:\ICLOGIN -A

where servername and directory are the names of the server and the 
directory containing the InterCheck files. Alternatively, if a 
permanent mapping to a drive is not required or not possible, use 
ICLOGIN with the -U command line qualifier and then remove the 
connection to the drive. The -U option makes ICLOGIN translate all 
the drive specifications to UNC (Universal Naming Convention) format, 
removing any dependency on the initial drive mapping. For example, 
for Windows NT:

NET USE I: \\servername\directory
I:\ICLOGIN -A -U
NET USE I: /DELETE

The next time that the workstation logs into the network, the login 
program will instruct Windows for Workgroups to run the InterCheck 
installation program. The installation program will install 
InterCheck to the local machine, and then automatically start the 
InterCheck client.

5.3 Installing manually from the client
---------------------------------------
On the client workstation, select Run from the Windows for Workgroups 
File menu and enter

I:\ICSETUPW.EXE

if the DOS drive I: is mapped to the directory on the server that 
contains the InterCheck files. This must be a permanent drive 
mapping. Alternatively, if a permanent connection to a DOS drive is 
not available or not desired, enter in the Run dialog box

\\servername\directory\ICSETUPW.EXE

where servername and directory are the names of the server and the 
directory containing the InterCheck files.
The installation program will copy all the InterCheck client files to 
a directory called C:\INTERCHK on the client workstation. After a 
successful installation, it will restart the workstation and then 
start the InterCheck client.

5.4 Interactive installation
----------------------------
Interactive installation may be required if the normal installation 
does not complete successfully, or if the user wants full control 
over every step of the installation process.

An interactive installation will always be necessary if the set-up 
process cannot determine the name or the address of the computer. 
This may occur when the computer is not connected to either a Novell 
NetWare or a Microsoft Network. The interactive installation will 
prompt for the machine name if the address cannot be determined. A 
unique name should be entered. It is used to identify the computer 
when reporting virus alerts to the server. 

There are two ways of running ICSETUPW interactively:

1.  Include the lines

[InstallOptions]
InteractiveInstall=1

in the configuration file (see also the 'ICSETUPW configuration file 
options' section) and run ICSETUPW. This is the only way of achieving 
interactive installation when a login script is used.

2. Run ICSETUPW.EXE with the -I command line qualifier. For example, 
if installing manually from the client, select Run from the File menu 
and enter

ICSETUPW -I

When the installation program is run from a login script in 
interactive mode, the next time that the workstation logs into the 
network the installation program will be presented to the user. The 
user is given the option of postponing the installation.

When the installation program is run either from a login script or 
manually from the client, the user is given the option to abort the 
process at all stages. The installation program will step through the 
configuration options available. No modifications will be made on the 
workstation until the user clicks Finish on the last page. The 
installation program will then copy all the InterCheck client files 
to the specified directory on the client workstation. It will then 
restart the workstation and start the InterCheck client.

5.5 ICSETUPW configuration file options
---------------------------------------
All ICSETUPW configuration file options should come under an 
[InstallOptions] section header in the InterCheck configuration file. 
See the 'Configuring the InterCheck client' chapter in the user 
manual for more information on the configuration file. The following 
options are available:

AutoInstallExclude[1...n]=<computer1>,<computer2>,...
-----------------------------------------------------
This option excludes named computers from ICSETUPW installations 
started by ICLOGIN. For example

AutoInstallExclude=Onion, Cheese, Marco
AutoInstallExclude1=Mini Marco, Derek

will exclude the computers with network names Onion, Cheese, Marco, 
Mini Marco and Derek. Computer names are not case sensitive.

CommsDirectory=<path>
---------------------
The default location for the InterCheck communications directory is 
COMMS in the InterCheck server directory. Use the CommsDirectory 
option to specify a different InterCheck communications directory. 
For example:

CommsDirectory=I:\SWEEP\COMMS"

DestinationDirectory=<path>
---------------------------
The default destination for the local WFWG InterCheck installation is 
C:\INTERCHK. Use the DestinationDirectory option to specify a 
different location. For example:

DestinationDirectory=C:\INTERCHK\COMMS

InteractiveInstall=YES|NO
-------------------------
If InteractiveInstall is set to YES, ICSETUPW will always run in 
interactive mode. If set to NO, ICSETUPW will not run in 
interactive mode, even if it started with the -I command line 
qualifier. See the 'Configuring the InterCheck client' chapter of the 
user manual for information on determining the computer name or 
network address of a client workstation.

SourceDirectory=<path>
----------------------
The default location of the WFWG InterCheck source files is the 
directory from which ICSETUPW is run. If for some reason the source 
files are stored elsewhere, use the SourceDirectory option. For 
example:

SourceDirectory=I:\INTERCHK\WFWG

PreserveAutoexecEntryOrderOnUpgrade=YES|NO
------------------------------------------
When this option is enabled, the InterCheck upgrade procedure will 
not 
alter the order of the commands in autoexec.bat file. 


6. Using the SWEEP VxD
----------------------
InterCheck supports a standalone mode of operation within the Windows 
3.1x and Windows 95 environments using a Windows Virtual Device 
Driver (VxD) to sweep the files that would normally be sent to a file 
server for authorisation. 

6.1 System Requirements
-----------------------
An 80386 (or above) based computer running Microsoft Windows 3.1x 
(enhanced mode) or Windows 95 is required.

A minimum of 4 Mbytes of memory is recommended. The Sweep VxD can be
installed on computers with less, but some applications may not run
correctly. Some memory related problems can be solved by enabling the
Windows virtual memory support or increasing the size of the virtual
memory swap file.

6.2 Windows 3.1 Installation 
----------------------------
The Sweep VxD is automatically installed as part of the standard 
InterCheck installation. However, by default the use of the VxD is 
disabled when installing to a network. This is the recommended 
configuration for most network based environments because it 
minimises the resources used on the remote workstations. In order to 
enable the use of the VxD the 'SweepVxDLoad' option must be added to 
the interchk.cfg file (see below)

InterCheck is automatically configured to use the Sweep VxD when you 
run ICINSTAL to install InterCheck on to the fixed disk of a 
workstation.

6.3 Windows 95 Installation 
----------------------------
To install InterCheck for Windows 95, run the SETUP.EXE program from 
the SWEEP for Windows 95 2.96a disk or later. Please consult the 
READ95.TXT file on the Sweep95 disk for additional information.

6.4 Operation
-------------
When the VxD is in use, InterCheck no longer displays 'requesting 
authorisation' messages, since these actually slow down the checking 
process. However, other functions are not affected by the presence of 
the VxD, for example, virus alerts are still reported to an attached 
InterCheck server.

6.5 Configuration options
-------------------------
The operation of the SWEEP VxD is controlled by a number of 
additional configuration options.

SweepVxDLoad=YES|NO
-------------------
The SweepVXDLoad option controls whether or not to use the SWEEP VxD. 
The default is NO. 

SweepVxDMode=FULL|QUICK
-----------------------
The SweepVxDMode option controls the method used by the VxD to sweep 
for viruses. Please refer to the SWEEP for DOS manual for a 
description of the FULL and QUICK sweeping modes. The default is 
QUICK.

SweepVxDScanCompressed=YES|NO
-----------------------------
The SweepVxDScanCompressed option can be used to suppress sweeping 
inside compressed files. Please refer to the SWEEP for DOS manual for 
more information about sweeping inside compressed files.

SweepVxDLogFile=<file name>
---------------------------
The SweepVxDLogFile option defines the name of the SWEEP VxD log 
file. Unless a file name has been defined using this option no 
information will be logged.

SweepVxDLogLevel=0..5
---------------------
The SweepVxDLogLevel controls the amount of information included in 
the log file.

    0 - No messages
    1 - Fatal errors
    2 - Virus alerts
    3 - Errors
    4 - Warnings [Default]
    5 - Information messages


7. Compatibility Issues
-----------------------
1. QEMM version 6.02
InterCheck will cause the system to hang in response to CTL-ALT-DEL 
if it is loaded high using QEMM v6.02. However, the diskette in the A 
drive will be checked for viruses before the system hangs so that the 
integrity of InterCheck is not compromised. There are a number of 
possible solutions:
        
a. Upgrade to QEMM version 7. 
b. Load InterCheck into low memory using the LoadLow=YES 
   configuration option.
c. Use the QEMM nr (norom) option. However this does not work with 
   the stealth option.

2. 386Max version 6.01d
InterCheck cannot load high when version 6.01d of the 386Max memory 
manager has been installed. An error message "Memory allocation 
error"  is displayed after InterCheck has run SWEEP. Use the LoadLow 
configuration option to load InterCheck into low memory. 
Alternatively upgrade to 386Max version 6.02 or above.

3. NetWare 4.01
The ICLOGIN program is not compatible with the version of the LOGIN 
program supplied as part of NetWare 4.01. In order to use the ICLOGIN
program you must upgrade the Novell login program to version 4.08 or 
later. Version 4.08 of LOGIN.EXE can be obtained, by all registered 
users of NetWare 4.01, as part of the "Novell 4.01 Upgrade kit Vol.1 
No.1".

4. MSD versions 2.10 and 2.11
The Microsoft diagnostic program, MSD.EXE, supplied with Windows 3.11
and DOS 6.x, does not work correctly with InterCheck. Unless the 
Novell LSL driver has been loaded before installing InterCheck, the 
MSD program will crash while initially examining the system, with 
unpredictable results. The problem has been fixed in version 2.13 of 
the MSD program, supplied with Windows 95. 

5.  Novell NetWare Client32 for Windows 95
InterCheck for Windows 95 cannot fully protect a system on which the 
Novell NetWare Client32 network drivers have been installed. Novell
have not implemented the low level functions used by InterCheck to 
monitor file access. Thus InterCheck does not 'see' and therefore
cannot check any files on remote NetWare drives. 

Novell are unable to provide information about when or if these 
functions will be provided in future versions of the client software.
We will, however, continue to investigate alternative means of 
providing support for the Novell client. 

An alternative solution, for users who need full NDS support in a 
NetWare 4 environment, is provided by the Microsoft NDS service.


8. Acknowledgments
------------------
This product uses the SPAWNO routines by Ralf Brown to minimise
memory use while shelling to DOS and running other programs.
