yes i think i answered to you. so if you buy a 320, ask the seller for a direct license transfer, then it should be troublefree.

and get a PCi card, the firewire interface does not serve what it promises (except when you want to link it to maxmsp)

don´t worry, the mkII had midi, but it does not work in OS9.

Luckily, I picked up a Midiman/M-Audio Midisport 2x2—after kicking myself for not buying an 828 MK2.

Thank you very much for your help.

And the Motu 828 is finally working—after I tried the M-Audio FW410 without success. !!!!
What a nightmare.

I'm working on an app that will convert many old Mac OS file formats (Claris Works, WordPerfect, MS Office, etc.) to modern formats, and am looking for sample documents to use for testing. Is there a site somewhere that has samples of old Mac files that I can use for this? I know I can create many such files from an emulator, but it would be good to have some real-world examples. Any useful information will be welcome.

can we add a temperature sensor after the fact?

something blabla about many kymas for sale how to get them running.

you seem to know! i want one for a historic rig

a working temp mon for the mini g4

Sadly @n8blz, here's the wall I've run into:

Turns out the Mini's setup is a bit different from the MDD, whose temperature sensor can be addressed directly, which is why the CSM worked so well for it. The Mini's temperature sensor, on the other hand, sits behind its PMU. As the G4 Mini was designed for OS X only, Mac OS 9 has no way of safely prodding the Mini's PMU (which controls power, reset, fans, etc) to grab a reading from the temperature sensor. A from-scratch driver would have to be built, and it could risk permanently hurting the Mini's ability to function properly in those critical areas if anything went wrong. As of now, only OS X can safely grab temp readings on the G4 Mini, although technically you can boot into Open Firmware and also get a real reading from the temperature sensor that way too (I have done it myself to confirm).

This adventure made me realize that this temperature monitor CSM ought to be "universal" anyway, reaching as many temp sensors on as many G3/G4 Macs as possible, so I updated the CSM to now search for any reachable temperature sensor on any OS 9 machine it gets installed on. The worst that could happen is that it can't reach any sensor and displays "n/a" for its temperature reading (as is currently the case for the Mini). Additionally, it will also display the exact type of sensor that it finds. If anyone gets a reading on any hardware besides an MDD, I'd love to know about it so I can update the documentation.

that´s because nobody know what to do, as it is nowhere propagated and users often sell their system years after using it the last time.

you can easily obtain a CD image from a user group - but it wont open.

because to run the kyma 4/5 software you need to properly transfer the hardware license. many people who sell their capy have no clue about that process.

well, actually the serialnumber of the hardware should also be enough to get it registered as second owner. but then they usually send you the last kyma X for classic and try to pretend that 4, 5, 6.22 are not available. i know for sure that they are.

It's still very experimental, but at long last... myth has become reality.

Introducing the first-of-its-kind USB 2.0 mass-storage driver for Mac OS 9. It's rough around the edges and I'm putting it out as an early beta, but it works... and it's FAST.

As many of you know, OS 9 only ever supported USB 1.1, operating at ~1 MB/s in practice. This experimental app mounts a USB 2.0 (or 3.0!) flash drive on a desktop and reads it at ~20 MB/s and writes at ~13 MB/s on my MDD via USB 2.0 PCI card, achieving speeds roughly 10-20x faster than anything OS 9 was doing before. Files copy in the Finder like any other disk.

All that said, I must stress that this is an early beta; a proof that hi-speed USB on OS 9 is possible. It is NOT a polished plug-and-play driver (yet). There's no extension to install. The whole stack (a built-from-scratch EHCI host-controller driver, a software-synthesized root hub, and a block driver) lives inside one small launcher app. Because USB 2.0 PCI cards share their physical ports with the old USB 1.1 "companion" controllers, when you plug in the drive makes all the difference, so it works through a specific sequence:

1) Boot with the drive UNPLUGGED from the PCI card
2) Run the launcher app. It will claim the card's ports for the 2.0 EHCI controller
3) When it says "INSERT USB DRIVE NOW," it's time to plug that sucker in
4) It mounts at 2.0 speed, and the drive icon will show a little "2.0" text badge on it, so you can tell it apart from a plain 1.1 mount at a glance. (Also it will generate some harmless dev logs.)

You MUST leave the app running because it hosts the stack. Eject the drive in the Finder before unplugging, and reboot to mount another drive.

My exact test rig: G4 MDD (non-FW800), an NEC-chipset IOGEAR USB 2.0 PCI card, and a SanDisk Ultra USB 3.0 64GB flash drive. That's the only combination I've been able to test so far, and I really need your help here; when you test this app, please make sure to report back with specific model information the following:
- the model Mac you used
- the model USB PCI card you used
- the type of USB flash drive you used
- the read/write speeds you achieved

Features that DO NOT work yet (and I'd genuinely appreciate some assistance with):
- auto-mounting an attached drive at boot
- hot-plugging (swapping drives without a reboot)

Mac OS 9's USB stack does not transfer a mass-storage device nicely from the USB 1.1 companion controller over to EHCI; a drive present at boot gets claimed by 1.1 before my driver has a chance to load (when placed in Startup Items). See the technical documentation for an explanation as to why my efforts thus far to prevent this have failed. If anyone here knows the classic USB stack intervals well enough to explain how to a companion controller correctly release a port to EHCI, or why ExpertIdleTask won't return after a mass-storage re-probe of a device that won't mount, I'd be very grateful for the advice!

Thanks in advance for your patience with the hot-off-the-press code. This stack took MANY hours of dev work and I'm hopeful we have something genuinely useful here to build from. Bug reports and hardware compatibility reports are welcome. I'm hoping to eventually get this working with late-model G4's that have onboard USB 2.0 (G4 Mac Mini anyone?) as well as USB 2.0 CardBus adapters for PowerBooks. In the meantime, I'll continue working on the hot-plugging feature. Let me know how it all goes, and I look forward to the collaboration.

-UB

https://github.com/UnexpectedBomb/MacOS9-USB2-EHCI

the classic os (7-9) for macmini forum threads seem to say that the audio problems are from using the mini's internal/onboard sound, and one solution is to use a usb dac for audio instead ...

... so for classic 7-8 os on non-mini machines like g4s and g3s,  could missing sound also be fixed by using audio hardware, like pci/usb/fw?

I can confirm that, with the OS 9 that we've had for the Mac Mini G4 for a while, an external USB audio device and an external mixer to work around the lack of software volume control works... but for 7 especially, I imagine drivers would become more of an issue.

(I haven't had time to poke at 7 more on my G4 Quicksilver 2002 lately.)

the classic os (7-9) for macmini forum threads seem to say that the audio problems are from using the mini's internal/onboard sound, and one solution is to use a usb dac for audio instead ...

... so for classic 7-8 os on non-mini machines like g4s and g3s,  could missing sound also be fixed by using audio hardware, like pci/usb/fw?