I suggest that you grab the first download "Generic Classic Environment for Mac OS X 10.4 Tiger" because it fits most needs, but feel free to try another Mac OS 9 System Folder if you want. Download it on your Mac OS X 10.4 computer and expand the .sit archive. Then drag the resulting System Folder to the Mac's hard drive. The standard location is at the top (root) level, but you can place it anywhere. If you downloaded a Classic Environment archive that contains an "Applications (OS9)" folder (optional) then also move that folder along.
SheepShaver is an Open Source PowerPC Mac OS run-time environment. That is, it enables you to run PowerPC Classic Mac OS software on your computer, even if you are using a different operating system. However, you still need a copy of Mac OS and a PowerMac ROM image to use this program. SheepShaver is distributed under the terms of the GNU General Public License (GPL).
Download Mac Classic Environment
Mac OS 9.x, based on Mac OS 8 was the final product based on the classic MacOS architecture. Like previous version, it lacks true protected memory or pre-emptive multitasking. MacOS 9 was abandoned in favor of of the Unix-ish NextStep/Openstep based Mac OS X.
What you actually need is a way to get a Mac OS 9.2.2 System Folder on your Mac's drive. You then set System Preferences Classic pane to use that System Folder for the Classic environment, so that Mac OS X can run "classic" (Mac OS 9 and earlier) applications.
NOTE: The info below is edited from something I wrote many years ago. I assume it still works as described, since the old download link is still active. The procedure is described, as I performed then on my old Mac running Mac OS X Tiger 10.4.11.
This download contains a System Folder for Mac OS 9.2.2. The downloaded file is called NetBoot9.dmg. Mount the NetBoot9.dmg disk image. The disk image has four language folders inside. Inside the English folder, there is a file called NetBoot.pkg.
At this point, go to System Preferences Classic pane and select that System Folder for Classic. Click the Start button to run the Classic environment. After a few messages about updates, Classic startup completes, and you can run Mac OS 9 apps.
Mac Classic is the home for guides, news and tips for using early Apple computers, and Classic Mac OS systems. Mac OS 9 is still capable of many common tasks and can be an excellent distraction free environment. For some, these machines are the perfect tools to get the job done.Classic is a loosely used term for Mac OS systems that predate Mac OS X. This website is not focused on the Mac OS Classic Environment (a Mac OS 9 emulator for OSX).
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.
If you have a newer Mac that is Intel-based or is above Mac OS X 10.5, you need a digital version of the game. You can add your CD keys to your Battle.net account to download the game client. If you've lost your CD key, you'll need to purchase a new copy of the game from the Battle.net Shop.
Note: The CD key needed for the digital download will be 26 characters in length. You can register an older 13 digit StarCraft CD key or 16 digit Diablo II (2000) CD key and it will automatically upgrade to the new 26 alphanumeric CD key required to install.
Manually downloading and installing Firefox and Chrome is a workaround for this problem. It is only when they are installed by brew that there is a problem. I'm not sure what the difference is when install via brew vs installed by the downloaded .dmg
The self updating mechanism mentioned in the comments doesn't work for me. Firefox will tell me that an update is available and offer to download it, but when I click the download button, the dialog goes away and Firefox doesn't get updated.
The Classic environment is a complete implementation of Mac OS 9.x on top ofMac OS X. To Mac OS X, Classic is nothing but another application; to a user,however, Classic is a gateway to his older software programs.
When using the Classic environment, the 9.x operating system must access allhardware through the Mac OS X kernel. This means that software that accesseshardware directly will likely fail. Users of 3Dfx video cards, hardware DVDplayback, video capture cards, and even some CD writers will find that theirhardware no longer functions correctly.
On the other hand, Classic brings the benefit of Mac OS X's virtualmemory underpinnings to legacy applications. Each Mac OS 9.x application can beconfigured for a much larger memory partition than was possible previously. Tothe Classic environment, the virtual memory appears to be real memory. Programshave much more breathing room in which to function.
Working with the Classic environment is a somewhat unusual experience.Depending on the application running, there can be graphic anomalies andconfusing filesystem navigation. This chapter shows what you'll see andwhat to do when things don't seem to work right.
The Classic environment is typically launched once during a Mac OS X loginsession—either manually or automatically. After it is running, Classicremains active until you log out or manually force it to shut down.
Classic does not gain all the stability features of Mac OS X, such asprotected memory. If an application crashes in Classic, it can bring down allapplications running in Classic. The Mac OS X system will be unaffected, but youmight need to manually restart the Classic environment.
Carbon applications are a special case of Mac OS X application. They arecapable of running natively on Mac OS X, and on Mac OS 9.x through the use ofCarbonLib. If you want to use the Classic environment to launch a Carbonapplication, a setting within the General pane of the Get Info pane can force aCarbon-compliant package to launch through Classic.
If you have multiple Mac OS 9.x installations, or want to manually start orstop the Classic environment, you can do so from the Classic System Preferencespane. First, open System Preferences (path: /Applications/SystemPreferences) and then click the Classic icon.
Select a Startup Volume for Classic—Mac OS X can start the Classicenvironment by booting any available Mac OS 9.x system. It is recommended thatyou use a separate drive or partition for Mac OS 9.x, as you will be able toboot to the Mac OS 9 partition, bypassing Mac OS X in case of anemergency.
Start Classic When You Log In—If you want Classic to start upimmediately after you log in to your computer (or immediately at startup, ifyou're using Mac OS X as a single-user system), click this button. Bewarned; the Classic environment takes a few minutes to start, and your systemperformance will be degraded during this time.
Warn Before Starting Classic—Use this option to force Mac OS X toprompt you each time it launches the Classic environment. If you find yourselfaccidentally starting Classic by double-clicking legacy files, and so on, thiscan be helpful.
Put Classic to Sleep When It Is Inactive For—When Classic isrunning, it is using your system resources. The Classic environment continues touse CPU time even if you aren't running a Classic application. This isbecause Mac OS 9.x must keep up the basic system maintenance and monitoringprocesses that happen behind the scenes. If you choose to put Classic to sleep,it stops using these resources after the length of time you choose.
Rebuild Desktop—Rebuilding the Mac OS 9.x desktop can help solve"generic icon" problems (files that should have custom icons show upas generic white icons in the Finder), as well as issues with documents thatcan't find the appropriate Classic application to open them. If yourClassic environment starts to act in unusual ways, rebuilding the desktop is agood place to start.
Classic,[1] also known as the Classic environment or Classic mode, is an abstraction layer that allows most legacy applications written for Mac OS 9 and earlier to function under PowerPC versions of Mac OS X.[2] It was supported from early versions of Mac OS X Public Beta through Mac OS X 10.4.11 as a vital part of the transition from classic Mac OS to OS X.
Mac OS X is based on NeXTSTEP, which uses a Unix-based kernel that is inherently incompatible with classic Mac applications. During its early development under the code name Rhapsody, a proof-of-concept called "Blue box" demonstrated that backward compatibility could be provided through a native application that would run the older software in a sandbox environment. Any problematic legacy program that would normally cause Mac OS 9 to crash could be contained and only require relaunching of the Classic environment without bringing down the main system.
During beta testing of Mac OS X, the minimum version of classic Mac OS to be supported was 9.0.4, which needed to be installed separately. Stability was inconsistent and improved with successive public beta releases. Another transition technology called Carbon was also introduced, which allowed applications which took advantage of the API to run on both Mac OS 9 and PowerPC versions of Mac OS X.[3][4] 2ff7e9595c
Comments