orlandokrot.blogg.se

Pcsx2 boot.elf
Pcsx2 boot.elf






pcsx2 boot.elf
  1. #PCSX2 BOOT.ELF PDF#
  2. #PCSX2 BOOT.ELF DRIVER#
  3. #PCSX2 BOOT.ELF CODE#
  4. #PCSX2 BOOT.ELF PS2#

Click Open, and then locate your save file that you just downloaded.ĥ. In this tutorial I am using a Kingdom Hearts Save.ģ. Find the game you want from and download the save file.

#PCSX2 BOOT.ELF PS2#

(NOTE: This also works for Memory Card Dumps from the PS2)īoot.ELF and PS2 Save Builder are located in the " memcardsave.rar " fileġ.

#PCSX2 BOOT.ELF PDF#

Microsoft Word And PDF Version have photos to go along with them The 'Namco MOTHER PCB' would need to be emulated, and this is a large board that would likely require some real skill to do.Creating Game Saves from GameFAQ and other sources for PCSX2 This looks like it's probably just some memories, so shouldn't be too hard to add into the emulator. The RAM32 PCB that it loads CDROM data into needs to be sorted. It's worth noting that even if this gets solved, there are still some other problems: I'd like to understand exactly how the magicgate chip is able to decrypt a single file, and also why the encryption algorithm leaves pretty much plain text at the end of boot.bin. I've heard that the boot.bin files have unique 32 bytes that ties them into the magicgate encryption chip on the donglee? Could we maybe jump past boot.bin, and just load the right file directly? I'm interested to see how this would work, and what the 'other' file is that is lamely xored.

pcsx2 boot.elf pcsx2 boot.elf

only boot.bin is affected by magic gate on system246, it loads another file within the FS which is a lamely xored ELF file, and that one is the game boot.When extracting boot.bin and looking at it, there is a lot of what looks like possibly encrpyted/compressed data with some words that are broken up.

#PCSX2 BOOT.ELF CODE#

The python source code for mymc.py which can list these files is here: This contains some files that are clearly ELFs (TK4GAME for example), and others that I'm unsure what format they are (boot.bin, TK4LOAD). The memory card dump can be displayed, and so the entire thing isn't encrypted. I am aware that there is some sort of magicgate protection applied to these memory cards, but I am unaware at what level this is applied or how it works. So my question is, what about `boot.bin` in the arcade dongle dump is not right? What makes a file 'right'? It'll also display this if you change `mc0:boot.bin` to something that it has on the room e.g `rom0:TESTMODE`, as it can access it but it's not 'right' (whatever right means).

#PCSX2 BOOT.ELF DRIVER#

When it cannot load this file it'll display a series of different error messages depending on why:ĭongle Driver Load Fail - I made it display this by changing mc0:boot.bin to cdrom0:boot.bin, you can guess what this means.ĭongle Card Does Not Exist or Is Not Right - It will display this if there is no memory card inserted, or one that is 'curroupted'.īoot File Not Exit - It'll display this with a blank memory card inserted.īoot File Is Not Right - It'll display this when an arcade dongle dump is inserted. This is boot.bin on the memory card in slot one. The program the bios will try to load is `mc0:boot.bin`. For example `rom0:TESTMODE` refers to a TESTMODE binary in the bios (the test mode binary just displays colour bars), `mc0:boot.bin` refers to a file called boot.bin on a memory card in the first slot. The bios loads from the memory card in slot one, so make sure you insert it there in the emulator.Īs a side note: In the bios it refers to files with the medium they are on, a colon and then the file name. Images of the dongles can be found here: After the BIOS boots, it tries to load a program from the 'dongle' which is a magicgate memory card.








Pcsx2 boot.elf