Good job!

@crazii recently returned to the forum again, so he might find this interesting.

I actually happen to have a Sandy Bridge 2011 Mac Mini lying around somewhere, but I don't know when I will have time to test this.

Anyone know a good way to scan and see what USB controller is in a DOS only system?

I have this little AASTRA system (formally a VOIP PBX) which is enough PC like that I was able to get DOS to boot on it: Re: Using XT-IDE on 386 with Compact Flash larger than 512MB - My tests.

But it doesn't take cards and has virtually no I/O other that PS2 Kbd/Mouse, Network and USB ports.
It's (not quite PC) BIOS recognized USB floppies and mass-storage but not much else.

I'd like to be able to test/set/reset some input bits - possibly connect a USB parallel port or serial ... but not knowing what it actually inside the box, I don't know where to start.

DaveDDS wrote on Yesterday, 20:50:

Anyone know a good way to scan and see what USB controller is in a DOS only system? […]
Show full quote

Anyone know a good way to scan and see what USB controller is in a DOS only system?

I have this little AASTRA system (formally a VOIP PBX) which is enough PC like that I was able to get DOS to boot on it: Re: Using XT-IDE on 386 with Compact Flash larger than 512MB - My tests.

But it doesn't take cards and has virtually no I/O other that PS2 Kbd/Mouse, Network and USB ports.
It's (not quite PC) BIOS recognized USB floppies and mass-storage but not much else.

I'd like to be able to test/set/reset some input bits - possibly connect a USB parallel port or serial ... but not knowing what it actually inside the box, I don't know where to start.

Fastest first step: USBHOSTS.COM from Bret Johnson's USBDOS suite (https://bretjohnson.us/) — it scans PCI specifically for USB host controllers and prints type (UHCI/OHCI/EHCI/xHCI), vendor/device IDs, IRQ, and I/O or memory-mapped base. One command, you'll know.

For a full PCI inventory (NIC, video, etc.) the usual suspects:

• PCI.EXE "Merlin's PCI Hardware Sniffer" by Craig Hart. Original site is dead; mirrored at https://www.vetusware.com/manufacturer/Craig% … rt/?author=7605 and https://www.bttr-software.de/freesoft/system.htm. Grab Ray Hinchliffe's updated PCIDEVS.TXT from http://rh-software.com/ — that database has ~3x the entries Craig's last build shipped with.
• ListPCI (Mercury Thirteen, GPLv2): https://www.mercurycoding.com/downloads.html#DOS
• HWiNFO for DOS (Mumak, resurrected): https://www.hwinfo.com/download/ — thread at HWiNFO for DOS resurrected !

If you want to identify USB controllers by hand from any PCI dump: class 0C, subclass 03, prog-IF tells you which — 00=UHCI, 10=OHCI, 20=EHCI, 30=xHCI.

Heads-up: since the Aastra originally ran XP, you've probably got EHCI or xHCI with no UHCI/OHCI companion (Intel moved that direction at the P55 generation). Bret's driver is UHCI-only and won't bind to those. The realistic alternatives:

• DOSUSB (Georg Potthast) — UHCI/OHCI/EHCI + partial xHCI, demo halts after 20 min (fine for bring-up), includes LPT1USB.SYS and a USB serial driver: https://www.georgpotthast.de/usb/

Thanks guys! Please also check my other recent post. [ALPHA - testers wanted] Rescue-D2 - single-floppy GUI rescue disk for 386+, *4 MB RAM* (FreeDOS base)

The updated driver hasn't been folded into that yet. Pending hardware testing.

Very cool!
The OHCI was only tested on my NEC versa s260 laptop, and a NEC µPD PCI adapter on a i820 mobo. Thank you for debug it on more machines.

This was the first time I wrote any driver for any real HW/device, and with the massive details in the usb specs, although I was as careful as I can, some could be missing or misunderstood, besides bugs in the code.
It was a difficult project requiring more pcs for debug & test, and far from being practically usable.

Currently the usb-disk is emulated in the DOS level (DOS driver list) not the BIOS level, so the partitions in the usb disk cannot be changed by fdisk (disk not recognized), hope it does have problem for your rescue disk. I guess a rescue disk doesn't need that self-partition.

Are you interested in creating a PR? Sorry I was busy during the past 2 years and failed to note any changes related on the projects on github. Thank God who blesses with a good timing. 😁

I checked github just now and saw your issue. Thank you again for the PR.
There is another PR that's CI related, I believe there isn't many conflict.

i can test on the following hardware:

- via kt133a system with uhci 1.1 controller
- intel 440bx laptop with uhci 1.1 controller
- nec pci card with ehci/ohci 2.0 controller
- renesas pci card with xhci 3.2 controller
- via cardbus card with ehci/ohci 2.0 controller

my primary interest is getting a usb 2.0 hub (keyboard) working under dos with an ohci controller. the bret johnson driver seems to work flawlessly in this scenario, but is limited to uhci. compiling the current usbddos code on github results in an instant lockup when connecting thru a hub.