Samsung phones only from AT&T
Yet another Virex 7.5.x report: Modem problems
We've covered many, many reports of issues with Virex 7.5.x. The latest, from reader Benjamin Doherty, involves the inability to use an iBook's internal modem after installing Virex 7.5.1:
"In late November, I installed Virex 7.5.1 because I assumed that the problems with 7.5 were fixed. Days later, I found that my internal modem on my early model iBook G4 (12" screen) stopped functioning. Not only did it stop functioning, but any attempt to engage the modem through dial up internet access or faxing would freeze the whole machine. I let the machine sit for over an hour once but the machine was still frozen with the spinning pinwheel.
"I sent the computer to AppleCare because I thought that maybe I had blown my modem somehow. I reinstalled OS X before sending it to Apple just to be sure, but because they recommended an archive and install procedure, I ended up preserving the problematic Virex 7.5.1...When I received the iBook back the second time, I still found that the computer would freeze when the modem began to engage.
"I wiped the drive clean and reinstalled OS X plain and with no additions. The modem worked! Then I reinstalled my software, bit by bit, until I again came to the problem [Virex 7.5.1]. Removing Virex 7.5.1 allowed me to dial out. I'm now using Virex 7.2, which is still reliable and functional and -- best of all -- does not break my modem."
Resources
on 10.3.7: my iBook would hang completely while connecting by modem: only
a reboot (ctrl-cmd-power) would get me out.
If I understand the logs correctly, Virex was scanning /dev/null,
which doesn't sound like a wise thing to do. I turned off
background virus detection and active virus detection and all was well,
though of course I'm then not using the product I've paid for. Fairly
extraordinary that such a basic problem should crop up so many months
after initial release, unless perhaps it's related to a very recent OS update.
There is no reference to "modem" in McAfee's knowledge base, so if they
know about this I guess they're not letting on. Consolation: at least with Virex
I don't get the kernel panics I get with Norton, but both packages are worse
than the problem they're supposed to protect you from.
Exactly what is Virex protecting you from? It's not making your life any easier that's for sure.
In my professional opinion dump it.
I agree. I installed 7.5.1 when I had to set up my iBook from scratch (I had cloned the disk, sent the computer in for service, but my clone corrupted on me while waiting for a return, and wouldn't boot, so from scratch we go). I got annoyed when I noticed that they were launching stuff at start-up, even though I told it not to scan at start-up (what, like it can't work unless there's some daemon running 24 hours a day?). Plus, I couldn't figure out how to scan my drive except to drag it to the program's window (how come there's no easy set of options there: scan drive, scan home directory, scan documents, scan other, etc?).
Anyway, went to scan my drive, and some 2 hours later it was still hacking away. I know there's lots of files in OS X, but two hours? And it didn't seem like it was close to being done. Since I wasn't going to let it run the active scanner (see virus, delete all mail, love it!), and its slowness scanning a drive or folder, I figured I'd rarely (never?) use it, so off it came.
I have had the same experience with a Dual G5 Desktop. When trying to send
a fax the cpu hangs with the spinning ball and will not respond to anything
but a hard restart, and then only a SAFE BOOT. After the safe boot I can then
restart normally.
I checked with Applecare and told them the problem occurred with Acrobat
Reader when trying to fax with 7.5.1 Virex installed.
Applecare had no knowledge of any problems with Virex, with Acrobat or with
the built in Fax "capability" They advised Archive and Install, insisting that
would the the only thing that would get the computer working. They were
wrong.
P.S. After getting the computer started I rebooted from an external Drive with
TechTool Pro's eDrive and checked the G5's main boot drive. Everything
tested out OK. !!!!! One interesting item -- while it was doing its testing the
modem fired up (on its own) and sent the fax that had frozen the computer
the day before. I verified this by getting the actual fax from the recipient. It
did all this in the background without any menus or windows displayed.
The only solution I have found is to trash Virext 7.5.1. and I am afraid to
tempt fate and try to fax again, even without Virex installed.
I wonder if the Applecare reps saying they have no knowledge of any problems with Virex, Acrobat, etc., and saying the only fix is an Archive and Install, is the result of Applecare phone support going overseas, to save Apple some bucks. I respect the people of India, etc., where much of this outsourcing winds up, but my experience is that too many of them are lousy at Mac tech support, maybe because Macs are used very little in these countries, so you almost never get someone on the phone who has a Mac at home or at work, and so they have no first-hand experience using Macs. When Applecare phone support was in the US, though often you'd get the very same runaround, at least US-based Mac support increased the chances that the person you reached had some experience with the Mac, or had someone nearby they could ask, and wouldn't throw up their hands at many problems and just tell you to erase and reinstall. I wonder if outsourcing tech support will wind up being a bust for Apple?
After shelling out the bucks for Applecare, I was and AM ticked that the tech
came to the archive and install solution "way to quickly" less than 20 minutes
on the phone -- considering the hours of time it takes to reinstall all ones
software and recreate all the aditional files we rely on. I invested in
Applecare to SAVE me time not pay the salary of some tech who (in my
opinion) was too lazy-arrogant-uninformed-uncaring (pick one) to really
deal with the problem.
since we are only trying not to spread that other system's diseases, clamX seems the smart way to go...
surprise me. This has been one of the most frustrating applications I have
ever had to deal with from Apple. I tried for over a month to get some
relevant information at all levels about it, its problems, and what Apple
intends to do about it but was essentially "stonewalled." Apples only response
at this point seems to be that if you are having problems with 7.5.1, remove
it and go back to 7.2.1. Here is a brief summary of what I know and don't
know (but want to) about it:
- The only support available for Virex, unless you are an Enterprise customer
of McAfee, is email via .MAC.
- So far the only solution that Apple provides is to retreat back to 7.2.1.
- Virex 7.5.1 gives the impression of slowing down the computer it is run on
and seems to trigger conflicts with the operation of the Apple Internal
Modem. It also may trigger other conflicts or problems, including problems
with Microsoft Entourage. It is a suspect application when problems occur.
- This is the second time since the release of 7.5 that Apple has
recommended that users with problems with it revert to 7.5.1.
- Who is responsible for Virex development and fixing it. I have had
comments from both Apple and McAfee denying ownership and each claiming
it is each others responsibility if or when anyone is going to address and fix
the problems with 7.5.1.
- In order to do this properly 7.5.1 must be removed using the uninstall tool
included with the download of 7.5.1.
- After 7.5.1 is removed, the user should repair their disk drive with Disk
Utilities, by booting from another drive or the System Install CD. Both
structure and preferences should be repaired.
- A message to me from Apple describing the procedure in detail for
reverting to Virex 7.2.1 was posted earlier on this forum.
- 7.2.1 also has some problems, especially with Virex updates. I recommend
monitoring software sites such as Version Tracker or MacUpdate weekly for
the updates, downloading them, and applying them manually, rather than
using the Virex internal update tool.
- Moving Virex from its installed location (root directory of the Applications
folder) can create problems, especially update problems.
- So far 7.2.1 has not exhibited for me any of the serious incompatibilities or
interference with OSX 10.3.x that 7.5.1 has. I am currently using OSX 10.3.7.
- The impression my research into this problem, and the response I have
received, leaves me with the strong impression that fixing Virex 7.5.1 is
currently not a high priority issue with either Apple or McAfee.
That about sums up what I know about it. I will be probing at MacWorld for
more information about this issue. Should I discover anything relevant that I
am allowed to mention, I will post an update.
I have excactly the same problem with Virex causing the modem to hang the
Mac.
Also, Virex causes intermittent booting problems. It gets stuck trying to
initialize Internet or file sharing settings.
You would think that Apple would fix this problem ASAP.
apparently no one received my report.
Just curious
Mario
- by lwb52 January 1, 2005 2:49 AM PST
- Virex is "free for .Mac subscribers, and Norton was demanding another year's payment, so I deleted all Norton files & folders, and all of its "Live Update" files, and installed Virex 7.5.x (since it won't install as long as Norton as on the disk too)... STUPID! Now my TiBook won't boot - not even into safe mode or even single-user mode! I can get it into target-disk & open-firmware modes, but deleting everthing labeled Virex still does not help. And I was trying to work on my finals...
- Like this Reply to this comment
-
(13 Comments)Any suggestions would be greatly appreciated!