A few things I'd like to fork out from Marshall's thread. Yes, .n64 is just plaintext of the input data with a header. Edit: I was thinking of .a64. However, with plain EEP 4k/16k you can just cut the save out of the file with a hex editor, with SRAM it's compressed as mentioned in the thread, so the compression format would have to be reversed. I don't think that's the case, but maybe you can show proof that it is actually compressed. A similar idea, but a better one I think: using libdragon by DragonMinded and the toolchain provided with it, write minimal c program to do dump the saves onto the mempak (perhaps with a checksum at the end to ensure integrity), and then load it using gsuploader by ppcasm. Although, it doesn't yet have any "easy" ways of reading SRAM/FlashRAM, that should still be doable with some work. Perhaps even just dump it to the PC over the parallel port. I'll write up some code in a bit just as a proof of concept to dump EEPROMs straight onto the mempak if you'd like, but to another point of the thread... Edit: here's the sample program, http://pastebin.com/Q6vBCCj5 Edit 2: note that will overwrite whatever is in the mempak, probably a good idea to back the mempak up first. It seems to me like there are some people out there that would appreciate being able to dump their saves, and I wouldn't mind looking into this, but I don't have a gameshark to test stuff on (one with a working parallel port), so, if anyone is willing to test code for the purposes of backing up save data, stop by #n64dev @ efnet and I'll try and set something up.