Can you tell me where I can find that app? Want to see if I can try to reproduce the error and try to fix it.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
10.6 Snow Leopard PowerPC Development
- Thread starter ChrisCharman
- WikiPost WikiPost
- Start date
-
- Tags
- poll powerpc snow leopard
- Sort by reaction score
- Status
Thank you! I have no idea what's happening then but I could reliably eject the drives I tested... this is very confusing lol
by the way, I couldn't figure out what's wrong with file sharing password but tested screen sharing and it worked. I'm attaching the files I've replaced to get to this point, maybe someone can figure out what's happening.
Yeah it’s very strange. We’ll figure it out eventually.
Thanks @educovas! I’ll have a look at the files later and keep digging as well.
Keyboard backlight works on both of my PowerBooks and is adjustable, however it isn’t as bright as when booted into Leopard strangely.
Picked up another machine to add to my collection today, for testing Snow Leopard on PowerPC. Was only £30! Absolute bargain.
Overview:
Apple eMac A1002 / M9425LL/A (1.25 GHz Combo)
| Machine Model: | Power Mac6,4 |
| CPU Туре | PowerPC G4 (1.1) |
| Number Of CPUs: | 1 |
| CPU Speed: | 1.25 Ghz |
| L2 Cache (per CPU): | 512 KB |
| Memory | 256 MB |
| Bus Speed | 167MHz |
| Boot ROM Version: | 4.8.2f1 |
For those of you that want to relaunch Finder to remove unmounted volumes from the desktop, here's a little utility that I knocked up to do the job - put it in your Applications and maybe drag it to the dock for a one click solution 
Both the Kill Finder app, plus the script file it's based on included for info...
Cheers
Hugh
Both the Kill Finder app, plus the script file it's based on included for info...
Cheers
Hugh
I have a legit copy. It only works with a USB dongle. That is the unfortunate part.
Still I will happily do testing for you.
Real Life (tm) has intruded on my ability to test for some time recently but this was wonderful to see!! I've gotten it installed and I'm posting this from the InterWebPPC in that image. Great job @ChrisCharman ! I'd love to understand what combination of updates finally cracked the UDP issue.
@atester2001, did one of your combination of settings tried actually allow ssh connections from another computer to your iMac? I tried setting the second option for the Firewall and turning on Remote Login in Sharing but cannot connect to my PowerBook remotely. I set these using the Systems Preferences UI but did attempt @ChrisCharman's command below when that didn't work (without any change in behavior):
sudo defaults write /System/Library/Preferences/com.apple.alf globalstate -int 0
Thanks @FBSD_Mac
Real life has been busy for me too, so have nothing further to offer yet aside from what you’re now testing.
Unfortunately, the files that I’d thought had to be replaced that fixed some of the networking issues, alone don’t account for the whole problem with the network stack. Further still the fix is proving hard for others to reproduce on older images as i’ve seemingly missed something important in my analysis that was replaced on my image. I will compare precisely what was changed when i have a good amount of free time to delve deeper, and tinker a bit more.
Watching some of the Developer Sessions (linked in the wiki via internet archive) revealed to me that MDNSResponder is responsible for ALL DNS on the system OS-wide, which moves away from how it was handled on Leopard - in fact disabling MDNSResponder on Snow Leopard will render all OS-wide DNS services unusable and is not recommended.
As I haven’t had time with my machines recently i’ve been dropping in and out to respond to comments and tweak the first 3x posts of the thread, but they are still very much WIP.
I hope to have the the 10A190 and 10A222 XCode 3.2 Beta packages uploaded and linked soon as well, for people that don’t want to download the complete .iso for each build just to have access to those.
Issue resolved by replacing AGL.framework with the one from 10.5.8.
Well done @educovas! More OpenGL fixes are always good.
Has anyone looked into Java yet as we don’t have a functioning Java on the system presently?
This is important for the OS itself not just 3rd party Java apps.
Thanks, @ChrisCharman -- I had seen the mDNSResponder change earlier when I was trying to get DNS working but didn't make any progress like yours!
I still haven't managed to connect to the PowerBook via ssh so for now I'm using reverse port forwarding on a connection from the PowerBook to another one of my computers.
By the way, if no one else has mentioned this it appears Bluetooth is non-functional. It may actually not be turning on as I don't see the computer with other devices and it also doesn't see any devices in pairing mode.
I still haven't managed to connect to the PowerBook via ssh so for now I'm using reverse port forwarding on a connection from the PowerBook to another one of my computers.
By the way, if no one else has mentioned this it appears Bluetooth is non-functional. It may actually not be turning on as I don't see the computer with other devices and it also doesn't see any devices in pairing mode.
Yeah bluetooth is currently non-functional. I really need to update the table of known issues so apologies for that, there are lots of quirks and bugs to iron out still.
It should go in /System/Library/Frameworks/AGL.framework/Versions/A/AGL
It’s more complicated unfortunately. OpenJDK can be installed, but Apple integrated their own versions of Java into OS X and I don’t know if OpenJDK can be used as a drop-in replacement for all functions. The problem for us is that some components in the OS are written in Java so we need to look into this more deeply. There are some users on the forum, that have spent a lot of time working with Java on Leopard, so hopefully they will be able to offer some assistance.
@JoyBed has a lot of experience with Mac OS X and Java.
Last edited:
@ChrisCharman @educovas You could just take openjdk8 and try using it for w/e purpose of interest.
Here are older versions: https://macos-powerpc.org/compilers/openjdk/openjdk8
Here is the latest one: https://macos-powerpc.org/packages/openjdk8-powerpc
You may need to either provide a few libraries externally or relink to system ones (which may or may not work, I never tried it). List is here: https://github.com/macos-powerpc/po...782baf/java/openjdk8-powerpc/Portfile#L91-L96
Notice, all openjdk builds currently have no GUI support (cocoa won’t be supported, X11 might be, but requires substantial changes to the build system).
Why No Java In 10.6.8 for PowerPC?
Mac OS X 10.6 Snow Leopard was targeted at intel based machines exclusively, and thus all Apple Java SE 6 implementations from 10.6-10.6.8 are only compatible with intel 32bit and 64bit.
@Jazzzny provides modern Java 17 for intel 10.6+ over on this thread.
I have been looking into Java today and the following findings are untested but look to me like a good start and source for a potential fix, for the moment.
WARNING: Altering the system Java or any other system component is highly experimental and is not recommended. Please only do so at your own risk! If you do not need Java then it can be safely ignored.
Reminder to all that WWDC Developer Sessions 2007-2009 are linked in the WikiPost as a research reference.
Java in OS X is a Core Framework and has been built into the operating system since 1998.
Each version of the OS is pegged to a specific Apple customised version, although users can install and switch to alternative versions if they like.
The operating system itself has a preferred version that is linked to at /System/Library/Frameworks… This is the version that should not be changed from the OS default version number. We do need to update the system Java SE 6 to be compatible with PowerPC.
Paths for other versions are safe to link to from /usr/bin/java and /Library/Java/Home.
Java SE 6 from the Snow Leopard 2008 Developer Preview onwards is the only officially supported version of Java, and only supports X86/X86_64.
The officially supported version for Leopard is SE 5.0, however, Apple did release separate developer previews for Tiger and Leopard (PowerPC) for their Java SE 6 implementation.
Java SE 6 Release 1 Developer Preview 6
This version will not install directly, however there is this useful guide which details step-by-step how to manually install Java SE 6 on Leopard, and may (untested and speculative) work for us in theory to replace the intel only implementation on our current build of 10.6.8 for PowerPC:
There is also a Java 6 and 7 implementation created by @JoyBed and detailed on this forum available to download from here.
In addition @barracuda156 has made OpenJDK8 available as well for those wanting to add a more recent version of Java to their system for development purposes (as a port)
There are other features and benefits to fixing the SE 6 implementation in the OS, particularly for 64bit but even 32bit, including far better integration with the GUI and with scripts.
A large part of Safari ‘Crash Resistance’ and stability on Snow Leopard is due to the ‘Out-Of-Browser’ plugin implementation. If the plugin crashes then it doesn’t take down the browser.
Another reason it is important to adhere to the correct system version is for compatibility with legacy apps, indeed Apple even provided an update for more recent versions of MacOS to address this issue on modern systems.
Attachments
Last edited:
As I recall, it is pretty useless, since neither headers nor libs provide what other apps expect (in particular, a newer JDK, which is what we ultimately need, since nothing prior to JDK8 is usable nowadays). Likewise, it probably won’t work as an OS component.
But if someone fixes it, that may be useful to restore Cocoa GUI in openjdk8.
The system needs SE 6. Users can install and select more recent JDKs for development purposes if targeting modern software.
Nothing in the system’s ppc slices can possibly need Java, since it never existed in the first place. The only software which does need Java is third-party, which was developed for Intel (and then it expects SE 6), or remnants of 10.4–10.5 era.
I mean, I have zero objections to having some working Apple Java, I just do not see any benefit in it for the OS itself.
@barracuda156 this is simply just incorrect. Java is a Core part of OS X Snow Leopard and it is pegged at version SE 6. There are internal OS components and apps and plugins etc that are built to work with the Apple SE 6 implementation. If you’re interested there are a lot of links to documentation and references in the wiki post explaining how the operating system works, and several hours of Apple Developer talks that go into more detail.
What you build to run on Snow Leopard for PowerPC (3rd party apps) is separate from what is needed to run Snow Leopard on PowerPC (as it is intended to run on intel), and also separate from what is required to run period appropriate legacy software on the platform which many users desire, despite your seemingly persistent desire to disregard that fact.
Fixing the OS implementation doesn’t prevent anyone from using OpenJDK or any other port.
No system components of 10.6 rely on Java at all, except for the Java control panel (though even that is a stretch, for obvious reasons). Apple only provided Java as a way for developers to write applications easily, though cracks were already showing by 10.6 as Apple continued their push for Cocoa/AppKit.
Well, we do not have SE 6 SL for powerpc, and likely it never existed. What we have is some SE 6 for another OS.