<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://library.morph.zone/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Korni</id>
		<title>MorphOS Library - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://library.morph.zone/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Korni"/>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/Special:Contributions/Korni"/>
		<updated>2026-04-28T04:00:39Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4211</id>
		<title>Hardware Compatibility</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4211"/>
				<updated>2021-07-08T12:09:47Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Mice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div id=&amp;quot;hardwareCompatibility&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Official Information ==&lt;br /&gt;
An official list of supported hardware is available at the [http://www.morphos-team.net/hardware MorphOS homepage] and a list of complete computer setups based on the official information is available [[Supported_Computers|here]].&lt;br /&gt;
&lt;br /&gt;
== User Provided Reports ==&lt;br /&gt;
This is a list of hardware compatibility reported by users. It isn't, by any means, a complete list of hardware compatibility, but just individual findings by users that may contain user errors or obsolete information. Please report your findings in [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.&lt;br /&gt;
&lt;br /&gt;
'''Note''': This list will only be as complete and comprehensive if you, a MorphOS user, report the hardware you have used in conjunction with MorphOS successfully, or unsuccessfully, for it to be included for others to gain the benefit from, and if necessary, possible and/or realistic, for further testing to be undertaken to establish if the hardware can be made functional for all users to enjoy with MorphOS. &lt;br /&gt;
&lt;br /&gt;
This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library. Where possible the lists will be maintained in alphabetical order (A-Z), but if you find any errors please [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 let us know] so correction(s) can be made.&lt;br /&gt;
&lt;br /&gt;
=== Game Controllers ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th class=&amp;quot;type&amp;quot;&amp;gt;USB Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;driver&amp;quot;&amp;gt;USB driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;8bitdo SFC30 Pro Controller&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;8bitdo SN30 Pro Controller&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid, xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wired&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=34 BIMONK Wired Gaming Controller]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=70 BIMONK Wireless Gaming Controller]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech Rumble Pad wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=85 Mcbazel Dobe Mini Arcade Stick]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.onyxsoft.se/joydivision.html OnyxSoft JoyDivision] DB9-USB adapter&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Connect an Atari style joystick to USB&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.retronicdesign.com/en/ Retronic Design] DB9-USB adapter&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Connect an Atari style joystick to USB&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Saitek P380 Dual Analog wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td style=&amp;quot;color:red;&amp;quot;&amp;gt;Sony Dualshock 3 (PS3)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;not supported&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sony Dualshock 4 (PS4)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Competition Pro USB&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Xeox Gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Thrustmaster 360 Modena Pro Racing Wheel&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;needs some setup for the ranges from the Poseidon prefs&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox 360 wired and wireless pads&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wireless supported via PC adapter&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox One gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wired only&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Keyboards ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%;&amp;quot;&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Apple A1016 Wireless BlueTooth&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Apple Magic Keyboard (Version 1)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Cooler Master MS210/MK110&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software needed for full RGB control and Fn multimedia keys do work out of the box&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Ducky Zero Keyboard DK2108SZ&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech UltraX Premium&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Wired Keyboard 600&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Model X880609-600&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Wireless 900 Keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Mouse+kb combo&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E6300 Ultra-Slim BT keyboard for iPad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E9050 Wireless Compact Ultra-Slim Keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E2710 Wireless Nano-USB Keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xenta Super Compact Black Wired Keyboard (RK 107)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
① requires a machine which supports paired BT input devices, like Mac mini&lt;br /&gt;
&lt;br /&gt;
=== Mice ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;A-Eon Technology MX-1000-1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Dacota Gaming Serpent Mouse&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Wired, 809024&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M180&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M185&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M220 Silent&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M330 Silent&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech T-RB22 Wireless Trackball&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech G203&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software control over RGB, DPI&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Labtec Optical Mouse 800&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Compact Optical Mouse 500&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Trackball Explorer v1.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;PS2&amp;gt;USB adapter required&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Wireless Mouse 900&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Mouse+kb combo&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td style=&amp;quot;color:red;&amp;quot;&amp;gt;Microsoft Wireless Mouse 4000&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Not working&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Razer Viper Mini&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software control over RGB, DPI&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sharkoon Skiller SGM2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software needed for RGB and DPI settings, side buttons don't work&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Targus AMU3102EU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=82 TENMOS K6 Wireless Gaming Mouse]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== MIDI Devices ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Yamaha PSR-433 keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Printers ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;TurboPrint (Printer) driver&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;PostScript (Printers) driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;HP 2500 Color LaserJet&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DE],  [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ES],  [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FR],  [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz IT]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Konica Minolta Magicolor 4650&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;M4650PX.ppd&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Lexmark E342n&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;HP_LaserJet5series&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://support.lexmark.com/index?productCode=LEXMARK_E340&amp;amp;segment=SUPPORTproductCode%3D&amp;amp;viewlocale=pt_BR&amp;amp;page=content&amp;amp;searchid=1378996742336&amp;amp;actp=search&amp;amp;id=DR13234&amp;amp;locale=EN&amp;amp;userlocale=EN_US Lexmark_E342n_en.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xerox 3225 Workcentre&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Reported to work with PS&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;HP Color LaserJet MFP M274n&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hp-color_laserjet_mfp_m274-ps.ppd&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Scanners ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Epson Perfection 1640SU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Including recent support for its ADF (Automatic Document Feeder).&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== USB Audio Devices ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Output&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Input&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;&amp;quot;[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]&amp;quot; USB sound card&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.aliexpress.com/item/Vikings-City-Bluetooth-Adapter-APT-X-Low-Latency-Driver-Free-Plug-n-Play-BT-4-1/32828525027.html ANTTUS Gaming USB Bluetooth Adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;C-Media soundcard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Corsair Void Elite Surround adapter/headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Headset with 3.5mm jack and a USB adapter. Analog volume control.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Corsair Void RGB Elite headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;FX-Audio- DAC-X3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.12&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;N/A&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Griffin iMic&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.inline-info.com/de/produkte/eingabe-ausgabe/kopfhoerer-verstaerker/9909/inline-ampusb-hi-res-audio-hifi-dsd-kopfhoerer-verstaerker-usb-digital-audio-konverter-384khz/32-bit InLine AmpUSB Headphone Amplifier]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;N/A&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech H540 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sony PlayStation Gold 7.1 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Works in stereo.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Only front output tested&amp;lt;/tD&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Steelseries Arctis 7 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Turtle Beach Stealth 520 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4210</id>
		<title>Hardware Compatibility</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4210"/>
				<updated>2021-07-08T12:09:30Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Mice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div id=&amp;quot;hardwareCompatibility&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Official Information ==&lt;br /&gt;
An official list of supported hardware is available at the [http://www.morphos-team.net/hardware MorphOS homepage] and a list of complete computer setups based on the official information is available [[Supported_Computers|here]].&lt;br /&gt;
&lt;br /&gt;
== User Provided Reports ==&lt;br /&gt;
This is a list of hardware compatibility reported by users. It isn't, by any means, a complete list of hardware compatibility, but just individual findings by users that may contain user errors or obsolete information. Please report your findings in [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.&lt;br /&gt;
&lt;br /&gt;
'''Note''': This list will only be as complete and comprehensive if you, a MorphOS user, report the hardware you have used in conjunction with MorphOS successfully, or unsuccessfully, for it to be included for others to gain the benefit from, and if necessary, possible and/or realistic, for further testing to be undertaken to establish if the hardware can be made functional for all users to enjoy with MorphOS. &lt;br /&gt;
&lt;br /&gt;
This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library. Where possible the lists will be maintained in alphabetical order (A-Z), but if you find any errors please [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 let us know] so correction(s) can be made.&lt;br /&gt;
&lt;br /&gt;
=== Game Controllers ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th class=&amp;quot;type&amp;quot;&amp;gt;USB Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;driver&amp;quot;&amp;gt;USB driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;8bitdo SFC30 Pro Controller&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;8bitdo SN30 Pro Controller&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid, xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wired&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=34 BIMONK Wired Gaming Controller]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=70 BIMONK Wireless Gaming Controller]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech Rumble Pad wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=85 Mcbazel Dobe Mini Arcade Stick]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.onyxsoft.se/joydivision.html OnyxSoft JoyDivision] DB9-USB adapter&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Connect an Atari style joystick to USB&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.retronicdesign.com/en/ Retronic Design] DB9-USB adapter&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Connect an Atari style joystick to USB&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Saitek P380 Dual Analog wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td style=&amp;quot;color:red;&amp;quot;&amp;gt;Sony Dualshock 3 (PS3)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;not supported&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sony Dualshock 4 (PS4)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Competition Pro USB&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Xeox Gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Thrustmaster 360 Modena Pro Racing Wheel&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;needs some setup for the ranges from the Poseidon prefs&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox 360 wired and wireless pads&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wireless supported via PC adapter&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox One gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wired only&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Keyboards ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%;&amp;quot;&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Apple A1016 Wireless BlueTooth&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Apple Magic Keyboard (Version 1)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Cooler Master MS210/MK110&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software needed for full RGB control and Fn multimedia keys do work out of the box&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Ducky Zero Keyboard DK2108SZ&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech UltraX Premium&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Wired Keyboard 600&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Model X880609-600&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Wireless 900 Keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Mouse+kb combo&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E6300 Ultra-Slim BT keyboard for iPad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E9050 Wireless Compact Ultra-Slim Keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E2710 Wireless Nano-USB Keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xenta Super Compact Black Wired Keyboard (RK 107)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
① requires a machine which supports paired BT input devices, like Mac mini&lt;br /&gt;
&lt;br /&gt;
=== Mice ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;A-Eon Technology MX-1000-1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Dacota Gaming Serpent Mouse&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Wired, 809024&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M180&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M185&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M220 Silent&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M330 Silent&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech T-RB22 Wireless Trackball&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech G203&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software control over RGB, DPI&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Labtec Optical Mouse 800&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Compact Optical Mouse 500&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Trackball Explorer v1.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;PS2&amp;gt;USB adapter required&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Wireless Mouse 900&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Mouse+kb combo&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td style=&amp;quot;color:red;&amp;quot;&amp;gt;Microsoft Wireless Mouse 4000&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Not working&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td style=&amp;quot;color:red;&amp;quot;&amp;gt;Razer Viper Mini&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software control over RGB, DPI&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sharkoon Skiller SGM2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software needed for RGB and DPI settings, side buttons don't work&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Targus AMU3102EU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=82 TENMOS K6 Wireless Gaming Mouse]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== MIDI Devices ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Yamaha PSR-433 keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Printers ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;TurboPrint (Printer) driver&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;PostScript (Printers) driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;HP 2500 Color LaserJet&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DE],  [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ES],  [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FR],  [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz IT]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Konica Minolta Magicolor 4650&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;M4650PX.ppd&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Lexmark E342n&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;HP_LaserJet5series&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://support.lexmark.com/index?productCode=LEXMARK_E340&amp;amp;segment=SUPPORTproductCode%3D&amp;amp;viewlocale=pt_BR&amp;amp;page=content&amp;amp;searchid=1378996742336&amp;amp;actp=search&amp;amp;id=DR13234&amp;amp;locale=EN&amp;amp;userlocale=EN_US Lexmark_E342n_en.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xerox 3225 Workcentre&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Reported to work with PS&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;HP Color LaserJet MFP M274n&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hp-color_laserjet_mfp_m274-ps.ppd&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Scanners ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Epson Perfection 1640SU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Including recent support for its ADF (Automatic Document Feeder).&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== USB Audio Devices ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Output&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Input&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;&amp;quot;[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]&amp;quot; USB sound card&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.aliexpress.com/item/Vikings-City-Bluetooth-Adapter-APT-X-Low-Latency-Driver-Free-Plug-n-Play-BT-4-1/32828525027.html ANTTUS Gaming USB Bluetooth Adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;C-Media soundcard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Corsair Void Elite Surround adapter/headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Headset with 3.5mm jack and a USB adapter. Analog volume control.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Corsair Void RGB Elite headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;FX-Audio- DAC-X3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.12&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;N/A&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Griffin iMic&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.inline-info.com/de/produkte/eingabe-ausgabe/kopfhoerer-verstaerker/9909/inline-ampusb-hi-res-audio-hifi-dsd-kopfhoerer-verstaerker-usb-digital-audio-konverter-384khz/32-bit InLine AmpUSB Headphone Amplifier]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;N/A&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech H540 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sony PlayStation Gold 7.1 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Works in stereo.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Only front output tested&amp;lt;/tD&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Steelseries Arctis 7 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Turtle Beach Stealth 520 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4209</id>
		<title>Hardware Compatibility</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4209"/>
				<updated>2021-07-08T12:02:20Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Game Controllers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div id=&amp;quot;hardwareCompatibility&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Official Information ==&lt;br /&gt;
An official list of supported hardware is available at the [http://www.morphos-team.net/hardware MorphOS homepage] and a list of complete computer setups based on the official information is available [[Supported_Computers|here]].&lt;br /&gt;
&lt;br /&gt;
== User Provided Reports ==&lt;br /&gt;
This is a list of hardware compatibility reported by users. It isn't, by any means, a complete list of hardware compatibility, but just individual findings by users that may contain user errors or obsolete information. Please report your findings in [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.&lt;br /&gt;
&lt;br /&gt;
'''Note''': This list will only be as complete and comprehensive if you, a MorphOS user, report the hardware you have used in conjunction with MorphOS successfully, or unsuccessfully, for it to be included for others to gain the benefit from, and if necessary, possible and/or realistic, for further testing to be undertaken to establish if the hardware can be made functional for all users to enjoy with MorphOS. &lt;br /&gt;
&lt;br /&gt;
This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library. Where possible the lists will be maintained in alphabetical order (A-Z), but if you find any errors please [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 let us know] so correction(s) can be made.&lt;br /&gt;
&lt;br /&gt;
=== Game Controllers ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th class=&amp;quot;type&amp;quot;&amp;gt;USB Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;driver&amp;quot;&amp;gt;USB driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;8bitdo SFC30 Pro Controller&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;8bitdo SN30 Pro Controller&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid, xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wired&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=34 BIMONK Wired Gaming Controller]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=70 BIMONK Wireless Gaming Controller]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech Rumble Pad wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=85 Mcbazel Dobe Mini Arcade Stick]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.onyxsoft.se/joydivision.html OnyxSoft JoyDivision] DB9-USB adapter&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Connect an Atari style joystick to USB&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.retronicdesign.com/en/ Retronic Design] DB9-USB adapter&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Connect an Atari style joystick to USB&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Saitek P380 Dual Analog wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td style=&amp;quot;color:red;&amp;quot;&amp;gt;Sony Dualshock 3 (PS3)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;not supported&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sony Dualshock 4 (PS4)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Competition Pro USB&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Xeox Gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Thrustmaster 360 Modena Pro Racing Wheel&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;needs some setup for the ranges from the Poseidon prefs&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox 360 wired and wireless pads&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wireless supported via PC adapter&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox One gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wired only&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Keyboards ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%;&amp;quot;&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Apple A1016 Wireless BlueTooth&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Apple Magic Keyboard (Version 1)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Cooler Master MS210/MK110&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software needed for full RGB control and Fn multimedia keys do work out of the box&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Ducky Zero Keyboard DK2108SZ&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech UltraX Premium&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Wired Keyboard 600&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Model X880609-600&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Wireless 900 Keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Mouse+kb combo&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E6300 Ultra-Slim BT keyboard for iPad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E9050 Wireless Compact Ultra-Slim Keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E2710 Wireless Nano-USB Keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xenta Super Compact Black Wired Keyboard (RK 107)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
① requires a machine which supports paired BT input devices, like Mac mini&lt;br /&gt;
&lt;br /&gt;
=== Mice ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;A-Eon Technology MX-1000-1&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Dacota Gaming Serpent Mouse&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Wired, 809024&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M180&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M185&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M220 Silent&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M330 Silent&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech T-RB22 Wireless Trackball&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech G203&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software control over RGB, DPI&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Labtec Optical Mouse 800&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Compact Optical Mouse 500&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Trackball Explorer v1.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;PS2&amp;gt;USB adapter required&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Microsoft Wireless Mouse 900&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Mouse+kb combo&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td style=&amp;quot;color:red;&amp;quot;&amp;gt;Microsoft Wireless Mouse 4000&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Not working&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sharkoon Skiller SGM2&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software needed for RGB and DPI settings, side buttons don't work&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Targus AMU3102EU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.morphos-store.com/product_info.php?products_id=82 TENMOS K6 Wireless Gaming Mouse]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== MIDI Devices ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Yamaha PSR-433 keyboard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Printers ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;TurboPrint (Printer) driver&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;PostScript (Printers) driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;HP 2500 Color LaserJet&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DE],  [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ES],  [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FR],  [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz IT]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Konica Minolta Magicolor 4650&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;M4650PX.ppd&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Lexmark E342n&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;HP_LaserJet5series&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://support.lexmark.com/index?productCode=LEXMARK_E340&amp;amp;segment=SUPPORTproductCode%3D&amp;amp;viewlocale=pt_BR&amp;amp;page=content&amp;amp;searchid=1378996742336&amp;amp;actp=search&amp;amp;id=DR13234&amp;amp;locale=EN&amp;amp;userlocale=EN_US Lexmark_E342n_en.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xerox 3225 Workcentre&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Reported to work with PS&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;HP Color LaserJet MFP M274n&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.15&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hp-color_laserjet_mfp_m274-ps.ppd&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Scanners ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Epson Perfection 1640SU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Including recent support for its ADF (Automatic Document Feeder).&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== USB Audio Devices ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Output&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Input&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;&amp;quot;[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]&amp;quot; USB sound card&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.aliexpress.com/item/Vikings-City-Bluetooth-Adapter-APT-X-Low-Latency-Driver-Free-Plug-n-Play-BT-4-1/32828525027.html ANTTUS Gaming USB Bluetooth Adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;C-Media soundcard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Corsair Void Elite Surround adapter/headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Headset with 3.5mm jack and a USB adapter. Analog volume control.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Corsair Void RGB Elite headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;FX-Audio- DAC-X3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.12&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;N/A&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Griffin iMic&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.inline-info.com/de/produkte/eingabe-ausgabe/kopfhoerer-verstaerker/9909/inline-ampusb-hi-res-audio-hifi-dsd-kopfhoerer-verstaerker-usb-digital-audio-konverter-384khz/32-bit InLine AmpUSB Headphone Amplifier]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;N/A&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech H540 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.14&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sony PlayStation Gold 7.1 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Works in stereo.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Only front output tested&amp;lt;/tD&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Steelseries Arctis 7 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Turtle Beach Stealth 520 headset&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.13&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4051</id>
		<title>Applications/VNCServer</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4051"/>
				<updated>2019-08-03T19:12:06Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Description ==&lt;br /&gt;
Remote access server allowing clients to connect using the VNC protocol.  &lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
=== Autostart ===&lt;br /&gt;
&lt;br /&gt;
Add to &amp;lt;nowiki&amp;gt;S:Network-User-Startup&amp;lt;/nowiki&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Run &amp;gt;NIL: SYS:Applications/VNCServer/VNCServer&lt;br /&gt;
&lt;br /&gt;
Once started VNCServer will be available in the Exchange ([[Utilities/Commodities#Exchange]]).&lt;br /&gt;
&lt;br /&gt;
=== Without GFX card ===&lt;br /&gt;
&lt;br /&gt;
Copy Virtual driver with its icon (MOSSYS:Storage/Devs/Virtual) to SYS:Devs/Monitors/.&lt;br /&gt;
Edit its icon information to enable wanted screenmodes.&lt;br /&gt;
&lt;br /&gt;
== Screenshot ==&lt;br /&gt;
: [[File:MorphOS3_jPV_Vncserver.png]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4050</id>
		<title>Applications/VNCServer</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4050"/>
				<updated>2019-08-03T19:10:54Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Description ==&lt;br /&gt;
Remote access server allowing clients to connect using the VNC protocol.  &lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
=== Autostart ===&lt;br /&gt;
&lt;br /&gt;
Add to &amp;lt;nowiki&amp;gt;S:Network-User-Startup&amp;lt;/nowiki&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Run &amp;gt;NIL: SYS:Applications/VNCServer/VNCServer&lt;br /&gt;
&lt;br /&gt;
Once started VNCServer will be available in the Exchange ([[Utilities/Commodities#Exchange]]).&lt;br /&gt;
&lt;br /&gt;
=== Without GFX card ===&lt;br /&gt;
&lt;br /&gt;
Copy Virtual driver with its icon (MOSSYS:Storage/Devs/Virtual) to SYS:Devs/Monitors/.&lt;br /&gt;
Edit its icon information to enable wanted screenmodes. Run Virtual driver or reboot the system.&lt;br /&gt;
&lt;br /&gt;
== Screenshot ==&lt;br /&gt;
: [[File:MorphOS3_jPV_Vncserver.png]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4049</id>
		<title>Applications/VNCServer</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4049"/>
				<updated>2019-08-03T19:10:23Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Description ==&lt;br /&gt;
Remote access server allowing clients to connect using the VNC protocol.  &lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
=== Autostart ===&lt;br /&gt;
&lt;br /&gt;
Add to &amp;lt;nowiki&amp;gt;S:Network-User-Startup&amp;lt;/nowiki&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Run &amp;gt;NIL: SYS:Applications/VNCServer/VNCServer&lt;br /&gt;
&lt;br /&gt;
Once started VNCServer will be available in the Exchange ([[Utilities/Commodities#Exchange]]).&lt;br /&gt;
&lt;br /&gt;
=== Without GFX card ===&lt;br /&gt;
&lt;br /&gt;
Copy Virtual driver with its icon (MOSSYS:Storage/Devs/Virtual) to SYS:Devs/Monitors/&lt;br /&gt;
Edit its icon information to enable wanted screenmodes. Run Virtual driver or reboot the system.&lt;br /&gt;
&lt;br /&gt;
== Screenshot ==&lt;br /&gt;
: [[File:MorphOS3_jPV_Vncserver.png]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4048</id>
		<title>Applications/VNCServer</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4048"/>
				<updated>2019-08-03T19:10:09Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Description ==&lt;br /&gt;
Remote access server allowing clients to connect using the VNC protocol.  &lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
=== Autostart ===&lt;br /&gt;
&lt;br /&gt;
Add to &amp;lt;nowiki&amp;gt;S:Network-User-Startup&amp;lt;/nowiki&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Run &amp;gt;NIL: SYS:Applications/VNCServer/VNCServer&lt;br /&gt;
&lt;br /&gt;
Once started VNCServer will be available in the Exchange ([[Utilities/Commodities#Exchange]]).&lt;br /&gt;
&lt;br /&gt;
=== Without GFX card ===&lt;br /&gt;
&lt;br /&gt;
Copy Virtual driver with its icon (MOSSYS:Storage/Devs/Virtual) to SYS:Devs/Monitors/&lt;br /&gt;
Edit its icon information to enable wanted screenmodes. Run directly Virtual driver or reboot the system.&lt;br /&gt;
&lt;br /&gt;
== Screenshot ==&lt;br /&gt;
: [[File:MorphOS3_jPV_Vncserver.png]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4047</id>
		<title>Applications/VNCServer</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Applications/VNCServer&amp;diff=4047"/>
				<updated>2019-08-02T17:59:24Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Description ==&lt;br /&gt;
Remote access server allowing clients to connect using the VNC protocol.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
=== Autostart ===&lt;br /&gt;
&lt;br /&gt;
Add to &amp;lt;nowiki&amp;gt;S:Network-User-Startup&amp;lt;/nowiki&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 Run &amp;gt;NIL: SYS:Applications/VNCServer/VNCServer&lt;br /&gt;
&lt;br /&gt;
Once started VNCServer will be available in the Exchange ([[Utilities/Commodities#Exchange]]).&lt;br /&gt;
&lt;br /&gt;
== Screenshot ==&lt;br /&gt;
: [[File:MorphOS3_jPV_Vncserver.png]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4040</id>
		<title>Hardware Compatibility</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4040"/>
				<updated>2019-04-11T20:24:02Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* USB Audio Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div id=&amp;quot;hardwareCompatibility&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Official Information ==&lt;br /&gt;
An official list of supported hardware is available at the [http://www.morphos-team.net/hardware MorphOS homepage] and a list of complete computer setups based on the official information is available [[Supported_Computers|here]].&lt;br /&gt;
&lt;br /&gt;
== User Provided Reports ==&lt;br /&gt;
This is a list of hardware compatibility reported by users. It isn't, by any means, a complete list of hardware compatibility, but just individual findings by users that may contain user errors or obsolete information. Please report your findings in [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.&lt;br /&gt;
&lt;br /&gt;
'''Note''': This list will only be as complete and comprehensive if you, a MorphOS user, report the hardware you have used in conjunction with MorphOS successfully, or unsuccessfully, for it to be included for others to gain the benefit from, and if necessary, possible and/or realistic, for further testing to be undertaken to establish if the hardware can be made functional for all users to enjoy with MorphOS. &lt;br /&gt;
&lt;br /&gt;
This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library. Where possible the lists will be maintained in alphabetical order (A-Z), but if you find any errors please [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 let us know] so correction(s) can be made.&lt;br /&gt;
&lt;br /&gt;
=== Gamepads ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th class=&amp;quot;type&amp;quot;&amp;gt;USB Game Controller&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;driver&amp;quot;&amp;gt;USB driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;8-bitdo SFC30 Pro Controller&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech Rumble Pad wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Saitek P380 Dual Analog wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td style=&amp;quot;color:red;&amp;quot;&amp;gt;Sony Dualshock 3 (PS3)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;not supported&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sony Dualshock 4 (PS4)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Competition Pro USB&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Xeox Gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Thrustmaster 360 Modena Pro Racing Wheel&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;needs some setup for the ranges from the Poseidon prefs&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox 360 wired and wireless pads&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wireless supported via PC adapter&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox One gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wired only&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Keyboards ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%;&amp;quot;&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Apple A1016 Wireless BlueTooth&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Ducky Zero Keyboard DK2108SZ&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech UltraX Premium&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E6300 Ultra-Slim BT keyboard for iPad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
① requires a machine which supports paired BT input devices, like Mac mini&lt;br /&gt;
&lt;br /&gt;
=== Mice ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M180&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M185&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech T-RB22 Wireless Trackball&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech G203&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software control over RGB, DPI&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Labtec Optical Mouse 800&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;MicroSoft Trackball Explorer v1.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;PS2&amp;gt;USB adapter required&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Targus AMU3102EU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Printers ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;TurboPrint (Printer) driver&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;PostScript (Printers) driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;HP 2500 Color LaserJet&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DE],  [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ES],  [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FR],  [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz IT]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Lexmark E342n&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;HP_LaserJet5series&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://support.lexmark.com/index?productCode=LEXMARK_E340&amp;amp;segment=SUPPORTproductCode%3D&amp;amp;viewlocale=pt_BR&amp;amp;page=content&amp;amp;searchid=1378996742336&amp;amp;actp=search&amp;amp;id=DR13234&amp;amp;locale=EN&amp;amp;userlocale=EN_US Lexmark_E342n_en.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xerox 3225 Workcentre&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Reported to work with PS&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Konica Minolta Magicolor 4650&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;M4650PX.ppd&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Scanners ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Epson Perfection 1640SU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Including recent support for its ADF (Automatic Document Feeder).&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== USB Audio Devices ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Output&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Input&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;&amp;quot;[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]&amp;quot; USB sound card&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.aliexpress.com/item/Vikings-City-Bluetooth-Adapter-APT-X-Low-Latency-Driver-Free-Plug-n-Play-BT-4-1/32828525027.html ANTTUS Gaming USB Bluetooth Adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;C-Media soundcard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;FX-Audio- DAC-X3&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.12&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;N/A&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Griffin iMic&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;only front Output tested&amp;lt;/tD&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4039</id>
		<title>Hardware Compatibility</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Hardware_Compatibility&amp;diff=4039"/>
				<updated>2019-04-11T19:55:33Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Mice */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div id=&amp;quot;hardwareCompatibility&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Official Information ==&lt;br /&gt;
An official list of supported hardware is available at the [http://www.morphos-team.net/hardware MorphOS homepage] and a list of complete computer setups based on the official information is available [[Supported_Computers|here]].&lt;br /&gt;
&lt;br /&gt;
== User Provided Reports ==&lt;br /&gt;
This is a list of hardware compatibility reported by users. It isn't, by any means, a complete list of hardware compatibility, but just individual findings by users that may contain user errors or obsolete information. Please report your findings in [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.&lt;br /&gt;
&lt;br /&gt;
'''Note''': This list will only be as complete and comprehensive if you, a MorphOS user, report the hardware you have used in conjunction with MorphOS successfully, or unsuccessfully, for it to be included for others to gain the benefit from, and if necessary, possible and/or realistic, for further testing to be undertaken to establish if the hardware can be made functional for all users to enjoy with MorphOS. &lt;br /&gt;
&lt;br /&gt;
This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library. Where possible the lists will be maintained in alphabetical order (A-Z), but if you find any errors please [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12445&amp;amp;forum=11 let us know] so correction(s) can be made.&lt;br /&gt;
&lt;br /&gt;
=== Gamepads ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th class=&amp;quot;type&amp;quot;&amp;gt;USB Game Controller&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;driver&amp;quot;&amp;gt;USB driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;8-bitdo SFC30 Pro Controller&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech Rumble Pad wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Saitek P380 Dual Analog wired (USB2)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td style=&amp;quot;color:red;&amp;quot;&amp;gt;Sony Dualshock 3 (PS3)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;-&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;not supported&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Sony Dualshock 4 (PS4)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Competition Pro USB&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Speedlink Xeox Gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Thrustmaster 360 Modena Pro Racing Wheel&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;hid&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;needs some setup for the ranges from the Poseidon prefs&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox 360 wired and wireless pads&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wireless supported via PC adapter&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xbox One gamepad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;xbox360&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;wired only&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Keyboards ===&lt;br /&gt;
&amp;lt;table style=&amp;quot;width:100%;&amp;quot;&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Apple A1016 Wireless BlueTooth&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Ducky Zero Keyboard DK2108SZ&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech UltraX Premium&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Rapoo E6300 Ultra-Slim BT keyboard for iPad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;①&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
① requires a machine which supports paired BT input devices, like Mac mini&lt;br /&gt;
&lt;br /&gt;
=== Mice ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M180&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech M185&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech T-RB22 Wireless Trackball&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Logitech G203&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No software control over RGB, DPI&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Labtec Optical Mouse 800&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;MicroSoft Trackball Explorer v1.0&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;PS2&amp;gt;USB adapter required&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Targus AMU3102EU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Printers ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;TurboPrint (Printer) driver&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;PostScript (Printers) driver&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;HP 2500 Color LaserJet&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DE],  [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ES],  [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FR],  [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz IT]&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Lexmark E342n&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;HP_LaserJet5series&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;[http://support.lexmark.com/index?productCode=LEXMARK_E340&amp;amp;segment=SUPPORTproductCode%3D&amp;amp;viewlocale=pt_BR&amp;amp;page=content&amp;amp;searchid=1378996742336&amp;amp;actp=search&amp;amp;id=DR13234&amp;amp;locale=EN&amp;amp;userlocale=EN_US Lexmark_E342n_en.PPD]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Xerox 3225 Workcentre&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Reported to work with PS&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Konica Minolta Magicolor 4650&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;M4650PX.ppd&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Scanners ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Model&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Epson Perfection 1640SU&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Including recent support for its ADF (Automatic Document Feeder).&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== USB Audio Devices ===&lt;br /&gt;
&amp;lt;table&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;th&amp;gt;Device&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;os&amp;quot;&amp;gt;OS&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Output&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Input&amp;lt;/th&amp;gt;&amp;lt;th class=&amp;quot;comments&amp;quot;&amp;gt;Comments&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;&amp;quot;[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]&amp;quot; USB sound card&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.10&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;No&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.aliexpress.com/item/Vikings-City-Bluetooth-Adapter-APT-X-Low-Latency-Driver-Free-Plug-n-Play-BT-4-1/32828525027.html ANTTUS Gaming USB Bluetooth Adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;C-Media soundcard&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Griffin iMic&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;distorted output&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;only front Output tested&amp;lt;/tD&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;3.11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;OK&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Untested&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3974</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3974"/>
				<updated>2019-01-24T14:47:52Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom Devaliases ==&lt;br /&gt;
The ''devalias'' command adds temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' stores a devalias in NVRAMRC. Variable ''use-nvramrc?'' needs to be set to true in order to execute NVRAMRC script at startup.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvunalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
&lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3973</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3973"/>
				<updated>2019-01-24T14:46:07Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom Devaliases ==&lt;br /&gt;
The ''devalias'' command adds temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' stores a devalias in NVRAMRC. Variable ''use-nvramrc?'' needs to be set to true in order to execute NVRAMRC script at startup.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvunalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3972</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3972"/>
				<updated>2019-01-24T14:40:12Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding Custom Devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom Devaliases ==&lt;br /&gt;
The ''devalias'' command adds temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' stores a devalias in NVRAMRC. Variable ''use-nvramrc?'' needs to be set to true in order to execute NVRAMRC script at startup.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvunalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3971</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3971"/>
				<updated>2019-01-24T14:39:10Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding Custom Devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom Devaliases ==&lt;br /&gt;
The ''devalias'' command adds temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' stores a devalias in nvramrc. Variable ''use-nvramrc?'' needs to be set to true in order to execute NVRAMRC script at startup.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvunalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3970</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3970"/>
				<updated>2019-01-24T14:38:55Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding Custom Devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom Devaliases ==&lt;br /&gt;
The ''devalias'' command adds temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' stores a devalias in nvramrc. Variable ''use-nvramrc?'' needs to be set to true in order to exectute NVRAMRC script at startup.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvunalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3969</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3969"/>
				<updated>2019-01-24T14:24:39Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding Custom Devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom Devaliases ==&lt;br /&gt;
The ''devalias'' command adds temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' stores a devalias in nvramrc. To survive a reboot (''reset-all'') variable ''use-nvramrc?'' needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvunalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3968</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3968"/>
				<updated>2019-01-24T14:20:06Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding Custom Devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom Devaliases ==&lt;br /&gt;
The ''devalias'' command adds temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' stores a devalias in nvramrc. To survive a reboot (''reset-all'') variable ''use-nvramrc?'' needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3967</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3967"/>
				<updated>2019-01-24T14:19:17Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding Custom devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom Devaliases ==&lt;br /&gt;
The ''devalias'' command can add temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' command stores a devalias in nvramrc. To survive a reboot (''reset-all'') variable ''use-nvramrc?'' needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3966</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3966"/>
				<updated>2019-01-24T14:18:16Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding Custom devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom devaliases ==&lt;br /&gt;
The ''devalias'' command can add temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' command stores a devalias in nvramrc. To survive a reboot (''reset-all'') variable ''use-nvramrc?'' needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3965</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3965"/>
				<updated>2019-01-24T14:16:35Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding Custom devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom devaliases ==&lt;br /&gt;
The ''devalias'' command can add temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvvalias'' command stores a devalias in nvramrc. To survive a reboot (''reset-all') variable use-nvramrc? needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''nvunalias'' deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3964</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3964"/>
				<updated>2019-01-24T14:15:11Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom devaliases ==&lt;br /&gt;
The ''devalias'' command can add temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
nvalias command stores a devalias in nvramrc. To survive a reboot (&amp;quot;reset-all&amp;quot;) variable use-nvramrc? needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;nvunalias&amp;quot; deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3963</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3963"/>
				<updated>2019-01-24T14:14:20Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom devaliases ==&lt;br /&gt;
The ''devalias'' command can add temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
nvalias command stores a devalias in nvramrc. To survive a reboot (&amp;quot;reset-all&amp;quot;) variable use-nvramrc? needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;nvunalias&amp;quot; deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3962</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3962"/>
				<updated>2019-01-24T14:12:40Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom devaliases ==&lt;br /&gt;
The ''devalias'' command can add temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
nvalias command stores a devalias in nvramrc. To survive a reboot (&amp;quot;reset-all&amp;quot;) variable use-nvramrc? needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;nvunalias&amp;quot; deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3961</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3961"/>
				<updated>2019-01-24T14:11:02Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding Custom devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom devaliases ==&lt;br /&gt;
The ''devalias'' command can add temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
nvalias command stores a devalias in nvramrc. To survive a reboot (&amp;quot;reset-all&amp;quot;) variable use-nvramrc? needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;nvunalias&amp;quot; deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3960</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3960"/>
				<updated>2019-01-24T14:10:20Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Adding custom devaliases */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding Custom devaliases ==&lt;br /&gt;
The ''devalias'' command can add temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
nvalias command stores a devalias in nvramrc. To survive a reboot (&amp;quot;reset-all&amp;quot;) variable use-nvramrc? needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;nvunalias&amp;quot; deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3959</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3959"/>
				<updated>2019-01-24T14:09:39Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Adding custom devaliases ==&lt;br /&gt;
The ''devalias'' command can add temporary user defined devaliases.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias dh /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
nvalias command stores a devalias in nvramrc. To survive a reboot (&amp;quot;reset-all&amp;quot;) variable use-nvramrc? needs to be set to true.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;nvunalias&amp;quot; deletes an alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; nvalias dh&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can replace existing devaliases with your own ones. Removing them will revert to original values.&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3958</id>
		<title>Open Firmware</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Open_Firmware&amp;diff=3958"/>
				<updated>2019-01-24T13:54:21Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Environment Variables */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Preface ==&lt;br /&gt;
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to the BIOS on a PC, found in all MorphOS compatible Macs. The Pegasos, Pegasos II, and Efika also have an Open Firmware based hardware implementation, but with small differences to Mac firmware.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses a Command-Line based user interface, which can be used to control booting and other processes. This tutorial focuses on useful tips and tricks when using the user interface by way of specific examples. The examples were tested on PowerPC Macs, but may also work under bPlan machines to some extent.&lt;br /&gt;
&lt;br /&gt;
Output texts in these examples have been truncated in most cases to show only the  information of interest.&lt;br /&gt;
&lt;br /&gt;
== Accessing the User Interface ==&lt;br /&gt;
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard, though the '''Option''' key is sometimes marked as '''Alt''' - with a symbol/icon below it, or press the '''Win-Alt-O-F''' key combination on a PC Windows keyboard while booting the machine. Release the keys only after you see the Open Firmware prompt display on a grey background.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50&lt;br /&gt;
Copyright 1994-2005 Apple Computer, Inc.&lt;br /&gt;
All Rights Reserved.&lt;br /&gt;
&lt;br /&gt;
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11&lt;br /&gt;
&lt;br /&gt;
To continue booting, type &amp;quot;mac-boot&amp;quot; and press return.&lt;br /&gt;
To shut down, type &amp;quot;shut-down&amp;quot; and press return.&lt;br /&gt;
&lt;br /&gt;
Release keys to continue!&lt;br /&gt;
&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the machine boots to an installed OS instead of the OF prompt, reboot and try again. It may help to connect the keyboard directly to the machine's USB port, not via a USB hub. The keys don't have to be pressed immediately when powering the machine on, but promptly after hearing the startup sound (if it has not been disabled) or as the machine triggers access to the optical drive.&lt;br /&gt;
&lt;br /&gt;
Open Firmware uses the '''US keyboard layout''', tips for typing using other keyboards can be found within the [http://www.morphos.de/guide/usb-boot#section5 official MorphOS USB boot guide].&lt;br /&gt;
&lt;br /&gt;
== Useful Commands ==&lt;br /&gt;
* '''mac-boot''' - Continues booting from the current OF state&lt;br /&gt;
* '''reset-all''' - Resets the machine to the power-on state and reboots&lt;br /&gt;
* '''shut-down''' - Shuts down the machine&lt;br /&gt;
* '''load &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory&lt;br /&gt;
* '''go''' - Runs/boots the loaded file&lt;br /&gt;
* '''boot &amp;lt;file&amp;gt; &amp;lt;args&amp;gt;''' - Loads an OF code file and boots it&lt;br /&gt;
* '''printenv''' - Prints environment variable values&lt;br /&gt;
* '''setenv''' - Sets environment variable values&lt;br /&gt;
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)&lt;br /&gt;
* '''.properties''' - Displays a list of properties for the selected device&lt;br /&gt;
* '''ls''' - Displays contents of the current path in the device tree&lt;br /&gt;
* '''pwd''' - Displays the current path within the device tree&lt;br /&gt;
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)&lt;br /&gt;
* '''dir''' - Lists files on a partition&lt;br /&gt;
&lt;br /&gt;
== Environment Variables ==&lt;br /&gt;
Use the ''printenv'' command to list all environment variable values.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; printenv&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
little-endian?           false                false&lt;br /&gt;
real-mode?              false                false&lt;br /&gt;
auto-boot?              true                 true&lt;br /&gt;
skip-netboot?           false                false&lt;br /&gt;
use-nvramrc?           false                false&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first value in the list is the current value and the second value is the default value. It's quite rare that you need to change these values, but it's interesting to learn more about your computer nevertheless.&lt;br /&gt;
&lt;br /&gt;
One common choice is to speed up Startup Manager (the boot menu you see when booting with the option/alt key pressed) by disabling the netboot option. So, let's change that, as an example, and check that we succeeded.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; setenv skip-netboot? true&lt;br /&gt;
0 &amp;gt; printenv skip-netboot?&lt;br /&gt;
-------------- Partition: common -------- Signature: 0x70 ---------------&lt;br /&gt;
skip-netboot?           true                 false&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Examining Devices ==&lt;br /&gt;
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information about the selected device. '''Note''' that it depends on the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and such like.&lt;br /&gt;
&lt;br /&gt;
=== Listing Aliases ===&lt;br /&gt;
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see a few examples of how to show that information.&lt;br /&gt;
&lt;br /&gt;
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases&lt;br /&gt;
0 &amp;gt; .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The commands can also be input combined, on a single line:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev /aliases .properties&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; devalias&lt;br /&gt;
name                    aliases &lt;br /&gt;
pci0                    /pci@f0000000&lt;br /&gt;
agp                     /pci@f0000000&lt;br /&gt;
pci1                    /pci@f2000000&lt;br /&gt;
pci2                    /pci@f4000000&lt;br /&gt;
usb0                    /pci@f2000000/@15&lt;br /&gt;
usb1                    /pci@f2000000/@15,1&lt;br /&gt;
usb2                    /pci@f2000000/@15,2&lt;br /&gt;
hd                      /pci@f4000000/ata-6@d/disk@0&lt;br /&gt;
cd                      /pci@f4000000/ata-6@d/disk@1&lt;br /&gt;
ud                      /pci@f2000000/usb@15,1/disk@1&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Other Useful Properties ===&lt;br /&gt;
''.properties'' on the root device shows the computer specs:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev / .properties&lt;br /&gt;
model                   PowerBook5,9&lt;br /&gt;
compatible              PowerBook5,9&lt;br /&gt;
                        MacRISC3&lt;br /&gt;
                        Power Macintosh&lt;br /&gt;
						&lt;br /&gt;
serial-number           SX0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev enet .properties&lt;br /&gt;
vendor-id               0000106b&lt;br /&gt;
device-id               0000006b&lt;br /&gt;
name                    ethernet&lt;br /&gt;
device_type             network&lt;br /&gt;
local-mac-address       001124e3 6666&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Devices ===&lt;br /&gt;
The ''ls'' command lists devices found in the current device in the device tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650  /disk@1&lt;br /&gt;
ff9e1a28: /device@2&lt;br /&gt;
ff9e1c48:   /keyboard@0&lt;br /&gt;
ff9e1f88:   /mouse@1&lt;br /&gt;
ff9e2230:   /interface@2&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Listing Files ===&lt;br /&gt;
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.&lt;br /&gt;
&lt;br /&gt;
Syntax of the ''dir'' command is:&lt;br /&gt;
'''dir disk:partition,path'''&lt;br /&gt;
&lt;br /&gt;
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /&lt;br /&gt;
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank&lt;br /&gt;
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory&lt;br /&gt;
&lt;br /&gt;
Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The &amp;quot;,&amp;quot; character could be omitted in certain cases, but it's safer to type that as well:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from the first partition on the (default) HD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing a sub-directory from a CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc32&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Listing the root directory from a USB mass storage device found in the usb1 device (use the previously mentioned ''ls'' command to find the correct device):&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected prior to starting the OF interface), so this does the same as the previous example:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir ud:,\&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Booting MorphOS ==&lt;br /&gt;
=== Basics ===&lt;br /&gt;
To boot into MorphOS, Open Firmware has to load a MorphOS boot image file, which is usually named as ''boot.img''. The boot image contains the MorphOS kernel and core drivers, so it's basically comparable to the Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS itself after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at a later stage.&lt;br /&gt;
&lt;br /&gt;
The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known to Open Firmware in any case. The ''Boot:'' partition only contains a few Open Firmware related files and isn't used for anything else than to get the kernel loaded by the machine itself. How MorphOS sees the partition isn't important and it can even be unmounted from a MorphOS point of view. MorphOS itself is booted from a partition containing a MorphOS compatible [[Filesystems|filesystem]] and MorphOS system files in it, and this partition is usually named as &amp;quot;System:&amp;quot; and the SYS: '''assign''' points to it as well.&lt;br /&gt;
&lt;br /&gt;
When booting manually from OF, you'll see some output lines on screen. There are two important lines that tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
Type in this line (if you have a MorphOS installation on your HD):&lt;br /&gt;
 0 &amp;gt; load hd:,\boot.img&lt;br /&gt;
 &lt;br /&gt;
And you'll see output like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; load hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; _&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Loading ELF&amp;quot; tells you that the file has been found and loaded.&lt;br /&gt;
&lt;br /&gt;
The file can be booted with the ''go'' command then:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; go&lt;br /&gt;
DO-QUIESCE finished_&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;DO-QUIESCE finished&amp;quot; indicates that the file has been booted and the machine is now running under MorphOS. Problems after that stage are MorphOS related, and if the MorphOS boot image doesn't appear soon, then MorphOS might not have found a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (Ctrl-Lcmd-Rcmd, Fn-alt-alt) also work at this stage even if there are any other problems halting the boot process.&lt;br /&gt;
&lt;br /&gt;
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.&lt;br /&gt;
&lt;br /&gt;
The previous example can be achieved with this single line:&lt;br /&gt;
 0 &amp;gt; boot hd:,\boot.img &lt;br /&gt;
 &lt;br /&gt;
And the output should then look like this:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; boot hd:,\boot.img load-size=16e8fc adler32=bd628950&lt;br /&gt;
&lt;br /&gt;
Loading ELF&lt;br /&gt;
 &lt;br /&gt;
DO-QUIESCE finished_&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Boot Arguments ===&lt;br /&gt;
Several boot arguments can be given to the ''boot.img'' file by adding them to the end of a ''load'' or ''boot'' line. More detailed explanations of these arguments can be found from '''Docs/Booting MorphOS.txt''' and '''Docs/PegasosFirmware.txt''' files on your MorphOS system or the installation CD, but let's cover the most useful booting related ones here.&lt;br /&gt;
&lt;br /&gt;
Without arguments MorphOS boots a device that is bootable and has the highest boot priority set. '''Note''' that this only applies to partitions that contain a MorphOS compatible bootable [[Filesystems|filesystem]]. If a MorphOS installation CD is inserted, it usually has a higher priority than bootable partitions on the HD. The HDConfig tool can be used to set partitions bootable and alter their boot priorities, but usually it's unnecessary to change these settings.&lt;br /&gt;
&lt;br /&gt;
The syntax for arguments is '''argument=value''', but the equals sign can be replaced with a space character. The arguments can be given in a longer or shorter, in parenthesis '''()''' format.&lt;br /&gt;
&lt;br /&gt;
* '''bootdevice (bd)''' - Overrides boot priorities and boots from a given partition. The partition name must be given in the form MorphOS sees it as a '''device name''' (volume names don't work), and the trailing &amp;quot;:&amp;quot; character can be omitted. For example, &amp;quot;bootdevice=dh1&amp;quot; works, but &amp;quot;bootdevice=System&amp;quot; doesn't.&lt;br /&gt;
* '''bootimage (bi)''' - Boots the MorphOS system from an ISO image file, which is placed on a partition that is accessible with the built-in filesystems of the boot.img ('''FAT, SFS, FFS, PFS3, CDFS'''). A full MorphOS style path must be given to the argument, but use '''device names''' instead of volume names again. For example, &amp;quot;bootimage=umsd0:morphos-3.11.iso&amp;quot;, &amp;quot;bootimage=dh2:morphos-3.11.iso&amp;quot;.&lt;br /&gt;
* '''bootmenu (bm)''' - Boots into the MorphOS bootmenu where you can change display settings, see information about devices, or boot without startup-sequence. The same bootmenu can be accessed by pressing the '''shift''' key during the MorphOS boot process. Pressing the '''v''' key in the bootmenu toggles between the default resolution and a 640x480@60Hz VESA mode, and that can be useful in case of display issues. The '''space''' toggles between multiple monitors instead.&lt;br /&gt;
&lt;br /&gt;
=== Examples ===&lt;br /&gt;
==== Booting from CD ====&lt;br /&gt;
MorphOS documentation's usual advice is to boot the machine with the ''c'' key pressed, but that method can sometimes be unreliable for one reason or another, so you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, which results in an error if the boot image and the CD aren't from the same MorphOS version. A more reliable way is to boot into the Startup Manager menu on Macs by holding the ''alt'' (''option'') key at boot, and select the CD from that graphical boot menu. Pressing the F12 key in the menu will eject the CD.&lt;br /&gt;
&lt;br /&gt;
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.&lt;br /&gt;
&lt;br /&gt;
To boot any inserted CD that is bootable on Macs:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\:tbxi&lt;br /&gt;
&lt;br /&gt;
&amp;quot;\\&amp;quot; will look for a ''blessed'' directory on a device (you can list it by ''dir cd:,\\'' or ''dir hd:,\\'', for instance) and '':tbxi'' looks for files of type tbxi (Toolbox image). This does practically the same thing as booting with the ''c'' key or booting from the Startup Manager menu, but you also see the output lines from OF (especially the &amp;quot;Loading ELF&amp;quot; &amp;amp; &amp;quot;DO-QUIESCE finished&amp;quot; lines) if you need some debug output.&lt;br /&gt;
&lt;br /&gt;
Another way to boot the MorphOS installation CD from the OF prompt is to locate a correct boot image file from the CD and boot it with some boot arguments.&lt;br /&gt;
&lt;br /&gt;
List the contents of the CD:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\&lt;br /&gt;
&lt;br /&gt;
  Volume: MorphOSBoot&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
        94 07/04/2018 04:54:42  ???? ???? .morphosid&lt;br /&gt;
   2287135 07/04/2018 04:03:02  boot UNIX boot.img&lt;br /&gt;
   1454648 07/04/2018 04:03:02  boot UNIX bootcyrusplus.img&lt;br /&gt;
   2201986 07/04/2018 04:03:02  boot UNIX bootefika.img&lt;br /&gt;
   2286039 07/04/2018 04:03:02  boot UNIX bootpeg1.img&lt;br /&gt;
   1416944 07/04/2018 04:03:02  boot UNIX bootsam_ppc4x0.img&lt;br /&gt;
           01/01/1904 00:00:00           *mac_ppc32&lt;br /&gt;
           01/01/1904 00:00:00            mac_ppc64&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As you can see, there are several different boot images for different architectures. ''boot.img'' is for Pegasos II and others are easy to guess. Boot images for Macs are located in sub-directories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.&lt;br /&gt;
&lt;br /&gt;
If we wanted to boot the CD on a G5 Mac:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir cd:,\mac_ppc64&lt;br /&gt;
&lt;br /&gt;
     Size/        GMT                     File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR    Name&lt;br /&gt;
   1499688 07/04/2018 04:03:02  boot UNIX  boot.img&lt;br /&gt;
   &lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot cd:,\mac_ppc64\boot.img bd cd0&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
cd0: is the default CD device on MorphOS and it can be given as a bootdevice argument. The system would most likely boot from the CD even without this argument, because of the previously mentioned boot priorities.&lt;br /&gt;
&lt;br /&gt;
To boot into the MorphOS boot menu on a G5 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc64\boot.img bm&lt;br /&gt;
&lt;br /&gt;
And the same for a G4 Mac:&lt;br /&gt;
 0 &amp;gt; boot cd:,\mac_ppc32\boot.img bm&lt;br /&gt;
&lt;br /&gt;
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:&lt;br /&gt;
 0 &amp;gt; boot cd:,\\boot.img bm&lt;br /&gt;
&lt;br /&gt;
==== Booting MorphOS ISO from USB ====&lt;br /&gt;
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot &amp;amp; Installation / Update Guide] describes the basics of USB booting, but let's cover a few special cases here. If you can't access your FAT formatted USB stick, refer to the official guide on how to re-format it in a compatible way. Some Macs can be more picky about the format than others, and the same stick, that works in G4 Macs, might not work in a G5 Mac, etc., but it usually helps if you format it as advised in the official guide. If you still have issues with USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get a system booted.&lt;br /&gt;
&lt;br /&gt;
The following examples assume that you have a '''correct boot image file''' (named as ''boot.img'' here) and a '''MorphOS ISO image file''' (named as ''morphos.iso'' here, remember that official MorphOS downloads have different names!) on a '''FAT formatted USB stick''', which is plugged in before starting the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs are stored in different directories (mac_ppc32 vs mac_ppc64). The files may be named differently too, there's no problem if you want to keep different versions around and boot whichever you want. You could have ''boot310.img'' and ''morphos310.iso'' as a bootable backup, for instance.&lt;br /&gt;
&lt;br /&gt;
So, the basic idea is to boot the system from an ISO image without burning it or extracting files from it. This can be achieved by giving the ISO image location to the boot image with the ''bootimage'' argument.&lt;br /&gt;
&lt;br /&gt;
Some firmware versions create a ''ud'' alias, which points to a USB mass storage device connected to the computer. [[Open_Firmware#Listing_Aliases | List the aliases]] to find out if it's been created.&lt;br /&gt;
&lt;br /&gt;
MorphOS itself creates a ''umsd0:'' device for the USB mass storage device and our ISO file is found from this device when the boot.img has been loaded.&lt;br /&gt;
&lt;br /&gt;
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:&lt;br /&gt;
 0 &amp;gt; boot ud:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
 &lt;br /&gt;
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:&lt;br /&gt;
 0 &amp;gt; dir ud:,\&lt;br /&gt;
&lt;br /&gt;
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree. List the aliases again or just start trying to list usb0, usb1, etc., devices until you find a device containing '''disk''' in its name, and that will reveal the full path to the USB stick, which can be used instead of the ''ud'' alias.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb0 ls&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /disk@1&lt;br /&gt;
0 &amp;gt; dir usb1/disk@1:,\&lt;br /&gt;
  Volume: USB&lt;br /&gt;
 258048000  07-24-2018 18:34:24    morphos.iso&lt;br /&gt;
   1501436  07-04-2018 04:03:02    boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dev usb1 ls&lt;br /&gt;
ff9e1650: /hub@1&lt;br /&gt;
ff9e1860:   /disk@4&lt;br /&gt;
0 &amp;gt; boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If a USB stick isn't recognised by Open Firmware, but it's accessible from MorphOS itself and you don't want to re-format it, you could copy the boot.img to a Mac partition on the HD, but still load the ISO image from the USB stick. The Mac partition can be an existing OSX installation (HFS+ formatted partition) or previous MorphOS installation (the HFS formatted Boot partition), for instance. The ISO image itself can't be loaded from an HFS partition, because MorphOS kernel (boot.img) doesn't have HFS support built-in. HFS support is loaded from filesystem level at the later stage when you boot MorphOS, but as OF recognises HFS partitions, boot.img can be loaded from them.&lt;br /&gt;
&lt;br /&gt;
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
0 &amp;gt; dir hd:1,\&lt;br /&gt;
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; dir hd:2,\&lt;br /&gt;
&lt;br /&gt;
  Volume: OSX&lt;br /&gt;
     Size/        GMT                      File/Dir&lt;br /&gt;
     bytes   date     time   TYPE CRTR     Name&lt;br /&gt;
           07/22/2017 07:27:40              Applications&lt;br /&gt;
           09/27/2016 09:59:40              bin&lt;br /&gt;
   1501436 07-04-2018 04:03:02  ???? UNIX   boot.img&lt;br /&gt;
 ok&lt;br /&gt;
0 &amp;gt; boot hd:2,\boot.img bi umsd0:morphos.iso&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3881</id>
		<title>Getting Started</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3881"/>
				<updated>2018-06-20T22:28:31Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== A Beginner's Guide to MorphOS ==&lt;br /&gt;
&lt;br /&gt;
You have installed MorphOS to a compatible machine, but... now what? You could always go and install a pre-configured package like Chrysalis, but you would end up with a system configured for someone else's taste and you still wouldn't know how to actually use the operating system. If you are in this situation and would like to learn how MorphOS works, this is a tutorial for you! The tutorial will guide you through the things you should do and notice after a fresh install, with practical examples from basic configuration options to installing new software. It won't cover all the details and is just an opinion on how to proceed, but it should give you some knowledge how to continue on your own and make your own decisions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting Comfortable with the User Interface and the Ambient Desktop ==&lt;br /&gt;
=== The First Boot ===&lt;br /&gt;
&lt;br /&gt;
After a boot you're presented with the plain looking Ambient, the desktop environment of MorphOS. The first thing you should learn is to get familiar with the basic usage, and to tune the interface settings so that they won't annoy you. The worst thing is if a user plays around a bit and just curses at the system when it doesn't work as expected or wanted. You aren't forced into just one kind of behaviour with MorphOS!&lt;br /&gt;
: [[File:GettingStarted_Ambient.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Right mouse click is widely used on MorphOS and if you're using a device without a physical button for it, check the tips over [[Tips_and_Tricks#How_to_Use_RMB_with_One-button_Mouse | here]]. Pressing the right mouse button over the Ambient screen opens Ambient's pulldown menus where you can find few important options. For example, options to shut down the system, to open a new shell window, or to open system settings.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Shutdown.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== System Settings ===&lt;br /&gt;
&lt;br /&gt;
The MorphOS Preferences application is used to edit system-wide settings. It can be launched from the Ambient's pulldown menu by selecting the &amp;quot;Settings-&amp;gt;System...&amp;quot; menu option or by browsing to the System:Prefs/ drawer and double clicking the Preferences icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_System_Settings.png]] [[File:GettingStarted_MorphOS_Preferences.png|237px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Screens ====&lt;br /&gt;
&lt;br /&gt;
If MorphOS didn't get the optimal resolution of your monitor with DDC, a different screen mode can be selected from the Screens settings. If the wanted mode isn't seen there, open the Monitors settings instead to create a completely new mode.&lt;br /&gt;
&lt;br /&gt;
If you have a graphics card with a low amount of memory, you can try to make the memory consumption smaller by disabling the Enhanced Display setting (3D accelerated graphics functions for 2D screens) or by reducing the color depth. More information can be found  [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
MorphOS skins (themes for the graphical appearance) can also be changed from the Screens settings.&lt;br /&gt;
&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== IControl ====&lt;br /&gt;
&lt;br /&gt;
IControl settings are the most important settings for the overall user experience. This is the place to look in order to avoid the usual comments like ''&amp;quot;Why doesn't X work like Y in the other OS?&amp;quot;'', ''&amp;quot;Why there isn't a feature Z?&amp;quot;'', ''&amp;quot;I can't use a system like this!&amp;quot;''. Everyone should check these settings first before going any further.&lt;br /&gt;
&lt;br /&gt;
===== Hotkeys =====&lt;br /&gt;
MorphOS has many nice features to use with keyboard shortcuts or mouse buttons, but only few are activated by default. Let's activate more!&lt;br /&gt;
&lt;br /&gt;
To add a new hotkey for the wanted function click the popup button on the right side, select &amp;quot;'''Sample'''&amp;quot;, and press the wanted key combination. The pressed combination is then recorded on the corresponding line and should be shown there. Repeat the procedure if you didn't get it as wanted on the first try. Changed settings will be taken into use after you click the Save or Use button.&lt;br /&gt;
&lt;br /&gt;
Here is how to set the &amp;quot;control left-alt c&amp;quot; key combination to '''center the active window''' on the screen:&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Hotkeys2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Here are some other recommendations to activate, but feel free to use your own preferences for the hotkeys:&lt;br /&gt;
* '''Active Window: To Back''' - double click with middle mouse button to send a window back of other windows.&lt;br /&gt;
* '''Active Window: Zoom''' - &amp;quot;control left-alt m&amp;quot;, to toggle between a maximized and minimized window.&lt;br /&gt;
* '''Active Window: Activate Next''' - &amp;quot;left-command tab&amp;quot;, to have the ''alt-tab'' functionality found on many other operating systems. Using ctrl-tab or alt-tab isn't recommended because they would overlap with the shell's functionality on MorphOS. Command-tab also happens be the same in OS X.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys3.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Note: You can also add several hotkeys for a function by selecting the New Hotkey option from the popup button's menu.&lt;br /&gt;
&lt;br /&gt;
===== Screens and Desktop =====&lt;br /&gt;
&lt;br /&gt;
Important options concerning how windows and menus behave can be found on the Screens and Desktop settings.&lt;br /&gt;
&lt;br /&gt;
I'd recommend turning on the '''Maximize window when clicking on the Zoom gadget''' option. The Zoom gadget will then toggle the window size between full screen (with the screen title bar still visible) and the initial window size and position. I find it much more comfortable than the legacy placement between two obscure positions. The previously configured Zoom hotkey will also work better with this option enabled.&lt;br /&gt;
&lt;br /&gt;
If you prefer being able to drag windows out of the screen without pressing any qualifier key, like on mainstream systems, select the '''When dragging windows... allow them to be placed out of screen, unless Control is pressed''' option.&lt;br /&gt;
&lt;br /&gt;
The default behaviour of the pulldown menus may be a bit unfamiliar for old Amiga users, but there are several options to get them working as expected. I like to disable the '''Menus shall remain opened even when mouse button is released''' option and enable the '''Open menus under mouse pointer outside screen titlebar area''' option.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Touchpad ====&lt;br /&gt;
&lt;br /&gt;
If you're using a laptop system, check the Touchpad setttings. You might want to disable clicking from the pad to avoid any accidental clicks.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Touchpad.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Laptop ====&lt;br /&gt;
&lt;br /&gt;
If you're not a Mac user, you might find it odd that you need to press the fn key when using the function keys for normal activities, and not when modifying, for example, the screen brightness. The '''Press and hold the fn key to modify screen brightness, audio volume, etc.''' option will change the functionality the other way around.&lt;br /&gt;
&lt;br /&gt;
Some systems also have the '''Automatic LCD brightness and keyboard backlight control''' option here. Disable it if you're annoyed by changing lightning.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Laptop.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Windows ===&lt;br /&gt;
&lt;br /&gt;
The first icon you see on the Ambient desktop is the &amp;quot;'''My MorphOS'''&amp;quot; icon. By double clicking it you'll get a window with icons of all volumes and assigns of the system. It works like a root directory with quick access to different locations.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS.png|320px]]&lt;br /&gt;
&lt;br /&gt;
If you find it a bit clumsy to work in the icon mode, like I do, you can change the view to '''the list mode''' from the cycle button on the right side of the window.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
With default settings Ambient doesn't remember the changed mode or other window properties next time you open it, but you can right click the window border or an empty area on the file lister to bring up a contextual window menu and select the &amp;quot;'''Snapshot-&amp;gt;Window'''&amp;quot; option to save the window properties. Default position and size for a window can be saved that way too. If you defined the centering hotkey earlier, you can try it now :)&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The same can also be done for normal directory windows. While &amp;quot;My MorphOS&amp;quot; window settings are exceptionally saved to Ambient's configuration files, normal directories' settings are saved to an icon file (a file with .info extension). If you change and save the mode for the Work: partition for example, you see a disk.info file appearing there.&lt;br /&gt;
: [[File:GettingStarted_Icon_Mode.png|320px]] [[File:GettingStarted_List_Mode_Snapshot.png|320px]] [[File:GettingStarted_List_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Displayed columns can be selected by right clicking the column title area, but modify the [[Getting_Started#Lister|default lister settings]] to your liking before starting to save settings for individual windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Lister_Columns.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Settings ===&lt;br /&gt;
&lt;br /&gt;
Ambient is actually a separate application itself and it has its own settings separated from the general system preferences. The previously mentioned system settings affect all programs and screens, but strictly desktop related settings are found in the Ambient settings. The Ambient Settings window can be opened by selecting the &amp;quot;Settings-&amp;gt;Ambient...&amp;quot; option from Ambient's pulldown menu.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Ambient_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
==== Miscellaneous ====&lt;br /&gt;
&lt;br /&gt;
The Miscellaneous page on the Ambient settings has a nice option to get the My MorphOS window opened when double clicking anywhere on the empty area of the desktop. It really speeds up the working when you don't have to move the mouse a long way to the top corner or dig the icon out from under some other windows. Enable it with the '''Double click on desktop opens MyMorphOS window''' option.&lt;br /&gt;
&lt;br /&gt;
The My MorphOS icon is just wasting space on the desktop after the previous setting and you can hide it by disabling the '''Display MyMorphOS icon''' option.&lt;br /&gt;
&lt;br /&gt;
If you like to have a bit more eye candy on the context menus, you can also enable the '''Show images in context menu''' option while you're here.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Misc.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Lister ====&lt;br /&gt;
The default properties of the list mode of Ambient windows can be changed on the Lister settings. Disable the '''Compact size display''' if you want to see exact file sizes in bytes always. You may also want to select different columns to be shown in the listers by double clicking items on the '''File Properties''' list to set them hidden or shown. '''Date &amp;amp; Time''' instead of just Date would probably be a common choice.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Lister.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Panels ====&lt;br /&gt;
&lt;br /&gt;
Many new users are wondering if there is any kind of dock application on MorphOS, because there isn't any shown by default. MorphOS has ''panels'' for that and you can have as many panels as you want on the desktop, arranged horizontally or vertically. The panels have features like zipping to hide and unhide them, sub panels and other Panel Object plugins, etc. There just isn't any configured by default and user can create a panel or panels how he likes.&lt;br /&gt;
&lt;br /&gt;
To create a new panel, open the Panels page on the Ambient settings and click the '''New Panel''' button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels1.png|320px]]&lt;br /&gt;
An empty panel can be dragged anywhere and you can find some of its settings on the '''Name &amp;amp; Look''' and '''Behaviour''' tabs. If you want to place the panel on a screen border the '''Attached to Borders''' option makes it easier. The '''Alpha''' option controls the transparency of a panel, but it only works if the Enhanced Display option for the Ambient screen enabled and working. The same applies to the '''Hide Dragbar''' option as well.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels2.png|320px]]&lt;br /&gt;
Programs can be added to the panel by dragging and dropping their icons to the panel list to the wanted position on the list tree, or to the panel itself. Items in the panel list can be rearranged by drag and drop too.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels3.png|320px]]&lt;br /&gt;
Available Panel Objects are listed on the right-hand side and they can be dragged and dropped to any position on the panel tree. All items on the panel may have their own settings, which are shown when an item is clicked once with the left mouse button. In this example picture a new sub panel has been created and its icon image is being changed to a custom one.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels4.png|320px]]&lt;br /&gt;
If you want to clone the color settings from the main panel to a sub panel, you can use the MUI clipboard to temporarily store a setting. Drag &amp;amp; drop the wanted color button to the clipboard button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels5.png|320px]]&lt;br /&gt;
Then activate the sub panel settings and drag &amp;amp; drop the clipboard button to the sub panel's color button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels6.png|320px]]&lt;br /&gt;
And here's a picture of the created panel with its sub panel in action. Remember to click the Save button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels7.png|320px]]&lt;br /&gt;
The panels also have a context menu that can be accessed with a right click. You'll have quick access to the panel settings and some other options there.&lt;br /&gt;
&lt;br /&gt;
If you lock a panel, items dragged to it aren't added to the panel anymore, but the dragged items are opened with the program you dropped them onto. Text files can be dropped onto the Scribble icon, MP3 files and directories can be dropped onto the Jukebox icon, video and audio files onto the MPlayer icon, and so on.&lt;br /&gt;
: [[File:GettingStarted_Panel_Locked1.png|320px]] [[File:GettingStarted_Panel_Locked2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Window ====&lt;br /&gt;
&lt;br /&gt;
Ambient windows are very configurable and users should at least check the buttons available for the toolbar. Just adding a few buttons can make a difference in usability. The buttons and other items can be dragged from the Available Buttons list to the Current Toolbar group, and vice versa to remove them from the toolbar. All changes are updated in real time to any open Ambient windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
In this example picture '''Makedir''' and '''Delete''' buttons are separated with the '''Space''' button, and they have been added into a row with other buttons. Also the '''Bookmarks''' button has been added as the last item on the toolbar. It always stays at the right border no matter how big a window is, because it's been added after the '''Flexible space''' button. &lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Keyboard ====&lt;br /&gt;
===== Built-in Command Hotkeys =====&lt;br /&gt;
Check the Ambient hotkeys from this section and change them to your liking. If you have a laptop without the numeric keypad, you should change hotkeys which are using numpad combinations by default. I, for example, am used to having the '''Cycle Mode''' option on the key above the tab key and the '''Cycle Submode''' option when the same key is pressed with the shift key. It feels somehow quicker to use them from there than from the numeric keypad with a standard keyboard too.&lt;br /&gt;
&lt;br /&gt;
===== Custom Command Hotkeys =====&lt;br /&gt;
Practically any functionality can be added to custom hotkey definitions. This might be a bit advanced topic, but let's show few definitions which will improve the usability.&lt;br /&gt;
&lt;br /&gt;
A new Ambient hotkey can be created by clicking the Add a Hotkey button. The first text field is for the name of the hotkey and it can be anything. The second text field is the actual keyboard combination to activate a function. The Edit Command button is used to define what actually happens when you press the hotkey in Ambient.&lt;br /&gt;
&lt;br /&gt;
Let's create two hotkeys which can be used to copy selected files' names as text to the clipboard, with and without the preceding path.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Copy name with path''' and the hotkey combination to '''ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si FULLPATH''', and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
* Click the '''Add a Hotkey''' button again, define the name as '''Copy name''' and the hotkey combination to '''rshift ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si''', and press the enter key. Click the '''Ok''' button, save the Ambient settings, and you're done.&lt;br /&gt;
&lt;br /&gt;
If you now select any files on an Ambient window and press the ''ralt c'' key combination, the selected file names with their full paths get copied to the clipboard and are available to be pasted to any other application. The ''rshift ralt c'' combination copies pathless file names to the clipboard.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Keyboard1.png|320px]] [[File:GettingStarted_Ambient_Settings_Keyboard2.png|320px]] [[File:GettingStarted_ActionEditor1.png|214px]]&lt;br /&gt;
&lt;br /&gt;
Another example which will extract any selected archive file to the ram disk with the ''lshift control e'' combination.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Extract to RAM''' and the hotkey combination to '''lshift control e'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Leave the action type to '''AmigaDOS''', type in the command '''XADUnFile &amp;amp;#37;sp RAM:''' , and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Screenbar Modules ===&lt;br /&gt;
&lt;br /&gt;
[[Screenbar_Modules | Screenbar modules]] are plugins which can populate the empty area on the screen title bar with some useful information and functionality. The modules are visible on every (MUI) [[Fundamentals_of_MorphOS#Screens | screen]], which makes them more useful than, for example, Panel Objects. Panel Objects are only seen on the Ambient screen and can be left under some other windows more easily.&lt;br /&gt;
&lt;br /&gt;
Screenbar modules can be enabled and disabled from the screen depth gadget menu. The menu also contains options to arrange order of the modules and to change their settings. The menu can be accessed by right clicking, or with a long left press, over the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget | screen depth gadget]].&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Menu.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Let's have a look at how to configure a few modules. Enable the '''CPU Monitor''', '''Drivelamps''', and '''Memory''' modules by, for example, multiselecting them at once. Reopen the screen depth gadget menu, select the '''Settings...''' option, and select CPU Monitor from the settings list. The CPU Monitor module is a bit narrow by default, so let's increase its width a little.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_CPU_Monitor.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Drivelamps module has more configuration options. Enable the '''Show lamp''' option for '''usbscsi.device''' if you want to see access indicators for both HD and USB drives. The default look doesn't seem to be that good for two lamps, but you can tune it a bit. Disabling the frame from the Look group (select None) and selecting the recessed frame for the Lamp Look group does some wonders already. You can also adjust the spacing options, if the lamps don't seem to match with the height of the CPU Monitor or other modules.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Drivelamps.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Memory module shows free memory in percents by default, but it can be changed to other types too. Click the popup button on the '''Information''' line to see the options. The information line can have any text, and for example a ''&amp;amp;#37;mfMB free'' line would show free memory in megabytes followed by the &amp;quot;MB free&amp;quot; text.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Memory.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== MUI Settings ===&lt;br /&gt;
&lt;br /&gt;
MUI is the default GUI toolkit of MorphOS and its looks and behaviour can be changed in almost every aspect. Its basic philosophy is to ''offer as much freedom as possible to users by taking away as much work as possible from programmers''. A user can modify the looks of MUI programs very drastically both globally and per program. It can be done by changing single settings or by loading complete themes (presets).&lt;br /&gt;
&lt;br /&gt;
The most important thing for a new user is to understand the difference between the global settings and settings of individual programs.&lt;br /&gt;
&lt;br /&gt;
The global settings are the default settings which will apply to any program using MUI. The global settings can be changed by selecting the '''Settings-&amp;gt;MUI...''' option from the Ambient's pulldown menus or by double clicking the '''SYS:Prefs/MUI''' icon.&lt;br /&gt;
&lt;br /&gt;
Each MUI program can also have its own MUI settings which will override the global settings, but be careful when changing for example the looks of an individual program. If you decide to change the global theme later, the changes made to the individual programs might not fit the global theme anymore. The MUI settings of a program can be found on its pulldown menu or from the window's [[Fundamentals_of_MorphOS#Window_border_gadgets | popup gadget]] menu. Ambient's MUI settings are found from the '''Settings-&amp;gt;Ambient MUI...''' option in the Ambient's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Let's change a couple of options in the global MUI settings as an example. Open the global MUI settings window.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_MUI_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
The default ghosting effect for buttons is a bit old-fashioned raster effect and it will look much better with just reduced visibility. Select the Buttons page and click the None option for the ghosted gadgets. The visibility can be changed with the slider below, but the default value will be fine too. You'll see the changes in real time on any MUI program, the Test button is a bit obsolete with the latest MUI. I also like to make the Active Gadgets Border a bit smaller than the original size. Click the Save button when you're satisfied.&lt;br /&gt;
: [[File:GettingStarted_MUI_Settings_Buttons.png|380px]]&lt;br /&gt;
&lt;br /&gt;
The Settings button in the top left corner opens a popup menu with options to reset the settings or load different presets.&lt;br /&gt;
&lt;br /&gt;
All MUI settings get saved to the ENVARC:MUI/ directory. If you mess too much with settings for individual programs, the last resort to revert the settings to default is to remove the corresponding settings files from that directory or restore them from a backup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hiding the Boot Image Partition on Macs ===&lt;br /&gt;
&lt;br /&gt;
On Macs you'll have a small HFS formatted partition which contains a few files needed to boot the system. The files are only used by [[Dictionary_of_Terms | Open Firmware]] at boot time and the user or MorphOS itself don't normally need them for anything. Open Firmware, as well as the MorphOS update wizard, can access the partition even if it's not mounted on MorphOS. If we disable the auto mounting of it, our desktop will look a bit cleaner and the crucial boot files will then be safe from accidents as well.&lt;br /&gt;
&lt;br /&gt;
Launch the [[Tools/HDConfig]] program and click on the small HFS partition. Its name should be '''DH0:''' if the system is installed with the default partition layout. Disable the '''Automatically mount partition''' option and click the '''OK''' button.&lt;br /&gt;
: [[File:GettingStarted_HDConfig1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button which is in the red area on the left side and accept the changes.&lt;br /&gt;
: [[File:GettingStarted_HDConfig2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Next time you boot the system, the partition isn't shown on the desktop. If you need to access it later for some reason, it can be mounted temporarily with the [[Tools/Mounter]] tool.&lt;br /&gt;
: [[File:GettingStarted_Ambient2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging the Drive Icons ===&lt;br /&gt;
The drive icons can be dragged to a different order and then saved to their positions by selecting the '''Snapshot''' option from the right click contextual menu. If the Ram Disk icon is dragged to the leftmost position and snapshot, it will appear at that position after a reboot and unsnapshot icons appear next to it.&lt;br /&gt;
: [[File:GettingStarted_Drive_Icons.png|320px]] [[File:GettingStarted_Drive_Icons_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installing, Updating, and Configuring Essential Software ==&lt;br /&gt;
&lt;br /&gt;
=== Checking the Network Connection ===&lt;br /&gt;
&lt;br /&gt;
Before continuing to installing new software, let's check if your machine is properly connected to the Internet.&lt;br /&gt;
&lt;br /&gt;
Open the shell by selecting the '''Ambient-&amp;gt;New Shell...''' option from the Ambient's pulldown menus, or by pressing '''rcommand n''' keyboard combination or doubleclicking the '''SYS:Tools/MUI Shell''' icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_New_Shell.png]]&lt;br /&gt;
&lt;br /&gt;
Check the Internet connection by pinging some hostname on the Internet. Type for example '''ping www.google.com''' on the shell window. If you get replies from the host, the connection is OK and you can proceed by pressing '''CTRL C''' to quit the Ping command and closing the shell window. If you don't get any replies with time values, quit the pinging by the CTRL C combination and read the [[Configuring_Network | Configuring a Network Connection]] tutorial.&lt;br /&gt;
: [[File:GettingStarted_Ping.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Grunch ===&lt;br /&gt;
&lt;br /&gt;
[http://geit.de/eng_grunch.html Grunch] is an advanced software package manager, which can install, update, and uninstall software. It's a good starting point for new users and I'd advice everyone to check what it has to offer before visiting [[Links#File_Repositories | other sites]] for more software.&lt;br /&gt;
&lt;br /&gt;
Start Odyssey Web Browser from '''SYS:Applications/OWB/OWB''' and download Grunch from its [http://geit.de/eng_grunch.html homepage] or from the [http://morphos-files.net/find.php?find=grunch MorphOS Files] site. Save the '''Grunch.lha''' archive file to any location, for example to Work partition or to Ram Disk. The archive isn't needed after the installation.&lt;br /&gt;
: [[File:GettingStarted_OWB4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Close the browser and use Ambient to browse to the location where you saved the Grunch.lha file. If you don't see the file, click the rightmost cycle gadget on the window to show all files. Double click the archive, open the Grunch directory, and double click the '''Grunch.install''' file to start the installer script. Running an installer directly from the unpacked archive is a bit of a shortcut which might not work with all programs, but let's demonstrate it anyway. The traditional and more failproof way would be to unpack an archive file to a temporary location and then run the installer script from an unarchived directory. Read more about installing third party software [[Installing_software | here]].&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Next''' button and select the destination location. The '''System:Applications''' path is OK unless you want to keep the bundled software and 3rd party software strictly separated. In that case you could make a new Applications directory on the Work partition, for example.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After the installation has finished, browse to the location where you installed the program and double click the '''Grunch''' icon. Grunch starts, but you'll have to wait a little while it does its initial checks and updates.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Start.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Before using the program any further, check the Grunch preferences. Select the '''Settings-&amp;gt;Grunch...''' option from the pulldown menus and open the '''Miscellaneous''' tab. I'd change the '''Temporary Directory''' path to somewhere else than to your system partition. If you have enough memory, you could have it even on the Ram Disk, but a temporary directory on the Work partition would be a safe bet.&lt;br /&gt;
&lt;br /&gt;
Click the file requester button at the end of the line to browse to the wanted location. The ''':''' button shows the available volumes, and you can also create new directories from the right click contextual menu on the file requester.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You should check the '''Path''' tab next, and think twice if you want to change them from the default paths. The default paths are OK if you think that all 3rd party and bundled software can reside mixed in the same directories and if you have enough free space on the system partition. But if you like to keep 3rd party and bundled software separated and have the system directories as clean as possible, change the paths now. You could make suitable directories on the Work partition, for instance.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
When you're happy with the settings, click the Save button.&lt;br /&gt;
&lt;br /&gt;
The Grunch icon can also be dragged to a panel for quick access later.&lt;br /&gt;
: [[File:GettingStarted_Dragging_Grunch_to_Panel.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software with Grunch ===&lt;br /&gt;
==== rexxsyslib.library ====&lt;br /&gt;
The rexxsyslib.library file enables the ARexx scripting language support on your system and it should be installed as early as possible. Many programs and their features rely on a working ARexx environment. Select it from the list and click the '''Install''' button on Grunch. You may need a reboot before it'll be in use.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software1.png]]&lt;br /&gt;
&lt;br /&gt;
==== Updating OWB ====&lt;br /&gt;
MorphOS usually comes with a bit old version of the OWB browser and you should check for a newer version. Select OWB from the list and click the '''Check''' button.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software2.png]]&lt;br /&gt;
&lt;br /&gt;
You probably have an old version, so click the '''Update...''' button and wait for it to finish.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software3.png]]&lt;br /&gt;
&lt;br /&gt;
You could also change the mode to Update.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software4.png]]&lt;br /&gt;
&lt;br /&gt;
==== MPlayer ====&lt;br /&gt;
MPlayer is hands down the best video player on MorphOS, just install it. It also works as an audio player with comprehensive support for different formats.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software5.png]]&lt;br /&gt;
&lt;br /&gt;
==== PowerSDL ====&lt;br /&gt;
PowerSDL libraries are required for many software ports from other platforms. It's better to install them as well.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software6.png]]&lt;br /&gt;
&lt;br /&gt;
==== CRABUM ====&lt;br /&gt;
CRABUM lets you to customize the pulldown menus on Ambient. It's quite handy for adding some hidden but quickly available features and shortcuts. We'll need this for some later examples.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software7.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Installed Software ===&lt;br /&gt;
==== Configuring Odyssey Web Browser ====&lt;br /&gt;
Here are few examples or suggestions for the initial configuration of OWB. Do the steps you like.&lt;br /&gt;
===== Downloading More Suitable Fonts for OWB =====&lt;br /&gt;
The fonts provided with MorphOS aren't designed with web usage in mind and it's better to download certain Microsoft fonts for the browser. Luckily it's an easy job to do, because there's a downloader script included in the OWB's directory.&lt;br /&gt;
&lt;br /&gt;
Open the '''SYS:Applications/OWB''' directory and double click the '''Download Fonts''' icon. Note: if the script doesn't seem to work, try [http://www.morphos-storage.net/?page=Network/Web&amp;amp;file=Download_Fonts_for_OWB.lha this one] instead.&lt;br /&gt;
: [[File:GettingStarted_OWB1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Yes''' on the requester and wait patiently for  the downloading and installing of the fonts. The output window closes when the process is finished.&lt;br /&gt;
: [[File:GettingStarted_OWB2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
OWB initializes the fonts on the first run, but it will start much quicker next time.&lt;br /&gt;
: [[File:GettingStarted_OWB3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Making OWB to Use Its Own Screen =====&lt;br /&gt;
A browser is usually an application people want to use in a full size window and on Amigaish systems it makes sense to put it on its own screen. When used on a separate screen it leaves more space for other programs on the Ambient screen, and you don't have such a hassle when handling them all. Bringing screens to front is also a very quick operation, you'll never see any slowdowns like on other systems where you reopen full size windows from taskbars, for example.&lt;br /&gt;
&lt;br /&gt;
You could send a program to a new screen with the &amp;quot;Jump to Screen -&amp;gt; New&amp;quot; option from the window popup gadget, but it's mainly designed for temporary usage. Let's do the configuration more proper way instead.&lt;br /&gt;
&lt;br /&gt;
Launch OWB, click on the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]], and select '''MUI Settings...'''. Another way to access the MUI settings would be from the '''Settings-&amp;gt;MUI...''' pulldown menu option when OWB's window is active.&lt;br /&gt;
: [[File:GettingStarted_OWB5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the '''Screen''' page, select the '''customized public screen from MUI screen database''' option, and click the '''New...''' button.&lt;br /&gt;
&lt;br /&gt;
The Edit Screen window opens. The name field is for the screen name and the title field for the screen title text. They can be anything you want, but it's better to keep them informative. '''OWB''' would be a good screen name now and '''Odyssey Web Browser''' for the title. Check if the default screen mode is what you want. Be also sure that the '''Close automatically''' option is enabled.&lt;br /&gt;
&lt;br /&gt;
It might be a good idea to disable the '''Enhanced Display''' option, because it doesn't give that much advantage with full screen applications. Graphics memory usage will also be lower, and it might be crucial to save some graphics memory on systems with less than 128 MB memory on the graphics card. Read more about how to reduce graphics memory usage [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
Click the '''Ok''' button on the Edit Screen window and the '''Save''' button on the MUI Settings window.&lt;br /&gt;
&lt;br /&gt;
Note: this method can be used with all MUI programs to put them on their own screens, from shell windows to small utilities, bigger applications, and games. I prefer to use the [[Applications/Showgirls|ShowGirls]] image viewer and other bigger applications on their own screens. Several MUI programs can also share the same custom screen, as it isn't limited just to a program per screen. You could for example group some network programs to one screen, and some other programs to another screen, etc.&lt;br /&gt;
: [[File:GettingStarted_OWB6.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The OWB window doesn't probably have optimal size and position on the newly created screen. Right click over the [[Fundamentals_of_MorphOS#Window_border_gadgets | zoom gadget]] and select the '''Maximize''' option or if you configured the zoom gadget as suggested [[Getting_Started#Screens_and_Desktop | earlier]], click the zoom gadget twice. The maximize option leaves the screen title bar visible, but otherwise resizes the window to full screen size. Select the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]] to save the window position permanently.&lt;br /&gt;
: [[File:Tips_Zoommenu.png|top]] [[File:GettingStarted_OWB7.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Open PDF Files Automatically =====&lt;br /&gt;
OWB's MIME Types settings can be used to configure automatic actions to files of certain types. Here is an example of how to show PDF files automatically with the [[Applications/VPDF|VPDF]] application when clicked on the browser.&lt;br /&gt;
&lt;br /&gt;
Open OWB's settings from the '''Settings-&amp;gt;Preferences...''' pulldown menu option and select the '''MIME Types''' page. Click the '''Add''' button and fill in the information below like this:&lt;br /&gt;
 MIME Type: '''application''' / '''pdf'''&lt;br /&gt;
 Extension: '''pdf'''&lt;br /&gt;
 Action: '''External Viewer''', Viewer: '''SYS:Applications/VPDF/VPDF''', and the last unnamed field: '''&amp;amp;#37;f'''&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button.&lt;br /&gt;
&lt;br /&gt;
If you now click a PDF file on a web page, the file is downloaded to a temporary location and shown on VPDF automatically.&lt;br /&gt;
: [[File:GettingStarted_OWB8.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Getting YouTube Videos to Play Better on the Browser Window =====&lt;br /&gt;
YouTube videos should play on OWB by default, but there are a thing or two to note.&lt;br /&gt;
&lt;br /&gt;
Playing videos in a small embedded window is a very CPU intensive task and not quite smooth on most systems. Moving the video playback from the embedded mode to the overlay mode helps the task hugely. This can be achieved with the YouTube Fullscreen Fix script. Videos will be shown in a nearly fullscreen window using the overlay functions and the CPU load may drop from 100&amp;amp;#37; even to 30&amp;amp;#37; on a G4 system, resulting in perfectly smooth playback of course.&lt;br /&gt;
&lt;br /&gt;
'''Download''' the latest script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js (YouTube changes its internals randomly and that's why the script on the MorphOS ISO is probably old already. Grunch also may have an old version and manual installation is highly advisable).&lt;br /&gt;
&lt;br /&gt;
Copy the downloaded script to the '''System:Applications/OWB/Scripts''' directory.&lt;br /&gt;
: [[File:GettingStarted_OWB9.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Scripts window from the '''Windows-&amp;gt;Scripts...''' pulldown menu entry on OWB.&lt;br /&gt;
: [[File:GettingStarted_OWB10.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Add''' button on the Scripts window and select the YouTube_Fullscreen_Fix.js file.&lt;br /&gt;
: [[File:GettingStarted_OWB11.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Make sure that the '''Enable''' setting is chosen and close the window. A '''restart''' of the browser is needed to activate the script, but after that you should be able to get any YouTube video to the smooth fullscreen mode by clicking the &amp;quot;fullscreen&amp;quot; or &amp;quot;large player&amp;quot; buttons on the video '''after the video playback has started'''. If you're watching a video embedded on some other external site, click the settings button instead. '''Double click''' the fullscreen video to get it to the embedded mode again.&lt;br /&gt;
: [[File:GettingStarted_OWB12.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Content Blocking and YouTube =====&lt;br /&gt;
If you have enabled the Content Blocking (AdBlock) option on the OWB settings, YouTube videos with ads will also get blocked. You can make a rule to the content blocking settings to allow those videos to be shown.&lt;br /&gt;
&lt;br /&gt;
Open '''Windows-&amp;gt;Content Blocking...''' from OWB's pulldown menus, click the '''Add''' button, and write '''youtube.com''' to the Rule line, and close the window.&lt;br /&gt;
: [[File:OWB_ContentBlockingYT.png]]&lt;br /&gt;
&lt;br /&gt;
If you have any other problems with the YouTube playback, check the [[Tips_and_Tricks#Problems_with_YouTube_Videos|Tips and Tricks]] page for more information.&lt;br /&gt;
&lt;br /&gt;
===== Configuring Fonts =====&lt;br /&gt;
&lt;br /&gt;
Browsers come with font settings. However, these settings are often neglected. Web developer has at least three options for selecting a font which would be displayed by default on your browser screen. &lt;br /&gt;
It can be a generic font, &amp;quot;hand picked&amp;quot; local font-family, or on-the-fly downloaded web font. Nevertheless the user still has the choice which font he or she actually wants to use. Reasons: privacy, security, speed, aesthetic.&lt;br /&gt;
&lt;br /&gt;
MorphOS is bundled with True Type, PostScript and Amiga Bitmap fonts.&lt;br /&gt;
OWB uses fontconfig for font handling. Fonts are cached whenever a change in font directories is detected.&lt;br /&gt;
If you want to use your fonts exclusively - fonts.conf should only use the path where you store the fonts (for example '''SYS:Fonts/_ttf''').&lt;br /&gt;
&lt;br /&gt;
Fontconfig is a library providing font configuration, customization and application access. It uses freetype library which supports plenty of font formats (excluding Amiga Bitmap fonts).&lt;br /&gt;
Presets are stored in the '''MOSSYS:Fontconfig/conf.avail''' directory.&lt;br /&gt;
&lt;br /&gt;
'''FONTS:Fontconfig/fonts.conf''' (configured font dirs)&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;!-- Font directory list --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;SYS:Fonts/_pcf&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;SYS:Fonts/_pfb&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pcf&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pfb&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_ttf&amp;lt;/dir&amp;gt; --&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Example settings:'''&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/conf.d/51-local.conf'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
	&amp;lt;!-- Load local system customization file --&amp;gt;&lt;br /&gt;
	&amp;lt;include ignore_missing=&amp;quot;yes&amp;quot;&amp;gt;local.conf&amp;lt;/include&amp;gt;&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/local.conf''' (turns off antialias for font sizes smaller than 16 and disables autohint)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;!-- /etc/fonts/local.conf file for local customizations --&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;size&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;pixelsize&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;autohint&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Blocking fonts'''&lt;br /&gt;
&lt;br /&gt;
In OWB, go to '''Settings-&amp;gt;Fonts''' and choose default fonts and sizes.&lt;br /&gt;
&lt;br /&gt;
To disable remote web fonts this line needs to be added to its filter '''SYS:Applications/OWB/Conf/blocked.prefs''':&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
/\.ttf|\.otf|\.woff|\.woff2\?/&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
A specific font can be whitelisted too:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
@@/*actually-nice-font.ttf&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
This isn't ideal. OWB will try block anything_not_whitelisted.ttf, even if you look for a nicefont.ttf in Google Search.&lt;br /&gt;
&lt;br /&gt;
==== Configuring MPlayer ====&lt;br /&gt;
===== General Options =====&lt;br /&gt;
The default configuration of MPlayer is quite fine, but here are a few options I like to set myself. Start MPlayer in the GUI mode by double clicking the GMPlayer icon in the MPlayer directory. There's just one MPlayer executable, but two icons with different [[Fundamentals_of_MorphOS#Icon_Tool_Types|tooltypes]] to start the program with or without the GUI mode.&lt;br /&gt;
&lt;br /&gt;
With default options MPlayer scales the played video to fit the current window dimensions which typically leaves big empty borders around the video. To get the window dimensions to change with the video dimensions, select the '''Video-&amp;gt;Window Dimension-&amp;gt;100&amp;amp;#37;''' option, and '''Settings-&amp;gt;Save''' to save it as a default setting.&lt;br /&gt;
: [[File:GettingStarted_MPlayer.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Preferences window by selecting the '''Settings-&amp;gt;Preferences...''' option from MPlayer's pulldown menus. There are some settings to consider.&lt;br /&gt;
&lt;br /&gt;
The Audio Driver has two audio output options for AHI to choose from. The default '''ahi''' option outputs the audio through the ''Music Unit'', which gives the best audio quality, but blocks simultaneous audio from any other sources. The '''ahi_dev''' option uses the device mode which can be shared with the other sources, but it results in a slight decrease in the audio quality. So, if you want to be able to watch videos while some other program, like a music player, would still continue with audio output, select the '''ahi_dev''' option.&lt;br /&gt;
&lt;br /&gt;
If you don't like any usage data gathering, disable the '''Remember last visited path''' option :)&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Preferences.png]]&lt;br /&gt;
&lt;br /&gt;
===== Setting MPlayer as the Default Player on Ambient  =====&lt;br /&gt;
MorphOS doesn't have any default player for videos and double clicking a video file from Ambient results in an error requester. MPlayer can be set as the default video player by editing the Ambient MIME type settings.&lt;br /&gt;
&lt;br /&gt;
Open the '''Ambient Settings''' window and the '''Mime''' page. With the built-in MIME editor you can add different kinds of actions for different file formats or classes. Let's add MPlayer as the default player for all video files, not just for some individual video formats.&lt;br /&gt;
&lt;br /&gt;
Select '''video''' from the right-hand side list tree and click the '''Edit''' button. Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
&lt;br /&gt;
In the Action Editor window type a name for the action, for example '''Play''', and click the '''Add''' button on that window too.&lt;br /&gt;
&lt;br /&gt;
Change the AmigaDOS command to '''Run &amp;gt;NIL: SYS:Applications/MPlayer/MPlayer -gui 1 &amp;amp;#37;sp''' (change the path to the MPlayer executable if you have it in a different location) and change the Event type to '''DoubleClick'''. Note: the ''-gui 1'' option, which starts MPlayer in the GUI mode, has to be written in lower case, having it in upper case doesn't work!&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Adding_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Ok''', '''Ok''', and '''Save''' buttons.&lt;br /&gt;
&lt;br /&gt;
If you now double click a video file in Ambient, it gets played on MPlayer. You can also see the Play option in the contextual menu when right clicking the video file.&lt;br /&gt;
: [[File:GettingStarted_MPlayer2.png|320px]] [[File:GettingStarted_MPlayer_Working_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You can add several actions as contextual menu events if you want to have more options for opening videos. Only imagination is the limit, and you can for example have contextual menu entries to start MPlayer playback with filters skipped (use the ''-lavdopts skiploopfilter=all'' option to speed up the video playback a little) and have an option to convert the video with mencoder etc.&lt;br /&gt;
: [[File:GettingStarted_ActionEditor2.png|230px]]&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with FlowStudio ====&lt;br /&gt;
&lt;br /&gt;
Custom menus in Ambient can be added with a lua script. Menus can be edited and reloaded via respective menu items.&lt;br /&gt;
&lt;br /&gt;
'''SYS:WBStartup/menus.lua''' script:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
require('ipc')&lt;br /&gt;
address('AMBIENT')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m1-0&amp;quot;						title=&amp;quot;Tools&amp;quot;			type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-1&amp;quot;		parentid=&amp;quot;m1-0&amp;quot;		title=&amp;quot;MUICON&amp;quot;			type=item shortcut=&amp;quot;S&amp;quot; command=&amp;quot;*&amp;quot;SYS:Tools/MUI Shell*&amp;quot;&amp;quot;						commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-2&amp;quot;		parentid=&amp;quot;m1-0&amp;quot;		title=&amp;quot;Snoopium&amp;quot;			type=item command=&amp;quot;SYS:Tools/Snoopium&amp;quot;									commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-3&amp;quot;		parentid=&amp;quot;m1-0&amp;quot;		title=&amp;quot;&amp;quot;				type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-4&amp;quot;		parentid=&amp;quot;m1-0&amp;quot;		title=&amp;quot;Mounter&amp;quot;			type=item command=&amp;quot;SYS:Tools/Mounter&amp;quot;									commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-5&amp;quot;		parentid=&amp;quot;m1-0&amp;quot;		title=&amp;quot;HDConfig&amp;quot;			type=item command=&amp;quot;SYS:Tools/HDConfig&amp;quot;									commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6&amp;quot;		parentid=&amp;quot;m1-0&amp;quot;		title=&amp;quot;&amp;quot;				type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-7-0&amp;quot;	parentid=&amp;quot;m1-0&amp;quot;		title=&amp;quot;Menu&amp;quot;			type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-7-1&amp;quot;	parentid=&amp;quot;m1-7-0&amp;quot;	title=&amp;quot;Edit&amp;quot;				type=item command=&amp;quot;SYS:Applications/FlowStudio/FlowStudio SYS:WBStartup/menus.lua&amp;quot;	commandtype=amigados')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-7-2&amp;quot;	parentid=&amp;quot;m1-7-0&amp;quot;	title=&amp;quot;Reload&amp;quot;			type=item command=&amp;quot;RXCmd AMBIENT *&amp;quot;menu remove*&amp;quot; &amp;amp;&amp;amp; LuaX SYS:WBStartup/menus.lua&amp;quot;	commandtype=amigados')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m2-0&amp;quot;						title=&amp;quot;Apps&amp;quot;				type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-1&amp;quot;		parentid=&amp;quot;m2-0&amp;quot;		title=&amp;quot;FlowStudio&amp;quot;			type=item shortcut=&amp;quot;W&amp;quot; command=&amp;quot;Run &amp;gt;NIL: SYS:Applications/FlowStudio/FlowStudio&amp;quot;		commandtype=amigados')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-2&amp;quot;		parentid=&amp;quot;m2-0&amp;quot;		title=&amp;quot;&amp;quot;				type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-3&amp;quot;		parentid=&amp;quot;m2-0&amp;quot;		title=&amp;quot;OWB&amp;quot;				type=item shortcut=&amp;quot;B&amp;quot; command=&amp;quot;SYS:Applications/OWB/OWB&amp;quot;						commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-4&amp;quot;		parentid=&amp;quot;m2-0&amp;quot;		title=&amp;quot;Transfer&amp;quot;			type=item command=&amp;quot;SYS:Applications/Transfer/Transfer&amp;quot;							commandtype=workbench')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m3-0&amp;quot;						title=&amp;quot;Utils&amp;quot;				type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-1&amp;quot;		parentid=&amp;quot;m3-0&amp;quot;		title=&amp;quot;MUIProCalc&amp;quot;		type=item command=&amp;quot;SYS:Utilities/MUIProCalc&amp;quot;									commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-2&amp;quot;		parentid=&amp;quot;m3-0&amp;quot;		title=&amp;quot;&amp;quot;				type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-3&amp;quot;		parentid=&amp;quot;m3-0&amp;quot;		title=&amp;quot;Zoom&amp;quot;			type=item shortcut=&amp;quot;Z&amp;quot; command=&amp;quot;SYS:Utilities/Zoom&amp;quot;							commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-4&amp;quot;		parentid=&amp;quot;m3-0&amp;quot;		title=&amp;quot;&amp;quot;				type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-5&amp;quot;		parentid=&amp;quot;m3-0&amp;quot;		title=&amp;quot;AudioRecorder&amp;quot;		type=item command=&amp;quot;SYS:Utilities/AudioRecorder&amp;quot;								commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-6&amp;quot;		parentid=&amp;quot;m3-0&amp;quot;		title=&amp;quot;JukeBox&amp;quot;			type=item shortcut=&amp;quot;J&amp;quot; command=&amp;quot;SYS:Utilities/JukeBox&amp;quot;							commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-7&amp;quot;		parentid=&amp;quot;m3-0&amp;quot;		title=&amp;quot;&amp;quot;				type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-8&amp;quot;		parentid=&amp;quot;m3-0&amp;quot;		title=&amp;quot;GraphicsBoards&amp;quot;		type=item command=&amp;quot;SYS:Utilities/GraphicBoards&amp;quot;								commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-9&amp;quot;		parentid=&amp;quot;m3-0&amp;quot;		title=&amp;quot;TaskManager&amp;quot;		type=item shortcut=&amp;quot;T&amp;quot; command=&amp;quot;SYS:Utilities/TaskManager&amp;quot;						commandtype=workbench')&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Create .info icon for menus.lua''':&lt;br /&gt;
&lt;br /&gt;
'''Copy ENV:SYS/def_tool.info SYS:WBStartup/menus.lua.info'''&lt;br /&gt;
&lt;br /&gt;
'''Set icon info''':&lt;br /&gt;
&lt;br /&gt;
Select menus.lua and open its Information window (COMMAND I). Set Type as a '''Project''', write '''LuaX''' as a Default Tool and press '''Save'''.&lt;br /&gt;
&lt;br /&gt;
Now you can run menus.lua script and enjoy Ambient menus.&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with CRABUM ====&lt;br /&gt;
&lt;br /&gt;
You can add custom pulldown menus to Ambient with ARexx scripts created by the CRABUM program. It's a good way to launch programs or scripts which you don't want to have on panels. Installation of [[Getting_Started#rexxsyslib.library|rexxsyslib.library]] is required.&lt;br /&gt;
&lt;br /&gt;
Let's create an Edit menu with options to edit different system startup scripts. Double click the CRABUM icon from the SYS:Utilities/CRABUM directory if you installed it with the default options.&lt;br /&gt;
&lt;br /&gt;
# Click the '''Menu''' button to add a new menu and change its title to '''Edit'''.&lt;br /&gt;
# Click the '''Item''' button to add a new item under the created menu.&lt;br /&gt;
# Type '''User-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-startup''' to the AmigaDOS command line. &amp;quot;Run &amp;gt;NIL:&amp;quot; starts the Ed program as a background process and it won't block Ambient while it is running.&lt;br /&gt;
# Create an another item by clicking the '''Item''' button.&lt;br /&gt;
# Type '''User-network-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-network-startup''' to the AmigaDOS command line.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM1.png|320px]]&lt;br /&gt;
# Click the '''Save''' button to save the resulting ARexx script.&lt;br /&gt;
# If you save the file to the SYS:WBStartup drawer, it will be launched automatically at boot time. Enter a suitable name for the file, for example '''Edit-menu'''. Click the '''Ok''' button.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After a reboot (or doubleclicking of the file) you'll have the new Edit menu on the Ambient pulldown menus and you can easily open the system files for editing.&lt;br /&gt;
: [[File:GettingStarted_CRABUM3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
== More Configuring ==&lt;br /&gt;
=== Synchronizing the Clock with an Internet Time Server ===&lt;br /&gt;
The system clock can be synchronized manually from the MorphOS Preferences application by clicking the '''Set date and time using the Internet''' button in the Time preferences.&lt;br /&gt;
: [[File:MorphOS_Preferences_Time.png|320px]]&lt;br /&gt;
&lt;br /&gt;
There's also the [[Shell_Commands/SetClockNTP|SetClockNTP]] shell command which can be launched manually or automatically at boot time. To synchronize the time every time the system starts edit the '''S:user-network-startup''' file and remove the semi-colon from the SetClockNTP line.&lt;br /&gt;
&lt;br /&gt;
To edit the S:user-network-startup file open the shell (or the Execute Command prompt) and type '''Ed S:user-network-startup''', or open the System partition, select the '''All Files''' mode, browse to the '''S''' directory and select the '''Edit...''' option from the right click contextual menu. Or if you configured the Edit menu with CRABUM earlier, use it now.&lt;br /&gt;
: [[File:GettingStarted_Enable_SetClockNTP.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Shell ===&lt;br /&gt;
==== Editing the Shell-startup file ====&lt;br /&gt;
The shell can be customized with the shell-startup file, but by default the file is only found in a MorphOS system directory where the user shouldn't do any modifications. It must be copied to a user directory first to make any changes to it. Open a new shell window and type '''Copy MOSSYS:S/shell-startup SYS:S/shell-startup''', and then edit it for example with the '''Ed SYS:S/shell-startup''' command. The shell-startup file is executed every time a new shell window is opened.&lt;br /&gt;
: [[File:GettingStarted_shell-startup.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Adding Paths ====&lt;br /&gt;
There are some useful shell commands around the installed system which aren't in the system's search path and thus you'll have to enter their complete paths when using them. Adding their locations to the search path allows them to be run just by their names, which is much more convenient.&lt;br /&gt;
&lt;br /&gt;
Here are few suggestions to add to the '''SYS:S/shell-startup''' file (remember the previous step first!). Or if you want them to be available globally on all occasions, they can be added to the '''S:user-startup''' file instead.&lt;br /&gt;
* '''Path SYS:Applications/RemoteShell/Files ADD''' adds SSH related commands like scp, sftp, ssh, etc to the search path. Note: use the [[Applications/RemoteShell|Remote Shell]] application for regular SSH sessions, because it supports arrow keys and other things better.&lt;br /&gt;
* '''Path SYS:Applications/OWB/Datas ADD''' adds wget to the search path.&lt;br /&gt;
* '''Path SYS:Applications/MPlayer ADD''' adds MPlayer and mencoder to the search path if you have installed MPlayer. Change the path if you have installed it elsewhere.&lt;br /&gt;
&lt;br /&gt;
==== Configuring the GUI ====&lt;br /&gt;
There are many buttons and hotkeys to add to the shell window besides the default ones. Check the preferences by selecting the '''Settings-&amp;gt;Edit Prefs...''' option from the Shell's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Available functions can be dragged to '''Hotkeys''' or '''Buttons''' lists and the changes are seen in real time in the shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You may also want to set the default window size and position for new shell windows on the '''Settings''' tab. Click the '''Get from window''' button to get values from the current shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Remember to save the modifications in the '''Settings''' menu.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Setting Jukebox as the Default Player for MP3 Files ===&lt;br /&gt;
If you double click an MP3 file in an Ambient window, it is played with the very simple internal player. Here are two solutions to change the default player to the more advanced [[Utilities/Jukebox|Jukebox]] music player. Ambient's internal player is still left to the context menu as an option.&lt;br /&gt;
==== Simple Solution ====&lt;br /&gt;
A simple solution is just to create a new mpeg audio MIME type definition which just launches the Jukebox player with the double clicked filename as an argument.&lt;br /&gt;
# Open the Mime page in the Ambient settings, select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''Run &amp;gt;NIL: SYS:Utilities/Jukebox &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and you should see this in the MIME Editor window.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Save''' buttons. If you double click an MP3 file now, Jukebox starts and plays the clicked file. There are also two entires in the right click contextual menu and the option which is used for the double click action is written in bold.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Advanced Solution ====&lt;br /&gt;
An advanced solution is to use the third party [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script. It will give more flexible options to add files to Jukebox, and we'll learn how to add submenus into context menus. There are shortcuts to install the script if you read the documentation in the archive, but let's do this manually to learn the configuration method better. It will be helpful in the future when configuring any other filetypes.&lt;br /&gt;
&lt;br /&gt;
# Download the script archive from [http://aminet.net/package/mus/play/JukeboxAdder Aminet] or from [http://morphos-files.net/find.php?find=jukeboxadder MorphOS Files].&lt;br /&gt;
# Copy the '''jukeboxadder.lua''' file from the archive to the '''SYS:S/''' directory.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder1.png|320px]]&lt;br /&gt;
# Open the '''Mime''' page in the '''Ambient settings''', select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua PLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and then click '''Add''' again in the MIME Editor window to create more ways to add files to Jukebox from the context menus.&lt;br /&gt;
# Type '''Add to Jukebox''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua ADD &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string. This will create a submenu named ''Jukebox'' in the context menu and place the new ''Add to Jukebox'' option there.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Add''' once again to create the last entry.&lt;br /&gt;
# Type '''Add to Jukebox and Play''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''MOSSYS:C/LuaX S:jukeboxadder.lua ADDPLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder4.png|320px]]&lt;br /&gt;
# Click '''Ok''', '''Ok''', and '''Save'''. Now you can see more options in the context menu for MP3 files and double clicking will always clear the previous songs and play the new song immediately.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
It is also possible to add the same functionality for context menus of directories if you want to be able to add whole directories to Jukebox at once. There's a special '''internal -&amp;gt; x-morphos-globalaction-directory''' MIME type which can be used to add context menu entries for all directories. Repeat the previous steps (6-18) for it, but make all '''Event types''' to use the '''Menu''' option (in step 9 too).&lt;br /&gt;
: [[File:GettingStarted_JukeboxAdder6.png|320px]] [[File:GettingStarted_JukeboxAdder7.png|320px]] [[File:GettingStarted_JukeboxAdder8.png|320px]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3880</id>
		<title>Getting Started</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3880"/>
				<updated>2018-06-19T19:52:39Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== A Beginner's Guide to MorphOS ==&lt;br /&gt;
&lt;br /&gt;
You have installed MorphOS to a compatible machine, but... now what? You could always go and install a pre-configured package like Chrysalis, but you would end up with a system configured for someone else's taste and you still wouldn't know how to actually use the operating system. If you are in this situation and would like to learn how MorphOS works, this is a tutorial for you! The tutorial will guide you through the things you should do and notice after a fresh install, with practical examples from basic configuration options to installing new software. It won't cover all the details and is just an opinion on how to proceed, but it should give you some knowledge how to continue on your own and make your own decisions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting Comfortable with the User Interface and the Ambient Desktop ==&lt;br /&gt;
=== The First Boot ===&lt;br /&gt;
&lt;br /&gt;
After a boot you're presented with the plain looking Ambient, the desktop environment of MorphOS. The first thing you should learn is to get familiar with the basic usage, and to tune the interface settings so that they won't annoy you. The worst thing is if a user plays around a bit and just curses at the system when it doesn't work as expected or wanted. You aren't forced into just one kind of behaviour with MorphOS!&lt;br /&gt;
: [[File:GettingStarted_Ambient.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Right mouse click is widely used on MorphOS and if you're using a device without a physical button for it, check the tips over [[Tips_and_Tricks#How_to_Use_RMB_with_One-button_Mouse | here]]. Pressing the right mouse button over the Ambient screen opens Ambient's pulldown menus where you can find few important options. For example, options to shut down the system, to open a new shell window, or to open system settings.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Shutdown.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== System Settings ===&lt;br /&gt;
&lt;br /&gt;
The MorphOS Preferences application is used to edit system-wide settings. It can be launched from the Ambient's pulldown menu by selecting the &amp;quot;Settings-&amp;gt;System...&amp;quot; menu option or by browsing to the System:Prefs/ drawer and double clicking the Preferences icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_System_Settings.png]] [[File:GettingStarted_MorphOS_Preferences.png|237px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Screens ====&lt;br /&gt;
&lt;br /&gt;
If MorphOS didn't get the optimal resolution of your monitor with DDC, a different screen mode can be selected from the Screens settings. If the wanted mode isn't seen there, open the Monitors settings instead to create a completely new mode.&lt;br /&gt;
&lt;br /&gt;
If you have a graphics card with a low amount of memory, you can try to make the memory consumption smaller by disabling the Enhanced Display setting (3D accelerated graphics functions for 2D screens) or by reducing the color depth. More information can be found  [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
MorphOS skins (themes for the graphical appearance) can also be changed from the Screens settings.&lt;br /&gt;
&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== IControl ====&lt;br /&gt;
&lt;br /&gt;
IControl settings are the most important settings for the overall user experience. This is the place to look in order to avoid the usual comments like ''&amp;quot;Why doesn't X work like Y in the other OS?&amp;quot;'', ''&amp;quot;Why there isn't a feature Z?&amp;quot;'', ''&amp;quot;I can't use a system like this!&amp;quot;''. Everyone should check these settings first before going any further.&lt;br /&gt;
&lt;br /&gt;
===== Hotkeys =====&lt;br /&gt;
MorphOS has many nice features to use with keyboard shortcuts or mouse buttons, but only few are activated by default. Let's activate more!&lt;br /&gt;
&lt;br /&gt;
To add a new hotkey for the wanted function click the popup button on the right side, select &amp;quot;'''Sample'''&amp;quot;, and press the wanted key combination. The pressed combination is then recorded on the corresponding line and should be shown there. Repeat the procedure if you didn't get it as wanted on the first try. Changed settings will be taken into use after you click the Save or Use button.&lt;br /&gt;
&lt;br /&gt;
Here is how to set the &amp;quot;control left-alt c&amp;quot; key combination to '''center the active window''' on the screen:&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Hotkeys2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Here are some other recommendations to activate, but feel free to use your own preferences for the hotkeys:&lt;br /&gt;
* '''Active Window: To Back''' - double click with middle mouse button to send a window back of other windows.&lt;br /&gt;
* '''Active Window: Zoom''' - &amp;quot;control left-alt m&amp;quot;, to toggle between a maximized and minimized window.&lt;br /&gt;
* '''Active Window: Activate Next''' - &amp;quot;left-command tab&amp;quot;, to have the ''alt-tab'' functionality found on many other operating systems. Using ctrl-tab or alt-tab isn't recommended because they would overlap with the shell's functionality on MorphOS. Command-tab also happens be the same in OS X.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys3.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Note: You can also add several hotkeys for a function by selecting the New Hotkey option from the popup button's menu.&lt;br /&gt;
&lt;br /&gt;
===== Screens and Desktop =====&lt;br /&gt;
&lt;br /&gt;
Important options concerning how windows and menus behave can be found on the Screens and Desktop settings.&lt;br /&gt;
&lt;br /&gt;
I'd recommend turning on the '''Maximize window when clicking on the Zoom gadget''' option. The Zoom gadget will then toggle the window size between full screen (with the screen title bar still visible) and the initial window size and position. I find it much more comfortable than the legacy placement between two obscure positions. The previously configured Zoom hotkey will also work better with this option enabled.&lt;br /&gt;
&lt;br /&gt;
If you prefer being able to drag windows out of the screen without pressing any qualifier key, like on mainstream systems, select the '''When dragging windows... allow them to be placed out of screen, unless Control is pressed''' option.&lt;br /&gt;
&lt;br /&gt;
The default behaviour of the pulldown menus may be a bit unfamiliar for old Amiga users, but there are several options to get them working as expected. I like to disable the '''Menus shall remain opened even when mouse button is released''' option and enable the '''Open menus under mouse pointer outside screen titlebar area''' option.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Touchpad ====&lt;br /&gt;
&lt;br /&gt;
If you're using a laptop system, check the Touchpad setttings. You might want to disable clicking from the pad to avoid any accidental clicks.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Touchpad.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Laptop ====&lt;br /&gt;
&lt;br /&gt;
If you're not a Mac user, you might find it odd that you need to press the fn key when using the function keys for normal activities, and not when modifying, for example, the screen brightness. The '''Press and hold the fn key to modify screen brightness, audio volume, etc.''' option will change the functionality the other way around.&lt;br /&gt;
&lt;br /&gt;
Some systems also have the '''Automatic LCD brightness and keyboard backlight control''' option here. Disable it if you're annoyed by changing lightning.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Laptop.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Windows ===&lt;br /&gt;
&lt;br /&gt;
The first icon you see on the Ambient desktop is the &amp;quot;'''My MorphOS'''&amp;quot; icon. By double clicking it you'll get a window with icons of all volumes and assigns of the system. It works like a root directory with quick access to different locations.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS.png|320px]]&lt;br /&gt;
&lt;br /&gt;
If you find it a bit clumsy to work in the icon mode, like I do, you can change the view to '''the list mode''' from the cycle button on the right side of the window.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
With default settings Ambient doesn't remember the changed mode or other window properties next time you open it, but you can right click the window border or an empty area on the file lister to bring up a contextual window menu and select the &amp;quot;'''Snapshot-&amp;gt;Window'''&amp;quot; option to save the window properties. Default position and size for a window can be saved that way too. If you defined the centering hotkey earlier, you can try it now :)&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The same can also be done for normal directory windows. While &amp;quot;My MorphOS&amp;quot; window settings are exceptionally saved to Ambient's configuration files, normal directories' settings are saved to an icon file (a file with .info extension). If you change and save the mode for the Work: partition for example, you see a disk.info file appearing there.&lt;br /&gt;
: [[File:GettingStarted_Icon_Mode.png|320px]] [[File:GettingStarted_List_Mode_Snapshot.png|320px]] [[File:GettingStarted_List_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Displayed columns can be selected by right clicking the column title area, but modify the [[Getting_Started#Lister|default lister settings]] to your liking before starting to save settings for individual windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Lister_Columns.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Settings ===&lt;br /&gt;
&lt;br /&gt;
Ambient is actually a separate application itself and it has its own settings separated from the general system preferences. The previously mentioned system settings affect all programs and screens, but strictly desktop related settings are found in the Ambient settings. The Ambient Settings window can be opened by selecting the &amp;quot;Settings-&amp;gt;Ambient...&amp;quot; option from Ambient's pulldown menu.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Ambient_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
==== Miscellaneous ====&lt;br /&gt;
&lt;br /&gt;
The Miscellaneous page on the Ambient settings has a nice option to get the My MorphOS window opened when double clicking anywhere on the empty area of the desktop. It really speeds up the working when you don't have to move the mouse a long way to the top corner or dig the icon out from under some other windows. Enable it with the '''Double click on desktop opens MyMorphOS window''' option.&lt;br /&gt;
&lt;br /&gt;
The My MorphOS icon is just wasting space on the desktop after the previous setting and you can hide it by disabling the '''Display MyMorphOS icon''' option.&lt;br /&gt;
&lt;br /&gt;
If you like to have a bit more eye candy on the context menus, you can also enable the '''Show images in context menu''' option while you're here.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Misc.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Lister ====&lt;br /&gt;
The default properties of the list mode of Ambient windows can be changed on the Lister settings. Disable the '''Compact size display''' if you want to see exact file sizes in bytes always. You may also want to select different columns to be shown in the listers by double clicking items on the '''File Properties''' list to set them hidden or shown. '''Date &amp;amp; Time''' instead of just Date would probably be a common choice.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Lister.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Panels ====&lt;br /&gt;
&lt;br /&gt;
Many new users are wondering if there is any kind of dock application on MorphOS, because there isn't any shown by default. MorphOS has ''panels'' for that and you can have as many panels as you want on the desktop, arranged horizontally or vertically. The panels have features like zipping to hide and unhide them, sub panels and other Panel Object plugins, etc. There just isn't any configured by default and user can create a panel or panels how he likes.&lt;br /&gt;
&lt;br /&gt;
To create a new panel, open the Panels page on the Ambient settings and click the '''New Panel''' button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels1.png|320px]]&lt;br /&gt;
An empty panel can be dragged anywhere and you can find some of its settings on the '''Name &amp;amp; Look''' and '''Behaviour''' tabs. If you want to place the panel on a screen border the '''Attached to Borders''' option makes it easier. The '''Alpha''' option controls the transparency of a panel, but it only works if the Enhanced Display option for the Ambient screen enabled and working. The same applies to the '''Hide Dragbar''' option as well.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels2.png|320px]]&lt;br /&gt;
Programs can be added to the panel by dragging and dropping their icons to the panel list to the wanted position on the list tree, or to the panel itself. Items in the panel list can be rearranged by drag and drop too.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels3.png|320px]]&lt;br /&gt;
Available Panel Objects are listed on the right-hand side and they can be dragged and dropped to any position on the panel tree. All items on the panel may have their own settings, which are shown when an item is clicked once with the left mouse button. In this example picture a new sub panel has been created and its icon image is being changed to a custom one.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels4.png|320px]]&lt;br /&gt;
If you want to clone the color settings from the main panel to a sub panel, you can use the MUI clipboard to temporarily store a setting. Drag &amp;amp; drop the wanted color button to the clipboard button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels5.png|320px]]&lt;br /&gt;
Then activate the sub panel settings and drag &amp;amp; drop the clipboard button to the sub panel's color button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels6.png|320px]]&lt;br /&gt;
And here's a picture of the created panel with its sub panel in action. Remember to click the Save button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels7.png|320px]]&lt;br /&gt;
The panels also have a context menu that can be accessed with a right click. You'll have quick access to the panel settings and some other options there.&lt;br /&gt;
&lt;br /&gt;
If you lock a panel, items dragged to it aren't added to the panel anymore, but the dragged items are opened with the program you dropped them onto. Text files can be dropped onto the Scribble icon, MP3 files and directories can be dropped onto the Jukebox icon, video and audio files onto the MPlayer icon, and so on.&lt;br /&gt;
: [[File:GettingStarted_Panel_Locked1.png|320px]] [[File:GettingStarted_Panel_Locked2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Window ====&lt;br /&gt;
&lt;br /&gt;
Ambient windows are very configurable and users should at least check the buttons available for the toolbar. Just adding a few buttons can make a difference in usability. The buttons and other items can be dragged from the Available Buttons list to the Current Toolbar group, and vice versa to remove them from the toolbar. All changes are updated in real time to any open Ambient windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
In this example picture '''Makedir''' and '''Delete''' buttons are separated with the '''Space''' button, and they have been added into a row with other buttons. Also the '''Bookmarks''' button has been added as the last item on the toolbar. It always stays at the right border no matter how big a window is, because it's been added after the '''Flexible space''' button. &lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Keyboard ====&lt;br /&gt;
===== Built-in Command Hotkeys =====&lt;br /&gt;
Check the Ambient hotkeys from this section and change them to your liking. If you have a laptop without the numeric keypad, you should change hotkeys which are using numpad combinations by default. I, for example, am used to having the '''Cycle Mode''' option on the key above the tab key and the '''Cycle Submode''' option when the same key is pressed with the shift key. It feels somehow quicker to use them from there than from the numeric keypad with a standard keyboard too.&lt;br /&gt;
&lt;br /&gt;
===== Custom Command Hotkeys =====&lt;br /&gt;
Practically any functionality can be added to custom hotkey definitions. This might be a bit advanced topic, but let's show few definitions which will improve the usability.&lt;br /&gt;
&lt;br /&gt;
A new Ambient hotkey can be created by clicking the Add a Hotkey button. The first text field is for the name of the hotkey and it can be anything. The second text field is the actual keyboard combination to activate a function. The Edit Command button is used to define what actually happens when you press the hotkey in Ambient.&lt;br /&gt;
&lt;br /&gt;
Let's create two hotkeys which can be used to copy selected files' names as text to the clipboard, with and without the preceding path.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Copy name with path''' and the hotkey combination to '''ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si FULLPATH''', and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
* Click the '''Add a Hotkey''' button again, define the name as '''Copy name''' and the hotkey combination to '''rshift ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si''', and press the enter key. Click the '''Ok''' button, save the Ambient settings, and you're done.&lt;br /&gt;
&lt;br /&gt;
If you now select any files on an Ambient window and press the ''ralt c'' key combination, the selected file names with their full paths get copied to the clipboard and are available to be pasted to any other application. The ''rshift ralt c'' combination copies pathless file names to the clipboard.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Keyboard1.png|320px]] [[File:GettingStarted_Ambient_Settings_Keyboard2.png|320px]] [[File:GettingStarted_ActionEditor1.png|214px]]&lt;br /&gt;
&lt;br /&gt;
Another example which will extract any selected archive file to the ram disk with the ''lshift control e'' combination.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Extract to RAM''' and the hotkey combination to '''lshift control e'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Leave the action type to '''AmigaDOS''', type in the command '''XADUnFile &amp;amp;#37;sp RAM:''' , and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Screenbar Modules ===&lt;br /&gt;
&lt;br /&gt;
[[Screenbar_Modules | Screenbar modules]] are plugins which can populate the empty area on the screen title bar with some useful information and functionality. The modules are visible on every (MUI) [[Fundamentals_of_MorphOS#Screens | screen]], which makes them more useful than, for example, Panel Objects. Panel Objects are only seen on the Ambient screen and can be left under some other windows more easily.&lt;br /&gt;
&lt;br /&gt;
Screenbar modules can be enabled and disabled from the screen depth gadget menu. The menu also contains options to arrange order of the modules and to change their settings. The menu can be accessed by right clicking, or with a long left press, over the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget | screen depth gadget]].&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Menu.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Let's have a look at how to configure a few modules. Enable the '''CPU Monitor''', '''Drivelamps''', and '''Memory''' modules by, for example, multiselecting them at once. Reopen the screen depth gadget menu, select the '''Settings...''' option, and select CPU Monitor from the settings list. The CPU Monitor module is a bit narrow by default, so let's increase its width a little.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_CPU_Monitor.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Drivelamps module has more configuration options. Enable the '''Show lamp''' option for '''usbscsi.device''' if you want to see access indicators for both HD and USB drives. The default look doesn't seem to be that good for two lamps, but you can tune it a bit. Disabling the frame from the Look group (select None) and selecting the recessed frame for the Lamp Look group does some wonders already. You can also adjust the spacing options, if the lamps don't seem to match with the height of the CPU Monitor or other modules.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Drivelamps.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Memory module shows free memory in percents by default, but it can be changed to other types too. Click the popup button on the '''Information''' line to see the options. The information line can have any text, and for example a ''&amp;amp;#37;mfMB free'' line would show free memory in megabytes followed by the &amp;quot;MB free&amp;quot; text.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Memory.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== MUI Settings ===&lt;br /&gt;
&lt;br /&gt;
MUI is the default GUI toolkit of MorphOS and its looks and behaviour can be changed in almost every aspect. Its basic philosophy is to ''offer as much freedom as possible to users by taking away as much work as possible from programmers''. A user can modify the looks of MUI programs very drastically both globally and per program. It can be done by changing single settings or by loading complete themes (presets).&lt;br /&gt;
&lt;br /&gt;
The most important thing for a new user is to understand the difference between the global settings and settings of individual programs.&lt;br /&gt;
&lt;br /&gt;
The global settings are the default settings which will apply to any program using MUI. The global settings can be changed by selecting the '''Settings-&amp;gt;MUI...''' option from the Ambient's pulldown menus or by double clicking the '''SYS:Prefs/MUI''' icon.&lt;br /&gt;
&lt;br /&gt;
Each MUI program can also have its own MUI settings which will override the global settings, but be careful when changing for example the looks of an individual program. If you decide to change the global theme later, the changes made to the individual programs might not fit the global theme anymore. The MUI settings of a program can be found on its pulldown menu or from the window's [[Fundamentals_of_MorphOS#Window_border_gadgets | popup gadget]] menu. Ambient's MUI settings are found from the '''Settings-&amp;gt;Ambient MUI...''' option in the Ambient's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Let's change a couple of options in the global MUI settings as an example. Open the global MUI settings window.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_MUI_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
The default ghosting effect for buttons is a bit old-fashioned raster effect and it will look much better with just reduced visibility. Select the Buttons page and click the None option for the ghosted gadgets. The visibility can be changed with the slider below, but the default value will be fine too. You'll see the changes in real time on any MUI program, the Test button is a bit obsolete with the latest MUI. I also like to make the Active Gadgets Border a bit smaller than the original size. Click the Save button when you're satisfied.&lt;br /&gt;
: [[File:GettingStarted_MUI_Settings_Buttons.png|380px]]&lt;br /&gt;
&lt;br /&gt;
The Settings button in the top left corner opens a popup menu with options to reset the settings or load different presets.&lt;br /&gt;
&lt;br /&gt;
All MUI settings get saved to the ENVARC:MUI/ directory. If you mess too much with settings for individual programs, the last resort to revert the settings to default is to remove the corresponding settings files from that directory or restore them from a backup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hiding the Boot Image Partition on Macs ===&lt;br /&gt;
&lt;br /&gt;
On Macs you'll have a small HFS formatted partition which contains a few files needed to boot the system. The files are only used by [[Dictionary_of_Terms | Open Firmware]] at boot time and the user or MorphOS itself don't normally need them for anything. Open Firmware, as well as the MorphOS update wizard, can access the partition even if it's not mounted on MorphOS. If we disable the auto mounting of it, our desktop will look a bit cleaner and the crucial boot files will then be safe from accidents as well.&lt;br /&gt;
&lt;br /&gt;
Launch the [[Tools/HDConfig]] program and click on the small HFS partition. Its name should be '''DH0:''' if the system is installed with the default partition layout. Disable the '''Automatically mount partition''' option and click the '''OK''' button.&lt;br /&gt;
: [[File:GettingStarted_HDConfig1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button which is in the red area on the left side and accept the changes.&lt;br /&gt;
: [[File:GettingStarted_HDConfig2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Next time you boot the system, the partition isn't shown on the desktop. If you need to access it later for some reason, it can be mounted temporarily with the [[Tools/Mounter]] tool.&lt;br /&gt;
: [[File:GettingStarted_Ambient2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging the Drive Icons ===&lt;br /&gt;
The drive icons can be dragged to a different order and then saved to their positions by selecting the '''Snapshot''' option from the right click contextual menu. If the Ram Disk icon is dragged to the leftmost position and snapshot, it will appear at that position after a reboot and unsnapshot icons appear next to it.&lt;br /&gt;
: [[File:GettingStarted_Drive_Icons.png|320px]] [[File:GettingStarted_Drive_Icons_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installing, Updating, and Configuring Essential Software ==&lt;br /&gt;
&lt;br /&gt;
=== Checking the Network Connection ===&lt;br /&gt;
&lt;br /&gt;
Before continuing to installing new software, let's check if your machine is properly connected to the Internet.&lt;br /&gt;
&lt;br /&gt;
Open the shell by selecting the '''Ambient-&amp;gt;New Shell...''' option from the Ambient's pulldown menus, or by pressing '''rcommand n''' keyboard combination or doubleclicking the '''SYS:Tools/MUI Shell''' icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_New_Shell.png]]&lt;br /&gt;
&lt;br /&gt;
Check the Internet connection by pinging some hostname on the Internet. Type for example '''ping www.google.com''' on the shell window. If you get replies from the host, the connection is OK and you can proceed by pressing '''CTRL C''' to quit the Ping command and closing the shell window. If you don't get any replies with time values, quit the pinging by the CTRL C combination and read the [[Configuring_Network | Configuring a Network Connection]] tutorial.&lt;br /&gt;
: [[File:GettingStarted_Ping.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Grunch ===&lt;br /&gt;
&lt;br /&gt;
[http://geit.de/eng_grunch.html Grunch] is an advanced software package manager, which can install, update, and uninstall software. It's a good starting point for new users and I'd advice everyone to check what it has to offer before visiting [[Links#File_Repositories | other sites]] for more software.&lt;br /&gt;
&lt;br /&gt;
Start Odyssey Web Browser from '''SYS:Applications/OWB/OWB''' and download Grunch from its [http://geit.de/eng_grunch.html homepage] or from the [http://morphos-files.net/find.php?find=grunch MorphOS Files] site. Save the '''Grunch.lha''' archive file to any location, for example to Work partition or to Ram Disk. The archive isn't needed after the installation.&lt;br /&gt;
: [[File:GettingStarted_OWB4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Close the browser and use Ambient to browse to the location where you saved the Grunch.lha file. If you don't see the file, click the rightmost cycle gadget on the window to show all files. Double click the archive, open the Grunch directory, and double click the '''Grunch.install''' file to start the installer script. Running an installer directly from the unpacked archive is a bit of a shortcut which might not work with all programs, but let's demonstrate it anyway. The traditional and more failproof way would be to unpack an archive file to a temporary location and then run the installer script from an unarchived directory. Read more about installing third party software [[Installing_software | here]].&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Next''' button and select the destination location. The '''System:Applications''' path is OK unless you want to keep the bundled software and 3rd party software strictly separated. In that case you could make a new Applications directory on the Work partition, for example.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After the installation has finished, browse to the location where you installed the program and double click the '''Grunch''' icon. Grunch starts, but you'll have to wait a little while it does its initial checks and updates.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Start.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Before using the program any further, check the Grunch preferences. Select the '''Settings-&amp;gt;Grunch...''' option from the pulldown menus and open the '''Miscellaneous''' tab. I'd change the '''Temporary Directory''' path to somewhere else than to your system partition. If you have enough memory, you could have it even on the Ram Disk, but a temporary directory on the Work partition would be a safe bet.&lt;br /&gt;
&lt;br /&gt;
Click the file requester button at the end of the line to browse to the wanted location. The ''':''' button shows the available volumes, and you can also create new directories from the right click contextual menu on the file requester.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You should check the '''Path''' tab next, and think twice if you want to change them from the default paths. The default paths are OK if you think that all 3rd party and bundled software can reside mixed in the same directories and if you have enough free space on the system partition. But if you like to keep 3rd party and bundled software separated and have the system directories as clean as possible, change the paths now. You could make suitable directories on the Work partition, for instance.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
When you're happy with the settings, click the Save button.&lt;br /&gt;
&lt;br /&gt;
The Grunch icon can also be dragged to a panel for quick access later.&lt;br /&gt;
: [[File:GettingStarted_Dragging_Grunch_to_Panel.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software with Grunch ===&lt;br /&gt;
==== rexxsyslib.library ====&lt;br /&gt;
The rexxsyslib.library file enables the ARexx scripting language support on your system and it should be installed as early as possible. Many programs and their features rely on a working ARexx environment. Select it from the list and click the '''Install''' button on Grunch. You may need a reboot before it'll be in use.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software1.png]]&lt;br /&gt;
&lt;br /&gt;
==== Updating OWB ====&lt;br /&gt;
MorphOS usually comes with a bit old version of the OWB browser and you should check for a newer version. Select OWB from the list and click the '''Check''' button.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software2.png]]&lt;br /&gt;
&lt;br /&gt;
You probably have an old version, so click the '''Update...''' button and wait for it to finish.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software3.png]]&lt;br /&gt;
&lt;br /&gt;
You could also change the mode to Update.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software4.png]]&lt;br /&gt;
&lt;br /&gt;
==== MPlayer ====&lt;br /&gt;
MPlayer is hands down the best video player on MorphOS, just install it. It also works as an audio player with comprehensive support for different formats.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software5.png]]&lt;br /&gt;
&lt;br /&gt;
==== PowerSDL ====&lt;br /&gt;
PowerSDL libraries are required for many software ports from other platforms. It's better to install them as well.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software6.png]]&lt;br /&gt;
&lt;br /&gt;
==== CRABUM ====&lt;br /&gt;
CRABUM lets you to customize the pulldown menus on Ambient. It's quite handy for adding some hidden but quickly available features and shortcuts. We'll need this for some later examples.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software7.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Installed Software ===&lt;br /&gt;
==== Configuring Odyssey Web Browser ====&lt;br /&gt;
Here are few examples or suggestions for the initial configuration of OWB. Do the steps you like.&lt;br /&gt;
===== Downloading More Suitable Fonts for OWB =====&lt;br /&gt;
The fonts provided with MorphOS aren't designed with web usage in mind and it's better to download certain Microsoft fonts for the browser. Luckily it's an easy job to do, because there's a downloader script included in the OWB's directory.&lt;br /&gt;
&lt;br /&gt;
Open the '''SYS:Applications/OWB''' directory and double click the '''Download Fonts''' icon. Note: if the script doesn't seem to work, try [http://www.morphos-storage.net/?page=Network/Web&amp;amp;file=Download_Fonts_for_OWB.lha this one] instead.&lt;br /&gt;
: [[File:GettingStarted_OWB1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Yes''' on the requester and wait patiently for  the downloading and installing of the fonts. The output window closes when the process is finished.&lt;br /&gt;
: [[File:GettingStarted_OWB2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
OWB initializes the fonts on the first run, but it will start much quicker next time.&lt;br /&gt;
: [[File:GettingStarted_OWB3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Making OWB to Use Its Own Screen =====&lt;br /&gt;
A browser is usually an application people want to use in a full size window and on Amigaish systems it makes sense to put it on its own screen. When used on a separate screen it leaves more space for other programs on the Ambient screen, and you don't have such a hassle when handling them all. Bringing screens to front is also a very quick operation, you'll never see any slowdowns like on other systems where you reopen full size windows from taskbars, for example.&lt;br /&gt;
&lt;br /&gt;
You could send a program to a new screen with the &amp;quot;Jump to Screen -&amp;gt; New&amp;quot; option from the window popup gadget, but it's mainly designed for temporary usage. Let's do the configuration more proper way instead.&lt;br /&gt;
&lt;br /&gt;
Launch OWB, click on the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]], and select '''MUI Settings...'''. Another way to access the MUI settings would be from the '''Settings-&amp;gt;MUI...''' pulldown menu option when OWB's window is active.&lt;br /&gt;
: [[File:GettingStarted_OWB5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the '''Screen''' page, select the '''customized public screen from MUI screen database''' option, and click the '''New...''' button.&lt;br /&gt;
&lt;br /&gt;
The Edit Screen window opens. The name field is for the screen name and the title field for the screen title text. They can be anything you want, but it's better to keep them informative. '''OWB''' would be a good screen name now and '''Odyssey Web Browser''' for the title. Check if the default screen mode is what you want. Be also sure that the '''Close automatically''' option is enabled.&lt;br /&gt;
&lt;br /&gt;
It might be a good idea to disable the '''Enhanced Display''' option, because it doesn't give that much advantage with full screen applications. Graphics memory usage will also be lower, and it might be crucial to save some graphics memory on systems with less than 128 MB memory on the graphics card. Read more about how to reduce graphics memory usage [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
Click the '''Ok''' button on the Edit Screen window and the '''Save''' button on the MUI Settings window.&lt;br /&gt;
&lt;br /&gt;
Note: this method can be used with all MUI programs to put them on their own screens, from shell windows to small utilities, bigger applications, and games. I prefer to use the [[Applications/Showgirls|ShowGirls]] image viewer and other bigger applications on their own screens. Several MUI programs can also share the same custom screen, as it isn't limited just to a program per screen. You could for example group some network programs to one screen, and some other programs to another screen, etc.&lt;br /&gt;
: [[File:GettingStarted_OWB6.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The OWB window doesn't probably have optimal size and position on the newly created screen. Right click over the [[Fundamentals_of_MorphOS#Window_border_gadgets | zoom gadget]] and select the '''Maximize''' option or if you configured the zoom gadget as suggested [[Getting_Started#Screens_and_Desktop | earlier]], click the zoom gadget twice. The maximize option leaves the screen title bar visible, but otherwise resizes the window to full screen size. Select the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]] to save the window position permanently.&lt;br /&gt;
: [[File:Tips_Zoommenu.png|top]] [[File:GettingStarted_OWB7.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Open PDF Files Automatically =====&lt;br /&gt;
OWB's MIME Types settings can be used to configure automatic actions to files of certain types. Here is an example of how to show PDF files automatically with the [[Applications/VPDF|VPDF]] application when clicked on the browser.&lt;br /&gt;
&lt;br /&gt;
Open OWB's settings from the '''Settings-&amp;gt;Preferences...''' pulldown menu option and select the '''MIME Types''' page. Click the '''Add''' button and fill in the information below like this:&lt;br /&gt;
 MIME Type: '''application''' / '''pdf'''&lt;br /&gt;
 Extension: '''pdf'''&lt;br /&gt;
 Action: '''External Viewer''', Viewer: '''SYS:Applications/VPDF/VPDF''', and the last unnamed field: '''&amp;amp;#37;f'''&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button.&lt;br /&gt;
&lt;br /&gt;
If you now click a PDF file on a web page, the file is downloaded to a temporary location and shown on VPDF automatically.&lt;br /&gt;
: [[File:GettingStarted_OWB8.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Getting YouTube Videos to Play Better on the Browser Window =====&lt;br /&gt;
YouTube videos should play on OWB by default, but there are a thing or two to note.&lt;br /&gt;
&lt;br /&gt;
Playing videos in a small embedded window is a very CPU intensive task and not quite smooth on most systems. Moving the video playback from the embedded mode to the overlay mode helps the task hugely. This can be achieved with the YouTube Fullscreen Fix script. Videos will be shown in a nearly fullscreen window using the overlay functions and the CPU load may drop from 100&amp;amp;#37; even to 30&amp;amp;#37; on a G4 system, resulting in perfectly smooth playback of course.&lt;br /&gt;
&lt;br /&gt;
'''Download''' the latest script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js (YouTube changes its internals randomly and that's why the script on the MorphOS ISO is probably old already. Grunch also may have an old version and manual installation is highly advisable).&lt;br /&gt;
&lt;br /&gt;
Copy the downloaded script to the '''System:Applications/OWB/Scripts''' directory.&lt;br /&gt;
: [[File:GettingStarted_OWB9.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Scripts window from the '''Windows-&amp;gt;Scripts...''' pulldown menu entry on OWB.&lt;br /&gt;
: [[File:GettingStarted_OWB10.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Add''' button on the Scripts window and select the YouTube_Fullscreen_Fix.js file.&lt;br /&gt;
: [[File:GettingStarted_OWB11.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Make sure that the '''Enable''' setting is chosen and close the window. A '''restart''' of the browser is needed to activate the script, but after that you should be able to get any YouTube video to the smooth fullscreen mode by clicking the &amp;quot;fullscreen&amp;quot; or &amp;quot;large player&amp;quot; buttons on the video '''after the video playback has started'''. If you're watching a video embedded on some other external site, click the settings button instead. '''Double click''' the fullscreen video to get it to the embedded mode again.&lt;br /&gt;
: [[File:GettingStarted_OWB12.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Content Blocking and YouTube =====&lt;br /&gt;
If you have enabled the Content Blocking (AdBlock) option on the OWB settings, YouTube videos with ads will also get blocked. You can make a rule to the content blocking settings to allow those videos to be shown.&lt;br /&gt;
&lt;br /&gt;
Open '''Windows-&amp;gt;Content Blocking...''' from OWB's pulldown menus, click the '''Add''' button, and write '''youtube.com''' to the Rule line, and close the window.&lt;br /&gt;
: [[File:OWB_ContentBlockingYT.png]]&lt;br /&gt;
&lt;br /&gt;
If you have any other problems with the YouTube playback, check the [[Tips_and_Tricks#Problems_with_YouTube_Videos|Tips and Tricks]] page for more information.&lt;br /&gt;
&lt;br /&gt;
===== Configuring Fonts =====&lt;br /&gt;
&lt;br /&gt;
Browsers come with font settings. However, these settings are often neglected. Web developer has at least three options for selecting a font which would be displayed by default on your browser screen. &lt;br /&gt;
It can be a generic font, &amp;quot;hand picked&amp;quot; local font-family, or on-the-fly downloaded web font. Nevertheless the user still has the choice which font he or she actually wants to use. Reasons: privacy, security, speed, aesthetic.&lt;br /&gt;
&lt;br /&gt;
MorphOS is bundled with True Type, PostScript and Amiga Bitmap fonts.&lt;br /&gt;
OWB uses fontconfig for font handling. Fonts are cached whenever a change in font directories is detected.&lt;br /&gt;
If you want to use your fonts exclusively - fonts.conf should only use the path where you store the fonts (for example '''SYS:Fonts/_ttf''').&lt;br /&gt;
&lt;br /&gt;
Fontconfig is a library providing font configuration, customization and application access. It uses freetype library which supports plenty of font formats (excluding Amiga Bitmap fonts).&lt;br /&gt;
Presets are stored in the '''MOSSYS:Fontconfig/conf.avail''' directory.&lt;br /&gt;
&lt;br /&gt;
'''FONTS:Fontconfig/fonts.conf''' (configured font dirs)&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;!-- Font directory list --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;SYS:Fonts/_pcf&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;SYS:Fonts/_pfb&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pcf&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pfb&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_ttf&amp;lt;/dir&amp;gt; --&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Example settings:'''&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/conf.d/51-local.conf'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
	&amp;lt;!-- Load local system customization file --&amp;gt;&lt;br /&gt;
	&amp;lt;include ignore_missing=&amp;quot;yes&amp;quot;&amp;gt;local.conf&amp;lt;/include&amp;gt;&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/local.conf''' (turns off antialias for font sizes smaller than 16 and disables autohint)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;!-- /etc/fonts/local.conf file for local customizations --&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;size&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;pixelsize&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;autohint&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Blocking fonts'''&lt;br /&gt;
&lt;br /&gt;
In OWB, go to '''Settings-&amp;gt;Fonts''' and choose default fonts and sizes.&lt;br /&gt;
&lt;br /&gt;
To disable remote web fonts this line needs to be added to its filter '''SYS:Applications/OWB/Conf/blocked.prefs''':&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
/\.ttf|\.otf|\.woff|\.woff2\?/&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
A specific font can be whitelisted too:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
@@/*actually-nice-font.ttf&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
This isn't ideal. OWB will try block anything_not_whitelisted.ttf, even if you look for a nicefont.ttf in Google Search.&lt;br /&gt;
&lt;br /&gt;
==== Configuring MPlayer ====&lt;br /&gt;
===== General Options =====&lt;br /&gt;
The default configuration of MPlayer is quite fine, but here are a few options I like to set myself. Start MPlayer in the GUI mode by double clicking the GMPlayer icon in the MPlayer directory. There's just one MPlayer executable, but two icons with different [[Fundamentals_of_MorphOS#Icon_Tool_Types|tooltypes]] to start the program with or without the GUI mode.&lt;br /&gt;
&lt;br /&gt;
With default options MPlayer scales the played video to fit the current window dimensions which typically leaves big empty borders around the video. To get the window dimensions to change with the video dimensions, select the '''Video-&amp;gt;Window Dimension-&amp;gt;100&amp;amp;#37;''' option, and '''Settings-&amp;gt;Save''' to save it as a default setting.&lt;br /&gt;
: [[File:GettingStarted_MPlayer.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Preferences window by selecting the '''Settings-&amp;gt;Preferences...''' option from MPlayer's pulldown menus. There are some settings to consider.&lt;br /&gt;
&lt;br /&gt;
The Audio Driver has two audio output options for AHI to choose from. The default '''ahi''' option outputs the audio through the ''Music Unit'', which gives the best audio quality, but blocks simultaneous audio from any other sources. The '''ahi_dev''' option uses the device mode which can be shared with the other sources, but it results in a slight decrease in the audio quality. So, if you want to be able to watch videos while some other program, like a music player, would still continue with audio output, select the '''ahi_dev''' option.&lt;br /&gt;
&lt;br /&gt;
If you don't like any usage data gathering, disable the '''Remember last visited path''' option :)&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Preferences.png]]&lt;br /&gt;
&lt;br /&gt;
===== Setting MPlayer as the Default Player on Ambient  =====&lt;br /&gt;
MorphOS doesn't have any default player for videos and double clicking a video file from Ambient results in an error requester. MPlayer can be set as the default video player by editing the Ambient MIME type settings.&lt;br /&gt;
&lt;br /&gt;
Open the '''Ambient Settings''' window and the '''Mime''' page. With the built-in MIME editor you can add different kinds of actions for different file formats or classes. Let's add MPlayer as the default player for all video files, not just for some individual video formats.&lt;br /&gt;
&lt;br /&gt;
Select '''video''' from the right-hand side list tree and click the '''Edit''' button. Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
&lt;br /&gt;
In the Action Editor window type a name for the action, for example '''Play''', and click the '''Add''' button on that window too.&lt;br /&gt;
&lt;br /&gt;
Change the AmigaDOS command to '''Run &amp;gt;NIL: SYS:Applications/MPlayer/MPlayer -gui 1 &amp;amp;#37;sp''' (change the path to the MPlayer executable if you have it in a different location) and change the Event type to '''DoubleClick'''. Note: the ''-gui 1'' option, which starts MPlayer in the GUI mode, has to be written in lower case, having it in upper case doesn't work!&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Adding_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Ok''', '''Ok''', and '''Save''' buttons.&lt;br /&gt;
&lt;br /&gt;
If you now double click a video file in Ambient, it gets played on MPlayer. You can also see the Play option in the contextual menu when right clicking the video file.&lt;br /&gt;
: [[File:GettingStarted_MPlayer2.png|320px]] [[File:GettingStarted_MPlayer_Working_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You can add several actions as contextual menu events if you want to have more options for opening videos. Only imagination is the limit, and you can for example have contextual menu entries to start MPlayer playback with filters skipped (use the ''-lavdopts skiploopfilter=all'' option to speed up the video playback a little) and have an option to convert the video with mencoder etc.&lt;br /&gt;
: [[File:GettingStarted_ActionEditor2.png|230px]]&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with FlowStudio ====&lt;br /&gt;
&lt;br /&gt;
Custom menus in Ambient can be added with a lua script. Menus can be edited and reloaded via respective menu items.&lt;br /&gt;
&lt;br /&gt;
'''SYS:WBStartup/menus.lua''' script:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
require('ipc')&lt;br /&gt;
address('AMBIENT')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m1-0&amp;quot;                               title=&amp;quot;Tools&amp;quot;             type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-1&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;MUICON&amp;quot;          type=item shortcut=&amp;quot;S&amp;quot; command=&amp;quot;*&amp;quot;SYS:Tools/MUI Shell*&amp;quot;&amp;quot;                                              commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-2&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;Snoopium&amp;quot;        type=item command=&amp;quot;SYS:Tools/Snoopium&amp;quot;                                                                     commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-3&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-4&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;Mounter&amp;quot;         type=item command=&amp;quot;SYS:Tools/Mounter&amp;quot;                                                                        commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-5&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;HDConfig&amp;quot;        type=item command=&amp;quot;SYS:Tools/HDConfig&amp;quot;                                                                       commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;&amp;quot;                   type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6-0&amp;quot; parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;Menu&amp;quot;            type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6-1&amp;quot; parentid=&amp;quot;m1-6-0&amp;quot;  title=&amp;quot;Edit&amp;quot;              type=item command=&amp;quot;SYS:Applications/FlowStudio/FlowStudio SYS:WBStartup/menus.lua&amp;quot;        commandtype=amigados')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6-2&amp;quot; parentid=&amp;quot;m1-6-0&amp;quot;  title=&amp;quot;Reload&amp;quot;          type=item command=&amp;quot;RXCmd AMBIENT *&amp;quot;menu remove*&amp;quot; &amp;amp;&amp;amp; LuaX SYS:WBStartup/menus.lua&amp;quot;    commandtype=amigados')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m2-0&amp;quot;                               title=&amp;quot;Apps&amp;quot;             type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-1&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;FlowStudio&amp;quot;      type=item shortcut=&amp;quot;W&amp;quot; command=&amp;quot;Run &amp;gt;NIL: SYS:Applications/FlowStudio/FlowStudio&amp;quot;          commandtype=amigados')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-2&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;&amp;quot;                    type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-3&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;OWB&amp;quot;              type=item shortcut=&amp;quot;B&amp;quot; command=&amp;quot;SYS:Applications/OWB/OWB&amp;quot;                                          commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-4&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;Transfer&amp;quot;         type=item command=&amp;quot;SYS:Applications/Transfer/Transfer&amp;quot;                                                   commandtype=workbench')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m3-0&amp;quot;                               title=&amp;quot;Utils&amp;quot;               type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-1&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;MUIProCalc&amp;quot;      type=item command=&amp;quot;SYS:Utilities/MUIProCalc&amp;quot;                                                                commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-2&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-3&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;Zoom&amp;quot;              type=item shortcut=&amp;quot;Z&amp;quot; command=&amp;quot;SYS:Utilities/Zoom&amp;quot;                                                      commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-4&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-5&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;AudioRecorder&amp;quot;  type=item command=&amp;quot;SYS:Utilities/AudioRecorder&amp;quot;                                                             commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-6&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;JukeBox&amp;quot;           type=item shortcut=&amp;quot;J&amp;quot; command=&amp;quot;SYS:Utilities/JukeBox&amp;quot;                                                   commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-7&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-8&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;GraphicsBoards&amp;quot;  type=item command=&amp;quot;SYS:Utilities/GraphicBoards&amp;quot;                                                           commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-9&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;TaskManager&amp;quot;    type=item shortcut=&amp;quot;T&amp;quot; command=&amp;quot;SYS:Utilities/TaskManager&amp;quot;                                            commandtype=workbench')&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Create .info icon for menus.lua''':&lt;br /&gt;
&lt;br /&gt;
'''Copy ENV:SYS/def_tool.info SYS:WBStartup/menus.lua.info'''&lt;br /&gt;
&lt;br /&gt;
'''Set icon info''':&lt;br /&gt;
&lt;br /&gt;
Select menus.lua and open its Information window (COMMAND I). Set Type as a '''Project''', write '''LuaX''' as a Default Tool and press '''Save'''.&lt;br /&gt;
&lt;br /&gt;
Now you can run menus.lua script and enjoy Ambient menus.&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with CRABUM ====&lt;br /&gt;
&lt;br /&gt;
You can add custom pulldown menus to Ambient with ARexx scripts created by the CRABUM program. It's a good way to launch programs or scripts which you don't want to have on panels. Installation of [[Getting_Started#rexxsyslib.library|rexxsyslib.library]] is required.&lt;br /&gt;
&lt;br /&gt;
Let's create an Edit menu with options to edit different system startup scripts. Double click the CRABUM icon from the SYS:Utilities/CRABUM directory if you installed it with the default options.&lt;br /&gt;
&lt;br /&gt;
# Click the '''Menu''' button to add a new menu and change its title to '''Edit'''.&lt;br /&gt;
# Click the '''Item''' button to add a new item under the created menu.&lt;br /&gt;
# Type '''User-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-startup''' to the AmigaDOS command line. &amp;quot;Run &amp;gt;NIL:&amp;quot; starts the Ed program as a background process and it won't block Ambient while it is running.&lt;br /&gt;
# Create an another item by clicking the '''Item''' button.&lt;br /&gt;
# Type '''User-network-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-network-startup''' to the AmigaDOS command line.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM1.png|320px]]&lt;br /&gt;
# Click the '''Save''' button to save the resulting ARexx script.&lt;br /&gt;
# If you save the file to the SYS:WBStartup drawer, it will be launched automatically at boot time. Enter a suitable name for the file, for example '''Edit-menu'''. Click the '''Ok''' button.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After a reboot (or doubleclicking of the file) you'll have the new Edit menu on the Ambient pulldown menus and you can easily open the system files for editing.&lt;br /&gt;
: [[File:GettingStarted_CRABUM3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
== More Configuring ==&lt;br /&gt;
=== Synchronizing the Clock with an Internet Time Server ===&lt;br /&gt;
The system clock can be synchronized manually from the MorphOS Preferences application by clicking the '''Set date and time using the Internet''' button in the Time preferences.&lt;br /&gt;
: [[File:MorphOS_Preferences_Time.png|320px]]&lt;br /&gt;
&lt;br /&gt;
There's also the [[Shell_Commands/SetClockNTP|SetClockNTP]] shell command which can be launched manually or automatically at boot time. To synchronize the time every time the system starts edit the '''S:user-network-startup''' file and remove the semi-colon from the SetClockNTP line.&lt;br /&gt;
&lt;br /&gt;
To edit the S:user-network-startup file open the shell (or the Execute Command prompt) and type '''Ed S:user-network-startup''', or open the System partition, select the '''All Files''' mode, browse to the '''S''' directory and select the '''Edit...''' option from the right click contextual menu. Or if you configured the Edit menu with CRABUM earlier, use it now.&lt;br /&gt;
: [[File:GettingStarted_Enable_SetClockNTP.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Shell ===&lt;br /&gt;
==== Editing the Shell-startup file ====&lt;br /&gt;
The shell can be customized with the shell-startup file, but by default the file is only found in a MorphOS system directory where the user shouldn't do any modifications. It must be copied to a user directory first to make any changes to it. Open a new shell window and type '''Copy MOSSYS:S/shell-startup SYS:S/shell-startup''', and then edit it for example with the '''Ed SYS:S/shell-startup''' command. The shell-startup file is executed every time a new shell window is opened.&lt;br /&gt;
: [[File:GettingStarted_shell-startup.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Adding Paths ====&lt;br /&gt;
There are some useful shell commands around the installed system which aren't in the system's search path and thus you'll have to enter their complete paths when using them. Adding their locations to the search path allows them to be run just by their names, which is much more convenient.&lt;br /&gt;
&lt;br /&gt;
Here are few suggestions to add to the '''SYS:S/shell-startup''' file (remember the previous step first!). Or if you want them to be available globally on all occasions, they can be added to the '''S:user-startup''' file instead.&lt;br /&gt;
* '''Path SYS:Applications/RemoteShell/Files ADD''' adds SSH related commands like scp, sftp, ssh, etc to the search path. Note: use the [[Applications/RemoteShell|Remote Shell]] application for regular SSH sessions, because it supports arrow keys and other things better.&lt;br /&gt;
* '''Path SYS:Applications/OWB/Datas ADD''' adds wget to the search path.&lt;br /&gt;
* '''Path SYS:Applications/MPlayer ADD''' adds MPlayer and mencoder to the search path if you have installed MPlayer. Change the path if you have installed it elsewhere.&lt;br /&gt;
&lt;br /&gt;
==== Configuring the GUI ====&lt;br /&gt;
There are many buttons and hotkeys to add to the shell window besides the default ones. Check the preferences by selecting the '''Settings-&amp;gt;Edit Prefs...''' option from the Shell's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Available functions can be dragged to '''Hotkeys''' or '''Buttons''' lists and the changes are seen in real time in the shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You may also want to set the default window size and position for new shell windows on the '''Settings''' tab. Click the '''Get from window''' button to get values from the current shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Remember to save the modifications in the '''Settings''' menu.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Setting Jukebox as the Default Player for MP3 Files ===&lt;br /&gt;
If you double click an MP3 file in an Ambient window, it is played with the very simple internal player. Here are two solutions to change the default player to the more advanced [[Utilities/Jukebox|Jukebox]] music player. Ambient's internal player is still left to the context menu as an option.&lt;br /&gt;
==== Simple Solution ====&lt;br /&gt;
A simple solution is just to create a new mpeg audio MIME type definition which just launches the Jukebox player with the double clicked filename as an argument.&lt;br /&gt;
# Open the Mime page in the Ambient settings, select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''Run &amp;gt;NIL: SYS:Utilities/Jukebox &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and you should see this in the MIME Editor window.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Save''' buttons. If you double click an MP3 file now, Jukebox starts and plays the clicked file. There are also two entires in the right click contextual menu and the option which is used for the double click action is written in bold.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Advanced Solution ====&lt;br /&gt;
An advanced solution is to use the third party [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script. It will give more flexible options to add files to Jukebox, and we'll learn how to add submenus into context menus. There are shortcuts to install the script if you read the documentation in the archive, but let's do this manually to learn the configuration method better. It will be helpful in the future when configuring any other filetypes.&lt;br /&gt;
&lt;br /&gt;
# Download the script archive from [http://aminet.net/package/mus/play/JukeboxAdder Aminet] or from [http://morphos-files.net/find.php?find=jukeboxadder MorphOS Files].&lt;br /&gt;
# Copy the '''jukeboxadder.lua''' file from the archive to the '''SYS:S/''' directory.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder1.png|320px]]&lt;br /&gt;
# Open the '''Mime''' page in the '''Ambient settings''', select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua PLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and then click '''Add''' again in the MIME Editor window to create more ways to add files to Jukebox from the context menus.&lt;br /&gt;
# Type '''Add to Jukebox''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua ADD &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string. This will create a submenu named ''Jukebox'' in the context menu and place the new ''Add to Jukebox'' option there.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Add''' once again to create the last entry.&lt;br /&gt;
# Type '''Add to Jukebox and Play''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''MOSSYS:C/LuaX S:jukeboxadder.lua ADDPLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder4.png|320px]]&lt;br /&gt;
# Click '''Ok''', '''Ok''', and '''Save'''. Now you can see more options in the context menu for MP3 files and double clicking will always clear the previous songs and play the new song immediately.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
It is also possible to add the same functionality for context menus of directories if you want to be able to add whole directories to Jukebox at once. There's a special '''internal -&amp;gt; x-morphos-globalaction-directory''' MIME type which can be used to add context menu entries for all directories. Repeat the previous steps (6-18) for it, but make all '''Event types''' to use the '''Menu''' option (in step 9 too).&lt;br /&gt;
: [[File:GettingStarted_JukeboxAdder6.png|320px]] [[File:GettingStarted_JukeboxAdder7.png|320px]] [[File:GettingStarted_JukeboxAdder8.png|320px]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3879</id>
		<title>Getting Started</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3879"/>
				<updated>2018-06-19T19:49:16Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== A Beginner's Guide to MorphOS ==&lt;br /&gt;
&lt;br /&gt;
You have installed MorphOS to a compatible machine, but... now what? You could always go and install a pre-configured package like Chrysalis, but you would end up with a system configured for someone else's taste and you still wouldn't know how to actually use the operating system. If you are in this situation and would like to learn how MorphOS works, this is a tutorial for you! The tutorial will guide you through the things you should do and notice after a fresh install, with practical examples from basic configuration options to installing new software. It won't cover all the details and is just an opinion on how to proceed, but it should give you some knowledge how to continue on your own and make your own decisions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting Comfortable with the User Interface and the Ambient Desktop ==&lt;br /&gt;
=== The First Boot ===&lt;br /&gt;
&lt;br /&gt;
After a boot you're presented with the plain looking Ambient, the desktop environment of MorphOS. The first thing you should learn is to get familiar with the basic usage, and to tune the interface settings so that they won't annoy you. The worst thing is if a user plays around a bit and just curses at the system when it doesn't work as expected or wanted. You aren't forced into just one kind of behaviour with MorphOS!&lt;br /&gt;
: [[File:GettingStarted_Ambient.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Right mouse click is widely used on MorphOS and if you're using a device without a physical button for it, check the tips over [[Tips_and_Tricks#How_to_Use_RMB_with_One-button_Mouse | here]]. Pressing the right mouse button over the Ambient screen opens Ambient's pulldown menus where you can find few important options. For example, options to shut down the system, to open a new shell window, or to open system settings.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Shutdown.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== System Settings ===&lt;br /&gt;
&lt;br /&gt;
The MorphOS Preferences application is used to edit system-wide settings. It can be launched from the Ambient's pulldown menu by selecting the &amp;quot;Settings-&amp;gt;System...&amp;quot; menu option or by browsing to the System:Prefs/ drawer and double clicking the Preferences icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_System_Settings.png]] [[File:GettingStarted_MorphOS_Preferences.png|237px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Screens ====&lt;br /&gt;
&lt;br /&gt;
If MorphOS didn't get the optimal resolution of your monitor with DDC, a different screen mode can be selected from the Screens settings. If the wanted mode isn't seen there, open the Monitors settings instead to create a completely new mode.&lt;br /&gt;
&lt;br /&gt;
If you have a graphics card with a low amount of memory, you can try to make the memory consumption smaller by disabling the Enhanced Display setting (3D accelerated graphics functions for 2D screens) or by reducing the color depth. More information can be found  [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
MorphOS skins (themes for the graphical appearance) can also be changed from the Screens settings.&lt;br /&gt;
&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== IControl ====&lt;br /&gt;
&lt;br /&gt;
IControl settings are the most important settings for the overall user experience. This is the place to look in order to avoid the usual comments like ''&amp;quot;Why doesn't X work like Y in the other OS?&amp;quot;'', ''&amp;quot;Why there isn't a feature Z?&amp;quot;'', ''&amp;quot;I can't use a system like this!&amp;quot;''. Everyone should check these settings first before going any further.&lt;br /&gt;
&lt;br /&gt;
===== Hotkeys =====&lt;br /&gt;
MorphOS has many nice features to use with keyboard shortcuts or mouse buttons, but only few are activated by default. Let's activate more!&lt;br /&gt;
&lt;br /&gt;
To add a new hotkey for the wanted function click the popup button on the right side, select &amp;quot;'''Sample'''&amp;quot;, and press the wanted key combination. The pressed combination is then recorded on the corresponding line and should be shown there. Repeat the procedure if you didn't get it as wanted on the first try. Changed settings will be taken into use after you click the Save or Use button.&lt;br /&gt;
&lt;br /&gt;
Here is how to set the &amp;quot;control left-alt c&amp;quot; key combination to '''center the active window''' on the screen:&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Hotkeys2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Here are some other recommendations to activate, but feel free to use your own preferences for the hotkeys:&lt;br /&gt;
* '''Active Window: To Back''' - double click with middle mouse button to send a window back of other windows.&lt;br /&gt;
* '''Active Window: Zoom''' - &amp;quot;control left-alt m&amp;quot;, to toggle between a maximized and minimized window.&lt;br /&gt;
* '''Active Window: Activate Next''' - &amp;quot;left-command tab&amp;quot;, to have the ''alt-tab'' functionality found on many other operating systems. Using ctrl-tab or alt-tab isn't recommended because they would overlap with the shell's functionality on MorphOS. Command-tab also happens be the same in OS X.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys3.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Note: You can also add several hotkeys for a function by selecting the New Hotkey option from the popup button's menu.&lt;br /&gt;
&lt;br /&gt;
===== Screens and Desktop =====&lt;br /&gt;
&lt;br /&gt;
Important options concerning how windows and menus behave can be found on the Screens and Desktop settings.&lt;br /&gt;
&lt;br /&gt;
I'd recommend turning on the '''Maximize window when clicking on the Zoom gadget''' option. The Zoom gadget will then toggle the window size between full screen (with the screen title bar still visible) and the initial window size and position. I find it much more comfortable than the legacy placement between two obscure positions. The previously configured Zoom hotkey will also work better with this option enabled.&lt;br /&gt;
&lt;br /&gt;
If you prefer being able to drag windows out of the screen without pressing any qualifier key, like on mainstream systems, select the '''When dragging windows... allow them to be placed out of screen, unless Control is pressed''' option.&lt;br /&gt;
&lt;br /&gt;
The default behaviour of the pulldown menus may be a bit unfamiliar for old Amiga users, but there are several options to get them working as expected. I like to disable the '''Menus shall remain opened even when mouse button is released''' option and enable the '''Open menus under mouse pointer outside screen titlebar area''' option.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Touchpad ====&lt;br /&gt;
&lt;br /&gt;
If you're using a laptop system, check the Touchpad setttings. You might want to disable clicking from the pad to avoid any accidental clicks.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Touchpad.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Laptop ====&lt;br /&gt;
&lt;br /&gt;
If you're not a Mac user, you might find it odd that you need to press the fn key when using the function keys for normal activities, and not when modifying, for example, the screen brightness. The '''Press and hold the fn key to modify screen brightness, audio volume, etc.''' option will change the functionality the other way around.&lt;br /&gt;
&lt;br /&gt;
Some systems also have the '''Automatic LCD brightness and keyboard backlight control''' option here. Disable it if you're annoyed by changing lightning.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Laptop.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Windows ===&lt;br /&gt;
&lt;br /&gt;
The first icon you see on the Ambient desktop is the &amp;quot;'''My MorphOS'''&amp;quot; icon. By double clicking it you'll get a window with icons of all volumes and assigns of the system. It works like a root directory with quick access to different locations.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS.png|320px]]&lt;br /&gt;
&lt;br /&gt;
If you find it a bit clumsy to work in the icon mode, like I do, you can change the view to '''the list mode''' from the cycle button on the right side of the window.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
With default settings Ambient doesn't remember the changed mode or other window properties next time you open it, but you can right click the window border or an empty area on the file lister to bring up a contextual window menu and select the &amp;quot;'''Snapshot-&amp;gt;Window'''&amp;quot; option to save the window properties. Default position and size for a window can be saved that way too. If you defined the centering hotkey earlier, you can try it now :)&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The same can also be done for normal directory windows. While &amp;quot;My MorphOS&amp;quot; window settings are exceptionally saved to Ambient's configuration files, normal directories' settings are saved to an icon file (a file with .info extension). If you change and save the mode for the Work: partition for example, you see a disk.info file appearing there.&lt;br /&gt;
: [[File:GettingStarted_Icon_Mode.png|320px]] [[File:GettingStarted_List_Mode_Snapshot.png|320px]] [[File:GettingStarted_List_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Displayed columns can be selected by right clicking the column title area, but modify the [[Getting_Started#Lister|default lister settings]] to your liking before starting to save settings for individual windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Lister_Columns.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Settings ===&lt;br /&gt;
&lt;br /&gt;
Ambient is actually a separate application itself and it has its own settings separated from the general system preferences. The previously mentioned system settings affect all programs and screens, but strictly desktop related settings are found in the Ambient settings. The Ambient Settings window can be opened by selecting the &amp;quot;Settings-&amp;gt;Ambient...&amp;quot; option from Ambient's pulldown menu.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Ambient_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
==== Miscellaneous ====&lt;br /&gt;
&lt;br /&gt;
The Miscellaneous page on the Ambient settings has a nice option to get the My MorphOS window opened when double clicking anywhere on the empty area of the desktop. It really speeds up the working when you don't have to move the mouse a long way to the top corner or dig the icon out from under some other windows. Enable it with the '''Double click on desktop opens MyMorphOS window''' option.&lt;br /&gt;
&lt;br /&gt;
The My MorphOS icon is just wasting space on the desktop after the previous setting and you can hide it by disabling the '''Display MyMorphOS icon''' option.&lt;br /&gt;
&lt;br /&gt;
If you like to have a bit more eye candy on the context menus, you can also enable the '''Show images in context menu''' option while you're here.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Misc.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Lister ====&lt;br /&gt;
The default properties of the list mode of Ambient windows can be changed on the Lister settings. Disable the '''Compact size display''' if you want to see exact file sizes in bytes always. You may also want to select different columns to be shown in the listers by double clicking items on the '''File Properties''' list to set them hidden or shown. '''Date &amp;amp; Time''' instead of just Date would probably be a common choice.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Lister.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Panels ====&lt;br /&gt;
&lt;br /&gt;
Many new users are wondering if there is any kind of dock application on MorphOS, because there isn't any shown by default. MorphOS has ''panels'' for that and you can have as many panels as you want on the desktop, arranged horizontally or vertically. The panels have features like zipping to hide and unhide them, sub panels and other Panel Object plugins, etc. There just isn't any configured by default and user can create a panel or panels how he likes.&lt;br /&gt;
&lt;br /&gt;
To create a new panel, open the Panels page on the Ambient settings and click the '''New Panel''' button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels1.png|320px]]&lt;br /&gt;
An empty panel can be dragged anywhere and you can find some of its settings on the '''Name &amp;amp; Look''' and '''Behaviour''' tabs. If you want to place the panel on a screen border the '''Attached to Borders''' option makes it easier. The '''Alpha''' option controls the transparency of a panel, but it only works if the Enhanced Display option for the Ambient screen enabled and working. The same applies to the '''Hide Dragbar''' option as well.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels2.png|320px]]&lt;br /&gt;
Programs can be added to the panel by dragging and dropping their icons to the panel list to the wanted position on the list tree, or to the panel itself. Items in the panel list can be rearranged by drag and drop too.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels3.png|320px]]&lt;br /&gt;
Available Panel Objects are listed on the right-hand side and they can be dragged and dropped to any position on the panel tree. All items on the panel may have their own settings, which are shown when an item is clicked once with the left mouse button. In this example picture a new sub panel has been created and its icon image is being changed to a custom one.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels4.png|320px]]&lt;br /&gt;
If you want to clone the color settings from the main panel to a sub panel, you can use the MUI clipboard to temporarily store a setting. Drag &amp;amp; drop the wanted color button to the clipboard button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels5.png|320px]]&lt;br /&gt;
Then activate the sub panel settings and drag &amp;amp; drop the clipboard button to the sub panel's color button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels6.png|320px]]&lt;br /&gt;
And here's a picture of the created panel with its sub panel in action. Remember to click the Save button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels7.png|320px]]&lt;br /&gt;
The panels also have a context menu that can be accessed with a right click. You'll have quick access to the panel settings and some other options there.&lt;br /&gt;
&lt;br /&gt;
If you lock a panel, items dragged to it aren't added to the panel anymore, but the dragged items are opened with the program you dropped them onto. Text files can be dropped onto the Scribble icon, MP3 files and directories can be dropped onto the Jukebox icon, video and audio files onto the MPlayer icon, and so on.&lt;br /&gt;
: [[File:GettingStarted_Panel_Locked1.png|320px]] [[File:GettingStarted_Panel_Locked2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Window ====&lt;br /&gt;
&lt;br /&gt;
Ambient windows are very configurable and users should at least check the buttons available for the toolbar. Just adding a few buttons can make a difference in usability. The buttons and other items can be dragged from the Available Buttons list to the Current Toolbar group, and vice versa to remove them from the toolbar. All changes are updated in real time to any open Ambient windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
In this example picture '''Makedir''' and '''Delete''' buttons are separated with the '''Space''' button, and they have been added into a row with other buttons. Also the '''Bookmarks''' button has been added as the last item on the toolbar. It always stays at the right border no matter how big a window is, because it's been added after the '''Flexible space''' button. &lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Keyboard ====&lt;br /&gt;
===== Built-in Command Hotkeys =====&lt;br /&gt;
Check the Ambient hotkeys from this section and change them to your liking. If you have a laptop without the numeric keypad, you should change hotkeys which are using numpad combinations by default. I, for example, am used to having the '''Cycle Mode''' option on the key above the tab key and the '''Cycle Submode''' option when the same key is pressed with the shift key. It feels somehow quicker to use them from there than from the numeric keypad with a standard keyboard too.&lt;br /&gt;
&lt;br /&gt;
===== Custom Command Hotkeys =====&lt;br /&gt;
Practically any functionality can be added to custom hotkey definitions. This might be a bit advanced topic, but let's show few definitions which will improve the usability.&lt;br /&gt;
&lt;br /&gt;
A new Ambient hotkey can be created by clicking the Add a Hotkey button. The first text field is for the name of the hotkey and it can be anything. The second text field is the actual keyboard combination to activate a function. The Edit Command button is used to define what actually happens when you press the hotkey in Ambient.&lt;br /&gt;
&lt;br /&gt;
Let's create two hotkeys which can be used to copy selected files' names as text to the clipboard, with and without the preceding path.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Copy name with path''' and the hotkey combination to '''ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si FULLPATH''', and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
* Click the '''Add a Hotkey''' button again, define the name as '''Copy name''' and the hotkey combination to '''rshift ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si''', and press the enter key. Click the '''Ok''' button, save the Ambient settings, and you're done.&lt;br /&gt;
&lt;br /&gt;
If you now select any files on an Ambient window and press the ''ralt c'' key combination, the selected file names with their full paths get copied to the clipboard and are available to be pasted to any other application. The ''rshift ralt c'' combination copies pathless file names to the clipboard.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Keyboard1.png|320px]] [[File:GettingStarted_Ambient_Settings_Keyboard2.png|320px]] [[File:GettingStarted_ActionEditor1.png|214px]]&lt;br /&gt;
&lt;br /&gt;
Another example which will extract any selected archive file to the ram disk with the ''lshift control e'' combination.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Extract to RAM''' and the hotkey combination to '''lshift control e'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Leave the action type to '''AmigaDOS''', type in the command '''XADUnFile &amp;amp;#37;sp RAM:''' , and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Screenbar Modules ===&lt;br /&gt;
&lt;br /&gt;
[[Screenbar_Modules | Screenbar modules]] are plugins which can populate the empty area on the screen title bar with some useful information and functionality. The modules are visible on every (MUI) [[Fundamentals_of_MorphOS#Screens | screen]], which makes them more useful than, for example, Panel Objects. Panel Objects are only seen on the Ambient screen and can be left under some other windows more easily.&lt;br /&gt;
&lt;br /&gt;
Screenbar modules can be enabled and disabled from the screen depth gadget menu. The menu also contains options to arrange order of the modules and to change their settings. The menu can be accessed by right clicking, or with a long left press, over the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget | screen depth gadget]].&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Menu.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Let's have a look at how to configure a few modules. Enable the '''CPU Monitor''', '''Drivelamps''', and '''Memory''' modules by, for example, multiselecting them at once. Reopen the screen depth gadget menu, select the '''Settings...''' option, and select CPU Monitor from the settings list. The CPU Monitor module is a bit narrow by default, so let's increase its width a little.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_CPU_Monitor.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Drivelamps module has more configuration options. Enable the '''Show lamp''' option for '''usbscsi.device''' if you want to see access indicators for both HD and USB drives. The default look doesn't seem to be that good for two lamps, but you can tune it a bit. Disabling the frame from the Look group (select None) and selecting the recessed frame for the Lamp Look group does some wonders already. You can also adjust the spacing options, if the lamps don't seem to match with the height of the CPU Monitor or other modules.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Drivelamps.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Memory module shows free memory in percents by default, but it can be changed to other types too. Click the popup button on the '''Information''' line to see the options. The information line can have any text, and for example a ''&amp;amp;#37;mfMB free'' line would show free memory in megabytes followed by the &amp;quot;MB free&amp;quot; text.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Memory.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== MUI Settings ===&lt;br /&gt;
&lt;br /&gt;
MUI is the default GUI toolkit of MorphOS and its looks and behaviour can be changed in almost every aspect. Its basic philosophy is to ''offer as much freedom as possible to users by taking away as much work as possible from programmers''. A user can modify the looks of MUI programs very drastically both globally and per program. It can be done by changing single settings or by loading complete themes (presets).&lt;br /&gt;
&lt;br /&gt;
The most important thing for a new user is to understand the difference between the global settings and settings of individual programs.&lt;br /&gt;
&lt;br /&gt;
The global settings are the default settings which will apply to any program using MUI. The global settings can be changed by selecting the '''Settings-&amp;gt;MUI...''' option from the Ambient's pulldown menus or by double clicking the '''SYS:Prefs/MUI''' icon.&lt;br /&gt;
&lt;br /&gt;
Each MUI program can also have its own MUI settings which will override the global settings, but be careful when changing for example the looks of an individual program. If you decide to change the global theme later, the changes made to the individual programs might not fit the global theme anymore. The MUI settings of a program can be found on its pulldown menu or from the window's [[Fundamentals_of_MorphOS#Window_border_gadgets | popup gadget]] menu. Ambient's MUI settings are found from the '''Settings-&amp;gt;Ambient MUI...''' option in the Ambient's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Let's change a couple of options in the global MUI settings as an example. Open the global MUI settings window.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_MUI_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
The default ghosting effect for buttons is a bit old-fashioned raster effect and it will look much better with just reduced visibility. Select the Buttons page and click the None option for the ghosted gadgets. The visibility can be changed with the slider below, but the default value will be fine too. You'll see the changes in real time on any MUI program, the Test button is a bit obsolete with the latest MUI. I also like to make the Active Gadgets Border a bit smaller than the original size. Click the Save button when you're satisfied.&lt;br /&gt;
: [[File:GettingStarted_MUI_Settings_Buttons.png|380px]]&lt;br /&gt;
&lt;br /&gt;
The Settings button in the top left corner opens a popup menu with options to reset the settings or load different presets.&lt;br /&gt;
&lt;br /&gt;
All MUI settings get saved to the ENVARC:MUI/ directory. If you mess too much with settings for individual programs, the last resort to revert the settings to default is to remove the corresponding settings files from that directory or restore them from a backup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hiding the Boot Image Partition on Macs ===&lt;br /&gt;
&lt;br /&gt;
On Macs you'll have a small HFS formatted partition which contains a few files needed to boot the system. The files are only used by [[Dictionary_of_Terms | Open Firmware]] at boot time and the user or MorphOS itself don't normally need them for anything. Open Firmware, as well as the MorphOS update wizard, can access the partition even if it's not mounted on MorphOS. If we disable the auto mounting of it, our desktop will look a bit cleaner and the crucial boot files will then be safe from accidents as well.&lt;br /&gt;
&lt;br /&gt;
Launch the [[Tools/HDConfig]] program and click on the small HFS partition. Its name should be '''DH0:''' if the system is installed with the default partition layout. Disable the '''Automatically mount partition''' option and click the '''OK''' button.&lt;br /&gt;
: [[File:GettingStarted_HDConfig1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button which is in the red area on the left side and accept the changes.&lt;br /&gt;
: [[File:GettingStarted_HDConfig2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Next time you boot the system, the partition isn't shown on the desktop. If you need to access it later for some reason, it can be mounted temporarily with the [[Tools/Mounter]] tool.&lt;br /&gt;
: [[File:GettingStarted_Ambient2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging the Drive Icons ===&lt;br /&gt;
The drive icons can be dragged to a different order and then saved to their positions by selecting the '''Snapshot''' option from the right click contextual menu. If the Ram Disk icon is dragged to the leftmost position and snapshot, it will appear at that position after a reboot and unsnapshot icons appear next to it.&lt;br /&gt;
: [[File:GettingStarted_Drive_Icons.png|320px]] [[File:GettingStarted_Drive_Icons_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installing, Updating, and Configuring Essential Software ==&lt;br /&gt;
&lt;br /&gt;
=== Checking the Network Connection ===&lt;br /&gt;
&lt;br /&gt;
Before continuing to installing new software, let's check if your machine is properly connected to the Internet.&lt;br /&gt;
&lt;br /&gt;
Open the shell by selecting the '''Ambient-&amp;gt;New Shell...''' option from the Ambient's pulldown menus, or by pressing '''rcommand n''' keyboard combination or doubleclicking the '''SYS:Tools/MUI Shell''' icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_New_Shell.png]]&lt;br /&gt;
&lt;br /&gt;
Check the Internet connection by pinging some hostname on the Internet. Type for example '''ping www.google.com''' on the shell window. If you get replies from the host, the connection is OK and you can proceed by pressing '''CTRL C''' to quit the Ping command and closing the shell window. If you don't get any replies with time values, quit the pinging by the CTRL C combination and read the [[Configuring_Network | Configuring a Network Connection]] tutorial.&lt;br /&gt;
: [[File:GettingStarted_Ping.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Grunch ===&lt;br /&gt;
&lt;br /&gt;
[http://geit.de/eng_grunch.html Grunch] is an advanced software package manager, which can install, update, and uninstall software. It's a good starting point for new users and I'd advice everyone to check what it has to offer before visiting [[Links#File_Repositories | other sites]] for more software.&lt;br /&gt;
&lt;br /&gt;
Start Odyssey Web Browser from '''SYS:Applications/OWB/OWB''' and download Grunch from its [http://geit.de/eng_grunch.html homepage] or from the [http://morphos-files.net/find.php?find=grunch MorphOS Files] site. Save the '''Grunch.lha''' archive file to any location, for example to Work partition or to Ram Disk. The archive isn't needed after the installation.&lt;br /&gt;
: [[File:GettingStarted_OWB4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Close the browser and use Ambient to browse to the location where you saved the Grunch.lha file. If you don't see the file, click the rightmost cycle gadget on the window to show all files. Double click the archive, open the Grunch directory, and double click the '''Grunch.install''' file to start the installer script. Running an installer directly from the unpacked archive is a bit of a shortcut which might not work with all programs, but let's demonstrate it anyway. The traditional and more failproof way would be to unpack an archive file to a temporary location and then run the installer script from an unarchived directory. Read more about installing third party software [[Installing_software | here]].&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Next''' button and select the destination location. The '''System:Applications''' path is OK unless you want to keep the bundled software and 3rd party software strictly separated. In that case you could make a new Applications directory on the Work partition, for example.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After the installation has finished, browse to the location where you installed the program and double click the '''Grunch''' icon. Grunch starts, but you'll have to wait a little while it does its initial checks and updates.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Start.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Before using the program any further, check the Grunch preferences. Select the '''Settings-&amp;gt;Grunch...''' option from the pulldown menus and open the '''Miscellaneous''' tab. I'd change the '''Temporary Directory''' path to somewhere else than to your system partition. If you have enough memory, you could have it even on the Ram Disk, but a temporary directory on the Work partition would be a safe bet.&lt;br /&gt;
&lt;br /&gt;
Click the file requester button at the end of the line to browse to the wanted location. The ''':''' button shows the available volumes, and you can also create new directories from the right click contextual menu on the file requester.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You should check the '''Path''' tab next, and think twice if you want to change them from the default paths. The default paths are OK if you think that all 3rd party and bundled software can reside mixed in the same directories and if you have enough free space on the system partition. But if you like to keep 3rd party and bundled software separated and have the system directories as clean as possible, change the paths now. You could make suitable directories on the Work partition, for instance.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
When you're happy with the settings, click the Save button.&lt;br /&gt;
&lt;br /&gt;
The Grunch icon can also be dragged to a panel for quick access later.&lt;br /&gt;
: [[File:GettingStarted_Dragging_Grunch_to_Panel.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software with Grunch ===&lt;br /&gt;
==== rexxsyslib.library ====&lt;br /&gt;
The rexxsyslib.library file enables the ARexx scripting language support on your system and it should be installed as early as possible. Many programs and their features rely on a working ARexx environment. Select it from the list and click the '''Install''' button on Grunch. You may need a reboot before it'll be in use.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software1.png]]&lt;br /&gt;
&lt;br /&gt;
==== Updating OWB ====&lt;br /&gt;
MorphOS usually comes with a bit old version of the OWB browser and you should check for a newer version. Select OWB from the list and click the '''Check''' button.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software2.png]]&lt;br /&gt;
&lt;br /&gt;
You probably have an old version, so click the '''Update...''' button and wait for it to finish.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software3.png]]&lt;br /&gt;
&lt;br /&gt;
You could also change the mode to Update.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software4.png]]&lt;br /&gt;
&lt;br /&gt;
==== MPlayer ====&lt;br /&gt;
MPlayer is hands down the best video player on MorphOS, just install it. It also works as an audio player with comprehensive support for different formats.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software5.png]]&lt;br /&gt;
&lt;br /&gt;
==== PowerSDL ====&lt;br /&gt;
PowerSDL libraries are required for many software ports from other platforms. It's better to install them as well.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software6.png]]&lt;br /&gt;
&lt;br /&gt;
==== CRABUM ====&lt;br /&gt;
CRABUM lets you to customize the pulldown menus on Ambient. It's quite handy for adding some hidden but quickly available features and shortcuts. We'll need this for some later examples.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software7.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Installed Software ===&lt;br /&gt;
==== Configuring Odyssey Web Browser ====&lt;br /&gt;
Here are few examples or suggestions for the initial configuration of OWB. Do the steps you like.&lt;br /&gt;
===== Downloading More Suitable Fonts for OWB =====&lt;br /&gt;
The fonts provided with MorphOS aren't designed with web usage in mind and it's better to download certain Microsoft fonts for the browser. Luckily it's an easy job to do, because there's a downloader script included in the OWB's directory.&lt;br /&gt;
&lt;br /&gt;
Open the '''SYS:Applications/OWB''' directory and double click the '''Download Fonts''' icon. Note: if the script doesn't seem to work, try [http://www.morphos-storage.net/?page=Network/Web&amp;amp;file=Download_Fonts_for_OWB.lha this one] instead.&lt;br /&gt;
: [[File:GettingStarted_OWB1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Yes''' on the requester and wait patiently for  the downloading and installing of the fonts. The output window closes when the process is finished.&lt;br /&gt;
: [[File:GettingStarted_OWB2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
OWB initializes the fonts on the first run, but it will start much quicker next time.&lt;br /&gt;
: [[File:GettingStarted_OWB3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Making OWB to Use Its Own Screen =====&lt;br /&gt;
A browser is usually an application people want to use in a full size window and on Amigaish systems it makes sense to put it on its own screen. When used on a separate screen it leaves more space for other programs on the Ambient screen, and you don't have such a hassle when handling them all. Bringing screens to front is also a very quick operation, you'll never see any slowdowns like on other systems where you reopen full size windows from taskbars, for example.&lt;br /&gt;
&lt;br /&gt;
You could send a program to a new screen with the &amp;quot;Jump to Screen -&amp;gt; New&amp;quot; option from the window popup gadget, but it's mainly designed for temporary usage. Let's do the configuration more proper way instead.&lt;br /&gt;
&lt;br /&gt;
Launch OWB, click on the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]], and select '''MUI Settings...'''. Another way to access the MUI settings would be from the '''Settings-&amp;gt;MUI...''' pulldown menu option when OWB's window is active.&lt;br /&gt;
: [[File:GettingStarted_OWB5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the '''Screen''' page, select the '''customized public screen from MUI screen database''' option, and click the '''New...''' button.&lt;br /&gt;
&lt;br /&gt;
The Edit Screen window opens. The name field is for the screen name and the title field for the screen title text. They can be anything you want, but it's better to keep them informative. '''OWB''' would be a good screen name now and '''Odyssey Web Browser''' for the title. Check if the default screen mode is what you want. Be also sure that the '''Close automatically''' option is enabled.&lt;br /&gt;
&lt;br /&gt;
It might be a good idea to disable the '''Enhanced Display''' option, because it doesn't give that much advantage with full screen applications. Graphics memory usage will also be lower, and it might be crucial to save some graphics memory on systems with less than 128 MB memory on the graphics card. Read more about how to reduce graphics memory usage [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
Click the '''Ok''' button on the Edit Screen window and the '''Save''' button on the MUI Settings window.&lt;br /&gt;
&lt;br /&gt;
Note: this method can be used with all MUI programs to put them on their own screens, from shell windows to small utilities, bigger applications, and games. I prefer to use the [[Applications/Showgirls|ShowGirls]] image viewer and other bigger applications on their own screens. Several MUI programs can also share the same custom screen, as it isn't limited just to a program per screen. You could for example group some network programs to one screen, and some other programs to another screen, etc.&lt;br /&gt;
: [[File:GettingStarted_OWB6.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The OWB window doesn't probably have optimal size and position on the newly created screen. Right click over the [[Fundamentals_of_MorphOS#Window_border_gadgets | zoom gadget]] and select the '''Maximize''' option or if you configured the zoom gadget as suggested [[Getting_Started#Screens_and_Desktop | earlier]], click the zoom gadget twice. The maximize option leaves the screen title bar visible, but otherwise resizes the window to full screen size. Select the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]] to save the window position permanently.&lt;br /&gt;
: [[File:Tips_Zoommenu.png|top]] [[File:GettingStarted_OWB7.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Open PDF Files Automatically =====&lt;br /&gt;
OWB's MIME Types settings can be used to configure automatic actions to files of certain types. Here is an example of how to show PDF files automatically with the [[Applications/VPDF|VPDF]] application when clicked on the browser.&lt;br /&gt;
&lt;br /&gt;
Open OWB's settings from the '''Settings-&amp;gt;Preferences...''' pulldown menu option and select the '''MIME Types''' page. Click the '''Add''' button and fill in the information below like this:&lt;br /&gt;
 MIME Type: '''application''' / '''pdf'''&lt;br /&gt;
 Extension: '''pdf'''&lt;br /&gt;
 Action: '''External Viewer''', Viewer: '''SYS:Applications/VPDF/VPDF''', and the last unnamed field: '''&amp;amp;#37;f'''&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button.&lt;br /&gt;
&lt;br /&gt;
If you now click a PDF file on a web page, the file is downloaded to a temporary location and shown on VPDF automatically.&lt;br /&gt;
: [[File:GettingStarted_OWB8.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Getting YouTube Videos to Play Better on the Browser Window =====&lt;br /&gt;
YouTube videos should play on OWB by default, but there are a thing or two to note.&lt;br /&gt;
&lt;br /&gt;
Playing videos in a small embedded window is a very CPU intensive task and not quite smooth on most systems. Moving the video playback from the embedded mode to the overlay mode helps the task hugely. This can be achieved with the YouTube Fullscreen Fix script. Videos will be shown in a nearly fullscreen window using the overlay functions and the CPU load may drop from 100&amp;amp;#37; even to 30&amp;amp;#37; on a G4 system, resulting in perfectly smooth playback of course.&lt;br /&gt;
&lt;br /&gt;
'''Download''' the latest script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js (YouTube changes its internals randomly and that's why the script on the MorphOS ISO is probably old already. Grunch also may have an old version and manual installation is highly advisable).&lt;br /&gt;
&lt;br /&gt;
Copy the downloaded script to the '''System:Applications/OWB/Scripts''' directory.&lt;br /&gt;
: [[File:GettingStarted_OWB9.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Scripts window from the '''Windows-&amp;gt;Scripts...''' pulldown menu entry on OWB.&lt;br /&gt;
: [[File:GettingStarted_OWB10.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Add''' button on the Scripts window and select the YouTube_Fullscreen_Fix.js file.&lt;br /&gt;
: [[File:GettingStarted_OWB11.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Make sure that the '''Enable''' setting is chosen and close the window. A '''restart''' of the browser is needed to activate the script, but after that you should be able to get any YouTube video to the smooth fullscreen mode by clicking the &amp;quot;fullscreen&amp;quot; or &amp;quot;large player&amp;quot; buttons on the video '''after the video playback has started'''. If you're watching a video embedded on some other external site, click the settings button instead. '''Double click''' the fullscreen video to get it to the embedded mode again.&lt;br /&gt;
: [[File:GettingStarted_OWB12.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Content Blocking and YouTube =====&lt;br /&gt;
If you have enabled the Content Blocking (AdBlock) option on the OWB settings, YouTube videos with ads will also get blocked. You can make a rule to the content blocking settings to allow those videos to be shown.&lt;br /&gt;
&lt;br /&gt;
Open '''Windows-&amp;gt;Content Blocking...''' from OWB's pulldown menus, click the '''Add''' button, and write '''youtube.com''' to the Rule line, and close the window.&lt;br /&gt;
: [[File:OWB_ContentBlockingYT.png]]&lt;br /&gt;
&lt;br /&gt;
If you have any other problems with the YouTube playback, check the [[Tips_and_Tricks#Problems_with_YouTube_Videos|Tips and Tricks]] page for more information.&lt;br /&gt;
&lt;br /&gt;
===== Configuring Fonts =====&lt;br /&gt;
&lt;br /&gt;
Browsers come with font settings. However, these settings are often neglected. Web developer has at least three options for selecting a font which would be displayed by default on your browser screen. &lt;br /&gt;
It can be a generic font, &amp;quot;hand picked&amp;quot; local font-family, or on-the-fly downloaded web font. Nevertheless the user still has the choice which font he or she actually wants to use. Reasons: privacy, security, speed, aesthetic.&lt;br /&gt;
&lt;br /&gt;
MorphOS is bundled with True Type, PostScript and Amiga Bitmap fonts.&lt;br /&gt;
OWB uses fontconfig for font handling. Fonts are cached whenever a change in font directories is detected.&lt;br /&gt;
If you want to use your fonts exclusively - fonts.conf should only use the path where you store the fonts (for example '''SYS:Fonts/_ttf''').&lt;br /&gt;
&lt;br /&gt;
Fontconfig is a library providing font configuration, customization and application access. It uses freetype library which supports plenty of font formats (excluding Amiga Bitmap fonts).&lt;br /&gt;
Presets are stored in the '''MOSSYS:Fontconfig/conf.avail''' directory.&lt;br /&gt;
&lt;br /&gt;
'''FONTS:Fontconfig/fonts.conf''' (configured font dirs)&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;!-- Font directory list --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;SYS:Fonts/_pcf&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;SYS:Fonts/_pfb&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pcf&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pfb&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_ttf&amp;lt;/dir&amp;gt; --&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Example settings:'''&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/conf.d/51-local.conf'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
	&amp;lt;!-- Load local system customization file --&amp;gt;&lt;br /&gt;
	&amp;lt;include ignore_missing=&amp;quot;yes&amp;quot;&amp;gt;local.conf&amp;lt;/include&amp;gt;&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/local.conf''' (turns off antialias for font sizes smaller than 16 and disables autohint)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;!-- /etc/fonts/local.conf file for local customizations --&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;size&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;pixelsize&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;autohint&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Blocking fonts'''&lt;br /&gt;
&lt;br /&gt;
In OWB, go to '''Settings-&amp;gt;Fonts''' and choose default fonts and sizes.&lt;br /&gt;
&lt;br /&gt;
To disable remote web fonts this line needs to be added to its filter '''SYS:Applications/OWB/Conf/blocked.prefs''':&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
/\.ttf|\.otf|\.woff|\.woff2\?/&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
A specific font can be whitelisted too:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
@@/*actually-nice-font.ttf&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
This isn't ideal. OWB will try block anything_not_whitelisted.ttf, even if you look for a nicefont.ttf in Google Search.&lt;br /&gt;
&lt;br /&gt;
==== Configuring MPlayer ====&lt;br /&gt;
===== General Options =====&lt;br /&gt;
The default configuration of MPlayer is quite fine, but here are a few options I like to set myself. Start MPlayer in the GUI mode by double clicking the GMPlayer icon in the MPlayer directory. There's just one MPlayer executable, but two icons with different [[Fundamentals_of_MorphOS#Icon_Tool_Types|tooltypes]] to start the program with or without the GUI mode.&lt;br /&gt;
&lt;br /&gt;
With default options MPlayer scales the played video to fit the current window dimensions which typically leaves big empty borders around the video. To get the window dimensions to change with the video dimensions, select the '''Video-&amp;gt;Window Dimension-&amp;gt;100&amp;amp;#37;''' option, and '''Settings-&amp;gt;Save''' to save it as a default setting.&lt;br /&gt;
: [[File:GettingStarted_MPlayer.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Preferences window by selecting the '''Settings-&amp;gt;Preferences...''' option from MPlayer's pulldown menus. There are some settings to consider.&lt;br /&gt;
&lt;br /&gt;
The Audio Driver has two audio output options for AHI to choose from. The default '''ahi''' option outputs the audio through the ''Music Unit'', which gives the best audio quality, but blocks simultaneous audio from any other sources. The '''ahi_dev''' option uses the device mode which can be shared with the other sources, but it results in a slight decrease in the audio quality. So, if you want to be able to watch videos while some other program, like a music player, would still continue with audio output, select the '''ahi_dev''' option.&lt;br /&gt;
&lt;br /&gt;
If you don't like any usage data gathering, disable the '''Remember last visited path''' option :)&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Preferences.png]]&lt;br /&gt;
&lt;br /&gt;
===== Setting MPlayer as the Default Player on Ambient  =====&lt;br /&gt;
MorphOS doesn't have any default player for videos and double clicking a video file from Ambient results in an error requester. MPlayer can be set as the default video player by editing the Ambient MIME type settings.&lt;br /&gt;
&lt;br /&gt;
Open the '''Ambient Settings''' window and the '''Mime''' page. With the built-in MIME editor you can add different kinds of actions for different file formats or classes. Let's add MPlayer as the default player for all video files, not just for some individual video formats.&lt;br /&gt;
&lt;br /&gt;
Select '''video''' from the right-hand side list tree and click the '''Edit''' button. Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
&lt;br /&gt;
In the Action Editor window type a name for the action, for example '''Play''', and click the '''Add''' button on that window too.&lt;br /&gt;
&lt;br /&gt;
Change the AmigaDOS command to '''Run &amp;gt;NIL: SYS:Applications/MPlayer/MPlayer -gui 1 &amp;amp;#37;sp''' (change the path to the MPlayer executable if you have it in a different location) and change the Event type to '''DoubleClick'''. Note: the ''-gui 1'' option, which starts MPlayer in the GUI mode, has to be written in lower case, having it in upper case doesn't work!&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Adding_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Ok''', '''Ok''', and '''Save''' buttons.&lt;br /&gt;
&lt;br /&gt;
If you now double click a video file in Ambient, it gets played on MPlayer. You can also see the Play option in the contextual menu when right clicking the video file.&lt;br /&gt;
: [[File:GettingStarted_MPlayer2.png|320px]] [[File:GettingStarted_MPlayer_Working_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You can add several actions as contextual menu events if you want to have more options for opening videos. Only imagination is the limit, and you can for example have contextual menu entries to start MPlayer playback with filters skipped (use the ''-lavdopts skiploopfilter=all'' option to speed up the video playback a little) and have an option to convert the video with mencoder etc.&lt;br /&gt;
: [[File:GettingStarted_ActionEditor2.png|230px]]&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with FlowStudio ====&lt;br /&gt;
&lt;br /&gt;
Custom menus in Ambient can be added with a lua script. Menus can be edited and reloaded by the respective menu items.&lt;br /&gt;
&lt;br /&gt;
'''SYS:WBStartup/menus.lua''' script:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
require('ipc')&lt;br /&gt;
address('AMBIENT')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m1-0&amp;quot;                               title=&amp;quot;Tools&amp;quot;             type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-1&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;MUICON&amp;quot;          type=item shortcut=&amp;quot;S&amp;quot; command=&amp;quot;*&amp;quot;SYS:Tools/MUI Shell*&amp;quot;&amp;quot;                                              commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-2&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;Snoopium&amp;quot;        type=item command=&amp;quot;SYS:Tools/Snoopium&amp;quot;                                                                     commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-3&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-4&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;Mounter&amp;quot;         type=item command=&amp;quot;SYS:Tools/Mounter&amp;quot;                                                                        commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-5&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;HDConfig&amp;quot;        type=item command=&amp;quot;SYS:Tools/HDConfig&amp;quot;                                                                       commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;&amp;quot;                   type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6-0&amp;quot; parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;Menu&amp;quot;            type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6-1&amp;quot; parentid=&amp;quot;m1-6-0&amp;quot;  title=&amp;quot;Edit&amp;quot;              type=item command=&amp;quot;SYS:Applications/FlowStudio/FlowStudio SYS:WBStartup/menus.lua&amp;quot;        commandtype=amigados')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6-2&amp;quot; parentid=&amp;quot;m1-6-0&amp;quot;  title=&amp;quot;Reload&amp;quot;          type=item command=&amp;quot;RXCmd AMBIENT *&amp;quot;menu remove*&amp;quot; &amp;amp;&amp;amp; LuaX SYS:WBStartup/menus.lua&amp;quot;    commandtype=amigados')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m2-0&amp;quot;                               title=&amp;quot;Apps&amp;quot;             type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-1&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;FlowStudio&amp;quot;      type=item shortcut=&amp;quot;W&amp;quot; command=&amp;quot;Run &amp;gt;NIL: SYS:Applications/FlowStudio/FlowStudio&amp;quot;          commandtype=amigados')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-2&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;&amp;quot;                    type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-3&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;OWB&amp;quot;              type=item shortcut=&amp;quot;B&amp;quot; command=&amp;quot;SYS:Applications/OWB/OWB&amp;quot;                                          commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-4&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;Transfer&amp;quot;         type=item command=&amp;quot;SYS:Applications/Transfer/Transfer&amp;quot;                                                   commandtype=workbench')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m3-0&amp;quot;                               title=&amp;quot;Utils&amp;quot;               type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-1&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;MUIProCalc&amp;quot;      type=item command=&amp;quot;SYS:Utilities/MUIProCalc&amp;quot;                                                                commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-2&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-3&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;Zoom&amp;quot;              type=item shortcut=&amp;quot;Z&amp;quot; command=&amp;quot;SYS:Utilities/Zoom&amp;quot;                                                      commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-4&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-5&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;AudioRecorder&amp;quot;  type=item command=&amp;quot;SYS:Utilities/AudioRecorder&amp;quot;                                                             commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-6&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;JukeBox&amp;quot;           type=item shortcut=&amp;quot;J&amp;quot; command=&amp;quot;SYS:Utilities/JukeBox&amp;quot;                                                   commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-7&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-8&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;GraphicsBoards&amp;quot;  type=item command=&amp;quot;SYS:Utilities/GraphicBoards&amp;quot;                                                           commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-9&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;TaskManager&amp;quot;    type=item shortcut=&amp;quot;T&amp;quot; command=&amp;quot;SYS:Utilities/TaskManager&amp;quot;                                            commandtype=workbench')&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Create .info icon for menus.lua''':&lt;br /&gt;
&lt;br /&gt;
'''Copy ENV:SYS/def_tool.info SYS:WBStartup/menus.lua.info'''&lt;br /&gt;
&lt;br /&gt;
'''Set icon info''':&lt;br /&gt;
&lt;br /&gt;
Select menus.lua and open its Information window (COMMAND I). Set Type as a '''Project''', write '''LuaX''' as a Default Tool and press '''Save'''.&lt;br /&gt;
&lt;br /&gt;
Now you can run menus.lua script and enjoy Ambient menus.&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with CRABUM ====&lt;br /&gt;
&lt;br /&gt;
You can add custom pulldown menus to Ambient with ARexx scripts created by the CRABUM program. It's a good way to launch programs or scripts which you don't want to have on panels. Installation of [[Getting_Started#rexxsyslib.library|rexxsyslib.library]] is required.&lt;br /&gt;
&lt;br /&gt;
Let's create an Edit menu with options to edit different system startup scripts. Double click the CRABUM icon from the SYS:Utilities/CRABUM directory if you installed it with the default options.&lt;br /&gt;
&lt;br /&gt;
# Click the '''Menu''' button to add a new menu and change its title to '''Edit'''.&lt;br /&gt;
# Click the '''Item''' button to add a new item under the created menu.&lt;br /&gt;
# Type '''User-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-startup''' to the AmigaDOS command line. &amp;quot;Run &amp;gt;NIL:&amp;quot; starts the Ed program as a background process and it won't block Ambient while it is running.&lt;br /&gt;
# Create an another item by clicking the '''Item''' button.&lt;br /&gt;
# Type '''User-network-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-network-startup''' to the AmigaDOS command line.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM1.png|320px]]&lt;br /&gt;
# Click the '''Save''' button to save the resulting ARexx script.&lt;br /&gt;
# If you save the file to the SYS:WBStartup drawer, it will be launched automatically at boot time. Enter a suitable name for the file, for example '''Edit-menu'''. Click the '''Ok''' button.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After a reboot (or doubleclicking of the file) you'll have the new Edit menu on the Ambient pulldown menus and you can easily open the system files for editing.&lt;br /&gt;
: [[File:GettingStarted_CRABUM3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
== More Configuring ==&lt;br /&gt;
=== Synchronizing the Clock with an Internet Time Server ===&lt;br /&gt;
The system clock can be synchronized manually from the MorphOS Preferences application by clicking the '''Set date and time using the Internet''' button in the Time preferences.&lt;br /&gt;
: [[File:MorphOS_Preferences_Time.png|320px]]&lt;br /&gt;
&lt;br /&gt;
There's also the [[Shell_Commands/SetClockNTP|SetClockNTP]] shell command which can be launched manually or automatically at boot time. To synchronize the time every time the system starts edit the '''S:user-network-startup''' file and remove the semi-colon from the SetClockNTP line.&lt;br /&gt;
&lt;br /&gt;
To edit the S:user-network-startup file open the shell (or the Execute Command prompt) and type '''Ed S:user-network-startup''', or open the System partition, select the '''All Files''' mode, browse to the '''S''' directory and select the '''Edit...''' option from the right click contextual menu. Or if you configured the Edit menu with CRABUM earlier, use it now.&lt;br /&gt;
: [[File:GettingStarted_Enable_SetClockNTP.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Shell ===&lt;br /&gt;
==== Editing the Shell-startup file ====&lt;br /&gt;
The shell can be customized with the shell-startup file, but by default the file is only found in a MorphOS system directory where the user shouldn't do any modifications. It must be copied to a user directory first to make any changes to it. Open a new shell window and type '''Copy MOSSYS:S/shell-startup SYS:S/shell-startup''', and then edit it for example with the '''Ed SYS:S/shell-startup''' command. The shell-startup file is executed every time a new shell window is opened.&lt;br /&gt;
: [[File:GettingStarted_shell-startup.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Adding Paths ====&lt;br /&gt;
There are some useful shell commands around the installed system which aren't in the system's search path and thus you'll have to enter their complete paths when using them. Adding their locations to the search path allows them to be run just by their names, which is much more convenient.&lt;br /&gt;
&lt;br /&gt;
Here are few suggestions to add to the '''SYS:S/shell-startup''' file (remember the previous step first!). Or if you want them to be available globally on all occasions, they can be added to the '''S:user-startup''' file instead.&lt;br /&gt;
* '''Path SYS:Applications/RemoteShell/Files ADD''' adds SSH related commands like scp, sftp, ssh, etc to the search path. Note: use the [[Applications/RemoteShell|Remote Shell]] application for regular SSH sessions, because it supports arrow keys and other things better.&lt;br /&gt;
* '''Path SYS:Applications/OWB/Datas ADD''' adds wget to the search path.&lt;br /&gt;
* '''Path SYS:Applications/MPlayer ADD''' adds MPlayer and mencoder to the search path if you have installed MPlayer. Change the path if you have installed it elsewhere.&lt;br /&gt;
&lt;br /&gt;
==== Configuring the GUI ====&lt;br /&gt;
There are many buttons and hotkeys to add to the shell window besides the default ones. Check the preferences by selecting the '''Settings-&amp;gt;Edit Prefs...''' option from the Shell's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Available functions can be dragged to '''Hotkeys''' or '''Buttons''' lists and the changes are seen in real time in the shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You may also want to set the default window size and position for new shell windows on the '''Settings''' tab. Click the '''Get from window''' button to get values from the current shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Remember to save the modifications in the '''Settings''' menu.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Setting Jukebox as the Default Player for MP3 Files ===&lt;br /&gt;
If you double click an MP3 file in an Ambient window, it is played with the very simple internal player. Here are two solutions to change the default player to the more advanced [[Utilities/Jukebox|Jukebox]] music player. Ambient's internal player is still left to the context menu as an option.&lt;br /&gt;
==== Simple Solution ====&lt;br /&gt;
A simple solution is just to create a new mpeg audio MIME type definition which just launches the Jukebox player with the double clicked filename as an argument.&lt;br /&gt;
# Open the Mime page in the Ambient settings, select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''Run &amp;gt;NIL: SYS:Utilities/Jukebox &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and you should see this in the MIME Editor window.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Save''' buttons. If you double click an MP3 file now, Jukebox starts and plays the clicked file. There are also two entires in the right click contextual menu and the option which is used for the double click action is written in bold.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Advanced Solution ====&lt;br /&gt;
An advanced solution is to use the third party [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script. It will give more flexible options to add files to Jukebox, and we'll learn how to add submenus into context menus. There are shortcuts to install the script if you read the documentation in the archive, but let's do this manually to learn the configuration method better. It will be helpful in the future when configuring any other filetypes.&lt;br /&gt;
&lt;br /&gt;
# Download the script archive from [http://aminet.net/package/mus/play/JukeboxAdder Aminet] or from [http://morphos-files.net/find.php?find=jukeboxadder MorphOS Files].&lt;br /&gt;
# Copy the '''jukeboxadder.lua''' file from the archive to the '''SYS:S/''' directory.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder1.png|320px]]&lt;br /&gt;
# Open the '''Mime''' page in the '''Ambient settings''', select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua PLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and then click '''Add''' again in the MIME Editor window to create more ways to add files to Jukebox from the context menus.&lt;br /&gt;
# Type '''Add to Jukebox''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua ADD &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string. This will create a submenu named ''Jukebox'' in the context menu and place the new ''Add to Jukebox'' option there.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Add''' once again to create the last entry.&lt;br /&gt;
# Type '''Add to Jukebox and Play''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''MOSSYS:C/LuaX S:jukeboxadder.lua ADDPLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder4.png|320px]]&lt;br /&gt;
# Click '''Ok''', '''Ok''', and '''Save'''. Now you can see more options in the context menu for MP3 files and double clicking will always clear the previous songs and play the new song immediately.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
It is also possible to add the same functionality for context menus of directories if you want to be able to add whole directories to Jukebox at once. There's a special '''internal -&amp;gt; x-morphos-globalaction-directory''' MIME type which can be used to add context menu entries for all directories. Repeat the previous steps (6-18) for it, but make all '''Event types''' to use the '''Menu''' option (in step 9 too).&lt;br /&gt;
: [[File:GettingStarted_JukeboxAdder6.png|320px]] [[File:GettingStarted_JukeboxAdder7.png|320px]] [[File:GettingStarted_JukeboxAdder8.png|320px]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3878</id>
		<title>Getting Started</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3878"/>
				<updated>2018-06-19T19:42:54Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Configuring the Installed Software */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== A Beginner's Guide to MorphOS ==&lt;br /&gt;
&lt;br /&gt;
You have installed MorphOS to a compatible machine, but... now what? You could always go and install a pre-configured package like Chrysalis, but you would end up with a system configured for someone else's taste and you still wouldn't know how to actually use the operating system. If you are in this situation and would like to learn how MorphOS works, this is a tutorial for you! The tutorial will guide you through the things you should do and notice after a fresh install, with practical examples from basic configuration options to installing new software. It won't cover all the details and is just an opinion on how to proceed, but it should give you some knowledge how to continue on your own and make your own decisions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting Comfortable with the User Interface and the Ambient Desktop ==&lt;br /&gt;
=== The First Boot ===&lt;br /&gt;
&lt;br /&gt;
After a boot you're presented with the plain looking Ambient, the desktop environment of MorphOS. The first thing you should learn is to get familiar with the basic usage, and to tune the interface settings so that they won't annoy you. The worst thing is if a user plays around a bit and just curses at the system when it doesn't work as expected or wanted. You aren't forced into just one kind of behaviour with MorphOS!&lt;br /&gt;
: [[File:GettingStarted_Ambient.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Right mouse click is widely used on MorphOS and if you're using a device without a physical button for it, check the tips over [[Tips_and_Tricks#How_to_Use_RMB_with_One-button_Mouse | here]]. Pressing the right mouse button over the Ambient screen opens Ambient's pulldown menus where you can find few important options. For example, options to shut down the system, to open a new shell window, or to open system settings.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Shutdown.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== System Settings ===&lt;br /&gt;
&lt;br /&gt;
The MorphOS Preferences application is used to edit system-wide settings. It can be launched from the Ambient's pulldown menu by selecting the &amp;quot;Settings-&amp;gt;System...&amp;quot; menu option or by browsing to the System:Prefs/ drawer and double clicking the Preferences icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_System_Settings.png]] [[File:GettingStarted_MorphOS_Preferences.png|237px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Screens ====&lt;br /&gt;
&lt;br /&gt;
If MorphOS didn't get the optimal resolution of your monitor with DDC, a different screen mode can be selected from the Screens settings. If the wanted mode isn't seen there, open the Monitors settings instead to create a completely new mode.&lt;br /&gt;
&lt;br /&gt;
If you have a graphics card with a low amount of memory, you can try to make the memory consumption smaller by disabling the Enhanced Display setting (3D accelerated graphics functions for 2D screens) or by reducing the color depth. More information can be found  [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
MorphOS skins (themes for the graphical appearance) can also be changed from the Screens settings.&lt;br /&gt;
&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== IControl ====&lt;br /&gt;
&lt;br /&gt;
IControl settings are the most important settings for the overall user experience. This is the place to look in order to avoid the usual comments like ''&amp;quot;Why doesn't X work like Y in the other OS?&amp;quot;'', ''&amp;quot;Why there isn't a feature Z?&amp;quot;'', ''&amp;quot;I can't use a system like this!&amp;quot;''. Everyone should check these settings first before going any further.&lt;br /&gt;
&lt;br /&gt;
===== Hotkeys =====&lt;br /&gt;
MorphOS has many nice features to use with keyboard shortcuts or mouse buttons, but only few are activated by default. Let's activate more!&lt;br /&gt;
&lt;br /&gt;
To add a new hotkey for the wanted function click the popup button on the right side, select &amp;quot;'''Sample'''&amp;quot;, and press the wanted key combination. The pressed combination is then recorded on the corresponding line and should be shown there. Repeat the procedure if you didn't get it as wanted on the first try. Changed settings will be taken into use after you click the Save or Use button.&lt;br /&gt;
&lt;br /&gt;
Here is how to set the &amp;quot;control left-alt c&amp;quot; key combination to '''center the active window''' on the screen:&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Hotkeys2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Here are some other recommendations to activate, but feel free to use your own preferences for the hotkeys:&lt;br /&gt;
* '''Active Window: To Back''' - double click with middle mouse button to send a window back of other windows.&lt;br /&gt;
* '''Active Window: Zoom''' - &amp;quot;control left-alt m&amp;quot;, to toggle between a maximized and minimized window.&lt;br /&gt;
* '''Active Window: Activate Next''' - &amp;quot;left-command tab&amp;quot;, to have the ''alt-tab'' functionality found on many other operating systems. Using ctrl-tab or alt-tab isn't recommended because they would overlap with the shell's functionality on MorphOS. Command-tab also happens be the same in OS X.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys3.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Note: You can also add several hotkeys for a function by selecting the New Hotkey option from the popup button's menu.&lt;br /&gt;
&lt;br /&gt;
===== Screens and Desktop =====&lt;br /&gt;
&lt;br /&gt;
Important options concerning how windows and menus behave can be found on the Screens and Desktop settings.&lt;br /&gt;
&lt;br /&gt;
I'd recommend turning on the '''Maximize window when clicking on the Zoom gadget''' option. The Zoom gadget will then toggle the window size between full screen (with the screen title bar still visible) and the initial window size and position. I find it much more comfortable than the legacy placement between two obscure positions. The previously configured Zoom hotkey will also work better with this option enabled.&lt;br /&gt;
&lt;br /&gt;
If you prefer being able to drag windows out of the screen without pressing any qualifier key, like on mainstream systems, select the '''When dragging windows... allow them to be placed out of screen, unless Control is pressed''' option.&lt;br /&gt;
&lt;br /&gt;
The default behaviour of the pulldown menus may be a bit unfamiliar for old Amiga users, but there are several options to get them working as expected. I like to disable the '''Menus shall remain opened even when mouse button is released''' option and enable the '''Open menus under mouse pointer outside screen titlebar area''' option.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Touchpad ====&lt;br /&gt;
&lt;br /&gt;
If you're using a laptop system, check the Touchpad setttings. You might want to disable clicking from the pad to avoid any accidental clicks.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Touchpad.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Laptop ====&lt;br /&gt;
&lt;br /&gt;
If you're not a Mac user, you might find it odd that you need to press the fn key when using the function keys for normal activities, and not when modifying, for example, the screen brightness. The '''Press and hold the fn key to modify screen brightness, audio volume, etc.''' option will change the functionality the other way around.&lt;br /&gt;
&lt;br /&gt;
Some systems also have the '''Automatic LCD brightness and keyboard backlight control''' option here. Disable it if you're annoyed by changing lightning.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Laptop.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Windows ===&lt;br /&gt;
&lt;br /&gt;
The first icon you see on the Ambient desktop is the &amp;quot;'''My MorphOS'''&amp;quot; icon. By double clicking it you'll get a window with icons of all volumes and assigns of the system. It works like a root directory with quick access to different locations.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS.png|320px]]&lt;br /&gt;
&lt;br /&gt;
If you find it a bit clumsy to work in the icon mode, like I do, you can change the view to '''the list mode''' from the cycle button on the right side of the window.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
With default settings Ambient doesn't remember the changed mode or other window properties next time you open it, but you can right click the window border or an empty area on the file lister to bring up a contextual window menu and select the &amp;quot;'''Snapshot-&amp;gt;Window'''&amp;quot; option to save the window properties. Default position and size for a window can be saved that way too. If you defined the centering hotkey earlier, you can try it now :)&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The same can also be done for normal directory windows. While &amp;quot;My MorphOS&amp;quot; window settings are exceptionally saved to Ambient's configuration files, normal directories' settings are saved to an icon file (a file with .info extension). If you change and save the mode for the Work: partition for example, you see a disk.info file appearing there.&lt;br /&gt;
: [[File:GettingStarted_Icon_Mode.png|320px]] [[File:GettingStarted_List_Mode_Snapshot.png|320px]] [[File:GettingStarted_List_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Displayed columns can be selected by right clicking the column title area, but modify the [[Getting_Started#Lister|default lister settings]] to your liking before starting to save settings for individual windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Lister_Columns.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Settings ===&lt;br /&gt;
&lt;br /&gt;
Ambient is actually a separate application itself and it has its own settings separated from the general system preferences. The previously mentioned system settings affect all programs and screens, but strictly desktop related settings are found in the Ambient settings. The Ambient Settings window can be opened by selecting the &amp;quot;Settings-&amp;gt;Ambient...&amp;quot; option from Ambient's pulldown menu.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Ambient_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
==== Miscellaneous ====&lt;br /&gt;
&lt;br /&gt;
The Miscellaneous page on the Ambient settings has a nice option to get the My MorphOS window opened when double clicking anywhere on the empty area of the desktop. It really speeds up the working when you don't have to move the mouse a long way to the top corner or dig the icon out from under some other windows. Enable it with the '''Double click on desktop opens MyMorphOS window''' option.&lt;br /&gt;
&lt;br /&gt;
The My MorphOS icon is just wasting space on the desktop after the previous setting and you can hide it by disabling the '''Display MyMorphOS icon''' option.&lt;br /&gt;
&lt;br /&gt;
If you like to have a bit more eye candy on the context menus, you can also enable the '''Show images in context menu''' option while you're here.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Misc.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Lister ====&lt;br /&gt;
The default properties of the list mode of Ambient windows can be changed on the Lister settings. Disable the '''Compact size display''' if you want to see exact file sizes in bytes always. You may also want to select different columns to be shown in the listers by double clicking items on the '''File Properties''' list to set them hidden or shown. '''Date &amp;amp; Time''' instead of just Date would probably be a common choice.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Lister.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Panels ====&lt;br /&gt;
&lt;br /&gt;
Many new users are wondering if there is any kind of dock application on MorphOS, because there isn't any shown by default. MorphOS has ''panels'' for that and you can have as many panels as you want on the desktop, arranged horizontally or vertically. The panels have features like zipping to hide and unhide them, sub panels and other Panel Object plugins, etc. There just isn't any configured by default and user can create a panel or panels how he likes.&lt;br /&gt;
&lt;br /&gt;
To create a new panel, open the Panels page on the Ambient settings and click the '''New Panel''' button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels1.png|320px]]&lt;br /&gt;
An empty panel can be dragged anywhere and you can find some of its settings on the '''Name &amp;amp; Look''' and '''Behaviour''' tabs. If you want to place the panel on a screen border the '''Attached to Borders''' option makes it easier. The '''Alpha''' option controls the transparency of a panel, but it only works if the Enhanced Display option for the Ambient screen enabled and working. The same applies to the '''Hide Dragbar''' option as well.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels2.png|320px]]&lt;br /&gt;
Programs can be added to the panel by dragging and dropping their icons to the panel list to the wanted position on the list tree, or to the panel itself. Items in the panel list can be rearranged by drag and drop too.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels3.png|320px]]&lt;br /&gt;
Available Panel Objects are listed on the right-hand side and they can be dragged and dropped to any position on the panel tree. All items on the panel may have their own settings, which are shown when an item is clicked once with the left mouse button. In this example picture a new sub panel has been created and its icon image is being changed to a custom one.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels4.png|320px]]&lt;br /&gt;
If you want to clone the color settings from the main panel to a sub panel, you can use the MUI clipboard to temporarily store a setting. Drag &amp;amp; drop the wanted color button to the clipboard button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels5.png|320px]]&lt;br /&gt;
Then activate the sub panel settings and drag &amp;amp; drop the clipboard button to the sub panel's color button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels6.png|320px]]&lt;br /&gt;
And here's a picture of the created panel with its sub panel in action. Remember to click the Save button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels7.png|320px]]&lt;br /&gt;
The panels also have a context menu that can be accessed with a right click. You'll have quick access to the panel settings and some other options there.&lt;br /&gt;
&lt;br /&gt;
If you lock a panel, items dragged to it aren't added to the panel anymore, but the dragged items are opened with the program you dropped them onto. Text files can be dropped onto the Scribble icon, MP3 files and directories can be dropped onto the Jukebox icon, video and audio files onto the MPlayer icon, and so on.&lt;br /&gt;
: [[File:GettingStarted_Panel_Locked1.png|320px]] [[File:GettingStarted_Panel_Locked2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Window ====&lt;br /&gt;
&lt;br /&gt;
Ambient windows are very configurable and users should at least check the buttons available for the toolbar. Just adding a few buttons can make a difference in usability. The buttons and other items can be dragged from the Available Buttons list to the Current Toolbar group, and vice versa to remove them from the toolbar. All changes are updated in real time to any open Ambient windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
In this example picture '''Makedir''' and '''Delete''' buttons are separated with the '''Space''' button, and they have been added into a row with other buttons. Also the '''Bookmarks''' button has been added as the last item on the toolbar. It always stays at the right border no matter how big a window is, because it's been added after the '''Flexible space''' button. &lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Keyboard ====&lt;br /&gt;
===== Built-in Command Hotkeys =====&lt;br /&gt;
Check the Ambient hotkeys from this section and change them to your liking. If you have a laptop without the numeric keypad, you should change hotkeys which are using numpad combinations by default. I, for example, am used to having the '''Cycle Mode''' option on the key above the tab key and the '''Cycle Submode''' option when the same key is pressed with the shift key. It feels somehow quicker to use them from there than from the numeric keypad with a standard keyboard too.&lt;br /&gt;
&lt;br /&gt;
===== Custom Command Hotkeys =====&lt;br /&gt;
Practically any functionality can be added to custom hotkey definitions. This might be a bit advanced topic, but let's show few definitions which will improve the usability.&lt;br /&gt;
&lt;br /&gt;
A new Ambient hotkey can be created by clicking the Add a Hotkey button. The first text field is for the name of the hotkey and it can be anything. The second text field is the actual keyboard combination to activate a function. The Edit Command button is used to define what actually happens when you press the hotkey in Ambient.&lt;br /&gt;
&lt;br /&gt;
Let's create two hotkeys which can be used to copy selected files' names as text to the clipboard, with and without the preceding path.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Copy name with path''' and the hotkey combination to '''ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si FULLPATH''', and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
* Click the '''Add a Hotkey''' button again, define the name as '''Copy name''' and the hotkey combination to '''rshift ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si''', and press the enter key. Click the '''Ok''' button, save the Ambient settings, and you're done.&lt;br /&gt;
&lt;br /&gt;
If you now select any files on an Ambient window and press the ''ralt c'' key combination, the selected file names with their full paths get copied to the clipboard and are available to be pasted to any other application. The ''rshift ralt c'' combination copies pathless file names to the clipboard.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Keyboard1.png|320px]] [[File:GettingStarted_Ambient_Settings_Keyboard2.png|320px]] [[File:GettingStarted_ActionEditor1.png|214px]]&lt;br /&gt;
&lt;br /&gt;
Another example which will extract any selected archive file to the ram disk with the ''lshift control e'' combination.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Extract to RAM''' and the hotkey combination to '''lshift control e'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Leave the action type to '''AmigaDOS''', type in the command '''XADUnFile &amp;amp;#37;sp RAM:''' , and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Screenbar Modules ===&lt;br /&gt;
&lt;br /&gt;
[[Screenbar_Modules | Screenbar modules]] are plugins which can populate the empty area on the screen title bar with some useful information and functionality. The modules are visible on every (MUI) [[Fundamentals_of_MorphOS#Screens | screen]], which makes them more useful than, for example, Panel Objects. Panel Objects are only seen on the Ambient screen and can be left under some other windows more easily.&lt;br /&gt;
&lt;br /&gt;
Screenbar modules can be enabled and disabled from the screen depth gadget menu. The menu also contains options to arrange order of the modules and to change their settings. The menu can be accessed by right clicking, or with a long left press, over the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget | screen depth gadget]].&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Menu.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Let's have a look at how to configure a few modules. Enable the '''CPU Monitor''', '''Drivelamps''', and '''Memory''' modules by, for example, multiselecting them at once. Reopen the screen depth gadget menu, select the '''Settings...''' option, and select CPU Monitor from the settings list. The CPU Monitor module is a bit narrow by default, so let's increase its width a little.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_CPU_Monitor.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Drivelamps module has more configuration options. Enable the '''Show lamp''' option for '''usbscsi.device''' if you want to see access indicators for both HD and USB drives. The default look doesn't seem to be that good for two lamps, but you can tune it a bit. Disabling the frame from the Look group (select None) and selecting the recessed frame for the Lamp Look group does some wonders already. You can also adjust the spacing options, if the lamps don't seem to match with the height of the CPU Monitor or other modules.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Drivelamps.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Memory module shows free memory in percents by default, but it can be changed to other types too. Click the popup button on the '''Information''' line to see the options. The information line can have any text, and for example a ''&amp;amp;#37;mfMB free'' line would show free memory in megabytes followed by the &amp;quot;MB free&amp;quot; text.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Memory.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== MUI Settings ===&lt;br /&gt;
&lt;br /&gt;
MUI is the default GUI toolkit of MorphOS and its looks and behaviour can be changed in almost every aspect. Its basic philosophy is to ''offer as much freedom as possible to users by taking away as much work as possible from programmers''. A user can modify the looks of MUI programs very drastically both globally and per program. It can be done by changing single settings or by loading complete themes (presets).&lt;br /&gt;
&lt;br /&gt;
The most important thing for a new user is to understand the difference between the global settings and settings of individual programs.&lt;br /&gt;
&lt;br /&gt;
The global settings are the default settings which will apply to any program using MUI. The global settings can be changed by selecting the '''Settings-&amp;gt;MUI...''' option from the Ambient's pulldown menus or by double clicking the '''SYS:Prefs/MUI''' icon.&lt;br /&gt;
&lt;br /&gt;
Each MUI program can also have its own MUI settings which will override the global settings, but be careful when changing for example the looks of an individual program. If you decide to change the global theme later, the changes made to the individual programs might not fit the global theme anymore. The MUI settings of a program can be found on its pulldown menu or from the window's [[Fundamentals_of_MorphOS#Window_border_gadgets | popup gadget]] menu. Ambient's MUI settings are found from the '''Settings-&amp;gt;Ambient MUI...''' option in the Ambient's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Let's change a couple of options in the global MUI settings as an example. Open the global MUI settings window.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_MUI_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
The default ghosting effect for buttons is a bit old-fashioned raster effect and it will look much better with just reduced visibility. Select the Buttons page and click the None option for the ghosted gadgets. The visibility can be changed with the slider below, but the default value will be fine too. You'll see the changes in real time on any MUI program, the Test button is a bit obsolete with the latest MUI. I also like to make the Active Gadgets Border a bit smaller than the original size. Click the Save button when you're satisfied.&lt;br /&gt;
: [[File:GettingStarted_MUI_Settings_Buttons.png|380px]]&lt;br /&gt;
&lt;br /&gt;
The Settings button in the top left corner opens a popup menu with options to reset the settings or load different presets.&lt;br /&gt;
&lt;br /&gt;
All MUI settings get saved to the ENVARC:MUI/ directory. If you mess too much with settings for individual programs, the last resort to revert the settings to default is to remove the corresponding settings files from that directory or restore them from a backup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hiding the Boot Image Partition on Macs ===&lt;br /&gt;
&lt;br /&gt;
On Macs you'll have a small HFS formatted partition which contains a few files needed to boot the system. The files are only used by [[Dictionary_of_Terms | Open Firmware]] at boot time and the user or MorphOS itself don't normally need them for anything. Open Firmware, as well as the MorphOS update wizard, can access the partition even if it's not mounted on MorphOS. If we disable the auto mounting of it, our desktop will look a bit cleaner and the crucial boot files will then be safe from accidents as well.&lt;br /&gt;
&lt;br /&gt;
Launch the [[Tools/HDConfig]] program and click on the small HFS partition. Its name should be '''DH0:''' if the system is installed with the default partition layout. Disable the '''Automatically mount partition''' option and click the '''OK''' button.&lt;br /&gt;
: [[File:GettingStarted_HDConfig1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button which is in the red area on the left side and accept the changes.&lt;br /&gt;
: [[File:GettingStarted_HDConfig2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Next time you boot the system, the partition isn't shown on the desktop. If you need to access it later for some reason, it can be mounted temporarily with the [[Tools/Mounter]] tool.&lt;br /&gt;
: [[File:GettingStarted_Ambient2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging the Drive Icons ===&lt;br /&gt;
The drive icons can be dragged to a different order and then saved to their positions by selecting the '''Snapshot''' option from the right click contextual menu. If the Ram Disk icon is dragged to the leftmost position and snapshot, it will appear at that position after a reboot and unsnapshot icons appear next to it.&lt;br /&gt;
: [[File:GettingStarted_Drive_Icons.png|320px]] [[File:GettingStarted_Drive_Icons_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installing, Updating, and Configuring Essential Software ==&lt;br /&gt;
&lt;br /&gt;
=== Checking the Network Connection ===&lt;br /&gt;
&lt;br /&gt;
Before continuing to installing new software, let's check if your machine is properly connected to the Internet.&lt;br /&gt;
&lt;br /&gt;
Open the shell by selecting the '''Ambient-&amp;gt;New Shell...''' option from the Ambient's pulldown menus, or by pressing '''rcommand n''' keyboard combination or doubleclicking the '''SYS:Tools/MUI Shell''' icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_New_Shell.png]]&lt;br /&gt;
&lt;br /&gt;
Check the Internet connection by pinging some hostname on the Internet. Type for example '''ping www.google.com''' on the shell window. If you get replies from the host, the connection is OK and you can proceed by pressing '''CTRL C''' to quit the Ping command and closing the shell window. If you don't get any replies with time values, quit the pinging by the CTRL C combination and read the [[Configuring_Network | Configuring a Network Connection]] tutorial.&lt;br /&gt;
: [[File:GettingStarted_Ping.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Grunch ===&lt;br /&gt;
&lt;br /&gt;
[http://geit.de/eng_grunch.html Grunch] is an advanced software package manager, which can install, update, and uninstall software. It's a good starting point for new users and I'd advice everyone to check what it has to offer before visiting [[Links#File_Repositories | other sites]] for more software.&lt;br /&gt;
&lt;br /&gt;
Start Odyssey Web Browser from '''SYS:Applications/OWB/OWB''' and download Grunch from its [http://geit.de/eng_grunch.html homepage] or from the [http://morphos-files.net/find.php?find=grunch MorphOS Files] site. Save the '''Grunch.lha''' archive file to any location, for example to Work partition or to Ram Disk. The archive isn't needed after the installation.&lt;br /&gt;
: [[File:GettingStarted_OWB4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Close the browser and use Ambient to browse to the location where you saved the Grunch.lha file. If you don't see the file, click the rightmost cycle gadget on the window to show all files. Double click the archive, open the Grunch directory, and double click the '''Grunch.install''' file to start the installer script. Running an installer directly from the unpacked archive is a bit of a shortcut which might not work with all programs, but let's demonstrate it anyway. The traditional and more failproof way would be to unpack an archive file to a temporary location and then run the installer script from an unarchived directory. Read more about installing third party software [[Installing_software | here]].&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Next''' button and select the destination location. The '''System:Applications''' path is OK unless you want to keep the bundled software and 3rd party software strictly separated. In that case you could make a new Applications directory on the Work partition, for example.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After the installation has finished, browse to the location where you installed the program and double click the '''Grunch''' icon. Grunch starts, but you'll have to wait a little while it does its initial checks and updates.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Start.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Before using the program any further, check the Grunch preferences. Select the '''Settings-&amp;gt;Grunch...''' option from the pulldown menus and open the '''Miscellaneous''' tab. I'd change the '''Temporary Directory''' path to somewhere else than to your system partition. If you have enough memory, you could have it even on the Ram Disk, but a temporary directory on the Work partition would be a safe bet.&lt;br /&gt;
&lt;br /&gt;
Click the file requester button at the end of the line to browse to the wanted location. The ''':''' button shows the available volumes, and you can also create new directories from the right click contextual menu on the file requester.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You should check the '''Path''' tab next, and think twice if you want to change them from the default paths. The default paths are OK if you think that all 3rd party and bundled software can reside mixed in the same directories and if you have enough free space on the system partition. But if you like to keep 3rd party and bundled software separated and have the system directories as clean as possible, change the paths now. You could make suitable directories on the Work partition, for instance.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
When you're happy with the settings, click the Save button.&lt;br /&gt;
&lt;br /&gt;
The Grunch icon can also be dragged to a panel for quick access later.&lt;br /&gt;
: [[File:GettingStarted_Dragging_Grunch_to_Panel.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software with Grunch ===&lt;br /&gt;
==== rexxsyslib.library ====&lt;br /&gt;
The rexxsyslib.library file enables the ARexx scripting language support on your system and it should be installed as early as possible. Many programs and their features rely on a working ARexx environment. Select it from the list and click the '''Install''' button on Grunch. You may need a reboot before it'll be in use.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software1.png]]&lt;br /&gt;
&lt;br /&gt;
==== Updating OWB ====&lt;br /&gt;
MorphOS usually comes with a bit old version of the OWB browser and you should check for a newer version. Select OWB from the list and click the '''Check''' button.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software2.png]]&lt;br /&gt;
&lt;br /&gt;
You probably have an old version, so click the '''Update...''' button and wait for it to finish.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software3.png]]&lt;br /&gt;
&lt;br /&gt;
You could also change the mode to Update.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software4.png]]&lt;br /&gt;
&lt;br /&gt;
==== MPlayer ====&lt;br /&gt;
MPlayer is hands down the best video player on MorphOS, just install it. It also works as an audio player with comprehensive support for different formats.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software5.png]]&lt;br /&gt;
&lt;br /&gt;
==== PowerSDL ====&lt;br /&gt;
PowerSDL libraries are required for many software ports from other platforms. It's better to install them as well.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software6.png]]&lt;br /&gt;
&lt;br /&gt;
==== CRABUM ====&lt;br /&gt;
CRABUM lets you to customize the pulldown menus on Ambient. It's quite handy for adding some hidden but quickly available features and shortcuts. We'll need this for some later examples.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software7.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Installed Software ===&lt;br /&gt;
==== Configuring Odyssey Web Browser ====&lt;br /&gt;
Here are few examples or suggestions for the initial configuration of OWB. Do the steps you like.&lt;br /&gt;
===== Downloading More Suitable Fonts for OWB =====&lt;br /&gt;
The fonts provided with MorphOS aren't designed with web usage in mind and it's better to download certain Microsoft fonts for the browser. Luckily it's an easy job to do, because there's a downloader script included in the OWB's directory.&lt;br /&gt;
&lt;br /&gt;
Open the '''SYS:Applications/OWB''' directory and double click the '''Download Fonts''' icon. Note: if the script doesn't seem to work, try [http://www.morphos-storage.net/?page=Network/Web&amp;amp;file=Download_Fonts_for_OWB.lha this one] instead.&lt;br /&gt;
: [[File:GettingStarted_OWB1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Yes''' on the requester and wait patiently for  the downloading and installing of the fonts. The output window closes when the process is finished.&lt;br /&gt;
: [[File:GettingStarted_OWB2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
OWB initializes the fonts on the first run, but it will start much quicker next time.&lt;br /&gt;
: [[File:GettingStarted_OWB3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Making OWB to Use Its Own Screen =====&lt;br /&gt;
A browser is usually an application people want to use in a full size window and on Amigaish systems it makes sense to put it on its own screen. When used on a separate screen it leaves more space for other programs on the Ambient screen, and you don't have such a hassle when handling them all. Bringing screens to front is also a very quick operation, you'll never see any slowdowns like on other systems where you reopen full size windows from taskbars, for example.&lt;br /&gt;
&lt;br /&gt;
You could send a program to a new screen with the &amp;quot;Jump to Screen -&amp;gt; New&amp;quot; option from the window popup gadget, but it's mainly designed for temporary usage. Let's do the configuration more proper way instead.&lt;br /&gt;
&lt;br /&gt;
Launch OWB, click on the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]], and select '''MUI Settings...'''. Another way to access the MUI settings would be from the '''Settings-&amp;gt;MUI...''' pulldown menu option when OWB's window is active.&lt;br /&gt;
: [[File:GettingStarted_OWB5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the '''Screen''' page, select the '''customized public screen from MUI screen database''' option, and click the '''New...''' button.&lt;br /&gt;
&lt;br /&gt;
The Edit Screen window opens. The name field is for the screen name and the title field for the screen title text. They can be anything you want, but it's better to keep them informative. '''OWB''' would be a good screen name now and '''Odyssey Web Browser''' for the title. Check if the default screen mode is what you want. Be also sure that the '''Close automatically''' option is enabled.&lt;br /&gt;
&lt;br /&gt;
It might be a good idea to disable the '''Enhanced Display''' option, because it doesn't give that much advantage with full screen applications. Graphics memory usage will also be lower, and it might be crucial to save some graphics memory on systems with less than 128 MB memory on the graphics card. Read more about how to reduce graphics memory usage [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
Click the '''Ok''' button on the Edit Screen window and the '''Save''' button on the MUI Settings window.&lt;br /&gt;
&lt;br /&gt;
Note: this method can be used with all MUI programs to put them on their own screens, from shell windows to small utilities, bigger applications, and games. I prefer to use the [[Applications/Showgirls|ShowGirls]] image viewer and other bigger applications on their own screens. Several MUI programs can also share the same custom screen, as it isn't limited just to a program per screen. You could for example group some network programs to one screen, and some other programs to another screen, etc.&lt;br /&gt;
: [[File:GettingStarted_OWB6.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The OWB window doesn't probably have optimal size and position on the newly created screen. Right click over the [[Fundamentals_of_MorphOS#Window_border_gadgets | zoom gadget]] and select the '''Maximize''' option or if you configured the zoom gadget as suggested [[Getting_Started#Screens_and_Desktop | earlier]], click the zoom gadget twice. The maximize option leaves the screen title bar visible, but otherwise resizes the window to full screen size. Select the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]] to save the window position permanently.&lt;br /&gt;
: [[File:Tips_Zoommenu.png|top]] [[File:GettingStarted_OWB7.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Open PDF Files Automatically =====&lt;br /&gt;
OWB's MIME Types settings can be used to configure automatic actions to files of certain types. Here is an example of how to show PDF files automatically with the [[Applications/VPDF|VPDF]] application when clicked on the browser.&lt;br /&gt;
&lt;br /&gt;
Open OWB's settings from the '''Settings-&amp;gt;Preferences...''' pulldown menu option and select the '''MIME Types''' page. Click the '''Add''' button and fill in the information below like this:&lt;br /&gt;
 MIME Type: '''application''' / '''pdf'''&lt;br /&gt;
 Extension: '''pdf'''&lt;br /&gt;
 Action: '''External Viewer''', Viewer: '''SYS:Applications/VPDF/VPDF''', and the last unnamed field: '''&amp;amp;#37;f'''&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button.&lt;br /&gt;
&lt;br /&gt;
If you now click a PDF file on a web page, the file is downloaded to a temporary location and shown on VPDF automatically.&lt;br /&gt;
: [[File:GettingStarted_OWB8.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Getting YouTube Videos to Play Better on the Browser Window =====&lt;br /&gt;
YouTube videos should play on OWB by default, but there are a thing or two to note.&lt;br /&gt;
&lt;br /&gt;
Playing videos in a small embedded window is a very CPU intensive task and not quite smooth on most systems. Moving the video playback from the embedded mode to the overlay mode helps the task hugely. This can be achieved with the YouTube Fullscreen Fix script. Videos will be shown in a nearly fullscreen window using the overlay functions and the CPU load may drop from 100&amp;amp;#37; even to 30&amp;amp;#37; on a G4 system, resulting in perfectly smooth playback of course.&lt;br /&gt;
&lt;br /&gt;
'''Download''' the latest script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js (YouTube changes its internals randomly and that's why the script on the MorphOS ISO is probably old already. Grunch also may have an old version and manual installation is highly advisable).&lt;br /&gt;
&lt;br /&gt;
Copy the downloaded script to the '''System:Applications/OWB/Scripts''' directory.&lt;br /&gt;
: [[File:GettingStarted_OWB9.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Scripts window from the '''Windows-&amp;gt;Scripts...''' pulldown menu entry on OWB.&lt;br /&gt;
: [[File:GettingStarted_OWB10.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Add''' button on the Scripts window and select the YouTube_Fullscreen_Fix.js file.&lt;br /&gt;
: [[File:GettingStarted_OWB11.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Make sure that the '''Enable''' setting is chosen and close the window. A '''restart''' of the browser is needed to activate the script, but after that you should be able to get any YouTube video to the smooth fullscreen mode by clicking the &amp;quot;fullscreen&amp;quot; or &amp;quot;large player&amp;quot; buttons on the video '''after the video playback has started'''. If you're watching a video embedded on some other external site, click the settings button instead. '''Double click''' the fullscreen video to get it to the embedded mode again.&lt;br /&gt;
: [[File:GettingStarted_OWB12.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Content Blocking and YouTube =====&lt;br /&gt;
If you have enabled the Content Blocking (AdBlock) option on the OWB settings, YouTube videos with ads will also get blocked. You can make a rule to the content blocking settings to allow those videos to be shown.&lt;br /&gt;
&lt;br /&gt;
Open '''Windows-&amp;gt;Content Blocking...''' from OWB's pulldown menus, click the '''Add''' button, and write '''youtube.com''' to the Rule line, and close the window.&lt;br /&gt;
: [[File:OWB_ContentBlockingYT.png]]&lt;br /&gt;
&lt;br /&gt;
If you have any other problems with the YouTube playback, check the [[Tips_and_Tricks#Problems_with_YouTube_Videos|Tips and Tricks]] page for more information.&lt;br /&gt;
&lt;br /&gt;
===== Configuring Fonts =====&lt;br /&gt;
&lt;br /&gt;
Browsers come with font settings. However, these settings are often neglected. Web developer has at least three options for selecting a font which would be displayed by default on your browser screen. &lt;br /&gt;
It can be a generic font, &amp;quot;hand picked&amp;quot; local font-family, or on-the-fly downloaded web font. Nevertheless the user still has the choice which font he or she actually wants to use. Reasons: privacy, security, speed, aesthetic.&lt;br /&gt;
&lt;br /&gt;
MorphOS is bundled with True Type, PostScript and Amiga Bitmap fonts.&lt;br /&gt;
OWB uses fontconfig for font handling. Fonts are cached whenever a change in font directories is detected.&lt;br /&gt;
If you want to use your fonts exclusively - fonts.conf should only use the path where you store the fonts (for example '''SYS:Fonts/_ttf''').&lt;br /&gt;
&lt;br /&gt;
Fontconfig is a library providing font configuration, customization and application access. It uses freetype library which supports plenty of font formats (excluding Amiga Bitmap fonts).&lt;br /&gt;
Presets are stored in the '''MOSSYS:Fontconfig/conf.avail''' directory.&lt;br /&gt;
&lt;br /&gt;
'''FONTS:Fontconfig/fonts.conf''' (configured font dirs)&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;!-- Font directory list --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;SYS:Fonts/_pcf&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;SYS:Fonts/_pfb&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pcf&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pfb&amp;lt;/dir&amp;gt; --&amp;gt;&lt;br /&gt;
&amp;lt;!--	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_ttf&amp;lt;/dir&amp;gt; --&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Example settings:'''&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/conf.d/51-local.conf'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
	&amp;lt;!-- Load local system customization file --&amp;gt;&lt;br /&gt;
	&amp;lt;include ignore_missing=&amp;quot;yes&amp;quot;&amp;gt;local.conf&amp;lt;/include&amp;gt;&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/local.conf''' (turns off antialias for font sizes smaller than 16 and disables autohint)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;!-- /etc/fonts/local.conf file for local customizations --&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;size&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;pixelsize&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;autohint&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Blocking fonts'''&lt;br /&gt;
&lt;br /&gt;
In OWB, go to '''Settings-&amp;gt;Fonts''' and choose default fonts and sizes.&lt;br /&gt;
&lt;br /&gt;
To disable remote web fonts this line needs to be added to its filter '''SYS:Applications/OWB/Conf/blocked.prefs''':&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
/\.ttf|\.otf|\.woff|\.woff2\?/&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
A specific font can be whitelisted too:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
@@/*actually-nice-font.ttf&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
This isn't ideal. OWB will try block anything_not_whitelisted.ttf, even if you look for a nicefont.ttf in Google Search.&lt;br /&gt;
&lt;br /&gt;
==== Configuring MPlayer ====&lt;br /&gt;
===== General Options =====&lt;br /&gt;
The default configuration of MPlayer is quite fine, but here are a few options I like to set myself. Start MPlayer in the GUI mode by double clicking the GMPlayer icon in the MPlayer directory. There's just one MPlayer executable, but two icons with different [[Fundamentals_of_MorphOS#Icon_Tool_Types|tooltypes]] to start the program with or without the GUI mode.&lt;br /&gt;
&lt;br /&gt;
With default options MPlayer scales the played video to fit the current window dimensions which typically leaves big empty borders around the video. To get the window dimensions to change with the video dimensions, select the '''Video-&amp;gt;Window Dimension-&amp;gt;100&amp;amp;#37;''' option, and '''Settings-&amp;gt;Save''' to save it as a default setting.&lt;br /&gt;
: [[File:GettingStarted_MPlayer.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Preferences window by selecting the '''Settings-&amp;gt;Preferences...''' option from MPlayer's pulldown menus. There are some settings to consider.&lt;br /&gt;
&lt;br /&gt;
The Audio Driver has two audio output options for AHI to choose from. The default '''ahi''' option outputs the audio through the ''Music Unit'', which gives the best audio quality, but blocks simultaneous audio from any other sources. The '''ahi_dev''' option uses the device mode which can be shared with the other sources, but it results in a slight decrease in the audio quality. So, if you want to be able to watch videos while some other program, like a music player, would still continue with audio output, select the '''ahi_dev''' option.&lt;br /&gt;
&lt;br /&gt;
If you don't like any usage data gathering, disable the '''Remember last visited path''' option :)&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Preferences.png]]&lt;br /&gt;
&lt;br /&gt;
===== Setting MPlayer as the Default Player on Ambient  =====&lt;br /&gt;
MorphOS doesn't have any default player for videos and double clicking a video file from Ambient results in an error requester. MPlayer can be set as the default video player by editing the Ambient MIME type settings.&lt;br /&gt;
&lt;br /&gt;
Open the '''Ambient Settings''' window and the '''Mime''' page. With the built-in MIME editor you can add different kinds of actions for different file formats or classes. Let's add MPlayer as the default player for all video files, not just for some individual video formats.&lt;br /&gt;
&lt;br /&gt;
Select '''video''' from the right-hand side list tree and click the '''Edit''' button. Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
&lt;br /&gt;
In the Action Editor window type a name for the action, for example '''Play''', and click the '''Add''' button on that window too.&lt;br /&gt;
&lt;br /&gt;
Change the AmigaDOS command to '''Run &amp;gt;NIL: SYS:Applications/MPlayer/MPlayer -gui 1 &amp;amp;#37;sp''' (change the path to the MPlayer executable if you have it in a different location) and change the Event type to '''DoubleClick'''. Note: the ''-gui 1'' option, which starts MPlayer in the GUI mode, has to be written in lower case, having it in upper case doesn't work!&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Adding_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Ok''', '''Ok''', and '''Save''' buttons.&lt;br /&gt;
&lt;br /&gt;
If you now double click a video file in Ambient, it gets played on MPlayer. You can also see the Play option in the contextual menu when right clicking the video file.&lt;br /&gt;
: [[File:GettingStarted_MPlayer2.png|320px]] [[File:GettingStarted_MPlayer_Working_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You can add several actions as contextual menu events if you want to have more options for opening videos. Only imagination is the limit, and you can for example have contextual menu entries to start MPlayer playback with filters skipped (use the ''-lavdopts skiploopfilter=all'' option to speed up the video playback a little) and have an option to convert the video with mencoder etc.&lt;br /&gt;
: [[File:GettingStarted_ActionEditor2.png|230px]]&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with FlowStudio ====&lt;br /&gt;
&lt;br /&gt;
Custom menus in Ambient can be added with a lua script. Menus can be edited and reloaded by the respective menu items.&lt;br /&gt;
&lt;br /&gt;
'''SYS:WBStartup/menus.lua''' script:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
require('ipc')&lt;br /&gt;
address('AMBIENT')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m1-0&amp;quot;                               title=&amp;quot;Tools&amp;quot;             type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-1&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;MUICON&amp;quot;          type=item shortcut=&amp;quot;S&amp;quot; command=&amp;quot;*&amp;quot;SYS:Tools/MUI Shell*&amp;quot;&amp;quot;                                              commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-2&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;Snoopium&amp;quot;        type=item command=&amp;quot;SYS:Tools/Snoopium&amp;quot;                                                                     commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-3&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-4&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;Mounter&amp;quot;         type=item command=&amp;quot;SYS:Tools/Mounter&amp;quot;                                                                        commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-5&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;HDConfig&amp;quot;        type=item command=&amp;quot;SYS:Tools/HDConfig&amp;quot;                                                                       commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6&amp;quot;    parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;&amp;quot;                   type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6-0&amp;quot; parentid=&amp;quot;m1-0&amp;quot;     title=&amp;quot;Menu&amp;quot;            type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6-1&amp;quot; parentid=&amp;quot;m1-6-0&amp;quot;  title=&amp;quot;Edit&amp;quot;              type=item command=&amp;quot;SYS:Applications/FlowStudio/FlowStudio SYS:WBStartup/menus.lua&amp;quot;        commandtype=amigados')&lt;br /&gt;
rx('menu add id=&amp;quot;m1-6-2&amp;quot; parentid=&amp;quot;m1-6-0&amp;quot;  title=&amp;quot;Reload&amp;quot;          type=item command=&amp;quot;RXCmd AMBIENT *&amp;quot;menu remove*&amp;quot; &amp;amp;&amp;amp; LuaX SYS:WBStartup/menus.lua&amp;quot;    commandtype=amigados')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m2-0&amp;quot;                               title=&amp;quot;Apps&amp;quot;             type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-1&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;FlowStudio&amp;quot;      type=item shortcut=&amp;quot;W&amp;quot; command=&amp;quot;Run &amp;gt;NIL: SYS:Applications/FlowStudio/FlowStudio&amp;quot;          commandtype=amigados')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-2&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;&amp;quot;                    type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-3&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;OWB&amp;quot;              type=item shortcut=&amp;quot;B&amp;quot; command=&amp;quot;SYS:Applications/OWB/OWB&amp;quot;                                          commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m2-4&amp;quot;    parentid=&amp;quot;m2-0&amp;quot;     title=&amp;quot;Transfer&amp;quot;         type=item command=&amp;quot;SYS:Applications/Transfer/Transfer&amp;quot;                                                   commandtype=workbench')&lt;br /&gt;
&lt;br /&gt;
rx('menu add id=&amp;quot;m3-0&amp;quot;                               title=&amp;quot;Utils&amp;quot;               type=menu')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-1&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;MUIProCalc&amp;quot;      type=item command=&amp;quot;SYS:Utilities/MUIProCalc&amp;quot;                                                                commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-2&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-3&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;Zoom&amp;quot;              type=item shortcut=&amp;quot;Z&amp;quot; command=&amp;quot;SYS:Utilities/Zoom&amp;quot;                                                      commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-4&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-5&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;AudioRecorder&amp;quot;  type=item command=&amp;quot;SYS:Utilities/AudioRecorder&amp;quot;                                                             commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-6&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;JukeBox&amp;quot;           type=item shortcut=&amp;quot;J&amp;quot; command=&amp;quot;SYS:Utilities/JukeBox&amp;quot;                                                   commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-7&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;&amp;quot;                     type=separator')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-8&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;TaskManager&amp;quot;    type=item shortcut=&amp;quot;T&amp;quot; command=&amp;quot;SYS:Utilities/TaskManager&amp;quot;                                            commandtype=workbench')&lt;br /&gt;
rx('menu add id=&amp;quot;m3-9&amp;quot;    parentid=&amp;quot;m3-0&amp;quot;     title=&amp;quot;GraphicsBoards&amp;quot;  type=item command=&amp;quot;SYS:Utilities/GraphicBoards&amp;quot;                                                           commandtype=workbench')&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Create .info icon for menus.lua''':&lt;br /&gt;
&lt;br /&gt;
'''Copy ENV:SYS/def_tool.info SYS:WBStartup/menus.lua.info'''&lt;br /&gt;
&lt;br /&gt;
'''Set icon info''':&lt;br /&gt;
&lt;br /&gt;
Select menus.lua and open its Information window (COMMAND I). Set Type as a '''Project''', write '''LuaX''' as a Default Tool and press '''Save'''.&lt;br /&gt;
&lt;br /&gt;
Now you can run menus.lua script and enjoy Ambient menus.&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with CRABUM ====&lt;br /&gt;
&lt;br /&gt;
You can add custom pulldown menus to Ambient with ARexx scripts created by the CRABUM program. It's a good way to launch programs or scripts which you don't want to have on panels. Installation of [[Getting_Started#rexxsyslib.library|rexxsyslib.library]] is required.&lt;br /&gt;
&lt;br /&gt;
Let's create an Edit menu with options to edit different system startup scripts. Double click the CRABUM icon from the SYS:Utilities/CRABUM directory if you installed it with the default options.&lt;br /&gt;
&lt;br /&gt;
# Click the '''Menu''' button to add a new menu and change its title to '''Edit'''.&lt;br /&gt;
# Click the '''Item''' button to add a new item under the created menu.&lt;br /&gt;
# Type '''User-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-startup''' to the AmigaDOS command line. &amp;quot;Run &amp;gt;NIL:&amp;quot; starts the Ed program as a background process and it won't block Ambient while it is running.&lt;br /&gt;
# Create an another item by clicking the '''Item''' button.&lt;br /&gt;
# Type '''User-network-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-network-startup''' to the AmigaDOS command line.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM1.png|320px]]&lt;br /&gt;
# Click the '''Save''' button to save the resulting ARexx script.&lt;br /&gt;
# If you save the file to the SYS:WBStartup drawer, it will be launched automatically at boot time. Enter a suitable name for the file, for example '''Edit-menu'''. Click the '''Ok''' button.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After a reboot (or doubleclicking of the file) you'll have the new Edit menu on the Ambient pulldown menus and you can easily open the system files for editing.&lt;br /&gt;
: [[File:GettingStarted_CRABUM3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
== More Configuring ==&lt;br /&gt;
=== Synchronizing the Clock with an Internet Time Server ===&lt;br /&gt;
The system clock can be synchronized manually from the MorphOS Preferences application by clicking the '''Set date and time using the Internet''' button in the Time preferences.&lt;br /&gt;
: [[File:MorphOS_Preferences_Time.png|320px]]&lt;br /&gt;
&lt;br /&gt;
There's also the [[Shell_Commands/SetClockNTP|SetClockNTP]] shell command which can be launched manually or automatically at boot time. To synchronize the time every time the system starts edit the '''S:user-network-startup''' file and remove the semi-colon from the SetClockNTP line.&lt;br /&gt;
&lt;br /&gt;
To edit the S:user-network-startup file open the shell (or the Execute Command prompt) and type '''Ed S:user-network-startup''', or open the System partition, select the '''All Files''' mode, browse to the '''S''' directory and select the '''Edit...''' option from the right click contextual menu. Or if you configured the Edit menu with CRABUM earlier, use it now.&lt;br /&gt;
: [[File:GettingStarted_Enable_SetClockNTP.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Shell ===&lt;br /&gt;
==== Editing the Shell-startup file ====&lt;br /&gt;
The shell can be customized with the shell-startup file, but by default the file is only found in a MorphOS system directory where the user shouldn't do any modifications. It must be copied to a user directory first to make any changes to it. Open a new shell window and type '''Copy MOSSYS:S/shell-startup SYS:S/shell-startup''', and then edit it for example with the '''Ed SYS:S/shell-startup''' command. The shell-startup file is executed every time a new shell window is opened.&lt;br /&gt;
: [[File:GettingStarted_shell-startup.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Adding Paths ====&lt;br /&gt;
There are some useful shell commands around the installed system which aren't in the system's search path and thus you'll have to enter their complete paths when using them. Adding their locations to the search path allows them to be run just by their names, which is much more convenient.&lt;br /&gt;
&lt;br /&gt;
Here are few suggestions to add to the '''SYS:S/shell-startup''' file (remember the previous step first!). Or if you want them to be available globally on all occasions, they can be added to the '''S:user-startup''' file instead.&lt;br /&gt;
* '''Path SYS:Applications/RemoteShell/Files ADD''' adds SSH related commands like scp, sftp, ssh, etc to the search path. Note: use the [[Applications/RemoteShell|Remote Shell]] application for regular SSH sessions, because it supports arrow keys and other things better.&lt;br /&gt;
* '''Path SYS:Applications/OWB/Datas ADD''' adds wget to the search path.&lt;br /&gt;
* '''Path SYS:Applications/MPlayer ADD''' adds MPlayer and mencoder to the search path if you have installed MPlayer. Change the path if you have installed it elsewhere.&lt;br /&gt;
&lt;br /&gt;
==== Configuring the GUI ====&lt;br /&gt;
There are many buttons and hotkeys to add to the shell window besides the default ones. Check the preferences by selecting the '''Settings-&amp;gt;Edit Prefs...''' option from the Shell's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Available functions can be dragged to '''Hotkeys''' or '''Buttons''' lists and the changes are seen in real time in the shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You may also want to set the default window size and position for new shell windows on the '''Settings''' tab. Click the '''Get from window''' button to get values from the current shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Remember to save the modifications in the '''Settings''' menu.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Setting Jukebox as the Default Player for MP3 Files ===&lt;br /&gt;
If you double click an MP3 file in an Ambient window, it is played with the very simple internal player. Here are two solutions to change the default player to the more advanced [[Utilities/Jukebox|Jukebox]] music player. Ambient's internal player is still left to the context menu as an option.&lt;br /&gt;
==== Simple Solution ====&lt;br /&gt;
A simple solution is just to create a new mpeg audio MIME type definition which just launches the Jukebox player with the double clicked filename as an argument.&lt;br /&gt;
# Open the Mime page in the Ambient settings, select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''Run &amp;gt;NIL: SYS:Utilities/Jukebox &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and you should see this in the MIME Editor window.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Save''' buttons. If you double click an MP3 file now, Jukebox starts and plays the clicked file. There are also two entires in the right click contextual menu and the option which is used for the double click action is written in bold.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Advanced Solution ====&lt;br /&gt;
An advanced solution is to use the third party [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script. It will give more flexible options to add files to Jukebox, and we'll learn how to add submenus into context menus. There are shortcuts to install the script if you read the documentation in the archive, but let's do this manually to learn the configuration method better. It will be helpful in the future when configuring any other filetypes.&lt;br /&gt;
&lt;br /&gt;
# Download the script archive from [http://aminet.net/package/mus/play/JukeboxAdder Aminet] or from [http://morphos-files.net/find.php?find=jukeboxadder MorphOS Files].&lt;br /&gt;
# Copy the '''jukeboxadder.lua''' file from the archive to the '''SYS:S/''' directory.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder1.png|320px]]&lt;br /&gt;
# Open the '''Mime''' page in the '''Ambient settings''', select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua PLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and then click '''Add''' again in the MIME Editor window to create more ways to add files to Jukebox from the context menus.&lt;br /&gt;
# Type '''Add to Jukebox''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua ADD &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string. This will create a submenu named ''Jukebox'' in the context menu and place the new ''Add to Jukebox'' option there.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Add''' once again to create the last entry.&lt;br /&gt;
# Type '''Add to Jukebox and Play''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''MOSSYS:C/LuaX S:jukeboxadder.lua ADDPLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder4.png|320px]]&lt;br /&gt;
# Click '''Ok''', '''Ok''', and '''Save'''. Now you can see more options in the context menu for MP3 files and double clicking will always clear the previous songs and play the new song immediately.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
It is also possible to add the same functionality for context menus of directories if you want to be able to add whole directories to Jukebox at once. There's a special '''internal -&amp;gt; x-morphos-globalaction-directory''' MIME type which can be used to add context menu entries for all directories. Repeat the previous steps (6-18) for it, but make all '''Event types''' to use the '''Menu''' option (in step 9 too).&lt;br /&gt;
: [[File:GettingStarted_JukeboxAdder6.png|320px]] [[File:GettingStarted_JukeboxAdder7.png|320px]] [[File:GettingStarted_JukeboxAdder8.png|320px]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3867</id>
		<title>Getting Started</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3867"/>
				<updated>2018-04-30T20:27:18Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== A Beginner's Guide to MorphOS ==&lt;br /&gt;
&lt;br /&gt;
You have installed MorphOS to a compatible machine, but... now what? You could always go and install a pre-configured package like Chrysalis, but you would end up with a system configured for someone else's taste and you still wouldn't know how to actually use the operating system. If you are in this situation and would like to learn how MorphOS works, this is a tutorial for you! The tutorial will guide you through the things you should do and notice after a fresh install, with practical examples from basic configuration options to installing new software. It won't cover all the details and is just an opinion on how to proceed, but it should give you some knowledge how to continue on your own and make your own decisions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting Comfortable with the User Interface and the Ambient Desktop ==&lt;br /&gt;
=== The First Boot ===&lt;br /&gt;
&lt;br /&gt;
After a boot you're presented with the plain looking Ambient, the desktop environment of MorphOS. The first thing you should learn is to get familiar with the basic usage, and to tune the interface settings so that they won't annoy you. The worst thing is if a user plays around a bit and just curses at the system when it doesn't work as expected or wanted. You aren't forced into just one kind of behaviour with MorphOS!&lt;br /&gt;
: [[File:GettingStarted_Ambient.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Right mouse click is widely used on MorphOS and if you're using a device without a physical button for it, check the tips over [[Tips_and_Tricks#How_to_Use_RMB_with_One-button_Mouse | here]]. Pressing the right mouse button over the Ambient screen opens Ambient's pulldown menus where you can find few important options. For example, options to shut down the system, to open a new shell window, or to open system settings.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Shutdown.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== System Settings ===&lt;br /&gt;
&lt;br /&gt;
The MorphOS Preferences application is used to edit system-wide settings. It can be launched from the Ambient's pulldown menu by selecting the &amp;quot;Settings-&amp;gt;System...&amp;quot; menu option or by browsing to the System:Prefs/ drawer and double clicking the Preferences icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_System_Settings.png]] [[File:GettingStarted_MorphOS_Preferences.png|237px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Screens ====&lt;br /&gt;
&lt;br /&gt;
If MorphOS didn't get the optimal resolution of your monitor with DDC, a different screen mode can be selected from the Screens settings. If the wanted mode isn't seen there, open the Monitors settings instead to create a completely new mode.&lt;br /&gt;
&lt;br /&gt;
If you have a graphics card with a low amount of memory, you can try to make the memory consumption smaller by disabling the Enhanced Display setting (3D accelerated graphics functions for 2D screens) or by reducing the color depth. More information can be found  [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
MorphOS skins (themes for the graphical appearance) can also be changed from the Screens settings.&lt;br /&gt;
&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== IControl ====&lt;br /&gt;
&lt;br /&gt;
IControl settings are the most important settings for the overall user experience. This is the place to look in order to avoid the usual comments like ''&amp;quot;Why doesn't X work like Y in the other OS?&amp;quot;'', ''&amp;quot;Why there isn't a feature Z?&amp;quot;'', ''&amp;quot;I can't use a system like this!&amp;quot;''. Everyone should check these settings first before going any further.&lt;br /&gt;
&lt;br /&gt;
===== Hotkeys =====&lt;br /&gt;
MorphOS has many nice features to use with keyboard shortcuts or mouse buttons, but only few are activated by default. Let's activate more!&lt;br /&gt;
&lt;br /&gt;
To add a new hotkey for the wanted function click the popup button on the right side, select &amp;quot;'''Sample'''&amp;quot;, and press the wanted key combination. The pressed combination is then recorded on the corresponding line and should be shown there. Repeat the procedure if you didn't get it as wanted on the first try. Changed settings will be taken into use after you click the Save or Use button.&lt;br /&gt;
&lt;br /&gt;
Here is how to set the &amp;quot;control left-alt c&amp;quot; key combination to '''center the active window''' on the screen:&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Hotkeys2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Here are some other recommendations to activate, but feel free to use your own preferences for the hotkeys:&lt;br /&gt;
* '''Active Window: To Back''' - double click with middle mouse button to send a window back of other windows.&lt;br /&gt;
* '''Active Window: Zoom''' - &amp;quot;control left-alt m&amp;quot;, to toggle between a maximized and minimized window.&lt;br /&gt;
* '''Active Window: Activate Next''' - &amp;quot;left-command tab&amp;quot;, to have the ''alt-tab'' functionality found on many other operating systems. Using ctrl-tab or alt-tab isn't recommended because they would overlap with the shell's functionality on MorphOS. Command-tab also happens be the same in OS X.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys3.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Note: You can also add several hotkeys for a function by selecting the New Hotkey option from the popup button's menu.&lt;br /&gt;
&lt;br /&gt;
===== Screens and Desktop =====&lt;br /&gt;
&lt;br /&gt;
Important options concerning how windows and menus behave can be found on the Screens and Desktop settings.&lt;br /&gt;
&lt;br /&gt;
I'd recommend turning on the '''Maximize window when clicking on the Zoom gadget''' option. The Zoom gadget will then toggle the window size between full screen (with the screen title bar still visible) and the initial window size and position. I find it much more comfortable than the legacy placement between two obscure positions. The previously configured Zoom hotkey will also work better with this option enabled.&lt;br /&gt;
&lt;br /&gt;
If you prefer being able to drag windows out of the screen without pressing any qualifier key, like on mainstream systems, select the '''When dragging windows... allow them to be placed out of screen, unless Control is pressed''' option.&lt;br /&gt;
&lt;br /&gt;
The default behaviour of the pulldown menus may be a bit unfamiliar for old Amiga users, but there are several options to get them working as expected. I like to disable the '''Menus shall remain opened even when mouse button is released''' option and enable the '''Open menus under mouse pointer outside screen titlebar area''' option.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Touchpad ====&lt;br /&gt;
&lt;br /&gt;
If you're using a laptop system, check the Touchpad setttings. You might want to disable clicking from the pad to avoid any accidental clicks.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Touchpad.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Laptop ====&lt;br /&gt;
&lt;br /&gt;
If you're not a Mac user, you might find it odd that you need to press the fn key when using the function keys for normal activities, and not when modifying, for example, the screen brightness. The '''Press and hold the fn key to modify screen brightness, audio volume, etc.''' option will change the functionality the other way around.&lt;br /&gt;
&lt;br /&gt;
Some systems also have the '''Automatic LCD brightness and keyboard backlight control''' option here. Disable it if you're annoyed by changing lightning.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Laptop.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Windows ===&lt;br /&gt;
&lt;br /&gt;
The first icon you see on the Ambient desktop is the &amp;quot;'''My MorphOS'''&amp;quot; icon. By double clicking it you'll get a window with icons of all volumes and assigns of the system. It works like a root directory with quick access to different locations.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS.png|320px]]&lt;br /&gt;
&lt;br /&gt;
If you find it a bit clumsy to work in the icon mode, like I do, you can change the view to '''the list mode''' from the cycle button on the right side of the window.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
With default settings Ambient doesn't remember the changed mode or other window properties next time you open it, but you can right click the window border or an empty area on the file lister to bring up a contextual window menu and select the &amp;quot;'''Snapshot-&amp;gt;Window'''&amp;quot; option to save the window properties. Default position and size for a window can be saved that way too. If you defined the centering hotkey earlier, you can try it now :)&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The same can also be done for normal directory windows. While &amp;quot;My MorphOS&amp;quot; window settings are exceptionally saved to Ambient's configuration files, normal directories' settings are saved to an icon file (a file with .info extension). If you change and save the mode for the Work: partition for example, you see a disk.info file appearing there.&lt;br /&gt;
: [[File:GettingStarted_Icon_Mode.png|320px]] [[File:GettingStarted_List_Mode_Snapshot.png|320px]] [[File:GettingStarted_List_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Displayed columns can be selected by right clicking the column title area, but modify the [[Getting_Started#Lister|default lister settings]] to your liking before starting to save settings for individual windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Lister_Columns.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Settings ===&lt;br /&gt;
&lt;br /&gt;
Ambient is actually a separate application itself and it has its own settings separated from the general system preferences. The previously mentioned system settings affect all programs and screens, but strictly desktop related settings are found in the Ambient settings. The Ambient Settings window can be opened by selecting the &amp;quot;Settings-&amp;gt;Ambient...&amp;quot; option from Ambient's pulldown menu.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Ambient_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
==== Miscellaneous ====&lt;br /&gt;
&lt;br /&gt;
The Miscellaneous page on the Ambient settings has a nice option to get the My MorphOS window opened when double clicking anywhere on the empty area of the desktop. It really speeds up the working when you don't have to move the mouse a long way to the top corner or dig the icon out from under some other windows. Enable it with the '''Double click on desktop opens MyMorphOS window''' option.&lt;br /&gt;
&lt;br /&gt;
The My MorphOS icon is just wasting space on the desktop after the previous setting and you can hide it by disabling the '''Display MyMorphOS icon''' option.&lt;br /&gt;
&lt;br /&gt;
If you like to have a bit more eye candy on the context menus, you can also enable the '''Show images in context menu''' option while you're here.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Misc.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Lister ====&lt;br /&gt;
The default properties of the list mode of Ambient windows can be changed on the Lister settings. Disable the '''Compact size display''' if you want to see exact file sizes in bytes always. You may also want to select different columns to be shown in the listers by double clicking items on the '''File Properties''' list to set them hidden or shown. '''Date &amp;amp; Time''' instead of just Date would probably be a common choice.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Lister.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Panels ====&lt;br /&gt;
&lt;br /&gt;
Many new users are wondering if there is any kind of dock application on MorphOS, because there isn't any shown by default. MorphOS has ''panels'' for that and you can have as many panels as you want on the desktop, arranged horizontally or vertically. The panels have features like zipping to hide and unhide them, sub panels and other Panel Object plugins, etc. There just isn't any configured by default and user can create a panel or panels how he likes.&lt;br /&gt;
&lt;br /&gt;
To create a new panel, open the Panels page on the Ambient settings and click the '''New Panel''' button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels1.png|320px]]&lt;br /&gt;
An empty panel can be dragged anywhere and you can find some of its settings on the '''Name &amp;amp; Look''' and '''Behaviour''' tabs. If you want to place the panel on a screen border the '''Attached to Borders''' option makes it easier. The '''Alpha''' option controls the transparency of a panel, but it only works if the Enhanced Display option for the Ambient screen enabled and working. The same applies to the '''Hide Dragbar''' option as well.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels2.png|320px]]&lt;br /&gt;
Programs can be added to the panel by dragging and dropping their icons to the panel list to the wanted position on the list tree, or to the panel itself. Items in the panel list can be rearranged by drag and drop too.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels3.png|320px]]&lt;br /&gt;
Available Panel Objects are listed on the right-hand side and they can be dragged and dropped to any position on the panel tree. All items on the panel may have their own settings, which are shown when an item is clicked once with the left mouse button. In this example picture a new sub panel has been created and its icon image is being changed to a custom one.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels4.png|320px]]&lt;br /&gt;
If you want to clone the color settings from the main panel to a sub panel, you can use the MUI clipboard to temporarily store a setting. Drag &amp;amp; drop the wanted color button to the clipboard button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels5.png|320px]]&lt;br /&gt;
Then activate the sub panel settings and drag &amp;amp; drop the clipboard button to the sub panel's color button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels6.png|320px]]&lt;br /&gt;
And here's a picture of the created panel with its sub panel in action. Remember to click the Save button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels7.png|320px]]&lt;br /&gt;
The panels also have a context menu that can be accessed with a right click. You'll have quick access to the panel settings and some other options there.&lt;br /&gt;
&lt;br /&gt;
If you lock a panel, items dragged to it aren't added to the panel anymore, but the dragged items are opened with the program you dropped them onto. Text files can be dropped onto the Scribble icon, MP3 files and directories can be dropped onto the Jukebox icon, video and audio files onto the MPlayer icon, and so on.&lt;br /&gt;
: [[File:GettingStarted_Panel_Locked1.png|320px]] [[File:GettingStarted_Panel_Locked2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Window ====&lt;br /&gt;
&lt;br /&gt;
Ambient windows are very configurable and users should at least check the buttons available for the toolbar. Just adding a few buttons can make a difference in usability. The buttons and other items can be dragged from the Available Buttons list to the Current Toolbar group, and vice versa to remove them from the toolbar. All changes are updated in real time to any open Ambient windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
In this example picture '''Makedir''' and '''Delete''' buttons are separated with the '''Space''' button, and they have been added into a row with other buttons. Also the '''Bookmarks''' button has been added as the last item on the toolbar. It always stays at the right border no matter how big a window is, because it's been added after the '''Flexible space''' button. &lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Keyboard ====&lt;br /&gt;
===== Built-in Command Hotkeys =====&lt;br /&gt;
Check the Ambient hotkeys from this section and change them to your liking. If you have a laptop without the numeric keypad, you should change hotkeys which are using numpad combinations by default. I, for example, am used to having the '''Cycle Mode''' option on the key above the tab key and the '''Cycle Submode''' option when the same key is pressed with the shift key. It feels somehow quicker to use them from there than from the numeric keypad with a standard keyboard too.&lt;br /&gt;
&lt;br /&gt;
===== Custom Command Hotkeys =====&lt;br /&gt;
Practically any functionality can be added to custom hotkey definitions. This might be a bit advanced topic, but let's show few definitions which will improve the usability.&lt;br /&gt;
&lt;br /&gt;
A new Ambient hotkey can be created by clicking the Add a Hotkey button. The first text field is for the name of the hotkey and it can be anything. The second text field is the actual keyboard combination to activate a function. The Edit Command button is used to define what actually happens when you press the hotkey in Ambient.&lt;br /&gt;
&lt;br /&gt;
Let's create two hotkeys which can be used to copy selected files' names as text to the clipboard, with and without the preceding path.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Copy name with path''' and the hotkey combination to '''ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si FULLPATH''', and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
* Click the '''Add a Hotkey''' button again, define the name as '''Copy name''' and the hotkey combination to '''rshift ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si''', and press the enter key. Click the '''Ok''' button, save the Ambient settings, and you're done.&lt;br /&gt;
&lt;br /&gt;
If you now select any files on an Ambient window and press the ''ralt c'' key combination, the selected file names with their full paths get copied to the clipboard and are available to be pasted to any other application. The ''rshift ralt c'' combination copies pathless file names to the clipboard.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Keyboard1.png|320px]] [[File:GettingStarted_Ambient_Settings_Keyboard2.png|320px]] [[File:GettingStarted_ActionEditor1.png|214px]]&lt;br /&gt;
&lt;br /&gt;
Another example which will extract any selected archive file to the ram disk with the ''lshift control e'' combination.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Extract to RAM''' and the hotkey combination to '''lshift control e'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Leave the action type to '''AmigaDOS''', type in the command '''XADUnFile &amp;amp;#37;sp RAM:''' , and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Screenbar Modules ===&lt;br /&gt;
&lt;br /&gt;
[[Screenbar_Modules | Screenbar modules]] are plugins which can populate the empty area on the screen title bar with some useful information and functionality. The modules are visible on every (MUI) [[Fundamentals_of_MorphOS#Screens | screen]], which makes them more useful than, for example, Panel Objects. Panel Objects are only seen on the Ambient screen and can be left under some other windows more easily.&lt;br /&gt;
&lt;br /&gt;
Screenbar modules can be enabled and disabled from the screen depth gadget menu. The menu also contains options to arrange order of the modules and to change their settings. The menu can be accessed by right clicking, or with a long left press, over the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget | screen depth gadget]].&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Menu.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Let's have a look at how to configure a few modules. Enable the '''CPU Monitor''', '''Drivelamps''', and '''Memory''' modules by, for example, multiselecting them at once. Reopen the screen depth gadget menu, select the '''Settings...''' option, and select CPU Monitor from the settings list. The CPU Monitor module is a bit narrow by default, so let's increase its width a little.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_CPU_Monitor.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Drivelamps module has more configuration options. Enable the '''Show lamp''' option for '''usbscsi.device''' if you want to see access indicators for both HD and USB drives. The default look doesn't seem to be that good for two lamps, but you can tune it a bit. Disabling the frame from the Look group (select None) and selecting the recessed frame for the Lamp Look group does some wonders already. You can also adjust the spacing options, if the lamps don't seem to match with the height of the CPU Monitor or other modules.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Drivelamps.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Memory module shows free memory in percents by default, but it can be changed to other types too. Click the popup button on the '''Information''' line to see the options. The information line can have any text, and for example a ''&amp;amp;#37;mfMB free'' line would show free memory in megabytes followed by the &amp;quot;MB free&amp;quot; text.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Memory.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== MUI Settings ===&lt;br /&gt;
&lt;br /&gt;
MUI is the default GUI toolkit of MorphOS and its looks and behaviour can be changed in almost every aspect. Its basic philosophy is to ''offer as much freedom as possible to users by taking away as much work as possible from programmers''. A user can modify the looks of MUI programs very drastically both globally and per program. It can be done by changing single settings or by loading complete themes (presets).&lt;br /&gt;
&lt;br /&gt;
The most important thing for a new user is to understand the difference between the global settings and settings of individual programs.&lt;br /&gt;
&lt;br /&gt;
The global settings are the default settings which will apply to any program using MUI. The global settings can be changed by selecting the '''Settings-&amp;gt;MUI...''' option from the Ambient's pulldown menus or by double clicking the '''SYS:Prefs/MUI''' icon.&lt;br /&gt;
&lt;br /&gt;
Each MUI program can also have its own MUI settings which will override the global settings, but be careful when changing for example the looks of an individual program. If you decide to change the global theme later, the changes made to the individual programs might not fit the global theme anymore. The MUI settings of a program can be found on its pulldown menu or from the window's [[Fundamentals_of_MorphOS#Window_border_gadgets | popup gadget]] menu. Ambient's MUI settings are found from the '''Settings-&amp;gt;Ambient MUI...''' option in the Ambient's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Let's change a couple of options in the global MUI settings as an example. Open the global MUI settings window.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_MUI_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
The default ghosting effect for buttons is a bit old-fashioned raster effect and it will look much better with just reduced visibility. Select the Buttons page and click the None option for the ghosted gadgets. The visibility can be changed with the slider below, but the default value will be fine too. You'll see the changes in real time on any MUI program, the Test button is a bit obsolete with the latest MUI. I also like to make the Active Gadgets Border a bit smaller than the original size. Click the Save button when you're satisfied.&lt;br /&gt;
: [[File:GettingStarted_MUI_Settings_Buttons.png|380px]]&lt;br /&gt;
&lt;br /&gt;
The Settings button in the top left corner opens a popup menu with options to reset the settings or load different presets.&lt;br /&gt;
&lt;br /&gt;
All MUI settings get saved to the ENVARC:MUI/ directory. If you mess too much with settings for individual programs, the last resort to revert the settings to default is to remove the corresponding settings files from that directory or restore them from a backup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hiding the Boot Image Partition on Macs ===&lt;br /&gt;
&lt;br /&gt;
On Macs you'll have a small HFS formatted partition which contains a few files needed to boot the system. The files are only used by [[Dictionary_of_Terms | Open Firmware]] at boot time and the user or MorphOS itself don't normally need them for anything. Open Firmware, as well as the MorphOS update wizard, can access the partition even if it's not mounted on MorphOS. If we disable the auto mounting of it, our desktop will look a bit cleaner and the crucial boot files will then be safe from accidents as well.&lt;br /&gt;
&lt;br /&gt;
Launch the [[Tools/HDConfig]] program and click on the small HFS partition. Its name should be '''DH0:''' if the system is installed with the default partition layout. Disable the '''Automatically mount partition''' option and click the '''OK''' button.&lt;br /&gt;
: [[File:GettingStarted_HDConfig1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button which is in the red area on the left side and accept the changes.&lt;br /&gt;
: [[File:GettingStarted_HDConfig2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Next time you boot the system, the partition isn't shown on the desktop. If you need to access it later for some reason, it can be mounted temporarily with the [[Tools/Mounter]] tool.&lt;br /&gt;
: [[File:GettingStarted_Ambient2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging the Drive Icons ===&lt;br /&gt;
The drive icons can be dragged to a different order and then saved to their positions by selecting the '''Snapshot''' option from the right click contextual menu. If the Ram Disk icon is dragged to the leftmost position and snapshot, it will appear at that position after a reboot and unsnapshot icons appear next to it.&lt;br /&gt;
: [[File:GettingStarted_Drive_Icons.png|320px]] [[File:GettingStarted_Drive_Icons_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installing, Updating, and Configuring Essential Software ==&lt;br /&gt;
&lt;br /&gt;
=== Checking the Network Connection ===&lt;br /&gt;
&lt;br /&gt;
Before continuing to installing new software, let's check if your machine is properly connected to the Internet.&lt;br /&gt;
&lt;br /&gt;
Open the shell by selecting the '''Ambient-&amp;gt;New Shell...''' option from the Ambient's pulldown menus, or by pressing '''rcommand n''' keyboard combination or doubleclicking the '''SYS:Tools/MUI Shell''' icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_New_Shell.png]]&lt;br /&gt;
&lt;br /&gt;
Check the Internet connection by pinging some hostname on the Internet. Type for example '''ping www.google.com''' on the shell window. If you get replies from the host, the connection is OK and you can proceed by pressing '''CTRL C''' to quit the Ping command and closing the shell window. If you don't get any replies with time values, quit the pinging by the CTRL C combination and read the [[Configuring_Network | Configuring a Network Connection]] tutorial.&lt;br /&gt;
: [[File:GettingStarted_Ping.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Grunch ===&lt;br /&gt;
&lt;br /&gt;
[http://geit.de/eng_grunch.html Grunch] is an advanced software package manager, which can install, update, and uninstall software. It's a good starting point for new users and I'd advice everyone to check what it has to offer before visiting [[Links#File_Repositories | other sites]] for more software.&lt;br /&gt;
&lt;br /&gt;
Start Odyssey Web Browser from '''SYS:Applications/OWB/OWB''' and download Grunch from its [http://geit.de/eng_grunch.html homepage] or from the [http://morphos-files.net/find.php?find=grunch MorphOS Files] site. Save the '''Grunch.lha''' archive file to any location, for example to Work partition or to Ram Disk. The archive isn't needed after the installation.&lt;br /&gt;
: [[File:GettingStarted_OWB4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Close the browser and use Ambient to browse to the location where you saved the Grunch.lha file. If you don't see the file, click the rightmost cycle gadget on the window to show all files. Double click the archive, open the Grunch directory, and double click the '''Grunch.install''' file to start the installer script. Running an installer directly from the unpacked archive is a bit of a shortcut which might not work with all programs, but let's demonstrate it anyway. The traditional and more failproof way would be to unpack an archive file to a temporary location and then run the installer script from an unarchived directory. Read more about installing third party software [[Installing_software | here]].&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Next''' button and select the destination location. The '''System:Applications''' path is OK unless you want to keep the bundled software and 3rd party software strictly separated. In that case you could make a new Applications directory on the Work partition, for example.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After the installation has finished, browse to the location where you installed the program and double click the '''Grunch''' icon. Grunch starts, but you'll have to wait a little while it does its initial checks and updates.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Start.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Before using the program any further, check the Grunch preferences. Select the '''Settings-&amp;gt;Grunch...''' option from the pulldown menus and open the '''Miscellaneous''' tab. I'd change the '''Temporary Directory''' path to somewhere else than to your system partition. If you have enough memory, you could have it even on the Ram Disk, but a temporary directory on the Work partition would be a safe bet.&lt;br /&gt;
&lt;br /&gt;
Click the file requester button at the end of the line to browse to the wanted location. The ''':''' button shows the available volumes, and you can also create new directories from the right click contextual menu on the file requester.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You should check the '''Path''' tab next, and think twice if you want to change them from the default paths. The default paths are OK if you think that all 3rd party and bundled software can reside mixed in the same directories and if you have enough free space on the system partition. But if you like to keep 3rd party and bundled software separated and have the system directories as clean as possible, change the paths now. You could make suitable directories on the Work partition, for instance.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
When you're happy with the settings, click the Save button.&lt;br /&gt;
&lt;br /&gt;
The Grunch icon can also be dragged to a panel for quick access later.&lt;br /&gt;
: [[File:GettingStarted_Dragging_Grunch_to_Panel.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software with Grunch ===&lt;br /&gt;
==== rexxsyslib.library ====&lt;br /&gt;
The rexxsyslib.library file enables the ARexx scripting language support on your system and it should be installed as early as possible. Many programs and their features rely on a working ARexx environment. Select it from the list and click the '''Install''' button on Grunch. You may need a reboot before it'll be in use.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software1.png]]&lt;br /&gt;
&lt;br /&gt;
==== Updating OWB ====&lt;br /&gt;
MorphOS usually comes with a bit old version of the OWB browser and you should check for a newer version. Select OWB from the list and click the '''Check''' button.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software2.png]]&lt;br /&gt;
&lt;br /&gt;
You probably have an old version, so click the '''Update...''' button and wait for it to finish.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software3.png]]&lt;br /&gt;
&lt;br /&gt;
You could also change the mode to Update.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software4.png]]&lt;br /&gt;
&lt;br /&gt;
==== MPlayer ====&lt;br /&gt;
MPlayer is hands down the best video player on MorphOS, just install it. It also works as an audio player with comprehensive support for different formats.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software5.png]]&lt;br /&gt;
&lt;br /&gt;
==== PowerSDL ====&lt;br /&gt;
PowerSDL libraries are required for many software ports from other platforms. It's better to install them as well.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software6.png]]&lt;br /&gt;
&lt;br /&gt;
==== CRABUM ====&lt;br /&gt;
CRABUM lets you to customize the pulldown menus on Ambient. It's quite handy for adding some hidden but quickly available features and shortcuts. We'll need this for some later examples.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software7.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Installed Software ===&lt;br /&gt;
==== Configuring Odyssey Web Browser ====&lt;br /&gt;
Here are few examples or suggestions for the initial configuration of OWB. Do the steps you like.&lt;br /&gt;
===== Downloading More Suitable Fonts for OWB =====&lt;br /&gt;
The fonts provided with MorphOS aren't designed with web usage in mind and it's better to download certain Microsoft fonts for the browser. Luckily it's an easy job to do, because there's a downloader script included in the OWB's directory.&lt;br /&gt;
&lt;br /&gt;
Open the '''SYS:Applications/OWB''' directory and double click the '''Download Fonts''' icon. Note: if the script doesn't seem to work, try [http://www.morphos-storage.net/?page=Network/Web&amp;amp;file=Download_Fonts_for_OWB.lha this one] instead.&lt;br /&gt;
: [[File:GettingStarted_OWB1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Yes''' on the requester and wait patiently for  the downloading and installing of the fonts. The output window closes when the process is finished.&lt;br /&gt;
: [[File:GettingStarted_OWB2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
OWB initializes the fonts on the first run, but it will start much quicker next time.&lt;br /&gt;
: [[File:GettingStarted_OWB3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Making OWB to Use Its Own Screen =====&lt;br /&gt;
A browser is usually an application people want to use in a full size window and on Amigaish systems it makes sense to put it on its own screen. When used on a separate screen it leaves more space for other programs on the Ambient screen, and you don't have such a hassle when handling them all. Bringing screens to front is also a very quick operation, you'll never see any slowdowns like on other systems where you reopen full size windows from taskbars, for example.&lt;br /&gt;
&lt;br /&gt;
You could send a program to a new screen with the &amp;quot;Jump to Screen -&amp;gt; New&amp;quot; option from the window popup gadget, but it's mainly designed for temporary usage. Let's do the configuration more proper way instead.&lt;br /&gt;
&lt;br /&gt;
Launch OWB, click on the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]], and select '''MUI Settings...'''. Another way to access the MUI settings would be from the '''Settings-&amp;gt;MUI...''' pulldown menu option when OWB's window is active.&lt;br /&gt;
: [[File:GettingStarted_OWB5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the '''Screen''' page, select the '''customized public screen from MUI screen database''' option, and click the '''New...''' button.&lt;br /&gt;
&lt;br /&gt;
The Edit Screen window opens. The name field is for the screen name and the title field for the screen title text. They can be anything you want, but it's better to keep them informative. '''OWB''' would be a good screen name now and '''Odyssey Web Browser''' for the title. Check if the default screen mode is what you want. Be also sure that the '''Close automatically''' option is enabled.&lt;br /&gt;
&lt;br /&gt;
It might be a good idea to disable the '''Enhanced Display''' option, because it doesn't give that much advantage with full screen applications. Graphics memory usage will also be lower, and it might be crucial to save some graphics memory on systems with less than 128 MB memory on the graphics card. Read more about how to reduce graphics memory usage [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
Click the '''Ok''' button on the Edit Screen window and the '''Save''' button on the MUI Settings window.&lt;br /&gt;
&lt;br /&gt;
Note: this method can be used with all MUI programs to put them on their own screens, from shell windows to small utilities, bigger applications, and games. I prefer to use the [[Applications/Showgirls|ShowGirls]] image viewer and other bigger applications on their own screens. Several MUI programs can also share the same custom screen, as it isn't limited just to a program per screen. You could for example group some network programs to one screen, and some other programs to another screen, etc.&lt;br /&gt;
: [[File:GettingStarted_OWB6.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The OWB window doesn't probably have optimal size and position on the newly created screen. Right click over the [[Fundamentals_of_MorphOS#Window_border_gadgets | zoom gadget]] and select the '''Maximize''' option or if you configured the zoom gadget as suggested [[Getting_Started#Screens_and_Desktop | earlier]], click the zoom gadget twice. The maximize option leaves the screen title bar visible, but otherwise resizes the window to full screen size. Select the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]] to save the window position permanently.&lt;br /&gt;
: [[File:Tips_Zoommenu.png|top]] [[File:GettingStarted_OWB7.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Open PDF Files Automatically =====&lt;br /&gt;
OWB's MIME Types settings can be used to configure automatic actions to files of certain types. Here is an example of how to show PDF files automatically with the [[Applications/VPDF|VPDF]] application when clicked on the browser.&lt;br /&gt;
&lt;br /&gt;
Open OWB's settings from the '''Settings-&amp;gt;Preferences...''' pulldown menu option and select the '''MIME Types''' page. Click the '''Add''' button and fill in the information below like this:&lt;br /&gt;
 MIME Type: '''application''' / '''pdf'''&lt;br /&gt;
 Extension: '''pdf'''&lt;br /&gt;
 Action: '''External Viewer''', Viewer: '''SYS:Applications/VPDF/VPDF''', and the last unnamed field: '''&amp;amp;#37;f'''&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button.&lt;br /&gt;
&lt;br /&gt;
If you now click a PDF file on a web page, the file is downloaded to a temporary location and shown on VPDF automatically.&lt;br /&gt;
: [[File:GettingStarted_OWB8.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Getting YouTube Videos to Play Better on the Browser Window =====&lt;br /&gt;
YouTube videos should play on OWB by default, but there are a thing or two to note.&lt;br /&gt;
&lt;br /&gt;
Playing videos in a small embedded window is a very CPU intensive task and not quite smooth on most systems. Moving the video playback from the embedded mode to the overlay mode helps the task hugely. This can be achieved with the YouTube Fullscreen Fix script. Videos will be shown in a nearly fullscreen window using the overlay functions and the CPU load may drop from 100&amp;amp;#37; even to 30&amp;amp;#37; on a G4 system, resulting in perfectly smooth playback of course.&lt;br /&gt;
&lt;br /&gt;
'''Download''' the latest script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js (YouTube changes its internals randomly and that's why the script on the MorphOS ISO is probably old already. Grunch also may have an old version and manual installation is highly advisable).&lt;br /&gt;
&lt;br /&gt;
Copy the downloaded script to the '''System:Applications/OWB/Scripts''' directory.&lt;br /&gt;
: [[File:GettingStarted_OWB9.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Scripts window from the '''Windows-&amp;gt;Scripts...''' pulldown menu entry on OWB.&lt;br /&gt;
: [[File:GettingStarted_OWB10.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Add''' button on the Scripts window and select the YouTube_Fullscreen_Fix.js file.&lt;br /&gt;
: [[File:GettingStarted_OWB11.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Make sure that the '''Enable''' setting is chosen and close the window. A '''restart''' of the browser is needed to activate the script, but after that you should be able to get any YouTube video to the smooth fullscreen mode by clicking the &amp;quot;fullscreen&amp;quot; or &amp;quot;large player&amp;quot; buttons on the video '''after the video playback has started'''. If you're watching a video embedded on some other external site, click the settings button instead. '''Double click''' the fullscreen video to get it to the embedded mode again.&lt;br /&gt;
: [[File:GettingStarted_OWB12.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Content Blocking and YouTube =====&lt;br /&gt;
If you have enabled the Content Blocking (AdBlock) option on the OWB settings, YouTube videos with ads will also get blocked. You can make a rule to the content blocking settings to allow those videos to be shown.&lt;br /&gt;
&lt;br /&gt;
Open '''Windows-&amp;gt;Content Blocking...''' from OWB's pulldown menus, click the '''Add''' button, and write '''youtube.com''' to the Rule line, and close the window.&lt;br /&gt;
: [[File:OWB_ContentBlockingYT.png]]&lt;br /&gt;
&lt;br /&gt;
If you have any other problems with the YouTube playback, check the [[Tips_and_Tricks#Problems_with_YouTube_Videos|Tips and Tricks]] page for more information.&lt;br /&gt;
&lt;br /&gt;
===== Configuring Fonts =====&lt;br /&gt;
&lt;br /&gt;
Browsers come with font settings. However, these settings are often neglected. Web developer has at least three options for selecting a font which would be displayed by default on your browser screen. &lt;br /&gt;
It can be a generic font, &amp;quot;hand picked&amp;quot; local font-family, or on-the-fly downloaded web font. Nevertheless the user still has the choice which font he or she actually wants to use. Reasons: privacy, security, speed, aesthetic.&lt;br /&gt;
&lt;br /&gt;
MorphOS is bundled with True Type, PostScript and Amiga Bitmap fonts.&lt;br /&gt;
OWB uses fontconfig for font handling. Fonts are cached whenever a change in font directories is detected.&lt;br /&gt;
If you want to use your fonts exclusively - fonts.conf should only use the path where you store the fonts (for example '''SYS:Fonts/_ttf''').&lt;br /&gt;
&lt;br /&gt;
Fontconfig is a library providing font configuration, customization and application access. It uses freetype library which supports plenty of font formats (excluding Amiga Bitmap fonts).&lt;br /&gt;
Presets are stored in the '''MOSSYS:Fontconfig/conf.avail''' directory.&lt;br /&gt;
&lt;br /&gt;
'''FONTS:Fontconfig/fonts.conf''' (default font dirs)&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;!-- Font directory list --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_pcf&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_pfb&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pcf&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pfb&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Example settings:'''&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/conf.d/51-local.conf'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
	&amp;lt;!-- Load local system customization file --&amp;gt;&lt;br /&gt;
	&amp;lt;include ignore_missing=&amp;quot;yes&amp;quot;&amp;gt;local.conf&amp;lt;/include&amp;gt;&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/local.conf''' (turns off antialias for font sizes smaller than 16 and disables autohint)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;!-- /etc/fonts/local.conf file for local customizations --&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;size&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;pixelsize&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;autohint&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Blocking fonts'''&lt;br /&gt;
&lt;br /&gt;
In OWB, go to '''Settings-&amp;gt;Fonts''' and choose default fonts and sizes.&lt;br /&gt;
&lt;br /&gt;
To disable remote web fonts this line needs to be added to its filter '''SYS:Applications/OWB/Conf/blocked.prefs''':&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
/\.ttf|\.otf|\.woff|\.woff2\?/&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
A specific font can be whitelisted too:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
@@/*actually-nice-font.ttf&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
This isn't ideal. OWB will try block anything_not_whitelisted.ttf, even if you look for a nicefont.ttf in Google Search.&lt;br /&gt;
&lt;br /&gt;
==== Configuring MPlayer ====&lt;br /&gt;
===== General Options =====&lt;br /&gt;
The default configuration of MPlayer is quite fine, but here are a few options I like to set myself. Start MPlayer in the GUI mode by double clicking the GMPlayer icon in the MPlayer directory. There's just one MPlayer executable, but two icons with different [[Fundamentals_of_MorphOS#Icon_Tool_Types|tooltypes]] to start the program with or without the GUI mode.&lt;br /&gt;
&lt;br /&gt;
With default options MPlayer scales the played video to fit the current window dimensions which typically leaves big empty borders around the video. To get the window dimensions to change with the video dimensions, select the '''Video-&amp;gt;Window Dimension-&amp;gt;100&amp;amp;#37;''' option, and '''Settings-&amp;gt;Save''' to save it as a default setting.&lt;br /&gt;
: [[File:GettingStarted_MPlayer.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Preferences window by selecting the '''Settings-&amp;gt;Preferences...''' option from MPlayer's pulldown menus. There are some settings to consider.&lt;br /&gt;
&lt;br /&gt;
The Audio Driver has two audio output options for AHI to choose from. The default '''ahi''' option outputs the audio through the ''Music Unit'', which gives the best audio quality, but blocks simultaneous audio from any other sources. The '''ahi_dev''' option uses the device mode which can be shared with the other sources, but it results in a slight decrease in the audio quality. So, if you want to be able to watch videos while some other program, like a music player, would still continue with audio output, select the '''ahi_dev''' option.&lt;br /&gt;
&lt;br /&gt;
If you don't like any usage data gathering, disable the '''Remember last visited path''' option :)&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Preferences.png]]&lt;br /&gt;
&lt;br /&gt;
===== Setting MPlayer as the Default Player on Ambient  =====&lt;br /&gt;
MorphOS doesn't have any default player for videos and double clicking a video file from Ambient results in an error requester. MPlayer can be set as the default video player by editing the Ambient MIME type settings.&lt;br /&gt;
&lt;br /&gt;
Open the '''Ambient Settings''' window and the '''Mime''' page. With the built-in MIME editor you can add different kinds of actions for different file formats or classes. Let's add MPlayer as the default player for all video files, not just for some individual video formats.&lt;br /&gt;
&lt;br /&gt;
Select '''video''' from the right-hand side list tree and click the '''Edit''' button. Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
&lt;br /&gt;
In the Action Editor window type a name for the action, for example '''Play''', and click the '''Add''' button on that window too.&lt;br /&gt;
&lt;br /&gt;
Change the AmigaDOS command to '''Run &amp;gt;NIL: SYS:Applications/MPlayer/MPlayer -gui 1 &amp;amp;#37;sp''' (change the path to the MPlayer executable if you have it in a different location) and change the Event type to '''DoubleClick'''. Note: the ''-gui 1'' option, which starts MPlayer in the GUI mode, has to be written in lower case, having it in upper case doesn't work!&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Adding_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Ok''', '''Ok''', and '''Save''' buttons.&lt;br /&gt;
&lt;br /&gt;
If you now double click a video file in Ambient, it gets played on MPlayer. You can also see the Play option in the contextual menu when right clicking the video file.&lt;br /&gt;
: [[File:GettingStarted_MPlayer2.png|320px]] [[File:GettingStarted_MPlayer_Working_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You can add several actions as contextual menu events if you want to have more options for opening videos. Only imagination is the limit, and you can for example have contextual menu entries to start MPlayer playback with filters skipped (use the ''-lavdopts skiploopfilter=all'' option to speed up the video playback a little) and have an option to convert the video with mencoder etc.&lt;br /&gt;
: [[File:GettingStarted_ActionEditor2.png|230px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with CRABUM ====&lt;br /&gt;
&lt;br /&gt;
You can add custom pulldown menus to Ambient with ARexx scripts created by the CRABUM program. It's a good way to launch programs or scripts which you don't want to have on panels. Installation of [[Getting_Started#rexxsyslib.library|rexxsyslib.library]] is required.&lt;br /&gt;
&lt;br /&gt;
Let's create an Edit menu with options to edit different system startup scripts. Double click the CRABUM icon from the SYS:Utilities/CRABUM directory if you installed it with the default options.&lt;br /&gt;
&lt;br /&gt;
# Click the '''Menu''' button to add a new menu and change its title to '''Edit'''.&lt;br /&gt;
# Click the '''Item''' button to add a new item under the created menu.&lt;br /&gt;
# Type '''User-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-startup''' to the AmigaDOS command line. &amp;quot;Run &amp;gt;NIL:&amp;quot; starts the Ed program as a background process and it won't block Ambient while it is running.&lt;br /&gt;
# Create an another item by clicking the '''Item''' button.&lt;br /&gt;
# Type '''User-network-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-network-startup''' to the AmigaDOS command line.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM1.png|320px]]&lt;br /&gt;
# Click the '''Save''' button to save the resulting ARexx script.&lt;br /&gt;
# If you save the file to the SYS:WBStartup drawer, it will be launched automatically at boot time. Enter a suitable name for the file, for example '''Edit-menu'''. Click the '''Ok''' button.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After a reboot (or doubleclicking of the file) you'll have the new Edit menu on the Ambient pulldown menus and you can easily open the system files for editing.&lt;br /&gt;
: [[File:GettingStarted_CRABUM3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== More Configuring ==&lt;br /&gt;
=== Synchronizing the Clock with an Internet Time Server ===&lt;br /&gt;
The system clock can be synchronized manually from the MorphOS Preferences application by clicking the '''Set date and time using the Internet''' button in the Time preferences.&lt;br /&gt;
: [[File:MorphOS_Preferences_Time.png|320px]]&lt;br /&gt;
&lt;br /&gt;
There's also the [[Shell_Commands/SetClockNTP|SetClockNTP]] shell command which can be launched manually or automatically at boot time. To synchronize the time every time the system starts edit the '''S:user-network-startup''' file and remove the semi-colon from the SetClockNTP line.&lt;br /&gt;
&lt;br /&gt;
To edit the S:user-network-startup file open the shell (or the Execute Command prompt) and type '''Ed S:user-network-startup''', or open the System partition, select the '''All Files''' mode, browse to the '''S''' directory and select the '''Edit...''' option from the right click contextual menu. Or if you configured the Edit menu with CRABUM earlier, use it now.&lt;br /&gt;
: [[File:GettingStarted_Enable_SetClockNTP.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Shell ===&lt;br /&gt;
==== Editing the Shell-startup file ====&lt;br /&gt;
The shell can be customized with the shell-startup file, but by default the file is only found in a MorphOS system directory where the user shouldn't do any modifications. It must be copied to a user directory first to make any changes to it. Open a new shell window and type '''Copy MOSSYS:S/shell-startup SYS:S/shell-startup''', and then edit it for example with the '''Ed SYS:S/shell-startup''' command. The shell-startup file is executed every time a new shell window is opened.&lt;br /&gt;
: [[File:GettingStarted_shell-startup.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Adding Paths ====&lt;br /&gt;
There are some useful shell commands around the installed system which aren't in the system's search path and thus you'll have to enter their complete paths when using them. Adding their locations to the search path allows them to be run just by their names, which is much more convenient.&lt;br /&gt;
&lt;br /&gt;
Here are few suggestions to add to the '''SYS:S/shell-startup''' file (remember the previous step first!). Or if you want them to be available globally on all occasions, they can be added to the '''S:user-startup''' file instead.&lt;br /&gt;
* '''Path SYS:Applications/RemoteShell/Files ADD''' adds SSH related commands like scp, sftp, ssh, etc to the search path. Note: use the [[Applications/RemoteShell|Remote Shell]] application for regular SSH sessions, because it supports arrow keys and other things better.&lt;br /&gt;
* '''Path SYS:Applications/OWB/Datas ADD''' adds wget to the search path.&lt;br /&gt;
* '''Path SYS:Applications/MPlayer ADD''' adds MPlayer and mencoder to the search path if you have installed MPlayer. Change the path if you have installed it elsewhere.&lt;br /&gt;
&lt;br /&gt;
==== Configuring the GUI ====&lt;br /&gt;
There are many buttons and hotkeys to add to the shell window besides the default ones. Check the preferences by selecting the '''Settings-&amp;gt;Edit Prefs...''' option from the Shell's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Available functions can be dragged to '''Hotkeys''' or '''Buttons''' lists and the changes are seen in real time in the shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You may also want to set the default window size and position for new shell windows on the '''Settings''' tab. Click the '''Get from window''' button to get values from the current shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Remember to save the modifications in the '''Settings''' menu.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Setting Jukebox as the Default Player for MP3 Files ===&lt;br /&gt;
If you double click an MP3 file in an Ambient window, it is played with the very simple internal player. Here are two solutions to change the default player to the more advanced [[Utilities/Jukebox|Jukebox]] music player. Ambient's internal player is still left to the context menu as an option.&lt;br /&gt;
==== Simple Solution ====&lt;br /&gt;
A simple solution is just to create a new mpeg audio MIME type definition which just launches the Jukebox player with the double clicked filename as an argument.&lt;br /&gt;
# Open the Mime page in the Ambient settings, select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''Run &amp;gt;NIL: SYS:Utilities/Jukebox &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and you should see this in the MIME Editor window.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Save''' buttons. If you double click an MP3 file now, Jukebox starts and plays the clicked file. There are also two entires in the right click contextual menu and the option which is used for the double click action is written in bold.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Advanced Solution ====&lt;br /&gt;
An advanced solution is to use the third party [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script. It will give more flexible options to add files to Jukebox, and we'll learn how to add submenus into context menus. There are shortcuts to install the script if you read the documentation in the archive, but let's do this manually to learn the configuration method better. It will be helpful in the future when configuring any other filetypes.&lt;br /&gt;
&lt;br /&gt;
# Download the script archive from [http://aminet.net/package/mus/play/JukeboxAdder Aminet] or from [http://morphos-files.net/find.php?find=jukeboxadder MorphOS Files].&lt;br /&gt;
# Copy the '''jukeboxadder.lua''' file from the archive to the '''SYS:S/''' directory.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder1.png|320px]]&lt;br /&gt;
# Open the '''Mime''' page in the '''Ambient settings''', select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua PLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and then click '''Add''' again in the MIME Editor window to create more ways to add files to Jukebox from the context menus.&lt;br /&gt;
# Type '''Add to Jukebox''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua ADD &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string. This will create a submenu named ''Jukebox'' in the context menu and place the new ''Add to Jukebox'' option there.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Add''' once again to create the last entry.&lt;br /&gt;
# Type '''Add to Jukebox and Play''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''MOSSYS:C/LuaX S:jukeboxadder.lua ADDPLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder4.png|320px]]&lt;br /&gt;
# Click '''Ok''', '''Ok''', and '''Save'''. Now you can see more options in the context menu for MP3 files and double clicking will always clear the previous songs and play the new song immediately.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
It is also possible to add the same functionality for context menus of directories if you want to be able to add whole directories to Jukebox at once. There's a special '''internal -&amp;gt; x-morphos-globalaction-directory''' MIME type which can be used to add context menu entries for all directories. Repeat the previous steps (6-18) for it, but make all '''Event types''' to use the '''Menu''' option (in step 9 too).&lt;br /&gt;
: [[File:GettingStarted_JukeboxAdder6.png|320px]] [[File:GettingStarted_JukeboxAdder7.png|320px]] [[File:GettingStarted_JukeboxAdder8.png|320px]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3866</id>
		<title>Getting Started</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3866"/>
				<updated>2018-04-30T20:22:59Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== A Beginner's Guide to MorphOS ==&lt;br /&gt;
&lt;br /&gt;
You have installed MorphOS to a compatible machine, but... now what? You could always go and install a pre-configured package like Chrysalis, but you would end up with a system configured for someone else's taste and you still wouldn't know how to actually use the operating system. If you are in this situation and would like to learn how MorphOS works, this is a tutorial for you! The tutorial will guide you through the things you should do and notice after a fresh install, with practical examples from basic configuration options to installing new software. It won't cover all the details and is just an opinion on how to proceed, but it should give you some knowledge how to continue on your own and make your own decisions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting Comfortable with the User Interface and the Ambient Desktop ==&lt;br /&gt;
=== The First Boot ===&lt;br /&gt;
&lt;br /&gt;
After a boot you're presented with the plain looking Ambient, the desktop environment of MorphOS. The first thing you should learn is to get familiar with the basic usage, and to tune the interface settings so that they won't annoy you. The worst thing is if a user plays around a bit and just curses at the system when it doesn't work as expected or wanted. You aren't forced into just one kind of behaviour with MorphOS!&lt;br /&gt;
: [[File:GettingStarted_Ambient.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Right mouse click is widely used on MorphOS and if you're using a device without a physical button for it, check the tips over [[Tips_and_Tricks#How_to_Use_RMB_with_One-button_Mouse | here]]. Pressing the right mouse button over the Ambient screen opens Ambient's pulldown menus where you can find few important options. For example, options to shut down the system, to open a new shell window, or to open system settings.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Shutdown.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== System Settings ===&lt;br /&gt;
&lt;br /&gt;
The MorphOS Preferences application is used to edit system-wide settings. It can be launched from the Ambient's pulldown menu by selecting the &amp;quot;Settings-&amp;gt;System...&amp;quot; menu option or by browsing to the System:Prefs/ drawer and double clicking the Preferences icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_System_Settings.png]] [[File:GettingStarted_MorphOS_Preferences.png|237px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Screens ====&lt;br /&gt;
&lt;br /&gt;
If MorphOS didn't get the optimal resolution of your monitor with DDC, a different screen mode can be selected from the Screens settings. If the wanted mode isn't seen there, open the Monitors settings instead to create a completely new mode.&lt;br /&gt;
&lt;br /&gt;
If you have a graphics card with a low amount of memory, you can try to make the memory consumption smaller by disabling the Enhanced Display setting (3D accelerated graphics functions for 2D screens) or by reducing the color depth. More information can be found  [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
MorphOS skins (themes for the graphical appearance) can also be changed from the Screens settings.&lt;br /&gt;
&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== IControl ====&lt;br /&gt;
&lt;br /&gt;
IControl settings are the most important settings for the overall user experience. This is the place to look in order to avoid the usual comments like ''&amp;quot;Why doesn't X work like Y in the other OS?&amp;quot;'', ''&amp;quot;Why there isn't a feature Z?&amp;quot;'', ''&amp;quot;I can't use a system like this!&amp;quot;''. Everyone should check these settings first before going any further.&lt;br /&gt;
&lt;br /&gt;
===== Hotkeys =====&lt;br /&gt;
MorphOS has many nice features to use with keyboard shortcuts or mouse buttons, but only few are activated by default. Let's activate more!&lt;br /&gt;
&lt;br /&gt;
To add a new hotkey for the wanted function click the popup button on the right side, select &amp;quot;'''Sample'''&amp;quot;, and press the wanted key combination. The pressed combination is then recorded on the corresponding line and should be shown there. Repeat the procedure if you didn't get it as wanted on the first try. Changed settings will be taken into use after you click the Save or Use button.&lt;br /&gt;
&lt;br /&gt;
Here is how to set the &amp;quot;control left-alt c&amp;quot; key combination to '''center the active window''' on the screen:&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Hotkeys2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Here are some other recommendations to activate, but feel free to use your own preferences for the hotkeys:&lt;br /&gt;
* '''Active Window: To Back''' - double click with middle mouse button to send a window back of other windows.&lt;br /&gt;
* '''Active Window: Zoom''' - &amp;quot;control left-alt m&amp;quot;, to toggle between a maximized and minimized window.&lt;br /&gt;
* '''Active Window: Activate Next''' - &amp;quot;left-command tab&amp;quot;, to have the ''alt-tab'' functionality found on many other operating systems. Using ctrl-tab or alt-tab isn't recommended because they would overlap with the shell's functionality on MorphOS. Command-tab also happens be the same in OS X.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys3.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Note: You can also add several hotkeys for a function by selecting the New Hotkey option from the popup button's menu.&lt;br /&gt;
&lt;br /&gt;
===== Screens and Desktop =====&lt;br /&gt;
&lt;br /&gt;
Important options concerning how windows and menus behave can be found on the Screens and Desktop settings.&lt;br /&gt;
&lt;br /&gt;
I'd recommend turning on the '''Maximize window when clicking on the Zoom gadget''' option. The Zoom gadget will then toggle the window size between full screen (with the screen title bar still visible) and the initial window size and position. I find it much more comfortable than the legacy placement between two obscure positions. The previously configured Zoom hotkey will also work better with this option enabled.&lt;br /&gt;
&lt;br /&gt;
If you prefer being able to drag windows out of the screen without pressing any qualifier key, like on mainstream systems, select the '''When dragging windows... allow them to be placed out of screen, unless Control is pressed''' option.&lt;br /&gt;
&lt;br /&gt;
The default behaviour of the pulldown menus may be a bit unfamiliar for old Amiga users, but there are several options to get them working as expected. I like to disable the '''Menus shall remain opened even when mouse button is released''' option and enable the '''Open menus under mouse pointer outside screen titlebar area''' option.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Touchpad ====&lt;br /&gt;
&lt;br /&gt;
If you're using a laptop system, check the Touchpad setttings. You might want to disable clicking from the pad to avoid any accidental clicks.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Touchpad.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Laptop ====&lt;br /&gt;
&lt;br /&gt;
If you're not a Mac user, you might find it odd that you need to press the fn key when using the function keys for normal activities, and not when modifying, for example, the screen brightness. The '''Press and hold the fn key to modify screen brightness, audio volume, etc.''' option will change the functionality the other way around.&lt;br /&gt;
&lt;br /&gt;
Some systems also have the '''Automatic LCD brightness and keyboard backlight control''' option here. Disable it if you're annoyed by changing lightning.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Laptop.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Windows ===&lt;br /&gt;
&lt;br /&gt;
The first icon you see on the Ambient desktop is the &amp;quot;'''My MorphOS'''&amp;quot; icon. By double clicking it you'll get a window with icons of all volumes and assigns of the system. It works like a root directory with quick access to different locations.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS.png|320px]]&lt;br /&gt;
&lt;br /&gt;
If you find it a bit clumsy to work in the icon mode, like I do, you can change the view to '''the list mode''' from the cycle button on the right side of the window.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
With default settings Ambient doesn't remember the changed mode or other window properties next time you open it, but you can right click the window border or an empty area on the file lister to bring up a contextual window menu and select the &amp;quot;'''Snapshot-&amp;gt;Window'''&amp;quot; option to save the window properties. Default position and size for a window can be saved that way too. If you defined the centering hotkey earlier, you can try it now :)&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The same can also be done for normal directory windows. While &amp;quot;My MorphOS&amp;quot; window settings are exceptionally saved to Ambient's configuration files, normal directories' settings are saved to an icon file (a file with .info extension). If you change and save the mode for the Work: partition for example, you see a disk.info file appearing there.&lt;br /&gt;
: [[File:GettingStarted_Icon_Mode.png|320px]] [[File:GettingStarted_List_Mode_Snapshot.png|320px]] [[File:GettingStarted_List_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Displayed columns can be selected by right clicking the column title area, but modify the [[Getting_Started#Lister|default lister settings]] to your liking before starting to save settings for individual windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Lister_Columns.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Settings ===&lt;br /&gt;
&lt;br /&gt;
Ambient is actually a separate application itself and it has its own settings separated from the general system preferences. The previously mentioned system settings affect all programs and screens, but strictly desktop related settings are found in the Ambient settings. The Ambient Settings window can be opened by selecting the &amp;quot;Settings-&amp;gt;Ambient...&amp;quot; option from Ambient's pulldown menu.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Ambient_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
==== Miscellaneous ====&lt;br /&gt;
&lt;br /&gt;
The Miscellaneous page on the Ambient settings has a nice option to get the My MorphOS window opened when double clicking anywhere on the empty area of the desktop. It really speeds up the working when you don't have to move the mouse a long way to the top corner or dig the icon out from under some other windows. Enable it with the '''Double click on desktop opens MyMorphOS window''' option.&lt;br /&gt;
&lt;br /&gt;
The My MorphOS icon is just wasting space on the desktop after the previous setting and you can hide it by disabling the '''Display MyMorphOS icon''' option.&lt;br /&gt;
&lt;br /&gt;
If you like to have a bit more eye candy on the context menus, you can also enable the '''Show images in context menu''' option while you're here.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Misc.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Lister ====&lt;br /&gt;
The default properties of the list mode of Ambient windows can be changed on the Lister settings. Disable the '''Compact size display''' if you want to see exact file sizes in bytes always. You may also want to select different columns to be shown in the listers by double clicking items on the '''File Properties''' list to set them hidden or shown. '''Date &amp;amp; Time''' instead of just Date would probably be a common choice.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Lister.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Panels ====&lt;br /&gt;
&lt;br /&gt;
Many new users are wondering if there is any kind of dock application on MorphOS, because there isn't any shown by default. MorphOS has ''panels'' for that and you can have as many panels as you want on the desktop, arranged horizontally or vertically. The panels have features like zipping to hide and unhide them, sub panels and other Panel Object plugins, etc. There just isn't any configured by default and user can create a panel or panels how he likes.&lt;br /&gt;
&lt;br /&gt;
To create a new panel, open the Panels page on the Ambient settings and click the '''New Panel''' button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels1.png|320px]]&lt;br /&gt;
An empty panel can be dragged anywhere and you can find some of its settings on the '''Name &amp;amp; Look''' and '''Behaviour''' tabs. If you want to place the panel on a screen border the '''Attached to Borders''' option makes it easier. The '''Alpha''' option controls the transparency of a panel, but it only works if the Enhanced Display option for the Ambient screen enabled and working. The same applies to the '''Hide Dragbar''' option as well.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels2.png|320px]]&lt;br /&gt;
Programs can be added to the panel by dragging and dropping their icons to the panel list to the wanted position on the list tree, or to the panel itself. Items in the panel list can be rearranged by drag and drop too.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels3.png|320px]]&lt;br /&gt;
Available Panel Objects are listed on the right-hand side and they can be dragged and dropped to any position on the panel tree. All items on the panel may have their own settings, which are shown when an item is clicked once with the left mouse button. In this example picture a new sub panel has been created and its icon image is being changed to a custom one.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels4.png|320px]]&lt;br /&gt;
If you want to clone the color settings from the main panel to a sub panel, you can use the MUI clipboard to temporarily store a setting. Drag &amp;amp; drop the wanted color button to the clipboard button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels5.png|320px]]&lt;br /&gt;
Then activate the sub panel settings and drag &amp;amp; drop the clipboard button to the sub panel's color button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels6.png|320px]]&lt;br /&gt;
And here's a picture of the created panel with its sub panel in action. Remember to click the Save button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels7.png|320px]]&lt;br /&gt;
The panels also have a context menu that can be accessed with a right click. You'll have quick access to the panel settings and some other options there.&lt;br /&gt;
&lt;br /&gt;
If you lock a panel, items dragged to it aren't added to the panel anymore, but the dragged items are opened with the program you dropped them onto. Text files can be dropped onto the Scribble icon, MP3 files and directories can be dropped onto the Jukebox icon, video and audio files onto the MPlayer icon, and so on.&lt;br /&gt;
: [[File:GettingStarted_Panel_Locked1.png|320px]] [[File:GettingStarted_Panel_Locked2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Window ====&lt;br /&gt;
&lt;br /&gt;
Ambient windows are very configurable and users should at least check the buttons available for the toolbar. Just adding a few buttons can make a difference in usability. The buttons and other items can be dragged from the Available Buttons list to the Current Toolbar group, and vice versa to remove them from the toolbar. All changes are updated in real time to any open Ambient windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
In this example picture '''Makedir''' and '''Delete''' buttons are separated with the '''Space''' button, and they have been added into a row with other buttons. Also the '''Bookmarks''' button has been added as the last item on the toolbar. It always stays at the right border no matter how big a window is, because it's been added after the '''Flexible space''' button. &lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Keyboard ====&lt;br /&gt;
===== Built-in Command Hotkeys =====&lt;br /&gt;
Check the Ambient hotkeys from this section and change them to your liking. If you have a laptop without the numeric keypad, you should change hotkeys which are using numpad combinations by default. I, for example, am used to having the '''Cycle Mode''' option on the key above the tab key and the '''Cycle Submode''' option when the same key is pressed with the shift key. It feels somehow quicker to use them from there than from the numeric keypad with a standard keyboard too.&lt;br /&gt;
&lt;br /&gt;
===== Custom Command Hotkeys =====&lt;br /&gt;
Practically any functionality can be added to custom hotkey definitions. This might be a bit advanced topic, but let's show few definitions which will improve the usability.&lt;br /&gt;
&lt;br /&gt;
A new Ambient hotkey can be created by clicking the Add a Hotkey button. The first text field is for the name of the hotkey and it can be anything. The second text field is the actual keyboard combination to activate a function. The Edit Command button is used to define what actually happens when you press the hotkey in Ambient.&lt;br /&gt;
&lt;br /&gt;
Let's create two hotkeys which can be used to copy selected files' names as text to the clipboard, with and without the preceding path.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Copy name with path''' and the hotkey combination to '''ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si FULLPATH''', and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
* Click the '''Add a Hotkey''' button again, define the name as '''Copy name''' and the hotkey combination to '''rshift ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si''', and press the enter key. Click the '''Ok''' button, save the Ambient settings, and you're done.&lt;br /&gt;
&lt;br /&gt;
If you now select any files on an Ambient window and press the ''ralt c'' key combination, the selected file names with their full paths get copied to the clipboard and are available to be pasted to any other application. The ''rshift ralt c'' combination copies pathless file names to the clipboard.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Keyboard1.png|320px]] [[File:GettingStarted_Ambient_Settings_Keyboard2.png|320px]] [[File:GettingStarted_ActionEditor1.png|214px]]&lt;br /&gt;
&lt;br /&gt;
Another example which will extract any selected archive file to the ram disk with the ''lshift control e'' combination.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Extract to RAM''' and the hotkey combination to '''lshift control e'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Leave the action type to '''AmigaDOS''', type in the command '''XADUnFile &amp;amp;#37;sp RAM:''' , and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Screenbar Modules ===&lt;br /&gt;
&lt;br /&gt;
[[Screenbar_Modules | Screenbar modules]] are plugins which can populate the empty area on the screen title bar with some useful information and functionality. The modules are visible on every (MUI) [[Fundamentals_of_MorphOS#Screens | screen]], which makes them more useful than, for example, Panel Objects. Panel Objects are only seen on the Ambient screen and can be left under some other windows more easily.&lt;br /&gt;
&lt;br /&gt;
Screenbar modules can be enabled and disabled from the screen depth gadget menu. The menu also contains options to arrange order of the modules and to change their settings. The menu can be accessed by right clicking, or with a long left press, over the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget | screen depth gadget]].&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Menu.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Let's have a look at how to configure a few modules. Enable the '''CPU Monitor''', '''Drivelamps''', and '''Memory''' modules by, for example, multiselecting them at once. Reopen the screen depth gadget menu, select the '''Settings...''' option, and select CPU Monitor from the settings list. The CPU Monitor module is a bit narrow by default, so let's increase its width a little.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_CPU_Monitor.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Drivelamps module has more configuration options. Enable the '''Show lamp''' option for '''usbscsi.device''' if you want to see access indicators for both HD and USB drives. The default look doesn't seem to be that good for two lamps, but you can tune it a bit. Disabling the frame from the Look group (select None) and selecting the recessed frame for the Lamp Look group does some wonders already. You can also adjust the spacing options, if the lamps don't seem to match with the height of the CPU Monitor or other modules.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Drivelamps.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Memory module shows free memory in percents by default, but it can be changed to other types too. Click the popup button on the '''Information''' line to see the options. The information line can have any text, and for example a ''&amp;amp;#37;mfMB free'' line would show free memory in megabytes followed by the &amp;quot;MB free&amp;quot; text.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Memory.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== MUI Settings ===&lt;br /&gt;
&lt;br /&gt;
MUI is the default GUI toolkit of MorphOS and its looks and behaviour can be changed in almost every aspect. Its basic philosophy is to ''offer as much freedom as possible to users by taking away as much work as possible from programmers''. A user can modify the looks of MUI programs very drastically both globally and per program. It can be done by changing single settings or by loading complete themes (presets).&lt;br /&gt;
&lt;br /&gt;
The most important thing for a new user is to understand the difference between the global settings and settings of individual programs.&lt;br /&gt;
&lt;br /&gt;
The global settings are the default settings which will apply to any program using MUI. The global settings can be changed by selecting the '''Settings-&amp;gt;MUI...''' option from the Ambient's pulldown menus or by double clicking the '''SYS:Prefs/MUI''' icon.&lt;br /&gt;
&lt;br /&gt;
Each MUI program can also have its own MUI settings which will override the global settings, but be careful when changing for example the looks of an individual program. If you decide to change the global theme later, the changes made to the individual programs might not fit the global theme anymore. The MUI settings of a program can be found on its pulldown menu or from the window's [[Fundamentals_of_MorphOS#Window_border_gadgets | popup gadget]] menu. Ambient's MUI settings are found from the '''Settings-&amp;gt;Ambient MUI...''' option in the Ambient's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Let's change a couple of options in the global MUI settings as an example. Open the global MUI settings window.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_MUI_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
The default ghosting effect for buttons is a bit old-fashioned raster effect and it will look much better with just reduced visibility. Select the Buttons page and click the None option for the ghosted gadgets. The visibility can be changed with the slider below, but the default value will be fine too. You'll see the changes in real time on any MUI program, the Test button is a bit obsolete with the latest MUI. I also like to make the Active Gadgets Border a bit smaller than the original size. Click the Save button when you're satisfied.&lt;br /&gt;
: [[File:GettingStarted_MUI_Settings_Buttons.png|380px]]&lt;br /&gt;
&lt;br /&gt;
The Settings button in the top left corner opens a popup menu with options to reset the settings or load different presets.&lt;br /&gt;
&lt;br /&gt;
All MUI settings get saved to the ENVARC:MUI/ directory. If you mess too much with settings for individual programs, the last resort to revert the settings to default is to remove the corresponding settings files from that directory or restore them from a backup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hiding the Boot Image Partition on Macs ===&lt;br /&gt;
&lt;br /&gt;
On Macs you'll have a small HFS formatted partition which contains a few files needed to boot the system. The files are only used by [[Dictionary_of_Terms | Open Firmware]] at boot time and the user or MorphOS itself don't normally need them for anything. Open Firmware, as well as the MorphOS update wizard, can access the partition even if it's not mounted on MorphOS. If we disable the auto mounting of it, our desktop will look a bit cleaner and the crucial boot files will then be safe from accidents as well.&lt;br /&gt;
&lt;br /&gt;
Launch the [[Tools/HDConfig]] program and click on the small HFS partition. Its name should be '''DH0:''' if the system is installed with the default partition layout. Disable the '''Automatically mount partition''' option and click the '''OK''' button.&lt;br /&gt;
: [[File:GettingStarted_HDConfig1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button which is in the red area on the left side and accept the changes.&lt;br /&gt;
: [[File:GettingStarted_HDConfig2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Next time you boot the system, the partition isn't shown on the desktop. If you need to access it later for some reason, it can be mounted temporarily with the [[Tools/Mounter]] tool.&lt;br /&gt;
: [[File:GettingStarted_Ambient2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging the Drive Icons ===&lt;br /&gt;
The drive icons can be dragged to a different order and then saved to their positions by selecting the '''Snapshot''' option from the right click contextual menu. If the Ram Disk icon is dragged to the leftmost position and snapshot, it will appear at that position after a reboot and unsnapshot icons appear next to it.&lt;br /&gt;
: [[File:GettingStarted_Drive_Icons.png|320px]] [[File:GettingStarted_Drive_Icons_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installing, Updating, and Configuring Essential Software ==&lt;br /&gt;
&lt;br /&gt;
=== Checking the Network Connection ===&lt;br /&gt;
&lt;br /&gt;
Before continuing to installing new software, let's check if your machine is properly connected to the Internet.&lt;br /&gt;
&lt;br /&gt;
Open the shell by selecting the '''Ambient-&amp;gt;New Shell...''' option from the Ambient's pulldown menus, or by pressing '''rcommand n''' keyboard combination or doubleclicking the '''SYS:Tools/MUI Shell''' icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_New_Shell.png]]&lt;br /&gt;
&lt;br /&gt;
Check the Internet connection by pinging some hostname on the Internet. Type for example '''ping www.google.com''' on the shell window. If you get replies from the host, the connection is OK and you can proceed by pressing '''CTRL C''' to quit the Ping command and closing the shell window. If you don't get any replies with time values, quit the pinging by the CTRL C combination and read the [[Configuring_Network | Configuring a Network Connection]] tutorial.&lt;br /&gt;
: [[File:GettingStarted_Ping.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Grunch ===&lt;br /&gt;
&lt;br /&gt;
[http://geit.de/eng_grunch.html Grunch] is an advanced software package manager, which can install, update, and uninstall software. It's a good starting point for new users and I'd advice everyone to check what it has to offer before visiting [[Links#File_Repositories | other sites]] for more software.&lt;br /&gt;
&lt;br /&gt;
Start Odyssey Web Browser from '''SYS:Applications/OWB/OWB''' and download Grunch from its [http://geit.de/eng_grunch.html homepage] or from the [http://morphos-files.net/find.php?find=grunch MorphOS Files] site. Save the '''Grunch.lha''' archive file to any location, for example to Work partition or to Ram Disk. The archive isn't needed after the installation.&lt;br /&gt;
: [[File:GettingStarted_OWB4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Close the browser and use Ambient to browse to the location where you saved the Grunch.lha file. If you don't see the file, click the rightmost cycle gadget on the window to show all files. Double click the archive, open the Grunch directory, and double click the '''Grunch.install''' file to start the installer script. Running an installer directly from the unpacked archive is a bit of a shortcut which might not work with all programs, but let's demonstrate it anyway. The traditional and more failproof way would be to unpack an archive file to a temporary location and then run the installer script from an unarchived directory. Read more about installing third party software [[Installing_software | here]].&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Next''' button and select the destination location. The '''System:Applications''' path is OK unless you want to keep the bundled software and 3rd party software strictly separated. In that case you could make a new Applications directory on the Work partition, for example.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After the installation has finished, browse to the location where you installed the program and double click the '''Grunch''' icon. Grunch starts, but you'll have to wait a little while it does its initial checks and updates.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Start.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Before using the program any further, check the Grunch preferences. Select the '''Settings-&amp;gt;Grunch...''' option from the pulldown menus and open the '''Miscellaneous''' tab. I'd change the '''Temporary Directory''' path to somewhere else than to your system partition. If you have enough memory, you could have it even on the Ram Disk, but a temporary directory on the Work partition would be a safe bet.&lt;br /&gt;
&lt;br /&gt;
Click the file requester button at the end of the line to browse to the wanted location. The ''':''' button shows the available volumes, and you can also create new directories from the right click contextual menu on the file requester.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You should check the '''Path''' tab next, and think twice if you want to change them from the default paths. The default paths are OK if you think that all 3rd party and bundled software can reside mixed in the same directories and if you have enough free space on the system partition. But if you like to keep 3rd party and bundled software separated and have the system directories as clean as possible, change the paths now. You could make suitable directories on the Work partition, for instance.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
When you're happy with the settings, click the Save button.&lt;br /&gt;
&lt;br /&gt;
The Grunch icon can also be dragged to a panel for quick access later.&lt;br /&gt;
: [[File:GettingStarted_Dragging_Grunch_to_Panel.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software with Grunch ===&lt;br /&gt;
==== rexxsyslib.library ====&lt;br /&gt;
The rexxsyslib.library file enables the ARexx scripting language support on your system and it should be installed as early as possible. Many programs and their features rely on a working ARexx environment. Select it from the list and click the '''Install''' button on Grunch. You may need a reboot before it'll be in use.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software1.png]]&lt;br /&gt;
&lt;br /&gt;
==== Updating OWB ====&lt;br /&gt;
MorphOS usually comes with a bit old version of the OWB browser and you should check for a newer version. Select OWB from the list and click the '''Check''' button.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software2.png]]&lt;br /&gt;
&lt;br /&gt;
You probably have an old version, so click the '''Update...''' button and wait for it to finish.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software3.png]]&lt;br /&gt;
&lt;br /&gt;
You could also change the mode to Update.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software4.png]]&lt;br /&gt;
&lt;br /&gt;
==== MPlayer ====&lt;br /&gt;
MPlayer is hands down the best video player on MorphOS, just install it. It also works as an audio player with comprehensive support for different formats.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software5.png]]&lt;br /&gt;
&lt;br /&gt;
==== PowerSDL ====&lt;br /&gt;
PowerSDL libraries are required for many software ports from other platforms. It's better to install them as well.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software6.png]]&lt;br /&gt;
&lt;br /&gt;
==== CRABUM ====&lt;br /&gt;
CRABUM lets you to customize the pulldown menus on Ambient. It's quite handy for adding some hidden but quickly available features and shortcuts. We'll need this for some later examples.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software7.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Installed Software ===&lt;br /&gt;
==== Configuring Odyssey Web Browser ====&lt;br /&gt;
Here are few examples or suggestions for the initial configuration of OWB. Do the steps you like.&lt;br /&gt;
===== Downloading More Suitable Fonts for OWB =====&lt;br /&gt;
The fonts provided with MorphOS aren't designed with web usage in mind and it's better to download certain Microsoft fonts for the browser. Luckily it's an easy job to do, because there's a downloader script included in the OWB's directory.&lt;br /&gt;
&lt;br /&gt;
Open the '''SYS:Applications/OWB''' directory and double click the '''Download Fonts''' icon. Note: if the script doesn't seem to work, try [http://www.morphos-storage.net/?page=Network/Web&amp;amp;file=Download_Fonts_for_OWB.lha this one] instead.&lt;br /&gt;
: [[File:GettingStarted_OWB1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Yes''' on the requester and wait patiently for  the downloading and installing of the fonts. The output window closes when the process is finished.&lt;br /&gt;
: [[File:GettingStarted_OWB2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
OWB initializes the fonts on the first run, but it will start much quicker next time.&lt;br /&gt;
: [[File:GettingStarted_OWB3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Making OWB to Use Its Own Screen =====&lt;br /&gt;
A browser is usually an application people want to use in a full size window and on Amigaish systems it makes sense to put it on its own screen. When used on a separate screen it leaves more space for other programs on the Ambient screen, and you don't have such a hassle when handling them all. Bringing screens to front is also a very quick operation, you'll never see any slowdowns like on other systems where you reopen full size windows from taskbars, for example.&lt;br /&gt;
&lt;br /&gt;
You could send a program to a new screen with the &amp;quot;Jump to Screen -&amp;gt; New&amp;quot; option from the window popup gadget, but it's mainly designed for temporary usage. Let's do the configuration more proper way instead.&lt;br /&gt;
&lt;br /&gt;
Launch OWB, click on the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]], and select '''MUI Settings...'''. Another way to access the MUI settings would be from the '''Settings-&amp;gt;MUI...''' pulldown menu option when OWB's window is active.&lt;br /&gt;
: [[File:GettingStarted_OWB5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the '''Screen''' page, select the '''customized public screen from MUI screen database''' option, and click the '''New...''' button.&lt;br /&gt;
&lt;br /&gt;
The Edit Screen window opens. The name field is for the screen name and the title field for the screen title text. They can be anything you want, but it's better to keep them informative. '''OWB''' would be a good screen name now and '''Odyssey Web Browser''' for the title. Check if the default screen mode is what you want. Be also sure that the '''Close automatically''' option is enabled.&lt;br /&gt;
&lt;br /&gt;
It might be a good idea to disable the '''Enhanced Display''' option, because it doesn't give that much advantage with full screen applications. Graphics memory usage will also be lower, and it might be crucial to save some graphics memory on systems with less than 128 MB memory on the graphics card. Read more about how to reduce graphics memory usage [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
Click the '''Ok''' button on the Edit Screen window and the '''Save''' button on the MUI Settings window.&lt;br /&gt;
&lt;br /&gt;
Note: this method can be used with all MUI programs to put them on their own screens, from shell windows to small utilities, bigger applications, and games. I prefer to use the [[Applications/Showgirls|ShowGirls]] image viewer and other bigger applications on their own screens. Several MUI programs can also share the same custom screen, as it isn't limited just to a program per screen. You could for example group some network programs to one screen, and some other programs to another screen, etc.&lt;br /&gt;
: [[File:GettingStarted_OWB6.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The OWB window doesn't probably have optimal size and position on the newly created screen. Right click over the [[Fundamentals_of_MorphOS#Window_border_gadgets | zoom gadget]] and select the '''Maximize''' option or if you configured the zoom gadget as suggested [[Getting_Started#Screens_and_Desktop | earlier]], click the zoom gadget twice. The maximize option leaves the screen title bar visible, but otherwise resizes the window to full screen size. Select the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]] to save the window position permanently.&lt;br /&gt;
: [[File:Tips_Zoommenu.png|top]] [[File:GettingStarted_OWB7.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Open PDF Files Automatically =====&lt;br /&gt;
OWB's MIME Types settings can be used to configure automatic actions to files of certain types. Here is an example of how to show PDF files automatically with the [[Applications/VPDF|VPDF]] application when clicked on the browser.&lt;br /&gt;
&lt;br /&gt;
Open OWB's settings from the '''Settings-&amp;gt;Preferences...''' pulldown menu option and select the '''MIME Types''' page. Click the '''Add''' button and fill in the information below like this:&lt;br /&gt;
 MIME Type: '''application''' / '''pdf'''&lt;br /&gt;
 Extension: '''pdf'''&lt;br /&gt;
 Action: '''External Viewer''', Viewer: '''SYS:Applications/VPDF/VPDF''', and the last unnamed field: '''&amp;amp;#37;f'''&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button.&lt;br /&gt;
&lt;br /&gt;
If you now click a PDF file on a web page, the file is downloaded to a temporary location and shown on VPDF automatically.&lt;br /&gt;
: [[File:GettingStarted_OWB8.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Getting YouTube Videos to Play Better on the Browser Window =====&lt;br /&gt;
YouTube videos should play on OWB by default, but there are a thing or two to note.&lt;br /&gt;
&lt;br /&gt;
Playing videos in a small embedded window is a very CPU intensive task and not quite smooth on most systems. Moving the video playback from the embedded mode to the overlay mode helps the task hugely. This can be achieved with the YouTube Fullscreen Fix script. Videos will be shown in a nearly fullscreen window using the overlay functions and the CPU load may drop from 100&amp;amp;#37; even to 30&amp;amp;#37; on a G4 system, resulting in perfectly smooth playback of course.&lt;br /&gt;
&lt;br /&gt;
'''Download''' the latest script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js (YouTube changes its internals randomly and that's why the script on the MorphOS ISO is probably old already. Grunch also may have an old version and manual installation is highly advisable).&lt;br /&gt;
&lt;br /&gt;
Copy the downloaded script to the '''System:Applications/OWB/Scripts''' directory.&lt;br /&gt;
: [[File:GettingStarted_OWB9.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Scripts window from the '''Windows-&amp;gt;Scripts...''' pulldown menu entry on OWB.&lt;br /&gt;
: [[File:GettingStarted_OWB10.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Add''' button on the Scripts window and select the YouTube_Fullscreen_Fix.js file.&lt;br /&gt;
: [[File:GettingStarted_OWB11.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Make sure that the '''Enable''' setting is chosen and close the window. A '''restart''' of the browser is needed to activate the script, but after that you should be able to get any YouTube video to the smooth fullscreen mode by clicking the &amp;quot;fullscreen&amp;quot; or &amp;quot;large player&amp;quot; buttons on the video '''after the video playback has started'''. If you're watching a video embedded on some other external site, click the settings button instead. '''Double click''' the fullscreen video to get it to the embedded mode again.&lt;br /&gt;
: [[File:GettingStarted_OWB12.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Content Blocking and YouTube =====&lt;br /&gt;
If you have enabled the Content Blocking (AdBlock) option on the OWB settings, YouTube videos with ads will also get blocked. You can make a rule to the content blocking settings to allow those videos to be shown.&lt;br /&gt;
&lt;br /&gt;
Open '''Windows-&amp;gt;Content Blocking...''' from OWB's pulldown menus, click the '''Add''' button, and write '''youtube.com''' to the Rule line, and close the window.&lt;br /&gt;
: [[File:OWB_ContentBlockingYT.png]]&lt;br /&gt;
&lt;br /&gt;
If you have any other problems with the YouTube playback, check the [[Tips_and_Tricks#Problems_with_YouTube_Videos|Tips and Tricks]] page for more information.&lt;br /&gt;
&lt;br /&gt;
===== Configuring Fonts =====&lt;br /&gt;
&lt;br /&gt;
Browsers come with font settings. However, these settings are often neglected. Web developer has at least three options for selecting a font which would be displayed by default on your browser screen. &lt;br /&gt;
It can be a generic font, &amp;quot;hand picked&amp;quot; local font-family, or on-the-fly downloaded web font. Nevertheless the user still has the choice which font he or she actually wants to use. Reasons: privacy, security, speed, aesthetic.&lt;br /&gt;
&lt;br /&gt;
MorphOS is bundled with True Type, PostScript and Amiga Bitmap fonts.&lt;br /&gt;
OWB uses fontconfig for font handling. Fonts are cached whenever a change in font directories is detected.&lt;br /&gt;
If you want to use your fonts exclusively - fonts.conf should only use the path where you store the fonts (for example '''SYS:Fonts/_ttf''').&lt;br /&gt;
&lt;br /&gt;
Fontconfig is a library providing font configuration, customization and application access. It uses freetype library which supports plenty of font formats (excluding Amiga Bitmap fonts).&lt;br /&gt;
Presets are stored in the '''MOSSYS:Fontconfig/conf.avail''' directory.&lt;br /&gt;
&lt;br /&gt;
'''FONTS:Fontconfig/fonts.conf''' (default font dirs)&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;!-- Font directory list --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_pcf&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_pfb&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;SYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pcf&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pfb&amp;lt;/dir&amp;gt;&lt;br /&gt;
	&amp;lt;dir&amp;gt;MOSSYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Example settings:'''&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
	&amp;lt;!-- Load local system customization file --&amp;gt;&lt;br /&gt;
	&amp;lt;include ignore_missing=&amp;quot;yes&amp;quot;&amp;gt;local.conf&amp;lt;/include&amp;gt;&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/local.conf''' (turns off antialias for font sizes smaller than 16 and disables autohint)&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
&amp;lt;?xml version=&amp;quot;1.0&amp;quot;?&amp;gt;&lt;br /&gt;
&amp;lt;!DOCTYPE fontconfig SYSTEM &amp;quot;fonts.dtd&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;!-- /etc/fonts/local.conf file for local customizations --&amp;gt;&lt;br /&gt;
&amp;lt;fontconfig&amp;gt;&lt;br /&gt;
  &lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;size&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot; &amp;gt;&lt;br /&gt;
		&amp;lt;test name=&amp;quot;pixelsize&amp;quot; qual=&amp;quot;any&amp;quot; compare=&amp;quot;more&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&lt;br /&gt;
		&amp;lt;/test&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;antialias&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
	&amp;lt;match target=&amp;quot;font&amp;quot;&amp;gt;&lt;br /&gt;
		&amp;lt;edit name=&amp;quot;autohint&amp;quot; mode=&amp;quot;assign&amp;quot;&amp;gt;&lt;br /&gt;
			&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&lt;br /&gt;
		&amp;lt;/edit&amp;gt;&lt;br /&gt;
	&amp;lt;/match&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/fontconfig&amp;gt;&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Blocking fonts'''&lt;br /&gt;
&lt;br /&gt;
In OWB, go to '''Settings-&amp;gt;Fonts''' and choose default fonts and sizes.&lt;br /&gt;
&lt;br /&gt;
To disable remote web fonts this line needs to be added to its filter '''SYS:Applications/OWB/Conf/blocked.prefs''':&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
/\.ttf|\.otf|\.woff|\.woff2\?/&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
A specific font can be whitelisted too:&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
@@/*actually-nice-font.ttf&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
This isn't ideal. OWB will try block anything_not_whitelisted.ttf, even if you look for a nicefont.ttf in Google Search.&lt;br /&gt;
&lt;br /&gt;
==== Configuring MPlayer ====&lt;br /&gt;
===== General Options =====&lt;br /&gt;
The default configuration of MPlayer is quite fine, but here are a few options I like to set myself. Start MPlayer in the GUI mode by double clicking the GMPlayer icon in the MPlayer directory. There's just one MPlayer executable, but two icons with different [[Fundamentals_of_MorphOS#Icon_Tool_Types|tooltypes]] to start the program with or without the GUI mode.&lt;br /&gt;
&lt;br /&gt;
With default options MPlayer scales the played video to fit the current window dimensions which typically leaves big empty borders around the video. To get the window dimensions to change with the video dimensions, select the '''Video-&amp;gt;Window Dimension-&amp;gt;100&amp;amp;#37;''' option, and '''Settings-&amp;gt;Save''' to save it as a default setting.&lt;br /&gt;
: [[File:GettingStarted_MPlayer.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Preferences window by selecting the '''Settings-&amp;gt;Preferences...''' option from MPlayer's pulldown menus. There are some settings to consider.&lt;br /&gt;
&lt;br /&gt;
The Audio Driver has two audio output options for AHI to choose from. The default '''ahi''' option outputs the audio through the ''Music Unit'', which gives the best audio quality, but blocks simultaneous audio from any other sources. The '''ahi_dev''' option uses the device mode which can be shared with the other sources, but it results in a slight decrease in the audio quality. So, if you want to be able to watch videos while some other program, like a music player, would still continue with audio output, select the '''ahi_dev''' option.&lt;br /&gt;
&lt;br /&gt;
If you don't like any usage data gathering, disable the '''Remember last visited path''' option :)&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Preferences.png]]&lt;br /&gt;
&lt;br /&gt;
===== Setting MPlayer as the Default Player on Ambient  =====&lt;br /&gt;
MorphOS doesn't have any default player for videos and double clicking a video file from Ambient results in an error requester. MPlayer can be set as the default video player by editing the Ambient MIME type settings.&lt;br /&gt;
&lt;br /&gt;
Open the '''Ambient Settings''' window and the '''Mime''' page. With the built-in MIME editor you can add different kinds of actions for different file formats or classes. Let's add MPlayer as the default player for all video files, not just for some individual video formats.&lt;br /&gt;
&lt;br /&gt;
Select '''video''' from the right-hand side list tree and click the '''Edit''' button. Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
&lt;br /&gt;
In the Action Editor window type a name for the action, for example '''Play''', and click the '''Add''' button on that window too.&lt;br /&gt;
&lt;br /&gt;
Change the AmigaDOS command to '''Run &amp;gt;NIL: SYS:Applications/MPlayer/MPlayer -gui 1 &amp;amp;#37;sp''' (change the path to the MPlayer executable if you have it in a different location) and change the Event type to '''DoubleClick'''. Note: the ''-gui 1'' option, which starts MPlayer in the GUI mode, has to be written in lower case, having it in upper case doesn't work!&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Adding_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Ok''', '''Ok''', and '''Save''' buttons.&lt;br /&gt;
&lt;br /&gt;
If you now double click a video file in Ambient, it gets played on MPlayer. You can also see the Play option in the contextual menu when right clicking the video file.&lt;br /&gt;
: [[File:GettingStarted_MPlayer2.png|320px]] [[File:GettingStarted_MPlayer_Working_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You can add several actions as contextual menu events if you want to have more options for opening videos. Only imagination is the limit, and you can for example have contextual menu entries to start MPlayer playback with filters skipped (use the ''-lavdopts skiploopfilter=all'' option to speed up the video playback a little) and have an option to convert the video with mencoder etc.&lt;br /&gt;
: [[File:GettingStarted_ActionEditor2.png|230px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with CRABUM ====&lt;br /&gt;
&lt;br /&gt;
You can add custom pulldown menus to Ambient with ARexx scripts created by the CRABUM program. It's a good way to launch programs or scripts which you don't want to have on panels. Installation of [[Getting_Started#rexxsyslib.library|rexxsyslib.library]] is required.&lt;br /&gt;
&lt;br /&gt;
Let's create an Edit menu with options to edit different system startup scripts. Double click the CRABUM icon from the SYS:Utilities/CRABUM directory if you installed it with the default options.&lt;br /&gt;
&lt;br /&gt;
# Click the '''Menu''' button to add a new menu and change its title to '''Edit'''.&lt;br /&gt;
# Click the '''Item''' button to add a new item under the created menu.&lt;br /&gt;
# Type '''User-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-startup''' to the AmigaDOS command line. &amp;quot;Run &amp;gt;NIL:&amp;quot; starts the Ed program as a background process and it won't block Ambient while it is running.&lt;br /&gt;
# Create an another item by clicking the '''Item''' button.&lt;br /&gt;
# Type '''User-network-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-network-startup''' to the AmigaDOS command line.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM1.png|320px]]&lt;br /&gt;
# Click the '''Save''' button to save the resulting ARexx script.&lt;br /&gt;
# If you save the file to the SYS:WBStartup drawer, it will be launched automatically at boot time. Enter a suitable name for the file, for example '''Edit-menu'''. Click the '''Ok''' button.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After a reboot (or doubleclicking of the file) you'll have the new Edit menu on the Ambient pulldown menus and you can easily open the system files for editing.&lt;br /&gt;
: [[File:GettingStarted_CRABUM3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== More Configuring ==&lt;br /&gt;
=== Synchronizing the Clock with an Internet Time Server ===&lt;br /&gt;
The system clock can be synchronized manually from the MorphOS Preferences application by clicking the '''Set date and time using the Internet''' button in the Time preferences.&lt;br /&gt;
: [[File:MorphOS_Preferences_Time.png|320px]]&lt;br /&gt;
&lt;br /&gt;
There's also the [[Shell_Commands/SetClockNTP|SetClockNTP]] shell command which can be launched manually or automatically at boot time. To synchronize the time every time the system starts edit the '''S:user-network-startup''' file and remove the semi-colon from the SetClockNTP line.&lt;br /&gt;
&lt;br /&gt;
To edit the S:user-network-startup file open the shell (or the Execute Command prompt) and type '''Ed S:user-network-startup''', or open the System partition, select the '''All Files''' mode, browse to the '''S''' directory and select the '''Edit...''' option from the right click contextual menu. Or if you configured the Edit menu with CRABUM earlier, use it now.&lt;br /&gt;
: [[File:GettingStarted_Enable_SetClockNTP.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Shell ===&lt;br /&gt;
==== Editing the Shell-startup file ====&lt;br /&gt;
The shell can be customized with the shell-startup file, but by default the file is only found in a MorphOS system directory where the user shouldn't do any modifications. It must be copied to a user directory first to make any changes to it. Open a new shell window and type '''Copy MOSSYS:S/shell-startup SYS:S/shell-startup''', and then edit it for example with the '''Ed SYS:S/shell-startup''' command. The shell-startup file is executed every time a new shell window is opened.&lt;br /&gt;
: [[File:GettingStarted_shell-startup.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Adding Paths ====&lt;br /&gt;
There are some useful shell commands around the installed system which aren't in the system's search path and thus you'll have to enter their complete paths when using them. Adding their locations to the search path allows them to be run just by their names, which is much more convenient.&lt;br /&gt;
&lt;br /&gt;
Here are few suggestions to add to the '''SYS:S/shell-startup''' file (remember the previous step first!). Or if you want them to be available globally on all occasions, they can be added to the '''S:user-startup''' file instead.&lt;br /&gt;
* '''Path SYS:Applications/RemoteShell/Files ADD''' adds SSH related commands like scp, sftp, ssh, etc to the search path. Note: use the [[Applications/RemoteShell|Remote Shell]] application for regular SSH sessions, because it supports arrow keys and other things better.&lt;br /&gt;
* '''Path SYS:Applications/OWB/Datas ADD''' adds wget to the search path.&lt;br /&gt;
* '''Path SYS:Applications/MPlayer ADD''' adds MPlayer and mencoder to the search path if you have installed MPlayer. Change the path if you have installed it elsewhere.&lt;br /&gt;
&lt;br /&gt;
==== Configuring the GUI ====&lt;br /&gt;
There are many buttons and hotkeys to add to the shell window besides the default ones. Check the preferences by selecting the '''Settings-&amp;gt;Edit Prefs...''' option from the Shell's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Available functions can be dragged to '''Hotkeys''' or '''Buttons''' lists and the changes are seen in real time in the shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You may also want to set the default window size and position for new shell windows on the '''Settings''' tab. Click the '''Get from window''' button to get values from the current shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Remember to save the modifications in the '''Settings''' menu.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Setting Jukebox as the Default Player for MP3 Files ===&lt;br /&gt;
If you double click an MP3 file in an Ambient window, it is played with the very simple internal player. Here are two solutions to change the default player to the more advanced [[Utilities/Jukebox|Jukebox]] music player. Ambient's internal player is still left to the context menu as an option.&lt;br /&gt;
==== Simple Solution ====&lt;br /&gt;
A simple solution is just to create a new mpeg audio MIME type definition which just launches the Jukebox player with the double clicked filename as an argument.&lt;br /&gt;
# Open the Mime page in the Ambient settings, select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''Run &amp;gt;NIL: SYS:Utilities/Jukebox &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and you should see this in the MIME Editor window.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Save''' buttons. If you double click an MP3 file now, Jukebox starts and plays the clicked file. There are also two entires in the right click contextual menu and the option which is used for the double click action is written in bold.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Advanced Solution ====&lt;br /&gt;
An advanced solution is to use the third party [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script. It will give more flexible options to add files to Jukebox, and we'll learn how to add submenus into context menus. There are shortcuts to install the script if you read the documentation in the archive, but let's do this manually to learn the configuration method better. It will be helpful in the future when configuring any other filetypes.&lt;br /&gt;
&lt;br /&gt;
# Download the script archive from [http://aminet.net/package/mus/play/JukeboxAdder Aminet] or from [http://morphos-files.net/find.php?find=jukeboxadder MorphOS Files].&lt;br /&gt;
# Copy the '''jukeboxadder.lua''' file from the archive to the '''SYS:S/''' directory.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder1.png|320px]]&lt;br /&gt;
# Open the '''Mime''' page in the '''Ambient settings''', select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua PLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and then click '''Add''' again in the MIME Editor window to create more ways to add files to Jukebox from the context menus.&lt;br /&gt;
# Type '''Add to Jukebox''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua ADD &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string. This will create a submenu named ''Jukebox'' in the context menu and place the new ''Add to Jukebox'' option there.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Add''' once again to create the last entry.&lt;br /&gt;
# Type '''Add to Jukebox and Play''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''MOSSYS:C/LuaX S:jukeboxadder.lua ADDPLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder4.png|320px]]&lt;br /&gt;
# Click '''Ok''', '''Ok''', and '''Save'''. Now you can see more options in the context menu for MP3 files and double clicking will always clear the previous songs and play the new song immediately.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
It is also possible to add the same functionality for context menus of directories if you want to be able to add whole directories to Jukebox at once. There's a special '''internal -&amp;gt; x-morphos-globalaction-directory''' MIME type which can be used to add context menu entries for all directories. Repeat the previous steps (6-18) for it, but make all '''Event types''' to use the '''Menu''' option (in step 9 too).&lt;br /&gt;
: [[File:GettingStarted_JukeboxAdder6.png|320px]] [[File:GettingStarted_JukeboxAdder7.png|320px]] [[File:GettingStarted_JukeboxAdder8.png|320px]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	<entry>
		<id>https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3865</id>
		<title>Getting Started</title>
		<link rel="alternate" type="text/html" href="https://library.morph.zone/index.php?title=Getting_Started&amp;diff=3865"/>
				<updated>2018-04-30T19:19:36Z</updated>
		
		<summary type="html">&lt;p&gt;Korni: /* Configuring Odyssey Web Browser */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== A Beginner's Guide to MorphOS ==&lt;br /&gt;
&lt;br /&gt;
You have installed MorphOS to a compatible machine, but... now what? You could always go and install a pre-configured package like Chrysalis, but you would end up with a system configured for someone else's taste and you still wouldn't know how to actually use the operating system. If you are in this situation and would like to learn how MorphOS works, this is a tutorial for you! The tutorial will guide you through the things you should do and notice after a fresh install, with practical examples from basic configuration options to installing new software. It won't cover all the details and is just an opinion on how to proceed, but it should give you some knowledge how to continue on your own and make your own decisions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Getting Comfortable with the User Interface and the Ambient Desktop ==&lt;br /&gt;
=== The First Boot ===&lt;br /&gt;
&lt;br /&gt;
After a boot you're presented with the plain looking Ambient, the desktop environment of MorphOS. The first thing you should learn is to get familiar with the basic usage, and to tune the interface settings so that they won't annoy you. The worst thing is if a user plays around a bit and just curses at the system when it doesn't work as expected or wanted. You aren't forced into just one kind of behaviour with MorphOS!&lt;br /&gt;
: [[File:GettingStarted_Ambient.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Right mouse click is widely used on MorphOS and if you're using a device without a physical button for it, check the tips over [[Tips_and_Tricks#How_to_Use_RMB_with_One-button_Mouse | here]]. Pressing the right mouse button over the Ambient screen opens Ambient's pulldown menus where you can find few important options. For example, options to shut down the system, to open a new shell window, or to open system settings.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Shutdown.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== System Settings ===&lt;br /&gt;
&lt;br /&gt;
The MorphOS Preferences application is used to edit system-wide settings. It can be launched from the Ambient's pulldown menu by selecting the &amp;quot;Settings-&amp;gt;System...&amp;quot; menu option or by browsing to the System:Prefs/ drawer and double clicking the Preferences icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_System_Settings.png]] [[File:GettingStarted_MorphOS_Preferences.png|237px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Screens ====&lt;br /&gt;
&lt;br /&gt;
If MorphOS didn't get the optimal resolution of your monitor with DDC, a different screen mode can be selected from the Screens settings. If the wanted mode isn't seen there, open the Monitors settings instead to create a completely new mode.&lt;br /&gt;
&lt;br /&gt;
If you have a graphics card with a low amount of memory, you can try to make the memory consumption smaller by disabling the Enhanced Display setting (3D accelerated graphics functions for 2D screens) or by reducing the color depth. More information can be found  [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
MorphOS skins (themes for the graphical appearance) can also be changed from the Screens settings.&lt;br /&gt;
&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== IControl ====&lt;br /&gt;
&lt;br /&gt;
IControl settings are the most important settings for the overall user experience. This is the place to look in order to avoid the usual comments like ''&amp;quot;Why doesn't X work like Y in the other OS?&amp;quot;'', ''&amp;quot;Why there isn't a feature Z?&amp;quot;'', ''&amp;quot;I can't use a system like this!&amp;quot;''. Everyone should check these settings first before going any further.&lt;br /&gt;
&lt;br /&gt;
===== Hotkeys =====&lt;br /&gt;
MorphOS has many nice features to use with keyboard shortcuts or mouse buttons, but only few are activated by default. Let's activate more!&lt;br /&gt;
&lt;br /&gt;
To add a new hotkey for the wanted function click the popup button on the right side, select &amp;quot;'''Sample'''&amp;quot;, and press the wanted key combination. The pressed combination is then recorded on the corresponding line and should be shown there. Repeat the procedure if you didn't get it as wanted on the first try. Changed settings will be taken into use after you click the Save or Use button.&lt;br /&gt;
&lt;br /&gt;
Here is how to set the &amp;quot;control left-alt c&amp;quot; key combination to '''center the active window''' on the screen:&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Hotkeys2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Here are some other recommendations to activate, but feel free to use your own preferences for the hotkeys:&lt;br /&gt;
* '''Active Window: To Back''' - double click with middle mouse button to send a window back of other windows.&lt;br /&gt;
* '''Active Window: Zoom''' - &amp;quot;control left-alt m&amp;quot;, to toggle between a maximized and minimized window.&lt;br /&gt;
* '''Active Window: Activate Next''' - &amp;quot;left-command tab&amp;quot;, to have the ''alt-tab'' functionality found on many other operating systems. Using ctrl-tab or alt-tab isn't recommended because they would overlap with the shell's functionality on MorphOS. Command-tab also happens be the same in OS X.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Hotkeys3.png|380px]]&lt;br /&gt;
&lt;br /&gt;
Note: You can also add several hotkeys for a function by selecting the New Hotkey option from the popup button's menu.&lt;br /&gt;
&lt;br /&gt;
===== Screens and Desktop =====&lt;br /&gt;
&lt;br /&gt;
Important options concerning how windows and menus behave can be found on the Screens and Desktop settings.&lt;br /&gt;
&lt;br /&gt;
I'd recommend turning on the '''Maximize window when clicking on the Zoom gadget''' option. The Zoom gadget will then toggle the window size between full screen (with the screen title bar still visible) and the initial window size and position. I find it much more comfortable than the legacy placement between two obscure positions. The previously configured Zoom hotkey will also work better with this option enabled.&lt;br /&gt;
&lt;br /&gt;
If you prefer being able to drag windows out of the screen without pressing any qualifier key, like on mainstream systems, select the '''When dragging windows... allow them to be placed out of screen, unless Control is pressed''' option.&lt;br /&gt;
&lt;br /&gt;
The default behaviour of the pulldown menus may be a bit unfamiliar for old Amiga users, but there are several options to get them working as expected. I like to disable the '''Menus shall remain opened even when mouse button is released''' option and enable the '''Open menus under mouse pointer outside screen titlebar area''' option.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop1.png|380px]] [[File:GettingStarted_MorphOS_Preferences_Screens_and_Desktop2.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Touchpad ====&lt;br /&gt;
&lt;br /&gt;
If you're using a laptop system, check the Touchpad setttings. You might want to disable clicking from the pad to avoid any accidental clicks.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Touchpad.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Laptop ====&lt;br /&gt;
&lt;br /&gt;
If you're not a Mac user, you might find it odd that you need to press the fn key when using the function keys for normal activities, and not when modifying, for example, the screen brightness. The '''Press and hold the fn key to modify screen brightness, audio volume, etc.''' option will change the functionality the other way around.&lt;br /&gt;
&lt;br /&gt;
Some systems also have the '''Automatic LCD brightness and keyboard backlight control''' option here. Disable it if you're annoyed by changing lightning.&lt;br /&gt;
: [[File:GettingStarted_MorphOS_Preferences_Laptop.png|380px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Windows ===&lt;br /&gt;
&lt;br /&gt;
The first icon you see on the Ambient desktop is the &amp;quot;'''My MorphOS'''&amp;quot; icon. By double clicking it you'll get a window with icons of all volumes and assigns of the system. It works like a root directory with quick access to different locations.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS.png|320px]]&lt;br /&gt;
&lt;br /&gt;
If you find it a bit clumsy to work in the icon mode, like I do, you can change the view to '''the list mode''' from the cycle button on the right side of the window.&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
With default settings Ambient doesn't remember the changed mode or other window properties next time you open it, but you can right click the window border or an empty area on the file lister to bring up a contextual window menu and select the &amp;quot;'''Snapshot-&amp;gt;Window'''&amp;quot; option to save the window properties. Default position and size for a window can be saved that way too. If you defined the centering hotkey earlier, you can try it now :)&lt;br /&gt;
: [[File:GettingStarted_MyMorphOS_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The same can also be done for normal directory windows. While &amp;quot;My MorphOS&amp;quot; window settings are exceptionally saved to Ambient's configuration files, normal directories' settings are saved to an icon file (a file with .info extension). If you change and save the mode for the Work: partition for example, you see a disk.info file appearing there.&lt;br /&gt;
: [[File:GettingStarted_Icon_Mode.png|320px]] [[File:GettingStarted_List_Mode_Snapshot.png|320px]] [[File:GettingStarted_List_Mode.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Displayed columns can be selected by right clicking the column title area, but modify the [[Getting_Started#Lister|default lister settings]] to your liking before starting to save settings for individual windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Lister_Columns.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ambient Settings ===&lt;br /&gt;
&lt;br /&gt;
Ambient is actually a separate application itself and it has its own settings separated from the general system preferences. The previously mentioned system settings affect all programs and screens, but strictly desktop related settings are found in the Ambient settings. The Ambient Settings window can be opened by selecting the &amp;quot;Settings-&amp;gt;Ambient...&amp;quot; option from Ambient's pulldown menu.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_Ambient_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
==== Miscellaneous ====&lt;br /&gt;
&lt;br /&gt;
The Miscellaneous page on the Ambient settings has a nice option to get the My MorphOS window opened when double clicking anywhere on the empty area of the desktop. It really speeds up the working when you don't have to move the mouse a long way to the top corner or dig the icon out from under some other windows. Enable it with the '''Double click on desktop opens MyMorphOS window''' option.&lt;br /&gt;
&lt;br /&gt;
The My MorphOS icon is just wasting space on the desktop after the previous setting and you can hide it by disabling the '''Display MyMorphOS icon''' option.&lt;br /&gt;
&lt;br /&gt;
If you like to have a bit more eye candy on the context menus, you can also enable the '''Show images in context menu''' option while you're here.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Misc.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Lister ====&lt;br /&gt;
The default properties of the list mode of Ambient windows can be changed on the Lister settings. Disable the '''Compact size display''' if you want to see exact file sizes in bytes always. You may also want to select different columns to be shown in the listers by double clicking items on the '''File Properties''' list to set them hidden or shown. '''Date &amp;amp; Time''' instead of just Date would probably be a common choice.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Lister.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Panels ====&lt;br /&gt;
&lt;br /&gt;
Many new users are wondering if there is any kind of dock application on MorphOS, because there isn't any shown by default. MorphOS has ''panels'' for that and you can have as many panels as you want on the desktop, arranged horizontally or vertically. The panels have features like zipping to hide and unhide them, sub panels and other Panel Object plugins, etc. There just isn't any configured by default and user can create a panel or panels how he likes.&lt;br /&gt;
&lt;br /&gt;
To create a new panel, open the Panels page on the Ambient settings and click the '''New Panel''' button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels1.png|320px]]&lt;br /&gt;
An empty panel can be dragged anywhere and you can find some of its settings on the '''Name &amp;amp; Look''' and '''Behaviour''' tabs. If you want to place the panel on a screen border the '''Attached to Borders''' option makes it easier. The '''Alpha''' option controls the transparency of a panel, but it only works if the Enhanced Display option for the Ambient screen enabled and working. The same applies to the '''Hide Dragbar''' option as well.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels2.png|320px]]&lt;br /&gt;
Programs can be added to the panel by dragging and dropping their icons to the panel list to the wanted position on the list tree, or to the panel itself. Items in the panel list can be rearranged by drag and drop too.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels3.png|320px]]&lt;br /&gt;
Available Panel Objects are listed on the right-hand side and they can be dragged and dropped to any position on the panel tree. All items on the panel may have their own settings, which are shown when an item is clicked once with the left mouse button. In this example picture a new sub panel has been created and its icon image is being changed to a custom one.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels4.png|320px]]&lt;br /&gt;
If you want to clone the color settings from the main panel to a sub panel, you can use the MUI clipboard to temporarily store a setting. Drag &amp;amp; drop the wanted color button to the clipboard button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels5.png|320px]]&lt;br /&gt;
Then activate the sub panel settings and drag &amp;amp; drop the clipboard button to the sub panel's color button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels6.png|320px]]&lt;br /&gt;
And here's a picture of the created panel with its sub panel in action. Remember to click the Save button.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Panels7.png|320px]]&lt;br /&gt;
The panels also have a context menu that can be accessed with a right click. You'll have quick access to the panel settings and some other options there.&lt;br /&gt;
&lt;br /&gt;
If you lock a panel, items dragged to it aren't added to the panel anymore, but the dragged items are opened with the program you dropped them onto. Text files can be dropped onto the Scribble icon, MP3 files and directories can be dropped onto the Jukebox icon, video and audio files onto the MPlayer icon, and so on.&lt;br /&gt;
: [[File:GettingStarted_Panel_Locked1.png|320px]] [[File:GettingStarted_Panel_Locked2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Window ====&lt;br /&gt;
&lt;br /&gt;
Ambient windows are very configurable and users should at least check the buttons available for the toolbar. Just adding a few buttons can make a difference in usability. The buttons and other items can be dragged from the Available Buttons list to the Current Toolbar group, and vice versa to remove them from the toolbar. All changes are updated in real time to any open Ambient windows.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
In this example picture '''Makedir''' and '''Delete''' buttons are separated with the '''Space''' button, and they have been added into a row with other buttons. Also the '''Bookmarks''' button has been added as the last item on the toolbar. It always stays at the right border no matter how big a window is, because it's been added after the '''Flexible space''' button. &lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Window2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Keyboard ====&lt;br /&gt;
===== Built-in Command Hotkeys =====&lt;br /&gt;
Check the Ambient hotkeys from this section and change them to your liking. If you have a laptop without the numeric keypad, you should change hotkeys which are using numpad combinations by default. I, for example, am used to having the '''Cycle Mode''' option on the key above the tab key and the '''Cycle Submode''' option when the same key is pressed with the shift key. It feels somehow quicker to use them from there than from the numeric keypad with a standard keyboard too.&lt;br /&gt;
&lt;br /&gt;
===== Custom Command Hotkeys =====&lt;br /&gt;
Practically any functionality can be added to custom hotkey definitions. This might be a bit advanced topic, but let's show few definitions which will improve the usability.&lt;br /&gt;
&lt;br /&gt;
A new Ambient hotkey can be created by clicking the Add a Hotkey button. The first text field is for the name of the hotkey and it can be anything. The second text field is the actual keyboard combination to activate a function. The Edit Command button is used to define what actually happens when you press the hotkey in Ambient.&lt;br /&gt;
&lt;br /&gt;
Let's create two hotkeys which can be used to copy selected files' names as text to the clipboard, with and without the preceding path.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Copy name with path''' and the hotkey combination to '''ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si FULLPATH''', and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
* Click the '''Add a Hotkey''' button again, define the name as '''Copy name''' and the hotkey combination to '''rshift ralt c'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Change the action type from AmigaDOS to '''Internal''', type in the command '''copyselectiontoclipboard VIEWID=&amp;amp;#37;Si''', and press the enter key. Click the '''Ok''' button, save the Ambient settings, and you're done.&lt;br /&gt;
&lt;br /&gt;
If you now select any files on an Ambient window and press the ''ralt c'' key combination, the selected file names with their full paths get copied to the clipboard and are available to be pasted to any other application. The ''rshift ralt c'' combination copies pathless file names to the clipboard.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Settings_Keyboard1.png|320px]] [[File:GettingStarted_Ambient_Settings_Keyboard2.png|320px]] [[File:GettingStarted_ActionEditor1.png|214px]]&lt;br /&gt;
&lt;br /&gt;
Another example which will extract any selected archive file to the ram disk with the ''lshift control e'' combination.&lt;br /&gt;
* Click the '''Add a Hotkey''' button, define the name as '''Extract to RAM''' and the hotkey combination to '''lshift control e'''. Click the '''Edit Command''' button and the '''Add''' button on the Action Editor window. Leave the action type to '''AmigaDOS''', type in the command '''XADUnFile &amp;amp;#37;sp RAM:''' , and press the enter key. Click the '''Ok''' button.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Screenbar Modules ===&lt;br /&gt;
&lt;br /&gt;
[[Screenbar_Modules | Screenbar modules]] are plugins which can populate the empty area on the screen title bar with some useful information and functionality. The modules are visible on every (MUI) [[Fundamentals_of_MorphOS#Screens | screen]], which makes them more useful than, for example, Panel Objects. Panel Objects are only seen on the Ambient screen and can be left under some other windows more easily.&lt;br /&gt;
&lt;br /&gt;
Screenbar modules can be enabled and disabled from the screen depth gadget menu. The menu also contains options to arrange order of the modules and to change their settings. The menu can be accessed by right clicking, or with a long left press, over the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget | screen depth gadget]].&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Menu.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Let's have a look at how to configure a few modules. Enable the '''CPU Monitor''', '''Drivelamps''', and '''Memory''' modules by, for example, multiselecting them at once. Reopen the screen depth gadget menu, select the '''Settings...''' option, and select CPU Monitor from the settings list. The CPU Monitor module is a bit narrow by default, so let's increase its width a little.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_CPU_Monitor.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Drivelamps module has more configuration options. Enable the '''Show lamp''' option for '''usbscsi.device''' if you want to see access indicators for both HD and USB drives. The default look doesn't seem to be that good for two lamps, but you can tune it a bit. Disabling the frame from the Look group (select None) and selecting the recessed frame for the Lamp Look group does some wonders already. You can also adjust the spacing options, if the lamps don't seem to match with the height of the CPU Monitor or other modules.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Drivelamps.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The Memory module shows free memory in percents by default, but it can be changed to other types too. Click the popup button on the '''Information''' line to see the options. The information line can have any text, and for example a ''&amp;amp;#37;mfMB free'' line would show free memory in megabytes followed by the &amp;quot;MB free&amp;quot; text.&lt;br /&gt;
: [[File:GettingStarted_Screenbar_Settings_Memory.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== MUI Settings ===&lt;br /&gt;
&lt;br /&gt;
MUI is the default GUI toolkit of MorphOS and its looks and behaviour can be changed in almost every aspect. Its basic philosophy is to ''offer as much freedom as possible to users by taking away as much work as possible from programmers''. A user can modify the looks of MUI programs very drastically both globally and per program. It can be done by changing single settings or by loading complete themes (presets).&lt;br /&gt;
&lt;br /&gt;
The most important thing for a new user is to understand the difference between the global settings and settings of individual programs.&lt;br /&gt;
&lt;br /&gt;
The global settings are the default settings which will apply to any program using MUI. The global settings can be changed by selecting the '''Settings-&amp;gt;MUI...''' option from the Ambient's pulldown menus or by double clicking the '''SYS:Prefs/MUI''' icon.&lt;br /&gt;
&lt;br /&gt;
Each MUI program can also have its own MUI settings which will override the global settings, but be careful when changing for example the looks of an individual program. If you decide to change the global theme later, the changes made to the individual programs might not fit the global theme anymore. The MUI settings of a program can be found on its pulldown menu or from the window's [[Fundamentals_of_MorphOS#Window_border_gadgets | popup gadget]] menu. Ambient's MUI settings are found from the '''Settings-&amp;gt;Ambient MUI...''' option in the Ambient's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Let's change a couple of options in the global MUI settings as an example. Open the global MUI settings window.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_MUI_Settings.png]]&lt;br /&gt;
&lt;br /&gt;
The default ghosting effect for buttons is a bit old-fashioned raster effect and it will look much better with just reduced visibility. Select the Buttons page and click the None option for the ghosted gadgets. The visibility can be changed with the slider below, but the default value will be fine too. You'll see the changes in real time on any MUI program, the Test button is a bit obsolete with the latest MUI. I also like to make the Active Gadgets Border a bit smaller than the original size. Click the Save button when you're satisfied.&lt;br /&gt;
: [[File:GettingStarted_MUI_Settings_Buttons.png|380px]]&lt;br /&gt;
&lt;br /&gt;
The Settings button in the top left corner opens a popup menu with options to reset the settings or load different presets.&lt;br /&gt;
&lt;br /&gt;
All MUI settings get saved to the ENVARC:MUI/ directory. If you mess too much with settings for individual programs, the last resort to revert the settings to default is to remove the corresponding settings files from that directory or restore them from a backup.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Hiding the Boot Image Partition on Macs ===&lt;br /&gt;
&lt;br /&gt;
On Macs you'll have a small HFS formatted partition which contains a few files needed to boot the system. The files are only used by [[Dictionary_of_Terms | Open Firmware]] at boot time and the user or MorphOS itself don't normally need them for anything. Open Firmware, as well as the MorphOS update wizard, can access the partition even if it's not mounted on MorphOS. If we disable the auto mounting of it, our desktop will look a bit cleaner and the crucial boot files will then be safe from accidents as well.&lt;br /&gt;
&lt;br /&gt;
Launch the [[Tools/HDConfig]] program and click on the small HFS partition. Its name should be '''DH0:''' if the system is installed with the default partition layout. Disable the '''Automatically mount partition''' option and click the '''OK''' button.&lt;br /&gt;
: [[File:GettingStarted_HDConfig1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button which is in the red area on the left side and accept the changes.&lt;br /&gt;
: [[File:GettingStarted_HDConfig2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Next time you boot the system, the partition isn't shown on the desktop. If you need to access it later for some reason, it can be mounted temporarily with the [[Tools/Mounter]] tool.&lt;br /&gt;
: [[File:GettingStarted_Ambient2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Arranging the Drive Icons ===&lt;br /&gt;
The drive icons can be dragged to a different order and then saved to their positions by selecting the '''Snapshot''' option from the right click contextual menu. If the Ram Disk icon is dragged to the leftmost position and snapshot, it will appear at that position after a reboot and unsnapshot icons appear next to it.&lt;br /&gt;
: [[File:GettingStarted_Drive_Icons.png|320px]] [[File:GettingStarted_Drive_Icons_Snapshot.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installing, Updating, and Configuring Essential Software ==&lt;br /&gt;
&lt;br /&gt;
=== Checking the Network Connection ===&lt;br /&gt;
&lt;br /&gt;
Before continuing to installing new software, let's check if your machine is properly connected to the Internet.&lt;br /&gt;
&lt;br /&gt;
Open the shell by selecting the '''Ambient-&amp;gt;New Shell...''' option from the Ambient's pulldown menus, or by pressing '''rcommand n''' keyboard combination or doubleclicking the '''SYS:Tools/MUI Shell''' icon.&lt;br /&gt;
: [[File:GettingStarted_Ambient_Menu_New_Shell.png]]&lt;br /&gt;
&lt;br /&gt;
Check the Internet connection by pinging some hostname on the Internet. Type for example '''ping www.google.com''' on the shell window. If you get replies from the host, the connection is OK and you can proceed by pressing '''CTRL C''' to quit the Ping command and closing the shell window. If you don't get any replies with time values, quit the pinging by the CTRL C combination and read the [[Configuring_Network | Configuring a Network Connection]] tutorial.&lt;br /&gt;
: [[File:GettingStarted_Ping.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Grunch ===&lt;br /&gt;
&lt;br /&gt;
[http://geit.de/eng_grunch.html Grunch] is an advanced software package manager, which can install, update, and uninstall software. It's a good starting point for new users and I'd advice everyone to check what it has to offer before visiting [[Links#File_Repositories | other sites]] for more software.&lt;br /&gt;
&lt;br /&gt;
Start Odyssey Web Browser from '''SYS:Applications/OWB/OWB''' and download Grunch from its [http://geit.de/eng_grunch.html homepage] or from the [http://morphos-files.net/find.php?find=grunch MorphOS Files] site. Save the '''Grunch.lha''' archive file to any location, for example to Work partition or to Ram Disk. The archive isn't needed after the installation.&lt;br /&gt;
: [[File:GettingStarted_OWB4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Close the browser and use Ambient to browse to the location where you saved the Grunch.lha file. If you don't see the file, click the rightmost cycle gadget on the window to show all files. Double click the archive, open the Grunch directory, and double click the '''Grunch.install''' file to start the installer script. Running an installer directly from the unpacked archive is a bit of a shortcut which might not work with all programs, but let's demonstrate it anyway. The traditional and more failproof way would be to unpack an archive file to a temporary location and then run the installer script from an unarchived directory. Read more about installing third party software [[Installing_software | here]].&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Next''' button and select the destination location. The '''System:Applications''' path is OK unless you want to keep the bundled software and 3rd party software strictly separated. In that case you could make a new Applications directory on the Work partition, for example.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Install2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After the installation has finished, browse to the location where you installed the program and double click the '''Grunch''' icon. Grunch starts, but you'll have to wait a little while it does its initial checks and updates.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Start.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Before using the program any further, check the Grunch preferences. Select the '''Settings-&amp;gt;Grunch...''' option from the pulldown menus and open the '''Miscellaneous''' tab. I'd change the '''Temporary Directory''' path to somewhere else than to your system partition. If you have enough memory, you could have it even on the Ram Disk, but a temporary directory on the Work partition would be a safe bet.&lt;br /&gt;
&lt;br /&gt;
Click the file requester button at the end of the line to browse to the wanted location. The ''':''' button shows the available volumes, and you can also create new directories from the right click contextual menu on the file requester.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You should check the '''Path''' tab next, and think twice if you want to change them from the default paths. The default paths are OK if you think that all 3rd party and bundled software can reside mixed in the same directories and if you have enough free space on the system partition. But if you like to keep 3rd party and bundled software separated and have the system directories as clean as possible, change the paths now. You could make suitable directories on the Work partition, for instance.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
When you're happy with the settings, click the Save button.&lt;br /&gt;
&lt;br /&gt;
The Grunch icon can also be dragged to a panel for quick access later.&lt;br /&gt;
: [[File:GettingStarted_Dragging_Grunch_to_Panel.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Installing Software with Grunch ===&lt;br /&gt;
==== rexxsyslib.library ====&lt;br /&gt;
The rexxsyslib.library file enables the ARexx scripting language support on your system and it should be installed as early as possible. Many programs and their features rely on a working ARexx environment. Select it from the list and click the '''Install''' button on Grunch. You may need a reboot before it'll be in use.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software1.png]]&lt;br /&gt;
&lt;br /&gt;
==== Updating OWB ====&lt;br /&gt;
MorphOS usually comes with a bit old version of the OWB browser and you should check for a newer version. Select OWB from the list and click the '''Check''' button.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software2.png]]&lt;br /&gt;
&lt;br /&gt;
You probably have an old version, so click the '''Update...''' button and wait for it to finish.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software3.png]]&lt;br /&gt;
&lt;br /&gt;
You could also change the mode to Update.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software4.png]]&lt;br /&gt;
&lt;br /&gt;
==== MPlayer ====&lt;br /&gt;
MPlayer is hands down the best video player on MorphOS, just install it. It also works as an audio player with comprehensive support for different formats.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software5.png]]&lt;br /&gt;
&lt;br /&gt;
==== PowerSDL ====&lt;br /&gt;
PowerSDL libraries are required for many software ports from other platforms. It's better to install them as well.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software6.png]]&lt;br /&gt;
&lt;br /&gt;
==== CRABUM ====&lt;br /&gt;
CRABUM lets you to customize the pulldown menus on Ambient. It's quite handy for adding some hidden but quickly available features and shortcuts. We'll need this for some later examples.&lt;br /&gt;
: [[File:GettingStarted_Grunch_Installing_Software7.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Installed Software ===&lt;br /&gt;
==== Configuring Odyssey Web Browser ====&lt;br /&gt;
Here are few examples or suggestions for the initial configuration of OWB. Do the steps you like.&lt;br /&gt;
===== Downloading More Suitable Fonts for OWB =====&lt;br /&gt;
The fonts provided with MorphOS aren't designed with web usage in mind and it's better to download certain Microsoft fonts for the browser. Luckily it's an easy job to do, because there's a downloader script included in the OWB's directory.&lt;br /&gt;
&lt;br /&gt;
Open the '''SYS:Applications/OWB''' directory and double click the '''Download Fonts''' icon. Note: if the script doesn't seem to work, try [http://www.morphos-storage.net/?page=Network/Web&amp;amp;file=Download_Fonts_for_OWB.lha this one] instead.&lt;br /&gt;
: [[File:GettingStarted_OWB1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Yes''' on the requester and wait patiently for  the downloading and installing of the fonts. The output window closes when the process is finished.&lt;br /&gt;
: [[File:GettingStarted_OWB2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
OWB initializes the fonts on the first run, but it will start much quicker next time.&lt;br /&gt;
: [[File:GettingStarted_OWB3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Making OWB to Use Its Own Screen =====&lt;br /&gt;
A browser is usually an application people want to use in a full size window and on Amigaish systems it makes sense to put it on its own screen. When used on a separate screen it leaves more space for other programs on the Ambient screen, and you don't have such a hassle when handling them all. Bringing screens to front is also a very quick operation, you'll never see any slowdowns like on other systems where you reopen full size windows from taskbars, for example.&lt;br /&gt;
&lt;br /&gt;
You could send a program to a new screen with the &amp;quot;Jump to Screen -&amp;gt; New&amp;quot; option from the window popup gadget, but it's mainly designed for temporary usage. Let's do the configuration more proper way instead.&lt;br /&gt;
&lt;br /&gt;
Launch OWB, click on the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]], and select '''MUI Settings...'''. Another way to access the MUI settings would be from the '''Settings-&amp;gt;MUI...''' pulldown menu option when OWB's window is active.&lt;br /&gt;
: [[File:GettingStarted_OWB5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the '''Screen''' page, select the '''customized public screen from MUI screen database''' option, and click the '''New...''' button.&lt;br /&gt;
&lt;br /&gt;
The Edit Screen window opens. The name field is for the screen name and the title field for the screen title text. They can be anything you want, but it's better to keep them informative. '''OWB''' would be a good screen name now and '''Odyssey Web Browser''' for the title. Check if the default screen mode is what you want. Be also sure that the '''Close automatically''' option is enabled.&lt;br /&gt;
&lt;br /&gt;
It might be a good idea to disable the '''Enhanced Display''' option, because it doesn't give that much advantage with full screen applications. Graphics memory usage will also be lower, and it might be crucial to save some graphics memory on systems with less than 128 MB memory on the graphics card. Read more about how to reduce graphics memory usage [[Tips_and_Tricks#How_to_Reduce_Graphics_Memory_Usage | here]].&lt;br /&gt;
&lt;br /&gt;
Click the '''Ok''' button on the Edit Screen window and the '''Save''' button on the MUI Settings window.&lt;br /&gt;
&lt;br /&gt;
Note: this method can be used with all MUI programs to put them on their own screens, from shell windows to small utilities, bigger applications, and games. I prefer to use the [[Applications/Showgirls|ShowGirls]] image viewer and other bigger applications on their own screens. Several MUI programs can also share the same custom screen, as it isn't limited just to a program per screen. You could for example group some network programs to one screen, and some other programs to another screen, etc.&lt;br /&gt;
: [[File:GettingStarted_OWB6.png|320px]]&lt;br /&gt;
&lt;br /&gt;
The OWB window doesn't probably have optimal size and position on the newly created screen. Right click over the [[Fundamentals_of_MorphOS#Window_border_gadgets | zoom gadget]] and select the '''Maximize''' option or if you configured the zoom gadget as suggested [[Getting_Started#Screens_and_Desktop | earlier]], click the zoom gadget twice. The maximize option leaves the screen title bar visible, but otherwise resizes the window to full screen size. Select the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets | window popup gadget]] to save the window position permanently.&lt;br /&gt;
: [[File:Tips_Zoommenu.png|top]] [[File:GettingStarted_OWB7.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Open PDF Files Automatically =====&lt;br /&gt;
OWB's MIME Types settings can be used to configure automatic actions to files of certain types. Here is an example of how to show PDF files automatically with the [[Applications/VPDF|VPDF]] application when clicked on the browser.&lt;br /&gt;
&lt;br /&gt;
Open OWB's settings from the '''Settings-&amp;gt;Preferences...''' pulldown menu option and select the '''MIME Types''' page. Click the '''Add''' button and fill in the information below like this:&lt;br /&gt;
 MIME Type: '''application''' / '''pdf'''&lt;br /&gt;
 Extension: '''pdf'''&lt;br /&gt;
 Action: '''External Viewer''', Viewer: '''SYS:Applications/VPDF/VPDF''', and the last unnamed field: '''&amp;amp;#37;f'''&lt;br /&gt;
&lt;br /&gt;
Click the '''Save''' button.&lt;br /&gt;
&lt;br /&gt;
If you now click a PDF file on a web page, the file is downloaded to a temporary location and shown on VPDF automatically.&lt;br /&gt;
: [[File:GettingStarted_OWB8.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Getting YouTube Videos to Play Better on the Browser Window =====&lt;br /&gt;
YouTube videos should play on OWB by default, but there are a thing or two to note.&lt;br /&gt;
&lt;br /&gt;
Playing videos in a small embedded window is a very CPU intensive task and not quite smooth on most systems. Moving the video playback from the embedded mode to the overlay mode helps the task hugely. This can be achieved with the YouTube Fullscreen Fix script. Videos will be shown in a nearly fullscreen window using the overlay functions and the CPU load may drop from 100&amp;amp;#37; even to 30&amp;amp;#37; on a G4 system, resulting in perfectly smooth playback of course.&lt;br /&gt;
&lt;br /&gt;
'''Download''' the latest script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js (YouTube changes its internals randomly and that's why the script on the MorphOS ISO is probably old already. Grunch also may have an old version and manual installation is highly advisable).&lt;br /&gt;
&lt;br /&gt;
Copy the downloaded script to the '''System:Applications/OWB/Scripts''' directory.&lt;br /&gt;
: [[File:GettingStarted_OWB9.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Scripts window from the '''Windows-&amp;gt;Scripts...''' pulldown menu entry on OWB.&lt;br /&gt;
: [[File:GettingStarted_OWB10.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click the '''Add''' button on the Scripts window and select the YouTube_Fullscreen_Fix.js file.&lt;br /&gt;
: [[File:GettingStarted_OWB11.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Make sure that the '''Enable''' setting is chosen and close the window. A '''restart''' of the browser is needed to activate the script, but after that you should be able to get any YouTube video to the smooth fullscreen mode by clicking the &amp;quot;fullscreen&amp;quot; or &amp;quot;large player&amp;quot; buttons on the video '''after the video playback has started'''. If you're watching a video embedded on some other external site, click the settings button instead. '''Double click''' the fullscreen video to get it to the embedded mode again.&lt;br /&gt;
: [[File:GettingStarted_OWB12.png|320px]]&lt;br /&gt;
&lt;br /&gt;
===== Content Blocking and YouTube =====&lt;br /&gt;
If you have enabled the Content Blocking (AdBlock) option on the OWB settings, YouTube videos with ads will also get blocked. You can make a rule to the content blocking settings to allow those videos to be shown.&lt;br /&gt;
&lt;br /&gt;
Open '''Windows-&amp;gt;Content Blocking...''' from OWB's pulldown menus, click the '''Add''' button, and write '''youtube.com''' to the Rule line, and close the window.&lt;br /&gt;
: [[File:OWB_ContentBlockingYT.png]]&lt;br /&gt;
&lt;br /&gt;
If you have any other problems with the YouTube playback, check the [[Tips_and_Tricks#Problems_with_YouTube_Videos|Tips and Tricks]] page for more information.&lt;br /&gt;
&lt;br /&gt;
===== Configuring Fonts =====&lt;br /&gt;
&lt;br /&gt;
Browsers come with font settings. However, these settings are often neglected. Web developer has at least three options for selecting a font which would be displayed by default on your browser screen. &lt;br /&gt;
It can be a generic font, &amp;quot;hand picked&amp;quot; local font-family, or on-the-fly downloaded web font. Nevertheless the user still has the choice which font he or she actually wants to use. Reasons: privacy, security, speed, aesthetic.&lt;br /&gt;
&lt;br /&gt;
MorphOS is bundled with True Type, PostScript and Amiga Bitmap fonts.&lt;br /&gt;
OWB uses fontconfig for font handling. Fonts are cached whenever a change in font directories is detected.&lt;br /&gt;
If you want to use your fonts exclusively - fonts.conf should only use the path where you store the fonts (for example '''SYS:Fonts/_ttf''').&lt;br /&gt;
&lt;br /&gt;
Fontconfig is a library providing font configuration, customization and application access. It uses freetype library which supports plenty of font formats (excluding Amiga Bitmap fonts).&lt;br /&gt;
Presets are stored in the '''MOSSYS:Fontconfig/conf.avail''' directory.&lt;br /&gt;
&lt;br /&gt;
'''FONTS:Fontconfig/fonts.conf''' (default font dirs)&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;dir&amp;gt;SYS:Fonts/_pcf&amp;lt;/dir&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;dir&amp;gt;SYS:Fonts/_pfb&amp;lt;/dir&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;dir&amp;gt;SYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pcf&amp;lt;/dir&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;dir&amp;gt;MOSSYS:Fonts/_pfb&amp;lt;/dir&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;dir&amp;gt;MOSSYS:Fonts/_ttf&amp;lt;/dir&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Example settings:'''&lt;br /&gt;
&lt;br /&gt;
&amp;lt;?xml&amp;amp;nbsp;version=&amp;quot;1.0&amp;quot;?&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;!DOCTYPE&amp;amp;nbsp;fontconfig&amp;amp;nbsp;SYSTEM&amp;amp;nbsp;&amp;quot;fonts.dtd&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;fontconfig&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;nowiki&amp;gt;&amp;lt;!--&amp;lt;/nowiki&amp;gt;&amp;amp;nbsp;Load&amp;amp;nbsp;local&amp;amp;nbsp;system&amp;amp;nbsp;customization&amp;amp;nbsp;file&amp;amp;nbsp;--&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;include&amp;amp;nbsp;ignore_missing=&amp;quot;yes&amp;quot;&amp;gt;local.conf&amp;lt;/include&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;/fontconfig&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''FONTS:fontconfig/local.conf''' (turns off antialias for font sizes smaller than 16 and disables autohint)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;?xml&amp;amp;nbsp;version=&amp;quot;1.0&amp;quot;?&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;!DOCTYPE&amp;amp;nbsp;fontconfig&amp;amp;nbsp;SYSTEM&amp;amp;nbsp;&amp;quot;fonts.dtd&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;!--&amp;lt;/nowiki&amp;gt;&amp;amp;nbsp;/etc/fonts/local.conf&amp;amp;nbsp;file&amp;amp;nbsp;for&amp;amp;nbsp;local&amp;amp;nbsp;customizations&amp;amp;nbsp;--&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;fontconfig&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;match&amp;amp;nbsp;target=&amp;quot;font&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;edit&amp;amp;nbsp;name=&amp;quot;antialias&amp;quot;&amp;amp;nbsp;mode=&amp;quot;assign&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/edit&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/match&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;match&amp;amp;nbsp;target=&amp;quot;font&amp;quot;&amp;amp;nbsp;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;test&amp;amp;nbsp;name=&amp;quot;size&amp;quot;&amp;amp;nbsp;qual=&amp;quot;any&amp;quot;&amp;amp;nbsp;compare=&amp;quot;more&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/test&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;edit&amp;amp;nbsp;name=&amp;quot;antialias&amp;quot;&amp;amp;nbsp;mode=&amp;quot;assign&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/edit&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/match&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;match&amp;amp;nbsp;target=&amp;quot;font&amp;quot;&amp;amp;nbsp;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;test&amp;amp;nbsp;name=&amp;quot;pixelsize&amp;quot;&amp;amp;nbsp;qual=&amp;quot;any&amp;quot;&amp;amp;nbsp;compare=&amp;quot;more&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;double&amp;gt;16&amp;lt;/double&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/test&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;edit&amp;amp;nbsp;name=&amp;quot;antialias&amp;quot;&amp;amp;nbsp;mode=&amp;quot;assign&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;bool&amp;gt;true&amp;lt;/bool&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/edit&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/match&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;match&amp;amp;nbsp;target=&amp;quot;font&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;edit&amp;amp;nbsp;name=&amp;quot;autohint&amp;quot;&amp;amp;nbsp;mode=&amp;quot;assign&amp;quot;&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;bool&amp;gt;false&amp;lt;/bool&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/edit&amp;gt;&amp;lt;br/&amp;gt;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;amp;nbsp;&amp;lt;/match&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;br/&amp;gt;&amp;lt;/fontconfig&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Blocking fonts'''&lt;br /&gt;
&lt;br /&gt;
In OWB, go to '''Settings-&amp;gt;Fonts''' and choose default fonts and sizes.&lt;br /&gt;
&lt;br /&gt;
To disable remote web fonts this line needs to be added to its filter '''SYS:Applications/OWB/Conf/blocked.prefs''':&lt;br /&gt;
&lt;br /&gt;
/\.ttf|\.otf|\.woff|\.woff2\?/&lt;br /&gt;
&lt;br /&gt;
A specific font can be whitelisted too:&lt;br /&gt;
&lt;br /&gt;
@@/*actually-nice-font.ttf&lt;br /&gt;
&lt;br /&gt;
This isn't ideal. OWB will try block anything_not_whitelisted.ttf, even if you look for a nicefont.ttf in Google Search.&lt;br /&gt;
&lt;br /&gt;
==== Configuring MPlayer ====&lt;br /&gt;
===== General Options =====&lt;br /&gt;
The default configuration of MPlayer is quite fine, but here are a few options I like to set myself. Start MPlayer in the GUI mode by double clicking the GMPlayer icon in the MPlayer directory. There's just one MPlayer executable, but two icons with different [[Fundamentals_of_MorphOS#Icon_Tool_Types|tooltypes]] to start the program with or without the GUI mode.&lt;br /&gt;
&lt;br /&gt;
With default options MPlayer scales the played video to fit the current window dimensions which typically leaves big empty borders around the video. To get the window dimensions to change with the video dimensions, select the '''Video-&amp;gt;Window Dimension-&amp;gt;100&amp;amp;#37;''' option, and '''Settings-&amp;gt;Save''' to save it as a default setting.&lt;br /&gt;
: [[File:GettingStarted_MPlayer.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Open the Preferences window by selecting the '''Settings-&amp;gt;Preferences...''' option from MPlayer's pulldown menus. There are some settings to consider.&lt;br /&gt;
&lt;br /&gt;
The Audio Driver has two audio output options for AHI to choose from. The default '''ahi''' option outputs the audio through the ''Music Unit'', which gives the best audio quality, but blocks simultaneous audio from any other sources. The '''ahi_dev''' option uses the device mode which can be shared with the other sources, but it results in a slight decrease in the audio quality. So, if you want to be able to watch videos while some other program, like a music player, would still continue with audio output, select the '''ahi_dev''' option.&lt;br /&gt;
&lt;br /&gt;
If you don't like any usage data gathering, disable the '''Remember last visited path''' option :)&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Preferences.png]]&lt;br /&gt;
&lt;br /&gt;
===== Setting MPlayer as the Default Player on Ambient  =====&lt;br /&gt;
MorphOS doesn't have any default player for videos and double clicking a video file from Ambient results in an error requester. MPlayer can be set as the default video player by editing the Ambient MIME type settings.&lt;br /&gt;
&lt;br /&gt;
Open the '''Ambient Settings''' window and the '''Mime''' page. With the built-in MIME editor you can add different kinds of actions for different file formats or classes. Let's add MPlayer as the default player for all video files, not just for some individual video formats.&lt;br /&gt;
&lt;br /&gt;
Select '''video''' from the right-hand side list tree and click the '''Edit''' button. Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
&lt;br /&gt;
In the Action Editor window type a name for the action, for example '''Play''', and click the '''Add''' button on that window too.&lt;br /&gt;
&lt;br /&gt;
Change the AmigaDOS command to '''Run &amp;gt;NIL: SYS:Applications/MPlayer/MPlayer -gui 1 &amp;amp;#37;sp''' (change the path to the MPlayer executable if you have it in a different location) and change the Event type to '''DoubleClick'''. Note: the ''-gui 1'' option, which starts MPlayer in the GUI mode, has to be written in lower case, having it in upper case doesn't work!&lt;br /&gt;
: [[File:GettingStarted_MPlayer_Adding_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Click '''Ok''', '''Ok''', and '''Save''' buttons.&lt;br /&gt;
&lt;br /&gt;
If you now double click a video file in Ambient, it gets played on MPlayer. You can also see the Play option in the contextual menu when right clicking the video file.&lt;br /&gt;
: [[File:GettingStarted_MPlayer2.png|320px]] [[File:GettingStarted_MPlayer_Working_MIME.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You can add several actions as contextual menu events if you want to have more options for opening videos. Only imagination is the limit, and you can for example have contextual menu entries to start MPlayer playback with filters skipped (use the ''-lavdopts skiploopfilter=all'' option to speed up the video playback a little) and have an option to convert the video with mencoder etc.&lt;br /&gt;
: [[File:GettingStarted_ActionEditor2.png|230px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Creating Menus with CRABUM ====&lt;br /&gt;
&lt;br /&gt;
You can add custom pulldown menus to Ambient with ARexx scripts created by the CRABUM program. It's a good way to launch programs or scripts which you don't want to have on panels. Installation of [[Getting_Started#rexxsyslib.library|rexxsyslib.library]] is required.&lt;br /&gt;
&lt;br /&gt;
Let's create an Edit menu with options to edit different system startup scripts. Double click the CRABUM icon from the SYS:Utilities/CRABUM directory if you installed it with the default options.&lt;br /&gt;
&lt;br /&gt;
# Click the '''Menu''' button to add a new menu and change its title to '''Edit'''.&lt;br /&gt;
# Click the '''Item''' button to add a new item under the created menu.&lt;br /&gt;
# Type '''User-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-startup''' to the AmigaDOS command line. &amp;quot;Run &amp;gt;NIL:&amp;quot; starts the Ed program as a background process and it won't block Ambient while it is running.&lt;br /&gt;
# Create an another item by clicking the '''Item''' button.&lt;br /&gt;
# Type '''User-network-startup''' to the title field and '''Run &amp;gt;NIL: Ed S:user-network-startup''' to the AmigaDOS command line.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM1.png|320px]]&lt;br /&gt;
# Click the '''Save''' button to save the resulting ARexx script.&lt;br /&gt;
# If you save the file to the SYS:WBStartup drawer, it will be launched automatically at boot time. Enter a suitable name for the file, for example '''Edit-menu'''. Click the '''Ok''' button.&amp;lt;br /&amp;gt;[[File:GettingStarted_CRABUM2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
After a reboot (or doubleclicking of the file) you'll have the new Edit menu on the Ambient pulldown menus and you can easily open the system files for editing.&lt;br /&gt;
: [[File:GettingStarted_CRABUM3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== More Configuring ==&lt;br /&gt;
=== Synchronizing the Clock with an Internet Time Server ===&lt;br /&gt;
The system clock can be synchronized manually from the MorphOS Preferences application by clicking the '''Set date and time using the Internet''' button in the Time preferences.&lt;br /&gt;
: [[File:MorphOS_Preferences_Time.png|320px]]&lt;br /&gt;
&lt;br /&gt;
There's also the [[Shell_Commands/SetClockNTP|SetClockNTP]] shell command which can be launched manually or automatically at boot time. To synchronize the time every time the system starts edit the '''S:user-network-startup''' file and remove the semi-colon from the SetClockNTP line.&lt;br /&gt;
&lt;br /&gt;
To edit the S:user-network-startup file open the shell (or the Execute Command prompt) and type '''Ed S:user-network-startup''', or open the System partition, select the '''All Files''' mode, browse to the '''S''' directory and select the '''Edit...''' option from the right click contextual menu. Or if you configured the Edit menu with CRABUM earlier, use it now.&lt;br /&gt;
: [[File:GettingStarted_Enable_SetClockNTP.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Configuring the Shell ===&lt;br /&gt;
==== Editing the Shell-startup file ====&lt;br /&gt;
The shell can be customized with the shell-startup file, but by default the file is only found in a MorphOS system directory where the user shouldn't do any modifications. It must be copied to a user directory first to make any changes to it. Open a new shell window and type '''Copy MOSSYS:S/shell-startup SYS:S/shell-startup''', and then edit it for example with the '''Ed SYS:S/shell-startup''' command. The shell-startup file is executed every time a new shell window is opened.&lt;br /&gt;
: [[File:GettingStarted_shell-startup.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Adding Paths ====&lt;br /&gt;
There are some useful shell commands around the installed system which aren't in the system's search path and thus you'll have to enter their complete paths when using them. Adding their locations to the search path allows them to be run just by their names, which is much more convenient.&lt;br /&gt;
&lt;br /&gt;
Here are few suggestions to add to the '''SYS:S/shell-startup''' file (remember the previous step first!). Or if you want them to be available globally on all occasions, they can be added to the '''S:user-startup''' file instead.&lt;br /&gt;
* '''Path SYS:Applications/RemoteShell/Files ADD''' adds SSH related commands like scp, sftp, ssh, etc to the search path. Note: use the [[Applications/RemoteShell|Remote Shell]] application for regular SSH sessions, because it supports arrow keys and other things better.&lt;br /&gt;
* '''Path SYS:Applications/OWB/Datas ADD''' adds wget to the search path.&lt;br /&gt;
* '''Path SYS:Applications/MPlayer ADD''' adds MPlayer and mencoder to the search path if you have installed MPlayer. Change the path if you have installed it elsewhere.&lt;br /&gt;
&lt;br /&gt;
==== Configuring the GUI ====&lt;br /&gt;
There are many buttons and hotkeys to add to the shell window besides the default ones. Check the preferences by selecting the '''Settings-&amp;gt;Edit Prefs...''' option from the Shell's pulldown menus.&lt;br /&gt;
&lt;br /&gt;
Available functions can be dragged to '''Hotkeys''' or '''Buttons''' lists and the changes are seen in real time in the shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences2.png|320px]]&lt;br /&gt;
&lt;br /&gt;
You may also want to set the default window size and position for new shell windows on the '''Settings''' tab. Click the '''Get from window''' button to get values from the current shell window.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences1.png|320px]]&lt;br /&gt;
&lt;br /&gt;
Remember to save the modifications in the '''Settings''' menu.&lt;br /&gt;
: [[File:GettingStarted_Shell_Preferences3.png|320px]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Setting Jukebox as the Default Player for MP3 Files ===&lt;br /&gt;
If you double click an MP3 file in an Ambient window, it is played with the very simple internal player. Here are two solutions to change the default player to the more advanced [[Utilities/Jukebox|Jukebox]] music player. Ambient's internal player is still left to the context menu as an option.&lt;br /&gt;
==== Simple Solution ====&lt;br /&gt;
A simple solution is just to create a new mpeg audio MIME type definition which just launches the Jukebox player with the double clicked filename as an argument.&lt;br /&gt;
# Open the Mime page in the Ambient settings, select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''Run &amp;gt;NIL: SYS:Utilities/Jukebox &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and you should see this in the MIME Editor window.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Save''' buttons. If you double click an MP3 file now, Jukebox starts and plays the clicked file. There are also two entires in the right click contextual menu and the option which is used for the double click action is written in bold.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg4.png|320px]]&lt;br /&gt;
&lt;br /&gt;
==== Advanced Solution ====&lt;br /&gt;
An advanced solution is to use the third party [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script. It will give more flexible options to add files to Jukebox, and we'll learn how to add submenus into context menus. There are shortcuts to install the script if you read the documentation in the archive, but let's do this manually to learn the configuration method better. It will be helpful in the future when configuring any other filetypes.&lt;br /&gt;
&lt;br /&gt;
# Download the script archive from [http://aminet.net/package/mus/play/JukeboxAdder Aminet] or from [http://morphos-files.net/find.php?find=jukeboxadder MorphOS Files].&lt;br /&gt;
# Copy the '''jukeboxadder.lua''' file from the archive to the '''SYS:S/''' directory.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder1.png|320px]]&lt;br /&gt;
# Open the '''Mime''' page in the '''Ambient settings''', select '''audio-&amp;gt;mpeg''' from the list tree, and click '''Edit'''.&lt;br /&gt;
# Select '''Play...''' and click '''Edit'''.&lt;br /&gt;
# Change '''Event type''' to '''Menu''' and click the '''Ok''' button. Ambient's internal player is now left as an optional context menu entry only.&amp;lt;br /&amp;gt;[[File:GettingStarted_Ambient_Settings_Mime_mpeg1.png|320px]]&lt;br /&gt;
# Click the '''Add''' button on the MIME Editor window.&lt;br /&gt;
# Type '''Play in Jukebox...''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua PLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''DoubleClick'''.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder2.png|320px]]&lt;br /&gt;
# Click '''Ok''' and then click '''Add''' again in the MIME Editor window to create more ways to add files to Jukebox from the context menus.&lt;br /&gt;
# Type '''Add to Jukebox''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command to '''MOSSYS:C/LuaX S:jukeboxadder.lua ADD &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string. This will create a submenu named ''Jukebox'' in the context menu and place the new ''Add to Jukebox'' option there.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder3.png|320px]]&lt;br /&gt;
# Click '''Ok''' and '''Add''' once again to create the last entry.&lt;br /&gt;
# Type '''Add to Jukebox and Play''' to the name string.&lt;br /&gt;
# Click the '''Add''' button and specify the '''AmigaDOS''' command as '''MOSSYS:C/LuaX S:jukeboxadder.lua ADDPLAY &amp;amp;#37;sp'''&lt;br /&gt;
# Set the '''Event type''' to '''Menu''', enable the '''Sort by parent''' option, and type '''Jukebox''' to the '''Parent Menu Name''' string.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder4.png|320px]]&lt;br /&gt;
# Click '''Ok''', '''Ok''', and '''Save'''. Now you can see more options in the context menu for MP3 files and double clicking will always clear the previous songs and play the new song immediately.&amp;lt;br /&amp;gt;[[File:GettingStarted_JukeboxAdder5.png|320px]]&lt;br /&gt;
&lt;br /&gt;
It is also possible to add the same functionality for context menus of directories if you want to be able to add whole directories to Jukebox at once. There's a special '''internal -&amp;gt; x-morphos-globalaction-directory''' MIME type which can be used to add context menu entries for all directories. Repeat the previous steps (6-18) for it, but make all '''Event types''' to use the '''Menu''' option (in step 9 too).&lt;br /&gt;
: [[File:GettingStarted_JukeboxAdder6.png|320px]] [[File:GettingStarted_JukeboxAdder7.png|320px]] [[File:GettingStarted_JukeboxAdder8.png|320px]]&lt;/div&gt;</summary>
		<author><name>Korni</name></author>	</entry>

	</feed>