I'm wondering why no searches were done for n>1K for bases 56 and 58.

I ran both bases myself for n=1 to n=2500. The web page is correct for all n<=1000. I found 4 additional primes for n=1000-2500. Attached are all of the primes that I found. Here are the 4 new primes:

(56^1698-1)^2-2

(58^1720-1)^2-2

(58^1734+1)^2-2
(58^2354+1)^2-2

I would like to search the bases to n=10K but I could not make cksieve work on my machine. So I just trial-factored in PFGW for the above. Every time I ran cksieve at the command prompt, I got a Windows error message as follows:
[code]
cksieve.exe has stopped working

A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available.
[/code]My machine is 64-bit, the O.S. is Windows 7, and there is 4 GB RAM. It is an Intel I7 running @ 2.67 Ghz. I have checked and even temporarily disabled my AntiVirus to make sure it wasn't being blocked.

Has anyone else had problems running cksieve?

[QUOTE=gd_barnes;477247]I'm wondering why no searches were done for n>1K for bases 56 and 58.

I ran both bases myself for n=1 to n=2500. The web page is correct for all n<=1000. I found 4 additional primes for n=1000-2500. Attached are all of the primes that I found. Here are the 4 new primes:

(56^1698-1)^2-2

(58^1720-1)^2-2

(58^1734+1)^2-2
(58^2354+1)^2-2

I would like to search the bases to n=10K but I could not make cksieve work on my machine. So I just trial-factored in PFGW for the above. Every time I ran cksieve at the command prompt, I got a Windows error message as follows:
[code]
cksieve.exe has stopped working

A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available.
[/code]My machine is 64-bit, the O.S. is Windows 7, and there is 4 GB RAM. It is an Intel I7 running @ 2.67 Ghz. I have checked and even temporarily disabled my AntiVirus to make sure it wasn't being blocked.

Has anyone else had problems running cksieve?[/QUOTE]

Hi Gary, thanks for joining.

I do not know why cksieve is crashing. This is the first that I've heard of anyone having such a problem. Does it crash immediately? What command line arguments are you passing? Can you build from source?

[QUOTE=rogue;477261]Hi Gary, thanks for joining.

I do not know why cksieve is crashing. This is the first that I've heard of anyone having such a problem. Does it crash immediately? What command line arguments are you passing? Can you build from source?[/QUOTE]

[QUOTE=gd_barnes;477247]I'm wondering why no searches were done for n>1K for bases 56 and 58.

I ran both bases myself for n=1 to n=2500. (snip)
I would like to search the bases to n=10K but I could not make cksieve work on my machine. So I just trial-factored in PFGW for the above. Every time I ran cksieve at the command prompt, I got a Windows error message as follows:
[code]
cksieve.exe has stopped working

A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available.
[/code]My machine is 64-bit, the O.S. is Windows 7, and there is 4 GB RAM. It is an Intel I7 running @ 2.67 Ghz. I have checked and even temporarily disabled my AntiVirus to make sure it wasn't being blocked.

Has anyone else had problems running cksieve?[/QUOTE]

I was able to run this on cksieve with no problem. Windows 10 command prompt, version 1.1.4.

[QUOTE=rogue;477261]Hi Gary, thanks for joining.

I do not know why cksieve is crashing. This is the first that I've heard of anyone having such a problem. Does it crash immediately? What command line arguments are you passing? Can you build from source?[/QUOTE]

Yes it crashes immediately. It doesn't matter how I run it or what command line arguments that I give it. I've tried running it both at the command prompt with correct command line arguments (using exactly what you stated on your web page) and without command line arguments at all. I've tried just pressing enter on the file name. I've tried right-clicking on it and choosing "run as administrator". All attempts crash immediately.

I run all versions of sr(x)sieve on this same machine with no problem so I'm very surprised. To check the machine, I just now downloaded the latest version of srsieve. It runs fine.

You would have to give me instructions on building from source. I've never done that.

This is my only Windows machine. Do you have a Linux version?

Edit: Here is the command line arguments that I give it:
cksieve -P1e9 -n1 -N1e5 -b56

[QUOTE=gd_barnes;477291]Yes it crashes immediately. It doesn't matter how I run it or what command line arguments that I give it. I've tried running it both at the command prompt with correct command line arguments (using exactly what you stated on your web page) and without command line arguments at all. I've tried just pressing enter on the file name. I've tried right-clicking on it and choosing "run as administrator". All attempts crash immediately.

I run all versions of sr(x)sieve on this same machine with no problem so I'm very surprised. To check the machine, I just now downloaded the latest version of srsieve. It runs fine.

You would have to give me instructions on building from source. I've never done that.

This is my only Windows machine. Do you have a Linux version?

Edit: Here is the command line arguments that I give it:
cksieve -P1e9 -n1 -N1e5 -b56[/QUOTE]

There is a makefile. It will build for Linux, Mac, and Windows (mingw64) using that makefile. Use "make" from a command prompt after you cd to the directory with the source.

[QUOTE=rogue;477296]There is a makefile. It will build for Linux, Mac, and Windows (mingw64) using that makefile. Use "make" from a command prompt after you cd to the directory with the source.[/QUOTE]

Make or Makefile are not executables so trying to execute them does not work. When I type "make" or "makefile" at the command prompt it just says:
[code]
'make' is not recognized as an internal or external command, operable program or batch file.
[/code]

What does "mingw64" mean? I have not compiled C programs in Windows/Linux before so you are going to have to be very basic here.

Gary,

Here is cksieve compiled for Linux using a generic corei7 arch (meaning it should work for pretty much any corei7 processor). Can you see if this works for you?

Edit: Just to add, it works for me under the Win10 Ubuntu linux shell.

[QUOTE=wombatman;477308]Gary,

Here is cksieve compiled for Linux using a generic corei7 arch (meaning it should work for pretty much any corei7 processor). Can you see if this works for you?

Edit: Just to add, it works for me under the Win10 Ubuntu linux shell.[/QUOTE]

Well none of my Linux machines are I7's. lol I'll try it though. Thanks.

...too many complications these days. Ugh.

[QUOTE=gd_barnes;477309]Well none of my Linux machines are I7's. lol I'll try it though. Thanks.

...too many complications these days. Ugh.[/QUOTE]

If you can tell me what they are, I can re-compile as appropriate :smile:

Actually, here's the most generic 64-bit compilation. So try this one if the other doesn't work.

[QUOTE=wombatman;477314]If you can tell me what they are, I can re-compile as appropriate :smile:

Actually, here's the most generic 64-bit compilation. So try this one if the other doesn't work.[/QUOTE]

Thank you! Unfortunately the first one didn't work and gave two error messages. The second generic version did not work either but only one error message was issued. For the generic version, here is a copy-and-paste of the command that I issued and the error message:

[code]
gary@herford:~/Desktop/Prime/prime/cksieve$ ./cksieve -P10e6 -n1 -N10e3 -b56
./cksieve: /lib/libm.so.6: version `GLIBC_2.15' not found (required by ./cksieve)
gary@herford:~/Desktop/Prime/prime/cksieve$
[/code]Here are my Linux CPU specs:
[code]
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
stepping : 11
cpu MHz : 2400.000
cache size : 4096 KB
[/code]Essentially an older Intel quad-core Q6600 running at 2.4 Ghz.

Edit: I'm running an old Ubuntu O.S. I feel like this may not work. I think a Windows version that is compatible with my I7 would be better. I really don't want to have to get into upgrading O.S.'s.

Lucky for you I'm taking tomorrow off from work, so here's a Windows version compiled with the generic x86-64 GCC flags. Try it out and see if it works for you. :smile: