Repository navigation
Releases
OpenASPI v0.1.0-alpha.9
Ninth alpha of the OpenASPI DOS driver suite. EXFAT.SYS 0.6 shows the right free space on SvarDOS and other EDR-DOS kernels.
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.6-us-disk1.img/exfat-0.6-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.11 or an Adaptec-compatible manager. DOS and ASPI managers are not bundled. The exFAT package needs no ASPI.
Changes since 0.1.0 Alpha 8
EXFAT.SYS 0.6: free space on EDR-DOS
- On SvarDOS (EDR-DOS kernel), DIR showed the free space of an exFAT drive too small by the number of sectors per cluster: the kernel's INT 21h AH=36h counts every cluster of a redirector drive as one sector. Reported with a patch as SvarDOS/edrdos#166.
- Until a fixed kernel is out, EXFAT.SYS reports one sector per cluster, with the cluster size as the sector size (up to 32 KB). The free space is then right on every DOS.
Code pages from mars-unicode-tables
- The FAT and exFAT library openfat now builds its code pages from the UNI_.TAB files of mars-unicode-tables. The DOS drivers and tools keep code pages 437 and 850 built in, now made from these tables.
- Only one character differs: in code page 850 the dotless i (D5h) stays as it is in 8.3 names instead of becoming "I", as with the Windows up-case table.
- An accented Latin letter that the code page lacks becomes its base letter in 8.3 names (as before for most letters, now for all of U+00C0-U+024F).
Validation and scope
Checked on SvarDOS: the free space DIR shows for the exFAT test drive (dos_exfat.sh with SVARDOS=1) equals its free clusters as dump.exfat counts them on the host. With an EDR-DOS kernel patched as proposed in SvarDOS/edrdos#166, INT 21h AH=36h returns the real sectors per cluster.
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
OpenASPI v0.1.0-alpha.8
Eighth alpha of the OpenASPI DOS driver suite. ASPIDSK can now offer its disks as BIOS hard disks (INT 13h), so tools such as NTFSDOS can read NTFS partitions on them (#2).
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), unchanged since Alpha 7.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.10 or an Adaptec-compatible manager. DOS and ASPI managers are not bundled. The exFAT package needs no ASPI.
Changes since 0.1.0 Alpha 7
ASPIDSK /I13: the disks as INT 13h drives
- Programs that read disks through the BIOS (NTFSDOS, disk editors, EXFAT.SYS's BIOS back end) do not see ASPI disks. With
DEVICE=ASPIDSK.SYS /I13every disk ASPIDSK takes also gets a BIOS drive number after the BIOS's own hard disks (80h + the count at 0040:0075, which grows accordingly). - This includes disks without a FAT volume, such as a disk with only an NTFS partition: it gets no drive letter but an INT 13h drive. If there are only such disks, ASPIDSK stays resident as a character device.
- Functions: reset, status, CHS read/write/verify, parameters (08h), type (15h), and the extensions 41h–44h, 47h, 48h (EDD 1.1, LBA). CHS uses 255 heads and 63 sectors. Up to 8 disks with 512-byte sectors, below 2 TB.
- Writes through INT 13h bypass DOS: do not write a volume that also has an ASPIDSK drive letter that way.
/I13is not offered by the installer yet; add it to theDEVICE=line of ASPIDSK.SYS by hand.
Validation and scope
New test: dos_ntfs_i13.sh (MS-DOS 7.1, EUSBASPI, a FAT16 stick and a disk with only an NTFS partition; also with the NTFS disk alone). A test program checks the INT 13h functions, including writes. Sysinternals NTFSDOS 3.02R mounts the NTFS partition through ASPIDSK and reads files (local test only; NTFSDOS is not part of OpenASPI). The NTFS4DOS build we had crashes in its DOS extender even on a plain IDE disk without OpenASPI, so it could not be tested.
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
OpenASPI v0.1.0-alpha.7
Seventh 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
OpenASPI 0.1.0 Alpha 6
Sixth alpha of the OpenASPI DOS driver suite. New: ASPIFDD gives EUSBASPI's hot plug slots a drive letter, USB disks the BIOS already serves stay with DOS, BackPack floppy drives go to ASPIFDD, a USB test matrix over every host controller in QEMU, VirtualBox and 86Box, and the relicense to the GPL version 2 or later.
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.4-us-disk1.img/exfat-0.4-gr-disk1.imgand the matching ZIPs: the exFAT package on its own (EXFAT.SYS, EXFMT, EXCHK). The programs are unchanged since Alpha 3; only the license texts are new.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.6 or an Adaptec-compatible manager. DOS and ASPI managers are not bundled. The exFAT package needs no ASPI.
Changes since 0.1.0 Alpha 5
ASPIFDD: drive letters for USB hot plug slots
- With
/H, EUSBASPI offers empty targets named "USB slot n". They answer MEDIUM NOT PRESENT until a stick is plugged in. - ASPIFDD now takes these slots. Each one gets a letter, like an empty ZIP drive, and the stick is read once it is there.
- An INQUIRY answer that is shorter than requested (with a residual count) is no longer rejected as empty.
USB disks served by the BIOS
- EUSBASPI 0.6 takes over the INT 13h of USB disks the BIOS already offers (for example a USB boot stick). It reports them through GET DISK INFO.
- ASPIDSK and ASPIFDD leave such a disk alone while DOS has a drive on it, and mount it when DOS does not.
ASPIFDD: devices named FLOPPY
- A floppy drive offered as a SCSI target now belongs to ASPIFDD, not ASPIDSK. An example is PORTASPI's BackPack floppy drive (MICROSOL BACKPACK FLOPPY).
License
- OpenASPI's own code is now under the GNU GPL version 2 or (at your option) any later version.
- Some parts stay under version 3: the GDI installer, and ASPIMGR.EXE and ASPIDDG.EXE (which link Open386MAX's QUILIB). Their license text comes along as
GPL3.TXT. - Setup shows all three licenses: OpenASPI, GPL3, and SHSUCD.LIC for SHSUCDX/CDAUDIO.
Native layer (not part of the DOS disks)
- A C ASPI layer for 32/64-bit kernels, with shared SCSI/ATAPI/SAT handling, interrupt-driven completion (INTx, MSI-X) and SMP locking.
- The FAT/exFAT library moved to openfat.
Validation and scope
New USB tests:
- QEMU (
dos_usb_matrix.sh): UHCI, OHCI, EHCI and xHCI, each with a multi-LUN USB device (hard disk, CD-ROM, ZIP 100 superfloppy) and a second stick, plugged in after the BIOS. ASPIDSK, ASPIFDD and ASPICDA read and copy files, and the host compares them and runs fsck. - 86Box (
dos_86box_usb.sh): the USB mass storage device with a hard disk, CD-ROM and ZIP on PIIX4 UHCI, the OPTi 82C861 OHCI card and the VIA VT83C572 UHCI card. - VirtualBox: OHCI, EHCI and xHCI with two sticks and a USB DVD drive.
dos_cda_usb.sh: ASPICDA with SHSUCDX on a USB CD, both with a full command set and with a minimal firmware that rejects READ SUB-CHANNEL, MODE SENSE, SEEK and others.
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
OpenASPI 0.1.0 Alpha 5
Fifth alpha of the OpenASPI DOS driver suite. New: ASPIFDD takes over BIOS-mapped drives, a drive letter for every volume, native 1024/2048-byte sectors, format IOCTLs and cartridge write protection.
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.4-us-disk1.img/exfat-0.4-gr-disk1.imgand the matching ZIPs: the exFAT package on its own (EXFAT.SYS, EXFMT, EXCHK), unchanged since Alpha 3.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 such as AHCIASPI 0.6, EUSBASPI 0.5 or an Adaptec-compatible manager first; DOS and ASPI managers are not bundled. The exFAT package needs no ASPI.
Changes since 0.1.0 Alpha 4
ASPIFDD: one letter for a drive the BIOS already maps
- A BIOS may map a removable drive itself. ReBIOS's SeaBIOS boots an ATAPI LS-120 as A:, and a ZIP as B: (superfloppy) or as hard disk 80h (partitioned). A SyQuest on the BIOS channel is hard disk 80h too.
- When the ASPI manager reports such a drive (GET DISK INFO, as AHCIASPI 0.6 does), ASPIFDD no longer skips it. It takes over the letter DOS already has for it.
- There is one letter, and it goes through ASPI: ASPIFMT, ASPICTL and raw-media sessions work on it.
- Floppy drives are found by their unit, hard disk volumes through DOS's drive data tables (INT 2Fh AX=0803h). Needs DOS 4 or later.
- With only taken-over drives, ASPIFDD stays resident as a character device.
- MS-DOS 7.1 refuses generic IOCTL category 80h for block devices. The OpenASPI tools (ASPIFMT, ASPIDD and the others) then send the request to the drive's driver directly.
ASPIDSK: a drive letter for every volume
- Each FAT partition gets its own letter, then the exFAT partitions. Primary partitions come first, then the logical drives.
- The letters of one removable device work together: a media change seen through one marks the others changed, and locks are counted over all of them.
- New options for ASPIDSK and ASPIFDD:
/ID:(only the listed targets),/NOSPINUP,/PAUSE,/R:n(ASPIDSK: at least n letters for a removable device). A stopped drive is now spun up at INIT.
ASPIDSK and ASPIFDD: 1024 and 2048-byte sectors
- MO and other media with larger sectors go to DOS unchanged.
/SEC:nsizes DOS's buffers for media inserted later. - On the FreeDOS kernel, ASPIDSK stays at 512 bytes. Raw access, exFAT and track IOCTLs stay 512-only.
ASPIFDD: format and media type IOCTLs
- Generic IOCTL 42h (format and verify track) sends FORMAT UNIT for the whole medium: the SFF-8070i form for LS-120/240, SBC for the others. 68h reports the media type.
ASPICTL PROTECT / UNPROTEC
- Set or clear the cartridge's own write protection (Iomega SET PROTECTION MODE). On SyQuest ATA drives, AHCIASPI 0.6 translates it to SyQuest's command.
PROTECT.EXEandUNPROTEC.EXEare installed with the other ASPICTL aliases.
Validation and scope
Tested in 86Box:
- ASPIFDD with ReBIOS's SeaBIOS under MS-DOS 7.1: LS-120 as A:, ZIP 100 with a partition as C:, LS-120 as A: plus a ZIP 100 superfloppy as B: (one letter each, ASPIFMT on it, copies with VERIFY, fsck)
- SyQuest drives through the BIOS, taken over by ASPIFDD
- PROTECT/UNPROTEC on the EZFlyer and on the parallel port ZIP 100/250
- the existing LS-120, ZIP and SyQuest tests
Tested in QEMU:
- the EZFlyer on an AHCI port, taken over from the BIOS and free
- multi-volume USB disks and sticks through EUSBASPI
- 2048-byte sector media on MS-DOS 7.1 and SvarDOS (FreeDOS refuses them, as intended)
All DOS test suites (except the mhVTL tape test, which needs an external setup) and the installation of both language disks 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
OpenASPI 0.1.0 Alpha 4
Fourth alpha of the OpenASPI DOS driver suite. New: SyQuest cartridge drives and hardware write protection.
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.4-us-disk1.img/exfat-0.4-gr-disk1.imgand the matching ZIPs: the exFAT package on its own (EXFAT.SYS, EXFMT, EXCHK), unchanged since Alpha 3.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 such as AHCIASPI 0.5, EUSBASPI 0.5 or an Adaptec-compatible manager first; DOS and ASPI managers are not bundled. The exFAT package needs no ASPI.
Changes since 0.1.0 Alpha 3
ASPIFDD: SyQuest drives
- ASPIFDD now also takes SyQuest drives (EZ135, EZFlyer, SyJet, SparQ), next to ZIP, Jaz, LS-120 and the others. ASPIDSK leaves them alone.
- The EZ135 and EZFlyer are ATA drives, not ATAPI. AHCIASPI 0.5 offers them as SCSI disks, on IDE channels and on AHCI ports (through an IDE to SATA adapter).
- A drive the BIOS already uses as a hard disk stays with the BIOS. ASPIFDD reports it as BIOS/DOS-owned and skips it.
ASPIFDD and ASPIDSK: hardware write protection
- When a medium is read in, MODE SENSE asks for its WP bit. A protected medium then fails every write at once with DOS error 00h ("write protect"), without the write being sent to the drive.
- This covers DOS, EXFAT.SYS and raw IOCTL writes. A medium change clears it.
- A device that doesn't report the bit is written to as before, and its own refusal gives the error.
ASPIFDD and ASPIDSK: Shuttle parallel port managers
- Shuttle's SD120PPD.SYS 5.46 (parallel port LS-120) hangs on GET DISK INFO and answers every LUN with LUN 0's drive.
- INIT now recognises this manager, does without GET DISK INFO and registers LUN 0 only. Before, INIT hung after the first INQUIRY.
Validation and scope
Tested in 86Box:
- SyQuest EZ135 and EZFlyer 230 through the BIOS
- the same drives through SyQuest's SQATDRVR.SYS 1.75
- a write-protected cartridge
- an EZ135 cartridge in the EZFlyer
- the drives through AHCIASPI and ASPIFDD, with FAT16 and with EXFAT.SYS
- parallel port ZIP 100 / ZIP 250 through Iomega's ASPIPPM1/ASPIPPM2
- parallel port LS-120 through Shuttle's SD120PPD.SYS
The 86Box tests use the SyQuest and parallel port drives of 86Box PRs #8697 and #8698.
Tested in QEMU:
- the EZFlyer on an AHCI port, once owned by the BIOS and once free
- write protection through EUSBASPI on a read-only USB disk
The existing host checks, DOS suites and the installation of both language disks and the exFAT package have passed for this build.
This is a development release, not yet tested on real SyQuest hardware: 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
OpenASPI 0.1.0 Alpha 3
Third alpha of the OpenASPI DOS driver suite. New: EXFAT.SYS writes.
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.4-us-disk1.img/exfat-0.4-gr-disk1.imgand the matching ZIPs: the exFAT package on its own (EXFAT.SYS, EXFMT, EXCHK), also usable on BIOS disks without ASPI.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 such as AHCIASPI, EUSBASPI or an Adaptec-compatible manager first; DOS and ASPI managers are not bundled. The exFAT package needs no ASPI.
Changes since 0.1.0 Alpha 2
EXFAT.SYS 0.4: writing
- Files are created, written, extended and cut, deleted (also by a pattern) and renamed or moved; directories are made, removed and renamed; attributes and times are set (COPY keeps the file time).
- Allocation bitmap, FAT chains and contiguous (NoFatChain) files, entry set checksums, name hashes through the volume's upcase table, directory growth; TexFAT keeps both FATs and bitmaps alike.
- Write order bitmap, FAT, data, directory entry: a crash loses clusters at most (EXCHK /F frees them). VolumeDirty is set while a change is under way.
- Writes go through INT 13h or the exFAT service of ASPIDSK/ASPIFDD; a write protected medium reports "write protect". No automatic retries.
- New switch
/R: read-only drives. - EXFATL.SYS also writes through the long file name calls (7139h, 713Ah, 7141h, 7156h, 716Ch, 7143h).
- Fixes found on the way: extended open (6C00h) returns its action under MS-DOS and honours EDR-DOS's create-new; device names such as AUX are never created as files; failed long name calls set DOS's last error (COPY, DEL and RD of MS-DOS 7 COMMAND.COM on the drive).
- Resident size: about 24 KB (EXFATL.SYS about 34 KB); loads high with DEVICEHIGH.
Validation and scope
Host write tests against fsck.exfat and the Linux exFAT driver (also TexFAT and a full volume); DOS write tests in QEMU under MS-DOS 7.1, SvarDOS (EDR-DOS kernel) and FreeDOS 1.4, with and without long names, loaded high, TexFAT and /R; writing through ASPIDSK and ASPIFDD across medium changes; the existing host checks, DOS suites and the installation of both language disks and the exFAT package have passed for this build.
This is a development release. exFAT writing is new: keep backups of important data. Tape writes are not yet qualified for production backups on real media. Physical device-specific formatting, complete reference-driver compatibility and Windows storage handover remain open. See the remaining driver work and the individual driver/tool READMEs.
OpenASPI 0.1.0 Alpha 2
Second alpha of the OpenASPI DOS driver suite, with English and German installation media and, new, a separate exFAT package.
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.3-us-disk1.img/exfat-0.3-gr-disk1.imgand the matching ZIPs: the exFAT package on its own (EXFAT.SYS, EXFMT, EXCHK), also usable on BIOS disks without ASPI.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 such as AHCIASPI, EUSBASPI or an Adaptec-compatible manager first; DOS and ASPI managers are not bundled. The same INSTALL.EXE also contains the Win16 frontend.
Changes since 0.1.0 Alpha 1
exFAT and FAT tools
- EXFAT.SYS 0.3: read-only exFAT drives through the DOS redirector, on ASPIDSK/ASPIFDD media and on BIOS disks; long file names as a setup choice (EXFATL.SYS).
- EXFMT (exFAT and TexFAT format) and EXCHK (check,
/Frepair, TexFAT FAT/bitmap recovery). - ASPICHK: FAT12/16/32 check and repair with the rules of fsck.fat. DEFRAG: FAT12/16/32 defragmentation that is safe against power loss.
- Installer options for exFAT and the FAT tools; the exFAT package installs on its own or together with OpenASPI.
Native tape API (ASPITAP and the C SDK)
- Positioning, partitions, setmarks, TapeAlert and RETENSION in the native tape interface (
include/openaspi/tape_api.h).
Driver robustness
- Unit Attention is latched: tape until an explicit rewind, block and CD drives until the media check reports it.
- ASPICDA reset drive is an ASPI device reset; real CD exchange through AHCIASPI tested in QEMU.
- Short INQUIRY, TOC and capacity replies are rejected instead of being read past their end.
- The extended host adapter inquiry is requested properly (AA55h), so managers that report residuals are used for CD replies.
- ASPISCAN waits for pending SRBs with interrupts enabled; pending, aborted and failed completions are tested.
- Write protection is tested live through ASPIDSK and ASPIFDD (DATA PROTECT from a read-only USB disk).
Installer
- GeosOne Dual Installer 1.16.0.
Validation and scope
Host/build checks, memory-only driver tests, the DOS media, disk and tape suites in QEMU, the installation of both language disks with the actual DOS installer pages, and the exFAT package alone and together with OpenASPI have passed for this build.
This is a development release. Tape writes are not yet qualified for production backups on real media. exFAT support is read-only in EXFAT.SYS. Physical device-specific formatting, complete reference-driver compatibility and Windows storage handover remain open. See the remaining driver work and the individual driver/tool READMEs for scope and limitations.
OpenASPI 0.1.0 Alpha 1
First public alpha of the OpenASPI DOS driver suite, with separate English and German installation media.
Downloads
*-us-disk1.img: English installation disk.*-gr-disk1.img: German installation disk.*-us.zip/*-gr.zip: the corresponding complete package for installation from a directory.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 such as AHCIASPI, EUSBASPI or an Adaptec-compatible manager first; DOS and ASPI managers are not bundled. The same INSTALL.EXE also contains the Win16 frontend.
Included functionality
- ASPITAP, ASPIDSK, ASPIFDD and ASPICDA device drivers, plus SHSUCDX and CD audio support.
- ASPICTL media controls and EJECT/CLOSE/LOCK/UNLOCK/STATUS filename aliases.
- ASPIFMT filesystem creation with surface reads and bad-cluster marking in both FAT copies; conditional FAT32 support tested with FreeDOS 1.4.
- ASPIDD full-medium and image copying, one-drive media exchange, read-back verification and
/RESCUEerror maps. - English/German QUILIB interfaces for ASPIMGR and ASPIDDG, sharing the Open386MAX library.
- BIOS/DOS ownership checks during block-driver installation, with an explicit fallback for unsupported managers. Filtering depends on accurate manager reports.
Installer pages and package READMEs follow the selected language. Driver diagnostics and CLI tools currently share English messages.
Validation and scope
Host/build checks, memory-only driver tests, disposable QEMU disk copying/formatting, injected read failures, FAT32 DOS file access, native LS-120 emulation, and both language disk installations have passed. Actual DOS installer welcome pages and controls were checked in both languages. The release installer was rebuilt from the committed GDI dependency and its pinned UPX revision in an isolated directory.
This is a development release. Tape writes are not yet qualified for production backups on real media. Physical device-specific formatting, complete reference-driver compatibility and Windows storage handover remain open. See the remaining driver work and the individual driver/tool READMEs for scope and limitations.