| 1 |
cebix |
1.1 |
<HTML> |
| 2 |
|
|
<HEAD> |
| 3 |
|
|
<TITLE>Troubleshooting</TITLE> |
| 4 |
|
|
</HEAD> |
| 5 |
|
|
<BODY BGCOLOR=#FFFFFF> |
| 6 |
|
|
|
| 7 |
|
|
<H1>Troubleshooting</H1> |
| 8 |
|
|
|
| 9 |
|
|
<H2>SheepShaver doesn't boot</H2> |
| 10 |
|
|
|
| 11 |
|
|
SheepShaver should boot all MacOS versions >=7.5.2, except MacOS X. However, |
| 12 |
|
|
your mileage may vary. If it doesn't boot, try again with extensions disabled |
| 13 |
|
|
(by pressing the shift key) and then remove some of these extensions: |
| 14 |
|
|
"MacOS Licensing Extension", Speed Doubler, 68k FPU extensions and MacsBug. |
| 15 |
|
|
|
| 16 |
|
|
<H2>The colors are wrong in 16 or 32 bit graphics modes</H2> |
| 17 |
|
|
|
| 18 |
|
|
If you're running SheepShaver on a something other than a PowerMac, it may be |
| 19 |
|
|
that 16 or 32 bit graphics modes show false colors due to the frame buffer being |
| 20 |
|
|
little-endian. Apart from patching the X server, there's unfortunately nothing |
| 21 |
|
|
that you or SheepShaver can do about this. |
| 22 |
|
|
|
| 23 |
|
|
<H2>Full-screen mode doesn't work</H2> |
| 24 |
|
|
|
| 25 |
|
|
Some X servers on Linux PPC don't support DGA and full-screen mode cannot be used |
| 26 |
|
|
with these (in this case, you should disable it in the "Graphics" settings). If you |
| 27 |
|
|
are seeing a message like "cannot map /dev/kmem (permission denied)", you have to |
| 28 |
|
|
either run SheepShaver as root (not recommended) or give yourself appropriate access |
| 29 |
|
|
rights to /dev/kmem if you can login as root. |
| 30 |
|
|
|
| 31 |
|
|
<H2>Ethernet doesn't work</H2> |
| 32 |
|
|
|
| 33 |
|
|
<UL> |
| 34 |
|
|
<LI>You have to either install the sheep_net driver or configure the ethertap device in the Linux kernel to use Ethernet. See <A HREF="using.html">Using SheepShaver</A> for more information. |
| 35 |
|
|
<LI>If you're using TCP/IP on the MacOS side, you have to set up different IP addresses for Linux and for the MacOS. |
| 36 |
|
|
</UL> |
| 37 |
|
|
|
| 38 |
|
|
<H2>SheepShaver crashes, but yesterday it worked</H2> |
| 39 |
|
|
|
| 40 |
|
|
Try the "Zap PRAM File" item in the main menu of the SheepShaver preferences editor. |
| 41 |
|
|
When you are using a ROM file and switching to a different ROM version, you <B>have</B> |
| 42 |
|
|
to zap the PRAM file or SheepShaver might behave very weird. |
| 43 |
|
|
|
| 44 |
|
|
<H2>Known incompatibilities</H2> |
| 45 |
|
|
|
| 46 |
|
|
<UL> |
| 47 |
|
|
<LI>MacOS programs or drivers which access Mac hardware directly are not supported by SheepShaver. |
| 48 |
|
|
<LI>Speed Doubler, RAM Doubler, 68k FPU emulators and similar programs don't run under SheepShaver. |
| 49 |
|
|
<LI>MacsBug is not compatible with SheepShaver. |
| 50 |
|
|
</UL> |
| 51 |
|
|
|
| 52 |
|
|
<H2>Known bugs</H2> |
| 53 |
|
|
|
| 54 |
|
|
<UL> |
| 55 |
|
|
<LI>The QuickTime 2.5 Cinepak codec crashes the emulator. |
| 56 |
|
|
<LI>Programs that use InputSprockets crash the emulator when in window mode. |
| 57 |
|
|
<LI>The mouse cursor hotspot in window mode is not correct. |
| 58 |
|
|
</UL> |
| 59 |
|
|
|
| 60 |
|
|
<HR> |
| 61 |
|
|
<ADDRESS> |
| 62 |
|
|
SheepShaver User's Guide |
| 63 |
|
|
</ADDRESS> |
| 64 |
|
|
</BODY> |
| 65 |
|
|
</HTML> |
