CodeBreaker PS2 File Utility

[misfire]

From the README:

cb2util was made to utilize different file formats of CodeBreaker PS2.

It currently supports:
- Code saves (V7)
- Code saves (V8+/Day1)
- PCB files (upgrades/homebrew/etc)

The features are:
- extract (and optionally decrypt) all cheats from code saves
- encrypt or decrypt PCB files
- convert PCB files into ELF files
- check digital signature on code saves and PCB files

Future versions may include more functionality, of course.

Originally, I was planning to integrate most of this program's features into
CB2crypt, but for several reasons I decided to develop a new portable console
application instead; read the chapter "Scripting", and you'll understand my
decision.

Download cb2util (Win32)

[Lazy Bastard]

Nice; you don't stop, heh. I'll add this to the Downloads section, with proper credit.

[vampirexx]

Thanx to Misfire for this utility,
I cannot use it, is there a gui to read the cheat codes form a .cbc file?

Thanx in advance

[misfire]

Why can't you use it? And why does such a simple tool need a GUI?

[vampirexx]

Sorry... I'm not developer it seems to be a dos-prompt consolle.. how can I read cheat codes inside a .cbc file? Thanx Misfire

[misfire]

IIRC, the tool comes with a README file...

[vampirexx]

Sorry Misfire, this will make you laugh.. but I cannot make it.
I tried the readme but I cannot seem to make it work, does it work on windows7 ?
Thanx

[Lazy Bastard]

vampirexx: You'll need to enter the command prompt before you execute the program.

I've attached a reg file that will add an option to your right-click context menu, called "CMD Prompt Here". After running the reg entry, the command will be installed, and right-clicking in an empty area of any window, and choosing CMD Prompt Here, will bring up a command prompt in the current directory.

After that, follow the directions of the readme.

You don't technically require this modification, but it's very convenient for command-line apps. Additionally, you could look into batch files, and consider scripting various commands and flags if you intend to use this program extensively, but for infrequent to moderate use, the context-menu 'hack' should suffice.

[vampirexx]

Thank you very much I will test it soon!

UUPDATE: I did it!!! It works very well! Thank you Lazy, I thought the cb2util prompt the dos on boot,
instead you have to launch the prompt manually, so I thought it was windows7 problem.

Sorry for my mistake, now I can extract cbc!

[misfire]

All non-interactive console applications need a command interpreter. That's obvious.

Although, cmd.exe is the most stupid thing I've ever seen.

[vampirexx]

Well, you're right Misfire..
but I think no developer people fit better with a gui tool.
Anyway cb2util is easy to use.

Thanx to develop great tools and converters

[misfire]

As for the GUI, it depends on the OS you're used to. Some (typically Windows) users like to have a GUI even for the simplest task (even if it would be nothing more than a handful of input boxes and a button).

Most of my tools only do one specific thing. I concentrate on doing it well rather than worrying about a (superfluous) GUI.

Honestly, I'll never create a GUI-driven program like CB2crypt again. It's way too inflexible. For example, you cannot use it to decrypt many text files with cheat codes in a row. This would be no problem if it was a (portable) console application that takes arguments and is executed by a powerful (scriptable etc.) command interpreter.

[Lazy Bastard]

And someone can always make inflexible GUI frontends for your apps

[vampirexx]

I akways use your converter or sometimes also omniconvert to have codebreaker codes in raw. It is very useful. And very fast to use. You are a linux developer, your best tool is probably the terminal.. or dos prompt using winzozz, so not all the people have the same abilities using such tools. Anyway I understand your point of view and agree even if I cannot compile any application, that a script tool could be easily more functional than a closed gui application. Thanx for your explanation

[misfire]

Yeah, the Bash is my friend.

I got used to terminals when fiddling around with Cygwin some years ago. Now I'm a paid Linux developer and, amongst other things, wrote a lot of bash scripts at work.