Common problems

• I can't install AWeb. The installer reports errors like: Unable to compile script.
  Most likely some misbehaving application installation has copied an obsolete version of the Commodore Installer utility to your hard drive. Make sure the Installer version in the SYS:C directory is "installer_2 2.17 (1993-02-13)" or better. This version can be found on the Amiga Workbench 3.x Install floppy disk.
  Also, delete any copies of the Installer program from your SYS:Utilities drawer.

• I received my keyfile UUencoded, but now AWeb says "keyfile size error". I used THOR to decode it.
  THOR doesn't decode the file right. It adds an extra byte, which would make AWeb crash if it didn't check the size.
  Use another UUdecoder, or use a binary file editor to remove the last byte from the file (at your own risk, use a copy of the keyfile). The corect size for the keyfile is 376 bytes.

• AWeb crashes when loading a GIF image
  The commonly used ZGif datatype version 39.16 had a bug. Be sure to use version 39.18 or better of the ZGif datatype, or another GIF datatype.

• AWeb doesn't display all of the page. Other browsers display the page correctly
  Probably the page contains some erroneous HTML. One of the common errors is the use of something like <!----------------------> as a dividor line in the HTML source. This can lead to large parts of the page commented out if the number of dashes is not exactly right.
  Apart from notifying the author of the page that his page contains erroneous HTML, you can try to use HTML mode compatible.

• AWeb becomes terribly slow if I run it on its own screen.
  This has something to do with chip memory usage and DMA bandwidth. Apparently, the problem becomes worse when you have an accelerated machine.
  The solution is to use either a lower or a higher speed ("baudrate") to communicate with your modem. Start at the modem speed (so if you own a 14k4 modem, start at 14k4 communication speed). Then increase the speed until you find a dramatic slowdown. Then go one step back.
  Changing the communication speed with your modem might involve adapting the settings for your dialler, TCP stack and/or your SANA driver. Refer to the respecive documentations.

• Backgrounds in AWeb are terribly slow, much slower than competitive Amiga browsers.
  This might be caused by an unsuited picture datatype. Use the 24-bit picture datatype only on CyberGraphics screens; on original Amiga screens this datatype becomes very slow. Use the original picture.datatype from your Workbench diskette.

• The colour requester from the Screen 2: palette settings page messes things up on a CyberGraphics screen.
  This is caused by the palette-orientated design of the Amiga OS. This works fine on Amiga chipset screens, but isn't really suited for graphics cards.

• Closing the AWeb public screen while there is a visitor window open crashes if the screen is a CyberGraphics screen.
  This is a bug in CyberGraphics V 2.15 and lower. The same thing happens on other CyberGraphics screens.

• If the window is not active, a click in the scroller container (outside the knob) moves the scroller but doesn't scroll the window contents.
  This is a bug in Intuition. The same thing happens sometimes with MultiView.

• I use MagicMenu, and every now and then my system hangs if I open a menu.
  This is a known problem in MagicMenu, caused by the fact that MagicMenu is not 100% compatible with the way Intuition handles menus.

• I don't use MagicMenu, but my system hangs if I click on the wide part of the chooser gadget in the settings window.
  Be sure to use the version of chooser.gadget included in this archive.
  Also, some animated mouse pointer commodities are known to cause this hang.