Thanks, that
s helpful

What super work this is! My brain is hurting from reading your post a few times  With great timing I just got a few Firewire drives to back up my Mac Mini, but I think these are now going to be used for a System 7 partition!

Quote from: n8blz on November 27, 2025, 03:28:43 PM

Quote from: Jubadub on November 27, 2025, 10:13:03 AM

I have thoroughly tested Mac OS 9.2.2 with this new ROM combination (latest Rairii 10.2.1 + latest Mac mini G4 patches AKA v9 patches), and from what I could tell, everything behaves exactly the same as with the previous ROM we always used.

Long shot, but, is the mouse-freezing bug still present?

You know... Now that you mention it, I don't think I encountered it. But maybe I was just "lucky": even with the previous ROM, it was not THAT common for me to encounter it (but at the same time, it wasn't exactly very rare).

If you have a mini, are you able to check it on your end, as well? The more people we have trying this out, the more likely we are to truly find out.

I suspect the mouse glitch probably remains, since as far as we know it's a shortcoming to be addressed in our patches for the mini rather than Apple's own code, but... who knows?

I'm afraid I can confirm, at least on a 1.5Ghz Mac Mini, the mouse freezing issue is still there. Oh well :-)

Thank you for offering to help me out, Gary!

Good point about doing it myself. I'll see what I can cobble together and if I get stuck I'll reach out. Thanks again

Welcome to Mac OS 9 Lives!

Greetings

Found this spot reviving my old machines to try to capture the output of some video software I wrote back in the 90s.  Wish me luck...

I have a new/old MDD 867mHz machine and would be amazing to run it on this as it was created on a 400mHz machine.  So far, finding it quite tricky to get it working but am suffering through swapping out optical drives and finding working IDE drives to try to get a fresh install going.

Cheers

It was Mac84, not "someone"... just give credit where credit is do:

https://www.youtube.com/watch?v=qbIoaulKYJY&pp=ygUFbWFjODQ%3D

I have, especially in the "Final Remarks" section with special emphasis on the archival and sharing of all the CHRP releases. I guess it is easy to miss because it's such a big post, but it's right over there:

========================================================
Final remarks
========================================================

Above all, thank you to everyone that made this possible. But I wanted to emphasize and give special thanks to Rairii for engineering all these ROMs, Mac84 for archiving and sharing all the CHRP discs, ELN for engineering all the Mac mini G4 ROM compatibility scripts and creating all the ROM and other Mac OS tooling, and to the Mac community at large everywhere that assisted in all of this into becoming reality. There's honestly many, many people to thank we owe over this one way or another, both in small and big ways.

The exact quote you highighted was meant to credit and cover at least two different people in one go:

- Someone who is not Mac84, who is the person (people?) who kept those CDs recorded and intact for all these decades, and who decided to let them go to different hands;

- Mac84 himself, for generously and selflessly going after these releases, securing them, archiving them and sharing them with the world and the community at large, while simultaneously making an incredibly helpful and educational video about it.

In other words, I wanted to credit everyone down the chain: the public archivist (Mac84) and the decades-long preservationist(s) who had the CDs all along (unknown/ undisclosed person or people), while also getting the whole information / story across with as much brevity (as much as I could without cutting info out) to everyone by relying on hyperlinks plus a "Final Remarks" section so that there would be no misgivings about who did what. (I hyperlinked to both the Macintosh Garden and archive.org pages, as both lead to Mac84 as the public archivist of CHRP, which also contains the YouTube video link, for that very reason.)

To be even more precise:

- The "someone" in what you highlighted refers specifically to the decades-long preservationist(s): "someone preserved some of these Mac versions, [...]";

- The part that follows immediately after is Mac84: "[...] which were then acquired and preserved and shared with the world".

So you are not exactly right about your attribution, if we are to be pedantic... But moving on.

I hope this thoroughly suffices to clear up your misunderstanding. I commend your willingness to stand up for what is right, but it is equally important to be careful to go through the whole thing first before pointing fingers...

It was Mac84, not "someone"... just give credit where credit is do:

https://www.youtube.com/watch?v=qbIoaulKYJY&pp=ygUFbWFjODQ%3D

Congratulations all involved! That's quite the hack and definitely something that brings excitement to the whole space. Great write up and it was cool to see how the efforts of multiple individuals came together.

Hey, it's great to see you return here, @ELN! Your scripts and tools really saved the Mac-day here!

I wasn't sure about Go, but yeah, Python doesn't usually leave me with the best impression with lack of forward compatibility among even minor versions... I thought the infamous Python 2 to 3 migration was going to be the last time it would have issues like this, but I guess not. However, I'm just glad your tools work with most Python 3.x versions still! They made all the difference, and they were very easy to use thanks to the lengths you went through to keep it as heavily-commentated and easy-to-use as possible for a CLI app. I see why you would favor Go nowadays, though, as they reassure to do better to devs. (What about good ol' Perl?)

By the way, in case it might interest you, you can interact with Rairii directly through this Discord server of his (listed in his Nintendo PPC NT GitHub page, which currently accomodates PowerPC/MIPS WinNT + Mac discussions/developments in particular).

Excellent work!

I switched from Python to Go in large part for the compatibility guarantee. https://go.dev/doc/go1compat