                 McAfee VIRUSCAN 2.00 Public Beta B
                      Problem Reporting Guide
                           (REPGUIDE.TXT)
                                
                    Author:             David Pierce
                    Last Update:        94/03/23 (DAP)
                    Printed:            94/03/23 (DAP)


Thank you for participating in the McAfee VIRUSCAN 2.00 Public
Beta Program.  This document is intended to aide you in detecting
and reporting problems encountered during the beta period, and
includes the following:

  * Problem Reporting
  * Product Notes
  * Known Problems with 2.00 Beta B
  * Bug Report Form


DISCLAIMER

This product is Beta software, and as such, is not at production
quality levels.  It is not intended for daily use, and should not
be used as the sole source of anti-virus protection for your
system.  In no event shall McAfee Inc. be responsible for any
damages whatsoever arising out of the use or inability to use
this product.

PROBLEM REPORTING

If you encounter any problems during the course of the Beta
period, please review the list of known problems, below, to
see if your problem is on the list.  Problems listed are
currently being addressed, and will be fixed before the final
release of the product.  If your problem is not listed, please
notify us so we can address the issue; Fill out a copy of the
enclosed Bug Report Form and FAX or mail it to us at:
     
     E-mail:            vs20beta@mcafee.com
     FAX:               1-(408) 970-9727 (Address FAXes to to SQA)
     BBS:               1-(408) 988 4004 (send EMAIL to VS20BETA SUPPORT)
     
     Mailing Address:   McAfee Associates, Inc.
                        ATTN: SQA
                        2710 Walsh Avenue, Suite 200
                        Santa Clara, CA  95051-0963




                                   Page 1


Problem Reporting Guide                              Page 2


Ŀ
IMPORTANT NOTICE - PLEASE READ!


Due to the nature of anti-virus software, the slight chance exists
that a virus may be reported in a file that is not infected by that
virus.

If you receive a report of a virus infection which you believe may
be in error, please contact us by one of the methods listed above,
and upload a copy of the file in question to the BBS.  Include in
any correspondence your name, address, daytime telephone number,
fax number, and electronic mail address, if any.

PRODUCT NOTES

The following issues are not problems with this release, but
intentional differences having to do with the release schedule
and the product design.  If you are already familiar with McAfee
anti-virus products, please review this list to familiarize
yourself with the issues.  For more information on changes
between SCAN 2.0 and previous version, please see the enclosed
documentation (VIRUSCAN.TXT and VSHIELD.TXT).


*    Virus detection in this release is not complete.  If you
     encounter a virus which is not detected by this release, please
     notify us and upload a copy of the infected file to the BBS so
     we can ensure that the virus is detected in the final release.

*    Specific variants of most viruses are not distinguished from
     the parent virus in this release; therefore, many different
     variants will be identified as the same virus.  In the final
     release, known variants will be identified exactly and distinguished
     from each other.

*    The first public beta releases of VirusScan for DOS and OS/2 do not
     have any virus removal capabilities.  The next Beta releases of
     both products will include a CLEAN.DAT file which will provide
     this functionality.

*    The list of standard extensions used by VirusScan 2.00 has been
     changed from the list used by the old VIRUSCAN.  By default,
     VirusScan now checks all files for viruses.  Optionally, VirusScan
     can be set to only check files with extensions of .EXE, .COM, .SYS,
     .DLL, .OV?, and .BIN when run with /STDEXT (standard extensions)
     switch.





Problem Reporting Guide                              Page 3


*    In order to minimize memory usage, VShield uses a different data
     file format than VirusScan.  Although a copy of the data file,
     VSHIELD.DAT, is included pre-built with your beta release,
     VShield is designed with the ability to build it's own data file
     so that when you receive an updated version of SCAN.DAT for
     VirusScan, Vshield can generate an up-to-date data file.  The
     first time you run VShield after copying a new version of
     SCAN.DAT to the VShield program directory, VShield will rebuild
     VSHIELD.DAT.  This process may take a few minutes on slower
     systems, so please be aware that the wait is normal.

*    SCAN sometimes reports "File <file> if executable may be corrupted"
     Files which cause this message to be generated are internally
     structured like executables, but at some point deviate from
     that structure, indicating a corrupted executable.  This
     message may also be generated, however, for some perfectly
     good data files which just happen to be structured like
     executable files.  If you see this message for non-
     executables, you can safely ignore it.  If you see this
     message for executables, please notify us and upload a copy
     of the executable file to the BBS so we can inspect it and
     make changes to account for it.






























Problem Reporting Guide                              Page 4


Known Problems with VIRUSCAN 2.00 Beta B

The following bugs are known to exist in the Beta B version of
McAfee VirusScan 2.00 product.  All problems are currently being
addressed, and will be fixed before the final release of the
product.  When you encounter a problem, please check this list
to determine if your problem is on this list.  If the problem is
not on this list, please fill out a Bug Report Form and send it
to McAfee SQA so we can properly investigate the problem.

Bug #  Summary of Problem

43   SCAN doesn't detect viruses in PKLITE-compressed files
       This functionality will be included in the final release
261  Using the /RPTERR option causes 2 error summaries to be displayed in
     the report
       If the /RPTERR option is used in conjunction with the
       /REPORT option and non-critical errors are found, the line
       displaying the count of "Non-critical Error(s)" will be
       printed twice in the report.  This problem will be fixed in
       the final release.
275  SCAN /VIRLIST gives an error message: "No target for scanning was
     specified!"
       SCAN treats /VIRLIST like any other option, and will
       continue with a normal scan after the virus list is
       displayed.  Whether you specify /VIRLIST or not, if you do
       not specify anything to scan, SCAN will display this message
       and exit.
293  SCAN detects viruses in memory after infected files are opened
       When an infected file is opened, either by a DOS command such as
       copy or by a previous execution of SCAN, DOS loads the contents of
       the infected file into it's own buffers.  If SCAN is run
       immediately afterwards, SCAN will find the virus code in the DOS
       buffers, and report that the virus is in memory.  We are currently
       investigating this issue.
309  SCAN fails to find the SCAN.DAT file on the B: drive when SCAN is
     run from a different drive
       When SCAN.EXE and SCAN.DAT are located on the B: drive, but the
       current drive is not the B: drive, SCAN fails to find the SCAN.DAT
       file.   This problem will be fixed in the final release.
323  SCAN /AF creates a corrupted validation file when infected files are
     found
       When SCAN /AF <file> is run to add validation codes, and any of the
       files scanned are infected with viruses, the infected files are
       detected properly, but the validation file created is corrupted -
       subsequent runs of SCAN /AF or SCAN /CF using that file will
       generate an error message.  This problem will be fixed in the final
       release.




Problem Reporting Guide                              Page 5
ͻ
                 McAfee VIRUSCAN 2.00 Beta Bug Report Form                   
ͼ
I.      BETA TESTER CONTACT INFORMATION

                                
Your Name:          __________________________         Date: __________

Name on BBS:        __________________________

Internet Address:   __________________________

Phone Number:       __________________________

FAX Number:         __________________________


II.     PROBLEM IDENTIFICATION (SHORT)


Is this problem listed on the known bug list?:    Yes _____ No _____

                                                  Bug #: ___________

Product(s):     VirusScan for DOS     _____     VShield     _____
                VirusScan for OS/2    _____     VShieldCRC  _____
                VirusScan for Windows _____     CheckShield _____
                Other: __________________________________________

Operating System and Version: ________________________________________________

Network Software and Version: ________________________________________________

System Hardware Description:  ________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

Memory Manager(s):     HIMEM.SYS (version _____)  EMM386 (Version _____)

                       386MAX (version _____)     QEMM   (version _____)

                       Other: __________________________________________

Is the problem reproduceable?   Yes _____    No _____    Sometimes _____         Always      Sometimes






Problem Reporting Guide                              Page 6


A.      DOS and Windows Users:

        Please attach a copy of your CONFIG.SYS, AUTOEXEC.BAT, and MEM /DEBUG
        dump.  Alternatively, use a program like Microsoft System Diagnostics,
        Quarterdeck Manifest, or Norton SysInfo to generate a complete report
        of your system and attach the report file.


B.      IBM OS/2 Users:

        Please attach a copy of your CONFIG.SYS, AUTOEXEC.BAT, and
        STARTUP.CMD files.

III.    PROBLEM IDENTIFICATION (LONG)

Detailed Description of the Problem:
(Please include steps to reproduce the problem if known.)

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________

______________________________________________________________________________
        (Attach more lines if you need them to describe the problem.)


