| Previous | Next |
| ERROR_COUNTER_TIMEOUT | ERROR_FLOPPY_WRONG_CYLINDER |
ERROR_FLOPPY_ID_MARK_NOT_FOUND
No ID address mark was found on the floppy disk.
ERROR_FLOPPY_ID_MARK_NOT_FOUND has value 1122 (0x462). It is a low-level floppy-media result: while seeking a sector, the controller did not detect the address mark that identifies a sector header. The message is about on-media structure or controller interpretation, not merely a missing filename.
Where this legacy code can still appear
- reading physical floppy disks for archival, forensic, or industrial maintenance purposes
- USB floppy drives that translate controller failures into historical Win32 codes
- virtual machines with floppy images or emulated floppy controllers
- disk-imaging tools processing damaged, copy-protected, unusually formatted, or partially erased media
- old application logs imported into a modern support system
Even when no physical floppy drive exists, an image file can reproduce this result if its sector layout is incomplete or the emulator expects a different geometry. Preserve whether the source was real media, a raw image, or a virtual floppy device.
Likely explanations
- magnetic damage or degradation removed part of the sector header
- the disk was formatted with a density, geometry, or encoding the drive does not support
- the read head is misaligned or the drive speed and media quality are unstable
- the image omits low-level formatting information required by the emulator
- a controller, cable, USB bridge, or emulator returned incorrect sector-position data
Running a filesystem repair utility first may be inappropriate because the controller has not reliably delivered the sector containing filesystem data. Diagnose the medium and geometry before modifying logical structures.
Evidence to preserve
- drive model, interface, reported media type, density, and configured geometry
- cylinder, head, sector, transfer size, retry count, and whether adjacent sectors are readable
- raw image format and emulator configuration for virtual media
- whether a second known-good drive reads the same location
- controller or imaging-tool status beyond the translated Win32 code
For valuable media, minimize repeated passes on a failing disk and create a best-effort image with a tool designed to record unreadable regions. Aggressive ordinary retries can further damage marginal media while producing no additional diagnostic detail.
Recovery choices
If the data is replaceable, use a correctly formatted medium and rewrite it. If the content is unique, switch to preservation-oriented imaging, compare multiple drives, and keep the original read map. A virtual floppy should be checked for truncation, conversion mistakes, and geometry mismatches before replacing the guest driver.
Application code should report the physical sector context and allow the caller to skip, retry, or abort according to data value. Converting 1122 to “file not found” hides that the failure occurred below the filesystem namespace.
Similar floppy errors
ERROR_FLOPPY_WRONG_CYLINDER means a sector header was read but identified a different cylinder. ERROR_FLOPPY_BAD_REGISTERS points to inconsistent controller results. Error 1122 specifically says the identifying address mark could not be found at all.
Example
An archive workstation reads a 1.2 MB disk using a USB drive that supports only common 1.44 MB geometry. Several tracks return 1122 because the expected sector address marks are not recognized. The correct next step is a compatible drive and imaging setup, not repeated filesystem scans through the same bridge.
References
Looking for a different code? Search another status or error code.