- Thread starter El_isra
- Start date
El_isra
Developer
It can be reversed. but for some reason, retail OSDSYS cannot format cloned conquest cards. so MCA should do the trick
Kevstah2004
Member
This works with the Play! emulator?
Memory cards work from a virtual hosted folder instead of .PS2 or . VMC file so i'm not sure if it's able to save the superblock data at all with the ECC/EDC.
MCA copies it in a raw format along with Magicgate, the same as .VME but without encryption? or their both the same format & encrypted?
If we know the signed elf bittable/kci? can't we just paste that back onto the card so it's able to decrypt it if the card isn't official.
Memory cards work from a virtual hosted folder instead of .PS2 or . VMC file so i'm not sure if it's able to save the superblock data at all with the ECC/EDC.
MCA copies it in a raw format along with Magicgate, the same as .VME but without encryption? or their both the same format & encrypted?
If we know the signed elf bittable/kci? can't we just paste that back onto the card so it's able to decrypt it if the card isn't official.
El_isra
Developer
No. Play! does not seem to expose mc1: when running arcade games based on what i've tested. and got 0 response from their discord when I asked about it
Conquest card has no filesystem, raw data. so a raw image should be used to emulate it
MCA does nothing with magicgate, neither it dumps ECC...
Kbit and KC are most likely unrelated, whatever encryption the SoulCalibur2 program is applying, it is unknown to us, it's not the kbit and kc usual stuff, it would be inneficient to send 64 memory card commands to encrypt/decrypt a single page... and I don't see any call to the crypto memory card commands on my monitoring dongle
Whatever is happening here, it's happening on the EE and the mechacon is aiding in providing security information of the conquest card,
I'm probably giving up on resolving the whole mistery due to how nasty the game code is, it uses EE scratchpad for passing parameters to almost every conquest card related operation, and there are a lot of unused functions, heck, even namco placed a decoy DONGLEMAN driver in the dongle.
Anyone can continue working/investigating on this though... https://github.com/israpps/SoulCalibur2-game-unpacker
Kevstah2004
Member
That memory card testor app fails in Play! too complaining about SECRMAN.
I'm using 190j retail bios atm, if apps use extra modules they seem to be needed in the same root folder as the app to run properly, the used memory card modules I had to grab from the extracted rom0: bios folder.
Yeah i'm not overly sure how Play! supports arcade games either, I think it works via virtual mounted usb or hdd images the cdvd driver seems to be rudimental to the point where it won't even load up certain elfs, good luck with any future contributions, death to all drm.
Last edited:
