Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
But overall, it would be nice to have some upgrades for the last OS with 32 bit support.
Monterey is not 32 bit nor does it support 32 bit. Mojave was the last one to run 32 bit applications but it isn’t a 32 bit OS either.

I believe Lion 10.7 was the last one to actually be able to run on a 32 bit CPU, and even that needed coaxing.
 
  • Like
Reactions: MarkC426
Monterey is not 32 bit nor does it support 32 bit. Mojave was the last one to run 32 bit applications but it isn’t a 32 bit OS either.

I believe Lion 10.7 was the last one to actually be able to run on a 32 bit CPU, and even that needed coaxing.
Lion officially couldn't run it but I remember reading threads detailing how to get the 32-bit MacBooks to run it.

Apple has had many fails but those late 2005 G5s/PBG4s and the early 2006 intel Macs take the cake for top-tier terrible, no-good, very bad Apple. The life support for these machines is pretty pitiful, albeit slightly more excusable for the 32-bit Intel ones which at least ran Snow Leopard officially. You got 4 years from the PMG5 Quad and like 5 years from the first MBP Intels that had loads of heat issues. Thankfully OS X Lion played nice with 32-bit EFI so you could still run that OS but nothing for the Power Macs and iMacs unfortunately that could absolutely run Snow Leopard.
 
  • Like
Reactions: Project Alice
Lion officially couldn't run it but I remember reading threads detailing how to get the 32-bit MacBooks to run it.
Correct, hence it needed coaxing. I never did it personally, but I remember seeing threads about getting it running. Similarly, 2007 Macs that did have a 64bit CPU, had some half-assed firmware implementation making 64bit OS support annoying unless it was Windows under CSM. There was a fix for that too, but the fact Apple didn't fix it themselves was asinine. I had Mountain Lion 10.8 on a 2007 MBP. Had a Core 2 Duo, but 32bit EFI which meant Apple decided it couldn't have Mountain Lion instead of either releasing a firmware update or fixing the boot loader on their OS.
Apple has had many fails but those late 2005 G5s/PBG4s and the early 2006 intel Macs take the cake for top-tier terrible, no-good, very bad Apple. The life support for these machines is pretty pitiful, albeit slightly more excusable for the 32-bit Intel ones which at least ran Snow Leopard officially. You got 4 years from the PMG5 Quad and like 5 years from the first MBP Intels that had loads of heat issues. Thankfully OS X Lion played nice with 32-bit EFI so you could still run that OS but nothing for the Power Macs and iMacs unfortunately that could absolutely run Snow Leopard.
I would disagree with them being top-tier terrible, as they were (and most still are) very good machines, especially the PowerBooks. Other than having only a single core, the later PowerBooks (or probably iBooks would be a better comparison) had much better GPU power than any of the 2006 Intel's that didn't have a dedicated GPU. Intel iGPUs have been pretty useless until very recently.

I 100% agree about the life support on them though. Snow Leopard and maybe even Lion, should've ran on G4s and G5s. If we applied their logic from the PPC to x86 switch to their current x86 to ARM switch, all the Intel Macs already including the Mac Pro 7,1 would be totally unsupported by macOS probably two or three releases ago. The 2005 PPCs got literally one OS upgrade. That always irritated me.
 
The 2005 PPCs got literally one OS upgrade. That always irritated me.

Agreed!! I was SO disappointed/angry with Apple when my late model Power Mac G5 DP 2.3 GHz only got the one OS bump, from the Tiger it was delivered with to Leopard. I will NEVER understand how Apple so completely failed their customer base on this one.
 
Outside of that, I'm sort of drawing blanks at this point. Does anyone have any other ideas on what could be adjusted in another hypothetical revision?

Provide an optional installation of a package manager capable of building modern software. (Doesn’t have to be MacPorts, there are other options too.)
Ideally provide some fundamental software in pre-built form, like gcc and cmake. For someone with only G4 hardware that’s a big deal.
 
Monterey is not 32 bit nor does it support 32 bit. Mojave was the last one to run 32 bit applications but it isn’t a 32 bit OS either.

I believe Lion 10.7 was the last one to actually be able to run on a 32 bit CPU, and even that needed coaxing.
You're right, I got my "M" OSes mixed up there! Thanks for catching that.
 
D

DO NOT use the Macintosh Repository, they rip off their user base by charging stuff. You can get it for free instead in the Macintosh Garden.
I can’t find Sorbet Leopard v2 on Macintosh Garden. The only page there is for ‘1.5’ and the filename is ‘R15’ dated 2022-05-02.
 
According to the author its real from this thread:


Sorbet Leopard v2 has been released! Alongside it comes a revised version of the original Full Changelog to better represent this version.

Some of the changes include:

o Full ADB-based notebook compatibility

o Machine-tailored network settings

o Display-tailored window sizing and placement settings

o A more comprehensive system tune up script

o The bundled Welcome document has been revised to convey information in a more cohesive manner

o Bundled documents are now located on the Desktop front and center

o Window shadows are now on by default

o The built-in WebKit and Terminal optimizations now apply system-wide

o The file system is now 2 GB smaller (Disk Utility cannot shrink partitions below 8 GB)

o Other minor changes and adjustments to enhance the overall user experience

-

Just make sure to manually set a hostname in System Preferences > Sharing > Computer Name, as that no longer comes built-in.

Otherwise, please continue to enjoy Sorbet Leopard!
 
Hey that's cool! I was not aware - derp :D . @z970 where can we DL v2 of Sorbet? I also only saw 1.5 on MG and the alternate download window.

At the bottom of the page, there's a list of older versions. You will need a Macintosh Garden account to access them.


Looking at this list, "v2" was actually followed by "1.4", and then 1.5. I think this was because there were already two development builds produced for the testing volunteers between its reveal in June '21 and subsequent release in November. From what I recall, it needed incremental builds to release because the targeted change list was so large and it took time to implement them all.

So I guess it went like Dev 1.0 > Dev 1.1 > Release 1.2 ("v1") > Release 1.3 ("v2") > Release 1.4 > Release 1.5

I think all of the original goals were achieved by 1.4, so 1.5 was for the first time mostly focused on just polishing everything and making the user experience better.

On another note, the supplemental update was just a modified cookie file for the Invidious instance in the Sorbet App Store. That instance has closed down now, so the update is useless. At some point, I need to get around to removing it and replacing the instance there with a better solution for YouTube I found a little while back. The whole store needs updating to showcase some cool new projects that were released in the years since.

DO NOT use the Macintosh Repository, they rip off their user base by charging stuff. You can get it for free instead in the Macintosh Garden.

They also selfishly hog Macintosh Garden's bandwidth (making it slower for everyone else) because they're constantly scraping its servers for new software and updates to add to their own. So they scrape the Garden's servers for free content, and then charge for it to the unsuspecting.

It is a very unsavory site. I wish the folks at reddit would stop promoting it.
 
Thanks for the clarification I’ll get R15. How do I find out about the ‘cool new projects that were released in the years since’?
 
Between Coreplayer and Mplayer mine could but with so many tweaks the quality was degraded - so 720P looked better.
Even 720P will run your CPU hot - better not to torture such vintage hardware and play good quality 360/480P!

Out of curiosity, do mplayer-devel, mpv or qmplay2 perform better? (I would expect that they do, but it may depend on multiple factors.)
On 10.5 (and 10.6, of course, these should build from my PPCPorts). On 10.4 it may be a painful endeavor though.
 
Out of curiosity, do mplayer-devel, mpv or qmplay2 perform better? (I would expect that they do, but it may depend on multiple factors.)
On 10.5 (and 10.6, of course, these should build from my PPCPorts). On 10.4 it may be a painful endeavor though.
I don't specifically remember trying those - though I suspect I gave mpv and qmplay2 a try?

I have regularly pitched the ancient Mplayer against newer compiled versions and FFPlay though and it still has the edge in terms of CPU use (and less audio sync issues) but the newer players have better compatibility.
 
  • Like
Reactions: MarkC426
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.