If you're having trouble with the BeOS or the computer you're running it on, you may be able to narrow down or even fix the problem by reviewing the symptoms and suggestions in this appendix. If the suggestions in this appendix fail to solve the problem, contact Be customer service at custservice@be.com.
Check that you have a working power outlet: Unplug the computer and plug in something a lot simpler, like a lamp. If the power outlet is controlled by a switch, make sure the switch is turned on.
Check that the voltage switch is set correctly for your area: On a BeBox, the voltage switch is a small sliding switch next to the BeBox power switch, as described in the BeBox Owner's Guide. If you have another kind of computer, see its owner's guide for more information.
Check that all cables and cards are firmly connected: Following the instructions in the computer's owner's guide, make sure that all cables, cards, SIMMs, and other components are firmly seated in their connectors and slots and that all external cables and the power cord are securely connected to the correct ports.
Watch that memory passes the memory test: Most computers perform a memory test when you turn them on. The BeBox tries writing to and reading from each pair of installed SIMMs. As it tests writing to a pair of SIMMs, the left LED array on the front of the BeBox illuminates in a rising and falling pattern; as it tests reading from a pair of SIMMs, the right LED array illuminates in the same way. If you don't see this LED pattern, first check that all SIMMs are firmly seated in their sockets. Then try swapping out SIMMs to see if you can identify a bad one. Power Macintosh and compatibles also perform memory tests at startup—see your computer's owner's guide for details.
Check that all the cards you added are compatible with the BeOS: Revisit your owner's guide, installation instructions, "Release Notes," and the Be Web site (http://www.be.com/products) to make sure the cards and other devices you've added to your computer are the exact models supported by the BeOS.
Make sure SCSI disks are correctly terminated and don't have ID conflicts: Review the instructions in your computer's and disks' owner's guides to make sure each SCSI device has a unique SCSI ID and is terminated (or not terminated) correctly.
Use the boot selection screen to check for bootable disks: To open the boot selection screen on a BeBox, hold down any key immediately after you turn it on. To open the BeOS boot selection screen on a Macintosh, hold down the Option key immediately after you double-click BeOS Launcher on a Power Macintosh. The boot selection screen lists all disks it can find that contain a plausible /system folder, as described in "Selecting a Boot Disk" .
Watch for disks to be recognized on a terminal: Connect a terminal to your computer, as described in "Connecting a Terminal", and watch for messages about disks being found.
Check the contents of the floppy and CD-ROM drives: The BeOS tries to boot from a floppy and then a CD-ROM drive if it can find anything resembling a functional /system folder on one of them.
Try using a default screen setting: You can force the BeOS to revert to the default screen settings when booting if you hold down the spacebar as soon as the Be logo disappears. Or if you're already booted but the screen is a mess, press Command-Control-Shift-F12, using the modifier keys on the left side of the keyboard, to force the BeOS to revert to default screen settings.
If the BeOS boots but the Browser never starts, you may have a corrupted Be database. You can rebuild the database by selecting the "Erase their databases" option in the boot selection screen (for more information on the boot selection screen, see "Selecting a Boot Disk" ).
Caution: Rebuild the Be database only as a last resort. Rebuilding the database erases all information you've added to it: You lose all your e-mail, your window layouts, your arrangement of icons on the dock, your database of audio CDs, and all other information you've stored in the Be database.
An unpleasant window with "Team" in the title opens: This is the Be Debugger window. It opens when an application crashes. If you wrote the application, refer to "Using the Be Debugger". If you didn't write the application, try typing es and pressing Enter to close the Debugger window and to quit the crashed application cleanly. Then it's usually a good idea to save any open files and restart the BeOS.
An application goes south, but others don't seem affected: You can force an application to die a violent death. If you have a PC keyboard, hold down the keys labeled "Ctrl," "Alt," and "Shift" on the right side of the keyboard while you choose the application from the application list. If you have a Macintosh keyboard, press the Command, Option, and Shift keys while you choose the application from the application list. Then it's usually a good idea to save any open files and restart the BeOS.
The BeOS freezes up: You have to restart the BeOS. If you have a PC keyboard, first try pressing the keys labeled "Ctrl," "Alt," and "Del" at the same time. If you have a Macintosh keyboard, try pressing Command, Control, and the key labeled "del" above the arrow keys. If that doesn't work, reset the computer by pressing the Reset and Interrupt buttons at the same time on a BeBox, or the Reset button on a Power Macintosh, as described in "Resetting the BeOS".
When you try to shut down or restart, a panel informs you that an application isn't responding: This usually happens when an application has crashed, though it can be because an application is actually still finishing something you asked it to do. When you get tired of waiting, click Blow It Away in the panel.
An application that uses the new Game Kit crashes: The creator of the Game Kit included an escape hatch for rogue games:Press Command-Control-Shift-F12, using the modifier keys on the left side of the keyboard, to escape from the game.
On a BeBox, the BeOS system software and applications send information out serial port 4 if you hold down the F1 key on the keyboard for a few seconds after turning on the BeBox. On a Macintosh, the BeOS and applications send information out the Modem port if you hold down the Delete key for a few seconds after you double-click BeOS Launcher.
You can see these messages if you have a computer or terminal with a serial port that you connect to serial port 4 on the BeBox or the Modem port on a Power Macintosh using a null modem cable. Set the terminal's communications parameters to 19,200 baud, 8 data bits, no stop bits, and no parity.
Note: The messages applications send out the serial port are often misleading and alarmist; many of them were written by people for whom English is not their first language. So it's best to take what you see on a terminal with a grain of salt.
BeOS User's Guide, DR8.2 for Power Mac Edition, 1/16/97.
Copyright © 1997, Be, Inc. All rights reserved.
Please send corrections, suggestions, and comments to userdocs@be.com.