Member Avatar for humbug
humbug 5 Junior Poster in Training

Having hardly used macs in my life, I am now borrowing an old iMac 3G (OS 10.2.8 I think) to temporarily host some php files. I have downloaded the latest version of MAMP to get the job done and done the whole unzipping/moving to apps folder thing. My problem comes when I try to open the "Mamp" (Application) file, the MAMP logo jumps up and down in the doc then goes away, no error message, nuthin'.

Oh yeah, and the log file (of sorts) in the Utilities folder (system log, not MAMP log) said something about not finding a directory in "/usr/..." I can't remember exactly what it was, I'll check tomorrow.

Any pointers as to how to get the MAMP server running is greatly appreciated.

Cheers

  • 1 Contributor
  • 0 Replies
  • 110 Views

Dani AI

Generated

For 's Jaguar-era machine: a modern MAMP bundle can fail silently on OS X 10.2.x because of binary/OS incompatibility, missing expected system paths under /usr, or simple permission problems. The next steps are to capture the exact error output (system/launch logs or stdout from the app) and then act on that specific message.

First, gather diagnostics you can read locally:

  • Open the system console (Applications/Utilities/Console.app) and look for crash entries and any lines mentioning MAMP or the missing /usr/... path.
  • Check MAMP's own log folder if present (for example /Applications/MAMP/logs/) and any Apache/PHP error logs there.
  • Launch the MAMP executable from Terminal to see immediate errors (adjust the path if your bundle is different):
/Applications/MAMP/MAMP.app/Contents/MacOS/MAMP

If Terminal prints a “No such file or directory” for a path under /usr, note that exact path. If it’s just a missing directory that should be present, creating it and setting correct ownership can help; if a binary is missing, you’ll need a compatible build or to install the missing component.

Quick permission fixes (use carefully):

sudo chown -R $(whoami) /Applications/MAMP
sudo chmod -R u+rx /Applications/MAMP

If compatibility looks to be the issue (modern MAMP vs. Jaguar), either install a MAMP build that supports that OS or use the machine’s bundled Apache/PHP instead. MAMP’s download page lists supported versions: MAMP downloads. For compiling/installing server components on older macs, consider MacPorts as an alternative: MacPorts.

Collecting the exact console/crash lines is the key—those lines point to whether this is a permissions issue, a missing file, or an outright incompatibility.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.