Repository navigation
OpenASPI v0.1.0-alpha.7
Pre-releaseSeventh alpha of the OpenASPI DOS driver suite. It fixes EXFAT.SYS loaded with DEVLOAD (#1).
Downloads
openaspi-*-us-disk1.img/openaspi-*-gr-disk1.img: English / German OpenASPI installation disk.openaspi-*-us.zip/openaspi-*-gr.zip: the corresponding complete package for installation from a directory.exfat-0.5-us-disk1.img/exfat-0.5-gr-disk1.imgand the matching ZIPs: the exFAT package on its own (EXFAT.SYS, EXFMT, EXCHK).SHA256SUMSandBUILDINFO.txt: checksums, source revision and build dependencies.
Each floppy image is a nonbootable 1.44 MB FAT12 disk. Start DOS, insert the disk and run A:\INSTALL.EXE. Install an ASPI manager first, such as AHCIASPI 0.6, EUSBASPI 0.8 or an Adaptec-compatible manager. DOS and ASPI managers are not bundled. The exFAT package needs no ASPI.
Changes since 0.1.0 Alpha 6
EXFAT.SYS 0.5: drive letters right after DEVLOAD
- DOS builds its drive table only after CONFIG.SYS. EXFAT.SYS therefore took its drive letters when the next program started.
- Loaded with DEVLOAD from the command line, no program started before the shell's own commands used the drive. FreeCOM's
DIR D:then did not find the drive. A USB stick under ASPIDSK reported "unknown media type". - EXFAT.SYS now also takes its drive letters when a program ends, so they are there as soon as DEVLOAD returns.
Validation and scope
New test: dos_exfat.sh with DEVLOAD=1 loads EXFAT.SYS with FreeDOS DEVLOAD under FreeCOM and uses the drive at once. It failed before the fix.
All DOS test suites (except the mhVTL tape test, which needs an external setup) have passed for this build.
This is a development release, not yet tested on real hardware for the new functions: keep backups of important data. Tape writes are not yet qualified for production backups on real media. See the remaining driver work and the individual driver/tool READMEs.
🤖 Generated with Claude Code