4

I created a .app file that is 303KB on disk. When I right click it and press Compress... I end up getting a 8.4MB .zip archive.

I tried sending the .app via email to myself and compressing it on Windows, and was able to get a .rar file of 177 bytes. However, attempting to open the .app on OSX results in the message:

You cannot open the application...the Classic Environment is no longer supported`

What does this error mean?

Improve this question
4
  • Did you send the zip to Windows?
    – mmmmmm
    Commented Aug 16, 2014 at 19:00
  • Why was your rar 177 bytes? Are there any files that were lost during compression?
    – interestinglythere
    Commented Aug 18, 2014 at 18:57
  • The error was the compression from 8.4MB to 177 bytes. I'm guessing that your default for opening .rar files is a Classic app. There are more modern .rar decoders, you could try one of those. But don't expect it to restore that 177-byte file to the original 8.4MB file.
    – GEdgar
    Commented Feb 25, 2015 at 23:26
  • "I'm guessing that your default for opening .rar files is a Classic app." Probably not the case. OP said the dialog came up when they were trying to open the unrar'd .app, not when they were opening the rar archive. I agree though that the root cause is probably with making the rar – there were probably some Mac OS-y parts that got excluded from the archive.
    – interestinglythere
    Commented Feb 17, 2016 at 15:49

3 Answers 3

Reset to default
3

The Classic Environment is Apple's software that supports running Mac OS 9 apps on Mac OS X. ("Mac OS Classic" refers to Mac OS versions before Mac OS X.) Both Mac OS 9 and Classic are really old: Mac OS 9 was discontinued in 2001, and the last version of OS X to support Classic is 10.4 (Tiger), which was released in 2005.

What's the difference between Classic and OS X apps? Their code is completely different, as different as the difference between Windows and Mac apps. This is because Classic and OS X are very different architecturally.

Why did Mac OS X think your app was a Classic app? Most likely:

  • On UNIX systems, which includes Linux and Mac OS, launchable program files (executables) must have a executable property set to true.
  • Windows and Mac OS Classic are not UNIX and their filesystems don't have the concept of a executable property.
  • Most Mac OS apps are folders that appear as files in Mac OS. You know this if you've looked at the app in Windows. The executable part of the app is one of the files in TheApp.app/Contents/MacOS.
  • When you moved the file to Windows, the executable file property was lost, so when you moved it back to your Mac, the executable property became set to false.*
  • When you opened the app, Mac OS tried to launch the app, noticed that the app wasn't marked as executable, and figured it must be a Classic app.

* Usually files that come from non-UNIX systems will have the executable property set to true by default, e.g., if you move files using a flash drive or if you use zip instead of rar. The program you use to unrar files on your Mac would be the one to blame.

Why was your rar 177 bytes? Perhaps because there were entire files that were unsupported and so didn't get rar'd.

Improve this answer
2
  • It would have been better to ask the last line as a comment first as I suspect your answer will be irrelevant (but useful somewhere else)
    – mmmmmm
    Commented Aug 16, 2014 at 20:16
  • True; added as comment. I believe my explanation of what Classic is and why non-Classic apps appear as Classic would still be valid though.
    – interestinglythere
    Commented Aug 18, 2014 at 18:58
2

Just like PowerPC applications, Mac is no longer able to support the Classic Environment and will not ever support it. Keep in mind that the code is different from the Classic and OS X.

Improve this answer
1

The error means that the app that you are attempting to open is attempting to launch the Classic environment. Classic was removed from OS X a while ago and this error is informing you that newer versions of OS X won't be able to open these apps.

Compressing an OS X app in Windows is known to cause this problem; see:

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .