Understanding Mac OS 9.2, the Classic Environment, and Classic Applications

As you have learned throughout this book, Mac OS X is an entirely new operating system. As such, applications created for previous versions of the Mac OS won't work under Mac OS X well, not directly anyway. Rather than forcing you either to immediately obtain a Mac OS X compatible version of all the applications you use (which might or might not be available) or to go without, Apple includes the Classic environment in Mac OS X. As you learned in Chapter 1, "Mac OS X: Foundations," and Chapter 6, "Installing and Using Mac OS X Applications," the Classic environment enables you to run Classic versions of applications.

NOTE

A Classic application is one that was created for Mac OS 9.2 or earlier versions of the Mac OS.

The Classic environment is provided solely to ease your transition to Mac OS X because it takes time for new versions of applications to be created for a new version of the Mac OS (especially one as different as Mac OS X is from previous versions). Developers often wait for the new release of the Mac OS to stabilize before completing the development of new versions of their applications. And they also often wait until a significant proportion of Mac users are using the new version of the OS so that there will be a substantial market for their products when they release them.

After you have obtained Mac OS X versions of all the applications you use, there will no longer be any reason to use the Classic versions and thus, the Classic environment. Classic is really a bridge between the past (previous versions of the Mac OS) and the present and future (Mac OS X).

The Classic environment is actually a Mac OS X application that emulates Mac OS 9.2; you run Classic applications from within this emulated environment. The configuration of the Classic environment is the configuration of the Mac OS 9.2 installation you choose to use. The Classic environment provides all the system resources of Mac OS 9.2, such as extensions and control panels, and you can customize the Classic environment just as you can Mac OS 9.2 itself.

Although you will use the Classic environment to run Classic applications most of the time, you will probably also run into situations in which you want to run Mac OS 9.2 directly (for example, to use applications that access a hardware device that doesn't work under Mac OS X).

Classic, a Bridge to the Past

The Classic environment is analogous to the transition from 68K processors to the PowerPC processor. Applications written for the 68K processor could not run on PowerPC machines and vice versa. For a period of time, most applications were provided in fat versions, which meant the application came in both a 68K and a PowerPC version. You could use the application installer to choose which version was installed (sometimes both were installed or only the one appropriate for the processor that you were using). After a period of time, the 68K versions of applications were dropped because most people who were purchasing new software were also using a PowerPC machine.

You can expect a similar transition for Classic applications as Mac OS X versions are released. For a time, both versions will be available, but as more Mac users make the switch to Mac OS X, the development and distribution of applications that are compatible with Mac OS 9 or earlier versions of the OS will cease.

The Classic environment mostly does its job well and will enable you to use the versions of applications that you already have. However, it does have some limitations, which are the following:

• No memory protection Because the Classic environment is an emulation of Mac OS 9.2, Classic applications do not have protected memory. When one Classic application has a problem, it can (and usually does) affect other Classic applications you are running. In this respect, running applications under the Classic environment is just like running them under Mac OS 9.2 or earlier. When a Classic application crashes, it can take down the rest of the open Classic applications as well as the Classic environment itself.

  NOTE

  The Classic application itself is a Mac OS X application and does benefit from Mac OS X's protected memory architecture. If the Classic environment crashes, it won't affect Carbonized or Cocoa applications that are running.

  
  

• Emulated performance When you run a Classic application, you are using three "layers" of software, which are Mac OS X, the Classic environment, and the Classic application. Because of this, the performance of a Classic application can be considerably slower than when running it under Mac OS 9.2. This speed differential is most noticeable on slower Mac hardware and while using processor-intensive applications (such as advanced graphics or video applications).

• Spotty hardware support Because they run in an emulated environment, Classic applications can sometimes have trouble accessing hardware with which they are supposed to work. When you are unable to access a hardware device through the Classic environment, your only option is to restart under the Mac OS 9.2.

NOTE

All user accounts on your Mac share the same Classic environment. However, each user account can access the Classic pane of the System Preferences utility and so can change the Classic environment to suit their purposes. (The Classic pane does not require Administrator authentication.)

Some good news is that the Classic environment opens much more quickly under Mac OS X version 10.2 than it did under previous versions. Whereas opening Classic under those versions was painfully slow, launching Classic under version 10.2 is quite quick. The stability and controls for Classic have also been improved.