GlitchMod tutorials
Amiga modding wiki
Amiga CD32, CDTV and computer model identification, disc and disk preservation, WHDLoad compatibility, expansions and careful repair planning.
Browse topics
Tutorials & referenceAmiga modding and preservation wiki
Amiga CD32, CDTV and computer model identification, disc and disk preservation, WHDLoad compatibility, expansions and careful repair planning.
Console and computer routes
The Amiga family includes CDTV, CD32 and computer configurations. Choose the model identification guide before assuming that a game, expansion or repair procedure applies to all of them. Record the actual CPU, chipset, memory, ROM and storage arrangement. A machine with an expansion installed can behave differently from a stock unit with the same outside case.
For original disc-based use, establish a known-good controller and display path, then test loading and audio. For a computer installation, preserve the boot environment and partitions before changing storage. For emulation, retain a matching configuration rather than assuming the largest available CPU and memory settings produce the most faithful result.
Preserve media before expanding
The preservation guide distinguishes complete disc-track sets, floppy images, copied files and saves. Keep a master read untouched and work on copies. A title-specific WHDLoad installation has its own dependencies and behavior. The special plain-CD32 build has limitations different from regular WHDLoad, including its read-only operation; choose the route that actually meets your save requirements.
Use verified hardware documentation
Original Commodore service documents and expansion manufacturer manuals should establish connector assignments, component values and compatibility. This section does not replace them with guessed pinouts or generic replacement lists. A measured diagnosis and a test after repair are more useful than a universal claim that replacing one class of component repairs every machine.
Use this directory
Choose a guide by the work you intend to do, then record the hardware model, installed software and existing condition. Preserve data before a reset, storage change or firmware write. Each guide links primary documentation and separates documented requirements from editorial checklists. Keep a known-good baseline, change one variable at a time and verify a restore where saved progress matters. When contributing, include the exact tested configuration and source revision so another reader can reproduce the result and understand its limits.
Sources and review
Reviewed October 11, 2026. The linked manufacturer and project documentation establishes supported behavior. The diagnosis checklists and preservation suggestions are original editorial guidance. Menus, services and project support can change; verify the linked instructions before an irreversible change.