I've been struggling to find Intel Tiger images that will work on my A1212, which needs 10.4.8 or later. Would a 10.4.6 image work, even if it wasn't supported on the Late 2006 Macs?
Yeah, the grey discs is as good as it gets for Tiger client on Intel.Part of the reason you might have had trouble is there was never any such thing as a retail Tiger installer for Intel Macs. The earliest Intel Macs merely shipped with Tiger preinstalled; there was no older OS to upgrade from.
That installer is universal and works on both Intel and PPC Macs. It uses version 10.4.7 build 8K1079, the same build the original Mac Pro came with.There is a retail installer for Tiger Server, because in that case people needed a way to upgrade from client.
It's still miles away from those hacked installers modified to work on PCsSystem specific disks can be modified to work on any hardware, but then it’s not an official installer any more.
Some people REALLY like Tiger. There are a number of reasons for that, but I think the main reason for wanting to run Tiger on an Intel Mac is speed. Particularly if you're not intending to use the Mac on the internet.As a curiosity: why? Those machines work MUCH better with Snow Leopard.
I love Tiger because of its UI. Snow Leopard is great, but the UI is “unobtrusively unimpressive” IMHO.Some people REALLY like Tiger. […]
<chuckle>I love Tiger because of its UI. Snow Leopard is great, but the UI is “unobtrusively unimpressive” IMHO.
That is precisely it, I want to run Tiger for it's speed, I have Mountain Lion on it for daily use so no big deal about internet for me.I think the main reason for wanting to run Tiger on an Intel Mac is speed. Particularly if you're not intending to use the Mac on the internet.
On my 2,1 with a SSD, Tiger feels like Monterey does on my M1. Its absurd fast.That is precisely it, I want to run Tiger for it's speed, I have Mountain Lion on it for daily use so no big deal about internet for me.
Ah. I wouldn’t be too sure about it being the faster option, then: it still had a lot of stuff running in Rosetta and snow leopard was much more optimised.Some people REALLY like Tiger. There are a number of reasons for that, but I think the main reason for wanting to run Tiger on an Intel Mac is speed. Particularly if you're not intending to use the Mac on the internet.
You have the OS with the least overhead and a Mac with an Intel processor. If your Mac has an SSD then this is about as fast as you're ever likely to get that Mac to go.
I prefer my features, options and customizations and am willing to sacrifice some speed for that - but speed is king for a lot of users.
AFAIK Tiger itself was native throughout but some major apps were late to the party.I wouldn’t be too sure about it being the faster option, then: still had a lot of stuff running in Rosetta […]
According to this, onlyNot totally: back then it was widely criticised for having performance hindered by parts running in Rosetta. [...]
ATSServer
requires Rosetta.The article says 10.4.3.On which version? […]
There sure was, it’s what the DTKs originally shipped with. The article even contains a screenshot of it.There was never a released 10.4.1 for x86 […]
Afaik the first image to circulate, on which the deadmoo was based on, was a 10.4.3.The article says 10.4.3.
There sure was, it’s what the DTKs originally shipped with. The article even contains a screenshot of it.
10.4.4 was the first x86 release available to consumers on production hardware.
I have the Deadmoo image and an install DVD. Both are 10.4.1 build 8B1025.Afaik the first image to circulate, on which the deadmoo was based on, was a 10.4.3.
I wonder why Tiger on Intel relied on stuff running via Rosetta to bring up the GUI or whatever then?Also several odd assumptions (such as apple intentionally relying on Rosetta to lock off non apple hardware)
Is the Darwin/x86 boot loader related to or based on the one used by NeXTSTEP/OPENSTEP/Rhapsody on x86? If so, maybe it was a matter of bad wording.or plainly wrong statements (such as the boot loader used on early hackintosh systems being the one “written for next/apple”, which is a totally nonsensical statement, in fact it was the usual Darwin/x86 one
My memory must be mistaken then.I have the Deadmoo image and an install DVD. Both are 10.4.1 build 8B1025.
That’s actually easy to answer: porting takes time and resources, when they could obtain a viable system using emulation, even if at a performance cost, they did, with the idea of properly port the code over gradually in the following releases, which they did.I wonder why Tiger on Intel relied on stuff running via Rosetta to bring up the GUI or whatever then?
Possibly…As they wrote it it’s pure nonsense.Is the Darwin/x86 boot loader related to or based on the one used by NeXTSTEP/OPENSTEP/Rhapsody on x86? If so, maybe it was a matter of bad wording.
Safari and Finder in brushed metal.
Just no.