[aldostools]

FYI I have integrated this awesome tool by MAGiC333X to my BruteForce tool 2.2.0

[H3avyRa1n]

Originally Posted by aldostools FYI I have integrated this awesome tool by MAGiC333X to my BruteForce tool 2.2.0

way to go, love your work.

[stussy1]

dont no what it does but if its good for the community its good for me
might try it one day
oh just checked your cpu what a quensident my ones running at
the same clock

[MAGiC333X]

Hi all!

I've just released version 1.1 of my tool.

Forum-attachment link in first post, or here: klicencebruteforce-1.1 (MediaFire).

Changes:
Version 1.1 (October 7, 2012)
- Keys stored as hex-strings in keydata file will now be found
- Added option to select search mode (see USAGE for directions)
- Flushing output of progress updates to allow for better integration
- Performance increase (~40%)

[H3avyRa1n]

Originally Posted by MAGiC333X Hi all! I've just released version 1.1 of my tool. Forum-attachment link in first post, or here: klicencebruteforce-1.1 (MediaFire). Changes: Version 1.1 (October 7, 2012) - Keys stored as hex-strings in keydata file will now be found - Added option to select search mode (see USAGE for directions) - Flushing output of progress updates to allow for better integration - Performance increase (~40%)

great! thanks.

[MAGiC333X]

Hi,

Just released version 1.2 of my KLicence Brute-force Tool.
See first post for forum-attachment, of download here.


Changes:
Version 1.2 (October 7, 2012)
- Removed restriction on hex-string search mode
- (BugFix) Found hex-string is now displayed, instead of data at address

[GregoryRasputin]

MAGIC333X has updated hisKLicence Brute-force Tool, here is a quote of the changes:[quote]Hi all!

... [Read More]


You can download the update and view the release thread here:
[Released] KLicence Brute-force Tool - by MAGIC333X

[KDSBest]

770000 on a debug compiled version or released?

Released is faster than debug, way faster .
Dolphin Debug 40 Frames, Dolphin Release 100+ Frames

So I really recomment you to try a release build.
If it was release build just don't care my **** .

2. Running 4 instance should be slower than Threader. Since you got a OS overhead to manage them properly.

3.

#pragma once

should be cleaner than

#if 0 //fixes MS VC++ 2010 Express PCH warning
#endif

Other way:
For me the error didn't occure because my solution doesn't use precompiled header. You have to turn that off, don't remember where this crap ist.

4. a uint64_t is a unsigned long long or unsigned __int64. In case you want to get rid of that warning. The warning is only crucial if it comes to big numbers. Which might happen I didn't read through the whole code. I'm just bored and wanted to give my 2 cents.

Thanks for doing this tool.
I don't need it but this will help some people I guess. Well done

[Kurto2021]

any chance someone can teach me how to use it.

I have literally blown the dust off my PS3 ... first time it was fired up in almost a year. I have the disc uncharted 3 .... copied it to the HDD of the PS3 then I can ftp into it and pull down files. I was assuming all I needed to pull down was the eboot.bin but I have no clue.

[MAGiC333X]

Originally Posted by KDSBest 770000 on a debug compiled version or released? Released is faster than debug, way faster . Dolphin Debug 40 Frames, Dolphin Release 100+ Frames

It is a release build, but it's a great tip though!
When i first tried a release version, i was pretty amazed by the difference. Speed about doubled
Btw, new version does a little over 1 million on my system

Originally Posted by KDSBest 2. Running 4 instance should be slower than Threader. Since you got a OS overhead to manage them properly. 3. #pragma once should be cleaner than #if 0 //fixes MS VC++ 2010 Express PCH warning #endif Other way: For me the error didn't occure because my solution doesn't use precompiled header. You have to turn that off, don't remember where this crap ist.

2. I know about the overhead, but you still get a nice >99% performance increase per core.

3. I tried turning that option off, but couldn't get the errors to go away. Even tried making new solution, turning the option off in the wizard and then adding the source files, but it didn't work for me.

Using '#pragma once' looks cleaner, indeed. But when i was writing this, i was more concerned with getting rid of the errors

Originally Posted by KDSBest 4. a uint64_t is a unsigned long long or unsigned __int64. In case you want to get rid of that warning. The warning is only crucial if it comes to big numbers. Which might happen I didn't read through the whole code. I'm just bored and wanted to give my 2 cents.

The warnings are caused by using 64bit values read from the self file as parameters for functions that accept only 32bit values, here: malloc(), fseek() and fread().
This limits the maximum size of the header to about 2gb, so it shouldn't give any problems.
But thanks for your input!
Just noticed it could really use a couple of sanity checks there