save file of mario 64 for project 64 emulator

Save file of mario 64 for project 64 emulator how to#
Save file of mario 64 for project 64 emulator software#

However, I was unable to find any documentation on how to pull the SRAM data or if it was even accessible from the GameShark. The first thing that I tried was dumping the SRAM by using the GameShark. I contacted Interact and they were unable to provide me with information on the algorithm the GameShark used. Having no idea how it was compressed, I thought I was out of luck. This was useless to me unless I want to use the GameShark to transfer it back to the cartridge. So GameShark compressed it before copying it to the memory pack. That is because I later found out that the SRAM save format was too large for the GameShark to transfer. The only save that I had an issue with was Zelda Ocarina of Time. I simply grafted over the matching bytes from the DexDrive save into the existing save files in my hex editor, loaded them up in my Project 64 emulator, and everything worked without a hitch. I took known game save copies from the internet for each of my EEPROM games and matched them up to my DexDrive save contents.

Each one of the save files was structured in a different way. When examined with a hex editor, I noticed that each file was still there and all I had to do was cut out the bytes that made up the file container. But each save file was wrapped inside a proprietary container.

Once I transferred every game over to the memory pack, I used my Nintendo 64 DexDrive (Pictured below) to move the save files onto my computer. To transfer the EEPROM games, I used a GameShark (I chose v3.2) to transfer the save from my cartridge to the memory pack. I used kodewerx’s Hacking N64 wiki to know what addresses and offsets for the RAM and ROM space I needed. It also allowed me to dump my ram, but that is coming later. This program allowed me to back up each of my games for later use in my project. (Others have tried using GameShark’s software, but it has been problematic.

Save file of mario 64 for project 64 emulator software#

The first thing that I did was dump each game using the GameShark’s parallel port with the open source software N64RD using the command below. I followed a known method by using a DexDrive. Star Wars, Mario Party, and Super Mario 64 use EEPROM to store their game save.

Although this blog post follows the above, an easier method for converting the RAM dumps has been created by Bkacjios.

Graft a new save file from dumped data with a hex editor.

Dump contents of active RAM (with my glorious Pentium III).

Graft a new save file from DexDrive save with a hex editor.

Transfer memory pack data to computer using DexDrive.

Transfer save to memory pack using GameShark.

EEPROM Saves (Star Wars, Mario Party, and Super Mario): I had four games that I needed to get saves off of. To transfer all game saves from my minuscule N64 library into a digital format that I could use on other devices. I created a project with one goal in mind. I got out my N64 and started tinkering with it. So I did what any other dreamy eyed gamer would do. According to the trustworthy Internet, these batteries have a lifespan between 15 and 20 years. It turned out that this was one of a handful of cartridges in the Nintendo 64 library that uses a battery to maintain its save file. If you’d like to learn how to transfer other save files and how I originally dumped my Ocarina of Time save, read on.Ībout a year ago, I discovered that my Ocarina of Time cartridge was on borrowed time. If you are here looking for information on how to dump your N64 Ocarina of Time save files, check out my new guide for it. I remember the fun I had navigating through puzzles and chasing down heart containers. When I was younger, I would spend weekends after school playing through The Legend of Zelda: Ocarina of Time.