| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Stop TB
Thread: Help Stop TB Now available for 32 bit windows |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 63
|
|
| Author |
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges: 
|
I'm still getting errors running the x86 version on XP32:
----------------------------------------[error] Process creation failed: (unknown error) - error code 193 (0xc1) The error code 0xC1 is typical for EXEs unable to start because of missing imports. The problem is the import of the following DLLs, that are not present on 'standard' XP systems: IESHIMS.DLL: IEShims_InDllMainContext IEShims_SetRedirectRegistryForThread IEShims_Initialize IEShims_Uninitialize IEShims_GetOriginatingThreadId WER.DLL: WerReportCloseHandle WerReportSetParameter WerReportSubmit WerReportCreate Additionally, there seems to be a problem with the ANSI version of WNetRestoreConnection of MPR.DLL: WNetRestoreConnectionA which is not present on the system either. The UNICODE (W) version is present there. If you need more information/tests, just let me know.  [Edit 5 times, last edit by Mumak at Apr 27, 2016 2:14:03 PM] |
||
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges:
|
Well, the WCG app doesn't implicitly link with the IESHIMS and WER DLLs. According to the tree, these are used by: IEFRAME.DLL <- MSHTML.DLL <- SHDOCVW.DLL <- SHELL32.DLL
----------------------------------------The missing WNetRestoreConnectionA is imported by SHLWAPI.DLL Since those DLLs are delay-loaded perhaps neither of these issues is fatal and the problem is the runtime used. I'm unable to start the app, have tried to load into a debugger, but nothing tells me about the reason why the system won't start it. It seems VC was used with mscoree.dll. I also see some references to combase.dll, which is not present on the system.. [Edit 8 times, last edit by Mumak at Apr 27, 2016 3:17:18 PM] |
||
|
|
RTorpey
Advanced Cruncher Joined: Aug 24, 2005 Post Count: 67 Status: Offline Project Badges: 
|
Similar behavior here - 4 core WinXP running boinc 7.2.47.
All HST wu's fail immediately: 4/27/2016 7:03:33 PM | World Community Grid | [error] Process creation failed: (unknown error) 4/27/2016 7:03:33 PM | World Community Grid | [error] Process creation failed: (unknown error) 4/27/2016 7:03:33 PM | World Community Grid | [error] Process creation failed: (unknown error) 4/27/2016 7:03:33 PM | World Community Grid | [error] Process creation failed: (unknown error) 4/27/2016 7:03:33 PM | World Community Grid | [error] Process creation failed: (unknown error) 4/27/2016 7:03:35 PM | World Community Grid | Computation for task HST1_001246_000001_MT0017_T000_F00073_S00002_0 finished 4/27/2016 7:03:35 PM | World Community Grid | Output file HST1_001246_000001_MT0017_T000_F00073_S00002_0_r1100023719_0 for task HST1_001246_000001_MT0017_T000_F00073_S00002_0 absent 4/27/2016 7:03:35 PM | World Community Grid | Output file HST1_001246_000001_MT0017_T000_F00073_S00002_0_r1100023719_1 for task HST1_001246_000001_MT0017_T000_F00073_S00002_0 absent 4/27/2016 7:03:35 PM | World Community Grid | Output file HST1_001246_000001_MT0017_T000_F00073_S00002_0_r1100023719_2 for task HST1_001246_000001_MT0017_T000_F00073_S00002_0 absent 4/27/2016 7:03:35 PM | World Community Grid | Output file HST1_001246_000001_MT0017_T000_F00073_S00002_0_r1100023719_3 for task HST1_001246_000001_MT0017_T000_F00073_S00002_0 absent 4/27/2016 7:03:35 PM | World Community Grid | Output file HST1_001246_000001_MT0017_T000_F00073_S00002_0_r1100023719_4 for task HST1_001246_000001_MT0017_T000_F00073_S00002_0 absent 4/27/2016 7:03:35 PM | World Community Grid | Output file HST1_001246_000001_MT0017_T000_F00073_S00002_0_r1100023719_5 for task HST1_001246_000001_MT0017_T000_F00073_S00002_0 absent 4/27/2016 7:03:35 PM | World Community Grid | Output file HST1_001246_000001_MT0017_T000_F00073_S00002_0_r1100023719_6 for task HST1_001246_000001_MT0017_T000_F00073_S00002_0 absent |
||
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges: 
|
Copied the executable to a temp directory and added the .exe extension so WinXP would recognize it as an executable. Tried to run it in a cmd window and got the "is not a valid Win32 application" error. Since the application runs on Windows OSes newer than XP, maybe it is something like this:
https://social.msdn.microsoft.com/Forums/en-U...pplication?forum=winforms |
||
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges:
|
OK, I found the problem :-)
----------------------------------------It's the SUBSYSTEM version of the PE header, which is currently set to 6.0 and that prevents it from running on XP. This should be changed to 5.0x via respective linker option (/SUBSYSTEM:WINDOWS,5.01). [Edit 2 times, last edit by Mumak at Apr 28, 2016 10:32:13 AM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
'should'?, but are there technical drawbacks in doing that... slower execution for instance on later Windows OSses at 32 bit. (Don't see members being asked to set the execution to XP compatibility either)
----------------------------------------[Edit 1 times, last edit by SekeRob* at Apr 28, 2016 10:30:48 AM] |
||
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges:
|
I don't think there are any drawbacks. The version 6.0 used by their linker is probably just the default value. VS allows to choose XP targeting (depending on the VS version used).
----------------------------------------This has nothing to do with XP compatibility mode - it just determines the lowest system version required and as long as the program doesn't use any Vista and later specific bindings (which I believe it doesn't) it should be no problem. I think this is rather an attempt of MS to scrap XP. When I change this value to 5 in the HST1 executable, I can run it on XP32. [Edit 1 times, last edit by Mumak at Apr 28, 2016 11:55:46 AM] |
||
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges:
|
Patched the wcgrid_hst1_gromacs_7.16_windows_intelx86 with subsystem=5:
---------------------------------------- Forced the machine to pick up HST1 x86 tasks, which it did immediately (what a coincidence). And guess what? It runs  and runs... 2 tasks now: Will I get a special badge for this?  [Edit 7 times, last edit by Mumak at Apr 28, 2016 12:10:45 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
mumak,
Not being familiar with the tool(s) you're using, I just changed that byte with a hex editor and got, not too surprisingly, "Signature verification failed for wcgrid_hst1_gromacs_7.16_windows_intelx86". Can you tell us a little more detail as to where to get a tool that will not give this problem, please? (Unless the WCG techs are willing to give us formal fix at their end.) Tx. |
||
|
|
Mumak
Senior Cruncher Joined: Dec 7, 2012 Post Count: 477 Status: Offline Project Badges:
|
That's because such a modification requires to update the file checksum too.
----------------------------------------I used the PEInfo tool from here: http://pazera-download.com/development/PEInfo.rar Note, that some browsers might give a warning about this file, but I believe it's safe. Modify the file according to the screenshot I posted, you'll need to right-click on that entry to change it. It will automatically save the file and update the checksum. I was too hoping the techs will notice this and provide a fix it in the application. [Edit 2 times, last edit by Mumak at Apr 29, 2016 5:54:44 AM] |
||
|
|
|