Originally posted by High Max
Is this problem caused by SCP builds or the fact that my gamepad has some exposed wires sticking out of the black protective coating?
I've heard of a similar problem a while back. Apparently, some guy would flush his toilet, and his computer would restart.
More related, apparently someone was having trouble with their flash reader, performing some action would cause their computer to restart. It was also USB, so I'm guessing it may be some issue in the protocol caused by bad wiring.
Edit: That is, some aspect of the protocol that's exploited by the bad wiring. Although I doubt we'll see "Fix for Bad Wiring Exploit" listed in the next security update for Windows.
It takes at least six months for them to get their act together and form a commitee to discuss possibly forming a subcommitee to investigate forming a sub-sub-commitee to choose developers for the sub-sub-sub-commitee to determine how long it will take to fix the bug. At that point, the answer will be sent back to the first commitee, which will form a sub-commitee to pick qualified individuals from the first sub-sub-commitee to form a second sub-sub-commitee, along with select members from the commitee, that will chose the developers to work on the bug.
At that point, the fix will be sent to marketing, which will flip a coin to decide whether to include the bug in the next update, or to come up with some bull**** excuse like, "It would make us look too progressive."
The decision will be sent back to the commitee.
At this point a team of on-site lawyers will examine the bug, the fix, and all possible grounds that could be used to sue Microsoft, or possibly benefit the end-user, and append legal release notifications to the license agreement.
Finally, once the license agreement modifications are sent back to the commitee, they will forward (in triplicate, due to unpredictable database errors) a request for the addition of the bug to the Windows Update system, under the next Security Update. Two of the three copies will be tagged as spam by the hyperactive junk mail filter on the webmaster's account.
He will in turn forward five copies to the section head of Windows Update, who will forward 2 copies to the subsection head of Security Updates, along with 7 to his assistant, who will be forced to post a memo on the subsection head's favorite bathroom stall because of unpredictable database errors, spam, and a DOS attack from a group of asshats in Kenya.
Finally the subsection head will add it to the Security Updates, unaware that a sneaky little secretary has tampered with the fix and added a buffer overflow error.
And the process starts all over again.
Of course the true tragedy of it all will be that there never was a software bug in the first place, simply some loose wiring, and the 'fix' actually modified a piece of code that hasn't been used since Windows 3.1.
