What about this from Richard Haselgrove [[email protected]]: Windows system error codes seem to be in ntstatus.h Searching led me to http://www.microsoft.com/en-us/download/details.aspx?id=985 Although branded as an Exchange Server tool, it seems to cover operating systems too. From the small print: "Use the Error Code Lookup tool to determine error values from decimal and hexadecimal error codes in Microsoft Windows® operating systems." It's not a tool I would recommend to an end-user, but it seems to be a quick and easy aid to troubleshooting for those of us who spend time on help-desks. It has our OP's error: C:\Downloads\Err>err 0xc0000135 # for hex 0xc0000135 / decimal -1073741515 : STATUS_DLL_NOT_FOUND ntstatus.h # {Unable To Locate Component} # This application has failed to start because %hs was not # found. Re-installing the application may fix this problem. # 1 matches found for "0xc0000135"
It is exactly right. If worse came to worse, Boinc could perhaps call it as an external process and pipe back the results to itself. It is not something that happens often. Charles Elliott > -----Original Message----- > From: [email protected] [mailto:boinc_dev- > [email protected]] On Behalf Of David Anderson > Sent: Friday, August 10, 2012 2:55 PM > To: Rom Walton > Cc: [email protected] > Subject: Re: [boinc_dev] Error Messages > > OK, then we're using it incorrectly. > > Is there a function that maps exit codes to explanation strings? > > On 10-Aug-2012 11:54 AM, Rom Walton wrote: > > We are using FormatMessage correctly. However, the code we are > > passing it is not a value we get from GetLastError(), we are passing > > it a value being returned from GetExitCodeProcess(). > > > > ----- Rom > > > > -----Original Message----- From: David Anderson > > [mailto:[email protected]] Sent: Friday, August 10, 2012 2:30 PM > To: > > [email protected]; Rom Walton Subject: Re: [boinc_dev] Error > > Messages > > > > Windows supplies a function for converting numeric error codes to > > human-readable strings: FormatMessage(): > > http://msdn.microsoft.com/en- > us/library/windows/desktop/ms679351%28v=v > > s.85%29.aspx > > > > BOINC calls this when appropriate and shows the result. In this case > > it seems to be return an empty string for 0xc0000135. Rom, can you > > verify that we're calling FormatMessage() correctly? > > > > -- David > > > > On 09-Aug-2012 8:22 AM, Nicolás Alvarez wrote: > > > >> 0xc0000135 is a Windows error code, not a BOINC error code. That > >> number is the only information BOINC receives from Windows, so it'd > >> be hard for it to tell the user "what exactly is wrong and how to > fix it". > >> > > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
