FIXED: Error: Not an unsigned 32-bit number

Moderators: Site Moderators, PandeGroup

Re: Returned WU Status shows Error: Not an unsigned 32-bit n

Postby bruce » Mon May 27, 2019 2:51 am

Pick one machine and do a FINISH so that all WUs have been returned and then do a clean-install of FAHClient (deleteing data!) Does the CPUID of the next WU completed on that machine change?
bruce
 
Posts: 22623
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Returned WU Status shows Error: Not an unsigned 32-bit n

Postby toTOW » Mon May 27, 2019 10:08 am

toTOW wrote:All WUs I tested returned 2540BE3FF for CPUID ... and the same value is also returned for every entry when a WU is attempted multiple times ...

This is also the value I see when I use the link provided in first post of this topic ...

Read my answer again ... it applies to the WU tool : https://apps.foldingathome.org/wu

Take this WU, two people attempted to fold it, and both return the same CPUID : https://apps.foldingathome.org/wu?p=117 ... =2637&g=36

In CPU tool, all my machines have correct CPUID : https://apps.foldingathome.org/cpu ...
Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.

FAH-Addict : latest news, tests and reviews about Folding@Home project.

Image
User avatar
toTOW
Site Moderator
 
Posts: 8766
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France

Re: FIXED: Error: Not an unsigned 32-bit number

Postby foldy » Mon May 27, 2019 3:48 pm

In the wu website the CPUID is shortened 2540BE3FF while in the overview website the CPUID is longer e.g. 66ECD15C48E28ED9
So I guess in wu website it is only the Machine ID?
foldy
 
Posts: 1498
Joined: Sat Dec 01, 2012 3:43 pm

Previous

Return to Issues with a specific server

Who is online

Users browsing this forum: No registered users and 2 guests

cron