1. emutos detects a 68010 CPU by the implemented MOVE_FROM_CCR operation.
   This leads to a wrong TRAP operation because the 68010 has a 4 word
   stack frame while the 68K00 stacks only three words.
2. The 68010 CPU detection is assumed to fail the original TOS too.
3. The correct video load timing is detected via the DCYCn signal.
   This is temporarily routed to an external pin. This signal must load 
   the shifter every 500ns in the monochrome mode.
4. A first try of emutos on a real hardware failed (no screen synchronisation).
   The reason could be the character sets located in the high address area
   of the 512K ROMs. The original hardware uses only 256K ROMs.
5. During the debugging a kernel panic is sometimes caused by address errors.
   To detect this behavior, set address trace of the signal tap analyzer to 
   the address vectors of the respective interrupts (do not forget, that the
   address on the address bus is half the value of the vectors due to the
   missing least significant address bit).

WF - 20080410.