Redump Snes Site

Title: Preservation Through Verification: A Comprehensive Technical Guide to Redumping the Nintendo SNES/SFC Library

Abstract

This paper outlines the methodology, hardware requirements, and theoretical underpinnings required to preserve Nintendo Super Famicom (SNES) software via the "Redump" standard. As optical media preservation has matured, cartridge-based systems require equally rigorous standards to ensure data integrity across international hardware revisions. This document serves as a definitive guide for archivists and hobbyists seeking to contribute valid dumps to the Redump database, focusing on the specific challenges of the SNES architecture, including memory mapping, coprocessor chips, and anti-piracy verification.

---

Phase 3: Verification (The Redump Standard)

Once the file is on the PC:

1. File Extension: Ensure the file uses the .sfc extension (standard for Redump SNES) rather than .smc (Super Magicom), which often implies a 512-byte header is attached (see section 5). redump snes

2. Hash Calculation: Run the following command in a terminal (using certutil on Windows or shasum on Linux):

   sha1sum gamename.sfc
   md5sum gamename.sfc
   

   Redump requires both MD5 and SHA-1 hashes.

3. Internal Checksum Verification: Use uCON64 to check the internal integrity:

   ucon64 --snes gamename.sfc
   

   Look for the output: Checksum: Ok or Checksum: Bad. Phase 3: Verification (The Redump Standard) Once the

   • If Ok: The dump likely matches the intended program logic.
   • If Bad: Verify the PCB region. PAL and NTSC ROMs have different timings. If the cart is an original NTSC and the checksum is bad, verify unused padding bytes.

4. Padding Verification: SNES ROMs come in power-of-2 sizes (1MB, 2MB, 4MB). However, many games are smaller than the chip size (e.g., a 512KB game on a 1MB chip). The remaining space ($000000 to $0FFFFF) may be filled with 00 or FF.

   • The Redump Standard: The dump must reflect the actual chip size, not just the game data size. If a 4MB chip is used for a 1MB game, the dump should be 4MB, with the unused space mirroring the open bus or chip behavior (usually mirroring the first bank).
   • Trimming the ROM (removing padding) invalidates a Redump submission.

Diving into the Dat-o-verse: Why “Redump SNES” is the Gold Standard for Preservation

If you’ve ever downloaded a Super Nintendo ROM, you’ve likely seen the term (Redump) in the filename. To the uninitiated, it looks like just another tag from a release group. But to collectors and preservationists, those seven letters represent the difference between a perfect digital archive and a glitchy, corrupted, or altered piece of history.

Let’s break down what "Redump SNES" actually means, why it matters for your retro gaming experience, and how it fits into the larger world of game preservation.

Community resources & databases

• Redump.org and No-Intro DATs (for reference and matching).
• Preservation-focused communities (rom preservation forums, archival groups).
• Hardware developer threads for dumper firmware updates and chip support.

1. Introduction

The Super Nintendo Entertainment System (SNES), released in 1990 (as Super Famicom in Japan), represents a pivotal era in 16-bit computing. Unlike standard optical media, SNES cartridges contain various integrated circuits (ICs), including mask ROMs, volatile RAM, and specialized coprocessors (DSP, Super FX, SA-1). File Extension: Ensure the file uses the

The historical standard for SNES preservation was the "GoodTools" (GoodSNES), which focused on playability and ROM management. However, the Redump standard prioritizes bit-perfect archival images. The primary distinction lies in the retention of header data (where applicable) and, crucially, the verification of unused data areas (blank padding) and internal checksum consistency.

Using Redump SNES ROMs

Because Redump does not distribute ROMs, you have two legal options:

5. The "Header" Issue

Historically, copier devices like the Super Wild Card added a 512-byte header to the beginning of the ROM file to manage SRAM mapping and region bypassing.

• Redump Policy: The Redump database generally rejects copier headers. Valid dumps should be raw (headerless).
• Detection: If a file size is X mb + 512 bytes, it likely has a copier header.
• Removal:

  ucon64 --strip gamename.sfc
  

  Remove the header before hashing for submission.

8. Handling co‑processor chips and special hardware

• Many SNES games include external chips whose code/data might not be on the main ROM chip or require special handling:
  • Super FX: polygon rendering co‑processor with separate mask ROMs or embedded code.
  • SA‑1: CPU co‑processor with its own ROM/ram mapping.
  • DSP‑1/2/3/4, CX4, and other math/audio/special chips: some use internal microcode not directly accessible; in such cases, preserving the PCB and documenting is essential, and dumps that emulate external chip functionality require correct ROM images and sometimes additional data (or emulation microcode).
• When a co‑processor has ROM on the cartridge, ensure the dumper reads those chips. If not readable, capture as much metadata as possible and consult community resources.