Hi all,

I have just posted new prpclient 5.3.2 packages to http://uwin.mine.nu/PRPNet/. This includes a 32-bit XP-compatible Windows build of the prpclient, and PFGW 3.7.8, which adds support for FMA3, so should be somewhat faster on Haswell (and may show a small speedup on Sandy/Ivy Bridge).

As always, post any problems or questions here, or drop me a PM.

Thanks to those who provided binaries for various different platforms.

Cheers

- Iain
____________
Twitter: IainBethune
Proud member of team "Aggie The Pew". Go Aggie!
3073428256125*2^1290000-1 is Prime!

I have an XP machine -- let me go check and see if they run on it.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

I have an XP machine -- let me go check and see if they run on it.

I don't recall that the wwww application was ever available for non-64-bit systems?

I don't recall that the wwww application was ever available for non-64-bit systems?

I still can't run either pfgw32, wwwwcl.exe or wwww.exe on my 32-bit Windows XP machine, with a "is not a valid Win32 program" errors. Any tips for troubleshooting?

Actually, I think that wwwwcl IS supposed to work on 32-bit systems (Thus, we also have wwwwcl64 as a different application). The CPU app required 64-bit for some specific reason, but I thought that wasn't the case with the OpenCL versions for running on a GPU. Indeed, I vaguely recall running wwwwcl on a pair of GTX-460s in a 32-bit XP system some time ago (that system was upgraded to 64-bit Win 7 and different GPUs a while back).

...maybe I am not remembering that correctly???


EDIT: The first few posts by rogue in this thread seem to show that wwwwcl is indeed a 32-bit application.

After the other comments, it's clear that wwww and wwwwcl are not supposed to work on 32 bit XP. pfgw32 almost certainly should, but I'm not sure if FMA will work in 32 bit mode.

After the other comments, it's clear that wwww and wwwwcl are not supposed to work on 32 bit XP. pfgw32 almost certainly should, but I'm not sure if FMA will work in 32 bit mode.

Ouch. Look like everybody missed this conversation.
I'll quote:

"wwwwcl itself was taken from current PrpNet package, but version fields in the header were patched (file offsets 0x140 and 0x148, change 6 to 5). Really, it is already XP-compatible (does not references new Vista+ Win32 APIs) and runs just fine after this change. Only have to install MSVC 2012 Redistributable to get VCOMP11.DLL on my system."

So - wwwwcl is incorrectly linked. If it cannot be rebuilt, just patch the executable header as described.

wwww: FAILS (not compiled for XP) - this is a 64-bit executable (must be renamed to avoid confusion, I think)
llrcuda: FAILS (not compiled for XP) - this is a 64-bit executable too
pfgw32: FAILS (not compiled for XP) - must be patched, like wwwwcl, offsets 0x160 and 0x168.

Also must be noted that MSVC 2012 Runtime is required for pfgw32 and wwwwcl (I've posted a download link on MS few days ago)

AVX/AVX2/FMA really will not work under XP, but problem is not in the bitness but in the OS itself. OS must know how to save new AVX/AVX2 registers. E.g. 32-bit Windows7 is OK. If OS knows this, then it also knows how to turn on AVX module in the CPU (it's disabled by default). Since XP does not knows, AVX(2) will stay disabled. Well-written application will just say that AVX is not available on this CPU.

Next, the distribution is bloated by unused/useless versions of CUDA libraries, although really used versions are only 5.5 and 3.2:
genefercuda.exe - cudart32_55.dll, cufft32_55.dll (and these libraries are not included!)
llrCUDA.exe - cudart64_32_16.dll, cufft64_32_16.dll

genefer32.exe, genefer64.exe and wwww.exe does not have debug information stripped (another few useless megabytes).

I'll take a look at pfgw, but you need to understand the even M$ doesn't support XP anymore.

The genefer and wwww executables shouldn't be larger than 1 MB, so I don't understand what you mean by "few useless megabytes".

So what? All these XP boxes suddenly become rotten?

I'll take a look at pfgw, but you need to understand the even M$ doesn't support XP anymore. It is not high on my priority list to address. As there are thousands of users of pfgw, I'm certain that I would have received numerous other complaints if it others couldn't run it on XP. That implies that they have upgraded.

I'll take a look at pfgw, but you need to understand the even M$ doesn't support XP anymore. It is not high on my priority list to address. As there are thousands of users of pfgw, I'm certain that I would have received numerous other complaints if it others couldn't run it on XP. That implies that they have upgraded.

Regardless of what Microsoft supports, PrimeGrid's current policy is that we support 32 bit XP, as described here. We therefore prefer that apps be compatible with XP-32.

Does Primegrid have a timetable on when support for XP will end so folks can prepare?