Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Okay, fine, I did it. I installed the SL alpha build. My biggest blocker was lack of sleep on portables. Solution: Mac mini, I guess. Used to be a server in the server hallway but it really didn't do servery things so I pulled it out and deployed Snowy to it, along with PPCPorts and friends.

View attachment 2648520

it was either this or the Quad and my power bill is already ridiculous from running the air con, so the Mini it is

I recommend pulling today’s updates, some stuff for Wayland was fixed (in Owl and foot), and I got swayimg working too.
 
Anyone interested in a terminal document reader/converter? No dependencies (zlib at runtime), basic, but with support for math symbols, emojis, Asian scripts and some layout.

docx.png


minimark in PPCPorts
 
Alright, here's that for ya. Ran into a small snag with dependencies but that was dealt with real quick; shouldn't adversely affect these results.

@Doq If it is doable again, will be really helpful at this point.

Need to follow exact steps to ensure we actually test what we need to be tested. On any G4 machine:

1. Make sure no local override of ffmpeg8 exists (if it does, temporarily remove it: we need to use macos-powerpc source).
Code:
% port file ffmpeg8
/opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/multimedia/ffmpeg8/Portfile

2. Run the following:
Code:
sudo port deactivate active
sudo port -v sync
sudo port clean ffmpeg8 x264
sudo port -v patch ffmpeg8 +G4
sudo port -v -N destroot ffmpeg8 +G4
(If you have ccache enabled in macports.conf, then do `sudo port install ccache` before ffmpeg, otherwise it will refuse to configure.)
This runs patch stage separately to make sure altivec patches are used (you should see 0001-0031 patch series applied).

Once the build completes,
Code:
cd /opt/local/var/macports/build/_opt_local_var_macports_sources_macos-powerpc.org_macos-powerpc_PPCPorts_ports_multimedia_ffmpeg8/ffmpeg8/work/ffmpeg-8.1.2
export CC=/opt/local/bin/gcc-mp-16 && sudo make tests/checkasm/checkasm
./tests/checkasm/checkasm --bench 2>&1 | tee ~/bench-ffmpeg-g4-patch0031.txt

P. S. @Forest Expertise Assuming you had no issues with ffmpeg8 build earlier, you could do this as well. I need some input from G4 to finalize some tuning decisions. macOS version does not matter.
 
2. Run the following:
sudo port deactivate active sudo port -v sync sudo port clean ffmpeg8 x264 sudo port -v patch ffmpeg8 +G4 sudo port -v -N destroot ffmpeg8 +G4(If you have ccache enabled in macports.conf, then do `sudo port install ccache` before ffmpeg, otherwise it will refuse to configure.)
This runs patch stage separately to make sure altivec patches are used (you should see 0001-0031 patch series applied).
Build fails gcc-16.1.0 does not exist.

Also I've lost all my ports (terminal included)
 
Build fails gcc-16.1.0 does not exist.

Also I've lost all my ports (terminal included)

Are you on 10.6.8? gcc16 is available pre-built, so it does not matter if it was somehow lost: installing everything from scratch is fast, the only constraint being internet connection.

gcc16 is the default compiler now, you probably want it, regardless of running any tests. (For ffmpeg it does not really matter, if there is gcc14 installed, that gonna work for the purpose too.)

P. S. Running `deactivate` does not remove any ports, they are just not available until activated back (and `install` for an already existing port simply activates it back).
 
Are you on 10.6.8? gcc16 is available pre-built, so it does not matter if it was somehow lost: installing everything from scratch is fast, the only constraint being internet connection.
Oh I see what the problem is.

When running sudo port -v -N destroot ffmpeg8 +G4 port is trying to fetch

http://macos-powerpc.org/packages/libgcc16/libgcc16-16.1.0_0+G4+stdlib_flag.darwin_10.ppc.tbz2

but such a package doesn't exist (there is a +G5 package and a package with only +stdlib flag, but no package with +G4), so it now tries to pull down sources and fails because it can't locate gcc-16.1.0.tar.xz
 
@Doq Ok, fair enough, I forgot about that gcc has G4 variant. Do this:

Code:
sudo port clean libgcc16 gcc16
sudo port -v -N install gcc16

Then proceed with the rest. MacPorts tries to match variants, but it is not forced, so as long gcc16 is already present, it won’t look for +G4.
(We don’t really care which variant of gcc16 is used, but on a G4 it makes no sense to install +G5, so regular will do.)
 
I've been kinda going back and forth between different projects, making little bits of progress wherever I'm having the most fun.

I can mostly boot GameCube games in Dolphin now, but a lot of porting work is still required:
1785779858665.png

Here's a work-in-progress port of Far Cry/Cryengine (On my G5 Quad running Leopard):
1785779809691.png

1785618112795.png


Starting to get the hang of this OS 9 porting thing. Kinda got Vice City working:
1785779588779.png

Pinball.. (and ImGui)
1785779617907.png

PvZ...
1785779633798.png

Serious Sam:
1785784090671.png

I'm also working on an update for the Half-Life port that fixes a bunch of the bugs that were found.
 
@Doq If it is doable again, will be really helpful at this point.

Need to follow exact steps to ensure we actually test what we need to be tested. On any G4 machine:

1. Make sure no local override of ffmpeg8 exists (if it does, temporarily remove it: we need to use macos-powerpc source).
Code:
% port file ffmpeg8
/opt/local/var/macports/sources/macos-powerpc.org/macos-powerpc/PPCPorts/ports/multimedia/ffmpeg8/Portfile

2. Run the following:
Code:
sudo port deactivate active
sudo port -v sync
sudo port clean ffmpeg8 x264
sudo port -v patch ffmpeg8 +G4
sudo port -v -N destroot ffmpeg8 +G4
(If you have ccache enabled in macports.conf, then do `sudo port install ccache` before ffmpeg, otherwise it will refuse to configure.)
This runs patch stage separately to make sure altivec patches are used (you should see 0001-0031 patch series applied).

Once the build completes,
Code:
cd /opt/local/var/macports/build/_opt_local_var_macports_sources_macos-powerpc.org_macos-powerpc_PPCPorts_ports_multimedia_ffmpeg8/ffmpeg8/work/ffmpeg-8.1.2
export CC=/opt/local/bin/gcc-mp-16 && sudo make tests/checkasm/checkasm
./tests/checkasm/checkasm --bench 2>&1 | tee ~/bench-ffmpeg-g4-patch0031.txt

P. S. @Forest Expertise Assuming you had no issues with ffmpeg8 build earlier, you could do this as well. I need some input from G4 to finalize some tuning decisions. macOS version does not matter.
Sorry for the late response, libarchive broke on last update for Tiger and I need to make a PR with my fix.
Hopefully I will be able to test after rebuilding four ffmpegs.
 
Took a look at that Kisak-COD project and a Linux/OpenGL port that someone else had been working on..

It was surprisingly easy to get it building this far, and because CoD 4 and Black Ops have pretty low scene complexity relative to the newer games in the series, these games should actually run pretty well on PowerPC.

Pretty cool stuff.

1785868501860.png
1785868817772.png
 
@srp How difficult would it be to port 3D Pinball Space Cadet to OSX, and what made you port the Windows version instead of just using the Maxis original?
SpaceCadetPinball is already for OS X - I ported this a while ago but haven't released it because @Matias_
was going to release his own port (not sure if it did end up released or not).

The OS 9 port is just a backport of the existing OS X codebase at https://github.com/doctashay/SpaceCadetPinball, which itself is a fork of https://github.com/k4zmu2a/SpaceCadetPinball! Only reason I worked on this project was because of the decompilation, so the Maxis original wasn't really on my radar.
 
  • Like
Reactions: AdamBuker
I didn't even know Transmission had a Qt frontend to begin with, let alone on a Mac. TIL

Did you see mpv playing video in Wayland btw?

wayland_mpv.png


All updates are in, then `mpv --vo=wlshm` should work (check `port notes owl` for how to run wayland ports).

P. S. Install `mpv-devel +wayland` for this.
 
I may be 21 years late, but I am now experiencing the G5 for the first time. Or should I say, two G5s. For reference, I have had G4 and G3s over the years but never a G5. Or a dual CPU powerpc system for that matter.

You know at this point, if I bought a used mac of this era and it didn't have someones personal info still on it with auto login on I'd be surprised. Nuked that immediately, installed tiger via the same USB I used on my mac mini G4: https://forums.macrumors.com/thread...revision-g4-mini-users-please-report.2485054/. The only command that has ever worked for me is boot ud:,\\:tbxi . Any and all variations result in the prohibit sign in my experience.

Somehow I lucked out and have an optical drive (yes I wanted one for burning discs, my Mac Pro 1,1's optical got replaced by HDDs). Then looking around I saw this...
Picture 1.png

Damn... I was trying to avoid this issue by ordering a complete, working system. Then I looked at the memory:
Picture 2.png

Fingers crossed, I swapped the RAM around (wow they were hard to get out):
Picture 5.png

OK i can work with that. 2 bad sticks can be replaced. And 2GBs on Tiger is like 32GBs today anyways... I thought 2GBs in this was weird, so makes sense.
GPU:
Picture 3.png


Picture 4.png

Still pretty happy.
 
Got mplayer 1.5 working on Tiger, works great on Tiger Server Universal on an ibook G4 1.33 Ghz.
If anyone is interested, I suspect alex-free's TigerPorts will be the easiest way to build it for Tiger users, though PowerPC ports should work too.
 
Got mplayer 1.5 working on Tiger, works great on Tiger Server Universal on an ibook G4 1.33 Ghz.
If anyone is interested, I suspect alex-free's TigerPorts will be the easiest way to build it for Tiger users, though PowerPC ports should work too.
Audio works? Also, what download do you use for tiger server universal?
 
I may be 21 years late, but I am now experiencing the G5 for the first time. Or should I say, two G5s. For reference, I have had G4 and G3s over the years but never a G5. Or a dual CPU powerpc system for that matter.

You know at this point, if I bought a used mac of this era and it didn't have someones personal info still on it with auto login on I'd be surprised. Nuked that immediately, installed tiger via the same USB I used on my mac mini G4: https://forums.macrumors.com/thread...revision-g4-mini-users-please-report.2485054/. The only command that has ever worked for me is boot ud:,\\:tbxi . Any and all variations result in the prohibit sign in my experience.

Somehow I lucked out and have an optical drive (yes I wanted one for burning discs, my Mac Pro 1,1's optical got replaced by HDDs). Then looking around I saw this...
View attachment 2651203
Damn... I was trying to avoid this issue by ordering a complete, working system. Then I looked at the memory:
View attachment 2651205
Fingers crossed, I swapped the RAM around (wow they were hard to get out):
View attachment 2651207
OK i can work with that. 2 bad sticks can be replaced. And 2GBs on Tiger is like 32GBs today anyways... I thought 2GBs in this was weird, so makes sense.
GPU:
View attachment 2651206

View attachment 2651204
Still pretty happy.
You gotta be kidding me. The RAM isn't even bad (probably). There are two 256MB sticks, and two 1GB sticks. 2GBs is showing, and performance was absolutely crawling because they didn't do matching pairs
 
You gotta be kidding me. The RAM isn't even bad (probably). There are two 256MB sticks, and two 1GB sticks. 2GBs is showing, and performance was absolutely crawling because they didn't do matching pairs
I recommend you download a service manual for your model. The ram DIMMs must be installed in pairs and in particular order for them to work properly. Also RAM specs are quite strict.

BTW. what G5 is this and how many RAM slots in your machine?
 
Booted up my G4 Powerbook 15" and upgraded the browser with PowerFox, which albeit needs some tweaking, but already seems to be working better than Tenfourfox which was getting a little old in the tooth.
 
I recommend you download a service manual for your model. The ram DIMMs must be installed in pairs and in particular order for them to work properly. Also RAM specs are quite strict.

BTW. what G5 is this and how many RAM slots in your machine?
So this is a dual 2ghz early 2005 with 4 slots: https://everymac.com/systems/apple/powermac_g5/specs/powermac_g5_2.0_dp_pci.html

So what I actually belive happened is the original owner bought it, put in 2 1GB RAM sticks (in pair) so that it was at one point at 2.5GBs. The 2 256MB RAM sticks that are showing as bad are most likely the original RAM sticks. Apparently as long as it’s a pair (2x256MB and 2x1GB) this should work, but the 256MB RAM sticks do not show up and fail system diagnostics so I thew them out after verifying the ram slots themselves are not bad by swapping around the RAM. I have 2 1GB sticks coming to get this to 4GBs.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.