Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

JWSandi

macrumors regular
Original poster
Jul 19, 2008
120
0
Trashville, TN.
I'm running the most updated version of Snow Leopard on my iMac.

I've recently purchased some add on planes for x-plane they were delivered in an installer with a .app extension.

When I double click on them the icon does the usual animation to show it has responded to you clicking on it, but then nothing.

It will not install or do anything at all, just sits there.

I've tried restarting.

I've been working with the vender and they are stumped so they just sent me a zip file of the plane for me to manually install, which I've done.

But anyway.

My question to all here is...

Has anyone ever experiences similar problems, is it some type of setting I might have changed thats prohibiting these from running??

Do I need to do something special to get them to run?

When I download stuff that uses the .dmg extension I have no troubles installing them.

Everything else runs fine

Email, Safari, Widgets... everything.

This is the first issue I've had with my iMac or OSX.

Any help is most welcomed!

Thanks in advance
 

wrldwzrd89

macrumors G5
Jun 6, 2003
12,110
77
Solon, OH
Odds are it's an issue with the way the .app bundle was delivered to you - which caused the executable permission to not be set on the actual executable within the .app bundle. Known "safe" Mac OS X packaging methods include, but are not limited to:
  1. Disk image
  2. ZIP archive
  3. TAR archive, compressed with GZIP, BZIP2, or any other method

Was the file you received from the vendor in one of these known good formats?
 

q64ceo

macrumors 6502a
Aug 13, 2010
518
785
Open up terminal.

Type in Open

Drag the .app to the terminal window and press enter.

If there is an issue or an error, it should show up in the terminal window.
 

JWSandi

macrumors regular
Original poster
Jul 19, 2008
120
0
Trashville, TN.
Odds are it's an issue with the way the .app bundle was delivered to you - which caused the executable permission to not be set on the actual executable within the .app bundle. Known "safe" Mac OS X packaging methods include, but are not limited to:
  1. Disk image
  2. ZIP archive
  3. TAR archive, compressed with GZIP, BZIP2, or any other method

Was the file you received from the vendor in one of these known good formats?



It was delivered via a zipped filed, which unzipped fine.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.