Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Snow Leopard on Unsupported PowerPC Macs

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
barracuda156 said:
If you got the one compatible with the Quad, absolutely, I will highly appreciate that (and of course cover postage).
Click to expand...

Ah. The multi-core Power Macs use the A1126, and because I’ve yet to own one, I don’t know whether those use an “innie” of “outie” receptacle. Thing is, I might have one, but I’d need to check on which receptacle it uses.

But if you can find out which one the multicore Power Mac G5s accept, let me know and if it’s the one I have, I’ll be happy to send one your way. :)
 
Last edited:
  • Like
Reactions: ChrisCharman and barracuda156
ChrisCharman said:
I’m intrigued @B S Magnet
Click to expand...

Naw it was nothing special; I erroneously posted twice in a row instead of aggregating a two-part reply into one post (the second ¶ of the previous reply was what was posted in the second post I later removed). There’s just no way to remove my own post without getting a mod involved.
 
  • Like
Reactions: ChrisCharman
Things I’ve been working on this week, over on the 10A96 side:

1) Trying to figure out why opening a file — ⌘O (File > Open) — in either InterwebPPC or TenFourFox doesn’t open the usual dialogue box; if pressing ⌘O multiple times in a row (out of frustration), then it can crash the browser.

It’s an issue I’ve been aware of for a few months, but it’s generally not been a high priority. I haven’t tested a bone-stock install of 10A96 to determine whether this is either a bug of the modifications or a bug with the build itself. It comes up when, say, I want to “attach files” to a post on MR forums. This issue prevents that from being possible.

2) Somewhat related, possibly, but this one’s likely on my end: the other day, I tried repeating a scan-to-PDF-to-open-in-Photoshop CS4 task I did back in August without trouble, but this time something caused Photoshop to hang indefinitely (though not crash) after copy-pasting an image from one Photoshop document to another. It has me worried that something I’ve changed over the past couple of months is the culprit, and backtracking could take a while. It might be related to the pasteboard server (pbs), but I’m not yet sure.

3) I’ve just (barely) started to look at differences between binaries in /usr/* 10A96 and other builds. This one’s tougher because it’s difficult to figure out what version a binary is (i.e., running a “[binary name] --version” doesn’t often work, since that flag was never implemented in a lot of low-level binaries). It seems this is the layer between the kernel and frameworks (with kexts heaped atop all those). So that could be a long slog.

4) I’m trying to pinpoint where the sizing for this feature in (mostly) Finder lives:

1635947009744.png
1635947255028.png


On left is how the label boxes appear in Leopard (and the SL-PPC betas); on right is how they appear in Snow Leopard 10.6.0 through 10.6.8. This is another thing I’ve mentioned before, but still haven’t pinpointed where it is. My guess, unless somebody else might know, is it’s something buried deep inside Finder’s code itself. I do know it probably isn’t in one of the “.nib” interface files located within each supported language set (i.e., “Contents > Resources > English.lproj…”). I could be completely wrong, though.

5) This one’s not just for SL-PPC, but really for pretty much everything from 10.5.0 to at least Lion (I think): creating .icns for earlier Mac products so that they appear correctly on the left bar for Finder windows. Back in June, I brought over more recent .icns and associated .plist for CoreTypes.bundle which updated the appearance for many of the more recent Macs. Now I’m concentrated on the other direction — namely for now, the iMac G3 and iBook G3 (PowerBook2,1 and PowerBook2,2, best known as the clamshell iBook).

Not only do .icns need to be made (which I’ve done, sourcing from Apple’s original media images for these products), but the associated .plist needs the correct definitions in place so that when a remote computer in the local network says, “I’m an iBook 2,1 [or 2,2]”, the host (local) computer can look it up on the plist and say, “Ah, here you are, I’m supposed to use this .icns file to represent you.” Except that an iBook clamshell or iMac G3 show up instead as:

1635948216253.png


and

1635948276143.png


And not with one of these icons, respective to their hardware :

1635949207041.png
1635949239521.png


So in short, there’s a lot to work on. But y’all ought to know what I’m preoccupied by right now. :)
 
  • Like
  • Love
Reactions: fra9000, maxoakland, barracuda156 and 1 other person
B S Magnet said:
Things I’ve been working on this week, over on the 10A96 side:

1) Trying to figure out why opening a file — ⌘O (File > Open) — in either InterwebPPC or TenFourFox doesn’t open the usual dialogue box; if pressing ⌘O multiple times in a row (out of frustration), then it can crash the browser.

It’s an issue I’ve been aware of for a few months, but it’s generally not been a high priority. I haven’t tested a bone-stock install of 10A96 to determine whether this is either a bug of the modifications or a bug with the build itself. It comes up when, say, I want to “attach files” to a post on MR forums. This issue prevents that from being possible.

2) Somewhat related, possibly, but this one’s likely on my end: the other day, I tried repeating a scan-to-PDF-to-open-in-Photoshop CS4 task I did back in August without trouble, but this time something caused Photoshop to hang indefinitely (though not crash) after copy-pasting an image from one Photoshop document to another. It has me worried that something I’ve changed over the past couple of months is the culprit, and backtracking could take a while. It might be related to the pasteboard server (pbs), but I’m not yet sure.

3) I’ve just (barely) started to look at differences between binaries in /usr/* 10A96 and other builds. This one’s tougher because it’s difficult to figure out what version a binary is (i.e., running a “[binary name] --version” doesn’t often work, since that flag was never implemented in a lot of low-level binaries). It seems this is the layer between the kernel and frameworks (with kexts heaped atop all those). So that could be a long slog.

4) I’m trying to pinpoint where the sizing for this feature in (mostly) Finder lives:

View attachment 1901416View attachment 1901419

On left is how the label boxes appear in Leopard (and the SL-PPC betas); on right is how they appear in Snow Leopard 10.6.0 through 10.6.8. This is another thing I’ve mentioned before, but still haven’t pinpointed where it is. My guess, unless somebody else might know, is it’s something buried deep inside Finder’s code itself. I do know it probably isn’t in one of the “.nib” interface files located within each supported language set (i.e., “Contents > Resources > English.lproj…”). I could be completely wrong, though.

5) This one’s not just for SL-PPC, but really for pretty much everything from 10.5.0 to at least Lion (I think): creating .icns for earlier Mac products so that they appear correctly on the left bar for Finder windows. Back in June, I brought over more recent .icns and associated .plist for CoreTypes.bundle which updated the appearance for many of the more recent Macs. Now I’m concentrated on the other direction — namely for now, the iMac G3 and iBook G3 (PowerBook2,1 and PowerBook2,2, best known as the clamshell iBook).

Not only do .icns need to be made (which I’ve done, sourcing from Apple’s original media images for these products), but the associated .plist needs the correct definitions in place so that when a remote computer in the local network says, “I’m an iBook 2,1 [or 2,2]”, the host (local) computer can look it up on the plist and say, “Ah, here you are, I’m supposed to use this .icns file to represent you.” Except that an iBook clamshell or iMac G3 show up instead as:

View attachment 1901435

and

View attachment 1901436

And not with one of these icons, respective to their hardware :

View attachment 1901447View attachment 1901449

So in short, there’s a lot to work on. But y’all ought to know what I’m preoccupied by right now. :)
Click to expand...
Hi @B S Magnet

In regard to point (3) are you using otool to check the binaries currently?
 
ChrisCharman said:
Hi @B S Magnet

In regard to point (3) are you using otool to check the binaries currently?
Click to expand...

I am, but it’s just really slow-going (the difference between running it individually in two term windows, side-by-side, between two binary sources, and simply viewing the version number in a Finder window column). And when working with command-line stuff, “--version” comes more automatically than “otool -L” does.
 
  • Like
Reactions: ChrisCharman
B S Magnet said:
I am, but it’s just really slow-going (the difference between running it individually in two term windows, side-by-side, between two binary sources, and simply viewing the version number in a Finder window column). And when working with command-line stuff, “--version” comes more automatically than “otool -L” does.
Click to expand...
Yes this is also the method i’ve been using and I can’t help but wonder if there isn’t a better way, perhaps piping results via diff or something similar. There are some other methods i’m exploring so i will share if i find a more efficient and less time-consuming way of doing this.
 
  • Like
Reactions: B S Magnet
barracuda156 said:
You mean what in particular? Which factor?
Click to expand...
Unfortunately I can't remember. I hit the wrong button and it doesn't have a quote and I can't find what I was responding to. I vaguely remember it was some kind of interesting technical issue that I hadn't heard about before

EDIT: Now I remember: It was about support for non-PCI Graphics cards. Something about NVidia or ATI starting to use a different technology and dumping support for the graphics cards, which seemed like it would've required a lot of work on Apple's part to make up for it. It made me think maybe that was the straw that broke the camel's back
 
  • Like
Reactions: ChrisCharman
maxoakland said:
Unfortunately I can't remember. I hit the wrong button and it doesn't have a quote and I can't find what I was responding to. I vaguely remember it was some kind of interesting technical issue that I hadn't heard about before

EDIT: Now I remember: It was about support for non-PCI Graphics cards. Something about NVidia or ATI starting to use a different technology and dumping support for the graphics cards, which seemed like it would've required a lot of work on Apple's part to make up for it. It made me think maybe that was the straw that broke the camel's back
Click to expand...

It is due to the details I described to you a few days ago.
 
  • Like
Reactions: ChrisCharman and barracuda156
barracuda156 said:
I was googling in an attempt to find later builds, and this popped up: http://macosrumors.com/2009/02/10/macosx-106-snow-leopard-1st-peek/3/
Apparently 10A261 did actually run on PowerPC, at least on G5.
View attachment 1904635
Click to expand...

Excellent sleuthing! Thanks for posting this finding! :)

It might be the longest of long shots to email the remaining folks at rumors-at-macosrumors-dot-com — as per this post — to ask whether any of the old editorial team might still have the Universal Binary Build of 10A261 or later buried in some old DVD-R stack or archived drive somewhere and, if so, whether they’d be cool with quietly and anonymously adding it/them to the Macgarden archive page.
 
  • Like
Reactions: pc297, barracuda156, ChrisCharman and 2 others
Super-minor update:

In Table 1 of the WikiPost, you’ll find a new-to-this-project beta build of Snow Leopard which turned up in one of my periodic, “I should try this query” searches through Archive-dot-org’s collection. I turned up with a hit this time — one which, evidently, had not been chronicled for this project, even though it’s unlikely to impact Universal Binary-related stuff very much.

Previously, Table 1 pointed to a seed build called “10A402” which was pushed in July 2009 via Software Update. The hit I found today is for Build 10A403 which, according to its uploader, reportedly appeared long enough on the Apple Developer site to be found, sometime in 2016, in a search for Server-related software.

1636321285875.png


I went ahead and logged onto the ADC site this day to see whether this still quietly lingered at the bottom of the Developer pile of software. It’s long-gone, but the above is from the upload on archive-dot-org. At present, I’m grabbing it via torrent and filing it away in my local collection of 10A* builds. But I figured I’d let y’all know about it in case you wanted to also have a look. :)
 
  • Like
  • Wow
Reactions: maxoakland, barracuda156, ChrisCharman and 1 other person
B S Magnet said:
Excellent sleuthing! Thanks for posting this finding! :)

It might be the longest of long shots to email the remaining folks at rumors-at-macosrumors-dot-com — as per this post — to ask whether any of the old editorial team might still have the Universal Binary Build of 10A261 or later buried in some old DVD-R stack or archived drive somewhere and, if so, whether they’d be cool with quietly and anonymously adding it/them to the Macgarden archive page.
Click to expand...

I found it and DL'ing now. How to tell if it's UB?
 
  • Like
Reactions: ChrisCharman
666sheep said:
I found it and DL'ing now. How to tell if it's UB?
Click to expand...

A good starting point might be to extract “mach_kernel” and “Finder.app” from the .dmg using Pacifist, and then using Terminal to run either or both of “file [binary file name]” or “otool -L [binary file name]” to see what it reports back. I’m anticipating the “mach_kernel” and “Finder” binaries to both be “two architectures” (i386 and x86_64), but if the binary inside the Contents/MacOS subdirectory of Finder.app reports back that it’s anything other than “two architectures”, then we might be onto something significant.

Update: 10A403 appears to be an internal-only immediate successor of the 10A402 seed update which was released publicly to developers. I just pulled and ran both file and otool on “Finder” and “mach_kernel”; as with earlier builds, while mach_kernel is a three-architecture binary (which makes more sense if factoring whether Apple were developing an internal-only Universal Binary fork for whatever reason).

Code: 
sh-3.2# otool -L ./*
./Finder (architecture x86_64):
    /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv (compatibility version 1.0.0, current version 67.0.0)
    /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 287.0.0)
    /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 36910.0.0)
    /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom (compatibility version 2.0.0, current version 164.0.0)
    /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/PrivateFrameworks/FileSync.framework/Versions/A/FileSync (compatibility version 100.0.0, current version 354.0.0)
    /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
    /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI (compatibility version 1.0.0, current version 110.0.0)
    /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore (compatibility version 1.2.0, current version 1.6.0)
    /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 15.0.0)
    /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook (compatibility version 1.0.0, current version 323.0.0)
    /System/Library/Frameworks/Collaboration.framework/Versions/A/Collaboration (compatibility version 1.0.0, current version 38.0.0)
    /usr/lib/libicucore.A.dylib (compatibility version 1.0.0, current version 40.0.0)
    /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox (compatibility version 1.0.0, current version 432.0.0)
    /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI (compatibility version 1.0.0, current version 323.0.0)
    /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)
    /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 44.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 548.0.0)
    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 38.0.0)
    /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 748.0.0)
    /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1031.0.0)
./Finder (architecture i386):
    /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv (compatibility version 1.0.0, current version 67.0.0)
    /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 287.0.0)
    /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 36910.0.0)
    /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom (compatibility version 2.0.0, current version 164.0.0)
    /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/PrivateFrameworks/FileSync.framework/Versions/A/FileSync (compatibility version 100.0.0, current version 354.0.0)
    /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
    /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI (compatibility version 1.0.0, current version 110.0.0)
    /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore (compatibility version 1.2.0, current version 1.6.0)
    /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 15.0.0)
    /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook (compatibility version 1.0.0, current version 323.0.0)
    /System/Library/Frameworks/Collaboration.framework/Versions/A/Collaboration (compatibility version 1.0.0, current version 38.0.0)
    /usr/lib/libicucore.A.dylib (compatibility version 1.0.0, current version 40.0.0)
    /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox (compatibility version 1.0.0, current version 432.0.0)
    /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI (compatibility version 1.0.0, current version 323.0.0)
    /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)
    /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 44.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 548.0.0)
    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 38.0.0)
    /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 748.0.0)
    /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1031.0.0)
./mach_kernel:
sh-3.2# file mach_kernel
mach_kernel: Mach-O universal binary with 3 architectures
mach_kernel (for architecture x86_64):    Mach-O 64-bit executable x86_64
mach_kernel (for architecture i386):    Mach-O executable i386
mach_kernel (for architecture ppc):    Mach-O executable ppc
sh-3.2# file Finder
Finder: Mach-O universal binary with 2 architectures
Finder (for architecture x86_64):    Mach-O 64-bit executable x86_64
Finder (for architecture i386):    Mach-O executable i386
sh-3.2#
 
Last edited:
  • Like
Reactions: barracuda156 and ChrisCharman
666sheep said:
OK, with 10A261 i found here, I got exactly the same output as you: mach_kernel is 3 architectures, Finder only x86_64 and i386.
Click to expand...

The versions we (i.e., the outside world, outside of 1 Infinite Loop) have been privy to have all trended toward Intel-only architecture after Builds 10A96 and 10A190. What makes the above pull-quote posted by @barracuda156 so intriguing is we now know definitively there were post-10A190 builds quietly and confidentially leaked out of 1 Infinite Loop. The current whereabouts of that build — or those builds — outside of 1 Infinite Loop remains anyone’s guess.

I’m half-tempted to create a confidential email account to post on my MR profile so that anyone who may still have one of those Universal Binary builds can write to mention in confidence where to download it and then add to Macgarden and/or Archive-dot-org, assuring their privacy is maintained and their long-term relationship with the ADC isn’t jeopardized. Update: and now I’ve done just that.
 
Last edited:
  • Like
Reactions: barracuda156 and ChrisCharman
666sheep said:
OK, with 10A261 i found here, I got exactly the same output as you: mach_kernel is 3 architectures, Finder only x86_64 and i386.
Click to expand...
The Mach_Kernel will most likely be universal in all builds, however this cannot be moved across the various seeds. What we may find however are other later PowerPC compatible binaries that we can use. Unless we can get hold of the internal only builds.
 
B S Magnet said:
A good starting point might be to extract “mach_kernel” and “Finder.app” from the .dmg using Pacifist, and then using Terminal to run either or both of “file [binary file name]” or “otool -L [binary file name]” to see what it reports back. I’m anticipating the “mach_kernel” and “Finder” binaries to both be “two architectures” (i386 and x86_64), but if the binary inside the Contents/MacOS subdirectory of Finder.app reports back that it’s anything other than “two architectures”, then we might be onto something significant.

Update: 10A403 appears to be an internal-only immediate successor of the 10A402 seed update which was released publicly to developers. I just pulled and ran both file and otool on “Finder” and “mach_kernel”; as with earlier builds, while mach_kernel is a three-architecture binary (which makes more sense if factoring whether Apple were developing an internal-only Universal Binary fork for whatever reason).

Code: 
sh-3.2# otool -L ./*
./Finder (architecture x86_64):
    /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv (compatibility version 1.0.0, current version 67.0.0)
    /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 287.0.0)
    /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 36910.0.0)
    /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom (compatibility version 2.0.0, current version 164.0.0)
    /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/PrivateFrameworks/FileSync.framework/Versions/A/FileSync (compatibility version 100.0.0, current version 354.0.0)
    /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
    /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI (compatibility version 1.0.0, current version 110.0.0)
    /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore (compatibility version 1.2.0, current version 1.6.0)
    /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 15.0.0)
    /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook (compatibility version 1.0.0, current version 323.0.0)
    /System/Library/Frameworks/Collaboration.framework/Versions/A/Collaboration (compatibility version 1.0.0, current version 38.0.0)
    /usr/lib/libicucore.A.dylib (compatibility version 1.0.0, current version 40.0.0)
    /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox (compatibility version 1.0.0, current version 432.0.0)
    /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI (compatibility version 1.0.0, current version 323.0.0)
    /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)
    /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 44.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 548.0.0)
    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 38.0.0)
    /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 748.0.0)
    /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1031.0.0)
./Finder (architecture i386):
    /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv (compatibility version 1.0.0, current version 67.0.0)
    /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 287.0.0)
    /System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 36910.0.0)
    /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom (compatibility version 2.0.0, current version 164.0.0)
    /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/PrivateFrameworks/FileSync.framework/Versions/A/FileSync (compatibility version 100.0.0, current version 354.0.0)
    /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
    /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI (compatibility version 1.0.0, current version 110.0.0)
    /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore (compatibility version 1.2.0, current version 1.6.0)
    /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 15.0.0)
    /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/QuickLook.framework/Versions/A/QuickLook (compatibility version 1.0.0, current version 323.0.0)
    /System/Library/Frameworks/Collaboration.framework/Versions/A/Collaboration (compatibility version 1.0.0, current version 38.0.0)
    /usr/lib/libicucore.A.dylib (compatibility version 1.0.0, current version 40.0.0)
    /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox (compatibility version 1.0.0, current version 432.0.0)
    /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit (compatibility version 1.0.0, current version 1.0.0)
    /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI (compatibility version 1.0.0, current version 323.0.0)
    /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
    /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
    /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 227.0.0)
    /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 44.0.0)
    /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 548.0.0)
    /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 38.0.0)
    /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 748.0.0)
    /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1031.0.0)
./mach_kernel:
sh-3.2# file mach_kernel
mach_kernel: Mach-O universal binary with 3 architectures
mach_kernel (for architecture x86_64):    Mach-O 64-bit executable x86_64
mach_kernel (for architecture i386):    Mach-O executable i386
mach_kernel (for architecture ppc):    Mach-O executable ppc
sh-3.2# file Finder
Finder: Mach-O universal binary with 2 architectures
Finder (for architecture x86_64):    Mach-O 64-bit executable x86_64
Finder (for architecture i386):    Mach-O executable i386
sh-3.2#
Click to expand...
Excellent to have another build to take apart for goodies! A big thank you to @ASentientBot for uploading the 10A403 server internal build, license key and seed notes to the archive. I wonder how many other builds lay waiting to be uncovered?
 
  • Like
Reactions: ASentientBot
barracuda156 said:
There was also 10A222 Server build, but the torrent I was able to find so far seems long dead.

View attachment 1905573
Click to expand...
The client build is available Here along with the 10A222 kernel debug kit but i haven’t uploaded the server version as I don’t have that one yet. In theory there should be 432 different internal edition builds - 10A403 is the only additional build we’ve come across for a while now unfortunately.
 
If anybody here has ftp access to the software repository held at Beta Archive, there are several builds available there that we are missing.

The builds listed there are:

10A096
10A190
10A222
10A261
10A286
10A314
10A354
10A380
10A403
10A432

If you are able to download and share it would be a great help to those of us working on getting Snow Leopard on PowerPC up and running.
 
  • Like
Reactions: barracuda156
ChrisCharman said:
The client build is available Here along with the 10A222 kernel debug kit but i haven’t uploaded the server version as I don’t have that one yet. In theory there should be 432 different internal edition builds - 10A403 is the only additional build we’ve come across for a while now unfortunately.
Click to expand...

What does the kernel debug kit do by the way? (Sorry if a silly question.)
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back