Recent content by doccaz

Even though the cards themselves have the same hardware, they differ on the keyset used, like the "COH" model used on System 246/256. What are the models on the backs of these cards? Also, I've read that the SCII card doesn't use the standard filesystem. Putting it into a PS2 basically destroys...

Have you tried clearing the network settings on the DIMM menu and setting the IP address again? If it fails to save the info, you might have a busted NetDIMM.

Out of curiosity, can you validate if these bytes are correct for the FileKey and the HeaderData XOR on the boot.bin you provided (this is printed from inside meDecryptDiskContentKey())? Just trying to pinpoint where exactly this is going wrong...

I'm doing it with native Linux and mingw64, patched a couple of things to make it not complain about autotools and some newer GCC complaints. I also compared the resulting binary behavior after compiling it with a (very old) distro to cross-check I didn't make any boo-boos. So far it works fine...

Mine matches these. I also added all the keysets and made them selectable. I think I matched these hex values with the wiki a few dozen times now, but we never know... 8|

Thanks for this. I now have something to compare against :)

So, the "unsign" operation is just pasting those 32 bytes to 0x28? Or would you need to decrypt something using those bytes? Ahh, now that makes sense on why just moving those 32 bytes from the original boot.bin to the new one works. Thanks for the explanation. Weird, I'm getting different...

I did save mine, and if I put back the boot.bin from the backup, it boots as expected :) I still want to get the re-signing thing done correctly though.

About AnthonyPS2: it contains all the ps3mca code (with the wrong keys) and requires the WinUSB drivers (it needs to load the "WinUsb Device" built-in to Win10). It only does 4 things: read from card, read from file, write to card, write to file. No single file manipulation, only full card...

I took a look at those two... The first one is a tool to merge ECC data into dongle images taken from MAME. Not the case here. The second one is interesting. It requires a copy of ps3mca-tool.exe with the proper keys (of course), and libusbK drivers for the PS3 MCA USB adapter (which I found...

So, after quite some time I finally got all the pieces together: COH dongles, the Sony USB reader, and the software. I did compile ps3mca-tool and got it talking to the COH dongles (so I guess I got the correct keys). So, just for kicks I formatted one my spare COH dongles, copied the files...

I found this one almost by accident: https://github.com/elepro/Anthony It appears to be the entire ps3mca tool with the retail keyset and a new GUI for Windows, and it's being actively maintained (see the "AntonyPS2" directory).

That's unusual. A bass channel, maybe? So, I'd gather it's supplied by the regular JVS power connector (the 8-pin JST one) and the amplified audio is out on CN1?

I got a couple of these boards, marked "V329 AMP" I the midst of an auction haul, I'd guess that they're just sound amps judging by the chip on the heatsink, but... What is that yellow jack doing there? Does anyone have the pinouts to these connectors?

I got curious and gave it another shot using another JVS interface and the ODE I mentioned. Tried two HDD images, Battle Gear 3 and Gundam vs Gundam NEXT (which is an 80GB image). I *can* get Battle Gear to start and show "Boot 01" (sometimes "Boot 02" and "Boot 03"), which I believe is just it...