[ Version 1.1 ]
2. The beginning
3. Adapt Startup-Sequence
4. Configure MorphOS
5. If MorphOS wont start
6. Installation success
Before starting with the actual guidance, i want to point out, that this guide will be kept as
generally as possible, but not 100%, because every system is individual. Means, it need not run
at everybody machine on sight!
Another point: If its getting to difficult, i really regret. The MOS-Installation isnt really
easy to realise. But i will try it nevertheless, to explain it as easy as possible, that everyone
can handle this. But i have to add, that a bit experience with Amiga is needed.
Its important, to have an 68040.library higher then 46.2 and quite a lot of memory, means, who has
less then 32 MB should better not start (MOS itself gulps 16MB). Furthermore the AmigaROM 3.1 is
needed (Version 40.68, incl. 40.70). It play no role, if this is in existant via the internal ROM
or a ROM-File. If its a File, it has to be added to Butterfly/extensions at Kickstart!
Without this ROM MorphOS wont start!
Maybe its also important to know, that MorphOS aims on OS3.1 compatibility, not on OS3.5 or 3.9,
although it runs with both of them.
From OS3.5 on: Regretfully in this Versions there are still problems with "Reaction" left, so it
might be, that when starting the Preferences in Sys:Prefs and change something there, the
Amiga-Emulation-Box (A/Box) of MOS immediately freezes.
Another point: dont be worried at the installation, no files will deleted, overridden or otherwise
changed. Improtant: Copy the files unchanged!
And dont worry, the copied files delete no others, they also dont disable the normal 68k-operating
in any way.
Concret: If a file is named
"blabla.elf", it will be copied as
"blabla.elf" and not
The beginning ...once there was a MorphOS Version 0.4...
To install the at this time actual (still unfortunately) MorphOS-Version (0.4),
MorphOS-Archiv from 15.02.2001 is needed first.
After the decrunching, it can be practically installed (via a
Installer-Script) wherever wanted. I take "Hd0:" as example.
Furthermore, inside the archive a program named Butterfly is located. This program is a tool to
configure and launch MorphOS. This file should be manually copied to
"Hd0:MorphOS" (because MorphOS was installed to "Hd0:").
Next, all files inside "hd0:MorphOS/Amigaextensions"
should be copied in the intended directories.
For example hd0:MorphOS/Amigaextensions/libs to LIBS:
(best archived using "copy hd0:MorphOS/Amigaextensions/libs/ ALL LIBS:").
Same for other directories. In addition:
"C:" (but isnt needed).
Now, all CGX-User should copy these files, too:
If BVision-Drivers are used, delete the CVision driver and the other way round. If both arent used,
delete both and use CGX-AGA Modes.
ah, and another thing: For all of you who feel unsure at those "copy-operations" or are extrem lazy
'typers', i have done a copy-script, which arranges the copy of these files. The Script is named
"Copy-Script" and needs to be copied to
"Hd0:MorphOS" and starts with
If all files were copied...then Part 1 is finished...
Now some needed changing on the Startup-Sequence is aimed.
Before "playing around" there, the production of a secure copy is strongly suggested!
(No worry, it has no effect to the 68k use!)
This changing causes, that native PPC-monitor-drivers are used, when MOS is started and the normal
68k-drivers when starting in normal 68k-Mode.
Following has to be inserted. Best is, to paste that directly after the Setpatch command.
Before "Version>NIL:" comes for the first time, enter Failat 21:
C:version >NIL: MorphOS
C:list >NIL: DEVS:Monitors/~(#?.info|VGAOnly|#?.elf) TO T:M LFORMAT "devs:Monitors/%s"
if EXISTS Devs:Monitors/CGXAGA
C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
Where normally this command can be found:
C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
simply set a ';' in front (causes the command not being executed)
; C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
Is this is done, ALL Patches should be removed or deactivated!!!
Those can disable, slow-down or crash MOS. The Startup-Sequence in its original state should be used.
Furthermore, all programs in "Sys:WBStartup" should be deactivated.
This means Tools like BPPC, MCP, installppclib...to be deactivate!!! (i dont care how you do it. Its
here also possible to set a semicolon in front, or use the next script)
Normally people want to continue with those patches, when using AOS, and want them being disabled
when MOS runs. This can be done with this script:
C:Version >NIL: MorphOS
(the used Patches..., eventually Setpatch with ROMUPDATE, if wanted)
(here nothing, eventually Setpatch NOROMUPDATE)
If Setpatch is taken inside depends on the use of the ROMUPDATE (AOS3.5/9) in the AOS-Mode and not
in MOS. But because of the fact, that this ROMUPDATE at MOS operating same, there is no need to
I want to give an example, of course:
C:Version >NIL: MorphOS
C:BPPCFix INSTALL >NIL:
There also a nice "trick" which can be used, to avoid a second boot to start MOS. The program
from the Aminet is needed for that. The program checks, if a mousebutton is pressed. This
can be used, that when a button is pressed, MOS starts directly without starting AOS first.
The script, which is inserted at the very beginning of the Startup-Serquence, can look this way:
IF $rc eq 1
The StartMOS-Skript is, of course, available as file.
Copy this one to "MorphOS/MorphOS".
This script also includes only standard adjustments, the content looks like the following:
startup hal="hal.rom" Kernel="kernel.rom" Amiga="amiga.rom" module="module.rom"
If the Startup-Sequence was changed...then part2 was done!...
Now MOS should be eventually configured by the Butterfly-Tool. If neither a BVision nor a CVision
is used, its strongly needed to mark "DisableCVPPC", otherwise MorphOS will/could crash!
On the other hand, nothing further should be changed. Now MorphOS can be principally launched.
Important: The ROM must not be kicked. The original AmigaROM has to be used, you can check it with
"Version exec.library", the result should be
Now, MorphOS should be started!!!
Beginning from this point more or less solubly Problems can emerge...Good Luck!!!
When the Computer boots now, the PowerLED will blinking, slowly and always again. This means MorphOS
is initialized !!!
To my knowledge, short after MOS was started using a BVision, the standard 31kHz-signal (the
Bootscreen) will be displayed (as usual). When the 31kHz signal normally comes, but not with MOS,
it means that it already crashed or
"DisableCVPPC" was activated. That can mean, that a wrong ROM
or a kicked ROM was used. If the "DisableCVPPC" function was activated, simply wait what happens.
If nothing happens, means neither the LED is blinking fast nor the Harddisk is rumbling, then it
means, MorphOS has crashed. This can, again, indicate a wrong ROM or someone played with the MorphOS
adjustments ;) .
If the signal appears, this is a good omen. After a couple of seconds, if you hear the Harddisk, the
PowerLED begins to flicker. This means it boots. Short after that a picture should displayed and
soon after that the Workbench appears. MorphOS runs!
If MorphOS runs, skip this part!
If neither the picture nor the Workbench appears, something has crashed. Now the real fun begins ;)
There might be several reasons, why MOS crashed , but a single one might be enough..., that why the
problem has to be searched.
OK now, if you use a Graphicboard, the Amiga should be connected to a TV in addition (via the
standard Chinch-Connector or the TV-Adapter).
Now try to get into the Boot-Menu (or however its named :)), with (as usual) holding both
Mousebuttons pressed, until it appears. Arrived there, simply choose
"Boot without Startup-Sequence",
causes the Startup-Sequence not being executed at startup. Pushing this button, firstly brings you
inside the shell, where something like "MorphOS - Emulation by Ralph Schmidt" (or similar) is written.
Now try to manually boot the WB. Either do a small script before, or enter it...
It should look approximately this way:
copy Envarc: ALL ram:env
Assign env: ram:env
Makedir Ram:t Ram:Clipboards
Assign T: ram:
Assign Clips: ram:Clipboards
Setpatch NOROMUPDATE (firstly without)
Dann mit Loadwb die WB starten.
Then to "Devs:Monitors/" and the start needed drivers (example: BVisionppc.elf).
If this wont crash (a bug-report logfile (MorphOS-Log) would be displayed, if it crashes), then its known that
it no depends on this.But, should this crash and all libraries (those inside
"MorphOS/Cybergfxppc") were copied correctly and
"DisableCVPPC"-funktion is unchecked at startup, then I regretfully cant help
you further...Sorry, please notify in the IRC-Chat
irc.vapor.com #morphos - eventually those persons could help.
But continuing, if these drivers didnt fail...now start the Tool
a screen, which is supported by this driver (in this case a BVisionPPC-Screenmode), if its opened and
works correctly, then its known, that the drivers are working and the problem lies elsewhere.
If MOS crashes in this place, either the display freezes or a "MorphOS-Log"
again, please consult irc.vapor.com #morphos :(
So, this was a possibility to check if the Monitor driver works correctly.
In the case, the Amiga still not willing to boot "normally", try to boot (if its ever in use) with
Should it go better then, willy-nilly dispense with it :(
But if wanted to know this for 100%, then start MOS Startup-Sequence and easily enter Setpatch, hold
both mouse buttons and wait. If the Boot-Menu appears, start without Startup-Sequence again...
back in the Shell enter 'Setpatch', a list should appear then, showing if the RomUptdate was
So its possible to check this. Reffering to a test in the AmigaPlus (german Amiga-print magazin) it
runs with OS3.9, to my knowledge it also runs with OS3.5, at least it should runs with both of them.
Regertfully theres a problem with certain A4000-Boards from Micronik. There its needed to play
around with the "Restlevel". Regertfully i cant say in general which one,
because I have heard various (resetlevel 5, 7...)
Another tip: Increase the Stack at the beginning of the Startup-Sequence to 500.000
(paste "Stack 500000" at the very beginning), this could also help...
If things were observed MOS must run. ;)
Should MOS nevertheless not start, please e-mail me and send me his Config and his Startup-Sequence.
I dont know if i can help further, but its obviously possible, that somebody did a tiny mistake and
didnt noticed it.
But there yet another little trick, which could help eventually.
Having a Snooper program (like SnoopDOs), so it can be started in the Shell, before the
Startup-Sequence is executed. Is the program running, then it eventually can be seen wheres it was
I will offer
to help and understanding.
If the Installion succeeded...
Now lets say, almost 70% are done.
Now the part is coming, where it need to find out, what runs with MOS and what runs not. In other
words, all things deleted from the Startup-Sequence, can now being add (exept the Patches).
The adding should be done "piece by piece", in order to approximately know, what the exeption caused
(better: on which program it lay down). Is this also done, some adjustments on the MOS-Prferences
(from AmigaOS-Mode) should eventually be prepared. "DisableLED" causes that the PowerLED isnt
blinking in MOS-Mode anymore, but the sounds gets correct then.
So, now it can be started to install MOS-Tools...Mui-PPC, YAM-PPC...
find most of them at
www.morphos.de... Viel Spaß!
... Have Fun!
All of you, who didnt get this "thing" running, i can only say, notify me or wait for the next public
release...if it was due to the comprehension of this guidance, then i feel sorry...i cant do it
All of you, who got it, i can only gratulate..it wasnt easy :) If you test MOS now and you dont like it
on the first view, dont be disappointed too much..its just a Beta Version 0.4.
I hope you had fun with the installation ... i had it too ;)
On this place i would like to express my gratitude to David S. and
Thorsten S. for their help and co-operation!
Gregor `McGreg` Galwas
roughly translated to english by 'anonymer MOS-Fan'
Under the following link you'll find an installation guide
to MorphOS 0.4beta. Everybody should be able to install
the public beta version of MorphOS on his system after
reading this guide. If you still have any questions you'll
find more information within the help area.
>>There it is!