if python 3 would run on a PPC, that is probably what everyone would do.

A local web app or small drag-and-drop utility would probably be ideal: select your ROM + the driver/extension, it runs the existing dump/build Python tools locally, patches the device tree, and spits out the modified ROM.

That would give us essentially the same “auto-tbxi service” experience without having to store or transmit anyone’s ROM.

the USB 2.0 bomb made me think again about something which is in my head for quite a while:

couldn´t we run a hotline-folder-script-based or web-based auto-tbxi service?

where people upload the driver in question and their personal*) ROM file - or choose which content to delete - and then the "dump" and "build" python commands run in background?

most people probably do not have the patience and/or boldness to boot into OSX or linux, install python, explode the ROM file and edit the tree in the finder.

*) and they can be personal, the might have been edited before for something else.

Hey

I have a Firewire Solo and a Firewire 1814 that I'll send you for the price of a box + postage.

Located in Denmark. I don't know if it's still possible to send things outside of the EU without a bunch of hassle. If you take them both I'll check.

nope, not supported.

What a great development! Thanks for all your efforts and the time and knowledge you put into it!

- Total calendar span of dev time: 38 days (repo created July 9)
- Development hours: 200

Thanks for that information as well! It is very interresting. I am wondering why we ever accepted – be it from Apple or the X-fanboys around the world – the statements that such a driver is impossible!? Afer 2 decades, it needed an unexpected bomb, and "just" 6 weeks of structured and purposeful work to prove all of them wrong.

Imagine what may (have) be(en) possible with an active community of 100 to 200 good developers!

amazing 

Folks, this is the big one, the goal I had been striving towards since the very beginning:

USB 2.0 on Mac OS 9, fully and seamlessly integrated into the Mac OS ROM and a single system extension!

This is by far the most robust USB 2.0 release to date, and it has now been validated on THREE different machines:

- Mac Mini G4 (built from Elliot Nunn's modified Mini G4 ROM)
- Power Mac G4 MDD (built from the special MDD ROM from Apple's "OS9General.dmg") using NEC-chip USB 2.0 PCI card
- Power Mac G3 B&W (built from stock retail OS 9 ROM) using NEC-chip USB 2.0 PCI card

The B&W validation was notable because, unlike the Mini and MDD, it didn't involve a specialized machine-specific ROM; this gives me optimism that it could possibly also be used in some (or all) of the non-MDD G4 towers as well (Sawtooth, Gigabit, Digital Audio, Quicksilver). I don't own any of those towers, so I'd be very grateful if some intrepid souls out there could test this theory on those towers and report back!

INSTALLATION INSTRUCTIONS:

Step 0) Make a backup copy of your Mac OS ROM and store it somewhere safe (this step is NOT optional!!)
Step 1) Download and expand the correct ROM/extension pair for your machine
Step 2) Boot from an OS 9 CD
Step 3) Install the USB 2.0 ROM into your System Folder and the matching extension into your Extensions folder
Step 4) Reboot

...and that's it! When you boot up again, your USB 2.0 ports (whether on a PCI card or on-board) will now operate at USB 2.0 speeds with USB 2.0 drives in Mac OS 9, for the first time ever. NO MORE flaky, crash-prone desktop "helper apps". It's now a native-like experience, as it always should have been.

Changes/fixes since the last release include:

- Apple System Profiler no longer crashes when scanning "Devices and Volumes"
- Disk First Aid now shows correct bus information for mounted USB 2.0 drives
- Pulling a drive without ejecting now shows Apple's own warning message
- Drives connected at boot now mount at Hi-Speed automatically once the desktop loads (just like OHCI does)

Things you may notice (and what to do):

- "This disk is unreadable" at startup, sometimes, with a drive attached at boot. Intermittent and harmless: the drive was offered to the system a moment before its filesystem was readable. Click Eject (never Initialize, which would erase it). The drive mounts by itself a few seconds later.
- A pause of 15 to 45 seconds during startup, sometimes with the keyboard and mouse briefly dead, typically right when a Keychain or file-server dialog appears. That is Mac OS 9 itself trying to reach an AppleShare server from your Servers folder at boot; the whole system's input freezes during that window, including on stock machines. Wait it out; it recovers on its own. It is not the USB driver, and pulling cables during it can interrupt a mount in progress.
- A USB volume occasionally missing from Disk First Aid's list at its first launch after boot. The volume is mounted and healthy; DFA just did not pick it up while building its initial list. Eject and reinsert the drive (it pops into the running DFA immediately) or quit and relaunch DFA. Cosmetic only.

Current limitations to be solved in future updates:

- A maximum of four concurrently mounted USB drives (if you actually need to mount more than four at a time, I'm curious about your use case, haha)
- Full-speed and low-speed devices behind a Hi-Speed hub will not work
- MDD's Sleep function is still deactivated when the USB PCI card is installed (this is being actively investigated for a solution, hopefully fixed soon)
- non-NEC-chip PCI cards have not been tested and may not work
- Boot-from-USB is still not possible (and may never be, due to lack of support in Open Firmware)

Models that still need testing (because I don't own them):

- All non-MDD G4 towers (via USB 2.0 PCI card)
- Aluminum G4 PowerBooks, G4 iBooks, and late model G4 iMacs and eMacs (on-board USB 2.0)
- Beige G3 (this is OldWorld, a special case, and would require its own separate custom solution; I'd need a donor machine to develop one for it)

Projects/updates currently underway:

- CardBus USB 2.0 solution for G3/G4 PowerBooks
- eSATA drivers for LaCie PCI cards that will eventually unlock boot-from-external-SSD

For more technical details, please review the README and other technical documentation on the repo. Be sure to report back once you've had a chance to download, install, and test! This community rocks and I appreciate all of you. Hopefully this project brings you some Mac OS 9 joy.

-UB

https://github.com/UnexpectedBomb/MacOS9-USB2-EHCI/releases/tag/h97rel

*******************************************
USB 2.0 for Mac OS 9, by the numbers (approximated):

- Total calendar span of dev time: 38 days (repo created July 9)
- Development hours: 200
- Distinct test builds: 280
- Total boots: 600
- Total USB drive insertions: 1,000
- ROM images built: 40
- Driver log lines written: 300,000
- Sanity remaining: <45%

Brochure, EM Feb '93, EM Feb '93, Studio Sound Feb '93, EQ Apr '93, EQ Jun '93, EQ Aug '93, EQ Dec '93, SOS Mar '94, EM Jun '94", EM Sep '94", EM Sep '94, Studio Sound Oct '94, SOS Dec '94, EM Jan '95, SOS Mar '95, SOS Jun '95, SOS Jun '95

how to integrate the Session 8 hardware with Mac OS 9 (not for beginners):

• Studio 8 aka 882 Studio Interface (PZ001) requires "Session 8 Mac" -later renamed "Pro Tools Project"- or a "Disk I/O" NuBus Card (only the first) and a host computer. You can forward the audio to a Mac OS 9 rig via SPDI/F, AES/EBU or ADAT with an original Digidesign ADAT Interface
• 888 I/O (Original) → MIX Core / MIX Farm / MIX I/O → Pro Tools 5.1.1/5.1.3 MIX on Mac OS 9.x as well as Standalone mode
• 882 I/O (+882|20) Interface → MIX Core / MIX Farm / MIX I/O → Pro Tools 5.1.1/5.1.3 MIX on Mac OS 9.x as well as Standalone mode