Hi Georg First of all, Great work on your win32 build! It is highly appreciated.
I have a few questions/suggestions regarding your win32 build. 1: Will you support network shares in the future (if not already? please provide correct syntax for tables.conf if already supported) I know it's not fast, but could become useful 2: Please elaborate on the syntax (and especially your use of tables.conf (the start of the data sector).) Will the binary look for the files in the root directory, or will it recursively go through the directory structure. If so, is it guessing the filesystem used? Does the rest of the fs have to be empty? Maybe it's just me, but wouldn't it be much more convenient to use unc paths here i.e.: Device: c:\tables1 20 Device: d:\tables2 20 instead of internal disknames + partition offset bytes? 3: Even though I use CPU power instead of GPU the binary still needs aticalcl.dll for some reason. Is this a hardcoded link? 4: Something i noticed: when providing a path without a trailing slash ie d:\rainbow , the path to tables.conf is not concatenated correctly: this will become d:\rainbowtables.conf. If you feel like it, add a check here that adds the trailing slash if needed. I'm not saying that you should follow up on these, just suggesting some improvements. Best regards, Stefan PS: Maybe im just missing the point on why there should be links to physical drives instead of actual paths.
_______________________________________________ A51 mailing list [email protected] http://lists.lists.reflextor.com/cgi-bin/mailman/listinfo/a51
