Linux is faster than windows. Pls note that you have no total runtime in logfile in v2.1

I need to check the code. Maybe we can do something more to support it in the older version.

We are working on a convertion of the latest code to linux which fixes all issues we have found in v2.1, currently is (on windows v2.3 has all the fixes):

- maxNfbncsieve must be greater than 0 for automatic setting (standard 4)

Linux is faster than windows. Pls note that you have no total runtime in logfile in v2.1

maxNfbncsieve=0 is working now for automatic setting, srbsieve was recompiled and fixed in latest source, update package soon

We are working on a v2.3 linux script to avoid any errors which we have found in v2.1. Also some optimizations on the code conversion.

Testing is nearly done with more improvements, v2.3 linux is public soon

v2.3 linux is done, we have found a last minute bug in srbsieve, changelog is coming soon

srbsieve v1.9.2 Changes:

1. Small fix: When you are in extend mode and a worker finds no primes in a single phase, it would sometimes crash with a segmentation fault error. It was caused by the program attempting a comparison on what should have been an inaccessible area of memory. Adding a check for the existence of the file before making the comparison fixed the problem.

2. Most useful: The version number of the program will now be displayed when the program starts.

Important for those running under Linux:

Included in the updated attachment in the first post are updated Linux binaries for srbsieve and srbverify to include all of the latest changes for both programs. The previous binaries were very old and should not be used anymore. Full testing was done by both Reb and me on the binaries.

Note that the Windows executables of both programs are compiled as static while the Linux binaries are compiled as dynamic. If you would like static compiles, let me know and I can provide them.

I got everything fixed on srbsieve_mthd_linux version 2.3. Full testing was done using your new srbsieve and srbverify binaries. Fixes:

1. All workers will now automatically minimize.*
2. All workers should be in order on the taskbar.**
3. Ctrl-C on the main terminal now properly closes all workers and stops their processing.

* Sometimes 1-2 workers may not minimize. I put a 0.25 second sleep command in there that prevented most of the problem. I could make it longer but then it would take a little too long to open and minimize them all if you are running 30+ workers.

** Sometimes workers may be slightly out of order within your taskbar but for the most part they are very much in order. I have observed that this happens on Windows too so it is not a bug. An additional sleep command could probably be added somewhere to prevent it but that would take even more time.

A lot of cleanup was done:

1. Removed all Windows-specific code related to the opening and closing of the workers.
2. Removed the need for a Linux xterm bash script. This is now handled in the srbsieve_mthd program.
3. Rewrote the entire section of code related to the opening and stopping of the workers and handling of Ctrl-C.
4. Program is now completely up to date to version 2.3.

There are some new requirements:
1. Users will need to download the xdotool package for Linux. This allows the workers to be minimized. If they don't do that, it won't hurt anything. They will just have to manually minimize them.
2. The folder where the programs are stored must begin with a capital letter, e.g. Base, Programs, or Files. All other folders are capitalized and this was the way it was originally written by Pokemonlover.
3. pfgw64.exe and srbsieve.exe are no longer needed. Only the applicable Linux binaries are needed.

Download the xdotool package if you don't have it already. The command for Ubuntu is: sudo apt-get install xdotool. This allows the worker windows to run minimized

srbsieve v1.9.3. This affects Linux users only.

There was a small problem only when running in Linux: If PFGW was unable to prove a PRP, the code that made additional attempts to prove the PRP did not run correctly. This resulted in the pl_unknown file when running srbsieve and pl_missing file when running srbverify, which required additional user intervention. That has now been fixed so the files should no longer appear.

There was no functional change to Windows code but the logic that runs through both O.S.s was slightly changed to accommodate Linux processing so there is both an updated Windows executable and Linux binary.

This is a never-ending problem with PFGW. The problem appeared in the latest version 4.1.7. There have been multiple fixes in various GWNUMs over the years but it never goes away entirely so the srbsieve code will always need to be there to prove unproven PRPs.