Sounds like you're working with a fast hash?
If so, and if your list of rules is just as you show - only four rules long - then that may be part of the reason why. Native hashcat combinator attack (-a 1) can do all of the "combining" within hashcat. If you have to pipe it in from somewhere else, there's not a lot of additional work for the GPU(s) to do. If there were many rules, that would improve the speed.
If your rules list is really that short, you might be better off just running them one at a time:
If so, and if your list of rules is just as you show - only four rules long - then that may be part of the reason why. Native hashcat combinator attack (-a 1) can do all of the "combining" within hashcat. If you have to pipe it in from somewhere else, there's not a lot of additional work for the GPU(s) to do. If there were many rules, that would improve the speed.
If your rules list is really that short, you might be better off just running them one at a time:
Code:
hashcat64.exe -m 99999 -a 1 combi.hash combi.dict combi.dict -k '$0 $0'
hashcat64.exe -m 99999 -a 1 combi.hash combi.dict combi.dict -k '$1 $1'
hashcat64.exe -m 99999 -a 1 combi.hash combi.dict combi.dict -k '$2 $2'
hashcat64.exe -m 99999 -a 1 combi.hash combi.dict combi.dict -k '$3 $3'
~