aperture 1.5.1 hack

hmm, it ain’t working for me, i’m on a mac mini (Radeon 9200) and it says my graphics card ain’t supported.
at which offsets do i have to change something? the previous offsets aren’t correct anymore, although, i found similar HEX’s at: 173AC and B550… but didn’t work 🙁 😕

Could be – that’s the same video card I have in my 1GHz model, although the tech specs say the NVIDIA GeForce 5200 Ultra is ok so maybe they just match on the model number and don;t worry about the variant/VRAM any more ? I certainly haven’t seen the resolution be a problem, and as 1.25GHz is the new minimum you’ve unofficially scraped in ! Certainly helpful if there are any more updates 🙂

I’ve not seen those problems (not done much editing yet) but I did see an oddity whilst importing 97 images: the previews were only generated for 60 of them and then it refused to do any more. The album name also stayed greyed out in the Library list although it was selectable I couldn’t double-click on it to edit it, and when I quit Aperture it didn’t try to do the usual update for the iLife suite. Restarting made the album name turn black like the rest, and choosing Update previews for the album picked up where it had left off doing the final 37 (which were from the middle if the set, oddly).

Time for more testing: I’ll let you know if I see that shadow thing (not checked the Apple forums yet though).

TTFN,

Ian,

I really appreciate you keeping up on the hex edit. I have a dual 1.42 ghz G4 with 2gb of ram and was quite disappointed with the hardware requirements. But then Ian came to the rescue. Thanks again, especially with the 1.5.1.

Hi, I want to start using Aperture and I feel that my laptop should meet the requirements, yet it falls just short (1GHz). It’s an Aluminum PowerBook G4 1GHz with the Radeon 9600 Pro and 1GB of RAM. The –only– thing I can see it is catching me on is the processor speed. I opened the Aperture.app like you described, but the original data you show for each offset doesn’t seem to match what’s in the file. I made the modifications anyway and it just causes the app to crash (instead of displaying the sorry your hardware isn’t good enough box). Is the code different? I am evaluating the software before I spend the money buying the retail, so I downloaded the demo from Apple. I would appreciate any help anyone can offer.

I’ve been trying to get some variant of this to work on my 1ghz PB 17″ with 1g ram. After updating to 1.5.1 from a working 1.0 installation, I edited the above 3 binaries (which match exactly as listed above), but I’m still getting the “hardware not supported” screen. I don’t have Core Image graphics (my machine was the last one made which didn’t support it). I wonder if I need an additional binary patch which disables a search for Core Image? BTW, the only thing the lack of Core Image does, is prevent the use of the full screen mode.

Hello there,

I upgraded my version 1.5 to 1.5.1 and totally blew it (I lost the original Aperture.app). Is there someone who can help me by sending me the original 1.5.1 Aperture.app file so I can edit the Hex code again?

BTW, I’m running Aperture on my old ibook G4 800Mhz with 640 Meg without a hitch (yes it’s slower but it’s perfect to have a look at the application).

Thanks,

Thanks, worked perfectly here.

How do you find performance with Aperture 1.5 on a PowerBook G4 12″? Mine has 768mb RAM and 1.5GHz G4 and I was thinking of using it with large JPEGs – any thoughts?

Hi:

I have a Dual 1.42 PowerPC G4 with 2gb memory, ATI Radeon 9000 Pro and Tiger 10.4.8. I tried the hack using the )xED but when I entered the hex addesses the numbers that showed up are not the same. I changed it anyway, but Aperture 1.5 Crashed. How can I make it run on my G4.

HELP!!!

On my intel Mac, tho compatibility checker said OK, the trial would not install.

So here’s what I did:

– Use PAcifist and extact the .mpkg file (of trial) and move files to appropriate places.
– Download the “ProKit for Intel” availabe as a torrent file.
– Replace system/library/PrivateFrameworks/ProKit.framework with the download. This was required to get aperture to work inspite of hex edits.
– Use 0xed to find the first three HEX occurrences of 40 9e 00 88 (while searching don’t use gaps) and replace with 48 00 00 88.
-Launch Aperture. I did the first three hex replacements, but you may want ot try only hte first TWO to see if that works, since I now feel I should have done that instead of three. ANyways, it has not crashed!!

I’m sorry to say that I can’t help either of the problems with the video card detection, as I don’t have those particular models to test things on. Do the values that Gary mentions on David Djsiska’s blog help at all ?

0xB8E8 40 9E 00 88 => 48 00 00 88

0xB984 40 9E 00 88 => 48 00 00 88

0xFAF8 40 9E 00 D8 => 48 00 00 D8

Note that I have not tried these edits myself.

HTH,

Steve – I’m not aware there are any different values for G4 towers: if the values above don’t work for you then do check your version number, as 1.5.2 is the latest version of Aperture and that has different values.

From what I’ve seen though the 9600 is a fully supported card, and in 1.5.2 (at least, maybe others in the 1.5 series) the Info.plist simply demands a single 1.2GHz CPU and 1GB of memory, both tests you ought to pass with ease. You can grab the 1.5.2 version directly from Apple’s Aperture web site if you have an Apple ID (free from the Developer Connection, iTunes purchases or Apple Store purchases) and the serial number. I would be surprised if simply running the 1.5.2 installer didn’t just work for you.

HTH,

As #19 suggested I installed trial version 1.52 on my eMac( 1.25Ghz/1Gb ram) with Pacifist. I swaped the first three instances of 40 9e 00 88 and replaced with 48 00 00 88. I did not download and install Prokit ( it appears to be included with this trial version.) On launch it prompted me for the SN and then opened. Seems to be working fine although it’s a little on the slow side.

Serial from here, or if you may be able to get one here if you qualify.

HTH

I can assure you that should anyone actually try to post information here that would allow piracy of (any) software, you’d never get to see that comment.

If you can’t Google for it then a) I’m very surprised, and b) I’d strongly advise against posting such requests all over the web, as it does leave a trail in search engine archives advertising to the world that you want to steal software: will any future employer(s) do a web search on your name ?

Just something worth thinking about, as is this post from the 28th of January 2007 on a web forum:

“If you happen to be using Aperture with a warez serial, be careful. For some reason, Apple Legal is targeting this app and hammering people who they find registering with a pirated serial number.

I’ve been getting nasty calls for 2 days now. I’ll have to erase my HD and throw it in the oven, then bury the ashes.”