I love Windows don’t you? I mean the program can barely stay open long enough before you get one of those cryptic little error popup windows that makes no sense to you and even though you forward the error to Microsoft, you know that no one will ever read it and it won’t happen again until the exact condition is met that made it pop up the first time. Well now there is hope. If you get say error code 50, you can now look it up and find out why you are getting that error code and possibly do something about it.
I for one plan on using this a lot, especially with those hexadecimal ones, just because of how big a pain they are to me. I wish they would just tell you in plain english what had happened and why something went nuts, but they don’t. They want you to feel like an idiot with those 0x000544JB errors that pop up all the time. I have taken Windows courses and even taken an Assembly language course that dealt with registers and even that gave more specific errors than Windows does at times. I think Windows errors can be put into one of two piles, ones that crash the program, and ones that crash the entire system. Neither one is good, and each one is just as confusing as the other.
