Fact-checked by Grok 2 weeks ago

ROM image

A ROM image, also known as a ROM file, is a digital file that serves as an exact binary copy of the data contained within a (ROM) chip from hardware devices such as cartridges, motherboards, or computer . These files replicate the non-volatile contents of the original ROM, preserving the exact byte-for-byte structure without alteration, and are typically stored with a .rom file extension. Common in retro and contexts, ROM images enable the reproduction of software or games originally designed for obsolete hardware. ROM images are created through a process called "dumping," where specialized hardware tools extract the directly from the physical or the entire medium, such as a game or circuit board. This extraction method varies by device—for instance, video game consoles like the (NES) or require readers, while arcade systems involve s from printed circuit boards. The resulting maintains the original layout, including program code, , and sound assets, ensuring fidelity to the source material. Due to the technical nature of dumping, it often demands expertise to avoid corruption or incomplete captures. The primary application of ROM images is in software , where they are loaded into programs to simulate the behavior of original hardware on modern computers, allowing users to run legacy operating systems, , or video games without the physical devices. For example, in via projects like MAME (Multiple Arcade Machine Emulator), ROM images are organized into "sets" comprising multiple files from specific chips, which the combines to recreate the full game environment accurately. Beyond gaming, ROM images support embedded systems development by providing test environments for updates and hardware prototyping. In efforts, ROM images play a crucial role in archiving software-dependent artifacts, particularly , by capturing irreplaceable data from aging media that may degrade or become unreadable on original . paired with ROM images mitigates technological obsolescence, enabling long-term access to materials like classic titles from consoles or arcades when is unavailable. However, file formats can vary significantly by —such as merged single files for consoles versus multi-chip sets for arcades—requiring compatible emulators for proper functionality. This variability underscores the importance of standardized dumping practices in preservation workflows.

Overview

Definition

A ROM image is a that contains an exact of the stored on a (ROM) chip or cartridge, preserving the original bit-for-bit contents without alteration. This replication captures the immutable as it exists on the physical , serving as a portable representation suitable for storage and analysis on computing devices. The key components of a ROM image consist of a raw dump, which typically includes program code for execution, graphics assets for visual rendering, and sound for audio output. In contrast to the physical ROM, a hardware-bound component integrated into devices like cartridges or circuit boards that requires specialized equipment to modify or duplicate, a ROM image exists as a software that decouples the from its original medium, enabling broader accessibility and manipulation in environments. ROM images are commonly associated with contexts such as arcade machines, home video game consoles like the Nintendo Entertainment System (NES) and Sega Genesis, and early personal computers, where they replicate the firmware or game data essential to these systems. They also appear in embedded systems, where ROM images represent firmware that initializes and controls device operations. As a primary use case, ROM images facilitate software emulation, allowing modern hardware to simulate the behavior of legacy systems.

History

The practice of creating ROM images emerged in the among home computer enthusiasts who sought to preserve and back up software from erasable programmable read-only memory (EPROM) chips embedded in cartridges and hardware. Using specialized EPROM programmers, hobbyists would extract the binary data from these chips, often for personal archiving or to replicate functionality on compatible systems. In the , ROM image creation and sharing expanded through systems (BBS) and nascent communities, closely tied to the burgeoning console scene. Early NES emulators, such as the Family Computer Emulator developed in 1990 for the FM Towns PC and iNES released in 1996, relied on dumped ROMs to simulate original hardware, fostering a culture of distribution via file-sharing networks. Milestones included the 1997 release of the first public ROM sets via tools like GoodTools, which standardized verification and organization of ROM collections for various platforms. The 2000s saw further standardization through projects like MAME, which debuted in 1997 and by the decade's midpoint had evolved into a comprehensive for ROMs, promoting organized sets for preservation and play. This period also marked the rise of sites, where out-of-print video games, including ROM images, were archived and shared online, reflecting growing concerns over software obsolescence. From the onward, institutional efforts gained prominence, with organizations like the hosting extensive collections of ROM images for to safeguard . Legal advancements, such as the 2018 U.S. DMCA exemption, permitted libraries, archives, and museums to circumvent controls on lawfully acquired for preservation purposes, provided they were not commercially available and lacked remote content dependencies. Concurrently, modern platforms like integrated retro game collections, allowing users to extract ROM images from purchased compilations for . In October 2024, the U.S. Copyright Office denied proposals to expand the DMCA exemption to permit remote to preserved in libraries and archives. Preservation efforts continued, with organizations like the Video Game History Foundation reporting progress in archiving and advocacy as of 2024. In July 2025, the Council on Library and Information Resources published a guide on as a preservation , emphasizing its role in maintaining to legacy software.

Creation

Dumping Techniques

Dumping techniques for creating ROM images from primarily involve hardware-based methods to directly interface with memory chips, as these ensure accurate capture of the binary data stored in (ROM) types such as mask ROM or . Hardware approaches are favored for vintage game cartridges and embedded systems due to the non-volatile and fixed nature of the data, avoiding the need for runtime execution. In hardware-based dumping, the process begins with identifying the chip type, such as distinguishing mask ROM (non-erasable, factory-programmed) from (ultraviolet-erasable). For desoldering methods, the chip is removed from the circuit board using a or hot air station, then inserted into an EPROM programmer like the XGecu TL866II Plus, which connects via USB to a computer. The programmer's software detects the chip, reads its contents sector by sector—typically in 256-byte or 512-byte blocks—and outputs a binary file (.bin). To handle multi-chip cartridges, such as those in games with separate PRG (program) and CHR (character) ROMs, each chip is dumped individually; the resulting files are then combined using tools like nesromtool, which interleaves or concatenates them according to the system's mapper specifications to form a complete ROM image. Cartridge adapters simplify the process without , emulating the console's bus to access in . Devices like the Retrode connect via USB and support systems including , SNES, and ; users insert the , and the device exposes the data as a file on the host computer, often requiring adapter plugins for specific formats. Similarly, the open-source INL Retro Dumper-Programmer handles , SNES, , and others by connecting to a PC ( preferred) and running scripts to read and save binary dumps, with manual header addition for iNES or similar formats post-dump. For logic analyzers, tools like Saleae capture address and data lines during console operation, reconstructing the by logging reads, though this is less direct and more suited to verification. Software-based approaches apply to flashable ROMs in modern or reprogrammable devices, leveraging debug interfaces rather than direct chip access. Using (Joint Test Action Group) or SWD (Serial Wire Debug) ports, a like Segger J-Link connects to the device's pins, allowing software such as OpenOCD to halt execution, probe memory addresses, and extract flash contents into a . This method suits embedded systems with NAND or NOR flash, where commands like "dump_image" read sectors sequentially. Debug modes, activated via manufacturer-specific pins or bootloaders, enable similar extraction without hardware modification. Common challenges include bit errors from chip aging, poor connections, or electrical noise, which can flip individual bits and corrupt the dump; solutions involve performing multiple reads (e.g., 3–5 times) and comparing outputs with tools like or verification to identify and correct discrepancies by majority vote. Sector alignment issues arise in multi-chip or bank-switched setups, where incorrect address mapping leads to misordered data; this is resolved by referencing system documentation or using dumper software with predefined mapper profiles to ensure proper sequencing. Copy protection schemes can complicate reads by scrambling data or requiring specific timing, but general dumping focuses on raw capture before such obstacles.

Copy Protection Challenges

Copy protection in ROM images presents significant obstacles during the creation process, as manufacturers implemented various mechanisms to prevent unauthorized duplication of cartridges and . These protections often rely on hardware-specific features that verify before allowing access to the data, complicating direct dumping techniques. Without proper circumvention, attempts to extract the can result in failed reads, incomplete data , or of anti-tampering measures that halt the process. Common types of protection include hardware locks, such as battery-backed checks that monitor system and erase or corrupt data if unauthorized access is detected, and custom application-specific integrated circuits () embedded in cartridges to enforce proprietary handshakes with the console. schemes, like Sega's TradeMark Security System (TMSS) introduced in the early , require specific code sequences—such as writing the string "" to designated memory locations—to unlock execution, otherwise displaying a and disabling the game. These methods evolved from simpler 1980s checksum validations, where cartridges computed hashes during to detect modifications, to more sophisticated proprietary encodings that integrated console-specific authentication protocols. Historical examples illustrate the prevalence of these challenges in console gaming. Nintendo's Checking Integrated Circuit (CIC) lockout chip, deployed in the (NES) and (SNES) from the mid-1980s, uses a paired in both the console and to perform a one-way sequence; failure to match resets the CPU repeatedly, preventing ROM access. Overcoming these protections during ROM creation typically involves hardware modifications, such as physically clipping or replacing lockout chips like the CIC to disable authentication signals, or using software patches applied post-extraction to neutralize embedded checks. Specialized adapters, including the SNES EverDrive , facilitate bypassing by emulating legitimate hardware responses, allowing ROM data to be read and dumped without triggering protections, though compatibility varies with chip-specific games. In modern contexts, reverse-engineering tools like enable analysts to disassemble protected ROMs, identify authentication routines, and develop targeted patches for complete extraction. Failure to address copy protection adequately poses risks, including data corruption from interrupted reads or anti-tampering mechanisms that alter memory contents, leading to incomplete or unverifiable dumps. Such issues can manifest as bit errors in the extracted image, potentially propagating glitches into emulated gameplay or preservation archives if verification steps like checksum comparisons are skipped.

Applications

Emulation

ROM images serve as the foundational input for software , enabling the replication of original environments on modern systems. The core process involves loading the ROM data into an emulator's simulated , where it emulates the target system's CPU instructions, mapping, and peripheral devices such as graphics processors and sound chips. For instance, in cycle-accurate , the emulator precisely replicates the timing of operations to ensure compatibility with timing-sensitive software like certain games, preventing glitches in audio or video output that could occur with less precise methods. Prominent exemplify this approach across different platforms. MAME, focused on systems, achieves high accuracy by simulating hardware at a low level, loading sets that include program code and graphics data to recreate original behaviors. , a cycle-accurate for the (), prioritizes faithful replication of the 6502 CPU and PPU (Picture Processing Unit), supporting up to 1MB in size for enhanced games. , for and consoles, employs both high-level (HLE) for optimized performance on complex titles and low-level (LLE) for precise hardware simulation, loading ISO-based images to run games at resolutions far exceeding the originals. Emulation via ROM images offers significant advantages, including cross-platform accessibility that allows games to run on , mobile devices, or consoles without the original , reducing wear on aging physical components. Users benefit from enhancements such as effects for improved visuals, like scanline filters mimicking displays, and netplay features for online multiplayer in originally single-player titles. These capabilities extend the lifespan of legacy software, supporting efforts by enabling archival playback on contemporary . To function effectively, emulators require ROMs in compatible formats, often necessitating additional BIOS files—firmware dumps from the original console—for systems with proprietary boot processes. For example, emulators like DuckStation demand BIOS files such as SCPH-5501 to initialize the MIPS CPU and handle CD-ROM interactions before loading game ROMs. Performance optimization is crucial for larger ROMs, such as (SNES) titles exceeding 1MB, where just-in-time () compilation dynamically translates emulated code into native machine instructions, boosting execution speed while maintaining compatibility.

Digital Preservation

ROM images play a crucial role in by safeguarding cultural artifacts from the inevitable degradation of physical hardware. Video game cartridges and other ROM-based media are susceptible to environmental factors such as heat, humidity, and , which can corrupt stored over time; for instance, battery leakage in cartridges often leads to acid that damages and renders the originals unreadable. By creating digital dumps, preservationists mitigate these risks, ensuring that software like classic titles or console games remains accessible as a record of technological and cultural history. Methods for preserving ROM images involve meticulously dumping data from original hardware using specialized tools, such as readers or custom devices like the Sanni Cart Reader, to produce verified binary files. These dumps are then archived in public repositories, including the Internet Archive's extensive collections of emulatable software, such as the C64 Preservation Project, which hosts bit-accurate copies of vintage games. Similarly, the Software Preservation Society focuses on authentic, unaltered dumps of classic games to prevent and maintain the original production state, often relying on community-sourced originals for systems like the and ST. Checksums from standardized files verify the integrity of these dumps, allowing for reliable storage and future playback via . Standardization enhances the effectiveness of ROM preservation through projects like NOINTRO and TOSEC, which provide consistent naming conventions and comprehensive catalogs. NOINTRO maintains a database of the best available ROM copies, incorporating such as CRC32 hashes for verification and region codes to distinguish variants, ensuring dumps are complete and free from alterations like intros or hacks. TOSEC, dedicated to retrocomputing preservation, catalogs software and with detailed naming that includes version, language, and media type, facilitating organized sets for long-term archiving. These standards promote across tools and repositories, reducing errors in collection management. Institutional efforts have advanced ROM preservation through legal and practical initiatives. Exemptions under the U.S. , first granted by the in 2018 and renewed in 2021, permitted eligible libraries, archives, and museums to circumvent technological protection measures on lawfully acquired for preservation purposes, provided server support had ended and access was restricted to on-site use. However, this exemption lapsed effective October 28, 2024, as it was not renewed in the subsequent triennial . The , a , supports these activities by building specialized research libraries, recovering lost and prototypes, and advocating for broader access to preserved materials like early game builds. Corporate efforts have also advanced preservation; for example, established a dedicated team in 2022, which by March 2025 had preserved over 1,000 builds of games, including alphas, betas, and releases. Despite these advances, challenges persist in ROM image preservation, including sourcing rare original and , which are increasingly scarce due to and prior discard. Managing duplicates requires rigorous hash verification to eliminate redundant or corrupted files, while format obsolescence threatens long-term accessibility as unsupported binary structures may become unreadable without ongoing efforts.

Modifications

Modifications to ROM images involve altering the binary data to enhance gameplay, add new features, or adapt content for different audiences, often through community-driven efforts. Common types include ROM hacks, which redesign elements like levels or mechanics, and fan translations, which convert text and from one language to another. For instance, ROM hacks may use level editors to create custom stages in games such as , while fan translations repatch Japanese-exclusive titles into English using dedicated tools and resources. Tools for these modifications typically include hex editors for direct byte-level changes, assemblers for injecting assembly code, and patch formats like for applying non-destructive alterations to the original . Hex editors such as allow precise editing of data structures, while assemblers enable advanced code modifications by recompiling snippets into the ROM's memory layout. IPS patches, created with utilities like Lunar IPS, store only the differences between the original and modified ROM, facilitating easy distribution and reversal without overwriting the base file. Notable examples demonstrate the creative potential of these techniques. , a ROM hack of developed by T. Takemoto, dramatically increases difficulty through redesigned levels and precise platforming challenges, serving as a benchmark for hardcore modifications. Similarly, certain ROM hacks incorporate or exploit (ACE) glitches to aid speedrunners by enabling custom warps or sequence breaks, as seen in tool-assisted speedrun demonstrations of the original . Communities played a central role in fostering these modifications, with platforms like Romhacking.net, which served as a major repository until August 2024. The site's archived collection includes approximately 8,520 ROM hacks and numerous fan translations, preserved on the for enthusiasts to access, while balancing the preservation of unmodified originals alongside modded variants. Technical constraints in ROM modifications arise from hardware limitations, such as , where larger ROMs divide data into swappable segments to exceed addressable memory bounds, requiring modders to carefully manage bank transitions to avoid corrupting code execution. Additionally, alterations can trigger errors—validation sums embedded in the ROM header that detect tampering—potentially preventing the modified from loading in emulators or original ; these are often resolved using specialized fixers like for SNES titles or rgbfix for ROMs. Copy protection schemes in some original ROMs further complicate modding by necessitating bypasses before unprotected dumps can be reliably altered.

Technical Aspects

File Formats

ROM images are stored in various file formats, ranging from simple raw dumps to more structured, system-specific containers that include for with emulators. Raw formats provide unadorned copies of the ROM data without additional structure, making them versatile but requiring external information for proper interpretation. The .bin extension denotes a pure dump of the ROM chip's contents, commonly used across multiple systems as it preserves the exact data layout from the original hardware. Similarly, the .rom extension serves as a generic identifier for console ROM images, often applied to dumps from systems like or older handhelds, where the file lacks built-in headers and relies on naming conventions or accompanying documentation for context. System-specific formats incorporate headers or interleaving to encode hardware details directly in the file. For the (NES), the .nes extension uses the iNES format, which includes a 16-byte header followed by program ROM (PRG) and character ROM (CHR) data; the header specifies PRG size in 16 KB units (byte 4), CHR size in 8 KB units (byte 5), mapper number (bytes 6-7), mirroring configuration, and other flags like presence or system. The Mega Drive (also known as ) employs the .smd format for ROM dumps, featuring a 512-byte header and interleaved data in 16 KB chunks—alternating even bytes from one ROM half with odd bytes from the other—to facilitate loading via devices like the Super Magic Drive copier; this format is often compressed with for distribution. Container formats bundle multiple files or compress single ROMs to manage larger sets, particularly for systems with segmented . The .zip format archives ROM images, widely used for games where sets include separate files for program code, graphics, and sound data, allowing like MAME to load complete hardware simulations from one file. The .7z format offers superior compression ratios over and is similarly applied to multi-file ROM collections or individual dumps, though compatibility varies by —many support direct loading while others require extraction. For disc-based systems, the .iso format serves an archival role akin to ROM images by encapsulating read-only data tracks, though it is more commonly associated with optical media . Headers and metadata in formats like iNES enhance usability by making files self-describing, embedding details such as mapper type (for memory mapping), PRG/CHR sizes, and hardware flags directly after the initial "" identifier bytes, which simplifies configuration and reduces errors in video mode or setup. These features provide advantages over dumps by enabling automatic detection of cartridge specifics, improving cross-platform portability, and supporting advanced emulation without manual intervention. Tools like RomCenter assist in standardizing ROM formats by auditing collections against databases, verifying integrity, renaming files to match preferred extensions (e.g., converting .bin to .smd), and rebuilding containers like ZIP archives to ensure consistency for emulation libraries.

Verification Methods

Verification of ROM images relies on hashing algorithms to ensure data integrity by detecting bit flips, corruption, or unauthorized modifications. Common methods include CRC32 for basic error detection, MD5 for more robust checks despite its cryptographic vulnerabilities, and SHA-1 as a preferred option for reliable verification of ROM contents. These hashes are computed from the ROM file and compared against predefined values to confirm accuracy. Redumping protocols enhance reliability by requiring multiple independent dumps of the same ROM source, followed by bit-by-bit comparisons using tools like hex editors or diff utilities to identify discrepancies. For instance, in disc-based systems, a dump achieves verified status only after corroboration from several sources, ensuring errors from hardware faults or media degradation are minimized. Specialized tools facilitate large-scale verification by scanning ROM collections against database files (DATs) that list expected hashes, sizes, and names. ClrMamePro, a widely used utility, audits for completeness and correctness, flagging mismatches or missing files based on DAT inputs from sources like MAME or console sets. Similarly, FinalBurn Neo (FBNeo) verifies by matching against its specific ROMset versions, often using DAT files to confirm compatibility and integrity during setup. Authenticity checks extend beyond hashes to validate internal structures, such as headers in files. For ROMs, the iNES header is examined for the mapper ID (bits 4-7 of byte 6 and bits 0-3 of byte 7), which specifies the memory mapping , and region flags (bit 0 of byte 7 for and other indicators for territorial variants). Cross-referencing these with hardware tests, like running the ROM on original consoles, further confirms legitimacy by observing behavior against known specifications. Best practices emphasize sourcing from verified repositories to distinguish "good" dumps—accurate, unaltered copies—from "bad" variants like pirated or corrupted files. Communities such as No-Intro provide files listing hashes for their catalog of optimal ROMs, enabling users to rebuild collections excluding inferior or modified versions. GoodSets DATs similarly archive comprehensive hash databases, including alongside CRC32 and , to support thorough integrity audits.

Related Concepts

Similar Image Types

ROM images share conceptual similarities with other types of digital dumps but differ in their origins from hardware, which enforces immutability. Disk images, commonly saved as .img or .iso files, capture the contents of floppy disks, hard drives, or optical media such as and DVDs, often allowing read-write access when mounted as virtual drives. In contrast, ROM images derive from non-modifiable memory chips, preventing alterations and emphasizing archival fidelity over interactive use. Cartridge dumps for handheld consoles like the Game Boy produce full images, typically in .gb format, encompassing the entire game program and assets from the cartridge's mask or . These differ from partial dumps, which extract only battery-backed save data from volatile static chips on the same cartridge, preserving user progress rather than the core software. Firmware images, such as or dumps, closely resemble images in structure as non-volatile binary copies but serve as bootloaders to initialize hardware and operating systems, rather than delivering interactive game content. firmware, for instance, uses /COFF formats loaded into runtime or boot services memory, enabling persistent execution post-boot, unlike the fixed, game-specific payloads in images. A core distinction lies in images' non-volatile nature and fixed size, derived from hardware that retains data without power and maintains static dimensions (often megabytes per chip), setting them apart from volatile dumps that evaporate on shutdown or compressed archives that reduce file size at the potential cost of exact bit-for-bit preservation. Overlaps occur in preservation workflows, where ROM-like data is extracted from larger images; for example, tools can pull assets or sub-ROMs from 1 CD dumps in .bin/.cue format, converting multi-track optical data into focused binary files for . This process highlights shared applications in , where both ROM and images enable accurate software reproduction.

Legal Considerations

ROM images, which replicate the data from video game cartridges or chips, are generally treated as reproductions of copyrighted software under law, potentially qualifying as derivative works if modifications are involved. In the United States, owners of original game copies may create personal archival backups under 17 U.S.C. § 117, which permits the owner of a to make an additional copy for archival purposes, provided the original is retained and the backup is destroyed if the original is transferred. However, video game ROMs often fall into a gray area due to debates over , where personal backups for non-commercial purposes might be defensible, but any distribution or public sharing constitutes direct . Key U.S. legislation includes the of 1998, which prohibits circumvention of technological protection measures (TPMs) on copyrighted works, complicating ROM creation even for owned games since many involve bypassing hardware protections. Exemptions granted by the U.S. Copyright Office provide limited relief for preservation; for instance, the 2015 rulemaking allowed libraries, archives, and museums to circumvent TPMs on for preservation purposes, without public access. This was expanded in 2018 to remove the prior limitation to games published before 2014, now covering all —including online and server-dependent ones—enabling eligible institutions to maintain playable copies for research and on their physical premises, with renewals in 2021 and 2024 maintaining this scope as of October 2024. Ethical concerns surrounding ROM images center on the tension between cultural preservation and the risk of facilitating , as unauthorized distribution undermines developers' revenue while archiving rare titles prevents their loss. A prominent case illustrating this dilemma is 's 2018 lawsuit against the operators of LoveROMs and LoveRETRO websites, where the ruled in favor of , resulting in a $12.1 million judgment for mass through ROM hosting and downloads. Regional differences highlight varying approaches; in the , Directive 2019/790 introduced mandatory exceptions allowing cultural heritage institutions to reproduce and make available works, including software, for preservation without commercial intent, extending protections to as part of digital . In contrast, Japanese copyright law under the Copyright Act of 1970 lacks a broad doctrine and provides narrower exceptions for private use, with companies like asserting that backup copies of their do not qualify under limited computer program provisions, leading to stricter enforcement against ROM creation and sharing. To navigate these issues responsibly, individuals should limit ROM use to private, non-distributed backups of personally owned originals and support official re-releases, such as Nintendo Switch Online's emulation of classic titles, which provide legal access while compensating rights holders. Digital preservation efforts by qualified institutions remain a legally supported pathway to safeguard ROM-based games without ethical conflicts.

References

  1. [1]
    ROM File - What is a .rom file and how do I open it? - FileInfo.com
    A ROM file is a data file that contains an exact copy of the read-only memory ROM chip for a hardware device, typically from a computer or a video game ...Missing: definition | Show results with:definition
  2. [2]
    How to open ROM file (and what it is)
    May 19, 2024 · ROM stands for Read-Only Memory Image. Files with the .rom file extension are used by computer hardware to update the data that is stored on the computer ...Missing: definition | Show results with:definition
  3. [3]
    About ROMs and Sets - MAME Documentation
    For arcade games, a ROM image or file is a copy of all of the data inside a given chip on the arcade motherboard. For most consoles and handhelds, the ...
  4. [4]
    [PDF] Video Game Preservation and Emulation from Three Perspectives
    Nov 2, 2023 · Emulation allows users to read ROM (Read-Only Memory) files taken from the original formats such as cartridges, CDs (Compact Discs) or tapes and ...Missing: image definition
  5. [5]
    2. NES Architecture Overview — Nerdy Nights 0.0.1 documentation
    One holds the program code (PRG), another holds the character graphics (CHR), and the last is the lockout. The graphics chip can be RAM instead of ROM ...2.1. System Overview · 2.1. 1. Lockout Chip · 2.2. Graphics System...
  6. [6]
    Fast retro gaming on mobile - Mozilla Hacks - the Web developer blog
    Video game emulation starts with ROM image files (ROM files for short). A ROM file is the representation of a game cartridge chip obtained through a process ...
  7. [7]
    What are ROMS? - Emulation Zone
    Basically a ROM image is the information that's on a video game cartridge (graphics, sound etc). Using a "copier" it's possible to copy the code that's on ...
  8. [8]
    Firmware standards - The Ganssle Group
    ... ROM image. This includes compiling and assembling source files, linking, locating (if needed), and whatever else must be done to produce a final ROM image.
  9. [9]
    Taking A Dump From Some Old Hardware - Hackaday
    Jun 26, 2012 · The targets of their hunt are EPROM chips. Note the single 'E'. These are Erasable Programmable Read-Only Memory chips, and predate EEPROM which ...
  10. [10]
    The ROM Dump Tutorial - The HP 9845 Project
    The standard procedure for most vintage systems is to draw the ROMs from their sockets and read them out with a suitable EPROM-programmer - ideally before they' ...
  11. [11]
    The History of NES Emulation - Retro Reversing
    A significant breakthrough came in 1997 with the release of NESticle, a Windows-based NES emulator created by programmer Icer Addis of Bloodlust Software.
  12. [12]
    [PDF] Stuff You Can Click: Sensing Infrastructure with Software Emulation
    Dec 3, 2020 · A culture of sharing, iterating, and hobbyists developed an 1990s run of these emulators, distributing them first over BBS's, FTP and ...
  13. [13]
    GoodTools - Emulation General Wiki
    The popularity of GoodTools originated the practice of distributing, instead of single or arbitrarily collected ROMs, the so-called "goodsets", packaged ...Missing: 1997 | Show results with:1997
  14. [14]
    Previous MAME Releases
    Below is a collection of older MAME releases, dating back to the first official release from February, 1997. MESS only releases (prior to version 0.148) are ...
  15. [15]
    ESSAY; New Front in the Copyright Wars: Out-of-Print Computer ...
    May 18, 2000 · Greg Costikyan article holds abandonware Internet sites that offer computer games that are no longer published and emulators to let users ...
  16. [16]
    The Unsung Heroes of Game Preservation, Part 1 - superjump
    Jul 22, 2023 · The games industry, for the most part, turned a blind eye to the abandonware scene. These games had long since ceased being profitable, and the ...
  17. [17]
    C64 Preservation Project 10th Anniversary Collection
    Nov 27, 2015 · This item contains two versions of the same set of files, both nibble copies and G64 versions. Each is in their own .ZIP file, for convenience.
  18. [18]
    The Expanded DMCA Exemption for Video Game Preservation ...
    Nov 26, 2018 · Online games have finally found their way into the video game preservation exemption to Section 1201 of the Digital Millennium Copyright Act (DMCA).
  19. [19]
    Guide :: Getting ROMs (legally) from Retro Collections on Steam
    Jul 4, 2023 · Guide on how to get ROMs as legally as possible from game collections sold on Steam...Missing: integration | Show results with:integration
  20. [20]
    Dumping roms - MAMEDEV Wiki
    Jul 10, 2019 · Dumping memory chips is the core part of the whole dumping process. It basically requires an EPROM programmer, a PC and some dedication. We ...
  21. [21]
    start [dumping.guide]
    ### Summary of Dumping.Guide on ROM Dumping Techniques
  22. [22]
    Dumping NES Mask ROMs : 6 Steps - Instructables
    Dumping involves desoldering mask ROMs, wiring them to a microcontroller, uploading a sketch, and then processing the output to create a ROM file.Missing: multi- interleaving
  23. [23]
    Dump NES ROM using an INLretro programmer-dumper - Kevin Smith
    This guide will walk you through dumping NES cartridges on Linux using an INLretro programmer-dumper from Infinite NES Lives.
  24. [24]
    Preserving the data from your older game cartridges - iFixit
    The Retrode also supports ROM dumping, so that users can save the data from their cartridges to their computers and later run them on an emulator. Additional ...
  25. [25]
    INLretro Dumper-Programmer (formerly kazzo) - INFINITE NES LIVES
    Dumping of carts generates binary rom image only, headers must be added manually. See host/scripts/nes in the gitlab project for a list of currently ...
  26. [26]
    Extracting firmware from devices using JTAG - sergioprado.blog
    Feb 20, 2020 · Step 1: Identify the JTAG pins · Step 2: Test the JTAG connection · Step 3: Identify information about flash memory · Step 4: Extracting the ...
  27. [27]
    JTAG 101 - Part 1: Overview and On-Chip Debug Methods - EE Times
    This paper deals with using the Test Access Port (TAP) as a means to control the execution of the processor, and to debug software via the TAP.
  28. [28]
    What is the origin of corruption in ROM memories?
    Apr 4, 2025 · I would like to know if there is any external condition which could generate or accelerate corruption or it is just the material deteriorating inside the chip.
  29. [29]
    Ripping games - Emulation General Wiki
    Protection Scanning: Under Tools > Options > Dumping > Protection, you can configure how MPF handles copy protection. Enable options like "Scan for ...
  30. [30]
    silent scope 2 - fatal judgement nvram image - Arcade Controls Forum
    Feb 19, 2013 · I have a silent scope 2 fatal judgment game that errors out on boot. I've found its because the battery on the timekeeper NVRam is dead.
  31. [31]
    TradeMark Security System - Sega Retro
    TMSS is a Sega Mega Drive feature that displays a copyright notice and was initially intended as a region lockout, later used to prevent unlicensed games.Purpose · Known games without support
  32. [32]
    Copy Protection In The 80s, Showcased By Classic Game Dungeon ...
    Jun 25, 2019 · The copy protection in the classic 80s game Dungeon Master for the Atari ST and Amiga was next-level. It implemented measures that went well beyond its ...
  33. [33]
    CIC lockout chip - NESdev Wiki
    Jul 18, 2024 · The frontloading NES has a CIC Lockout Chip, a microcontroller that performs a proprietary handshake, as an anticompetitive measure.Overview · Disabling · Two-wire method
  34. [34]
    Sony PS1 Libcrypt Protection Bible - Kippykip Network
    Jun 16, 2024 · LibCrypt is an additional copy-protection, used by about 100 PSX games. The protection uses a 16bit decryption key, which is stored as bad ...
  35. [35]
    Antipiracy on Super Everdrive? - ASSEMBLERgames.org
    The DPF is not as complex as the modern logic chips in these flash carts. Right it does not decode ROM with the proper mirroring effect. Perhaps it saved money, ...Missing: bypass | Show results with:bypass
  36. [36]
    Learning Ghidra Basics Analyzing Firmware - Cutaway Security
    Ghidra is used to analyze firmware by extracting it from ROM, disassembling ARM instructions, and using search to find functions like update.
  37. [37]
    How likely is it that a ROM could be "corrupted" resulting in visual ...
    Oct 17, 2020 · The most straightforward answer is that they're making a joke, but I can tell you that bad dumps resulting in visual artifacts is very plausible.Missing: risks | Show results with:risks<|separator|>
  38. [38]
    MAMEdev.org | Home of The MAME Project
    ### Summary: MAME's Use of ROM Images for Emulation
  39. [39]
    Emulation accuracy - Emulation General Wiki
    If emulators are accurate enough, it produces much fewer audio and video glitches, usually at the cost of more processing power needed.Missing: image | Show results with:image
  40. [40]
    Dolphin Emulator - GameCube/Wii games on PC
    ### Summary of Dolphin Emulator's Use of ROM Images (ISOs) for GameCube/Wii Emulation
  41. [41]
    Get RetroArch Try RetroArch Online
    RetroArch is able to record your gaming session to a video file. The same mechanism also enables you to live stream your games to platforms like Twitch.tv or ...
  42. [42]
    Sony - PlayStation (PCSX ReARMed) - Libretro Docs
    BIOS¶. Required or optional firmware files go in the frontend's system directory. If more than one BIOS file exists, the PCSX ReARMed core uses ...
  43. [43]
    GameRoy: JIT compilation in High-Accuracy Game Boy Emulation
    Sep 2, 2023 · In this blog post, I will describe the process and considerations of implementing a JIT compiler in my emulator, and how I solved the problem of handling ...Missing: large | Show results with:large
  44. [44]
    [PDF] Digital Preservation Handbook - Strong Museum
    ... ROM images to be run on the original hardware such as the EverDrive line of flash carts. These cartridges vary in quality, but they provide an authentic ...
  45. [45]
    Software Preservation Society
    Mar 18, 2010 · Digital preservation of magnetic media based games and software for various systems.
  46. [46]
    No-Intro
    No-Intro catalogs the best available copies of ROMs and digital games, providing DAT files for ROM managers, and an online database.Wiki · No-Intro · DAT-o-MATICMissing: standards | Show results with:standards
  47. [47]
    TOSECdev Home
    TOSEC now has its own Discord! Feel free to join, ask your questions, submit data and help, or simply hang out with us!TOSEC Project Homepage · Downloads · TOSEC release! (2025-03-13) · News
  48. [48]
    Exemption to Prohibition on Circumvention of Copyright Protection ...
    Oct 28, 2015 · SUMMARY: In this final rule, the Librarian of Congress adopts exemptions to the provision of the Digital Millennium Copyright Act (“DMCA”) that ...
  49. [49]
    Video Game History Foundation: Home
    The Video Game History Foundation is a 501(c)3 non-profit organization dedicated to preserving, celebrating, and teaching the history of video games.Category: Collections · Check out our blog · Team · The Video Game History Hour
  50. [50]
    Preservation action - Digital Preservation Handbook
    Obsolescence is an issue because all files have their own hardware and software dependencies. This was particularly the case in the early days of computing.
  51. [51]
    Hacks - Romhacking.net
    Classic video game modification community. Home to ROM hack mods, fan translations, documents, utilities, homebrew, and other learning resources.The Hag in White · Costume Corrections for... · Latest Hacks · Kureji Lufia
  52. [52]
    btelwy/awesome-romhacking - GitHub
    Lunar IPS - Creates and applies IPS patches.; Online ROM ... WindHex32 - A hex editor with romhacking features, especially ones targeted for SNES games.
  53. [53]
    Utilities - Patch Checker - Romhacking.net
    Sep 18, 2014 · The Patch Checker compares all the bytes changed in the 2 .IPS patches and gives you a percentage as to how compatible they are.
  54. [54]
    Hacks - Kaizo Mario World 1 - Romhacking.net
    May 1, 2023 · Kaizo Mario is a rom hack of Super Mario World created by T. Takemoto, an unknown Japanese rom hacker. It was made to split your eyes out and make you cry.
  55. [55]
    https://www.romhacking.net/utilities/1080/
  56. [56]
    Romhacking.net - Home
    Classic video game modification community. Home to ROM hack mods, fan translations, documents, utilities, homebrew, and other learning resources..ROM Hacks · Translations · Getting Started · ROM Hacking DiscussionMissing: techniques | Show results with:techniques
  57. [57]
    Bank Switching Cartridges | hackup.net
    Jul 10, 2019 · Any cartridge that provides more data needs to implement some form of bank switching, ie some mechanism to switch between different sections (banks) of ROM.
  58. [58]
    Checksum Fixes - ROMhacking.net
    Nov 21, 2023 · When a certain game's ROM is modified, some emulators may say that the modified ROM has a bad checksum. This is why after you apply the ...Missing: limits bank errors
  59. [59]
    Trainers - Do It Yourself - Articles - SMS Power!
    Dec 4, 2013 · FrHed - a hex-editor to punch your modifications into the original ROM. ... Lunar IPS - for creating and applying .ips patches; SMS Power ...<|separator|>
  60. [60]
    List of filetypes - Emulation General Wiki
    For the different sections for the file types, see: Archives, Disc/Disk Images, Tape Files, ROM Images, Saves, Shaders and Filters, Other, CHIP-8.
  61. [61]
    iNES - NESdev Wiki
    Oct 27, 2025 · The .NES file format (file name suffix .nes) is the de facto standard for distribution of NES binary programs, with use even in licensed ...
  62. [62]
    SMD and BIN - what gives? | Sonic and Sega Retro Forums
    Jun 18, 2025 · SMD is an interleaved format based on 16KB chunks, plus a 512-byte header at the beginning of the file. Each 16KB chunk is interleaved by taking the even bytes, ...WHY do we have so many damn formats for SEGA Megadrive/GenSMD to BIN | Sonic and Sega Retro ForumsMore results from forums.sonicretro.org
  63. [63]
    iNES Documentation - Marat Fayzullin
    Interleaved NES ROM image is a file which contains the ROM data in each even byte, and the VROM data in each odd byte. You will have to write a program to ...
  64. [64]
    Rom manager
    Romcenter 4.1.0 is ready. Requirement : .net framework 4, windows xp to windows 10. As usual, you can report issues directly here.Download · About RomCenter · New update to romcenter 4.2 · RomCenter wiki
  65. [65]
    Hashes - Data Crystal
    Mar 29, 2025 · SHA-1 is probably the best candidate for verifying ROM images. SHA ... Supports CRC32, MD5, SHA-1, SHA-256. FCEUX. Access hashes via Help ...Missing: methods | Show results with:methods
  66. [66]
    SMSReader - Guide to Responsible Dumping - Development
    Use the SMSREAD utility with the verify and (in the case of SMS cartridges) checksum switches, and discard the dump if anything untoward is found.
  67. [67]
    Moderating guidelines for IBM PC and other systems - Redump Wiki
    No readable text found in the HTML.<|separator|>
  68. [68]
    clrmamepro
    ### Summary of ClrMamePro as a Tool for ROM Verification
  69. [69]
    systems:fbneo [Batocera.linux - Wiki]
    ROMs. FBNeo uses ROMsets in similar vein to MAME. A table of which ROMset version is being used in whatever version of Batocera can be found on the arcade guide ...
  70. [70]
    Nintendo header - NESdev Wiki
    The slot is checked for whether it contains a cartridge by checking 17 addresses for any non-$FF value. · The mapper is written with value $00 and mask $FF. · The ...Missing: authenticity ID
  71. [71]
    SnowflakePowered/opengood: Freely available DATs of ... - GitHub
    OpenGood is primarily available for historical preservation purposes because of its outdated romset information. As well, Parent-Clone DATs are not widely ...Missing: 1997 | Show results with:1997
  72. [72]
    ISO vs. BIN vs. CUE vs. IMG: Disk Image Formats Explained
    Oct 2, 2023 · Although there are several differences, the major factor is that ISO files come in only one format, while IMG images can be compressed or ...
  73. [73]
    Game Boy / Game Boy Color - carts - dumping.guide
    Oct 18, 2025 · There are numerous tools available for dumping Game Boy / Game Boy Color games. The cheapest tool for dumping carts is a GBxCart RW, followed by the Joey Jr.
  74. [74]
    2. Overview — UEFI Specification 2.10 documentation
    The major differences between image types are the memory type that the firmware will load the image into, and the action taken when the image's entry point ...
  75. [75]
    Difference between RAM and ROM - GeeksforGeeks
    Jul 11, 2025 · RAM is more flexible, but it costs more, while ROM is more stable and secure, but it doesn't have as much freedom. Understanding the differences ...
  76. [76]
    Tools and resources for PSX reverse-engineering
    CD-ROM tools ; Three tools: psxrip (extract files and disc metadata from BIN/CUE), psxbuild (creates a disc image), and psxinject (modify a disc image).
  77. [77]
    17 U.S. Code § 117 - Limitations on exclusive rights - Law.Cornell.Edu
    It is not an infringement for the owner of a copy of a computer program to make or authorize the making of another copy or adaptation of that computer program.
  78. [78]
    Chapter 1 - Circular 92 | U.S. Copyright Office
    117. Limitations on exclusive rights: Computer programs54. (a) Making of Additional Copy or Adaptation by Owner of Copy.— Notwithstanding the provisions of ...
  79. [79]
    Nintendo ROM Site Owner To Pay $12 Million For Game Piracy
    Nov 13, 2018 · An Arizona man has agreed to pay Nintendo $12 million for pirating the company's games through two ROM sites, according to court documents.
  80. [80]
    EU adjusts copyright rules to the digital age - Consilium
    Apr 15, 2019 · The directive introduces mandatory exceptions to copyright for the purposes of text and data mining, online teaching activities and the ...
  81. [81]
    https://www.copyright.gov/title17/92chap1.html