First aid for problems with WarpOS
----------------------------------

- Problem:
  The powerpc.library can't be opened. The WarpUp demos don't work at
  all and eventually cause error messages like 'can't open
  powerpc.library'.

- Solution:
  The powerpc.library V8 or higher can only be opened if the ppc.library
  from Phase5 isn't active. This means, if WarpOS should be used it is
  required to make sure that no PowerPC applications are running which
  use the ppc.library.

  It is important to note, that even programs, which are running in the
  background, can use the ppc.library. For example some versions of the
  graphics card software 'CyberGraphX' exist which use the ppc.library.
  In this case it is necessary to install a version of CyberGraphX
  without ppc.library support if WarpOS should be used.


- Problem:
  The powerpc.library can't be opened although no application was ever
  started which could have opened the ppc.library.

- Solution:
  In this case it's possible that the ppc.library is opened at boot time,
  then it is probably located in nonvolatile memory.

  The best solution would be to make un upgrade of the nonvolatile memory
  so that the ppc.library is not opened anymore at boot time. The hardware
  and software should continue working properly. This is the only way
  that WarpOS can integrate itself in a completely system compliant way.

  If no upgrade is available which fixes these problems then you should
  set the environment variable 'powerpc/Terminator' to a non-null value.
  WarpOS then tries to remove the ppc.library and related resources by
  hand. If this causes problems please tell us so that we can develop
  further terminators to fix these problems.



- Problem:
  Every demo which opens the powerpc.library, crashes.

- Solution:
  - On systems without PPC board, the env variable 'noPPC' must
    absolutely be set to a value unequal zero. After that, all
    demos which are able to run without PPC (but which try to
    open the powerpc.library) should run.



- Problem:
  If a demo is started several times in the shell, crashes occur.

- Solution:
  The problem can occur in conjunction with the WShell, which frees
  signals that were not allocated by itself. The problem can be
  solved with the env variable 'earlyterm'. If this variable is set
  to 1, the problems should be solved. Restrictions: no global settings
  can be made in the shell, which could affect the PPC, so the tools
  'stackppc' and 'changemmu' don't work anymore. To set the PPC stack
  size, you have to use the command 'stack' (the PPC stack is about
  double the stack size of the 68K stack).


- Problem:
  Since version 1.6 the voxelspace demo doesn't work with Picasso96
  anymore.

- Solution:
  The voxelspace supports the OS3.0 multibuffering for Picasso96
  since V1.6 to achieve a better display quality. Therefore it is
  required that an appropriate new version of Picasso96 is installed.


- Problem:
  When those demos are started, a screen mode requester appears which
  is empty.

- Solution:
  This effects occurs if a CyberGFX emulation for AGA is active. In this
  case the demos have to be started with the 'PAL' parameter.