Hi,

I searched the 'net' for BitCollider without knowing its name for a long time. Maybe you should consider better MetaTags for HTML to increase hit rate...

I'm amazed to see your effort to create such a unique program. It's the P2P collector's dream. I use many P2P whereever it's appropriate and it's so common to hit same files with different Names & Hashes (although same size). To eliminiate this there's only one way: by keeping the their 'Hash'es for various P2P programs. Also it's useful to avoid 'fakes' & submit to fake 'engines' like yourselves.

Before BitCollider I tried many hashers where they only calculate one type only which is inefficient. Thanks for the developers of this great program.

To further promote this babe, here's my wishlist:

- STDOUT support for Win/Dos console so that the 'output' can be saved for checking & program can be used within a batch file. Maybe even a 'check' parameter?

- Old FastTrack UUHash support to use with other P2P programs.

- Old but soon to rebirth WinMX Hash support which is included in a program located @ hxxp://www.sharepoint.boo.pl/main.php?module=winmx_mxlinx

Thanks again for the effort & thanks in advance for the response I'll be waiting...

If you use the -p flag you can redirect output to a file, even using cmd.exe

bitcollider.exe -p foo.mp3 > out.txt

What do you have in mind for a 'check' parameter?

Old FastTrack UUHash support is in bitcollider 0.4.0, which you can download from sourceforge. What programs (besides old Kazaa-family versions) use FTUUHash?

Can you point out a specification or implementation source for the WinMX Hash?

Also, the first 20 bytes of the new KZHASH are the old FastTrack 'UUHash' -- except now displayed in hexadecimal rather than Base64. So you certainly could extract the old values from the new Bitcollider output.

- Gordon @ Bitzi

Hi again,

Sorry for the delay of reply:

- 'check' parameter is for 'test'. Say; you redirected & collected the Hashes for different files. And you keep these hashes with the files with ,say, '.txt' extension. If there will be a 'check/test' option like md5sum, advanced checksum verifier... you can therefore CHECK the INTEGRITY of the files you already burned on media. So the hashes serve for 2 purposes: not-redownload & integrity-check. If this -(option) is going to be implemented, I might offer write a win-front-end for the program. (I'm not pro but also not a bad programmer myself).

- for the redirection: I'm not a newbie & a long user of 4DOS & familiar to the concept. If you ever tried the '> out.txt' redirection you'll see that it DIDN'T work not in W9X nor WNT COMMAND/CMD consoles. If you examined the code like I did c++ code use 'sprintf' not 'cout' which is for console output. Sprintf is for streams and I didn't know/bother to modify to code.

- for WinMX hash: there's a program called QuickMX located @ http://www.sharepoint.boo.pl/main.php?module=winmx_mxlinx . But the writer of the program asks for donation which is fine for me but I don't know his opinion about publicizing his code for bitcollider. (I checked the genereated hashes & they're fine). You may suggest just use it then but isn't it better to find all your 'hash' needs in one package like Bitcollider?

- for old Kazaa Hash; thank you both for information & I'll use the version you specified. But I don't want to convert manually hex/base64. I prefer direct output which you mentioned to exist in 0.4.0 version

Thank you for your time to answer & future answers...