Actually I just remembered the viruses can break current hardware. There are many CPU's out there that can be overclocked in software. The PowerPC 750 (aka G3) cpu using in Apple computers is one of them. And I doubt anyone will try to argue that OCing can kill the cpu.
On 1/23/04 7:40 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > On Fri, 23 Jan 2004 17:07:18 EST, [EMAIL PROTECTED] said: >> I actually saw the refresh issue kill a monitor about 6 years back. NT4.0 >> can't remember the service pack level. It wasn't a virus or DOS hack though >> it was a boneheaded admin. He then plugged that same machine (with the bad >> refresh rates) into another monitor and blew it to. Then he got fired. > > To be fair, if you learned your trade since the advent of multisync monitors, > you may not even be aware that once there were monitors too stupid to put up > an > "out of range" logo if the hsync/vsync was totally bogus. > > It's surprising that 6 years ago, the site had *two* monitors ancient enough > to > be lacking the circuitry to protect them from that error. They were probably > aged enough that they needed replacing anyhow. > > This of course ties into the "user error" discussion on the other thread - is > this > an error that *any* of us could have made, because "You can't toast a > multisync > capable monitor that way"? Who here actually *checks* each monitor they plug > in to make *sure* it's able to multisync? > "The ACLU (American Civil Liberties Union) is the most dangerous organization in the world." Bill O'Reilly on Fox News during the "No Spin Zone" on January 10th 2004 _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
