Important additional information:
----------------------------------

The following information is not included in the manual, but should 
nevertheless be read carefully. It may be a good idea to print it out.

* IMPORTANT!!! If you use programs that interact with Kobold 2 or 2.5 and you
want to use them with Kobold 3, please use the conversion program KB2TOKB3.TTP,
which you will find in the folder KOBOLD35 / TOOLS / KB2TOKB3 including a manual,
that allows you to patch these programs for the new Kobold.

* Kobold automatically saves all settings when you exit it. If you have
  experimented a bit and do not want Kobold to save the modified settings, just
  hold SHIFT when clicking the close button or exit Kobold with CTRL-SHIFT-Q.

* If Kobold does not find a KOBOLD_3.INF file when calling it (ie on the very
  first call), Kobold tries to find out the names of the connected drives. This
  may possibly lead to an error message if a registered device is not switched
  on or connected. However, this does not occur with further Kobold calls, as
  Kobold then uses only the names from its own parameter file.

* The software suite includes a backup program for backup copies on floppy disks
  or any other exchangeable media (removable disks, Bernoulli drives, etc.). It
  simply creates a job that can then be processed by KOBOLD. Some users have
  requested a backup option after such a procedure. This program was developed
  by Bernd Schieferdecker, who kindly allowed us to add it to the KOBOLD disk.
  KAKTUS does not support this product! If you have any problems or requests,
  please contact the author directly (see instructions), who of course will be
  glad to take a donation if you like the program.

* If you add new drives - e.g. start a ramdisk - you can update the drive list
  in a running Kobold by selecting '?' again or add 'ESC' (or 'Shift-ESC') to
  the newly added drive. If you install such a ramdisk with the EXECUTE job
  processing command, the new drive will automatically be added to the list of
  available drives and can be addressed immediately after the EXECUTE command
  completes.

* Under standard TOS versions, it is not actually possible to start another
  program from an Accessory. When executing the EXECUTE job command in accessory
  mode, KOBOLD can do this only with tricks that intrude very deeply into the
  system. With a heavy heart, we have decided to do this in this way, rather than
  simply blocking the command in Accessory mode completely, because the trick
  works in most cases with programs (Packer, Tree Check, etc.) without any
  problems. However, we can not guarantee that this works fine under all
  configurations. If your system hangs or bombs while running a program from the
  Accessory option, we can not help you. Actually it should work out though.
  In multi-processing environments like Mag! C or MultiTOS this is not a
  problem! It is not forbidden to start programs from an Accessory.

* When using a preemptive multitasking-system (e.g. MultiTOS, Mag!X 2.0), 
  disk formatting may take a little longer than in a single-tasking 
  environment. Sometimes task-switching may occur before the next track is 
  stepped to - this will force another revolution of the disk before the 
  next track can be formatted.

* The maximum formatting speed of 35 seconds for a double-sided disk can 
  only be achieved with 'Verify' set to 'off'.

* HD-switching on a Falcon is preset to 'STE/TT' because this works in 
  exactly the same way on all these models.

* If you own an HD or ED upgrade kit and want to do HD/ED switching 
  automatically ('automatic' in the 'formatting/special' dialog), a cookie 
  has to be set to inform Kobold that your operating system supports these 
  formats. If you have any problems with this option, it could be that your 
  HD/ED software does not set the corresponding cookies. In this case you 
  will find two programs for this purpose in the TOOLS folder. Please refer 
  to COOKIES.TXT for further information.

* If Kobold is run as an accessory under an operating system which allows 
  you to change  the screen resolution (e.g. TOS 4.0x on the Falcon), the 
  option 'reserve memory' in the memory configuration dialog should not be 
  set. It could otherwise prevent the system from allowing a resolution 
  change.

* Sometimes users ask us questions concerning the error message 'Bad data 
  on disk C:' or similar. This messsage is not created by Kobold (note the 
  difference in appearance between the simple TOS alert and the Kobold 
  alerts!), but comes from the operating system or harddisk driver. This 
  message means that a hardware error has been detected - this may be 
  attributable to either long or loose cables or alternatively a drive 
  which is unable to read/write a specific sector (due to serious internal 
  problems). Such a problem cannot be caused by Kobold. KOBOLD IS NOT ABLE 
  TO PHYSICALLY DESTROY YOUR HARDDISK! Kobold never writes to a bootsector 
  and cannot reach the vitally important root sector! If for any reason 
  your harddisk is not addressable, it cannot be a consequence of any 
  copying you have done using Kobold!

  One relatively frequent problem with hard disks that may render them 
  unaddressable is the much-feared 'headcrash'. In this case the read/write 
  head (hovering only a few micrometers above the disk surface) crashes 
  against a dust particle, thereby scratching the surface and destroying 
  the data on the disk. Removeable hard disks which are not 100 percent 
  airtight are especially prone to headcrashes - they easily become dirty 
  when used in a dusty or smokey room.

  If you own a SCSI-harddisk and an unreadable sector is found, this is 
  usually reported via an alert. If you select 'try again' here, attempting 
  to access it a second time, the unreadable sector will be replaced by one 
  of a set of reserved sectors. The original data will of course be lost, 
  and this new sector will usually contain only zeros or a formatting 
  test-pattern. You can recognise this if you see truncated files or 
  directories. Part of the file will be filled up with 'UUUUUU...' (whereby 
  the letter 'U' is equivalent to hexdecimal 55, the usual formatting 
  test-pattern). The directory will contain several files all named 
  'UUUUUUUU.UUU'. If you see this effect you should now know the reason!

  If such problems occur frequently, your harddisk has probably suffered a 
  minor headcrash (a major headcrash would have prevented the drive from 
  working altogether). You should be prepared to lose the complete 
  harddisk within a few days! After all bad sectors have been replaced with 
  reserved sectors, the drive will carry on reporting more and more 'bad 
  data' errors because the dust-particle responsible for the damage is 
  still in there doing harm to the surface of your disk. These bad sectors 
  are no longer accessable even when you click 'try again' because they 
  cannot be replaced anymore. You can now use the program 'CORRECT' to test 
  the sectors. You should seldom find any new bad sectors on a SCSI-device 
  because of this replacement - at this point CORRECT will find all the 
  irreplaceable bad sectors. This is the time to backup all the data you 
  can because the harddisk will soon become totally unusable!
