home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!darwin.sura.net!jvnc.net!netnews.upenn.edu!netnews.cc.lehigh.edu!news
- From: gary@sci34hub.sci.com (Gary Heston)
- Newsgroups: comp.virus
- Subject: F-Prot 2.05 on NetWare.... (PC)
- Message-ID: <0008.9209081605.AA21066@barnabas.cert.org>
- Date: 3 Sep 92 20:44:49 GMT
- Sender: virus-l@lehigh.edu
- Lines: 34
- Approved: news@netnews.cc.lehigh.edu
-
- Greetings, all....
-
- I've run into a *very* strange interaction problem. When using
- F-Prot 2.05 to scan a group of servers, it works it's way through five
- servers running NetWare 3.11 without any problem. When it gets to the
- last server, which is the one it's being run from and which has
- NetWare 2.15c installed, it scans merrily along until it hits the
- \public\ms_dos\v500 directory, then locks up *solidly*. I can't even
- toggle the numlock LED, or do a warm boot. It's red switch time.
-
- However, it'll scan a DOS 5 system without any problems at all. I
- tried changing the command line to remove the /all file selection
- switch, with the result that it locks up on a *different* file.
- Actions are identical if run interactively (I've got a user set up on
- each server to attach the other five and kick off F-Prot automatically
- upon login; I run this each morning), scanning all files or
- executables. It's consistent about which files it crashes on; scanning
- all files it doesn't like DOSSHELL.HLP, and locks *every* time. If
- checking executables only, it dies on another file.
-
- Has anyone else seen this? I've been running 2.04a for weeks without
- a glitch, and have dropped back to it until I can figure out what's
- going on. It still runs fine.
-
- My copy of FP-205 was retrieved from uunet, FWIW.
-
- Puzzled;
- Gary
-
- - --
- Gary Heston SCI Systems, Inc. gary@sci34hub.sci.com site admin
- The Chairman of the Board and the CFO speak for SCI. I'm neither.
- The most dangerous person in the world is Jessica Fletcher.
- Everywhere she goes, people die.
-