Troubleshooting FAQ

Now Airburst has been available for a while, we've got some good feedback on any problems people might be having with installing and running Airburst. If you're having problems with the game, have a look through this list of frequently asked questions and see if it helps. If not, send us an email at zwilnik@mac.com and we'll do our best to help you out.

Q) When I try to run Airburst I get the message "Can't load CarbonLib <<whateverfunction>>" or similar... A) Make sure you've got the latest CarbonLib from Apple installed, Airburst (and many other games) needs an up to date version. You can download it from Apple here... CarbonLib 1.4

Q) When I run Airburst the game says it couldn't run in 800x600 mode on my monitor and is in 'compatibility mode'. How do I get it to run in full screen ? A) Some monitors cannot automatically select 800x600 mode, so we've added the 'compatibility mode' whereby the game attempts to find the nearest big enough screen mode to run the game. Sometimes, your monitor *can* do 800x600 but doesn't tell MacOS that it's 'safe' to use the mode. If this happens, Airburst attempts to change into that resolution and pops up a dialogue box to ask you if it looks ok. If it is ok, then click on the OK button, if the screen has gone funny then either click on cancel to just use the screen mode you were already in, or wait 10 seconds for the same result. If your monitor can't handle 800x600 mode or if you would prefer to stay in the screen mode you use normally for your desktop, hold down the SHIFT key while launching Airburst and the game will stick with the screen size you are already in. Please note that Airburst will need at least 800x600 pixels to work though ! If you do use a larger screen mode (by choice or because your monitor doesn't support 800x600) then you may want to increase the memory allocation of Airburst if you're using MacOS 8.6 or 9.

Q) I've got an iBook 500 (twin USB) and sound cuts off after about 15 seconds. What' can I do ? A) This is a known bug that seems to occur on *some* iBook500s (unfortunately not ours). Fortunately it's easily solved by updating to MacOS 9.22