#XBENCH 1.3 MAC OS X#
#XBENCH 1.3 MAC OS#
#XBENCH 1.3 INSTALL#
#XBENCH 1.3 PATCH#
#XBENCH 1.3 UPGRADE#

I hadn't booted 9 on this Mac in a while, and it simply refused to be coerced into starting up in Mac OS 9.

#XBENCH 1.3 INSTALL#

Install the processor - three screws out and in.

#XBENCH 1.3 PATCH#

Boot into Mac OS 9.2 to install the Sonnet firmware patch - power down the machine.Here's the short process for the Sonnet processor installation: Today's upgrade, turned into a 4-1/2 hour adventure.

#XBENCH 1.3 UPGRADE#

The Apple to OWC Mercury processor upgrade a couple years ago took literally 10 minutes, and yes, it's been up for most of the past few years without too many kernel panics and the like (OK PC guys, Mac's do crash, and we've been blowing smoke when we say they don't. Usually the gods are either smiling-or at least not paying attention-when I start messing with my own hardware. The G4 will move to very a very respectable server job down the road. Since I am not buying a G5 tower to tide me over until the MacPro move, I wanted (probably as much as needed) the boost that TWO processors bring to the table-and if I'm going to slap down cash for an upgrade, it made sense to get the top end product. 'No' answer: The dual processor solution has real applications in the heavy processing end of things, like video processing and the higher end applications. It's a pain when Photoshop CS2 panics the machine 5 times in a row when I'm trying to get work done. But then I also had a flaky RAM module I replaced at the same time as today's upgrade, and there were some other 'phase of the moon' issues. 'Maybe' answer: There were some stability issues that I never tracked down and I started getting the gut feeling that it might be a CPU bug. 'Yes' answer: For most of my needs, the single G4 OWC upgrade rocked. Second question: Wasn't the 1.33 Ghz OWC processor fast enough to meet your needs. In the real world this is a true measure of how a single application will cook on the processor, but it isn't being dragged down at all by the other tasks running under OS X - which also rocks on a dual CPU machine. Something that measures the base CPU ability. the XBench application, for the most part, only beats on one of the processors. Note- The dual G4 benchmark doesn't represent the true picture. I'll get into the 'gotchas' in a minute, but first let me wow you with some raw performance data. The transition from the OWC 1.33 GHz single G4 was not without a few glitches, and I had a graduation party to attend mid afternoon, so the applied time to figure this all out and work around the issues took somewhere around 4-1/2 hours. For a shade under $600 Other World Computing shipped a Sonnet Duet 1.8 GHz G4 processor upgrade to me on a Saturday Morning - 9:30AM - And I'm creating this web page at 5:00PM running on this wicked dual processor G4 tower.

This weekend (early June, 2006) I upgraded my G4 Digital Audio to it's ultimate performance level. I know there are likely few people out there that are doing these things outside of recreational use, but this is a real help for me to eke out a few more years (decades?) with these old workflows.Marc's Notes: Comments, Ramblings, Rants & Tips G4 Digital Audio CPU Benchmarks Since each Qemu-system-ppc instance, I assume, utilizes its own core/thread, this should not impact the other instances as long as the host machine is beefy enough-right?īoth of the above Mac emulation instances will mount a shared folder on the host so they can access common content. I plan to add a second instance of QEMU and run a companion image processing setup with Mac OS 9.2, Photoshop (from the old days ), and another REALbasic program that automates it. I can't tell you how happy I am to have Qemu-system-ppc as an enabler.

#XBENCH 1.3 MAC OS X#

I'm running a Mac OS X 10.4.11 installation (under Mojave) with FileMaker, Adobe InDesign, and my own legacy REALbasic program that acts as an automated 'compositing' engine taking AppleScript commands and directing graphic creation into PDF to print. Put me down for desiring multi-threading if it can speed things up, but it is such a big step to go from no emulation to any emulation that I cannot complain. Just a cheer from the peanut gallery: Thank you and all those who have contributed to QEMU to bring it to life. When emulating a guest architecture, Qemu-system-pcc currently uses the single threaded tcg, mttcg (multi-threaded tcg) does not yet work for qemu-system-ppc.

Xbench 1.3