DOS ain't dead - USBDDOS USB-for-DOS tester v2.0.0-alpha.1.1

RayeR

CZ,
08.06.2026, 16:02

USBDDOS USB-for-DOS tester v2.0.0-alpha.1.1 (Announce)

There's new USBDDOS forked from Crazii work including a lot of patches
https://github.com/netrunner01/USBDDOS/releases
(Crazii hadn't time to merge it yet but it's a plan)

Interesting feature - this version has enabled serial debug @COM1/9600/8/n so maybe I'll see more than just a hanged PC...

---
DOS gives me freedom to unlimited HW access.

Japheth

Germany (South),
09.06.2026, 09:47

@ RayeR

USBDDOS USB-for-DOS tester v2.0.0-alpha.1.1

Post reply

> Interesting feature - this version has enabled serial debug @COM1/9600/8/n
> so maybe I'll see more than just a hanged PC...

Haven't tested this yet. Is this driver supposed to be an alternative to the Panasonic "ASPI" driver for USB mass storage devices ( di1000dd.sys )?

---
MS-DOS forever!

RayeR

CZ,
09.06.2026, 14:57

@ Japheth

USBDDOS USB-for-DOS tester v2.0.0-alpha.1.1

Post reply

Even better, it supports mass-stotage and HID devices (currently KB and mouse). I tested it yesterday and good new is that it doesn't hang but properly detects the EHCI, topology and endpoints. I captured some logs from serial terminal. Problem is that it detect my usb flashdisk, assign a drive letter but it displays only a single file or directory that seems to be the 1st dir entry, no more files. Tried both on FAT16 and 32 flashdisks. But it seems be on a good way maybe I'll have working USB driver after some 10 years again. Meantime all new MBs adopted xHCI that is not supported yet, I don't know if new MBs still contains some EHCI or XHCI-only now?

---
DOS gives me freedom to unlimited HW access.

RayeR

CZ,
15.06.2026, 15:06
(edited by RayeR, 17.06.2026, 14:39)

@ RayeR

USBDDOS USB-for-DOS tester v2.0.0-alpha.1.1

Post reply

Anybody else tried yet?
Maybe it could work with flashdisk formatted with FS-only, not partition table?
EDIT: no, it parses partition table and correctly read VBR and BPB, I added some debug outputs at init phase and looks OK... but dir command later is bad...
MBR CHS: 2/255/63, partition start CHS: 0/32/33, LBA 2048 VBR HS: 255/63, 4 sectors per cluster, 8 reserved, 2048 hidden, 512 root entries (32 sect.) root dir start at LBA: 2176 entry #0 - volume label "MR_SD32MB" entry #1 - LOCALE entry #2 - COMMAND.COM ... H:\USBDDOS.SRC\MAKE\OUTPUT>usbddosp.exe /disk No driver found at port: 5 for device (class 0b/00/00 smartcard), skip MSC_ReadSector: dev=291ac, sect=0, cnt=1 partition 0 - LBA start: 2048 FAT partition found (type: 14) MSC_ReadSector: dev=291ac, sect=2048, cnt=1 Sector per FAT: 60, 60, FATs: 2 - OK Sector per cluster: 4 - OK Reserved sectors: 8 - OK RootDirCluster7.0+: 414e204fh - bad Label7.0+: ¸àŽÀ‰î‰ï¹ - bad Label4.0: MR_SD32MB - OK Serial7.0+: 7c00bdd8 - bad Serial4.0: ac8edda8 - OK VBRSector: 2048 - OK RootDirs: 512 - OK USB Disk 'Generic Mass Storage Device' mounted as drive N:. C:\>dir n: Volume in drive N is MR_SD32MB Directory of N:\ LOCALE <DIR> 01-04-14 4:56p 1 file(s) 0 bytes 10,618,880 bytes free

UPDATE:
I enabled serial port debugging and added call of DBG_Log() into BOOL USB_MSC_ReadSector() but I still can see just only 2 read sectors call (MBR and VBR) on terminal log. I cannot explain how it can read part of root dir when there's no such sector read.

---
DOS gives me freedom to unlimited HW access.