Identify the complete system
The Disk System is an accessory arrangement for the Famicom, not an ordinary cartridge that adds a drive to every NES-shaped console. Nintendo's official historical hardware page identifies the HVC-022 disk drive and HVC-023 RAM adapter. Record those components and the base console separately. Integrated machines and modern replacements need their own wiring and service instructions.
Photograph model labels, the adapter cable, drive opening, battery compartment and power equipment. Test the base Famicom with a known working cartridge first. This establishes display, controller and console behavior before the accessory adds more variables. A drive motor moving does not prove that the adapter or disk data is functioning.
Use the intended power and display arrangements
Compare each supply with the component it powers. The base console and drive should not be assigned adapters by plug appearance. Verify output type, voltage, polarity, current capacity and physical connector against the actual label and appropriate manual. Inspect the battery compartment for leakage before using the drive's documented battery arrangement.
The picture and controls remain part of the base-console setup. Keep the same working display route for accessory tests. Connect the RAM adapter and drive with power removed unless a particular replacement device's documentation expressly describes another procedure. Do not apply a loader's hot-plug instructions to unrelated original hardware or an improvised cable.
Commission with one verified disk
- Record a successful base-console cartridge test.
- Assemble the identified adapter and drive using the original arrangement.
- Start the system and observe the adapter's boot behavior.
- Insert a known working appropriate disk in its documented orientation.
- Record loading, side-change prompts and a later gameplay transition.
- Test saving on expendable media before writing valuable progress.
Keep error messages and disk-side information exactly as displayed. A disk that fails in two setups and a drive that fails every known disk are different patterns. Inspect physical media condition before repeated reads. Do not diagnose a head-alignment fault from one unknown rewritten disk.
Distinguish physical drives and image loaders
The FDSStick maker's documentation describes a loader and disk-transfer workflow. FDSKey is a different original project with its own configuration and save-writing behavior. Match each device to its documented RAM-adapter and file requirements. A drive emulator bypasses physical-media mechanics, but does not repair a damaged original drive.
Record loader firmware, adapter identity and output-image format alongside test results. A program working through a virtual disk route is useful evidence for that route, not proof that a physical belt or head is aligned. Continue with drive service planning and preservation before altering disks or mechanical settings.