aperture 1.5.3 hack

Update 22apr07: Hex offsets for MDD dual 867MHz now available

Ok, things haven’t changed much for machines close to the minimum spec since 1.5.2, so for my 1GHz 12″ PowerBook all I need to edit is the Info.plist file inside the Aperture.app/Contents directory. I changed both the minimum RAM and minimum CPU requirements down to 500MB and 1GHz:




Edit those entries with either a text editor, or the plist editor that comes with the (free) Developer Tools. Note that I don’t have any hex offsets for video card check bypass, as I no longer have a machine that triggers those checks and therefore have no way of testing any values I may find.

I’ve now found an offset for a G4 MDD dual 867 MHz machine, but do bear in mind that this system has 2GB of RAM and a supported graphics card, so I have not applied the graphics edits kindly provided in the comments. The only change I needed to make after applying the Software Update to 1.5.3 was:

0xb5e8: 40 9E 00 88 -> 48 00 00 80

← Previous Post

Next Post →


  1. rock monkey

    I got mine to bypass the video card requirements by editing address B684. Same data change
    0xB684: 40 9E 00 88 -> 48 00 00 80

    I got an 667Mhz 1GB RAM Powerbook

  2. what about G4 Desktops? I’ve got a dual 1.42 MDD 2GB RAM and Radeon 9800 Pro 128MB

    I meet requirements easily but Apple locks us out i’ve hexed 1.5.2, but what about 1.5.3? Someone help.

  3. If you keep you 1.5.2 hacked binary, you can update aperture in software update, then copy in the 1.5.2 binary, and keep a backup of the 1.5.3 version untill someone figures out the hack for 1.5.3.

    (Dual 1.42Ghz G4 MDD 2GB RAM, ATi Radeon 9800 Pro 128MB)

  4. ThunDer

    HELP I also need a new HEX edit for 1.5.3 — don’t meet min hardware with a G4 1.25 PPC MDD

    This sucks!

    Can anyone help?

  5. Ciubecca

    Could you please describe the process how to get the offset for those who still have a machine that triggers the video card checks? I have the Developer Tools installed and thought that the Sampler application would be a good start but launching and recording Aperture from there shows no data.

  6. longroper

    I used the HEX edit given and still had a problem with the video card. So I also replaced the HEX code below also. Then it worked.

    0xb684: 40 9E 00 88 -> 48 00 00 80

  7. mr_josh

    Just thought I’d chime in: v1.5.3 works great on my MDD G4 dual 867 with the hex provided in the April 22nd update to this post. FWIW my machine has 2GB of RAM and a modded GeForce FX 5200 from a G5, so the RAM and video card pass the checks, it’s just the processor that fails without the hex.

    For those with video card issues, it looks like longroper has the key in his post.

  8. Brian Stanfill

    Running OSx86 v10.4.8 on an Intel P4 2.8 GHz with 1024MB ram and an NVIDIA FX 5600 Ultra and cannot get past the GPU minimum reqs test for Aperture 1.5.2 or 1.5.3 with any of the hex edits.

    I see a lot of threads that provide these very same hacked offset values, but no thread explains what the hacked values actually do. Do the hacked offsets (1) cause Aperture to not check GPU requirements or (2) cause Aperture to accept a less advanced graphics card (say an 8 instead of a 10, but still fails in the case of a 7 for example)?

    If (2) is the case, then it may be possible that different offset values are needed for even less advanced graphics cards like mine.

    Has anyone else ran into trouble running Aperture in a homebuilt OSx86 development environment?


    Brian Stanfill
    Palmer, Alaska

  9. I’m trying to run the Aperture 1.5.3 trial on a 933MHz Quicksilver with 2GB RAM and a Radeon 9800 Pro. It won’t install, of course, so I googled and came up with the series of Aperture hack pages here. I mounted the .dmg file and looked at the package contents, but I can’t find any file called simply Aperture or Aperture.app. Where have I gone wrong?

  10. Hi Richard,

    I haven’t downloaded the trial in a while, but in the comments for 1.5.2 hack and I’ve gone over how to get ‘inside’ the installer to find the right Aperture file to change, and it’s something like:

    …you need to right click (or ctrl+click) on the trial package and choose ‘Show Package Contents’ (or similar: not sure of the exact wording), then go inside the Contents directory, and look for another set of packages.

    Install each of the ones that isn’t Aperture, then unpack the Aperture installer, patch those files, and then run the new Application. Unpacking the installer is easy enough from the command line if you’re familiar with gzip and pax, but I haven’t tried it at all from the Finder. Some people say nice things about Pacifist, but I’ve not used it so I don’t know what exactly it can do to packages.

    Apologies for the vagueness of some names, but I don’t have the trial version, and have only talked someone through this over the phone, so didn’t see the exact steps.


  11. I am a legit user of Aperture, who has it installed on two machines: a Powerbook G4 and my Powermac G4. I have upgraded the Powermac G4 with a high end Raedon card, 1.5 GB memory, and a 1.6 Ghz Processor…so all the requirements are met, but I have to used a cracked version to run it on that machine. While the performance is slow, it’s acceptable until I can afford to upgrade the computer.

    Meanwhile….The cracked version I’m running is 1.5.1. I haven’t been able to get a later version to work for me yet. And my install disks are the original version 1.0 that I simply run updates for, so I don’t have a later installer.

    I’d like to know if any of you can be of assistance in patching the newer version to run on my Powermac (preferably 1.5.4 that just came out.)

    Thanks in advance for your help!:grin: