Repository navigation
atariATR 1.1
Adds a native plugin for Double Commander and, thanks to release builds now
running on GitHub Actions, binaries for platforms that could not be cross-compiled
from an ARM Mac before: Intel Mac and Linux.
Polski opis projektu: README.pl.md
What's new since 1.0
- Double Commander support (macOS, Linux). Double Commander implements the
same plugin interface as Total Commander and calls the Unicode entry points on
every platform, so the plugin is the same code built natively.
One real fix was needed: on macOS the loader resolves symbols withdlsym,
which prepends an underscore per the C convention, while Free Pascal exports
OpenArchiveWrather than_OpenArchiveW. The failure was quiet — the library
loaded and not a single function was found. Underscore-prefixed exports now
apply under{$IFDEF DARWIN}; the Windows DLL is unchanged. tests/wcx-loadcheck: a new test that loads the built plugin the way a file
manager does (LoadLibrary/GetProcedureAddress, i.e.dlopen/dlsym),
checks that all 19 entry points resolve, and walks an archive through them.
It runs in CI and gates the release: a plugin that is not dynamically
discoverable does not get published.- Release builds are automated per platform (GitHub Actions), which brings the
Intel macOS and Linux artifacts that were missing from 1.0. - File names coming from the host are converted to 8.3 using the rules of the
target file system, so adding e.g.my-file v2.txtto a MyDOS image works
instead of failing (this was the "CRC error" seen in Total Commander).
Assets
| File | What it is |
|---|---|
atrtool-1.1-windows-x64.exe |
command line tool, 64-bit Windows |
atrtool-1.1-macos-arm64 |
command line tool, Apple Silicon |
atrtool-1.1-macos-x86_64 |
command line tool, Intel Mac |
atrtool-1.1-linux-x86_64 |
command line tool, Linux |
AtrWcx-1.1.zip |
Total Commander plugin — drag onto TC to install |
AtrWcx-1.1-macos-arm64.wcx |
Double Commander plugin, Apple Silicon |
AtrWcx-1.1-macos-x86_64.wcx |
Double Commander plugin, Intel Mac |
AtrWcx-1.1-linux-x86_64.wcx |
Double Commander plugin, Linux |
SHA256SUMS.txt |
checksums |
The Intel macOS build is best-effort — GitHub is retiring that runner — so if it
is missing from this list, it did not build.
There is still no 32-bit .wcx. The Windows runner's Free Pascal only targets
x86_64, and installing a 32-bit compiler on it did not work out. If you use a
32-bit Total Commander, build the plugin yourself on Windows with a 32-bit FPC:
build/build-wcx.sh win32.
Installing
Total Commander: drag AtrWcx-1.1.zip onto a Total Commander window; the
bundled pluginst.inf makes TC offer to install it.
Double Commander: take the .wcx for your platform and add it under
Configuration → Options → Plugins → Packer plugins, associating the extension
atr.
macOS: downloads are unsigned, so clear the quarantine flag once:
xattr -d com.apple.quarantine atrtool-1.1-macos-* AtrWcx-1.1-macos-*.wcx
chmod +x atrtool-1.1-macos-*What the tools do
atrtool creates, inspects and modifies ATR/XFD images — Atari DOS 2.0S,
DOS 2.5, MyDOS and SpartaDOS, up to 16 MB with subdirectories — and can make
an image bootable by transplanting a DOS from a template image you already own.
atrtool create hd.atr 16m
atrtool format hd.atr mydos
atrtool installdos hd.atr "Mydos 4.50.atr"
atrtool add hd.atr mygame.xex
atrtool list hd.atr -rThe plugin opens an .atr file like an archive: browse the full subdirectory
tree, copy files in and out, delete them. It does not create images — that needs
decisions about geometry and file system, which belong in atrtool.
Verification
Unchanged from 1.0 and still passing: round-trip on 1705 real disk images (1689
byte-identical), 943 images read as file systems, byte-exact cross-validation
against lsatr from mkatr, agreement with MyDOS
TECH.DOC, writing into a real SpartaDOS X 4.48 image touching only 5 metadata
bytes, an 8 MB MyDOS image booting on real MyDOS in an emulator, and 38 checks
of the plugin through a Total Commander call-order harness — now joined by the
dynamic load check described above.
Known limitations
- SDFS writing covers 128 and 256 byte sectors; 512 byte sectors (32 MB images
under SpartaDOS X) are read but not written, because one superblock field for
that case is undocumented and could not be verified. - No GUI yet.