Re: [boinc_dev] BOINC exit status numbers

2016-06-02 Thread Richard Haselgrove
OK, so the 

Re: [boinc_dev] BOINC exit status numbers

2016-06-02 Thread Richard Haselgrove
Following on from
0xC26B


STATUS_DLL_INIT_FAILED_LOGOFF{DLL Initialization Failed}
The application failed to initialize because the window station is shutting 
down.

David, thanks for cleaning the exit status formatting - that will make it much 
easier to track down the true meaning of these messages.
Rom - I've made a private build to see if catching the 0xC26B case with a 
'will_restart' exit helps. The exit status isn't new - Google searches find 
tasks at sztaki dated January 2014, and CPDN dated August 2013, still unpurged. 
Both those machines are currently running Windows 7, as were the majority of 
the machines discussed in the SETI message board thread.
One additional problem reveals itself in my build from Head - every Event Log 
message is escaped, like

02/06/2016 14:00:54 |  |   
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
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] BOINC exit status numbers

2016-05-28 Thread Richard Haselgrove
BOINC reports and displays exit status on the user web, typically, in a 
negative 64-bit hexadecimal format. Today's trending number is

0xc26b


as in http://setiathome.berkeley.edu/result.php?resultid=4947399120:

Exit status -1073741205 (0xc26b) Unknown error number


If you Google the 64-bit Hex version of the error number, the results you get 
are, exclusively, BOINC task pages or BOINC message board discussions, like 
http://setiathome.berkeley.edu/forum_thread.php?id=79695. But Windows error 
numbers are conventionally represented as 32-bit positive Hex numbers, which 
leads us to a very simple understanding.

0xC26BSTATUS_DLL_INIT_FAILED_LOGOFF{DLL Initialization Failed}
The application failed to initialize because the window station is shutting 
down.

Unless other operating systems require 64-bit error numbers (or Microsoft has 
indicated an intention to switch to 64-bit numbers in the future), could we use 
a 32-bit reporting format, please?
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.