Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
todo [2026/04/18 14:54] – GBA e-Reader page created xprismtodo [2026/04/30 22:19] (current) – [Unsorted] hiccup
Line 27: Line 27:
   * Vita: look into https://github.com/Prominos/NoGrw0Write and https://github.com/oestriot/GcToolKit   * Vita: look into https://github.com/Prominos/NoGrw0Write and https://github.com/oestriot/GcToolKit
   * Re. GBA dumping: "if you have dirty contacts you end up with address lines not working (mirrored data), or the data lines having a bit stuck high/low [not a single bit flip]". may apply to ROM dumping in general too.   * Re. GBA dumping: "if you have dirty contacts you end up with address lines not working (mirrored data), or the data lines having a bit stuck high/low [not a single bit flip]". may apply to ROM dumping in general too.
 +  * 3DS: add something about this tool https://github.com/skawo/GodMode9-with-Cartridge-Fixer
 ===== Add new systems =====  ===== Add new systems ===== 
  
Line 65: Line 66:
   * Add explanations of why the different pieces of info are useful to record to [[submission:general-detailed|Gathering and Submitting Dump Info (Detailed)]].   * Add explanations of why the different pieces of info are useful to record to [[submission:general-detailed|Gathering and Submitting Dump Info (Detailed)]].
   * Hiccup's notes: https://hiccup.miraheze.org/wiki/Notes_to_assist_with_dumping_guides   * Hiccup's notes: https://hiccup.miraheze.org/wiki/Notes_to_assist_with_dumping_guides
-  * It may be a good idea to overdump (dump past the maximum known capacity) from some carts on some systems, to make sure all the ROM is dumped (even if the capacity is written on the ROM chip), and then analyse the overdump to find the actual size. Maybe this is something that could be done by the dumping hardware itself - maybe make suggestion on OSCR github discussions.+  * It may be a good idea to overdump (dump past the maximum known capacity) from some carts on some systems, to make sure all the ROM is dumped (even if the capacity is written on the ROM chip), and then analyse the overdump to find the actual size - maybe using a script. Maybe this is something that could be done by the dumping hardware itself - maybe make suggestion on OSCR github discussions. Would need to decide how much to dump though.
   * Hardware: integrate Lesserkuma's {{ ::cart_reader_dumping_compatibility_chart.xlsx |}}   * Hardware: integrate Lesserkuma's {{ ::cart_reader_dumping_compatibility_chart.xlsx |}}
   * Some carts may have DLC in the save data. Add a note to the dumping guide pages about this.   * Some carts may have DLC in the save data. Add a note to the dumping guide pages about this.
   * Rewritable Hard Disks and Flash Media: add instructions on how to censor personal information without altering the surrounding data structure (e.g. FF/00-out file contents without modifying the filesystem metadata or shifting data)   * Rewritable Hard Disks and Flash Media: add instructions on how to censor personal information without altering the surrounding data structure (e.g. FF/00-out file contents without modifying the filesystem metadata or shifting data)
   * Full PCB documentation/disassembly guide?   * Full PCB documentation/disassembly guide?