[QUOTE=rogue;517983]I am no longer managing the search. Please check out [url]http://mfprimes.cba.pl/[/url] to find the contact information for the person coordinating the search.

chroma, I strongly suggest that you add a section to your page regarding "how to" telling users how to participate.[/QUOTE]

Hmmm
Thank you rouge:sorry:

[QUOTE=rogue;517983]
chroma, I strongly suggest that you add a section to your page regarding "how to" telling users how to participate.[/QUOTE]


Thanks!
I added[URL="http://mfprimes.cba.pl/participate.html"] http://mfprimes.cba.pl/participate.html[/URL]

[QUOTE=chroma;518037]Thanks!
I added[URL="http://mfprimes.cba.pl/participate.html"] http://mfprimes.cba.pl/participate.html[/URL][/QUOTE]

Please change the link for mfsieve to [url]https://mersenneforum.org/rogue/mtsieve.html[/url]. mfsieve is built upon the mtsieve framework.

[QUOTE=rogue;518042]Please change the link for mfsieve to [URL]https://mersenneforum.org/rogue/mtsieve.html[/URL]. mfsieve is built upon the mtsieve framework.[/QUOTE]


It's very nice that you've collected all the procedures for sieving into mtsieve framework
But mfsieve.exe does not work:
error: The clCreateComandQueueWithProperties procedure input was not found in the mfsieve.exe library

[QUOTE=chroma;518077]It's very nice that you've collected all the procedures for sieving into mtsieve framework
But mfsieve.exe does not work:
error: The clCreateComandQueueWithProperties procedure input was not found in the mfsieve.exe library[/QUOTE]

Are you trying to use GPU threads? If not, I'll take a look.

[QUOTE=rogue;518081]Are you trying to use GPU threads?.[/QUOTE]


No
The mfsieve can not be started with or without parameters. (also with -h)

[QUOTE=chroma;518108]No
The mfsieve can not be started with or without parameters. (also with -h)[/QUOTE]

Hmm. That doesn't seem right. It shouldn't take that code path unless trying to use GPU threads. I'll look into it.

If you have mingw64 installed, I can tell you how to recompile to avoid that issue. Alternatively you can d/l the AMD SDK and install it.

[QUOTE=rogue;518126]Hmm. That doesn't seem right. It shouldn't take that code path unless trying to use GPU threads. I'll look into it.

If you have mingw64 installed, I can tell you how to recompile to avoid that issue. Alternatively you can d/l the AMD SDK and install it.[/QUOTE]

This occurs when OpenCL.dll is not found at runtime. You will need to install it. If you have mingw64 installed, then you can rebuild with ENABLE_GPU=no in the makefile. The check leading to this error is done when the application is loaded by the OS and before it executes so I have no way to catch and ignore.

[QUOTE=rogue;518130]This occurs when OpenCL.dll is not found at runtime. You will need to install it. If you have mingw64 installed, then you can rebuild with ENABLE_GPU=no in the makefile. The check leading to this error is done when the application is loaded by the OS and before it executes so I have no way to catch and ignore.[/QUOTE]


OpenCL.dl I have 2 times
c: \ Windows \ System32 \ OpenCL.DLL
c: \ Windows \ SysWOW64 \ OpenCL.DLL
Copying it to the folder from mfsieve gives nothing

The link I gave was mfsieve compiled by a lalera. His program works correctly without any additions.
A normal computer user usually does not have any programming tools and wants the program to run on his computer. You should compile your programs so that the program works independently.

Ideally, you would check your compiled programs on a computer without mingw64 and other software tools.

PS. I do not have mingw64 because I'm not a programmer

[QUOTE=chroma;518166]OpenCL.dl I have 2 times
c: \ Windows \ System32 \ OpenCL.DLL
c: \ Windows \ SysWOW64 \ OpenCL.DLL
Copying it to the folder from mfsieve gives nothing

The link I gave was mfsieve compiled by a lalera. His program works correctly without any additions.
A normal computer user usually does not have any programming tools and wants the program to run on his computer. You should compile your programs so that the program works independently.

Ideally, you would check your compiled programs on a computer without mingw64 and other software tools.

PS. I do not have mingw64 because I'm not a programmer[/QUOTE]

He likely compiled with DEBUG=no in the makefile or built an old version that didn't support OpenCL. The software is designed to only use OpenCL if you provide a command line argument to run a thread with OpenCL. I can't help it if Windows chooses to do this verification when the software is loaded rather than letting the software make the decision at runtime.

The software doesn't require any programming tools. Most people that run my software don't have mingw64 installed. I only suggested that in case you were willing to trying building it yourself. I suspect an incompatibility between the OpenCL SDK that I used to build mfsieve and the OpenCL that you have on your computer. I have little control over that.

Here is the build of mfsieve based upon the current mtsieve framework. This build does not have any GPU capabilities.

[QUOTE=rogue;518232]Here is the build of mfsieve based upon the current mtsieve framework. This build does not have any GPU capabilities.[/QUOTE]


Thank you for the next mfsieve compilation.
I did a comparison of 3 mfsieve files
S1 - file compiled by the lalera
S2 - The mfsieve file in mtsieve framework
S3 - the file mfsieve-1.5 last delivered by you

I tested them on different versions of windows 64
Vista w7 w8.1 w10
S1 + + + +
S2 - - - +
S3 ? ? + +

mfsieve from mtsieve framework (S2) works only on w10!

I have w8.1 and the S3 version works flawlessly. On this computer with i7 I could
easily choose the option -W8. However, the calculation time is greater than for the S1 version (4 * 2)
On the computer with w10 the calculation time for S1 and S2 was similar.

Conclusion: On Win 8 and below, I recommend S3 or S1 and for w10 S2.

PS.1. I have corrected the link to mfsieve at mfprimes.cba.pl/participate.html
2 Correct the link in mtsieve.html - Mutifactorial - to the new address mfprimes.cba.pl

[QUOTE=chroma;518287]Thank you for the next mfsieve compilation.
I did a comparison of 3 mfsieve files
S1 - file compiled by the lalera
S2 - The mfsieve file in mtsieve framework
S3 - the file mfsieve-1.5 last delivered by you

I tested them on different versions of windows 64
Vista w7 w8.1 w10
S1 + + + +
S2 - - - +
S3 ? ? + +

mfsieve from mtsieve framework (S2) works only on w10!

I have w8.1 and the S3 version works flawlessly. On this computer with i7 I could
easily choose the option -W8. However, the calculation time is greater than for the S1 version (4 * 2)
On the computer with w10 the calculation time for S1 and S2 was similar.

Conclusion: On Win 8 and below, I recommend S3 or S1 and for w10 S2.

PS.1. I have corrected the link to mfsieve at mfprimes.cba.pl/participate.html
2 Correct the link in mtsieve.html - Mutifactorial - to the new address mfprimes.cba.pl[/QUOTE]

There are other factors in determining overall speed. Assuming you use a single thread, what are the speeds on windows 7 or windows 8?

I suggest that you have links to both, one for the non-GPU enabled version and one for the GPU enabled version.

The mfsieve 1.5 is also from the mtsieve framework. The only difference is that I compiled it with disabled GPU functionality.

BTW, I would never recommend a build of my software that is supplied by a third party. The main reason is that I cannot support it. I can only support software that you get directly from links I provide. If the other software is buggy, I won't be able to fix it.