OK thanks.
The integer read after the -r option seems to be a signed byte, can't go beyond 127 (you get a negative range)
Thanks! Fixed in current version.
Nice

I tried this (I am not sure if it does what I think it should

)
./clBitCrack -r 61 -d 1 -b 72 -t 256 -p 2048 --continue hup.txt -o res.txt 1AVJKwzs9AskraJLGHAZPiaZcrpDr1U6AB
And this is what I get in my continue file hup.txt
start=0000000000000000000000000000000000000000000000000000000000000001
next=00000000000000000000000000000000000000000000000000000004A4000001
end=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
blocks=72
threads=256
points=2048
compression=compressed
device=1
elapsed=344463
stride=0000000000000000000000000000000000000000000000000000000000000001
I suppose that in this context, continue file just tell me how many cases I ran .. right?