This information can be freely reproduced in any medium, as long as the information is unmodified.
This FAQ contains our suggested resolution for the following:
Hence those who installed VirusScan 4.5.1 with older installers are
requested to select a random time to do this update, using the procedure
below.
Installers that were released on or after 03 January, 2002 set up
randomization automatically, albeit in a different way. Make sure that you have tried to uninstall VirusScan via
Start/Settings/Control Panel/Add and Remove Software before you try
this procedure.
Note: It is a good idea to make sure that you are
including hidden files and folders in your search, since different
versions of Windows behave differently. In brief: Open any folder, then
select See Adobe's tutorial (leaving our
site) if you need assistance with showing hidden files.
Alternately, you may do this later; the easiest way to do that is to
use e.g., WinZip to extract the VScan451.MSI file from the Program folder
in vs451um.exe, and use that to install the components you want (just
double-click on the VScan451.MSI icon and follow the prompts). For most
of the options, you'll probably want to select the defaults offered by the
installer. Note that once installed, new components are NOT enabled.
You can enable them by right-clicking on the VirusScan icon in the System
Tray, then selecting Properties, and then selecting the module you want to
enable. Also: after installing, you need to reinstall the
VirusScan Service Pack 1, which can be downloaded from the
download page. Failure to install the Service Pack can
cause serious problems. Just do it! Ok, if you're using an outdated version of the installer, or a current
one that finds an "unexpected" file it couldn't open, here is what's going
on:
It appears that the new engine, 4.1.50, reports some things that its
predecessor did not. In particular, it seems to report files that it is
unable to scan because these files are locked by Windows. While this is an
accurate diagnosis, it probably does not indicate a real problem. For
example, the Windows "swapfile", usually C:\WINDOWS\WIN386.SWP on Win9x
systems, or one of several on NT/Win2000 systems, including:
We've seen some cases where temporary files --- those with
.tmp extentions -- cannot be scanned; to date, we have
not encountered any instances where these files were infected.
There may be other cases; it's too early for us to say at this point just
what this means, but it is unlikely that there would be any viruses in the
aforementioned files.
In any event, you can use a word processor or text editor -- e.g., NotePad
-- to open the VirusScan post-install logfile,
vs451pi.txt, which lives in the C:\VSINSTALL.451 folder.
If, at the bottom of the file it says SCANERROR = 12 and
all the lines in the file that contain the text Error occured
while scanning file only refer to files mentioned above, you're
probably virus-free. If you have any doubts, you can email the
vs451pi.txt file to the U-M VirusBusters team.
If you are having this problem with the 4.1.60 engine, please email me!
To prevent the engine from being re-updated automatically to v.4.1.50,
you need to: At a future date, you can reverse these steps to re-enable the
AutoUpgrade site, when the engine eventually behaves well
with the virus definitions (we hope!)
Issue: When running the U-M Preconfigured
VirusScan 4.5.1 installer (vs451um.exe), a message "Out of environment
space" appears.
Alternately, with an older version of the U-M installer: Modify
CONFIG.SYS to give more environment space. Click here for detailed directions. Issue:
Why does the University offer VirusScan 4.5.1 when the most recent version
of VirusScan is v.6.x?
We will be adding new items as we have time; please feel
free to suggest items that should be included in this FAQ.
-BPB
and
C:\WINDOWS\system32\config\system.LOG.
Last updated:
Tuesday, 05-Nov-2002 08:39:34 EST.
University of Michigan Virus Busters - virus.busters@umich.edu
visits to this page since 25 September 2001 02:32 EDT