Arkady V.Belousov wrote:
:) We can't protect from such hardware failures (when executed random
pieces of code). :(
Actually, you can. Changing something like this is the difference
between a stable and unstable kernel. BTW -- that wasn't random code
execution. It was an untested piece of code that didn't get executed
because that hardware failure never occurred. How much of the kernel
can any of us say has actually been executed? Are there any hardware
error cases that are not caught in the driver or has just not been
exercised because the error almost never happens?
Pat
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
