AREV 3.1 and virus or tape backup conflicts (AREV Specific)
At 06 NOV 1998 11:49:54AM Geoff wrote:
Does anyone know of any conflicts between AREV and anti-virus software or tape backup software? We are currently having to rebuild a large index about twice a week. We have found no other conflicts in any R/BASIC code that we have written and believe it is either the above problem or possibly a hardware problem. Any suggestions, comments, solutions welcome. Please contact me at:
geoffrc@hotmail.com
At 06 NOV 1998 01:06PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Ltd[/url] wrote:
Is the OV file missing? This can be caused by backup software or AV software. For the former log out before backup for the latter ensure that OV files are not checked.
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 10 NOV 1998 01:23PM Stephen Revelation wrote:
Geoff,
There have been some known problems with ARev and virus scanners. From our website I found the following:
"The problem with virus scanners is that they treat files with *.OV suffixes as OVerlay files (ie. executables). AREV's OVerflow data files are unnecessary targets. Virus scanners interfere with file I/O, and this can cause GFE's or zero byte files if a scan hits an open AREV file, or delays the OV portion of a write which spans LK and OV portions of a file. I'd advise you to exclude the AREV volumes from your virus scan. File corruption is likely if AREV is active or has open files. After hours may be a better time for a scan all together.
It sounds like the virus scanner might be scanning for OV? files, not OVL files. You really only need to look for OVL files. *Old DOS programs sometimes used overlay linkers, which produced .ovl files. Since .ovl files contain code, virus scanners check them. Most virus scanners check all .ov? files, not just all .ovl files. Toggle this and you should not have a problem.
**YOu can use NAV with AREV/OI there is just a setting that you need to use to avoid this problem. NAV assumes that a .ov filr is a a .ovl (dos overlay) file and scans it for virii. Naturally the .ov file does not conform to the .ovl specs and NAV thinks this has a virus. So what you need to do is exclude the scanning for the .ov files."Anyway, as you can see, many of these problems/postings are all similar. Maybe if you don't scan for the .ovl's then you can fix your problem. (I believe NAV stands for Norton Anti-Virus). Also, maybe you are backing up too often or at the wrong time with your tape backup software. This may interfere with locking if backups are being done while users are accessing files.
Regards,
Stephen Revelation