SYMANTEC CORPORATION - PETER NORTON GROUP
Build notes for Project Luigi (Norton AntiVirus for Windows 95)
Pre-release build 56 (External Test #4) 6/14/95

1. Disclaimer of Warranty
-------------------------

This software is pre-release software that may contain errors or other
deficiencies, and as such may not function properly and Symantec disclaims 
all liability for any such errors or malfunctions. Consequently, the 
enclosed software is provided as is, exclusive of any warranty, including, 
without limitation, any implied warranty of merchantability or fitness for 
a particular purpose, or any other warrant, whether expressed or implied. 
Symantec will not be liable for any damages including without limitation 
any indirect, incidental, or consequential damages (including but not 
limited to loss of anticipated profits) arising from any cause under or 
related to this software.

In english, the above statement simply says that you should use caution 
when using this software since it is still pre-release (pre-Beta, in fact).
You should not rely on it as your only source of virus protection and it 
may cause some unexpected behavior including corrupting files or making 
Windows 95 unstable.

2. Windows 95 Version Compatibility
-----------------------------------

2.1 Luigi is currently being tested with the builds 474 and later of
Windows 95. Earlier builds of Windows 95 are not supported and should 
not be used.

3. State of the Project
-----------------------

3.1 Luigi is at beta quality. It is code complete, largely stable,
    and at UI freeze except for some final artwork. Efforts are now 
    directed at compatibility, resolving final issues, and fixing
    cosmetic problems.

    Please be aware of the following issues:

3.1.1 ** IMPORTANT *** Smartcan in Tomahawk (NU95) builds prior 
      to ET 10 (including the preview version) can cause DATA
      CORUPTION if used with a newer version of either Luigi or 
      Raptor (Navigator). If you have an early version of NU95, 
      either uninstall it or disable Smartcan. Tomahawk ET 10
      and later correct this problem.
3.1.2 Luigi should now coexist with Tomahawk (NU95) and Raptor
      (Navigator). All versions must be dated June 14th or later.
      If you are using earlier versions of one or more products,
      you may experience version errors, system crashes, and 
      other unexpected behavior.
3.1.3 Low memory (all components) -- NAVAP has not been tuned for 
      memory usage yet and may not function well on a 4Meg machine.
      All components should behave reasonably well under low memory 
      conditions though.
3.1.4 Program Manager as the shell. Most components currently expect
      Explorer to be the shell. If Program Manager is your shell,
      items that normally appear in the tray will still be running but
      will not be visible (even in the task list). Also, scheduler will
      not startup automatically.
      
4. Installation Notes
---------------------

4.1 Before installing Luigi:

4.1.1 If you have an earlier build of Luigi...
      Uninstall any previous versions of Luigi. This will remove
      obsolete files and registry entries. Several files are obsolete
      starting with Build 51.
4.1.2 If you have NU95 and/or Norton Navigator...
      Use versions dated June 14th or later for best results. Earlier 
      versions did not coexist very well.
4.1.3 If you are using Luigi build 40 or earlier...
      Make sure it is not running when you install this build. Install
      will not detect Luigi build 40.
4.1.4 If you are using Luigi build 39 or earlier...
      Delete C:\NCDTREE\*.* before installing this build of Luigi. The
      file format was changed in build 40 and some components will lock
      the system if they encounter obsolete files. This warning does
      not apply to files created by NAV 3 -- Luigi is fully compatible
      with NAV 3 inoculation files.
4.1.5 If you are using DOS or Windows 3.1 anti-virus programs...
      Remove third party Dos/Windows 3.1 antivirus programs. Install 
      will only remove references to previous versions of NAV 3 and 
      Luigi files.

5. Highlights of this Build
---------------------------

5.1 The following has changed since build 52:

5.1.1 Most compatibility issues with Norton Navigator and Norton
      Utilities for Windows 95 have been resolved. Use versions of
      these programs dated June 14th or later for best results.
5.1.2 Install is now a 32-bit application.
5.1.3 NAVBOOT now takes only 512K. This will be reduced further before
      release.
5.1.4 MS-DOS Compatibility mode (i.e., 16-bit I/O with no VFAT) is
      now supported.
5.1.5 Rescue has been stabilized significantly. It may also use
      two disks if necessary.
5.1.6 Scanning speed is much faster and it will be further improved 
      before release.
5.1.7 Luigi now supports Compaq and other non-standard MBR partitioning
      schemes.

6. Known Problems
-----------------

6.1 General:

6.1.1 Deleted files are put in the recycle bin rather than being erased.
6.1.2 Do not install Luigi on a Windows NT system. Luigi is only designed
      for Windows 95 and will not run on NT.
6.1.3 Some components don't properly handle international characters
      in filenames, directories, or in some edit fields.
6.1.4 Final art for the icons, shutdown screen, and splash screens
      is not in yet.

6.2 DOS Components (NAVBOOT/NAVTSR):

6.2.1 NAVBOOT requires about 515K of free memory to load. The target 
      size for release is under 500K. If NAVBOOT won't load from your
      rescue disk because there isn't enough memory, make sure
      HIMEM.SYS is loaded and remove any unnecessary drivers from your
      boot disk's AUTOEXEC.BAT and CONFIG.SYS file. Drivespace seems
      to be a major source of memory and rescue disk problems. We
      are aware of this and working on a solution.
6.2.2 NAVTSR may cause Windows 95 to use real-mode drivers if it is
      loaded (e.g., if 'Programs run from AUTOEXEC' is checked in the
      Options:Startup tab of NAVW32. This results in the loss of long 
      filenames and a significant loss in system performance. This will 
      be addressed by the next external test. Until then, add a line like 
      the following in the IOS.INI file in your Windows directory:
                [SafeList]
                NAVBOOT.EXE
6.2.3 NAVBOOT doesn't acknowledge the bypass keys during startup.
6.2.4 NAVBOOT doesn't have an audible alert yet.

6.3 Windows Scanner (NAVW32/Scheduler):

6.3.1 Unloading Scheduler while the auto-protect agent is loaded
      may cause a system crash.
6.3.2 NAVW32 does not properly handle directory paths deeper than
      260 characters (the Win95 maximum). Longer directories are 
      possible on some network filesystems. If NAVW32 scans these
      directory trees, the results are not defined.
      
6.3.3 Launching scheduler from NAVW32 or at startup may not display 
      the toolbar the first time.
6.3.4 The scheduler and NAVW icons will disappear when you minimize these
      programs while running Program Manager as the shell.
6.3.5 Scheduler will not be loaded at startup when Program Manager is 
      the shell.

6.4 Auto-Protect (NAVAPW.EXE, NAVAP.VxD, SYMEVNT.386):


6.4.1 Auto-protect will lock the system if a power management or
      energy start screen saver disables the screen.
6.4.2 Auto-protect will lock the machine if it tries to display
      an alert while a screen saver is active.
6.4.3 Excluding an application from one virus-like activity will
      exclude it from all other virus-like activities.
6.4.4 The system may hang if the following conditions exist:
      A) Netscape is loaded
      B) Auto-protect is loaded
      C) Infected files are copied from one directory to another
      D) Auto-protect options are set as follows:
         * Scan a file when Run and Opened
         * Scan All Files
         * How to respond set to prompt with at least one button
           enabled.
6.4.5 Auto-protect may alert twice or more on some events caused
      by Win32 programs if you select Continue.
6.4.6 The auto-protect icon will not appear when running Program Manager
      as the shell.
6.4.7 Auto-protect does not update changes to the activity log,
      show icon, and allow to unload changes until the system
      is restarted. By release, these will be updated immediately.

6.5 Install:

6.5.1 Custom install is incomplete and has several minor flaws
6.5.2 Silent/unattended install is not working yet.
6.5.3 Uninstall may not clean-up all files in the NAV directory. When
      this is the case, it will not remove the directory either.
6.5.4 If the usage count for a shared component becomes 0 during an
      uninstall, install will not ask to delete the file.
6.5.5 Install doesn't "upgrade" other programs yet. Avoid installing 
      Luigi into any NAV 3 or other anti-virus program directories.
6.5.6 On-line registration is not supported yet.
6.5.7 Install does not insert a "Scan on Friday" event in scheduler
      even if the option is checked during install.
6.5.8 On multi-user configurations, the Start menu items only appear
      on the menu of the user who installed Luigi.
