ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/cebix/SheepShaver/doc/BeOS/troubleshooting.html
Revision: 1.1.1.1 (vendor branch)
Committed: 2002-02-04T16:58:13Z (22 years, 9 months ago) by cebix
Content type: text/html
Branch: MAIN, cebix
CVS Tags: start, HEAD
Changes since 1.1: +0 -0 lines
Log Message: 
Imported sources

File Contents

# User Rev Content
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 &gt;=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 BeBox, the only graphics modes that have
19     the right colors are the 8 bit modes (this is actually a hardware problem
20     and has to do with frame buffers being little-endian on the BeBox), unless
21     you are using a Matrox Milennium I/II.
22     <P>You should also be aware that not all graphics cards support 16 bit modes
23     under BeOS (especially S3 cards don't). Check the BeOS "Screen" preferences
24     application to see if your card does.
25    
26     <H2>SheepShaver appears to be very slow</H2>
27    
28     <UL>
29     <LI>Don't use the window modes, the fullscreen modes are much faster.
30     <LI>If you nevertheless want (or have) to use a window mode, you should set the
31     color depth in MacOS to the same as the BeOS workspace you are running SheepShaver on
32     (e.g. if you are on a 16-bit workspace, set the color depth in MacOS to "Thousands").
33     Also, set the window refresh rate to a low value (high values like 30Hz will make SheepShaver
34     (and BeOS) slower, not faster!).
35     </UL>
36    
37     <H2>Full-screen mode doesn't work</H2>
38    
39     If your machine uses the "IXMicro" BeOS video driver (TwinTurbo cards), you
40     will have to disable the "QuickDraw Acceleration" in the "Video" pane of the
41     SheepShaver settings.
42    
43     <H2>Ethernet doesn't work</H2>
44    
45     <UL>
46     <LI>Is the Ethernet set up under BeOS? Ethernet will not work in SheepShaver if you didn't set it up in the BeOS "Network" preferences.
47     <LI>If you're using TCP/IP on the MacOS side, you have to set up different IP addresses for the BeOS and for the MacOS.
48     <LI>Try disabling AppleTalk in the BeOS Network preferences (there might be conflicts between BeOS AppleTalk and SheepShaver networking).
49     </UL>
50    
51     <H2>SheepShaver crashes, but yesterday it worked</H2>
52    
53     Try the "Zap PRAM File" item in the main menu of the SheepShaver preferences editor.
54     When you are using a ROM file and switching to a different ROM version, you <B>have</B>
55     to zap the PRAM file or SheepShaver might behave very weird.
56    
57     <H2>Known incompatibilities</H2>
58    
59     <UL>
60     <LI>MacOS programs or drivers which access Mac hardware directly are not supported by SheepShaver.
61     <LI>Speed Doubler, RAM Doubler, 68k FPU emulators and similar programs don't run under SheepShaver.
62     <LI>MacsBug is not compatible with SheepShaver.
63     <LI>If you want to run RealPC on a BeBox, you have to disable one CPU in the "Pulse" application or it will crash.
64     </UL>
65    
66     <H2>Known bugs</H2>
67    
68     <UL>
69     <LI>The QuickTime 2.5 Cinepak codec crashes the emulator.
70     <LI>Programs that use InputSprockets crash the emulator when in window mode.
71     <LI>The mouse cursor hotspot in window mode is not correct.
72     </UL>
73    
74     <HR>
75     <ADDRESS>
76     SheepShaver User's Guide
77     </ADDRESS>
78     </BODY>
79     </HTML>