it does not work.
By firing "from scratch" on a clean script for the scope --keyspace 01000000000000000: 01FFFFFFFFFFFFFFF --share 41/160, the estimated time is 1.75 months. Using the --continue file which contains the starting point at half of what I initially set (just: in a situation where 50% of the range has already been scanned) - the counter gives 1.75 months. This is not something here .... since I've scanned 50% ... it can not be that it will take as long as it will last as if I started scanning from now on again
The -r option can not be used because it does not work with "- -continue "and not using this option at this level is probably a waste of time.
By firing "from scratch" on a clean script for the scope --keyspace 01000000000000000: 01FFFFFFFFFFFFFFF --share 41/160, the estimated time is 1.75 months. Using the --continue file which contains the starting point at half of what I initially set (just: in a situation where 50% of the range has already been scanned) - the counter gives 1.75 months. This is not something here .... since I've scanned 50% ... it can not be that it will take as long as it will last as if I started scanning from now on again
The -r option can not be used because it does not work with "- -continue "and not using this option at this level is probably a waste of time.Thanks! Fixed respecting the --continue file. Working on the changes for --continue with -r option now.
All changes are in the master branch now and the remaining branch has been removed.
Now everything works as it should! After changing the change of the exe file - it shows (probably) correctly the remaining time which in my case shortened from 1.75 to 1.2 month. Well, just a little suggestion that it would look like this: X months X days X hours X minutes instead of the current x.xx months, because in practice I do not know how to understand the period 1.75 months or the currently displayed 1.2 months in days ?
Thank you for a good job! For sure I will remember about you in the progress of the finds :-)