Linked by Thom Holwerda on Mon 2nd Jul 2012 18:19 UTC, submitted by anonymous
Permalink for comment 524947
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2006-06-09
While running Windows, remove your system SATA disk/ssd and check how it works fine.
Now imagine that instead of human removal the cause is disk controler going crazy sometimes, not definitively. Or it's manufacturer driver is immature and don't have this quicky hardware workaround (disclaimer: all kernel crashes appearing in this comment are fictitious. Any resemblance to real ones, pending or past, is purely coincidental...)
How do you get enough data to discover the root cause?
Plus, please notice that Haiku don't have the resources Microsoft had to wrote its Windows kernel, and still it took a lot of time to reach a mature kernel crash features set. And calling the bluescreen a mature kernel debugger is kinda funny, BTW...
Edited 2012-07-03 09:39 UTC