miligp.blogg.se

• #View microsoft error reporting driver

"Hi", "Just a moment" have replaced "Installing Knutsen Valve Protocol", "Step 11 of 47 - 2%" First, displaying a lengthy dump of hexadecimal and errors only an IT person can understand makes Windows look "hard".Īs we all know, Windows has spent the last 10 years trying to look simple and friendly. I agree with the OP, but I think the explanation is two-fold. Most error-catching code consists of things like: After all, it didn't happen on the developer's system, right?

#View microsoft error reporting driver

It's probably not rewarding to put that much effort into a device driver when you truly, truly believe it's never going to encounter any of these problems in real life. And putting in plain-language error codes would require "Internationalization" - there would have to be code to process the error, check the local region settings, select a language, and so on. My best guess? It's because English is probably not the programmer's native language. Some days I feel like a detective putting together small bits of information. The error codes can you tell you that much. Why can't the errors be more descriptive, like "this component failed, the software didn't load because of such and such"? Obviously they know there was a problem. I hate the generic "something went wrong, here's a useless error code".