| Previous | Next |
| ERROR_FLOPPY_ID_MARK_NOT_FOUND | ERROR_FLOPPY_UNKNOWN_ERROR |
ERROR_FLOPPY_WRONG_CYLINDER
Mismatch between the floppy disk sector ID field and the floppy disk controller track address.
ERROR_FLOPPY_WRONG_CYLINDER is decimal 1123 (0x463). The controller read a sector-identification field, but the cylinder encoded in that field did not match the track address where the controller expected to be operating. Unlike a simple missing sector, this result says recognizable header information was found and contradicted the current position.
Situations that can produce it
- a physical floppy has damaged, duplicated, or incorrectly formatted track headers
- the drive head steps to the wrong track because of alignment, mechanism, or controller problems
- media geometry or density is interpreted differently by the drive and the software
- a raw image was converted with incorrect cylinder/head/sector parameters
- a virtual floppy emulator presents sector IDs inconsistent with its selected track
This code is especially useful in imaging and preservation work because it distinguishes “header not found” from “header found in the wrong place.” That difference helps decide whether to change geometry, test another drive, or investigate track-positioning reliability.
Evidence to collect
- requested cylinder, head, sector, density, and transfer length
- cylinder and sector values actually reported by the controller or imaging tool
- drive model, interface, rotational behavior, and whether track zero calibration succeeds
- image format metadata and virtual-controller configuration
- a map showing which tracks fail and whether the mismatch is consistent or intermittent
A stable offset, such as every requested cylinder being read as the preceding one, suggests a stepping or geometry issue. Random mismatches across otherwise readable tracks point more toward media damage, unstable hardware, or faulty emulation.
Diagnostic sequence
- verify that the medium type and expected geometry are correct before issuing more reads
- read neighboring sectors and tracks without writing to determine the spatial pattern
- compare results on a second compatible drive or emulator
- preserve raw controller status rather than keeping only Win32 code 1123
- for unique media, image the readable regions first and postpone any repair attempt
Do not reformat or run a repair utility on archival media merely to make the error disappear. Reformatting replaces the very sector-identification structures needed to understand and recover the original disk.
Handling and recovery
Replaceable media can be recreated with the correct geometry. Valuable media should be handled with a read-only workflow, multiple-drive comparison, and explicit recording of mismatched IDs. A virtual image should be checked for a bad conversion profile or truncated track data before changing guest drivers.
Applications should expose the requested and observed cylinder values in diagnostics. Reporting only “disk read failed” removes the main fact that differentiates this condition from an unreadable sector.
Related floppy codes
ERROR_FLOPPY_ID_MARK_NOT_FOUND means no sector address mark was detected. ERROR_FLOPPY_BAD_REGISTERS describes inconsistent controller result registers. Error 1123 is narrower: a readable ID field points to a cylinder other than the selected one.
Example
A forensic tool requests cylinder 38 from a legacy disk and repeatedly receives sector headers marked as cylinder 37. A second drive reads the same disk correctly. The pattern indicates a head-stepping or alignment problem in the first drive, so continued retries there would add wear without improving recovery.
References
Looking for a different code? Search another status or error code.