Was anyone affected by 2/3/06's major Viri attack?

[Michelle Celio]

So much for such a "huge" Viri attack that was soposted to happen on Friday. I know not of one person that was affected. I think the media made to big a deal out of it.

What is your personal opionion on how the media handeld it?

Were you or anyone you know affected?

[Mike]

So much for such a "huge" Viri attack that was soposted to happen on Friday. I know not of one person that was affected. I think the media made to big a deal out of it.

What is your personal opionion on how the media handeld it?

Were you or anyone you know affected?
The media over-reacting about a topic they know nothing about (technology)?!?!

No way!

;)

[ForgottenSalad]

I love how they do that.

Y2K, anyone?

[Michelle Celio]

Y2K wasn't really a virus, just a programing error on Microsoft.

[ForgottenSalad]

Not saying it was a virus, but referring to mike's post -

"The media over-reacting about a topic they know nothing about (technology)?!?!

No way!"


:P

[Mike]

Y2K wasn't really a virus, just a programing error on Microsoft.
I don't think that it was necessarily Microsoft's problem. I believe the practice of using two spaces for years was started as early as the 60's, when memory was very expensive and the extra bytes could not be afforded.

Nonetheless, I'm going to start gearing up for the media-hype about the Year 2038 problem. Unix timestamps are stored as 32 bit signed integers, counting the number of seconds since January 1, 1970. This will overflow on January 19, 2038. It won't be a problem on your 15GHz quadruple-processor, 30TB hdd, personal computer at the time, since odds are it will use a 64 bit representation. This will only affect embedded systems and computers from this era.

This is all assuming that we get to 2038 before the technological singularity ;)

[Michelle Celio]

I don't think that it was necessarily Microsoft's problem. I believe the practice of using two spaces for years was started as early as the 60's, when memory was very expensive and the extra bytes could not be afforded.

Nonetheless, I'm going to start gearing up for the media-hype about the Year 2038 problem. Unix timestamps are stored as 32 bit signed integers, counting the number of seconds since January 1, 1970. This will overflow on January 19, 2038. It won't be a problem on your 15GHz quadruple-processor, 30TB hdd, personal computer at the time, since odds are it will use a 64 bit representation. This will only affect embedded systems and computers from this era.

This is all assuming that we get to 2038 before the technological singularity ;)
But it's FUN to blame microsoft =]

[Cuog]

I dont know what was supposed to be going on with that virus thing but it didnt matter all 8 HDs for all 4 of my computers were in the process of being reformated anyway since i was upgrading everything

[TheShadow]

I wasn't affected, but I wouldn't be surpised if my Comp. Security professor, a network security admin at UofM hospital, had to deal with a few occurances of it.

[ebmonon36]

I think the media made to big a deal out of it.




It could also be that the media did a good job at alerting the public and they were able to make the necessary updates to their anti-virus software programs to keep the outbreak from happening.
Eric