| Author |
Message |
|---|
|
|
|
Hello all,
I've successfully done manual sieving using gfnsvocl_w64_2G on one machine, uploaded results and received credit.
However, when attempting to perform another sieve on a different machine, I receive the following error:
"Bad n value 17"
The command I ran was: .\gfnsvocl_w32_2G.exe 17 148568 148570
On Windows 10 powershell (and regular cmd).
I have two GPUs on that machine: Intel HD Graphics and NVIDIA GF940MX with the latest drivers installed.
Anyone have an idea what could be causing this problem? |
|
|
streamVolunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 1033
ID: 301928
Credit: 543,608,970
RAC: 7,830
                         
|
|
Unfortunately, no idea. The code simply checks that argument passed by Windows contains only digits and it's value is within supported range (15-24). There shall be no embedded spaces or special characters. Try to copy-paste command line suggested during reservation.
|
|
|
|
|
|
I've tried that, and tried typing it manually, to no avail.
Perhaps launch it from a batch file? What would be the code for windows?
Maybe try in compatibility mode?
I'll post if anything succeeds.
Thanks! |
|
|
axnVolunteer developer
Send message
Joined: 29 Dec 07
Posts: 285
ID: 16874
Credit: 28,027,106
RAC: 0
            
|
|
Must be an older version of the program with different n limits. Just running the program without any parameter will print the help. What does it say in terms of supported n ? |
|
|
streamVolunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 1033
ID: 301928
Credit: 543,608,970
RAC: 7,830
|
Must be an older version of the program with different n limits. Just running the program without any parameter will print the help. What does it say in terms of supported n ?
No, it's a OpenCL version which based on 'final' codebase, and code is trivial.
int n = atoi(argv[1]);
if(!isnumeric(argv[1]) || (n < 15) || (n > 24))
{
printf("Bad n value %s\n", argv[1]);
usage_exit();
}
Executable is statically linked so it could not be problem with MSVC runtime libraries.
I have now idea what could be wrong on this particular PC.
|
|
|
 Michael Goetz Volunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 14011
ID: 53948
Credit: 433,135,545
RAC: 1,048,224
                         
|
Must be an older version of the program with different n limits. Just running the program without any parameter will print the help. What does it say in terms of supported n ?
No, it's a OpenCL version which based on 'final' codebase, and code is trivial.
int n = atoi(argv[1]);
if(!isnumeric(argv[1]) || (n < 15) || (n > 24))
{
printf("Bad n value %s\n", argv[1]);
usage_exit();
}
Executable is statically linked so it could not be problem with MSVC runtime libraries.
I have now idea what could be wrong on this particular PC.
I do have an idea, but it's a long shot. Complete guess.
The user's account says he's from Israel. Presumably the computer is set up to work in Hebrew. Perhaps that's causing some sort of character set encoding problem where "17" is encoded in some way other than 0x3137? If that's happening, it would look on the screen like "17" but the atoi() and/or isnumeric() functions/macros might not work correctly, depending on the exact libraries it was linked with.
Just a thought. It's the only thing even vaguely plausible I can think of to explain this behavior.
____________
My lucky number is 75898524288+1 |
|
|
Crun-chiVolunteer tester
Send message
Joined: 25 Nov 09
Posts: 3233
ID: 50683
Credit: 151,443,349
RAC: 99,549
               
|
|
Then one should to create bat file and send to them like zip file. In that case program will start correctly?
____________
92*10^1585996-1 NEAR-REPDIGIT PRIME :) :) :)
4 * 650^498101-1 CRUS PRIME
2022202116^131072+1 GENERALIZED FERMAT
Proud member of team Aggie The Pew. Go Aggie! |
|
|
|
|
|
After trying many different things, including changing the path, running from batch, etc... nothing worked.
But then I cloned the source from git and ran it - It works! (on the problematic machine).
Unfortunately, I'm unable to locate the problem because I can't reproduce it from source...
I am from Israel, but everything relevant is in English on the machine... |
|
|
|
|
|
I think I found the issue.
The binaries work fine on my desktop machine, which runs windows 7. The problematic machine runs windows 10. When I compiled the source, I noticed it requires the Windows 8.1 SDK.
Seeing as the only difference was compiling it on a machine running windows 10, I can only assume it has something to do with it, although I can't imagine how it would influence the interpretation of CLI arguments.
Any ideas? |
|
|
Crun-chiVolunteer tester
Send message
Joined: 25 Nov 09
Posts: 3233
ID: 50683
Credit: 151,443,349
RAC: 99,549
|
I think I found the issue.
The binaries work fine on my desktop machine, which runs windows 7. The problematic machine runs windows 10. When I compiled the source, I noticed it requires the Windows 8.1 SDK.
Seeing as the only difference was compiling it on a machine running windows 10, I can only assume it has something to do with it, although I can't imagine how it would influence the interpretation of CLI arguments.
Any ideas?
But wait, why you in first place compile compiled file? Why you just download file like rest of us, since you use win10?
____________
92*10^1585996-1 NEAR-REPDIGIT PRIME :) :) :)
4 * 650^498101-1 CRUS PRIME
2022202116^131072+1 GENERALIZED FERMAT
Proud member of team Aggie The Pew. Go Aggie! |
|
|
|
|
But wait, why you in first place compile compiled file? Why you just download file like rest of us, since you use win10?
I'm sorry, I don't understand - are you saying that because I'm using Windows 10 I should not have downloaded the binary file? |
|
|
mikey
Send message
Joined: 17 Mar 09
Posts: 1780
ID: 37043
Credit: 788,982,272
RAC: 1,376,513
          
|
But wait, why you in first place compile compiled file? Why you just download file like rest of us, since you use win10?
I'm sorry, I don't understand - are you saying that because I'm using Windows 10 I should not have downloaded the binary file?
No I think he's asking why you 'compiled' anything, it's Windows and it's more point and click or in this case download the file, put in it a directory, run the cmd prompt as an Admin, navigate over to the directory the file is in and run it from the c:\ prompt. |
|
|
|
|
|
Of course I did that - But it didn't work, it gave me the error I described.
To try and locate the cause of the error - that's why I downloaded and compiled the source, with the intent to debug the code - but it just worked. |
|
|
