Is there is a way to remove the cheats from CB.elf

[vsub]

Not delete them when I load CodeBreaker but remove them from the elf itself and in that way to make the elf smaller and to load faster because now it's loading for ~1 min. and it's FULL of "useless" cheats(for me)....when I'm adding new cheats they are saved to my hdd

[dlanor]

Not delete them when I load CodeBreaker but remove them from the elf itself and in that way to make the elf smaller and to load faster because now it's loading for ~1 min.

I know the feeling, but as far as I know we don't have the necessary tools to change this. It would require two things minimum.

1: A safe way to completely unpack not only the CB elf, but also its internal database.
I'm not sure if the two-stage unpacking used in patching it also completely unfolds the database. I guess only ffgriever may know that.

2: A fully compatible way of editing the database structure, which may be very hard to do right with just hex editing.

and it's FULL of "useless" cheats(for me)....when I'm adding new cheats they are saved to my hdd

The adding of the original 'useless' database contents should only happen on a new install. Once you have the database installed to the partition CodeBreaker made, any alterations you make to that cheat collection will be maintained as you make it. So any deletions you make will be permanent.

At least until the next time CodeBreaker screws up its partition, which I've found it prone to do occasionally. At such times it is necessary to either reinstall it from scratch (losing all your own cheats) or to revive a WinHiip disk backup (probably losing newer cheats).

Lately I have started to do all maintenance of my own cheat codes on a slim PStwo without HDD, and then move those cheats to a fat PS2 with HDD by erasing its old CB partition (using uLE HddManager) and booting with the MC from the slim PStwo inserted. This way I can make CB install my database from the slim's MC to the fat's HDD, and can easily make controlled backup of my code sets by psuPasting the CB save folder from that MC to a PC.

Adding new codes is then always done on the slim PS2, with frequent psuPasted backups to ensure that nothing can get lost. And when I want to use the new codes on the fat PS2 I routinely reinstall it as described. Since everything is backed up elsewhere a reinstall is no longer any big deal to me, as I have nothing to lose by it.

The same method can be used with a single PS2 as well, though then you must disconnect the HDD in order to update a database on MC.

These methods do take a bit of getting used to, but it is a great feeling to be secure in the knowledge that handmade cheats can no longer be lost so easily.

Best regards: dlanor

[vsub]

Thanks for the info and btw do you know if there is a way to make the CB partition smaller,because now it's using 512mb free space and I'm 100% sure that I'll never use more than 5-10mb of it.

[ffgriever]

The simplest way is to unpack it, then remove everything but the main code (or better - overwrite it with zeros) and compress it again. CB should run just fine (though, no cheats and no splash screens).

This could be done with 9.2 cracked, as there is no cb9.3/10 unpacker available to the public (not one that I've heard of). I got all of the versions unpacked, but I didn't publish them due to obvious reasons. I never really did a proper unpacker for these. My patch for 9.3/10 retail versions does not unpack it at all. It just patches the original executable to make it think there is cd/dvd in drive and that it just got a proper key from it. Then it just lets cb unpack/decode itself and after it's unpacked - patches the hdloader launch code in. Why to strain your muscles, while your victim can do everything for you .

This method is noobproof, but quite awkward. Anything else requires some basic knowledge.

[vsub]

The simplest way is to unpack it, then remove everything but the main code (or better - overwrite it with zeros) and compress it again. CB should run just fine (though, no cheats and no splash screens).

Well I can do that if I knew from where to where is the main code or from where to where are the cheats.I've tried to overwrite everything that I think was cheats but in the end I endup with not working app and I did unpack the cracked cb using the auto patcher.
I start the patcher,he unpack cb twice,then I patch it and copy the unpacked patched cb so I can remove the cheats(overwrite them with zeros)and after that to pack it

[dlanor]

This method is noobproof, but quite awkward. Anything else requires some basic knowledge.

At this point it is my duty to warn everyone that when ffgriever says something like "requires some basic knowledge",
you'd better put your thinking hats on to cope with it, and be prepared for some really hard labour...


Best regards: dlanor

[vsub]

At this point it is my duty to warn everyone that when ffgriever says something like "requires some basic knowledge",
you'd better put your thinking hats on to cope with it, and be prepared for some really hard labour...


Best regards: dlanor

Well if it's just offsets/addresses I think I can manage to do it

[Bootlegninja]

At this point it is my duty to warn everyone that when ffgriever says something like "requires some basic knowledge",
you'd better put your thinking hats on to cope with it, and be prepared for some really hard labour...


Best regards: dlanor

Aye. Even advanced users are sore pressed by the instructions left.

@ ffgriever - if you could please, post up the memory address range that we can destroy.

[broodje]

That isn't such a bad idea deleting all the cheats, and only add the ones u need/want.

i just bought this 32MB memory card, but still, its very useful.

[Bootlegninja]

I store mine on a 2GB usb stick, but I'm interested in this to make the program load faster.