Beginners FAQ:Troubleshooting (Rev #2)

This page gives you a few things to try if you find yourself stuck.

Boot-up problems

System unexpectedly boots to command line

This can happen for several reasons. A few examples:

• You pressed Shift-Break (or were holding down the Shift key as the system booted).
• The system couldn’t find the !Boot directory (e.g. it has been moved or deleted). This can also happen if you have – successfully – moved !Boot to a USB-attached disc drive but are now booting up with yet another disc drive or memory stick attached via USB.
• The “NoBoot” configuration option has been set, or one of the other configuration options (e.g. “FileSystem” or “SCSIFSDrive”) now have incorrect values. Use the *Status command to display the CMOS RAM settings.

How to fix it depends on what the problem was.

• If you have too many devices plugged in at boot time, unplug the additional devices.
• If CMOS RAM settings are now incorrect, use the *LoadCMOS command to load a known-good CMOS settings file. If you have a Raspberry Pi, see CMOS RAM on the Raspberry Pi.

Boot-up stops with an error message

What may happen is that the RISC OS logo appears during the boot, but instead of the desktop you get an error message.

• “Drive not ready”
  Something inside !Boot is trying to access a file on another disc. The most likely reason is that the file is on a FAT32-formatted drive but it appears so early in the boot sequence that Fat32FS (needed to access FAT32-format drives) has not been loaded yet.
• “Memory cannot be moved”
  A common cause of this is that you have configured too large a RAMDisc (the absolute maximum is 512MB but some systems can experience problems if you configure a RAMDisc of more than 400MB).
• “Program is not 32-bit compatible”
  Something recently added to !Boot was designed for use on RISC OS 3, not RISC OS 5. You will need to track down the failing component and remove it.
• “Waiting for boot drive to be ready”
  This is a special case of “Drive not ready” – it indicates that the system cannot get to !Boot itself. If you have a Raspberry Pi, you can sometimes fix this by using the boot_delay parameter in config.txt – see config.txt (Raspberry Pi). It may also indicate that you have additional disc drives connected (see next bullet point).
• System complains File not found on about 50% of reboots
  This can happen if you have multiple disc drives attached and the file in question is being referenced by drive number, not disc name. The problem is that disc drives won’t necessarily start up in the same order, so a given drive may not always get the same drive number.
  It is also a good idea to unplug other things (e.g. USB memory sticks, USB card readers) that might be mistaken for a disc drive at boot time.

Other problems

Game has crashed in a wonky mode

It is possible for an application (usually a game) to change the screen resolution such that when you return to the desktop the icon bar isn’t visible at all, so you can’t get to Display Manager to change the screen resolution to something more sensible.

The easy fix is to press CTRL-BREAK to reboot, but you may not want to do that (e.g. you have unsaved work). In that case, proceed as follows:

• Press F12¹ and blind-type
  wimpmode 32
  and then press RETURN twice. This should get you a full (if somewhat oddly-proportioned) desktop display, allowing you to reach Display Manager to set the screen resolution to something more to your liking.

¹ You probably won’t see a command prompt, but you might notice the desktop display shift upwards slightly.

No picture / Monitor reports “Out of range”

This will typically happen if you’ve somehow managed to select a RISC OS monitor type that is unsuitable for your monitor.

• First get to a screen mode that the monitor can display. You might use CTRL-BREAK to reboot the machine, or you can press F12 and blind-type wimpmode 32 (as mentioned above).
• Having got yourself to a desktop (of sorts) you can now use !Configure to set the monitor type to “Auto(your-monitor-name-here)” (e.g. “Auto(L225W)”) and the screen resolution to “Native”.

Keyboard not responding / Mouse clicks ignored

If nothing happens when you press keys on the keyboard and/or click a mouse button (but the mouse pointer still moves) this may indicate that an application is misbehaving. Try each of the following in turn:

1. Press ALT-BREAK and quit the first-named application².
2. Press CTRL-BREAK to reset the machine.
3. Power off, then power on again.

² If you successfully use ALT-BREAK to quit the application, the system could still be unstable. Save as much work as you can, then shut down and restart.

Files copied to a USB drive are incomplete (or missing)

This could be for one of two reasons:

• You didn’t dismount the drive and/or you didn’t wait the regulation 10-15 seconds before disconnecting.
• On a Raspberry Pi, you plugged your device into one of the built-in USB ports, overloading the Pi’s PSU and causing a voltage drop which interfered with the operation of the drive. This can be avoided by plugging the USB drive into a powered USB hub (i.e. a hub with its own power brick).