PDA

View Full Version : PowerPC Screensaver on an Intel Mac?



SubaruNation555
Jan 11, 2008, 12:40 PM
This may sound like a silly and trivial problem but I have a screensaver (.saver file) that is PowerPC and will not work on my Intel-based Mac. Is there anything I should try before I move on? Thanks.


Makosuke
Jan 11, 2008, 02:10 PM
I'd noticed the same thing, and I'm fairly certain that you'd need to run the screensaver subsystem in Rosetta to get this to work. Which is probably possible, but there's no easy way to do it.

I just gave up on the old ones, personally.
richard.mac
Jan 11, 2008, 06:58 PM
is there a "run in rosetta" option in the get info window for the power pc screensaver in ~/Library/Screen Savers?
SubaruNation555
Jan 12, 2008, 01:40 AM
is there a "run in rosetta" option in the get info window for the power pc screensaver in ~/Library/Screen Savers?

Nope, no such option that I can see.
richard.mac
Jan 12, 2008, 02:08 AM
i guess its time to beg Jeremy Clarkson for a universal binary :p
robbieduncan
Jan 12, 2008, 02:58 AM
Screen savers (.saver bundles) are not executable which is why there is no "Run in Rosetta" option. They are loadable bundles (basically plugins) which get loaded into the screen saver engine. To get one PPC screen saver to run you'd have to run the entire screen saver engine in Rosetta including any other screen savers until you change it back.

Unfortunately I don't think this is possible.
SubaruNation555
Jan 12, 2008, 08:30 AM
i guess its time to beg Jeremy Clarkson for a universal binary :p

Haha, something tells me he can't be bothered. Thanks for the replies guys, I figured it wasn't going to fly.
Makosuke
Jan 12, 2008, 05:06 PM
Unfortunately I don't think this is possible.I was thinking maybe that the screen saver engine is an easily accessible application (like, say, Finder or Disk Mounter), in which case you'd be able to Rosetta it, but on a cursory search, I didn't see it with the rest of such system bits.
robbieduncan
Jan 12, 2008, 05:44 PM
I think it's a private framework or something similar that runs under a fairly low level (and important) process. If you preview a screen saver in System Preferences no new executable gets launched and all the CPU used by the saver gets assigned to System Preferences.