Linked by Thom Holwerda on Mon 2nd Apr 2007 21:05 UTC, submitted by Dale Smoker
Thread beginning with comment 226725
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.






Member since:
2006-07-04
"(At least Microsoft are going out of their way to correct this problem though.)"
They're going out of their way only because they sat on their behinds on this bug. This bug could've been patched in any of the Jan, Feb, or March updates, and there would've been no need for a rushed out-of-cycle patch. Atrocious decision making.
Edited 2007-04-02 22:53