The Amiga ROM Collection (often abbreviated as ARexx/Amiga ROM Collection or AROS depending on context) generally refers to aggregated collections of ROM images, BIOS files, and system firmware used to emulate Commodore Amiga computers. These collections are used with emulators (e.g., WinUAE, FS-UAE, UAE4ALL, FS-UAE) to provide the system ROMs and Kickstart images required to run Amiga software and games.
| Filename | Version | Machine | Use Case |
|----------|---------|---------|----------|
| kick12.rom | 1.2 | Amiga 1000 | Early compatibility |
| kick13.rom | 1.3 | Amiga 500/2000 | Most OCS/ECS games |
| kick20.rom | 2.04 | Amiga 500+ / 600 | ECS+ 2.0 games |
| kick30.rom | 3.0 | Amiga 1200 | AGA games |
| kick31.rom | 3.1 | A1200/A4000 | WHDLoad & high-end |
| kick40.rom (3.X) | 3.X | Custom | Modern AmigaOS setups | amiga rom collection
To ensure your ROMs are not corrupted, use a tool like ClrMamePro or ROM Vault with a standard Amiga DAT file. The correct SHA-1 for kick13.rom is 82a21c1890cae844b3df741f2762d48d7e8e14d3. If your hashes don't match, the emulator will crash or fail to boot. The Amiga ROM Collection (often abbreviated as ARexx/Amiga
Why do people collect these files? For many, it is a race against time. Magnetic floppy disks degrade over time—a phenomenon known as "bit rot." The Amiga scene is particularly vibrant in the field of digital archaeology. The correct SHA-1 for kick13
Groups like the Software Preservation Society (SPS) (formerly CAPS) work to preserve these disks at a very low level, ensuring that the data is saved accurately for future generations before the physical media disintegrates. A "good" ROM collection is often verified against databases like TOSEC (The Old School Emulation Center), which catalogs specific file hashes to ensure the user has a working, uncorrupted copy.