|
-
May 11th, 2001, 10:21 AM
#1
mcafee freezes machines at startup screen
I just bought 3 new machines with the following specs:
Imageworld 6VA693AM mainboard
PIII 866 Mhz processor
128 Mb PC133 RAM
20 Gb HDD (Seagate)
S3 Trio 2d/3d 8 Mb AGP Video
52x CD (generic)
Intel 8255x based PCI Ethernet adapter
Win98 SE
Here is the issue :
Everything loads and runs fine until I install McAfee, I have tried 3 different engines (including latest dat/engine upgrade.) Once McAfee is loaded, the system reboots and if left alone for about 30 minutes to an hour it will finish booting. If I disable McAfee, it boots and runs fine again. I have seen this before and just installed Norton, but I never found a way around it. Now it is happening on all the new PC's from this vendor. Vendor denies responsibility.
I have also reloaded Win98 SE to no avail.
I have also tried it with 98 and McAfee as the only software on the system.
Any ideas would be appreciated.
-
May 11th, 2001, 10:25 AM
#2
I run into the same problem 3 or 4 times every week twelve as well as McAfee seems to want to use the modem (for updating I assume). This will cause the port to remain open and customers coming back complaining the modem is broke. As soon as I disable McAfee everything works great. So if you or anyone else can pass along the fix I too would be appreciative.
-
May 11th, 2001, 10:30 AM
#3
Maybe try editing the Autoexec.bat file and REM out the line McAfee puts in?
-
May 11th, 2001, 10:30 AM
#4
everything has to be a trial on Friday doesn't it. On a whim, I pulled the network card out of the one I am working on, re-enabled McAfee, boots fine now. Might be the drivers for the NIC then right? Have to identify first of course (no obvious name/ID on it.) Thank God for WinDrivers.
-
May 11th, 2001, 10:40 AM
#5
Yep TGIF! Hard to get me to think this time of the day.
-
May 11th, 2001, 11:08 AM
#6
That's one of the reasons I switched to Norton last year.
-
May 11th, 2001, 12:00 PM
#7
OK OK OK.... Sometimes I really hate my job....
I had tried doing what BSOD recommended... yes there is a but, I had disabled McAfee through msconfig, and made the stop at the autoexec.bat to change that too. I never actually tried disabling just the autoexec.bat part - although I have done that in the past. I am able to boot now without problems but I am still stumped on the NIC, it did boot without it and with the autoexec command still in... whatever though... it is working...
soon... time to drink and forget the troubles of the day...
hehehehe
Thanks all
-
May 11th, 2001, 12:04 PM
#8
-
May 11th, 2001, 02:44 PM
#9
Registered User
I've come across this problem at work. The problem is the chipset on the mainboard. Editing the Autoexec will do the trick. F8, go into DOS prompt, and edit there. You don't have to "disable" McAfee in Windows that way. As far as the vendor taking no responsibility, I'm not surprised. "Recommend" that they should go to a different mainboard, and I'll bet the problems go away!
-
May 11th, 2001, 03:39 PM
#10
You mean I actually helped? Yippee!!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks