When you purchase an app from the Mac App Store, it normally downloads and installs exactly as expected. But not always.
An easy way to run 'classic' Mac OS applications under Windows. Under Windows, software written for the 'classic' Mac OS (i.e. Versions 6 through 9) can only be run through software that emulates Macintosh hardware from 1980s and 1990s. The most advanced of these emulator programs is SheepShaver. Podcast 324: Talking apps, APIs, and open source with developers from Slack. Featured on Meta Stack Overflow for Teams is now free for up to 50 users, forever. Planned maintenance scheduled for Saturday, March 27, 2021 at 1:00 UTC Linked. How to reset the built-in Dictionary app for Look Up function?
One error that has cropped up for numerous users over the past year states: 'The product distribution file could not be verified. It may be damaged or was not signed.' When this error appears, the download of the purchased app fails.
The symptom seems more likely to occur if you are running Snow Leopard (OS X 10.6.x) than Lion (OS X 10.7.x), but it has been reported with both OS versions. A potential solution is to delete the App Store app itself from the Applications folder and reinstall the app. To do the reinstall for Snow Leopard, download and run a combo update (such as Mac OS X 10.6.8 Update Combo). An Apple Support Communities thread offers more details. If you're running Lion, another thread confirms that reinstalling OS X via Lion Recovery should similarly work. I assume running the OS X Update 10.7.2 Client Combo would also succeed.
For those willing to take a more 'techie' route to a solution, you can avoid a time-consuming reinstall. Instead, use the Console utility to identify the folder, located in the /var/folders directory, that is 'failing.' A problem with the folder appears to precipitate the App Store symptom. The 'corrupt' folder may vary (with names such as 3p or q1) but will be cited in the Console log. Once you've targeted the folder, delete it; the symptom should now be gone. A new folder will be created as needed. This works whether you're running Snow Leopard or Lion.
TUAW recently covered another Mac App Store download error. This one states: 'We could not complete your App Store request. An unknown error occurred (100).' In this case, the cause is apparently linked to a disconnect between the App Store app and the latest iTunes Terms and Conditions. You need to agree to these terms before a download can occur. The precise fix varies. It can be as simple as quitting and restarting the App Store and/or iTunes apps. You may also have to restart your Mac. If any of these restarts work, the Terms and Conditions window should appear prior to the next download attempt. After agreeing to the terms, all should be well. Otherwise, try downloading an iOS app from iTunes; this should bring up the Terms and Conditions. Agreeing to them should fix the problem for both the iTunes Store and Mac App Store.
Mac OS 9 for Windows
Run classic Mac OS apps in Windows | A similar app that runs System 7 | How to use MacOS9 | What the MacOS9 app contains | Acknowledgments | Support
An easy way to run 'classic' Mac OS applications under Windows
Under Windows, software written for the 'classic' Mac OS (i.e. versions 6 through 9) can only be run through software that emulates Macintosh hardware from 1980s and 1990s. The most advanced of these emulator programs is SheepShaver. SheepShaver is no longer supported by its original author, Gwenolé Beauchesne, but minor updates are available from an active support forum at E-Maculation.
This page provides a fully functional SheepShaver system that runs Mac OS 9.0.4 (US English version). Unlike other SheepShaver-based systems, it makes it relatively easy to exchange files between SheepShaver and Windows, and makes it easy to print from Mac OS applications to Windows printers, or to create PDF files on the Windows desktop. The system runs under Windows 7, 8.x and 10; it may work under earlier Windows versions, but I haven't tested it under earlier versions.
To install this system, download and run the MacOS9AppInstaller. (The file is around 400MB in size; it contains a 4GB hard disk image file.) Then launch the MacOS9.exe application, either from its folder or from the desktop shortcut that the installer offers to create.
Note: Updated 10 February 2021 with a new version of SheepShaver.
The program comes with an uninstaller. Every file installed or used by the program is inside the program's folder. After uninstalling, any files that may be left over will be in that same folder; those files and the folder itself may be safely deleted.
For a similar system that runs Mac OS 9 under OS X/macOS, see another page.
A similar system that runs System 7.6.1 in BasiliskII
I have created a similar system that runs Mac System 7.6.1 under BasiliskII. You may download its MacSys761Installer here. Run the installer and then launch the MacSys761.exe application, either from its folder or from a desktop shortcut that the installer offers to create.
The System 7 app works mostly in the same way that the MacOS9App works. You may copy files to System 7 desktop by dropping them on to the MacSys761.exe icon. And you may copy files to the Windows desktop by selecting them with the Copy to Host application or dropping them in to Send to Windows folder (both on the System 7 desktop).
Note: Updated 23 January 2021 with QuickTime Player added to the system.
How to use the MacOS9 app
I assume that you know something about Mac OS and don't need any advice from me. A few points are worth mentioning:
Depending on your Windows version, a Computer or This PC icon appears on the MacOS9 desktop. This icon leads to the drives on your host computer.
The File Transfer folder on the desktop is a convenience, to remind you that files found in the Computer or This PC folder should be copied into that folder (or any other folder in the MacOS9 disk image) before being used. They should not be copied merely to the desktop, because they almost certainly won't work until they are actually copied into the MacOS9 virtual disk. (When you copy a file from Windows to the MacOS9 desktop, the file itself is not copied to MacOS9 disk image; that is why you must copy it to a folder inside the disk image itself.)
The MacOS9 system includes a startup script named MacOS9StartUp. This script creates the necessary file-transfer folders for printing and exchanging files, and tests whether they are correct if they already exist. Please let it run without interference.
If you are confident that the file-transfer folders are working correctly, you can move the MacOS9StartUp script from the Startup Items folder in the System Folder to the Startup Items (Disabled) folder. Then move BackgroundScript from the Scripts folder in the System Folder to the Startup Items folder; shut down the MacOS9 app and start it again. If the file-transfer folders stop working, move the BackgroundScript out of the Startup Items folder and restore the MacOS9StartUp script to the Startup Items folder.
To transfer a file from Windows to MacOS9, drop it (in Windows) on MacOS9.exe or on the MacOS9 desktop shortcut. After a long pause, perhaps even longer than 30 seconds, a copy of the file should appear on the desktop of the MacOS9 disk. The original file remains in your Windows system.
To transfer a file to Windows from MacOS9, drop it on the 'Send to Windows' applet on the MacOS9 desktop. The file should be copied almost immediately to the Windows desktop. Or you may double-click on the 'Sent to Windows' applet and select a file to send to the Windows desktop.
To print from MacOS9 to your default Windows printer, simply use the File/Print menu in your MacOS9 application, and print with the default desktop printer, 'Print to Windows.' After a pause, the document should print to your default Windows printer.
To print from MacOS9 and select a Windows printer for the current print job, use the File/Print menu in your MacOS9 application, choose the desktop printer named 'Select Windows Printer', and print. After a pause, a popup list of Windows printers should appear; choose the one you want.
To create a PDF file in Windows when printing from MacOS9, use the File/Print menu in your MacOS9 application, choose the desktop printer named 'PDF to Windows Desktop', and print. The resulting PDF file on the Windows desktop will have an arbitrary name based on the current date and time.
To create a PDF file on the OS 9 desktop, use the File/Print menu in your MacOS9 application, choose the desktop printer named 'PDF to OS9 Desktop', and print. You will be prompted to enter a filename for the resulting PDF; an arbitrary filename will be offered based on the current date and time, but you can type over it to change it.
To print 'raw' PostScript data from MacOS9 to a PostScript-compatible Windows default printer, follow the printing instructions above, but choose the desktop printer named 'Raw PS to Win PS Printer.' The raw PostScript data will be sent to your Windows default printer; if that printer is not PostScript-compatible, you may waste a lot of paper, so be careful with this option.
If SheepShaver locks up: While the MacOS9 app is running, a small Mac-like icon appears in your Windows system tray. You may click on this to open a menu that includes 'Force Quit.' You may click on this to shut down SheepShaver forcibly; you will be asked to confirm that you intend to do this. (SheepShaver is notably unstable, and liable to crash without warning, so this feature may be useful.)
You may use the supplied SheepShaverGUI app (in the Programs folder inside the MacOS9 folder) to modify the system, but the file transfer and printing features will only work if you launch the MacOS9 app from the MacOS9 desktop icon or the MacOS9.exe program inside the MacOS9 folder! If you launch SheepShaver from the SheepShaverGUI, you may get error messages about the file transfer system; if this occurs, shut down SheepShaver and relaunch the MacOS9 icon or MacOS9.exe program.
Troubleshooting: If the SheepShaverGUI app produces an error message when you first run it, double-click on GTKLocalInstaller.exe in the same folder. You will not see any feeback from the GTKLocalInstaller.exe program, but the SheepShaverGUI should now run. (Or you may need to logout and login again.)
To transfer files from a real Mac to SheepShaver, follow the instructions in this post on emaculation.com.
To add additional disk space to MacOS9: This system includes a 4GB disk image. If you need additional disk space, then visit this page at Macintosh Garden and download one of the provided disk images (I recommend the third download, with a 10GB disk image). Then follow these steps:
Weredude Mac Os 11
- Use something like the 7z file manager app to extract the downloaded disk image.
- Rename the extracted disk image to something like Second.dsk (for convenience, use the .dsk extension, whatever the original extension might be).
- Move the renamed disk image into the MacOS9Programs folder.
- Use Notepad or any text editor to edit the SheepShaver_prefs file in the same folder and add this line after the first line: disk Second.dsk (using whatever name you gave the to the disk image file).
- Save the SheepShaver_prefs file and restart MacOS9.
'Cannot map second Kernel Data' error: If, on your system, SheepShaver starts up with the error message 'Cannot map second Kernel Data area: 487', then go to the Programs folder inside the MacOS9 folder, rename SheepShaver.exe to SheepShaver-old.exe and rename SheepShaver-noJIT.exe to SheepShaver.exe. This alternate version will probably be slower, but should at least run. (This error message occurs unpredictably on some systems but not on others.)
Weredude Mac Os X
Further details may be available later if you ask for them.
What the MacOS9 app contains
The MacOS9 application contains a standard US-English Mac OS 9 installation, without features that can't be used in this system, such as file-sharing. It also includes a large number of standard Mac OS applications, plus some Control Panels, Extensions, Scripting Additions, and a gray desktop image that you can easily change if you prefer. Cradle of rome mac os.
The file transfer system uses two AppleScripts: either the MacOS9StartUp script or the BackgroundScript script described above. The MacOS9AppData folder uses an OS9Action folder action script found in the Scripts:Folder Action Scripts folder.
In the MacOS9 disk image, the Transfer folder alias and From Windows folder are required by the file-transfer system, as are the MacOS9AppData folder and the WinPath.txt file found in the System Folder.
The Transfer folder is an alias of the Windows folder named Transfer (inside the MacOS9 folder, typically in your user folder). In contrast, the File Transfer folder on the MacOS9 desktop is a mere convenience for use when copying files from the Computer or This PC folder.
Acknowledgments
Weredude Mac Os Download
This system is built on software provided by many people who are more expert than I am. The included build of SheepShaver was built by Ronald P. Regensburg and posted at the E-Maculation support forum for SheepShaver. The AppleScripts used in this application could not have been written without the help of many experts at Macscripter.net, and the AutoIt script that provides the launcher application could not have been written without the help of many experts in the forum at AutoItScript.com.
Support
Because part of this system is written in the AutoIt scripting language, some anti-virus programs will flag it as malware. Absolutely do not waste your extremely valuable time alerting me to this; do not waste your extremely valuable time writing me an e-mail asking if the software is safe. Do not take my word for it that this is all the result of a false positive. Upload the software to a site like VirusTotal.com for testing. If you do not trust my software, do not use my software.
Please do not ask me to help you customize the 'classic' Mac OS or advise you about any applications. Please ask for support in the E-Maculation support forum for SheepShaver. If you want to get in touch with me about the AppleScript and AutoIt used in this system, then please visit this page.
Edward Mendelson (em thirty-six [at] columbia [dot] edu, but with two initials and two numerals before the [at] sign, not spelled out as shown here).
