GlitchMod tutorials

Expansion, video and repair planning

Match expansions and replacement parts to the exact CD32, CDTV or Amiga board, diagnose before replacing components, and validate after repair.

3 min read Updated 0 replies

A successful Amiga modification begins with a defined goal and an accurate hardware inventory. More memory, alternative storage, an accelerator and a modern display connection solve different problems. Select the smallest change that achieves the intended result, and preserve a working baseline before adding it.

Match an expansion to the actual machine

Check the expansion manufacturer's manual for the supported model, connector, mechanical fit and required firmware. A CD32 expansion is not automatically a CDTV or desktop expansion. The Wicher CD32 manual is an example of a product-specific source; its requirements should not be generalized to every other expansion.

Record the CPU, memory, ROM and storage configuration before and after installation. Keep the original components together and photograph connector orientation. If an expansion requires a particular software installation or boot configuration, test that prerequisite before concluding that the new board is defective.

Diagnose external faults first

Compare a suspected display failure with a known compatible video path. Confirm the signal and timings accepted by the converter and television. An adapter accepting one Amiga model's output does not prove that every output on another model is equivalent. Record whether the system appears to boot and whether audio or controller responses continue while the screen is blank.

For storage or optical faults, separate media problems from drive behavior. Use a known-good source, observe spin-up and loading, and retain any repeatable error. Do not begin by adjusting laser controls: doing so can obscure the original diagnosis and does not repair every optical or mechanical fault.

Use original service documentation

Commodore's CD32 technical release and CDTV service manual document their respective boards and components. Match the revision on your machine before following schematics or ordering parts. Component values, polarity and connector pin assignments should come from a verified diagram and physical inspection, not a generic list for the Amiga family.

Photograph corrosion, leakage or prior repairs before cleaning. A capacitor replacement can require repairing damaged traces as well as replacing the component. Measure the relevant supply and signal conditions with suitable equipment; a collection of new capacitors is not evidence that every remaining fault has been resolved.

Installation and validation checklist

  1. Back up readable media and user data before opening or changing hardware.
  2. Identify the board and expansion revisions and obtain the matching manuals.
  3. Inspect for damaged sockets, reversed cables or debris before applying power.
  4. Install one documented change and test the stock baseline again.
  5. Run software that exercises the added memory, storage or processing feature.
  6. Repeat a sustained test and a cold boot, then verify saved data can be restored.

If instability appears after an upgrade, compare without the new component where the documented procedure allows. Note whether the fault occurs during initialization, under load or when accessing a particular device. Those observations narrow the investigation more effectively than changing several settings at once.

Keep compatibility evidence

For game installations, distinguish a hardware fault from an unsupported software configuration. WHDLoad publishes system requirements and per-install information; the special CD32 build has its own limits. Preserve the relevant version and test result in your notes.

Use preservation for backups and the technical index to locate additional original manuals. A wiki repair addition should specify the exact board, measured cause and completed validation so another owner can reproduce the result responsibly.

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.

Guide discussion 0

Questions & community notes

Ask for help, suggest a correction, or share what worked for you.

Be the first to reply

Include your console model, firmware, and tool version when asking for help.