SYMANTEC CORPORATION - PETER NORTON GROUP
Build notes for Project Luigi (Norton AntiVirus for Windows 95)
Pre-release build 52G (Expanded Beta Test #1) 6/5/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 347 (M8) and 474 of
Windows 95. Earlier builds of Windows 95 are not supported and should 
not be used.

2.2 IMPORTANT: Windows 95 builds prior to 474 fixes two problems that
    Luigi benefits from. They are:

2.2.1 Memory leakage. Earlier builds of Windows 95 would not release
      memory when a file was closed. Eventually, your system will start
      swapping to disk and slow down. When Luigi's auto-protect component
      is used, this memory leak occurs faster.

2.2.2 Video driver bug. Earlier builds of Windows 95 would occationally
      hang or fail to redraw the screen after a 'blue screen' alert
      (GPF, etc.). Luigi's auto-protect component uses also this technique
      to inform you about viruses and other alerts. The bug happens 
      infrequently (less than 1 in 40,000) but appears to be fixed
      in build 474.

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

3.1 Luigi is approaching beta quality. It is code complete and near
    UI freeze. Efforts are now directed first toward stability
    issue, second towards compatiblity issues, and third towards
    cosmetic and other issues. By beta, most stability and compatibility 
    concerns should be addressed.

    Please be aware of the following issues:

3.1.1 Low memory (all components) -- NAVBOOT and NAVAP have not been
      tuned for memory usage yet. All components should behave
      reasonably well under low memory conditions though.
3.1.2 Intensive Multitasking and I/O -- This has recently been
      stabilized but not exhaustively tested. 
3.1.3 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.
3.1.4 MS-DOS compatibility mode (i.e., no VFAT) is not supported at this 
      time. File scans will still work but auto-protect and MBR/boot 
      scans do not work.
3.1.5 Write protected/Missing media -- Little testing has been done
      in this area yet.
      
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 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.3 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.4 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 48:

5.1.1 Rescue is now working and fully integrated into Luigi.
5.1.2 ZIP scanning is now complete and supports ZIP and LHA/LZH files.
5.1.3 Install will offer to either save or overwrite existing options.
5.1.4 NAVW32 now arbitrates the volume lock with other Norton programs.
      This allows NAVW32 to scan a drive that NDD or SDW is working on
      in the background. If NDD or SDW (and some other utilities) are
      in the foreground, NAVW32 will not be able to get access to the
      drive but will allow you to skip the boot scan and scan just files.
5.1.5 High memory scans should work on all systems.
5.1.6 NAVW32 will offer to load auto-protect if you enable it and it is
      not already loaded.
5.1.7 Auto-Protect options (including unload) can now be accessed from
      the auto-protect agent in the tray.
5.1.8 Install is now named SETUP to conform to the Windows 95 standard.
      This allows uninstall to be run from the control panel.

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

6.1 General:

6.1.1 Scanning speed is slower than anticipated for the final version. 
6.1.2 Excluding a wildcarded filespec does not always work as expected.
6.1.3 Deleted files are put in the recycle bin rather than being erased.
6.1.4 Luigi doesn't properly handle boot records and MBR's on some Compaq
      hard drives.
6.1.5 Do not install Luigi on a Windows NT system. Luigi is only designed
      for Windows 95 and will not run on NT.
6.1.6 Misc. cleanup. All components have a number of cosmetic problems such 
      as hotkey duplication, misspellings, specific message content, artwork 
      (icons, bitmaps, animation).


6.2 DOS Components (NAVBOOT/NAVTSR):

6.2.1 NAVBOOT requires about 545K 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.
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.3 Windows Scanner (NAVW32/Scheduler):

6.3.1 NAVW32 may hang or slow down when scanning large network volumes.
6.3.2 If auto-protect is started while NAVW32 is running, auto-protect
      may catch inoc and virus alerts instead of NAVW32 when scanning.
6.3.3 When loading NAVW32, the "system busy" cursor will remain until 
      you move the mouse.
6.3.4 Unloading Scheduler while the auto-protect agent is loaded
      may cause a system crash.
6.3.5 Launching scheduler from NAVW32 or at startup may not display 
      the toolbar the first time.
6.3.6 The scheduler and NAVW icons will disappear when you minimize these
      programs while running Program Manager as the shell.
6.3.7 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 not alert if a virus is found during the 
      floppy scan at shutdown if NAVW32 or auto-protect initiated 
      the shutdown (this will happen, for example, if auto-protects 
      finds a virus in memory).
6.4.2 The system may hang or not redraw the screen properly after
      an auto-protect alert. This does not seem to happen in Win95
      build 474.
6.4.3 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.4 Auto-protect may alert twice or more on some events caused
      by Win32 programs if you select Continue.
6.4.5 The options button doesn't work properly if NAVW32 is loaded.
6.4.6 The auto-protect icon will not appear when running Program Manager
      as the shell.

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 does not insert a "Scan on Friday" event in scheduler
      even if the option is checked during install.
6.5.6 If you click on the blue setup background during the creation
      of the recue disk, the progress dialog will move to the background.
      Press Alt-Tab to locate recue and bring it to the foreground.
