I think that the only problem here is that you already cracked this particular hash and hence oclHashcat won't crack it again and again.
If you *do not* enable the --potfile-disable switch, hashes that were already cracked, will be removed with the help of the file "cudaHashcat.pot" (in your case).
So you can try to run this:
cudaHashcat64.exe -m 400 -o crack.txt --potfile-disable example400.hash example.dict
and the crack.txt shouldn't be empty anymore.
P.s. you could also simply delete cudaHashcat.pot (but this is not recommended in general).
If you are looking carefully at the output of cudaHashcat64.exe you would also see something like this:
"INFO: removed 1 hash found in pot file"
if this is the case (without --potfile-disable in your particular example), then the hash would be removed from the internal state of oclHashcat and it won't be considered again for cracking.
Also always look at the status line, in your case (1 hash only) it should always say:
Status.........: Cracked
If you *do not* enable the --potfile-disable switch, hashes that were already cracked, will be removed with the help of the file "cudaHashcat.pot" (in your case).
So you can try to run this:
cudaHashcat64.exe -m 400 -o crack.txt --potfile-disable example400.hash example.dict
and the crack.txt shouldn't be empty anymore.
P.s. you could also simply delete cudaHashcat.pot (but this is not recommended in general).
If you are looking carefully at the output of cudaHashcat64.exe you would also see something like this:
"INFO: removed 1 hash found in pot file"
if this is the case (without --potfile-disable in your particular example), then the hash would be removed from the internal state of oclHashcat and it won't be considered again for cracking.
Also always look at the status line, in your case (1 hash only) it should always say:
Status.........: Cracked