Atom, thanks for the tip, but I already red this and this is not what I'm asking actually - and I'm politely asking for an example:
This is how the whole command looks in 0.08:
---
cudaHashcat-lite64.exe 9BB326FEA7FB0A0947D25866A1B6CEF6D43E57B5:003537910467133900 -m 1900 -n 10 --pw-skip=240000000000000 --pw-limit=250000000000000 --gpu-watchdog=100 --outfile-format=1 --outfile=70448_351659051384558.txt -1 00010203040506070809 ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1
---
With this command, I'm getting hashcat reporting that it is cracking chunk 24% to 25% (this is important because I use this info in the distributing server), so the server to know that this node is cracking this chunk
Atom, how should the command looks like in hashcat 0.09, so hashcat 0.09 to report me, that this node is cracking the chunk from 24% to 25%? (and the node to stop, on reaching 25-th %)
This is how the whole command looks in 0.08:
---
cudaHashcat-lite64.exe 9BB326FEA7FB0A0947D25866A1B6CEF6D43E57B5:003537910467133900 -m 1900 -n 10 --pw-skip=240000000000000 --pw-limit=250000000000000 --gpu-watchdog=100 --outfile-format=1 --outfile=70448_351659051384558.txt -1 00010203040506070809 ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1
---
With this command, I'm getting hashcat reporting that it is cracking chunk 24% to 25% (this is important because I use this info in the distributing server), so the server to know that this node is cracking this chunk
Atom, how should the command looks like in hashcat 0.09, so hashcat 0.09 to report me, that this node is cracking the chunk from 24% to 25%? (and the node to stop, on reaching 25-th %)