Hey Rusty,
Just doing my weekly updates & scans on computer & there is a 248MB update called 'Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) x86'

Any input other than don't download unless you have High Speed?

Thanks,
Tere

Sadly, many .net Framework services are called by applications one would think had no relation to those services. Best to download and install, as there are sometimes security patches buried inside - IF you have v3.5 installed (which I doubt). Go to Control Panel/Add or Remove Programs (check the box "Show Updates"), and scroll down to see if Microsoft .NET Framework 3.5 is installed. I doubt you have anything after v2.0 SP1.

So you can ignore it. The next time it show on the download list, you can use the "custom" option and click "hide", so it won't continue to bug you.

I have .NET Framework 3.0 SP1 Installed

Same advice applies? Ignore.
Tere

Ignore!

Hey Rusty. All of a sudden, ever web site that I want to go to has a warning 'This web site may harm your computer'. Do you know what this means? Even the Bartmobile site. Would appreciate your help Jim

quote:

Originally posted by Jim and Tere:
Hey Rusty. All of a sudden, ever web site that I want to go to has a warning 'This web site may harm your computer'. Do you know what this means? Even the Bartmobile site. Would appreciate your help Jim

Help, getting the same message this morning.

Nick

The warning is a Malware Warning page, supposedly by Google. Have we been had?
Tere

Nick/Rusty,
FYI - I switched from Google Chrome over to Internet Explorer to search & had same problem. Then went to Firefox & am not having any problems as of yet.

Tere

Google just released an update to Chrome, and I suspect this is a bug.

More later after I hit the Geeksites.

Well, here's the story:

"Google has now given an account of what happened:

Unfortunately (and here's the human error), the URL of '/' was mistakenly checked in as a value to the file and '/' expands to all URLs. Fortunately, our on-call site reliability team found the problem quickly and reverted the file. Since we push these updates in a staggered and rolling fashion, the errors began appearing between 6:27 a.m. and 6:40 a.m. and began disappearing between 7:10 and 7:25 a.m., so the duration of the problem for any particular user was approximately 40 minutes."

I suspect the problem also extended to users of the Google Toolbar.

This thread once again brings up the issue of peecee security, and I posted here a link to a tutorial for cleansing one's little electronic buddy.