Skip to content

Commit a9614de

Browse files
committed
Unrecommend editing save DB on Everdrive
1 parent 20830e2 commit a9614de

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -11,14 +11,14 @@ To use:
1111

1212
## Notes for Everdrive
1313

14-
Locate the `save_db.txt` file in the `ED64` directory on your SD card. Add this line to the CRC detection section:
14+
When you successfully run the dumper, a save file called `pif_rom_dumper.srm` will be created in the `ED64\Saves` directory.
15+
16+
The save type is specified in the header, so it should no longer be necessary to modify `save_db.txt` on Everdrive. For historical reference, this was once done by adding a line in the CRC detection section:
1517

1618
```
1719
0x5716C25D=3 (pif_rom_dumper)
1820
```
1921

20-
When you successfully run the dumper, a save file called `pif_rom_dumper.srm` will be created in the `ED64\Saves` directory.
21-
2222
## Notes for 64drive
2323

2424
I prefer to use the command line tool to send the ROM over USB, set the save type to 256K SRAM, and then read back the SRAM directly.

0 commit comments

Comments
 (0)