# Win10/Win11 compatibility notes for the ISD Falstaff USB-SCSI/ATA bridge

## Summary

This driver package cannot be made into a working Windows 10/11 x64 driver by editing the INF files alone.

The supplied kernel drivers are 32-bit x86 PE binaries:

- `FALSTAFF.SYS`: `Machine=0x014C`, `OptionalMagic=0x010B`
- `SPD2WDM.MPD`: `Machine=0x014C`, `OptionalMagic=0x010B`

Windows 11 is 64-bit only, and Windows 10/11 x64 cannot load a 32-bit kernel-mode `.sys`/miniport driver. The binaries are also unsigned, while modern 64-bit Windows requires kernel-mode drivers to be signed before they load.

## What these files are

- `FALSTAFF.INF` is a Windows 95/98 and early NT-style INF. It uses `Signature=$Windows 95$`, `Class=USB`, and legacy `DevLoader`/`NTMPDriver` registry entries.
- `FALSTAFF.SYS` is a vendor USB bridge driver from the DriverWorks/WDM era. Its strings reference ISD725, ATA/ATAPI/SCSI request handling, USB bulk/control URBs, and an `FSBridge\*ISDMAP` bridge.
- `SPD2WDM.INF`/`SPD2WDM.MPD` are legacy SCSI bridge/miniport components, not a modern Windows 10/11 storage driver package.

## Why INF-only conversion is not enough

Modernizing the INF can only change how Windows installs a driver. It cannot:

- convert a 32-bit x86 kernel binary into x64,
- make an unsigned kernel driver acceptable on normal Windows 10/11 x64 systems,
- replace the old USB bridge protocol implementation inside `FALSTAFF.SYS`,
- replace the legacy SCSI miniport/mapper design with a supported Storport/KMDF stack.

For Windows 10/11 x64, this needs a real port: source code for the bridge driver, a 64-bit build, testing, and Microsoft driver signing.

## Practical paths

1. Use a different USB-SCSI or USB-MO adapter that is USB Mass Storage/UASP class-compliant and already supported by Windows.
2. Use an older 32-bit Windows environment, such as Windows XP/2000 or possibly Windows 10 x86 in a test setup, to read/copy the MO media.
3. If source code for `FALSTAFF.SYS`/`SPD2WDM.MPD` exists, port it to a modern x64 KMDF/Storport-style driver and submit it for signing.
4. If only the media contents matter, use an older PC or a Linux system with suitable legacy USB storage bridge support to image/copy the disks.

## Device IDs found in `FALSTAFF.INF`

- `USB\VID_05AB&PID_0101`
- `USB\VID_05AB&PID_0200`
- `USB\VID_05AB&PID_0201`
- `USB\VID_05AB&PID_0202`
- `USB\VID_05AB&PID_0300`
- `USB\VID_05AB&PID_0CDA`