11-11-2013, 05:15 PM
hey TrAnn3l...
the problem here is that "." is a valid file in your path. Therefore it is treated as a path to a charset file.
As far as I know... devs are still discussing if charset file paths in *.hcmask files make sense or not. But since the first 4 (optional) sections are considered similar to the -1 -2 -3 -4 from the command line, this was the straightforward approach to use the same parsing/file-handling routines also for hcmask files.
you could rewrite your hcmask file line as:
123456789,?1?d.?1?d.?1?d.?1?d
and it should (hopefully) not report any wrong result
the problem here is that "." is a valid file in your path. Therefore it is treated as a path to a charset file.
As far as I know... devs are still discussing if charset file paths in *.hcmask files make sense or not. But since the first 4 (optional) sections are considered similar to the -1 -2 -3 -4 from the command line, this was the straightforward approach to use the same parsing/file-handling routines also for hcmask files.
you could rewrite your hcmask file line as:
123456789,?1?d.?1?d.?1?d.?1?d
and it should (hopefully) not report any wrong result