Virus? Bad programming?

[slopeoaks]

Hello all, just signed up and am pleased to be part of this community of helpful and knowledgable individuals. ok... just trying to motivate someone to help me. (don't mean to insinuate an unappreciation fer other forum members)

Got this message a day or so after installing "Audio Manager" (software) that came with my new evolution MP3 player:

The McAfee Winsock Filter detected that your Windows Sockets protocols were changed or upgraded. The Winsock Filter was reconfigured for these changes. However, you may need to restart your computer in order to access your network or internet connection.

The main thing that worries me is the short beep that came from the system speaker at the time the message came up. :frown: From what I understand about computers system speaker beeps are important and have meanings. (like the single one at startup that means hardware is ok) My comp has been freezing completely since this problem. (ctrl alt del=nada, mouse pointer frozen) Have to hit reset button. This is the first time had freezes within days of each other on this comp, which is bout 6 mos old. (sometimes same day)

Haven't changed BIOS settings or added any hardware in a long time. (ie months) My comp has been very reliable so far. (compared to Win Me, <grimace> ) I'm really pleased with XP Home.

Would grately appreciate knowledge in this area. (Windows sockets protocols?) Or point me in direction of reading related to this problem.

I'm tired, gotta go get some game time in (Mercs) before beddy by.

My comp:
Athlon XP2100+
512MB DDR
Asus A7N8X
GeForce 4 MX440 (I know, I was misleaded by the local comp store and am waiting for Gainward or other good card maker to ship the 5600Ultra)
400W PSU
3 drives
Win XP Home

 

[PowerMacG5]

Originally posted by: slopeoaks
Hello all, just signed up and am pleased to be part of this community of helpful and knowledgable individuals. ok... just trying to motivate someone to help me. (don't mean to insinuate an unappreciation fer other forum members) Got this message a day or so after installing "Audio Manager" (software) that came with my new evolution MP3 player: The McAfee Winsock Filter detected that your Windows Sockets protocols were changed or upgraded. The Winsock Filter was reconfigured for these changes. However, you may need to restart your computer in order to access your network or internet connection. The main thing that worries me is the short beep that came from the system speaker at the time the message came up. :frown: From what I understand about computers system speaker beeps are important and have meanings. (like the single one at startup that means hardware is ok) My comp has been freezing completely since this problem. (ctrl alt del=nada, mouse pointer frozen) Have to hit reset button. This is the first time had freezes within days of each other on this comp, which is bout 6 mos old. (sometimes same day) Haven't changed BIOS settings or added any hardware in a long time. (ie months) My comp has been very reliable so far. (compared to Win Me, <GRIMACE>) I'm really pleased with XP Home. Would grately appreciate knowledge in this area. (Windows sockets protocols?) Or point me in direction of reading related to this problem. I'm tired, gotta go get some game time in (Mercs) before beddy by. My comp: Athlon XP2100+ 512MB DDR Asus A7N8X GeForce 4 MX440 (I know, I was misleaded by the local comp store and am waiting for Gainward or other good card maker to ship the 5600Ultra) 400W PSU 3 drives Win XP Home

Once your booted into Windows, you will not receive beeps from the CMOS. When you hear the short beep when the McAfee box comes up is because when a messagebox pops up in windows, you can have a beep play (notice this is coming from the computer speakers, and not the motherboard speaker). I am not sure why your computer would be freezing (maybe because of McAfee). Most people recommend Symantec products over McAfee. I'm sorry I couldn't be of more assistance.

Oh Yeah, Welcome to the Forums.

 

[slopeoaks]

Thx fer reply KraziKid, but actually the beep was from the "CMOS". Again, that's why I'm worried. I don't know what the Windows Sockets Protocols are, I'm mostly concerned with what the single beep from the onboard computer speaker meant. ie: hardware, BIOS settings wrongly changed by software? I checked and they seem unchanged, although just noticed the FSB spread spectrum is at .50 and will not accept changing to disabled. But anyway, hope I communicated this problem well.

Oh yea, I keep my virus software updated (latest definitions) and run full scan every now and then. (once a month) I don't think Virus scan was running when I got CMOS beep. I keep it off when not on internet and I don't use this comp for email, only my other one.

Anyone knowledgable about audible CMOS messages and/or windows sockets protoocols, please reply with links or direct info. Thx.