v20260816-dev
Pre-release
Pre-release
Summary
Pre-release for testing. v20260816-dev of the fat95 filesystem handler and tools for m68k-amigaos (FAT12/16/32 support).
What's New
This pre-release marks a new major version, fat95 4.0. Partition auto-detection now runs on the new standalone ptable.library, so ptable.library is now required, and scanned partitions can be listed by the lsptres CLI tool.
Components in this release
fat95 4.0-dev (30.07.2026)(new)install95 3.19 (25.01.2026)dd 2.3 (16.08.2026)(new)debug95 3.19 (25.01.2026)SetFileSize 1.1 (25.01.2026)boot95 3.19 (25.01.2026)lsfsres 1.0 (16.05.2026)ptable.library 2.0-dev (30.07.2026)(new)lsptres 1.0-dev (30.07.2026)(new)
Changes
fat95 handler
- New
q(quiet) option. Control"+q"silences all fat95 error windows for a mount (errors go to the calling program instead). Unmounting a removed card now cancels any open window automatically. - Shared partition scanning. fat95 auto-detects its FAT partition (MBR, GPT, and flat whole-disk FAT) from the shared
partition.resourcepublished byptable.library, instead of scanning the partition table itself. The resolved mount Flags/CONTROL are reported and shown bylsptres. ptable.library 2.0is now mandatory. partition auto-detection requiresptable.libraryinLIBS:only explicit-geometry mountlist entries still mount without it. The bundledlsptrestool listspartition.resource. Theptable.libraryandlsptresare bundled in this archive but released as a separate project at amigaos-ptable.
Tools
dd 2.3 (fixes #26)
- A 64-bit transfer command (
NSCMD_TD64, orTD64) is now used whenever the driver advertises one, not only past 4 GiB. - New
CMDSRC(CS=) andCMDDST(CD=) force the transfer command for one side only.CMDstill sets both sides. Only a real.deviceside is affected. - A forced command the driver does not advertise is now reported before the transfer, together with the methods the device does offer. An I/O error
-3points atdd INSPECT. - New
MAXTRANSFER(MT=) sets the bytes per device request (default 130560). - New
MEMsets the buffer memory type (ANY|PUBLIC|CHIP|FAST|24BIT), instead of the type the driver reports. - Every transfer prints an
xfer:line with the bytes per request in use. INSPECTalso reports the buffer memory type and the device type.- A driver reporting fewer bytes moved than requested is reported once per transfer.
- Fixed: a source file that is not a whole number of blocks lost its last partial block.
- Fixed: a bad buffer when a device does not report its geometry.
- Fixed: a hang when the block size exceeds one request.