1. The core is equiped with 14MB RAM. During the boot process of TOS 2.06
   there is a memory test detecting 4MB RAM. The working portion of 14MB
   RAM is up to now not confirmed.
2. The IDE interface features Master/Slave operation. There was no way
   to operate a SD-Card configured as master and a 2.5" IDE hard drive
   configured as slave up to now. This seems not to be caused by the core.
3. The Suska-III-C core does sometimes not start correctly after power on.
   This effect seems to have something to do with the configuration of the
   FPGA and perhaps with the initialisation process of the SD-RAMs. Once
   started, the core runs fine. Workaround: switch off and on again.
4. 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.
5. The 68010 CPU detection is assumed to fail the original TOS too.
6. 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.
7. 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.
8. 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).
9. The Joyports seems to have a wrong wiring (wrong directions when Joysticks are used).
10.eMuTos version 0.8.3 do not start with PS/2 keyboard and PS/2 mouse. An original
     keyboard is required.
11.Fixed: The Printer port sometimes does not work as input.
12.Using a 'Megafile 60' at the ACSI port formated with one partition with 65.xxMB
     causes a TOS ERROR #35 when starting programs. Workaround: use two smaller
     partitions with 31MB each or so. The exact configuration of the Suska-III-C:
     Starting hddriver 8.23 from floppy drive A. The CF-Card is drive C and the 'Mega-
     file 60' is drive D.
13.Using HDDRIVER's AUTOPARK accessory version 8.23 causes the TOS2.06 system hang when
     selecting the Desktop info menu. Workaround: rename or delete the accessory.