Hi Stefan, > 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
Well, I think all of your questions are answered if I tell you that Kraken-win32 uses the same disk format as the original Kraken does. It needs composit tables on a disk, not the delta format that were distributed via BT. Use Behemoth.py to convert your berlin tables, as described in http://lists.lists.reflextor.com/pipermail/a51/2010-July/000683.html Behemoth will write on a physical device sector-wise. So make sure you don't overwrite your system HDD ;) Perhaps you will have to set up a linux in VirtualBox to write the tables onto the HDD. I didn't try nor port these tools for win32. But the code looks as if it will be no big deal to port them. I didn't use Behemoth/TableConvert since I received the disk already prepared, but I think the process is like this: _____________________________ | index free delta fmt files | <- DL'ed via BT/FTP |_____________________________| || \||/ \/ Behemoth.py <- scans the table files _______|_______ | | _____v______ | |TableConvert| | <- converts table format |____________| | and writes to HDD | | ___v___ ______v______ ( HDD + ) | | <- Behemoth creates config file (indexes) | tables.conf | with all the table offsets (_______) |_____________| | | |______ _______| \/ Kraken <- and kraken needs the config file > 2: Please elaborate on the syntax (and especially your use of > tables.conf (the start of the data sector).) If you have your prepared disk with the decompressed tables generated by Behemoth, you have to change the config file for using with Kraken-win32. Kraken-win32 just opens a "file" as the original linux version of kraken does. On Linux even partitions are available as a file, but on win32 there is just a way to open the disk drive as a whole, but not the partition itself. Thats the reason why there is the PhysicalDrive with a sector offset. (if someone knows a better way, any hint is appreciated :) ) > 3: Even though I use CPU power instead of GPU the binary still needs > aticalcl.dll for some reason. Is this a hardcoded link? I hoped it will just silently fail loading the A5Ati.dll if there is no CAL library available. But case ysou get a runtime error, just rename the A5Ati.dll and Kraken-win32 will use CPU power only. > 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. Okay I will fix it. Thats indeed a little irritating :) > PS: Maybe im just missing the point on why there should be links to > physical drives instead of actual paths. Yeah I think thats the point :) I hope, I explained the reason in the fist paragraph. BR, Georg _______________________________________________ A51 mailing list [email protected] http://lists.lists.reflextor.com/cgi-bin/mailman/listinfo/a51
