| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Stop TB
Thread: What determines whether client 7.26 or 7.16 is run & 32-bit vs. 64-bit? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 803 Status: Offline Project Badges: 
|
Couple questions I've noticed on my Windows clients:
----------------------------------------1) Some WUs appear as "Help Stop TB 7.26," while others appear as "Help Stop TB 7.16." Any rationale why an older application would be used? 2) On my Windows 10 box where BOINC is installed to run as a service, the 64-bit HSTB application runs, while on my other Windows 10 box where BOINC is installed regularly and not as a service, the 64-bit HSTB application runs but as a 32-bit process. In Task Manager: wcgrid_hst1_gromacs_7.26_windows_x86_64 vs.wcgrid_hst1_gromacs_7.26_windows_x86_64 (32-bit)
[Edit 2 times, last edit by hchc at Jan 31, 2019 7:31:07 PM] |
||
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 803 Status: Offline Project Badges:
|
Bump. My Win10 box just got two HSTB work units.
----------------------------------------1. T325 that will run 7.16 32-bit version of HSTB, even though my wingman is running "Windows 8.1 x64 Edition" (aka 64-bit). Why is the 32-bit version of 7.16 running instead of 7.26 64-bit??? 2. T300 that will run 7.26 64-bit. My wingman is also running "Windows 8.1 x64 Edition." Edited to Add. Both work units the first wingman just errored out with the infamous: <core_client_version>7.2.47</core_client_version> <![CDATA[ <message> couldn't start app: CreateProcess() failed - A required privilege is not held by the client. (0x522) </message> ]]> error message, using client 7.2.47 from 2014. So because this wingman was using obsolete software, it caused my client to default back to HSTB 7.16 32-bit, which runs slower. Why the heck can't these clients be removed from the user pool until they upgrade? They have a 100% error rate. That said, I still don't know the root cause why one work unit started at 7.16 32-bit and the other at 7.26 64-bit when both wingmen were running 64-bit Windows and client 7.2.47.
[Edit 2 times, last edit by hchc at Oct 7, 2019 10:00:03 PM] |
||
|
|
|