Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
sheepshaver_mac_os_x_setup [2018/06/17 02:20] – [First run, setup, basic functions] ronald_p._regensburg | sheepshaver_mac_os_x_setup [2019/04/12 03:49] – [Setting up SheepShaver for OSX/macOS on Intel Macs] ronald_p._regensburg | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Setting up SheepShaver for Mac OS X ====== | + | ====== Setting up SheepShaver for OSX/macOS on Intel Macs ====== |
- | (Last updated | + | (Last updated |
- | (You can also set up [[sheepshaver setup|SheepShaver | + | (You can also set up SheepShaver versions [[sheepshaver mac os x setup old|for PPC Mac]], |
===== Introduction ===== | ===== Introduction ===== | ||
=== === | === === | ||
- | This manual is revised for use with the 25-10-2009 | + | This manual is revised for use with the **July 2018 and later builds of [[SheepShaver]] for Intel Macs**.\\ |
+ | For older SheepShaver builds that will run on PPC Macs, see this [[sheepshaver mac os x setup old|older setup guide]]. | ||
- | **Download SheepShaver application from [[http:// | + | **Download |
+ | Please read the information on that page, newer information | ||
- | We start with the description of a classic setup with all files together in a folder named " | + | **Classic setup: |
+ | However, files and folders can be renamed and/or moved to different locations, provided you make sure the file names and/or full paths to the files are entered in SheepShaver preferences. | ||
- | **Note:** Changed settings | + | **Changing settings:** After saving changes |
- | **Mountain Lion and later issue:** OSX 10.8 and later prevents mounting of physical CD-ROMs in SheepShaver but images created from CD-ROMs | + | **CD-ROMs:** Up to Mac OS X 10.7, physical CD-ROMs can be mounted within SheepShaver. Just insert the CD on the host system and the CD will be mounted on the guest desktop. OS X 10.8 and later prevents mounting of physical CD-ROMs in SheepShaver but disk images created from CD-ROMs will work fine. |
- | // | + | As most users will now use disk image files instead of physical CD-ROMs, this guide will describe |
- | Please post questions and comments on E-Maculation SheepShaver forum: http://www.emaculation.com/forum/. | + | //(Alternative instructions for using a real physical install CD are added throughout this guide in italics between brackets.)// |
+ | Please post questions and comments on E-Maculation SheepShaver forum: https:// | ||
===== Setting up SheepShaver ===== | ===== Setting up SheepShaver ===== | ||
==== You need a Mac OS install CD ==== | ==== You need a Mac OS install CD ==== | ||
Line 29: | Line 33: | ||
You will need a compatible Mac OS install CD to be able to install a Mac OS in the SheepShaver emulated machine. Depending on the used ROM file (see below for more info on ROM files), SheepShaver can run System 7.5.3 through Mac OS 9.0.4. SheepShaver cannot run 9.1 or later. | You will need a compatible Mac OS install CD to be able to install a Mac OS in the SheepShaver emulated machine. Depending on the used ROM file (see below for more info on ROM files), SheepShaver can run System 7.5.3 through Mac OS 9.0.4. SheepShaver cannot run 9.1 or later. | ||
- | Only generic | + | Only general |
Line 39: | Line 43: | ||
=== === | === === | ||
- | //(A disk image of a retail Mac OS install CD can be used instead of the real CD. The disk image must be in a non-compressed format | + | This guide assumes that you own a suitable |
+ | Install CD image files can also be downloaded from various places on the internet. Make sure the image is indeed created from a general retail Mac OS install | ||
- | //(This guide assumes that you own a suitable retail Mac OS install CD and that you can create | + | You can create disk images |
+ | - Mount the CD in OSX/ | ||
+ | - Start Disk Utility (in the / | ||
+ | - Select the CD volume (not the drive) | ||
+ | - Click New Image in the tool bar or in newer Disk Utility versions use New Image from the File menu\\ | ||
+ | - Choose DVD/CD master | ||
+ | - Save the image file. It will have a .cdr extension. | ||
==== The files you need in your SheepShaver folder ==== | ==== The files you need in your SheepShaver folder ==== | ||
=== 1. The SheepShaver application === | === 1. The SheepShaver application === | ||
+ | |||
+ | The SheepShaver application and the SheepShaver folder are presented as separate downloads. Drag the SheepShaver application into the SheepShaver folder. | ||
=== 2. A compatible ROM file === | === 2. A compatible ROM file === | ||
Line 51: | Line 64: | ||
**SheepShaver will not run without a compatible ROM file. If SheepShaver does not find a compatible ROM file, it will immediately quit on launch.** | **SheepShaver will not run without a compatible ROM file. If SheepShaver does not find a compatible ROM file, it will immediately quit on launch.** | ||
- | It may be difficult to get hold of a compatible ROM file as distributing bare ROM files violates Apple license agreements. Emaculation.com site policy is to not offer or link directly to bare ROM files, although Apple seems to have stopped taking action against distribution of ROM files. | + | It may be difficult to get hold of a compatible ROM file as distributing bare ROM files violates Apple license agreements. Emaculation.com site policy is still to not offer or link directly to bare ROM files, although Apple seems to have stopped taking action against distribution of ROM files. |
- | The ROM file from a 9.0.4 system CD will not work with any version of SheepShaver. ROM files from a 8.5 or 8.6 system CD may work with SheepShaver for Windows, but do not work with SheepShaver for Mac OS X (with a few specific exceptions that are beyond the scope of this manual). | + | The ROM file from a 9.0.4 system CD will not work with any version of SheepShaver. ROM files from a 8.5 or 8.6 system CD may work with SheepShaver for Windows, but do not work with SheepShaver for OSX/ |
- | ROM files that will work with SheepShaver for Mac OS X are either an "old world" rom image grabbed from an actual hardware PowerMacintosh ROM, or the "new world" rom file extracted from the "Mac OS ROM Update 1.0" using TomeViewer. The "Mac OS ROM Update 1.0" can be downloaded from Apple, but you need to have a working Mac OS system (or Classic in Mac OS X) to run TomeViewer. | + | ROM files that will work with SheepShaver for OSX/ |
[[http:// | [[http:// | ||
Line 69: | Line 82: | ||
If you want to install 8.6 through 9.0.4, best use the new world rom. | If you want to install 8.6 through 9.0.4, best use the new world rom. | ||
- | When you have acquired a compatible ROM file, **rename it "Mac OS ROM" | + | When you have acquired a compatible ROM file, **rename it "Mac OS ROM"**, without the quotation marks and without a file name extension. You can check the existence of an extension in Finder Info for the file. (The renaming is needed because without configuration |
=== 3. A keycodes file === | === 3. A keycodes file === | ||
- | The keycodes file is needed with other than US-English QWERTY keyboard layouts. It is not needed (but does no harm either) if only a US-English keyboard will be used. If you did not get a keycodes file with your SheepShaver | + | The keycodes file is needed with other than US-English QWERTY keyboard layouts. It is not needed (but does no harm either) if only a US-English keyboard will be used. The keycodes file is already present in the downloaded |
+ | |||
+ | |||
+ | === 4. The install CD image file === | ||
- | [[http:// | + | If you are going to use an install CD image file for installing the Mac OS in SheepShaver, |
==== The shared folder ==== | ==== The shared folder ==== | ||
=== === | === === | ||
- | From within SheepShaver you will have access to a folder on the Mac OS X side. That folder will appear on the SheepShaver desktop as a disk named " | + | From within SheepShaver you will have access to a folder on the OSX/ |
- | Before you start configuring SheepShaver, | + | Before you start configuring SheepShaver, |
- | **Note:** Although | + | **Note:** Although serious bugs that plagued the shared folder feature in early versions of SheepShaver have been solved, we still advise to not use folders like your Documents folder or your Home folder as shared folder and not keep the only existing copy of a file in the shared folder. |
**Note:** Applications cannot run properly from the " | **Note:** Applications cannot run properly from the " | ||
Line 92: | Line 108: | ||
=== === | === === | ||
- | When the needed files are in the SheepShaver folder, when you have created a shared folder, and when you have your Mac OS system install disk ready, you can start configuring SheepShaver. | + | When the needed files are in the SheepShaver folder |
=== 1. Start SheepShaver === | === 1. Start SheepShaver === | ||
+ | |||
+ | SheepShaver is not code signed. The first time you launch SheepShaver you may need to right-click or control-click its icon to open it from the contextual menu. | ||
If SheepShaver does not find a compatible ROM file, it will immediately quit on launch. | If SheepShaver does not find a compatible ROM file, it will immediately quit on launch. | ||
Line 102: | Line 120: | ||
{{ http:// | {{ http:// | ||
- | **Note:** At this stage you can only quit SheepShaver pressing Control-Escape. | + | **Note:** At this stage you can only hard quit SheepShaver |
=== 2. Open Preferences from SheepShaver application menu === | === 2. Open Preferences from SheepShaver application menu === | ||
Line 108: | Line 126: | ||
Choose Preferences from the SheepShaver menu to open the preferences (Virtual Machine Settings) window. | Choose Preferences from the SheepShaver menu to open the preferences (Virtual Machine Settings) window. | ||
- | (The preferences settings will be saved in a invisible file .sheepshaver_prefs in your Home folder. The following description assumes that SheepShaver is set up for the first time and that there is no pre-existing ~/ | + | (The preferences settings will be saved in an invisible file .sheepshaver_prefs in your Home folder. The following description assumes that SheepShaver is set up for the first time and that there is no pre-existing ~/ |
=== 3. Configure preferences in Setup tab === | === 3. Configure preferences in Setup tab === | ||
Line 115: | Line 133: | ||
First add the ROM file name using the " | First add the ROM file name using the " | ||
- | {{ http:// | + | {{ :ssosxprefs0-2.png }} |
**Volumes**\\ | **Volumes**\\ | ||
You can now proceed with creating the disk image file that will be the virtual hard disk on the emulated Mac. Click the " | You can now proceed with creating the disk image file that will be the virtual hard disk on the emulated Mac. Click the " | ||
- | {{ http:// | + | {{ :ssosxcreate-2.png }} |
- | Choose an appropriate name for the image file, for instance MacOS9. (An extension .dsk will be suggested, but no extension is needed.) Choose a size for the volume (for instance | + | Choose an appropriate name for the image file, for instance MacOS9. (An extension .dsk will be suggested, but no extension is needed.) Choose a size in MB for the volume (for instance |
- | {{ http://www.emaculation.com/ | + | Then, if a Mac OS install CD image file is used, use the "Add..." button to find and " |
- | //(If an install CD disk image file is used instead of a real install CD: Use the "Add..." button to find and " | + | {{ :ssosxprefs1-2.png }} |
**Unix Root**\\ | **Unix Root**\\ | ||
Add the path to your shared folder using the second " | Add the path to your shared folder using the second " | ||
- | **Do not keep the default value "/", | + | **Do not keep the default value "/", |
**RAM Size (MB)**\\ | **RAM Size (MB)**\\ | ||
Line 142: | Line 160: | ||
=== 4. Configure preferences in Audio / Video tab === | === 4. Configure preferences in Audio / Video tab === | ||
- | {{ http:// | + | {{ :ssosxprefs2-2.png }} |
**Video Type**\\ | **Video Type**\\ | ||
Line 149: | Line 167: | ||
**Refresh Rate**\\ | **Refresh Rate**\\ | ||
- | On fast Intel machines | + | On fast Intel machines |
- | (On slower machines a lower setting like 30Hz or 15Hz may improve performance and will lower the extreme CPU hunger of SheepShaver on PPC machines.) | + | |
**Width and Height**\\ | **Width and Height**\\ | ||
- | Set Width and Height for the window to lower values than the width and height of your screen. If you have a large screen, you can enter higher values than those in the menu, for instance 1280 x 800. | + | Set Width and Height for the window to lower values than the width and height of your screen. If you have a large screen, you can enter higher values than the presets |
Check **Enable QuickDraw Acceleration**. | Check **Enable QuickDraw Acceleration**. | ||
Line 161: | Line 178: | ||
=== 5. Configure preferences in Miscellaneous tab === | === 5. Configure preferences in Miscellaneous tab === | ||
- | {{ : | + | {{ : |
**CPU Options**\\ | **CPU Options**\\ | ||
- | Check only " | + | Check " |
**Mouse/ | **Mouse/ | ||
Line 178: | Line 195: | ||
=== 6. Save your settings === | === 6. Save your settings === | ||
- | Click " | + | Click " |
+ | (In 2 February 2019 and later builds the " | ||
=== 7. Quit SheepShaver === | === 7. Quit SheepShaver === | ||
- | The emulated machine cannot be shutdown | + | The emulated machine cannot be shut down normally while waiting for a boot disk and SheepShaver cannot be quit with the emulated machine still running. So at this point we use Control-Escape to quit SheepShaver, |
==== Booting SheepShaver and installing the system ==== | ==== Booting SheepShaver and installing the system ==== | ||
=== === | === === | ||
- | If you use a real install CD, **first insert the CD** and have it mount in Mac OS X. | + | //(If you use a real install CD, **first insert the CD** and have it mount in OSX/macOS.)// |
- | //(If you use a install CD disk image instead of a real install CD, make sure the CD image file is locked | + | Do **not** have your install CD image mounted |
- | **Launch SheepShaver**. The emulated machine will startup | + | **Launch SheepShaver**. The emulated machine will start up from the install CD image //(or from the install |
- | During startup, the system will encounter the newly created volume and will offer to initialize it. Give the volume an appropriate name (for instance MacOS9HD) and (for Mac OS 8.1 or later) choose Mac OS Extended for the format. Click to proceed with initializing the volume. | + | During startup, the system will encounter the newly created volume and will offer to initialize it. Give the volume an appropriate name (for instance MacOS9HD) and (for Mac OS 8.1 and later) choose Mac OS Extended for the format. Click to proceed with initializing the volume. |
- | Finally, you will see the desktop with icons for the startup volume (the CD or the CD disk image), for the new volume that you will install the system onto, and for the " | + | Finally, you will see the desktop with icons for the startup volume (the CD image or the CD), for the new volume that you will install the system onto, and for the " |
Proceed with the system installation by starting (double-clicking) the installer "Mac OS Install" | Proceed with the system installation by starting (double-clicking) the installer "Mac OS Install" | ||
Line 208: | Line 225: | ||
When the installation is completed, you can quit the installer. | When the installation is completed, you can quit the installer. | ||
- | //(If you used a install CD disk image file instead of a real install CD: Open SheepShaver Preferences and remove the CD disk image file from the volumes list, select it and click the Remove button.)// | + | Open SheepShaver Preferences and **remove the CD disk image file from the volumes list**, select it and click the Remove button. |
Shut down the emulated machine and quit SheepShaver. | Shut down the emulated machine and quit SheepShaver. | ||
- | If you used a real install CD, you can now remove it in Mac OS X. | + | //(If you used a real install CD, you can now remove it in OSX/macOS.)// |
===== Running Mac OS in SheepShaver ===== | ===== Running Mac OS in SheepShaver ===== | ||
==== First run, setup, basic functions ==== | ==== First run, setup, basic functions ==== | ||
Line 228: | Line 245: | ||
**Enable network access**\\ | **Enable network access**\\ | ||
- | Set the TCP/IP control panel to Ethernet and DHCP. As soon as you start using IP network access, for instance with a web-browser, | + | Set the TCP/IP control panel to Ethernet and DHCP. As soon as you start using IP network access, for instance with a web-browser, |
**QuickTime**\\ | **QuickTime**\\ | ||
Line 236: | Line 253: | ||
**CD-ROM**\\ | **CD-ROM**\\ | ||
- | To use a CD-ROM in SheepShaver, insert | + | You can use a CD-ROM in SheepShaver |
- | (OSX 10.8 and later prevents mounting physical CD-ROMs in SheepShaver. Use disk images instead.) | + | OSX 10.8 and later prevents mounting physical CD-ROMs in SheepShaver. Use disk images instead. |
**Additional volumes**\\ | **Additional volumes**\\ | ||
- | In Preferences you can create additional volumes (disk image files) or add existing compatible disk image files as additional volumes. | + | In Preferences you can create additional volumes (disk image files) or add existing compatible disk image files as additional volumes. |
+ | Most ' | ||
+ | |||
+ | Note that after any change in preferences SheepShaver needs to be quit and launched again. | ||
==== The shared folder / " | ==== The shared folder / " | ||
Line 248: | Line 268: | ||
**Transferring files**\\ | **Transferring files**\\ | ||
- | As explained above, the shared folder that you created in Mac OS X will appear on the SheepShaver desktop as a disk (a volume) named “Unix”. Files copied or saved in SheepShaver to the “Unix” disk, will appear in the shared folder on the Mac OS X side and files placed in the shared folder on the Mac OS X side will appear in the “Unix” disk in SheepShaver. That way you can use the shared folder and the “Unix” disk to transfer or exchange files in both directions. | + | As explained above, the shared folder that you created in OSX/ |
Exchanging files via the shared folder used to be crippled by many bugs. The most serious bugs have been solved but you may still encounter occasional unexpected behaviour while copying folders to and from the “Unix” disk. | Exchanging files via the shared folder used to be crippled by many bugs. The most serious bugs have been solved but you may still encounter occasional unexpected behaviour while copying folders to and from the “Unix” disk. | ||
Line 255: | Line 275: | ||
If you use the shared folder and “Unix” disk to transfer applications for use in SheepShaver, | If you use the shared folder and “Unix” disk to transfer applications for use in SheepShaver, | ||
- | Note that moving files directly from the “Unix” disk onto the SheepShaver desktop, does not copy them to the startup system volume. Those files will still be on the “Unix” disk, in fact inside the folder “Desktop Folder” in the shared folder. | + | Note that moving files directly from the “Unix” disk onto the SheepShaver desktop, does not copy them to the startup system volume. Those files will still be on the “Unix” disk, in fact inside the folder “Desktop Folder” in the shared folder. If you want to copy files from the " |
**Trashing files**\\ | **Trashing files**\\ | ||
- | Trashing files from the shared folder should be done at the Mac OS X side. On the Mac OS side, the trash cannot be emptied when it contains files from the " | + | Trashing files from the shared folder should be done at the OSX/ |
- | + | ||
- | ==== Mounting disk images ==== | + | |
- | + | ||
- | === === | + | |
- | + | ||
- | Most ' | + | |
- | + | ||
- | Disk images created with Disk Utility in Mac OS X can be mounted the same way, provided the format chosen while creating the image is either " | + | |
- | + | ||
- | A system install CD image file must be locked in Mac OS X Finder Get Info because the installer will refuse to work on writeable media. Locking the file is usually not needed for other CD images, but it can be used as a precaution to make sure the content of the image is not changed. | + | |
==== Printing ==== | ==== Printing ==== | ||
Line 284: | Line 294: | ||
=== === | === === | ||
- | SheepShaver can be set to run full-screen | + | SheepShaver can run full-screen. |
- | While SheepShaver is running full-screen, | + | While SheepShaver is running full-screen, |
- | + | ||
- | The latest SheepShaver build makes that easy with a new feature: **fullscreen/ | + | |
- | + | ||
- | \\ | + | |
- | \\ | + | |
- | + | ||
- | With older builds, if you want to go back to running SheepShaver in window mode, you can use the stand-alone preferences editor: | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | Or you can edit the related line in the prefs file in a text editor: | + | |
- | + | ||
- | Window mode and 1024x769 resolution: | + | |
- | screen win/ | + | |
- | + | ||
- | Fullscreen mode and 1024x769 resolution: | + | |
- | screen dga/ | + | |
- | + | ||
- | Fullscreen mode and maximum resolution: | + | |
- | screen dga/0/0 | + | |
+ | In SheepShaver Preferences, | ||
+ | **Mission Control and Spaces** | ||
+ | The 64-bit 2.5 version SheepShaver builds (Mac OS X 10.7 and later only) will behave much like other applications in full-screen mode. It is compatible with Mission Control and you can easily switch between SheepShaver in full-screen mode and other applications in full-screen mode or the desktop using the swipe gesture that moves between spaces. | ||
===== Virtual machines ===== | ===== Virtual machines ===== | ||
Line 314: | Line 307: | ||
=== === | === === | ||
- | SheepShaver for OS X supports self-contained virtual machines. These virtual machines are packages with all needed files inside. They are portable to any compatible | + | SheepShaver for OSX/ |
- | The feature was added to SheepShaver in 2009. It was discussed in the forum here:\\ | + | Apart from the .sheepvm package creation, the setup is identical |
- | http:// | + | |
- | + | ||
- | These instructions are about self-contained .sheepvm packages. A way to manage multiple virtual machines from one setup window will be described under " | + | |
- | + | ||
- | Apart from the .sheepvm package creation, the setup is similar | + | |
**1. A SheepShaver application needs to be present on your machine.** | **1. A SheepShaver application needs to be present on your machine.** | ||
Line 332: | Line 320: | ||
- Add a .sheepvm extension to the folder name\\ | - Add a .sheepvm extension to the folder name\\ | ||
- | When you add the extension, the folder will change into a package with a SheepShaver icon. I will refer to it as the VM. | + | As soon as you add the extension, the folder will change into a package with a SheepShaver icon. I will refer to it as the VM. |
**3. Double-click the VM icon.**\\ | **3. Double-click the VM icon.**\\ | ||
- | SheepShaver will start and you can set up the VM in SheepShaver preferences as you would a ' | + | SheepShaver will start and you can set up the VM in SheepShaver preferences as you would a ' |
- | Multiple different | + | VMs are portable and will work on any compatible OSX/macOS system that has SheepShaver installed. If a SheepShaver.app is added to the VM, it is portable as one single package to machines that do not have SheepShaver installed. * * |
- | VMs are portable and will work on any compatible Mac OS X system that has SheepShaver installed. If a SheepShaver.app is added to the VM, it is portable as one single package to machines that do not have SheepShaver installed. | + | You can add or remove files to/from the VM by opening |
== == | == == | ||
- | //The VM will not necessarily use the SheepShaver application inside. The VM behaves as a SheepShaver document that will be opened with the " | + | //* The empty " |
+ | //* * Note that the VM will not necessarily use the SheepShaver application inside. The VM behaves as a SheepShaver document that will be opened with the " | ||
=== === | === === | ||
- | You can add or remove files to/from the VM by opening it in the Finder: Select the VM, right-click (or control-click) on the icon and choose "Show Package Contents" | ||
- | * The empty " | + | ===== Additional features ===== |
- | ==== SheepShaverLauncher | + | |
+ | === === | ||
- | ===== Uninstalling SheepShaver | + | Some features are not mentioned elsewhere in this manual: |
+ | |||
+ | **Grabbing mouse cursor toggle** (Only in version 2.4 builds)\\ | ||
+ | Using Control-F5 will contain the mouse cursor within the SheepShaver window. This may be useful with some games. | ||
+ | |||
+ | ===== Advanced features (Version 2.5 builds only) ===== | ||
=== === | === === | ||
- | To uninstall SheepShaver, | + | **These features can be activated by manually editing |
- | Then remove | + | **• Hardware cursor in window mode**\\ |
- | | + | The version 2.5 builds use a different way to display |
- | | + | |
+ | However, with the hardware cursor the cursor issues in version 2.4, when switching between window mode and full-screen mode, will also return. (See below under Known Issues.) | ||
- | That's it! | + | **• Hardware cursor in full-screen mode** (29 March 2019 and later builds)\\ |
- | =====Known issues===== | + | The hardware cursor can also be used in full-screen mode if also integer scaling is used. You can enable the hardware cursor in full-screen mode by adding these lines to the preferences file |
+ | hardcursor true | ||
+ | scale_integer true | ||
+ | scale_nearest true | ||
+ | See also " | ||
- | ====All Builds==== | + | **• Changing the hotkey**\\ |
+ | By default, the hotkey used with window/ | ||
- | === === | + | 1: control(default)\\ |
+ | 2: option\\ | ||
+ | 3: control+option\\ | ||
+ | 4: command\\ | ||
+ | 5: control+command\\ | ||
+ | 6: option+command\\ | ||
+ | 7: control+option+command | ||
- | **On PPC machines**\\ | + | For instance, you can set the hotkey to Control-Command by adding this line to the preferences file: |
- | SheepShaver | + | hotkey 5 |
+ | |||
+ | **• Changing scaling algorithm** (Works as intended in 24 February 2019 and later builds)\\ | ||
+ | Using nearest-neighbour or integer scaling will improve display quality when a low resolution emulator screen | ||
+ | scale_integer true | ||
- | **Crash at startup**\\ | + | scale_nearest true |
- | On some host machines and/or with some configurations in the installed Mac OS system, SheepShaver will crash during Mac OS startup. In Console log you will then typically find, among the lines that refer to SheepShaver, | + | |
- | The exact cause of the crash is not known, but in most cases it can be prevented | + | **• Changing reported CPU speed** (16 January 2019 and later builds)\\ |
+ | SheepShaver identifies itself as a 100MHz machine to software running on it. Although | ||
+ | cpuclock 200 | ||
+ | This line wil make SheepShaver identify itself | ||
+ | **Note: **This setting does not change the actual speed! | ||
- | Download: http://www.xs4all.nl/ | + | **• Offset date in years and/or days** (20 February 2019 and later builds)\\ |
+ | The date inside SheepShaver can be set in the past or in the future, in years and/or days. This may be needed for using some specific software. | ||
+ | Adding these lines to the preferences file will set the date to 25 February 1989 when the actual date on the host is 20 February 2019: | ||
+ | yearofs -30 | ||
+ | dayofs +5 | ||
+ | **Note: **This feature can mix up relations between older files and newer files and between files' creation dates and modification dates. It should only be used by experienced users who know what they are doing, preferably in a separate (sheepvm VM) setup. | ||
+ | ===== Uninstalling SheepShaver ===== | ||
- | **CD-ROMs in OSX 10.8 (Mountain Lion) and later**\\ | + | === === |
- | OSX 10.8 and later prevent mounting of physical CD-ROMs in SheepShaver. Use CD disk images instead.\\ | + | |
- | To create a disk image: \\ | + | To uninstall SheepShaver, |
- | - Mount the CD in OSX \\ | + | |
- | - Start Disk Utility (in the / | + | |
- | - Select the CD in the list on the left\\ | + | |
- | - Click New Image in the tool bar (in newer Disk Utility versions use New Image from the File menu)\\ | + | |
- | - Choose DVD/CD master for the format\\ | + | |
- | - Click Save\\ | + | |
- | - Place the image file where you want to use it and then lock the file in the OSX Finder (checkbox in the Finder Info panel for the file).\\ | + | |
- | - Use the SheepShaver preferences editor to add the image to the volumes list. Shut down and restart SheepShaver. The CD will show up on the desktop.\\ | + | |
- | In some cases, when the CD has a special format or when the software insists that the original CD needs to be present, you need to use the **Virtual DVD-ROM/CD Utility** to get a CD image to mount in SheepShaver. | + | Then remove |
+ | rm .sheepshaver_prefs | ||
+ | rm .sheepshaver_nvram | ||
+ | |||
+ | Or use the two scripts that are included | ||
- | Download: http:// | + | That's it! |
+ | =====Known issues===== | ||
- | - Start SheepShaver.\\ | + | ==== All 2018 and later builds ==== |
- | - Install the Virtual DVD-ROM/CD Utility\\ | + | |
- | - Create a new volume with the preferences editor, large enough to hold the contents of the CD image you will create. For one CD image, 800 Mb should be enough. You can create a larger volume to hold more such CD images.\\ | + | |
- | - Shut down and restart SheepShaver. The new disk image will need to be initialized.\\ | + | |
- | - Use the preferences editor to add the CD image you created earlier in OSX (see above) to the volumes list.\\ | + | |
- | - Shut down SheepShaver, | + | |
- | - Launch the Virtual DVD-ROM/CD Utility, click the button " | + | |
- | - Save the new image to the large volume you created for this purpose.\\ | + | |
- | - Unmount the first CD volume from MacOS, remove the CD image from the volumes list, save, and shut down SheepShaver.\\ | + | |
- | - Start again SheepShaver and launch the Virtual DVD-ROM/CD Utility, click the button "Mount Toast .ati file as Virtual DVD-ROM" | + | |
- | + | ||
- | ==== 11 February 2012 and later builds ==== | + | |
=== === | === === | ||
- | **On PPC machines**\\ | + | **Crash at startup**\\ |
- | These later builds appear to be unstable on some PPC configurations. | + | On some host machines and/or with some configurations |
- | http://www.xs4all.nl/ | + | Most of these crashes can be prevented by checking “Ignore Illegal Memory Accesses” in Miscellaneous tab in SheepShaver preferences as advised in the configuration directions above. When it is impossible to start SheepShaver because of the crash, you can move the startup volume temporarily to a different location. Then you can launch SheepShaver to the screen with blinking question mark and access the Preferences. |
- | (That build will present on PPC an " | + | **Bug with the mount image as CD-ROM feature**\\ |
+ | Unintended behavior when you try to remove/ | ||
- | **On Intel machines**\\ | + | This issue can be avoided by only adding |
- | After minimizing or hiding the SheepShaver window | + | |
- | If you find this issue very disturbing and do not need new features in later builds, you can try the older 25 October 2009 build: | + | ==== Version 2.4 (9 July 2018) build ==== |
- | http:// | + | === === |
- | **In 64-bit mode in Snow Leopard**\\ | + | **Cursor issues when switching between window mode and full-screen |
- | Serious cursor problems with clicking in the menu bar in full-screen mode. Use SheepShaver in 32-bit mode if you want to use it full-screen. | + | When you switch from window to full-screen mode using Control-Return before |
- | ==== 1 February 2014 build ==== | + | When you switch from full-screen to window mode using Control-Return, |
+ | ==== Version 2.5 builds | ||
=== === | === === | ||
- | When you switch from window to full-screen mode using Ctrl-Return before you used the mouse cursor in the emulator at least once, you may loose the cursor. One click on the desktop or pressing the control key suffices to bring back the cursor. | + | **CapsLock issue**\\ |
+ | If SheepShaver is launched while CapsLock is active, typed text will not correctly reflect | ||
+ | One press on the CapsLock key will correct the issue. |