Known Bugs
General problems
- There is a general problem with all extra hardware connected to the Amiga
which generates Interrupts at random or regular times. An example is my
network card (Hydra). If I have my TCP/IP stack running, nearly every
installed program will freeze after a short time because the card creates
PORTS interrupts (the same type as interrupts created by the keyboard) which
cannot correctly replied to by the installed program. This is because as soon
as the request has been acknowledged with an rte, the next interrupt occurs).
To avoid this problem, the TCP/IP stack must be stopped before starting WHDLoad.
- There are some rare hardware configurations which don't support the MMU
related features of WHDload. The only systems affected are 68030 based. The
option MMU/S must not enabled on these systems! If
the option is set, WHDLoad will freeze the whole machine. Currently the
following hardware is known to cause problems: accelerator boards "Apollo
A630", "Apollo 1230" and "Magnum MK2".
Developer related
- The operation of switching between the operation system (OS) and the
installed program is not completely reliable. The problem is that most Custom
registers and some Cia registers cannot be read and therefore cannot be saved
and restored. WHDLoad itself does not change these registers, but when it
switches from the installed program to the OS (e.g. to load a file from disk)
the OS may change some of these not restorable registers. If the installed
program depends on all registers remaining unchanged, this will cause
problems. It is known that the OS changes at least cop2lc, bltafwm and
bltalwm, and perhaps more. As a workround for this problem there is a
possibility to restore the changed registers during the switch sequence. See
AutoDocs/WHDLTAG_CBSWITCH_SET for more
info.