!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!                 MorphOS Public Beta Version                  !!!
!!!             Copyright Ralph Schmidt, Frank Mariak            !!!
!!!                           2000                               !!!
!!!                                                              !!!
!!!            Backup your HDs before you do anything            !!!
!!!    Beta means...*NOT* finished...*MAY* have obvious Bugs     !!!
!!!       It`s meant for experienced developers and users        !!!
!!!                                                              !!!
!!!  Don`t make prejudgements about the finished product`s       !!!
!!!  stability.                                                  !!!
!!!                                                              !!!
!!!  If something doesn`t work the way you think it should work  !!!
!!!  please *NOTIFY* us through email or through bugforms at     !!!
!!!                                                              !!!
!!!                       www.morphos.de                         !!!
!!!                                                              !!!
!!!   It makes no sense to post bugs to usenet as we may         !!!
!!!   miss them, may cause misperceptions to normal users and    !!!
!!!   may cause unnecessary mud slinging and flame wars.         !!!
!!!                                                              !!!
!!!   And a last word....                                        !!!
!!!   This product is very complex. It has to emulate the 68k,   !!!
!!!   provide a new PPC/68k interface, several native drivers    !!!
!!!   and has to handle all kinds of unknown hardware and        !!!
!!!   software which may have all kinds of sideeffects, may      !!!
!!!   contain hidden bugs and we aren`t perfect either.          !!!
!!!   So don`t expect miracles about handling all your prefered  !!!
!!!   hardware and software combinations.                        !!!
!!!                                                              !!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 o Which Hardware should work and which doesn`t ?

   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
   !! You MUST read the <Hardware.txt> file before going on. !!
   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 o Does it need a different partition ?

   No. You can run it on your standard boot partition.
   But we are not reliable for any data loss if you do
   so.

 o What do i have to care for when i want to try it.

   o OS 3.5 users
     Add this to your startup-sequence

     c:version >NIL: "MorphOS"
     IF WARN
     C:SetPatch QUIET ; SKIPROMUPDATES "NCR scsi.device"
     ELSE
     C:SetPatch QUIET NONSD NOROMUPDATE
     ENDIF

     to avoid that it causes a reset and installs some
     messy drivers.

   o MorphOS contains PPC SFS 1.85 which is compatible to 1.84.
     So if you use a SFS partition better make sure you use the
     latest 68k version.

   o Install CyberGfx 5 as P96 drivers may run into
     gfx glitches caused by timing issues.
     Not to speak about the performance degration.

   o Install the new ppc 8n1 serial.device replacement
     because the old serial.device does NOT yet work.

   o If you use an Ariadne2 you must patch your ariadne
     driver to fix a synchronizing problem. Otherwise
     your network connection doesn`t really work.

   o Install ixemul.library.elf from the Ixemul archive
     *if* you use ixemul programs.
     68k ixemul.library crashes under MorphOS.

   o Remove system extensions like

     o every MMU toy like
       FastExec, QuickRom, rom2fast, VM, Enforcer, Mu#?...

                         DROP ALL THAT

       MorphOS doesn`t allow the 68040/68060.library to load
       so that should catch most MMU software but you never know.

     o WarpUP and programs or datatypes using it.
       MorphOS doesn`t allow the powerpc.library to load
       to avoid serious crashes.

     o executive or any other program which plays around
       with exec's internals.

     o Avoid unnecessary lowlevel system patches like 
       <copymemquicker> and <fblit>.
       They may collide and patch ppc code with slow 68k
       code.

     o poolmem
       May collide and patch ppc code with slow 68k
       code.

     o stackattack
       May cause real havoc

     o Be careful with MCP and simular system "enhancers".
       Some sane people call them "Multiple Crash Plugins".
       Be aware that all these patches may replace PPC system
       functions with slow 68k functions.

   o "Secure" system extensions are "Arq", ClickToFront, MagicMenu
     ToolManager, TWA, DynamiCache, NewMode, SwazInfo and if you
     know what you`re doing...also MFR.
     If you use ToolManager 2.1 instead of 3.0 you should update
     because the PPC icon.datatype speeds up newicon loading a lot.
      

   You can also make a startup which handles 68k and PPC
   mode this way.

    c:version >NIL: "MorphOS"
    if WARN 
       68k mode
       start the hacks
    endif

 o What is the demo limitation ?

   It only runs fast for roughly <30> minutes, then shows a requester
   which warns you and shortly afterwards it slows down to an A500
   level. I'm sure you'll enjoy the great old times:-)

 o How do i start MorphOS ?

   1) First check if you have the following roms

      o A4000
        Kickstart 40.68 or 40.70

      o A4000T
        Kickstart 40.70

      o A3000
        Kickstart 40.68 or 40.70

      o A1200
        Kickstart 40.68

      If not you can also overrule the rom by the command

      <kickstart=kick.A4000.40.68> which you must add to
      the <startup> script.

      IF YOU DON'T HAVE ONE OF THE ABOVE KICKSTARTS MORPHOS
      WON'T WORK.


   2) The std script is configurated for 38400 Baud *serial* debug output
      and the startup program itself gives output to the serial by <Verbose>.

                   The serial is *NOT* captured by sushi.

      If you don`t care for the startup debug output remove <Verbose>.
      If you have no serial terminal add <RamDebug> where you can get potential
      debugoutput after a crash by qstartup/debugramdump

   3) stop all kinds of hd activity.

   4) If you have a CyberstormPPC 68040 you
      probably have to set <ResetLevel=4> and do a manual reset
      (yes..by your hands:-)) after startup loaded everything and
      shows no activity for some time.

   5) Enter <startup> in the shell.

   6) If nothing happens for a while you MUST read startup.doc about
      <ResetLevel>.
      You should also set all kinds of debug options to determine where
      the problem is.

      HDebugFlags="Init Log"
      QDebugFlags="Init Log EmulMapping"
      EDebugFlags="InitResident"

      is a good start.*

      If you run debug output be aware that the emulation isn`t smooth
      as during debugoutput the exec task scheduling is disabled.


 o What should I do when it hangs during booting ?

   In this case please boot up with a fresh WBStartup, uncomment
   programs in the startup-sequence and user-startup until you
   found the trouble maker.
   Please notify us in such cases.

