All files that I've replaced are in the post
#2,273 so anyone could get that zipped folder and create their own installation. I've installed the OS on an Intel Mac, imaged the installation, then restored to the PPC Mac.
I appreciate the quick reply.
What you provided with that post was a general
overview of the areas you replaced in your imaged build. This was not an
individual-level breakdown I asked to be provided then, nor asked in what I posted to this discussion about an hour or so ago.
The way the wikipost’s
Table 4 delivers on the mandate of individual-level breakdown is what I was — and am — requesting. We need that to repeat the conditions to make possible your uploaded image of build 10A222.
Although it may not
seem obvious, I came to learn, through two years of testing this project, how this granular-level approach helps to spot conditions wherein a single component, library, or kext from one area of functionality — say, wifi; model-specific hardware sensors; and so on — might pose as a solitary barrier to prevent another areas of the system/hardware from functioning properly. Scalpel, not scissors.
That we are seeing problems with the 10A222 image you uploaded not booting properly, successfully, and/or completely, on systems which
should be able to do so, points to some individual-level components which may require an item-by-item swap.
We get to figuring out
what those choke points are once we all have access to the same, granular-level changes you made to make your build run properly on in your A1106 1.5GHz PowerBook. Yes, this is slow and exhaustive. It may feel tedious. It’s also how thorough, repeatable QA testing slogs ahead.
Cheers.