McAfee VIRUSCAN 2.0.0 Public Beta Problem Reporting Guide (REPGUIDE.TXT) Author: David Pierce Last Update: 3/16/94 Printed: 3/16/94 Thank you for participating in the McAfee VIRUSCAN 2.0 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.0.0 Beta A * 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@cinnamon.McAfee.COM FAX: (408) 970-9727 (Address FAXes to to SQA) BBS: (408) 988 4004 User: VS20BETA SUPPORT Mailing Address: ATTN: SQA 2710 Walsh Avenue Suite 200 Santa Clara, CA 95051-0963 ------------------------------- 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, 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 VIRUSCAN and OS/2 SCAN 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 GENESIS has been changed from the list used by the old VIRUSCAN. The new list of standard extensions includes the following extensions: .EXE, .COM, .SYS, .DLL, .OV?, and .BIN * In order to minimize memory usage, VSHIELD uses a different data file format than VIRUSCAN. 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 VIRUSCAN, 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 if executable may be corrupted" Files which cause this message to be generated are 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. VIRUSCAN 2.0.0 Beta A Known Bugs ============================== The following bugs are known to exist in the Beta A version of McAfee VIRUSCAN 2.0 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. 276 SCAN displays "Program Error" if the virus data file (SCAN.DAT) is out of date If your SCAN.DAT file is more than 7 months old, SCAN displays the message "Program Error" 5 times, and then continues to scan normally. Since the data file sent with the Beta release is up to date, you will only see this problem if your system date is more than 7 months ahead. This problem will be fixed in the final release. 279 SCAN does not always set the exit code on error SCAN 2.0.0 is designed to return specific error codes to distinguish among more than 15 different error conditions. The Beta A version does not always set the exit code to non-zero when some of these error conditions occur, including when infections are found and when invalid targets are specified. This problem will be fixed in the final release. 292 SCAN /ADN displays summary info for non-existant drives on systems with no network drives If SCAN is run with the /ADN switch on a system with no network drives mapped, SCAN will display summary reports showing 0 files, 1 partition table, and 1 boot sector scanned for drives H:, J:, L:, N:, ... all the way to Z: If you experience this problem on a machine with network drives, please contact us. This problem will be fixed in the final release. 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. OS/2 SCAN 2.0 Beta A Known Bugs =============================== Bug # Summary of Problem ------------------------------------------------------------------------------ 43 OS/2 SCAN doesn't detect viruses in PKLITE compressed files This functionality will be included in the final release VSHIELD 2.0 Beta A Known Bugs =============================== Bug # Summary of Problem ------------------------------------------------------------------------------ 294 VSHIELD /FILEACCESS doesn't prevent all access to infected files When VSHIELD is run with the /FILEACCESS switch, it does not prevent all types of access to infected files. Copy operations are prevented, but infected files can still be read into some file editors. This problem will be fixed in the final release. 295 VSHIELD /IGNORE /FILEACCESS prevents access to files on the ignored drive When VSHIELD is run with both the /IGNORE and /FILEACCESS options, it prevents access to files on the drive which is supposed to be ignored, including files which are not infected. VSHIELD does not display any messages indicating that access was blocked. VSHIELD behaves similarly when run with both the /ONLY and /FILEACCESS options, preventing access to files on all drives other than the one(s) specified. This problem will be fixed in the final release. =============================================================================== McAfee VIRUSCAN 2.0 Beta Bug Report Form =============================================================================== Your Name: __________________________ Date: __________ BBS Account: __________________________ Internet Address: __________________________ Phone Number: _____________________ FAX Number: _____________________ ============================================================================== Is this problem listed on the known bug list?: Yes No Bug #: ___________ Product(s): SCAN OS/2 SCAN VSHIELD VSHLDCRC CHKSHLD Operating System and Version: ________________________________________________ Network Software and Version: ________________________________________________ System Hardware Description: ________________________________________________ Memory Manager(s): HIMEM.SYS EMM386 386MAX (version _____) QEMM (version _____) Other: _________________________________________ Is the problem reproduceable? No Always Sometimes ============================================================================== Detailed Description of the Problem: (Please include steps to reproduce the problem if known) ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________