MorphOS Library - User contributions [en]

Hardware Compatibility

2024-02-14T08:02:51Z

NewSense: /* Game Controllers */

<div id="hardwareCompatibility">

== Official Information ==
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]].

== User Provided Reports ==
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&forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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&forum=11 let us know] so correction(s) can be made.

=== Game Controllers ===
<table style="width:100%">
<tr><th class="type">USB Device</th><th class="driver">USB driver</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>8bitdo SFC30 Pro Controller</td><td>hid</td><td>3.11</td></tr>
<tr><td>8bitdo SN30 Pro Controller</td><td>hid, xbox360</td><td>3.11</td><td>wired</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=34 BIMONK Wired Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=70 BIMONK Wireless Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>Logitech Rumble Pad wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=85 Mcbazel Dobe Mini Arcade Stick]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.onyxsoft.se/joydivision.html OnyxSoft JoyDivision] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>[https://www.retronicdesign.com/en/ Retronic Design] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>Saitek P380 Dual Analog wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td style="color:red;">Sony Dualshock 3 (PS3)</td><td>-</td><td>-</td><td>not supported</td></tr>
<tr><td>Sony Dualshock 4 (PS4)</td><td>xbox360</td><td>3.10</td></tr>
<tr><td>Speedlink Competition Pro USB</td><td>hid</td><td>3.11</td></tr>
<tr><td>Speedlink Xeox Gamepad</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)</td><td>hid</td><td>3.15</td></tr>
<tr><td>Thrustmaster 360 Modena Pro Racing Wheel</td><td>hid</td><td>3.11</td><td>needs some setup for the ranges from the Poseidon prefs</td></tr>
<tr><td>Xbox 360 wired and wireless pads</td><td>xbox360</td><td>3.11</td><td>wireless supported via PC adapter</td></tr>
<tr><td>Xbox One gamepad</td><td>xbox360</td><td>3.11</td><td>wired only</td></tr>
<tr><td>[https://www.marvo-tech.com/products/gt-016-wired-gaming-controller Marvo Scorpion GT-016 Joypad]</td><td>hid</td><td>3.18</td><td>wired,Dual-Analog, USB2 (PC,Android & PS3)<td></tr>
</table>

=== Keyboards ===
<table style="width:100%;"><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Apple A1016 Wireless BlueTooth</td><td>3.10</td><td>①</td></tr>
<tr><td>Apple Magic Keyboard (Version 1)</td><td>3.13</td><td>①</td></tr>
<tr><td>Cooler Master MS210/MK110</td><td>3.13</td><td>No software needed for full RGB control and Fn multimedia keys do work out of the box</td></tr>
<tr><td>Ducky Zero Keyboard DK2108SZ</td><td>3.10</td><td></td></tr>
<tr><td>IBM SK-8815 Corded USB Keyboard</td><td>3.15</td><td></td></tr>
<tr><td>Logitech UltraX Premium</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Wired Keyboard 600</td><td>3.13</td><td>Model X880609-600</td></tr>
<tr><td>Microsoft Wireless 900 Keyboard</td><td>3.13</td><td>Mouse+kb combo</td></tr>
<tr><td>Rapoo E6300 Ultra-Slim BT keyboard for iPad</td><td>3.11</td><td>①</td></tr>
<tr><td>Rapoo E9050 Wireless Compact Ultra-Slim Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Rapoo E2710 Wireless Nano-USB Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Xenta Super Compact Black Wired Keyboard (RK 107)</td><td>3.13</td><td></td></tr>
</table>
① requires a machine which supports paired BT input devices, like Mac mini

=== Mice ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>A-Eon Technology MX-1000-1</td><td>3.13</td><td></td></tr>
<tr><td>Dacota Gaming Serpent Mouse</td><td>3.15</td><td>Wired, 809024</td></tr>
<tr><td>[https://www.logitech.com/en-us/products/mice/m100-usb-mouse.910-001601.html Logitech M100 Optical Corded Mouse]</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M180</td><td>3.11</td><td></td></tr>
<tr><td>Logitech M185</td><td>3.10</td><td></td></tr>
<tr><td>Logitech M190</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M220 Silent</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M330 Silent</td><td>3.14</td><td></td></tr>
<tr><td>Logitech T-RB22 Wireless Trackball</td><td>3.11</td><td></td></tr>
<tr><td>Logitech G203</td><td>3.10</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Labtec Optical Mouse 800</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Compact Optical Mouse 500</td><td>3.14</td><td></td></tr>
<tr><td>Microsoft Trackball Explorer v1.0</td><td>3.11</td><td>PS2>USB adapter required</td></tr>
<tr><td>Microsoft Wireless Mouse 900</td><td>3.14</td><td>Mouse+kb combo</td></tr>
<tr><td style="color:red;">Microsoft Wireless Mouse 4000</td><td>3.13</td><td>Not working</td></tr>
<tr><td>Razer Viper Mini</td><td>3.15</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Sharkoon Skiller SGM2</td><td>3.13</td><td>No software needed for RGB and DPI settings, side buttons don't work</td></tr>
<tr><td>Targus AMU3102EU</td><td>3.10</td><td></td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=82 TENMOS K6 Wireless Gaming Mouse]</td><td>3.15</td><td></td></tr>
</table>

=== MIDI Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>Yamaha PSR-433 keyboard</td><td>3.14</td><td></td></tr>
</table>

=== Networking ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>TL-WR702N Nano Router</td><td></td><td></td></tr>
<tr><td>TL-WR802N Nano Router</td><td></td><td></td></tr>
</table>

=== Printers ===
<table><tr><th>Model</th><th class="os">OS</th><th>TurboPrint (Printer) driver</th><th>PostScript (Printers) driver</th><th class="comments">Comments</th></tr>
<tr><td>HP 2500 Color LaserJet</td><td>3.11</td><td></td><td>[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]</td><td>[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]</td></tr>
<tr><td>Konica Minolta Magicolor 4650</td><td>3.11</td><td></td><td>M4650PX.ppd</td><td></td></tr>
<tr><td>Lexmark E342n</td><td>3.11</td><td>HP_LaserJet5series</td><td>[http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD]</td><td></td></tr>
<tr><td>Xerox 3225 Workcentre</td><td>3.11</td><td></td><td></td><td>Reported to work with PS</td></tr>
<tr><td>HP Color LaserJet MFP M274n</td><td>3.15</td><td></td><td>hp-color_laserjet_mfp_m274-ps.ppd</td></tr>
</table>

=== Scanners ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Epson Perfection 1640SU</td><td>3.11</td><td>Including recent support for its ADF (Automatic Document Feeder).</td></tr>
</table>

=== Storage ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.amazon.co.uk/Hama-00055348-35in1-Multi-Reader/dp/B000IH1W20?th=1 HAMA USB 2.0 Card Reader 35 in 1]</td><td></td><td></td></tr>
</table>

=== USB Audio Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th>Output</th><th>Input</th><th class="comments">Comments</th></tr>
<tr><td>"[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card</td><td>3.10</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[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]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>C-Media soundcard</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>Corsair Void Elite Surround adapter/headset</td><td>3.14</td><td>OK</td><td>No</td><td>Headset with 3.5mm jack and a USB adapter. Analog volume control.</td></tr>
<tr><td>Corsair Void RGB Elite headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>FX-Audio- DAC-X3</td><td>3.12</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Griffin iMic</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>[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]</td><td>3.14</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Logitech H540 headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>Sony PlayStation Gold 7.1 headset</td><td>3.13</td><td>OK</td><td>Untested</td><td>Works in stereo.</td></tr>
<tr><td>[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]</td><td>3.11</td><td>OK</td><td>Untested</td><td>Only front output tested</tD></tr>
<tr><td>Steelseries Arctis 7 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>Turtle Beach Stealth 520 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
</table>

</div>

Hardware Compatibility

2024-02-14T08:02:03Z

NewSense: /* Game Controllers */

<div id="hardwareCompatibility">

== Official Information ==
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]].

== User Provided Reports ==
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&forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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&forum=11 let us know] so correction(s) can be made.

=== Game Controllers ===
<table style="width:100%">
<tr><th class="type">USB Device</th><th class="driver">USB driver</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>8bitdo SFC30 Pro Controller</td><td>hid</td><td>3.11</td></tr>
<tr><td>8bitdo SN30 Pro Controller</td><td>hid, xbox360</td><td>3.11</td><td>wired</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=34 BIMONK Wired Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=70 BIMONK Wireless Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>Logitech Rumble Pad wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=85 Mcbazel Dobe Mini Arcade Stick]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.onyxsoft.se/joydivision.html OnyxSoft JoyDivision] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>[https://www.retronicdesign.com/en/ Retronic Design] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>Saitek P380 Dual Analog wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td style="color:red;">Sony Dualshock 3 (PS3)</td><td>-</td><td>-</td><td>not supported</td></tr>
<tr><td>Sony Dualshock 4 (PS4)</td><td>xbox360</td><td>3.10</td></tr>
<tr><td>Speedlink Competition Pro USB</td><td>hid</td><td>3.11</td></tr>
<tr><td>Speedlink Xeox Gamepad</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)</td><td>hid</td><td>3.15</td></tr>
<tr><td>Thrustmaster 360 Modena Pro Racing Wheel</td><td>hid</td><td>3.11</td><td>needs some setup for the ranges from the Poseidon prefs</td></tr>
<tr><td>Xbox 360 wired and wireless pads</td><td>xbox360</td><td>3.11</td><td>wireless supported via PC adapter</td></tr>
<tr><td>Xbox One gamepad</td><td>xbox360</td><td>3.11</td><td>wired only</td></tr>
<tr><td>[https://www.marvo-tech.com/products/gt-016-wired-gaming-controller Marvo Scorpion GT-016 Joypad]</td><td>hid</td><td>3.18</td><td>wired,Dual-Analog,USB2 (PC,Android & PS3)<td></tr>
</table>

=== Keyboards ===
<table style="width:100%;"><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Apple A1016 Wireless BlueTooth</td><td>3.10</td><td>①</td></tr>
<tr><td>Apple Magic Keyboard (Version 1)</td><td>3.13</td><td>①</td></tr>
<tr><td>Cooler Master MS210/MK110</td><td>3.13</td><td>No software needed for full RGB control and Fn multimedia keys do work out of the box</td></tr>
<tr><td>Ducky Zero Keyboard DK2108SZ</td><td>3.10</td><td></td></tr>
<tr><td>IBM SK-8815 Corded USB Keyboard</td><td>3.15</td><td></td></tr>
<tr><td>Logitech UltraX Premium</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Wired Keyboard 600</td><td>3.13</td><td>Model X880609-600</td></tr>
<tr><td>Microsoft Wireless 900 Keyboard</td><td>3.13</td><td>Mouse+kb combo</td></tr>
<tr><td>Rapoo E6300 Ultra-Slim BT keyboard for iPad</td><td>3.11</td><td>①</td></tr>
<tr><td>Rapoo E9050 Wireless Compact Ultra-Slim Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Rapoo E2710 Wireless Nano-USB Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Xenta Super Compact Black Wired Keyboard (RK 107)</td><td>3.13</td><td></td></tr>
</table>
① requires a machine which supports paired BT input devices, like Mac mini

=== Mice ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>A-Eon Technology MX-1000-1</td><td>3.13</td><td></td></tr>
<tr><td>Dacota Gaming Serpent Mouse</td><td>3.15</td><td>Wired, 809024</td></tr>
<tr><td>[https://www.logitech.com/en-us/products/mice/m100-usb-mouse.910-001601.html Logitech M100 Optical Corded Mouse]</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M180</td><td>3.11</td><td></td></tr>
<tr><td>Logitech M185</td><td>3.10</td><td></td></tr>
<tr><td>Logitech M190</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M220 Silent</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M330 Silent</td><td>3.14</td><td></td></tr>
<tr><td>Logitech T-RB22 Wireless Trackball</td><td>3.11</td><td></td></tr>
<tr><td>Logitech G203</td><td>3.10</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Labtec Optical Mouse 800</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Compact Optical Mouse 500</td><td>3.14</td><td></td></tr>
<tr><td>Microsoft Trackball Explorer v1.0</td><td>3.11</td><td>PS2>USB adapter required</td></tr>
<tr><td>Microsoft Wireless Mouse 900</td><td>3.14</td><td>Mouse+kb combo</td></tr>
<tr><td style="color:red;">Microsoft Wireless Mouse 4000</td><td>3.13</td><td>Not working</td></tr>
<tr><td>Razer Viper Mini</td><td>3.15</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Sharkoon Skiller SGM2</td><td>3.13</td><td>No software needed for RGB and DPI settings, side buttons don't work</td></tr>
<tr><td>Targus AMU3102EU</td><td>3.10</td><td></td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=82 TENMOS K6 Wireless Gaming Mouse]</td><td>3.15</td><td></td></tr>
</table>

=== MIDI Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>Yamaha PSR-433 keyboard</td><td>3.14</td><td></td></tr>
</table>

=== Networking ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>TL-WR702N Nano Router</td><td></td><td></td></tr>
<tr><td>TL-WR802N Nano Router</td><td></td><td></td></tr>
</table>

=== Printers ===
<table><tr><th>Model</th><th class="os">OS</th><th>TurboPrint (Printer) driver</th><th>PostScript (Printers) driver</th><th class="comments">Comments</th></tr>
<tr><td>HP 2500 Color LaserJet</td><td>3.11</td><td></td><td>[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]</td><td>[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]</td></tr>
<tr><td>Konica Minolta Magicolor 4650</td><td>3.11</td><td></td><td>M4650PX.ppd</td><td></td></tr>
<tr><td>Lexmark E342n</td><td>3.11</td><td>HP_LaserJet5series</td><td>[http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD]</td><td></td></tr>
<tr><td>Xerox 3225 Workcentre</td><td>3.11</td><td></td><td></td><td>Reported to work with PS</td></tr>
<tr><td>HP Color LaserJet MFP M274n</td><td>3.15</td><td></td><td>hp-color_laserjet_mfp_m274-ps.ppd</td></tr>
</table>

=== Scanners ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Epson Perfection 1640SU</td><td>3.11</td><td>Including recent support for its ADF (Automatic Document Feeder).</td></tr>
</table>

=== Storage ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.amazon.co.uk/Hama-00055348-35in1-Multi-Reader/dp/B000IH1W20?th=1 HAMA USB 2.0 Card Reader 35 in 1]</td><td></td><td></td></tr>
</table>

=== USB Audio Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th>Output</th><th>Input</th><th class="comments">Comments</th></tr>
<tr><td>"[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card</td><td>3.10</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[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]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>C-Media soundcard</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>Corsair Void Elite Surround adapter/headset</td><td>3.14</td><td>OK</td><td>No</td><td>Headset with 3.5mm jack and a USB adapter. Analog volume control.</td></tr>
<tr><td>Corsair Void RGB Elite headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>FX-Audio- DAC-X3</td><td>3.12</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Griffin iMic</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>[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]</td><td>3.14</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Logitech H540 headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>Sony PlayStation Gold 7.1 headset</td><td>3.13</td><td>OK</td><td>Untested</td><td>Works in stereo.</td></tr>
<tr><td>[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]</td><td>3.11</td><td>OK</td><td>Untested</td><td>Only front output tested</tD></tr>
<tr><td>Steelseries Arctis 7 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>Turtle Beach Stealth 520 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
</table>

</div>

Hardware Compatibility

2024-02-14T07:56:05Z

NewSense: /* Game Controllers */

<div id="hardwareCompatibility">

== Official Information ==
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]].

== User Provided Reports ==
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&forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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&forum=11 let us know] so correction(s) can be made.

=== Game Controllers ===
<table style="width:100%">
<tr><th class="type">USB Device</th><th class="driver">USB driver</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>8bitdo SFC30 Pro Controller</td><td>hid</td><td>3.11</td></tr>
<tr><td>8bitdo SN30 Pro Controller</td><td>hid, xbox360</td><td>3.11</td><td>wired</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=34 BIMONK Wired Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=70 BIMONK Wireless Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>Logitech Rumble Pad wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=85 Mcbazel Dobe Mini Arcade Stick]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.onyxsoft.se/joydivision.html OnyxSoft JoyDivision] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>[https://www.retronicdesign.com/en/ Retronic Design] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>Saitek P380 Dual Analog wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td style="color:red;">Sony Dualshock 3 (PS3)</td><td>-</td><td>-</td><td>not supported</td></tr>
<tr><td>Sony Dualshock 4 (PS4)</td><td>xbox360</td><td>3.10</td></tr>
<tr><td>Speedlink Competition Pro USB</td><td>hid</td><td>3.11</td></tr>
<tr><td>Speedlink Xeox Gamepad</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)</td><td>hid</td><td>3.15</td></tr>
<tr><td>Thrustmaster 360 Modena Pro Racing Wheel</td><td>hid</td><td>3.11</td><td>needs some setup for the ranges from the Poseidon prefs</td></tr>
<tr><td>Xbox 360 wired and wireless pads</td><td>xbox360</td><td>3.11</td><td>wireless supported via PC adapter</td></tr>
<tr><td>Xbox One gamepad</td><td>xbox360</td><td>3.11</td><td>wired only</td></tr>
<tr><td>[https://www.marvo-tech.com/products/gt-016-wired-gaming-controller Marvo Scorpion GT-016 Joypad]</td><td>hid</td><td>3.18</td><td>wired, Dual Analog USB2 (PC, Android & PS3)<td></tr>
</table>

=== Keyboards ===
<table style="width:100%;"><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Apple A1016 Wireless BlueTooth</td><td>3.10</td><td>①</td></tr>
<tr><td>Apple Magic Keyboard (Version 1)</td><td>3.13</td><td>①</td></tr>
<tr><td>Cooler Master MS210/MK110</td><td>3.13</td><td>No software needed for full RGB control and Fn multimedia keys do work out of the box</td></tr>
<tr><td>Ducky Zero Keyboard DK2108SZ</td><td>3.10</td><td></td></tr>
<tr><td>IBM SK-8815 Corded USB Keyboard</td><td>3.15</td><td></td></tr>
<tr><td>Logitech UltraX Premium</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Wired Keyboard 600</td><td>3.13</td><td>Model X880609-600</td></tr>
<tr><td>Microsoft Wireless 900 Keyboard</td><td>3.13</td><td>Mouse+kb combo</td></tr>
<tr><td>Rapoo E6300 Ultra-Slim BT keyboard for iPad</td><td>3.11</td><td>①</td></tr>
<tr><td>Rapoo E9050 Wireless Compact Ultra-Slim Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Rapoo E2710 Wireless Nano-USB Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Xenta Super Compact Black Wired Keyboard (RK 107)</td><td>3.13</td><td></td></tr>
</table>
① requires a machine which supports paired BT input devices, like Mac mini

=== Mice ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>A-Eon Technology MX-1000-1</td><td>3.13</td><td></td></tr>
<tr><td>Dacota Gaming Serpent Mouse</td><td>3.15</td><td>Wired, 809024</td></tr>
<tr><td>[https://www.logitech.com/en-us/products/mice/m100-usb-mouse.910-001601.html Logitech M100 Optical Corded Mouse]</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M180</td><td>3.11</td><td></td></tr>
<tr><td>Logitech M185</td><td>3.10</td><td></td></tr>
<tr><td>Logitech M190</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M220 Silent</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M330 Silent</td><td>3.14</td><td></td></tr>
<tr><td>Logitech T-RB22 Wireless Trackball</td><td>3.11</td><td></td></tr>
<tr><td>Logitech G203</td><td>3.10</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Labtec Optical Mouse 800</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Compact Optical Mouse 500</td><td>3.14</td><td></td></tr>
<tr><td>Microsoft Trackball Explorer v1.0</td><td>3.11</td><td>PS2>USB adapter required</td></tr>
<tr><td>Microsoft Wireless Mouse 900</td><td>3.14</td><td>Mouse+kb combo</td></tr>
<tr><td style="color:red;">Microsoft Wireless Mouse 4000</td><td>3.13</td><td>Not working</td></tr>
<tr><td>Razer Viper Mini</td><td>3.15</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Sharkoon Skiller SGM2</td><td>3.13</td><td>No software needed for RGB and DPI settings, side buttons don't work</td></tr>
<tr><td>Targus AMU3102EU</td><td>3.10</td><td></td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=82 TENMOS K6 Wireless Gaming Mouse]</td><td>3.15</td><td></td></tr>
</table>

=== MIDI Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>Yamaha PSR-433 keyboard</td><td>3.14</td><td></td></tr>
</table>

=== Networking ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>TL-WR702N Nano Router</td><td></td><td></td></tr>
<tr><td>TL-WR802N Nano Router</td><td></td><td></td></tr>
</table>

=== Printers ===
<table><tr><th>Model</th><th class="os">OS</th><th>TurboPrint (Printer) driver</th><th>PostScript (Printers) driver</th><th class="comments">Comments</th></tr>
<tr><td>HP 2500 Color LaserJet</td><td>3.11</td><td></td><td>[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]</td><td>[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]</td></tr>
<tr><td>Konica Minolta Magicolor 4650</td><td>3.11</td><td></td><td>M4650PX.ppd</td><td></td></tr>
<tr><td>Lexmark E342n</td><td>3.11</td><td>HP_LaserJet5series</td><td>[http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD]</td><td></td></tr>
<tr><td>Xerox 3225 Workcentre</td><td>3.11</td><td></td><td></td><td>Reported to work with PS</td></tr>
<tr><td>HP Color LaserJet MFP M274n</td><td>3.15</td><td></td><td>hp-color_laserjet_mfp_m274-ps.ppd</td></tr>
</table>

=== Scanners ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Epson Perfection 1640SU</td><td>3.11</td><td>Including recent support for its ADF (Automatic Document Feeder).</td></tr>
</table>

=== Storage ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.amazon.co.uk/Hama-00055348-35in1-Multi-Reader/dp/B000IH1W20?th=1 HAMA USB 2.0 Card Reader 35 in 1]</td><td></td><td></td></tr>
</table>

=== USB Audio Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th>Output</th><th>Input</th><th class="comments">Comments</th></tr>
<tr><td>"[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card</td><td>3.10</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[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]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>C-Media soundcard</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>Corsair Void Elite Surround adapter/headset</td><td>3.14</td><td>OK</td><td>No</td><td>Headset with 3.5mm jack and a USB adapter. Analog volume control.</td></tr>
<tr><td>Corsair Void RGB Elite headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>FX-Audio- DAC-X3</td><td>3.12</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Griffin iMic</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>[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]</td><td>3.14</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Logitech H540 headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>Sony PlayStation Gold 7.1 headset</td><td>3.13</td><td>OK</td><td>Untested</td><td>Works in stereo.</td></tr>
<tr><td>[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]</td><td>3.11</td><td>OK</td><td>Untested</td><td>Only front output tested</tD></tr>
<tr><td>Steelseries Arctis 7 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>Turtle Beach Stealth 520 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
</table>

</div>

Hardware Compatibility

2024-02-14T07:46:54Z

NewSense: /* Game Controllers */

<div id="hardwareCompatibility">

== Official Information ==
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]].

== User Provided Reports ==
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&forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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&forum=11 let us know] so correction(s) can be made.

=== Game Controllers ===
<table style="width:100%">
<tr><th class="type">USB Device</th><th class="driver">USB driver</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>8bitdo SFC30 Pro Controller</td><td>hid</td><td>3.11</td></tr>
<tr><td>8bitdo SN30 Pro Controller</td><td>hid, xbox360</td><td>3.11</td><td>wired</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=34 BIMONK Wired Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=70 BIMONK Wireless Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>Logitech Rumble Pad wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=85 Mcbazel Dobe Mini Arcade Stick]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.onyxsoft.se/joydivision.html OnyxSoft JoyDivision] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>[https://www.retronicdesign.com/en/ Retronic Design] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>Saitek P380 Dual Analog wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td style="color:red;">Sony Dualshock 3 (PS3)</td><td>-</td><td>-</td><td>not supported</td></tr>
<tr><td>Sony Dualshock 4 (PS4)</td><td>xbox360</td><td>3.10</td></tr>
<tr><td>Speedlink Competition Pro USB</td><td>hid</td><td>3.11</td></tr>
<tr><td>Speedlink Xeox Gamepad</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)</td><td>hid</td><td>3.15</td></tr>
<tr><td>Thrustmaster 360 Modena Pro Racing Wheel</td><td>hid</td><td>3.11</td><td>needs some setup for the ranges from the Poseidon prefs</td></tr>
<tr><td>Xbox 360 wired and wireless pads</td><td>xbox360</td><td>3.11</td><td>wireless supported via PC adapter</td></tr>
<tr><td>Xbox One gamepad</td><td>xbox360</td><td>3.11</td><td>wired only</td></tr>
<tr><td>[https://www.marvo-tech.com/products/gt-016-wired-gaming-controller Marvo Scorpion GT-016 Joypad]</td><td>hid</td><td>3.18</td><td>wired, Dual Analog USB2 (PC & PS3)<td></tr>
</table>

=== Keyboards ===
<table style="width:100%;"><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Apple A1016 Wireless BlueTooth</td><td>3.10</td><td>①</td></tr>
<tr><td>Apple Magic Keyboard (Version 1)</td><td>3.13</td><td>①</td></tr>
<tr><td>Cooler Master MS210/MK110</td><td>3.13</td><td>No software needed for full RGB control and Fn multimedia keys do work out of the box</td></tr>
<tr><td>Ducky Zero Keyboard DK2108SZ</td><td>3.10</td><td></td></tr>
<tr><td>IBM SK-8815 Corded USB Keyboard</td><td>3.15</td><td></td></tr>
<tr><td>Logitech UltraX Premium</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Wired Keyboard 600</td><td>3.13</td><td>Model X880609-600</td></tr>
<tr><td>Microsoft Wireless 900 Keyboard</td><td>3.13</td><td>Mouse+kb combo</td></tr>
<tr><td>Rapoo E6300 Ultra-Slim BT keyboard for iPad</td><td>3.11</td><td>①</td></tr>
<tr><td>Rapoo E9050 Wireless Compact Ultra-Slim Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Rapoo E2710 Wireless Nano-USB Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Xenta Super Compact Black Wired Keyboard (RK 107)</td><td>3.13</td><td></td></tr>
</table>
① requires a machine which supports paired BT input devices, like Mac mini

=== Mice ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>A-Eon Technology MX-1000-1</td><td>3.13</td><td></td></tr>
<tr><td>Dacota Gaming Serpent Mouse</td><td>3.15</td><td>Wired, 809024</td></tr>
<tr><td>[https://www.logitech.com/en-us/products/mice/m100-usb-mouse.910-001601.html Logitech M100 Optical Corded Mouse]</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M180</td><td>3.11</td><td></td></tr>
<tr><td>Logitech M185</td><td>3.10</td><td></td></tr>
<tr><td>Logitech M190</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M220 Silent</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M330 Silent</td><td>3.14</td><td></td></tr>
<tr><td>Logitech T-RB22 Wireless Trackball</td><td>3.11</td><td></td></tr>
<tr><td>Logitech G203</td><td>3.10</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Labtec Optical Mouse 800</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Compact Optical Mouse 500</td><td>3.14</td><td></td></tr>
<tr><td>Microsoft Trackball Explorer v1.0</td><td>3.11</td><td>PS2>USB adapter required</td></tr>
<tr><td>Microsoft Wireless Mouse 900</td><td>3.14</td><td>Mouse+kb combo</td></tr>
<tr><td style="color:red;">Microsoft Wireless Mouse 4000</td><td>3.13</td><td>Not working</td></tr>
<tr><td>Razer Viper Mini</td><td>3.15</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Sharkoon Skiller SGM2</td><td>3.13</td><td>No software needed for RGB and DPI settings, side buttons don't work</td></tr>
<tr><td>Targus AMU3102EU</td><td>3.10</td><td></td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=82 TENMOS K6 Wireless Gaming Mouse]</td><td>3.15</td><td></td></tr>
</table>

=== MIDI Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>Yamaha PSR-433 keyboard</td><td>3.14</td><td></td></tr>
</table>

=== Networking ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>TL-WR702N Nano Router</td><td></td><td></td></tr>
<tr><td>TL-WR802N Nano Router</td><td></td><td></td></tr>
</table>

=== Printers ===
<table><tr><th>Model</th><th class="os">OS</th><th>TurboPrint (Printer) driver</th><th>PostScript (Printers) driver</th><th class="comments">Comments</th></tr>
<tr><td>HP 2500 Color LaserJet</td><td>3.11</td><td></td><td>[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]</td><td>[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]</td></tr>
<tr><td>Konica Minolta Magicolor 4650</td><td>3.11</td><td></td><td>M4650PX.ppd</td><td></td></tr>
<tr><td>Lexmark E342n</td><td>3.11</td><td>HP_LaserJet5series</td><td>[http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD]</td><td></td></tr>
<tr><td>Xerox 3225 Workcentre</td><td>3.11</td><td></td><td></td><td>Reported to work with PS</td></tr>
<tr><td>HP Color LaserJet MFP M274n</td><td>3.15</td><td></td><td>hp-color_laserjet_mfp_m274-ps.ppd</td></tr>
</table>

=== Scanners ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Epson Perfection 1640SU</td><td>3.11</td><td>Including recent support for its ADF (Automatic Document Feeder).</td></tr>
</table>

=== Storage ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.amazon.co.uk/Hama-00055348-35in1-Multi-Reader/dp/B000IH1W20?th=1 HAMA USB 2.0 Card Reader 35 in 1]</td><td></td><td></td></tr>
</table>

=== USB Audio Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th>Output</th><th>Input</th><th class="comments">Comments</th></tr>
<tr><td>"[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card</td><td>3.10</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[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]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>C-Media soundcard</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>Corsair Void Elite Surround adapter/headset</td><td>3.14</td><td>OK</td><td>No</td><td>Headset with 3.5mm jack and a USB adapter. Analog volume control.</td></tr>
<tr><td>Corsair Void RGB Elite headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>FX-Audio- DAC-X3</td><td>3.12</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Griffin iMic</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>[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]</td><td>3.14</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Logitech H540 headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>Sony PlayStation Gold 7.1 headset</td><td>3.13</td><td>OK</td><td>Untested</td><td>Works in stereo.</td></tr>
<tr><td>[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]</td><td>3.11</td><td>OK</td><td>Untested</td><td>Only front output tested</tD></tr>
<tr><td>Steelseries Arctis 7 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>Turtle Beach Stealth 520 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
</table>

</div>

Hardware Compatibility

2024-02-14T07:41:23Z

NewSense: /* Game Controllers */

<div id="hardwareCompatibility">

== Official Information ==
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]].

== User Provided Reports ==
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&forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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&forum=11 let us know] so correction(s) can be made.

=== Game Controllers ===
<table style="width:100%">
<tr><th class="type">USB Device</th><th class="driver">USB driver</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>8bitdo SFC30 Pro Controller</td><td>hid</td><td>3.11</td></tr>
<tr><td>8bitdo SN30 Pro Controller</td><td>hid, xbox360</td><td>3.11</td><td>wired</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=34 BIMONK Wired Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=70 BIMONK Wireless Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>Logitech Rumble Pad wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=85 Mcbazel Dobe Mini Arcade Stick]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.onyxsoft.se/joydivision.html OnyxSoft JoyDivision] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>[https://www.retronicdesign.com/en/ Retronic Design] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>Saitek P380 Dual Analog wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td style="color:red;">Sony Dualshock 3 (PS3)</td><td>-</td><td>-</td><td>not supported</td></tr>
<tr><td>Sony Dualshock 4 (PS4)</td><td>xbox360</td><td>3.10</td></tr>
<tr><td>Speedlink Competition Pro USB</td><td>hid</td><td>3.11</td></tr>
<tr><td>Speedlink Xeox Gamepad</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)</td><td>hid</td><td>3.15</td></tr>
<tr><td>Thrustmaster 360 Modena Pro Racing Wheel</td><td>hid</td><td>3.11</td><td>needs some setup for the ranges from the Poseidon prefs</td></tr>
<tr><td>Xbox 360 wired and wireless pads</td><td>xbox360</td><td>3.11</td><td>wireless supported via PC adapter</td></tr>
<tr><td>Xbox One gamepad</td><td>xbox360</td><td>3.11</td><td>wired only</td></tr>
<tr><td>[https://www.marvo-tech.com/products/gt-016-wired-gaming-controller Marvo Scorpion GT-016 Joypad]</td><td>hid</td><td>3.18</td><td>wired, Dual Analog USB2, originally for PC & PS3<td></tr>
</table>

=== Keyboards ===
<table style="width:100%;"><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Apple A1016 Wireless BlueTooth</td><td>3.10</td><td>①</td></tr>
<tr><td>Apple Magic Keyboard (Version 1)</td><td>3.13</td><td>①</td></tr>
<tr><td>Cooler Master MS210/MK110</td><td>3.13</td><td>No software needed for full RGB control and Fn multimedia keys do work out of the box</td></tr>
<tr><td>Ducky Zero Keyboard DK2108SZ</td><td>3.10</td><td></td></tr>
<tr><td>IBM SK-8815 Corded USB Keyboard</td><td>3.15</td><td></td></tr>
<tr><td>Logitech UltraX Premium</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Wired Keyboard 600</td><td>3.13</td><td>Model X880609-600</td></tr>
<tr><td>Microsoft Wireless 900 Keyboard</td><td>3.13</td><td>Mouse+kb combo</td></tr>
<tr><td>Rapoo E6300 Ultra-Slim BT keyboard for iPad</td><td>3.11</td><td>①</td></tr>
<tr><td>Rapoo E9050 Wireless Compact Ultra-Slim Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Rapoo E2710 Wireless Nano-USB Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Xenta Super Compact Black Wired Keyboard (RK 107)</td><td>3.13</td><td></td></tr>
</table>
① requires a machine which supports paired BT input devices, like Mac mini

=== Mice ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>A-Eon Technology MX-1000-1</td><td>3.13</td><td></td></tr>
<tr><td>Dacota Gaming Serpent Mouse</td><td>3.15</td><td>Wired, 809024</td></tr>
<tr><td>[https://www.logitech.com/en-us/products/mice/m100-usb-mouse.910-001601.html Logitech M100 Optical Corded Mouse]</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M180</td><td>3.11</td><td></td></tr>
<tr><td>Logitech M185</td><td>3.10</td><td></td></tr>
<tr><td>Logitech M190</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M220 Silent</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M330 Silent</td><td>3.14</td><td></td></tr>
<tr><td>Logitech T-RB22 Wireless Trackball</td><td>3.11</td><td></td></tr>
<tr><td>Logitech G203</td><td>3.10</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Labtec Optical Mouse 800</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Compact Optical Mouse 500</td><td>3.14</td><td></td></tr>
<tr><td>Microsoft Trackball Explorer v1.0</td><td>3.11</td><td>PS2>USB adapter required</td></tr>
<tr><td>Microsoft Wireless Mouse 900</td><td>3.14</td><td>Mouse+kb combo</td></tr>
<tr><td style="color:red;">Microsoft Wireless Mouse 4000</td><td>3.13</td><td>Not working</td></tr>
<tr><td>Razer Viper Mini</td><td>3.15</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Sharkoon Skiller SGM2</td><td>3.13</td><td>No software needed for RGB and DPI settings, side buttons don't work</td></tr>
<tr><td>Targus AMU3102EU</td><td>3.10</td><td></td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=82 TENMOS K6 Wireless Gaming Mouse]</td><td>3.15</td><td></td></tr>
</table>

=== MIDI Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>Yamaha PSR-433 keyboard</td><td>3.14</td><td></td></tr>
</table>

=== Networking ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>TL-WR702N Nano Router</td><td></td><td></td></tr>
<tr><td>TL-WR802N Nano Router</td><td></td><td></td></tr>
</table>

=== Printers ===
<table><tr><th>Model</th><th class="os">OS</th><th>TurboPrint (Printer) driver</th><th>PostScript (Printers) driver</th><th class="comments">Comments</th></tr>
<tr><td>HP 2500 Color LaserJet</td><td>3.11</td><td></td><td>[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]</td><td>[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]</td></tr>
<tr><td>Konica Minolta Magicolor 4650</td><td>3.11</td><td></td><td>M4650PX.ppd</td><td></td></tr>
<tr><td>Lexmark E342n</td><td>3.11</td><td>HP_LaserJet5series</td><td>[http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD]</td><td></td></tr>
<tr><td>Xerox 3225 Workcentre</td><td>3.11</td><td></td><td></td><td>Reported to work with PS</td></tr>
<tr><td>HP Color LaserJet MFP M274n</td><td>3.15</td><td></td><td>hp-color_laserjet_mfp_m274-ps.ppd</td></tr>
</table>

=== Scanners ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Epson Perfection 1640SU</td><td>3.11</td><td>Including recent support for its ADF (Automatic Document Feeder).</td></tr>
</table>

=== Storage ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.amazon.co.uk/Hama-00055348-35in1-Multi-Reader/dp/B000IH1W20?th=1 HAMA USB 2.0 Card Reader 35 in 1]</td><td></td><td></td></tr>
</table>

=== USB Audio Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th>Output</th><th>Input</th><th class="comments">Comments</th></tr>
<tr><td>"[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card</td><td>3.10</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[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]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>C-Media soundcard</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>Corsair Void Elite Surround adapter/headset</td><td>3.14</td><td>OK</td><td>No</td><td>Headset with 3.5mm jack and a USB adapter. Analog volume control.</td></tr>
<tr><td>Corsair Void RGB Elite headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>FX-Audio- DAC-X3</td><td>3.12</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Griffin iMic</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>[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]</td><td>3.14</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Logitech H540 headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>Sony PlayStation Gold 7.1 headset</td><td>3.13</td><td>OK</td><td>Untested</td><td>Works in stereo.</td></tr>
<tr><td>[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]</td><td>3.11</td><td>OK</td><td>Untested</td><td>Only front output tested</tD></tr>
<tr><td>Steelseries Arctis 7 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>Turtle Beach Stealth 520 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
</table>

</div>

Hardware Compatibility

2024-02-14T07:30:47Z

NewSense: /* Game Controllers */

<div id="hardwareCompatibility">

== Official Information ==
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]].

== User Provided Reports ==
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&forum=11 this thread] at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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&forum=11 let us know] so correction(s) can be made.

=== Game Controllers ===
<table style="width:100%">
<tr><th class="type">USB Device</th><th class="driver">USB driver</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>8bitdo SFC30 Pro Controller</td><td>hid</td><td>3.11</td></tr>
<tr><td>8bitdo SN30 Pro Controller</td><td>hid, xbox360</td><td>3.11</td><td>wired</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=34 BIMONK Wired Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=70 BIMONK Wireless Gaming Controller]</td><td>hid</td><td>3.15</td></tr>
<tr><td>Logitech Rumble Pad wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=85 Mcbazel Dobe Mini Arcade Stick]</td><td>hid</td><td>3.15</td></tr>
<tr><td>[https://www.onyxsoft.se/joydivision.html OnyxSoft JoyDivision] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>[https://www.retronicdesign.com/en/ Retronic Design] DB9-USB adapter</td><td>hid</td><td>3.13</td><td>Connect an Atari style joystick to USB</td></tr>
<tr><td>Saitek P380 Dual Analog wired (USB2)</td><td>hid</td><td>3.11</td></tr>
<tr><td style="color:red;">Sony Dualshock 3 (PS3)</td><td>-</td><td>-</td><td>not supported</td></tr>
<tr><td>Sony Dualshock 4 (PS4)</td><td>xbox360</td><td>3.10</td></tr>
<tr><td>Speedlink Competition Pro USB</td><td>hid</td><td>3.11</td></tr>
<tr><td>Speedlink Xeox Gamepad</td><td>hid</td><td>3.11</td></tr>
<tr><td>[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)</td><td>hid</td><td>3.15</td></tr>
<tr><td>Thrustmaster 360 Modena Pro Racing Wheel</td><td>hid</td><td>3.11</td><td>needs some setup for the ranges from the Poseidon prefs</td></tr>
<tr><td>Xbox 360 wired and wireless pads</td><td>xbox360</td><td>3.11</td><td>wireless supported via PC adapter</td></tr>
<tr><td>Xbox One gamepad</td><td>xbox360</td><td>3.11</td><td>wired only</td></tr>
<tr><td>[https://www.marvo-tech.com/products/gt-016-wired-gaming-controller Marvo Scorpion GT-106 Joypad]</td><td>hid</td><td>3.18</td><td>wired, Dual Analog USB2, originally for PC & PS3<td></tr>
</table>

=== Keyboards ===
<table style="width:100%;"><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Apple A1016 Wireless BlueTooth</td><td>3.10</td><td>①</td></tr>
<tr><td>Apple Magic Keyboard (Version 1)</td><td>3.13</td><td>①</td></tr>
<tr><td>Cooler Master MS210/MK110</td><td>3.13</td><td>No software needed for full RGB control and Fn multimedia keys do work out of the box</td></tr>
<tr><td>Ducky Zero Keyboard DK2108SZ</td><td>3.10</td><td></td></tr>
<tr><td>IBM SK-8815 Corded USB Keyboard</td><td>3.15</td><td></td></tr>
<tr><td>Logitech UltraX Premium</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Wired Keyboard 600</td><td>3.13</td><td>Model X880609-600</td></tr>
<tr><td>Microsoft Wireless 900 Keyboard</td><td>3.13</td><td>Mouse+kb combo</td></tr>
<tr><td>Rapoo E6300 Ultra-Slim BT keyboard for iPad</td><td>3.11</td><td>①</td></tr>
<tr><td>Rapoo E9050 Wireless Compact Ultra-Slim Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Rapoo E2710 Wireless Nano-USB Keyboard</td><td>3.11</td><td></td></tr>
<tr><td>Xenta Super Compact Black Wired Keyboard (RK 107)</td><td>3.13</td><td></td></tr>
</table>
① requires a machine which supports paired BT input devices, like Mac mini

=== Mice ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>A-Eon Technology MX-1000-1</td><td>3.13</td><td></td></tr>
<tr><td>Dacota Gaming Serpent Mouse</td><td>3.15</td><td>Wired, 809024</td></tr>
<tr><td>[https://www.logitech.com/en-us/products/mice/m100-usb-mouse.910-001601.html Logitech M100 Optical Corded Mouse]</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M180</td><td>3.11</td><td></td></tr>
<tr><td>Logitech M185</td><td>3.10</td><td></td></tr>
<tr><td>Logitech M190</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M220 Silent</td><td>3.15</td><td></td></tr>
<tr><td>Logitech M330 Silent</td><td>3.14</td><td></td></tr>
<tr><td>Logitech T-RB22 Wireless Trackball</td><td>3.11</td><td></td></tr>
<tr><td>Logitech G203</td><td>3.10</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Labtec Optical Mouse 800</td><td>3.10</td><td></td></tr>
<tr><td>Microsoft Compact Optical Mouse 500</td><td>3.14</td><td></td></tr>
<tr><td>Microsoft Trackball Explorer v1.0</td><td>3.11</td><td>PS2>USB adapter required</td></tr>
<tr><td>Microsoft Wireless Mouse 900</td><td>3.14</td><td>Mouse+kb combo</td></tr>
<tr><td style="color:red;">Microsoft Wireless Mouse 4000</td><td>3.13</td><td>Not working</td></tr>
<tr><td>Razer Viper Mini</td><td>3.15</td><td>No software control over RGB, DPI</td></tr>
<tr><td>Sharkoon Skiller SGM2</td><td>3.13</td><td>No software needed for RGB and DPI settings, side buttons don't work</td></tr>
<tr><td>Targus AMU3102EU</td><td>3.10</td><td></td></tr>
<tr><td>[https://www.morphos-store.com/product_info.php?products_id=82 TENMOS K6 Wireless Gaming Mouse]</td><td>3.15</td><td></td></tr>
</table>

=== MIDI Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard</td><td>3.13</td><td></td></tr>
<tr><td>Yamaha PSR-433 keyboard</td><td>3.14</td><td></td></tr>
</table>

=== Networking ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>TL-WR702N Nano Router</td><td></td><td></td></tr>
<tr><td>TL-WR802N Nano Router</td><td></td><td></td></tr>
</table>

=== Printers ===
<table><tr><th>Model</th><th class="os">OS</th><th>TurboPrint (Printer) driver</th><th>PostScript (Printers) driver</th><th class="comments">Comments</th></tr>
<tr><td>HP 2500 Color LaserJet</td><td>3.11</td><td></td><td>[http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz HP2500_6.PPD]</td><td>[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]</td></tr>
<tr><td>Konica Minolta Magicolor 4650</td><td>3.11</td><td></td><td>M4650PX.ppd</td><td></td></tr>
<tr><td>Lexmark E342n</td><td>3.11</td><td>HP_LaserJet5series</td><td>[http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD]</td><td></td></tr>
<tr><td>Xerox 3225 Workcentre</td><td>3.11</td><td></td><td></td><td>Reported to work with PS</td></tr>
<tr><td>HP Color LaserJet MFP M274n</td><td>3.15</td><td></td><td>hp-color_laserjet_mfp_m274-ps.ppd</td></tr>
</table>

=== Scanners ===
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>Epson Perfection 1640SU</td><td>3.11</td><td>Including recent support for its ADF (Automatic Document Feeder).</td></tr>
</table>

=== Storage ===
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr>
<tr><td>[https://www.amazon.co.uk/Hama-00055348-35in1-Multi-Reader/dp/B000IH1W20?th=1 HAMA USB 2.0 Card Reader 35 in 1]</td><td></td><td></td></tr>
</table>

=== USB Audio Devices ===
<table><tr><th>Device</th><th class="os">OS</th><th>Output</th><th>Input</th><th class="comments">Comments</th></tr>
<tr><td>"[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card</td><td>3.10</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[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]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>[https://www.amazon.ca/Avantree-Bluetooth-Driver-Free-Wireless-Transmitter/dp/B01G3J1I5M Avantree Leaf BT 4.1 adapter]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>C-Media soundcard</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>Corsair Void Elite Surround adapter/headset</td><td>3.14</td><td>OK</td><td>No</td><td>Headset with 3.5mm jack and a USB adapter. Analog volume control.</td></tr>
<tr><td>Corsair Void RGB Elite headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>FX-Audio- DAC-X3</td><td>3.12</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Griffin iMic</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr>
<tr><td>[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]</td><td>3.14</td><td>OK</td><td>N/A</td><td></td></tr>
<tr><td>Logitech H540 headset</td><td>3.14</td><td>OK</td><td>No</td><td>Volume control binds to the HID class. Hint: can be used with [http://aminet.net/package/mus/play/MultiMeedio this].</td></tr>
<tr><td>Sony PlayStation Gold 7.1 headset</td><td>3.13</td><td>OK</td><td>Untested</td><td>Works in stereo.</td></tr>
<tr><td>[https://de.creative.com/p/sound-cards/sound-blaster-digital-music-premium-hd Sound Blaster X-Fi]</td><td>3.11</td><td>OK</td><td>Untested</td><td>Only front output tested</tD></tr>
<tr><td>Steelseries Arctis 7 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
<tr><td>[https://www.terratec.de/details.php?artnr=195448 TerraTec 195448 Aureon Dual USB]</td><td>3.11</td><td>OK</td><td>Untested</td><td></td></tr>
<tr><td>Turtle Beach Stealth 520 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr>
</table>

</div>

Multi-display

2019-11-16T22:55:09Z

NewSense: /* Examples */

== Basics ==
MorphOS has limited support for multi-display setups. On the hardware side there's multi-head support for selected Radeon R3xx cards and configurations on PowerMac G5, PowerBook, and iMac setups. It's also possible to use multiple individual graphics cards in specific setups.

On the software side, from a users' perspective, multi-display setups rely on the [[Fundamentals_of_MorphOS#Screens|screens]] concept, which is inherited from AmigaOS. Individual screens can be configured to be opened on individual displays/monitors. The Ambient desktop will always be on its own screen and it cannot be stretched over several screens, it's always displayed only on one monitor, but you can open other programs on other monitors quite freely and decide which program is displayed on which monitor.

Neither is there a system provided way to move the mouse pointer to another screen by moving it over the screen borders, so it must be done by cycling the screens just as when using multiple screens on a single monitor setup.

== Configuring ==
When booting a multi-display setup for the first time, the Ambient screen opens on the largest or first display it finds. The other display(s) should show a mirrored image of the Ambient screen, but it may fail dependant on monitor specifications.

Which screen is displayed on which monitor can be configured from the '''Screens preferences''' in the MorphOS [[Getting_Started#System_Settings|system settings]]. There you can edit existing screens or create whole new screens.

To change the monitor a screen is displayed on, double-clicking the corresponding entry in the screens list and the '''Edit Screen''' window should then open.
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|500px]]

The '''mode list''' shows all the available screenmodes on the computer, and these can be selected for the screen that needs editing. Mode names start with the graphics cards' name. On single-display setups all modes have the same name, but on multi-display setups the mode names reveal on which monitor the mode will be shown. On multi-head setups (single card/chipset, but several outputs), names only differ by the number added at the end of the names.
: [[File:Multi-display_modes.png]]

== Examples ==
=== Configuring Ambient for the Internal Display on PowerBooks ===
For example, on PowerBook5,9 modes for the internal display have the name '''Radeon9700Mob''' and modes for the external monitor have the name '''Radeon9700Mob.1'''. To set the Ambient screen to the internal display, you'd select the ''Radeon9700Mob 24bit 1680 x 1050'' mode when editing the Ambient screen settings. Available resolutions differ between PowerBook models, but you should always select a mode that is equal to the native resolution of your display.

=== Configuring a Program to Use the Other Display ===
All MUI (the native GUI toolkit of MorphOS) programs can be configured to use a screen on any monitor. With non-MUI programs (legacy 68k programs mainly) it depends on whether a program has a specific setting for its screenmode.

Here's a tutorial on how to configure a MUI program to use its own screen: [[Getting_Started#Making_OWB_to_Use_Its_Own_Screen|Making_OWB_to_Use_Its_Own_Screen]]. Just remember to select a screenmode for the required monitor in this case.

=== Using Several Programs on a Single External Screen ===
If you want to keep things tidy by only having one screen per monitor, you can create a single external screen to accompany your Ambient screen, and spread regularly used programs between them.

To create the screen, click '''New''' in the Screens preferences. Fill the '''Name''' and '''Title''' fields, for example, with ''External'' and ''External Monitor'' texts. Select a screenmode that has an alternate mode name than your Ambient screen has (ending in .1, for instance). Click '''Ok''', and '''Save''' or '''Use''' to test out the available screen on your system.
: [[File:Multi-display_external_setup.png|550px]]

Now you can move (MUI) programs to that screen by selecting '''Jump to Screen -> External''' from the [[Fundamentals_of_MorphOS#Window_border_gadgets|window popup gadget]]. If you don't see the gadget, check the ''Windows'' page in the MUI settings to enable it. The next screenshots show how to move a Shell window to the external screen.
: [[File:Multi-display_external_jump.png]] [[File:Multi-display_external_screen.png]]

Programs can also be set to use the external screen permanently, you don't have to make them jump around all the time after reboots. Open the program's own MUI settings by clicking the [[Fundamentals_of_MorphOS#Window_border_gadgets|window popup gadget]] and select '''MUI Settings...''', or by selecting the '''Settings -> MUI...''' pull-down menu option when program's window is active. Activate the '''Screen''' page and select ''External'' from the list.
: [[File:Multi-display_mui_settings.png]]

Program windows can be saved to fixed positions on the screen by selecting the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets|window popup gadget]].

Here's an example screenshot with several networking related programs snapshotted in fixed positions on the external screen.
: [[File:Multi-display_netscreen.png|550px]]

== Usage ==
Only one screen can be active at once, and both the mouse pointer and the active text input will be on that screen.

To change the active screen, and thus the display/monitor you work on, you'll have to ''cycle'' screens in the traditional Amiga/MorphOS ways. By default that can be done by pressing the '''lcommand m''' keyboard shortcut or by using the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget|screen depth gadget]].

The keyboard shortcut, or mouse action, can be freely configured from the [[Getting_Started#IControl|IControl]] preferences in the MorphOS [[Getting_Started#System_Settings|system settings]]. It's done by editing the '''Screen: To Back''' hotkey.

It's also possible to add several different hotkeys for each action. Here's an example screenshot where both ''lcommand m'' and double-click with the middle mouse button (wheel) will cycle screens.
: [[File:Multi-display_icontrol.png|550px]]

There are also some 3rd party programs, or ''commodities'', to cycle the screens in different ways.

Multi-display

2019-11-16T22:48:08Z

NewSense: /* Configuring */

== Basics ==
MorphOS has limited support for multi-display setups. On the hardware side there's multi-head support for selected Radeon R3xx cards and configurations on PowerMac G5, PowerBook, and iMac setups. It's also possible to use multiple individual graphics cards in specific setups.

On the software side, from a users' perspective, multi-display setups rely on the [[Fundamentals_of_MorphOS#Screens|screens]] concept, which is inherited from AmigaOS. Individual screens can be configured to be opened on individual displays/monitors. The Ambient desktop will always be on its own screen and it cannot be stretched over several screens, it's always displayed only on one monitor, but you can open other programs on other monitors quite freely and decide which program is displayed on which monitor.

Neither is there a system provided way to move the mouse pointer to another screen by moving it over the screen borders, so it must be done by cycling the screens just as when using multiple screens on a single monitor setup.

== Configuring ==
When booting a multi-display setup for the first time, the Ambient screen opens on the largest or first display it finds. The other display(s) should show a mirrored image of the Ambient screen, but it may fail dependant on monitor specifications.

Which screen is displayed on which monitor can be configured from the '''Screens preferences''' in the MorphOS [[Getting_Started#System_Settings|system settings]]. There you can edit existing screens or create whole new screens.

To change the monitor a screen is displayed on, double-clicking the corresponding entry in the screens list and the '''Edit Screen''' window should then open.
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|500px]]

The '''mode list''' shows all the available screenmodes on the computer, and these can be selected for the screen that needs editing. Mode names start with the graphics cards' name. On single-display setups all modes have the same name, but on multi-display setups the mode names reveal on which monitor the mode will be shown. On multi-head setups (single card/chipset, but several outputs), names only differ by the number added at the end of the names.
: [[File:Multi-display_modes.png]]

== Examples ==
=== Configuring Ambient on the Internal Display on PowerBooks ===
For example, on PowerBook5,9 modes for the internal display have the name '''Radeon9700Mob''' and modes for the external monitor have the name '''Radeon9700Mob.1'''. To set the Ambient screen to the internal display, you'd select the ''Radeon9700Mob 24bit 1680 x 1050'' mode when editing the Ambient screen settings. Available resolutions differ between PowerBook models, but you should always select a mode that is equal to the native resolution of your display.

=== Configuring a Program to Use the Other Display ===
All MUI (the native GUI toolkit of MorphOS) programs can be configured to use a screen on any monitor. With non-MUI programs (legacy 68k programs mainly) it depends on if a program has a separate setting for the screenmode.

Here's a tutorial how to configure a MUI program to use its own screen: [[Getting_Started#Making_OWB_to_Use_Its_Own_Screen|Making_OWB_to_Use_Its_Own_Screen]]. Just remember to select a screenmode on the wanted monitor in this case.

=== Using Several Programs on a Single External Screen ===
If you want to keep things tidy by only having one screen per monitor, you can create a single external screen to accompany your Ambient screen, and spread regularly used programs between them.

To create the screen, click '''New''' in the Screens preferences. Fill the '''Name''' and '''Title''' fields, for example, with ''External'' and ''External Monitor'' texts. Select a screenmode that has different kind of mode name than your Ambient screen has (ending to .1, for instance). Click '''Ok''', and '''Save''' or '''Use''' to get the screen available on the system.
: [[File:Multi-display_external_setup.png|550px]]

Now you can move (MUI) programs to that screen by selecting '''Jump to Screen -> External''' from the [[Fundamentals_of_MorphOS#Window_border_gadgets|window popup gadget]]. If you don't see the gadget, check the ''Windows'' page in the MUI settings to enable it. The next screenshots show how to move a shell window to the external screen.
: [[File:Multi-display_external_jump.png]] [[File:Multi-display_external_screen.png]]

Programs can also be set to use the external screen permanently, you don't have to make them jump around all the time after reboots. Open program's own MUI settings by clicking the [[Fundamentals_of_MorphOS#Window_border_gadgets|window popup gadget]] and select '''MUI Settings...''', or by selecting the '''Settings -> MUI...''' pull-down menu option when program's window is active. Activate the '''Screen''' page and select ''External'' from the list.
: [[File:Multi-display_mui_settings.png]]

Program windows can be saved to fixed positions on the screen by selecting the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets|window popup gadget]].

Here's an example screenshot with several networking related programs snapshotted on fixed positions on the external screen.
: [[File:Multi-display_netscreen.png|550px]]

== Usage ==
Only one screen can be active at once, and both the mouse pointer and the active text input will be on that screen.

To change the active screen, and thus the display/monitor you work on, you'll have to ''cycle'' screens in the traditional Amiga/MorphOS ways. By default that can be done by pressing the '''lcommand m''' keyboard shortcut or by using the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget|screen depth gadget]].

The keyboard shortcut, or mouse action, can be freely configured from the [[Getting_Started#IControl|IControl]] preferences in the MorphOS [[Getting_Started#System_Settings|system settings]]. It's done by editing the '''Screen: To Back''' hotkey.

It's also possible to add several different hotkeys for each action. Here's an example screenshot where both ''lcommand m'' and double-click with the middle mouse button (wheel) will cycle screens.
: [[File:Multi-display_icontrol.png|550px]]

There are also some 3rd party programs, or ''commodities'', to cycle the screens in different ways.

Multi-display

2019-11-16T22:44:16Z

NewSense: /* Basics */

== Basics ==
MorphOS has limited support for multi-display setups. On the hardware side there's multi-head support for selected Radeon R3xx cards and configurations on PowerMac G5, PowerBook, and iMac setups. It's also possible to use multiple individual graphics cards in specific setups.

On the software side, from a users' perspective, multi-display setups rely on the [[Fundamentals_of_MorphOS#Screens|screens]] concept, which is inherited from AmigaOS. Individual screens can be configured to be opened on individual displays/monitors. The Ambient desktop will always be on its own screen and it cannot be stretched over several screens, it's always displayed only on one monitor, but you can open other programs on other monitors quite freely and decide which program is displayed on which monitor.

Neither is there a system provided way to move the mouse pointer to another screen by moving it over the screen borders, so it must be done by cycling the screens just as when using multiple screens on a single monitor setup.

== Configuring ==
When booting a multi-display setup first time, the Ambient screen opens on the biggest or first display it finds. The other display(s) should show a mirrored image of the Ambient screen, but it may fail depending on monitor specifications.

Which screen is displayed on which monitor can be configured from the '''Screens preferences''' in the MorphOS [[Getting_Started#System_Settings|system settings]]. There you can edit existing screens or create whole new screens.

To change the monitor a screen is displayed on, double-click the corresponding entry in the screens list and the '''Edit Screen''' window should open.
: [[File:GettingStarted_MorphOS_Preferences_Screens.png|500px]]

The '''mode list''' shows all available screenmodes on the computer, and these can be selected for the screen we are editing. Mode names start with the graphics cards' name. On single-display setups all modes have the same name, but on multi-display setups the mode names reveal on which monitor the mode will be shown. On multi-head setups (single card/chipset, but several outputs), names only differ by the number added at the end of the names.
: [[File:Multi-display_modes.png]]

== Examples ==
=== Configuring Ambient on the Internal Display on PowerBooks ===
For example, on PowerBook5,9 modes for the internal display have the name '''Radeon9700Mob''' and modes for the external monitor have the name '''Radeon9700Mob.1'''. To set the Ambient screen to the internal display, you'd select the ''Radeon9700Mob 24bit 1680 x 1050'' mode when editing the Ambient screen settings. Available resolutions differ between PowerBook models, but you should always select a mode that is equal to the native resolution of your display.

=== Configuring a Program to Use the Other Display ===
All MUI (the native GUI toolkit of MorphOS) programs can be configured to use a screen on any monitor. With non-MUI programs (legacy 68k programs mainly) it depends on if a program has a separate setting for the screenmode.

Here's a tutorial how to configure a MUI program to use its own screen: [[Getting_Started#Making_OWB_to_Use_Its_Own_Screen|Making_OWB_to_Use_Its_Own_Screen]]. Just remember to select a screenmode on the wanted monitor in this case.

=== Using Several Programs on a Single External Screen ===
If you want to keep things tidy by only having one screen per monitor, you can create a single external screen to accompany your Ambient screen, and spread regularly used programs between them.

To create the screen, click '''New''' in the Screens preferences. Fill the '''Name''' and '''Title''' fields, for example, with ''External'' and ''External Monitor'' texts. Select a screenmode that has different kind of mode name than your Ambient screen has (ending to .1, for instance). Click '''Ok''', and '''Save''' or '''Use''' to get the screen available on the system.
: [[File:Multi-display_external_setup.png|550px]]

Now you can move (MUI) programs to that screen by selecting '''Jump to Screen -> External''' from the [[Fundamentals_of_MorphOS#Window_border_gadgets|window popup gadget]]. If you don't see the gadget, check the ''Windows'' page in the MUI settings to enable it. The next screenshots show how to move a shell window to the external screen.
: [[File:Multi-display_external_jump.png]] [[File:Multi-display_external_screen.png]]

Programs can also be set to use the external screen permanently, you don't have to make them jump around all the time after reboots. Open program's own MUI settings by clicking the [[Fundamentals_of_MorphOS#Window_border_gadgets|window popup gadget]] and select '''MUI Settings...''', or by selecting the '''Settings -> MUI...''' pull-down menu option when program's window is active. Activate the '''Screen''' page and select ''External'' from the list.
: [[File:Multi-display_mui_settings.png]]

Program windows can be saved to fixed positions on the screen by selecting the '''Snapshot''' option from the [[Fundamentals_of_MorphOS#Window_border_gadgets|window popup gadget]].

Here's an example screenshot with several networking related programs snapshotted on fixed positions on the external screen.
: [[File:Multi-display_netscreen.png|550px]]

== Usage ==
Only one screen can be active at once, and both the mouse pointer and the active text input will be on that screen.

To change the active screen, and thus the display/monitor you work on, you'll have to ''cycle'' screens in the traditional Amiga/MorphOS ways. By default that can be done by pressing the '''lcommand m''' keyboard shortcut or by using the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget|screen depth gadget]].

The keyboard shortcut, or mouse action, can be freely configured from the [[Getting_Started#IControl|IControl]] preferences in the MorphOS [[Getting_Started#System_Settings|system settings]]. It's done by editing the '''Screen: To Back''' hotkey.

It's also possible to add several different hotkeys for each action. Here's an example screenshot where both ''lcommand m'' and double-click with the middle mouse button (wheel) will cycle screens.
: [[File:Multi-display_icontrol.png|550px]]

There are also some 3rd party programs, or ''commodities'', to cycle the screens in different ways.

Mounting Network Drives

2019-11-16T22:38:31Z

NewSense: /* A simple example ran from the shell */

== SmbFS ==
Windows shares, and Samba shares on other systems like Linux servers and NAS devices, can be mounted with the native [[Shell_Commands/SmbFS|SmbFS]] Shell command which is included with MorphOS. You shouldn't install any third party versions, because the included command is the most up-to-date and compatible version available, and it also has 64-bit I/O support.

The ''SYS:MorphOS/Locale/Help/english/SmbFS.txt'' file contains a detailed description of all [[Shell_Commands/SmbFS|SmbFS]] options, but in most cases you'll be fine with just few basic options.

=== A simple example run from the Shell ===
'''SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
Connected '//win7/sharedstuff' to 'Win7_share:'; "Break 5" or [Ctrl-C] to stop...

The VOLUME option specifies a volume name for the mounted device. Without it the device would only be accessible with its device name and no icon would appear on the Ambient desktop. Any name you want will be fine.

The first part of the SERVICE option contains a remote file server's name as seen, for example, on the network computers list on Windows. It is followed by a share name, which would be seen if you opened a network computer on Windows. The server name is ''win7'' and the share name is ''sharedstuff'' in this case.

The share can be unmounted by pressing ''CTRL C'' keyboard combination when started like this.

The server name should work as it is, but if the host can't be found for some reason, you could try to add it to the Hosts settings in the MorphOS preferences.
: [[File:MorphOS_Preferences_Hosts.png|320px]]

If you want to start the [[Shell_Commands/SmbFS|SmbFS]] command as a background process from the Shell, the S:user-network-startup file, or anywhere else, you can launch it with the [[Shell_Commands/Run|Run]] command. The ''>NIL:'' redirect ensures that no output windows will pop up either.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''

There are several ways to unmount the share now, but the easiest is to use the Eject [[Screenbar_Modules|screenbar module]] or the [[Shell_Commands/UnMount|UnMount]] command.
: [[File:NetworkDrives_SmbFS_Eject.png]]

If you replace the PASSWORD option with the ASKPASSWORD option, you'll get a requester asking for the password.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=MorphOS_Rulez ASKPASSWORD VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
: [[File:NetworkDrives_SmbFS_PW.png]]

== Ssh2FS ==
The built-in [[Shell_Commands/Ssh2FS|Ssh2FS]] command can be used to mount a remote SFTP share on your local MorphOS machine. Practically all remote servers you can access using a SSH2 client can also be mounted as part of the filesystem with this command.

The ''SYS:MorphOS/Locale/Help/english/Ssh2FS.readme'' file contains a detailed description of all [[Shell_Commands/Ssh2FS|Ssh2FS]] the options.

=== Requirements ===
Ssh2FS needs a home directory for the user, and that directory must be set to ''MorphOS Preferences -> Users -> Home Dir'' or provided as a Command-Line argument to Ssh2FS (''HOME=path:dir/'').

It is recommended to set the home directory in the MorphOS Preferences for easier use later on.
# Create a new directory somewhere. ''SYS:Home'', for instance.
# Set this directory to ''MorphOS Preferences -> Users -> Home Dir'' and save settings. A ''HOME:'' assign is created automatically to point into this directory.

=== Examples ===
Here are some examples to run from the Shell. '''Bold lines''' are what you need to type into the Shell.

==== Mounting with the Password Prompt ====
This will ask for a password for the "linuxuser" account, and mounts the remote server with "Linux" as a volume name. A drive icon with that name will appear on the Ambient desktop.
'''ssh2fs linuxuser@192.168.1.4 Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Host '192.168.1.4' is not known!
Add host to known_hosts file ? (y/n)'''y'''
Enter password:
SFTP connection established.

Now you can unmount the share by pressing the ''CTRL C'' keyboard combination, by using the Eject [[Screenbar_Modules|screenbar module]], or with the [[Shell_Commands/UnMount|UnMount]] Shell command (''UnMount Linux:'').

The previous example mounted the root directory of the server, but this would only mount your own home directory.
'''ssh2fs linuxuser@192.168.1.4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

If you have mapped a hostname for your server's IP address from ''MorphOS Preferences -> Hosts'', that will also work, as well as any URL to remote servers on the Internet. Here we have ''linux4'' set for the LAN address 192.168.1.4.
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

==== Passwordless Mounting ====
If you prefer to avoid entering the password, and do more automatic mounting of shares, a public key can be generated and used for authentication.
# Set a hostname for your machine in ''MorphOS Preferences -> Network -> Host and DNS'' if not already set
# Open the Shell, type '''SYS:Applications/RemoteShell/Files/ssh-keygen -t rsa''', and press the Enter key a few times (don't set the passphrase).
# Copy the resulting files (''id_rsa'' and ''id_rsa.pub'') to the ''.ssh'' directory in your MorphOS home directory. For example, '''Copy SYS:Applications/RemoteShell/Files/conf/id_rsa#? HOME:.ssh/'''
# Append the contents of the ''id_rsa.pub'' file to the ''~/.ssh/authorized_keys'' file on the server. There are several ways to do that, such as, these two (pick only one, and notice the double > character):
## Copy the file to the server, connect by an SSH client, execute ''cat id_rsa.pub >> ~/.ssh/authorized_keys''
## Mount your own remote ''home directory'' with Ssh2FS and the password option as mentioned in the previous section, type in the MorphOS Shell: '''Type HOME:.ssh/id_rsa.pub >> Linux:.ssh/authorized_keys'''

Now you should be able to mount the server without encountering a password prompt with the ''pk'' argument:
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
SFTP connection established.

==== Mounting as a Background Process ====
The previous examples required user interaction in the Shell, but if you want to start Ssh2FS mounts as a background processes, you'll have to use the
[[Shell_Commands/RunFS|RunFS]] command. Normally you would do that with the Run command, but that has some limitations in this case and so that's why the RunFS command is provided.

Note that you'll have to provide a path to the Ssh2FS location (''C:''), otherwise RunFS won't find it. In this example we'll also disable the output with the ''Q=QUIET'' argument.
'''runfs Q C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

If you want to open a new Ambient window automatically for the newly mounted share, you can use the ''O=OPEN'' argument.
'''runfs Q O C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

With the previous lines you can mount SFTP shares, for example, automatically on each boot from ''S:user-network-startup'', or manually from the menus or keyboard shortcuts.

=== Unmounting ===
As mentioned earlier, mounted Ssh2FS shares can be unmounted in several ways.
* Use the Eject [[Screenbar_Modules|screenbar module]]
* Use the [[Shell_Commands/UnMount|UnMount]] Shell command: ''UnMount VolumeName:''
* Send a ''CTRL C'' signal to the Ssh2FS task, for example, by keyboard, using the [[Shell_Commands/Break|Break]] command, or using the [[Utilities/TaskManager|TaskManager]] utility.

== NetFS Revised ==
[http://aminet.net/package/comm/net/NetFS-revised NetFS Revised] allows the mounting of drives between MorphOS and AmigaOS systems. It is the best alternative to share files between Amiga compatible systems, because it preserves protection bits and other Amiga-like file properties. NetFS Revised also contains a tool to access ARexx ports remotely.

Here's a step-by-step guide of how to install it on MorphOS.

# Copy contents of the '''NetFS/SYS.MorphOS/''' directory to your '''SYS:''' partition
# Copy '''NetFS/Prefs/Env-Archive/netfs-server.config''' to '''ENVARC:'''
# (Optionally) Copy '''NetFS/Devs/DOSDrivers/ANETFS0''' to '''SYS:Storage/DOSDrivers/''' (if you want to mount a drive with a mountlist later)
# (Optionally) Copy '''NetFS/Help/english/NetFS.guide''' to '''HELP:english/''' (to keep the documentation available)
# Add '''amiganetfs 2500/tcp''', '''amiganetfs 2500/udp''', and '''amiganetfsprobe 2501/udp''' lines to the '''ENVARC:sys/net/services''' file. [[File:NetworkDrives_NetFS1.png|480px]]
# Add '''amiganetfs stream tcp nowait root C:InetD/netfs-server''' and '''amiganetfs dgram udp wait root C:InetD/netfs-server''' lines to the '''ENVARC:sys/net/inetd.conf''' file. If you don't plan to use the system as a server, you may leave it commented by starting the line with the # character, but better add the line there for any future use. [[File:NetworkDrives_NetFS2.png|480px]]
# Edit the last line on the '''ENVARC:netfs-server.config''' file to your liking on the server machine. In this example we'll allow access to the Work: partition with a specified login and password. [[File:NetworkDrives_NetFS3.png|480px]]
# '''Reboot''' the machine before trying it out.

The server works automatically, and you just need to connect to it from a client machine. We can mount the server's Work: partition by running the NetMount command on the client machine. Server's IP address is 192.168.1.10 in this example.

'''NetMount 192.168.1.10 Work: NetFS0: LOGIN=morphos PASS=rulez''' mounts the remote Work: partition as a local device called NetFS0:. The local device name can be anything you want, but NetMount creates the volume name automatically by adding the address after the remote volume name.
: [[File:NetworkDrives_NetFS4.png|480px]]

A better solution is to add a hostname for the server IP address, if you haven't done that already, and use that instead of the numerical address. Let's remove the mount with the [[Shell_Commands/UnMount|UnMount]] command and add a hostname on the Hosts settings in the MorphOS preferences.
: [[File:NetworkDrives_NetFS5.png|480px]]

So, let's try that again with the '''NetMount pb Work: NetFS0: LOGIN=morphos PASS=rulez''' command.
: [[File:NetworkDrives_NetFS6.png|480px]]

If you want to unmount the shares with the Eject [[Screenbar_Modules|screenbar module]], you'll have to decide to use a certain pattern with device names you mount and add that pattern to the Eject module's settings. If you keep using device names like NetFS0, NetFS1, NetFS3, etc, you could add '''NetFS#[0-9]''' or '''NetFS#?''' or similar to the Unmount pattern.
: [[File:NetworkDrives_NetFS7.png|480px]] [[File:NetworkDrives_NetFS8.png|480px]]

Also if you want to have a new default icon for the previous devices, copy or create an icon named def_NetFSxdisk.info to the SYS:Prefs/Presets/Deficons/ directory. '''Copy SYS:Prefs/Presets/Deficons/def_SMBFSxdisk.info to SYS:Prefs/Presets/Deficons/def_NetFSxdisk.info''' which would then use the same icon with SmbFS and NetFS shares.

== RDesktop ==
The [[Applications/RDesktop|RDesktop]] application included in MorphOS displays a remote machine's desktop on your computer, but it can also mount a local directory on the remote machine. If you're using [[Applications/RDesktop|RDesktop]] to control a remote machine, it's a good way to share MorphOS files with the remote machine without needing to install any other services on your MorphOS computer.

Click the '''Options''' button on the RDesktopGUI window, open the '''Resources''' tab, and select a directory on the '''Mounted Directories''' group. The directory will be shown on the remote machine when you connect to it.
: [[File:MorphOS3_jPV_Rdesktop.png|320px]] [[File:RDesktop_netdisk_mount.png|320px|top]]

== Google Drive and Dropbox Handlers ==
The [http://aminet.net/package/comm/tcp/AmigaCloudHandlers Amiga Cloud Handlers] pack contains handlers to mount both Google Drive and Dropbox cloud store-types. Write support for both handlers requires a licence key.

If you want mounted devices being activated immediately, and not when first accessed, change the wanted '''Activate = 0''' lines to '''Activate = 1''' lines in the DEVS:Cloud/cloud.mountlist file. Also, move mount lines from the S:user-startup file to the S:user-network-startup file, or somewhere else to be mounted later when the network connection is up for sure.

A registered version of Google Drive handler can also export Google documents to RTF, ODT, HTML, PDF, ZIP, DOCX, and TXT formats. It simply asks for the desired format when copying a Google document file from a mounted volume to any other location.
: [[File:NetworkDrives_GoogleDrive1.png|320px]]

== NFS ==
There aren't any native clients or servers for Sun's NFS protocol on MorphOS, but you can still use old 68k binaries for that purpose.

Read more about it [https://amiga23.wordpress.com/2014/11/21/how-to-use-nfs-shares-on-morphos/ here].

== FTPMount ==
FTP sites can be mounted as part of a filesystem with the FTPMount program.

An installation tutorial is to be found [https://amiga23.wordpress.com/2014/11/22/how-to-access-ftp-servers-via-the-filesystem-on-morphos/ here].

== Samba ==
There are few ports of the full Samba package, but they are quite old and usually just overkill in most cases. If [[Shell_Commands/SmbFS|SmbFS]] or [[Applications/RDesktop|RDesktop]] fills your needs, don't go for full Samba.

== Other ==

You might find other options and protocols to mount network drives, especially from 68k binaries. For example Envoy should work on MorphOS, to some degree, but be prepared to Google around and to face up to some issues when setting it up.

Mounting Network Drives

2019-11-16T22:36:44Z

NewSense:

== SmbFS ==
Windows shares, and Samba shares on other systems like Linux servers and NAS devices, can be mounted with the native [[Shell_Commands/SmbFS|SmbFS]] Shell command which is included with MorphOS. You shouldn't install any third party versions, because the included command is the most up-to-date and compatible version available, and it also has 64-bit I/O support.

The ''SYS:MorphOS/Locale/Help/english/SmbFS.txt'' file contains a detailed description of all [[Shell_Commands/SmbFS|SmbFS]] options, but in most cases you'll be fine with just few basic options.

=== A simple example ran from the shell ===
'''SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
Connected '//win7/sharedstuff' to 'Win7_share:'; "Break 5" or [Ctrl-C] to stop...

The VOLUME option specifies a volume name for the mounted device. Without it the device would only be accessible with its device name and no icon would appear on the Ambient desktop. Any name you want will be fine.

The first part of the SERVICE option contains a remote file server's name as seen, for example, on the network computers list on Windows. It is followed by a share name, which would be seen if you'd open a network computer on Windows. The server name is ''win7'' and the share name is ''sharedstuff'' in this case.

The share can be unmounted by pressing ''CTRL C'' keyboard combination when started like this.

The server name should work as it is, but if the host can't be found for some reason, you could try to add it to the Hosts settings in the MorphOS preferences.
: [[File:MorphOS_Preferences_Hosts.png|320px]]

If you want to start the [[Shell_Commands/SmbFS|SmbFS]] command as a background process from the Shell, the S:user-network-startup file, or anywhere else, you can launch it with the [[Shell_Commands/Run|Run]] command. The ''>NIL:'' redirect ensures that no output windows will pop up either.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''

There are several ways to unmount the share now, but the easiest is to use the Eject [[Screenbar_Modules|screenbar module]] or the [[Shell_Commands/UnMount|UnMount]] command.
: [[File:NetworkDrives_SmbFS_Eject.png]]

If you replace the PASSWORD option with the ASKPASSWORD option, you'll get a requester asking for the password.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=MorphOS_Rulez ASKPASSWORD VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
: [[File:NetworkDrives_SmbFS_PW.png]]

== Ssh2FS ==
The built-in [[Shell_Commands/Ssh2FS|Ssh2FS]] command can be used to mount a remote SFTP share on your local MorphOS machine. Practically all remote servers you can access using a SSH2 client can also be mounted as part of the filesystem with this command.

The ''SYS:MorphOS/Locale/Help/english/Ssh2FS.readme'' file contains a detailed description of all [[Shell_Commands/Ssh2FS|Ssh2FS]] the options.

=== Requirements ===
Ssh2FS needs a home directory for the user, and that directory must be set to ''MorphOS Preferences -> Users -> Home Dir'' or provided as a Command-Line argument to Ssh2FS (''HOME=path:dir/'').

It is recommended to set the home directory in the MorphOS Preferences for easier use later on.
# Create a new directory somewhere. ''SYS:Home'', for instance.
# Set this directory to ''MorphOS Preferences -> Users -> Home Dir'' and save settings. A ''HOME:'' assign is created automatically to point into this directory.

=== Examples ===
Here are some examples to run from the Shell. '''Bold lines''' are what you need to type into the Shell.

==== Mounting with the Password Prompt ====
This will ask for a password for the "linuxuser" account, and mounts the remote server with "Linux" as a volume name. A drive icon with that name will appear on the Ambient desktop.
'''ssh2fs linuxuser@192.168.1.4 Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Host '192.168.1.4' is not known!
Add host to known_hosts file ? (y/n)'''y'''
Enter password:
SFTP connection established.

Now you can unmount the share by pressing the ''CTRL C'' keyboard combination, by using the Eject [[Screenbar_Modules|screenbar module]], or with the [[Shell_Commands/UnMount|UnMount]] Shell command (''UnMount Linux:'').

The previous example mounted the root directory of the server, but this would only mount your own home directory.
'''ssh2fs linuxuser@192.168.1.4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

If you have mapped a hostname for your server's IP address from ''MorphOS Preferences -> Hosts'', that will also work, as well as any URL to remote servers on the Internet. Here we have ''linux4'' set for the LAN address 192.168.1.4.
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

==== Passwordless Mounting ====
If you prefer to avoid entering the password, and do more automatic mounting of shares, a public key can be generated and used for authentication.
# Set a hostname for your machine in ''MorphOS Preferences -> Network -> Host and DNS'' if not already set
# Open the Shell, type '''SYS:Applications/RemoteShell/Files/ssh-keygen -t rsa''', and press the Enter key a few times (don't set the passphrase).
# Copy the resulting files (''id_rsa'' and ''id_rsa.pub'') to the ''.ssh'' directory in your MorphOS home directory. For example, '''Copy SYS:Applications/RemoteShell/Files/conf/id_rsa#? HOME:.ssh/'''
# Append the contents of the ''id_rsa.pub'' file to the ''~/.ssh/authorized_keys'' file on the server. There are several ways to do that, such as, these two (pick only one, and notice the double > character):
## Copy the file to the server, connect by an SSH client, execute ''cat id_rsa.pub >> ~/.ssh/authorized_keys''
## Mount your own remote ''home directory'' with Ssh2FS and the password option as mentioned in the previous section, type in the MorphOS Shell: '''Type HOME:.ssh/id_rsa.pub >> Linux:.ssh/authorized_keys'''

Now you should be able to mount the server without encountering a password prompt with the ''pk'' argument:
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
SFTP connection established.

==== Mounting as a Background Process ====
The previous examples required user interaction in the Shell, but if you want to start Ssh2FS mounts as a background processes, you'll have to use the
[[Shell_Commands/RunFS|RunFS]] command. Normally you would do that with the Run command, but that has some limitations in this case and so that's why the RunFS command is provided.

Note that you'll have to provide a path to the Ssh2FS location (''C:''), otherwise RunFS won't find it. In this example we'll also disable the output with the ''Q=QUIET'' argument.
'''runfs Q C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

If you want to open a new Ambient window automatically for the newly mounted share, you can use the ''O=OPEN'' argument.
'''runfs Q O C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

With the previous lines you can mount SFTP shares, for example, automatically on each boot from ''S:user-network-startup'', or manually from the menus or keyboard shortcuts.

=== Unmounting ===
As mentioned earlier, mounted Ssh2FS shares can be unmounted in several ways.
* Use the Eject [[Screenbar_Modules|screenbar module]]
* Use the [[Shell_Commands/UnMount|UnMount]] Shell command: ''UnMount VolumeName:''
* Send a ''CTRL C'' signal to the Ssh2FS task, for example, by keyboard, using the [[Shell_Commands/Break|Break]] command, or using the [[Utilities/TaskManager|TaskManager]] utility.

== NetFS Revised ==
[http://aminet.net/package/comm/net/NetFS-revised NetFS Revised] allows the mounting of drives between MorphOS and AmigaOS systems. It is the best alternative to share files between Amiga compatible systems, because it preserves protection bits and other Amiga-like file properties. NetFS Revised also contains a tool to access ARexx ports remotely.

Here's a step-by-step guide of how to install it on MorphOS.

# Copy contents of the '''NetFS/SYS.MorphOS/''' directory to your '''SYS:''' partition
# Copy '''NetFS/Prefs/Env-Archive/netfs-server.config''' to '''ENVARC:'''
# (Optionally) Copy '''NetFS/Devs/DOSDrivers/ANETFS0''' to '''SYS:Storage/DOSDrivers/''' (if you want to mount a drive with a mountlist later)
# (Optionally) Copy '''NetFS/Help/english/NetFS.guide''' to '''HELP:english/''' (to keep the documentation available)
# Add '''amiganetfs 2500/tcp''', '''amiganetfs 2500/udp''', and '''amiganetfsprobe 2501/udp''' lines to the '''ENVARC:sys/net/services''' file. [[File:NetworkDrives_NetFS1.png|480px]]
# Add '''amiganetfs stream tcp nowait root C:InetD/netfs-server''' and '''amiganetfs dgram udp wait root C:InetD/netfs-server''' lines to the '''ENVARC:sys/net/inetd.conf''' file. If you don't plan to use the system as a server, you may leave it commented by starting the line with the # character, but better add the line there for any future use. [[File:NetworkDrives_NetFS2.png|480px]]
# Edit the last line on the '''ENVARC:netfs-server.config''' file to your liking on the server machine. In this example we'll allow access to the Work: partition with a specified login and password. [[File:NetworkDrives_NetFS3.png|480px]]
# '''Reboot''' the machine before trying it out.

The server works automatically, and you just need to connect to it from a client machine. We can mount the server's Work: partition by running the NetMount command on the client machine. Server's IP address is 192.168.1.10 in this example.

'''NetMount 192.168.1.10 Work: NetFS0: LOGIN=morphos PASS=rulez''' mounts the remote Work: partition as a local device called NetFS0:. The local device name can be anything you want, but NetMount creates the volume name automatically by adding the address after the remote volume name.
: [[File:NetworkDrives_NetFS4.png|480px]]

A better solution is to add a hostname for the server IP address, if you haven't done that already, and use that instead of the numerical address. Let's remove the mount with the [[Shell_Commands/UnMount|UnMount]] command and add a hostname on the Hosts settings in the MorphOS preferences.
: [[File:NetworkDrives_NetFS5.png|480px]]

So, let's try that again with the '''NetMount pb Work: NetFS0: LOGIN=morphos PASS=rulez''' command.
: [[File:NetworkDrives_NetFS6.png|480px]]

If you want to unmount the shares with the Eject [[Screenbar_Modules|screenbar module]], you'll have to decide to use a certain pattern with device names you mount and add that pattern to the Eject module's settings. If you keep using device names like NetFS0, NetFS1, NetFS3, etc, you could add '''NetFS#[0-9]''' or '''NetFS#?''' or similar to the Unmount pattern.
: [[File:NetworkDrives_NetFS7.png|480px]] [[File:NetworkDrives_NetFS8.png|480px]]

Also if you want to have a new default icon for the previous devices, copy or create an icon named def_NetFSxdisk.info to the SYS:Prefs/Presets/Deficons/ directory. '''Copy SYS:Prefs/Presets/Deficons/def_SMBFSxdisk.info to SYS:Prefs/Presets/Deficons/def_NetFSxdisk.info''' which would then use the same icon with SmbFS and NetFS shares.

== RDesktop ==
The [[Applications/RDesktop|RDesktop]] application included in MorphOS displays a remote machine's desktop on your computer, but it can also mount a local directory on the remote machine. If you're using [[Applications/RDesktop|RDesktop]] to control a remote machine, it's a good way to share MorphOS files with the remote machine without needing to install any other services on your MorphOS computer.

Click the '''Options''' button on the RDesktopGUI window, open the '''Resources''' tab, and select a directory on the '''Mounted Directories''' group. The directory will be shown on the remote machine when you connect to it.
: [[File:MorphOS3_jPV_Rdesktop.png|320px]] [[File:RDesktop_netdisk_mount.png|320px|top]]

== Google Drive and Dropbox Handlers ==
The [http://aminet.net/package/comm/tcp/AmigaCloudHandlers Amiga Cloud Handlers] pack contains handlers to mount both Google Drive and Dropbox cloud store-types. Write support for both handlers requires a licence key.

If you want mounted devices being activated immediately, and not when first accessed, change the wanted '''Activate = 0''' lines to '''Activate = 1''' lines in the DEVS:Cloud/cloud.mountlist file. Also, move mount lines from the S:user-startup file to the S:user-network-startup file, or somewhere else to be mounted later when the network connection is up for sure.

A registered version of Google Drive handler can also export Google documents to RTF, ODT, HTML, PDF, ZIP, DOCX, and TXT formats. It simply asks for the desired format when copying a Google document file from a mounted volume to any other location.
: [[File:NetworkDrives_GoogleDrive1.png|320px]]

== NFS ==
There aren't any native clients or servers for Sun's NFS protocol on MorphOS, but you can still use old 68k binaries for that purpose.

Read more about it [https://amiga23.wordpress.com/2014/11/21/how-to-use-nfs-shares-on-morphos/ here].

== FTPMount ==
FTP sites can be mounted as part of a filesystem with the FTPMount program.

An installation tutorial is to be found [https://amiga23.wordpress.com/2014/11/22/how-to-access-ftp-servers-via-the-filesystem-on-morphos/ here].

== Samba ==
There are few ports of the full Samba package, but they are quite old and usually just overkill in most cases. If [[Shell_Commands/SmbFS|SmbFS]] or [[Applications/RDesktop|RDesktop]] fills your needs, don't go for full Samba.

== Other ==

You might find other options and protocols to mount network drives, especially from 68k binaries. For example Envoy should work on MorphOS, to some degree, but be prepared to Google around and to face up to some issues when setting it up.

Mounting Network Drives

2019-11-16T22:20:57Z

NewSense: /* SmbFS */

== SmbFS ==
Windows shares, and Samba shares on other systems like Linux servers and NAS devices, can be mounted with the native [[Shell_Commands/SmbFS|SmbFS]] Shell command which is included with MorphOS. You shouldn't install any third party versions, because the included command is the most up-to-date and compatible version available, and it also has 64-bit I/O support.

The ''SYS:MorphOS/Locale/Help/english/SmbFS.txt'' file contains a detailed description of all [[Shell_Commands/SmbFS|SmbFS]] options, but in most cases you'll be fine with just few basic options.

=== A simple example ran from the shell ===
'''SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
Connected '//win7/sharedstuff' to 'Win7_share:'; "Break 5" or [Ctrl-C] to stop...

The VOLUME option specifies a volume name for the mounted device. Without it the device would only be accessible with its device name and no icon would appear on the Ambient desktop. Any name you want will be fine.

The first part of the SERVICE option contains a remote file server's name as seen, for example, on the network computers list on Windows. It is followed by a share name, which would be seen if you'd open a network computer on Windows. The server name is ''win7'' and the share name is ''sharedstuff'' in this case.

The share can be unmounted by pressing ''CTRL C'' keyboard combination when started like this.

The server name should work as it is, but if the host can't be found for some reason, you could try to add it to the Hosts settings in the MorphOS preferences.
: [[File:MorphOS_Preferences_Hosts.png|320px]]

If you want to start the [[Shell_Commands/SmbFS|SmbFS]] command as a background process from the Shell, the S:user-network-startup file, or anywhere else, you can launch it with the [[Shell_Commands/Run|Run]] command. The ''>NIL:'' redirect ensures that no output windows will pop up either.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''

There are several ways to unmount the share now, but the easiest is to use the Eject [[Screenbar_Modules|screenbar module]] or the [[Shell_Commands/UnMount|UnMount]] command.
: [[File:NetworkDrives_SmbFS_Eject.png]]

If you replace the PASSWORD option with the ASKPASSWORD option, you'll get a requester asking for the password.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=MorphOS_Rulez ASKPASSWORD VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
: [[File:NetworkDrives_SmbFS_PW.png]]

== Ssh2FS ==
The built-in [[Shell_Commands/Ssh2FS|Ssh2FS]] command can be used to mount a remote SFTP share on your local MorphOS machine. Practically all remote servers you can access using a SSH2 client can also be mounted as part of the filesystem with this command.

The ''SYS:MorphOS/Locale/Help/english/Ssh2FS.readme'' file contains a detailed description of all [[Shell_Commands/Ssh2FS|Ssh2FS]] the options.

=== Requirements ===
Ssh2FS needs a home directory for the user, and that directory must be set to ''MorphOS Preferences -> Users -> Home Dir'' or provided as a Command-Line argument to Ssh2FS (''HOME=path:dir/'').

It is recommended to set the home directory in the MorphOS Preferences for easier use later on.
# Create a new directory somewhere. ''SYS:Home'', for instance.
# Set this directory to ''MorphOS Preferences -> Users -> Home Dir'' and save settings. A ''HOME:'' assign is created automatically to point into this directory.

=== Examples ===
Here are some examples to run from the Shell. '''Bold lines''' are what you need to type into the Shell.

==== Mounting with the Password Prompt ====
This will ask for a password for the "linuxuser" account, and mounts the remote server with "Linux" as a volume name. A drive icon with that name will appear on the Ambient desktop.
'''ssh2fs linuxuser@192.168.1.4 Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Host '192.168.1.4' is not known!
Add host to known_hosts file ? (y/n)'''y'''
Enter password:
SFTP connection established.

Now you can unmount the share by pressing the ''CTRL C'' keyboard combination, by using the Eject [[Screenbar_Modules|screenbar module]], or with the [[Shell_Commands/UnMount|UnMount]] Shell command (''UnMount Linux:'').

The previous example mounted the root directory of the server, but this would only mount your own home directory.
'''ssh2fs linuxuser@192.168.1.4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

If you have mapped a hostname for your server's IP address from ''MorphOS Preferences -> Hosts'', that will also work, as well as any URL to remote servers on the Internet. Here we have ''linux4'' set for the LAN address 192.168.1.4.
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

==== Passwordless Mounting ====
If you prefer to avoid entering the password, and do more automatic mounting of shares, a public key can be generated and used for authentication.
# Set a hostname for your machine in ''MorphOS Preferences -> Network -> Host and DNS'' if not already set
# Open the Shell, type '''SYS:Applications/RemoteShell/Files/ssh-keygen -t rsa''', and press the Enter key a few times (don't set the passphrase).
# Copy the resulting files (''id_rsa'' and ''id_rsa.pub'') to the ''.ssh'' directory in your MorphOS home directory. For example, '''Copy SYS:Applications/RemoteShell/Files/conf/id_rsa#? HOME:.ssh/'''
# Append the contents of the ''id_rsa.pub'' file to the ''~/.ssh/authorized_keys'' file on the server. There are several ways to do that, such as, these two (pick only one, and notice the double > character):
## Copy the file to the server, connect by an SSH client, execute ''cat id_rsa.pub >> ~/.ssh/authorized_keys''
## Mount your own remote ''home directory'' with Ssh2FS and the password option as mentioned in the previous section, type in the MorphOS Shell: '''Type HOME:.ssh/id_rsa.pub >> Linux:.ssh/authorized_keys'''

Now you should be able to mount the server without encountering a password prompt with the ''pk'' argument:
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
SFTP connection established.

==== Mounting as a Background Process ====
The previous examples required user interaction in the Shell, but if you want to start Ssh2FS mounts as a background processes, you'll have to use the
[[Shell_Commands/RunFS|RunFS]] command. Normally you would do that with the Run command, but that has some limitations in this case and so that's why the RunFS command is provided.

Note that you'll have to provide a path to the Ssh2FS location (''C:''), otherwise RunFS won't find it. In this example we'll also disable the output with the ''Q=QUIET'' argument.
'''runfs Q C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

If you want to open a new Ambient window automatically for the newly mounted share, you can use the ''O=OPEN'' argument.
'''runfs Q O C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

With the previous lines you can mount SFTP shares, for example, automatically on each boot from ''S:user-network-startup'', or manually from the menus or keyboard shortcuts.

=== Unmounting ===
As mentioned earlier, mounted Ssh2FS shares can be unmounted in several ways.
* Use the Eject [[Screenbar_Modules|screenbar module]]
* Use the [[Shell_Commands/UnMount|UnMount]] Shell command: ''UnMount VolumeName:''
* Send a ''CTRL C'' signal to the Ssh2FS task, for example, by keyboard, using the [[Shell_Commands/Break|Break]] command, or using the [[Utilities/TaskManager|TaskManager]] utility.

== NetFS Revised ==
[http://aminet.net/package/comm/net/NetFS-revised NetFS Revised] allows to mount drives between MorphOS and AmigaOS systems. It is the best alternative to share files between Amiga compatible systems, because it preserves protection bits and other Amiga-like file properties. NetFS Revised also contains a tool to access ARexx ports remotely.

Here's a step-by-step guide how to install it on MorphOS.

# Copy contents of the '''NetFS/SYS.MorphOS/''' directory to your '''SYS:''' partition
# Copy '''NetFS/Prefs/Env-Archive/netfs-server.config''' to '''ENVARC:'''
# (Optionally) Copy '''NetFS/Devs/DOSDrivers/ANETFS0''' to '''SYS:Storage/DOSDrivers/''' (if you want to mount a drive with a mountlist later)
# (Optionally) Copy '''NetFS/Help/english/NetFS.guide''' to '''HELP:english/''' (to keep the documentation available)
# Add '''amiganetfs 2500/tcp''', '''amiganetfs 2500/udp''', and '''amiganetfsprobe 2501/udp''' lines to the '''ENVARC:sys/net/services''' file. [[File:NetworkDrives_NetFS1.png|480px]]
# Add '''amiganetfs stream tcp nowait root C:InetD/netfs-server''' and '''amiganetfs dgram udp wait root C:InetD/netfs-server''' lines to the '''ENVARC:sys/net/inetd.conf''' file. If you don't plan to use the system as a server, you may leave it commented by starting the line with the # character, but better add the line there for the future use. [[File:NetworkDrives_NetFS2.png|480px]]
# Edit the last line on the '''ENVARC:netfs-server.config''' file to your liking on the server machine. In this example we'll allow access to the Work: partition with certain login and password. [[File:NetworkDrives_NetFS3.png|480px]]
# '''Reboot''' the machine before trying it out.

The server works automatically, and you just need to connect to it from a client machine. We can mount server's Work: partition by running the NetMount command on the client machine. Server's IP address is 192.168.1.10 in this example.

'''NetMount 192.168.1.10 Work: NetFS0: LOGIN=morphos PASS=rulez''' mounts the remote Work: partition as a local device called NetFS0:. The local device name can be anything you want, but NetMount creates the volume name automatically by adding the address after the remote volume name.
: [[File:NetworkDrives_NetFS4.png|480px]]

A prettier solution is to add a hostname for the server IP address, if you haven't done that already, and use that instead of the numerical address. Let's remove the mount with the [[Shell_Commands/UnMount|UnMount]] command and add a hostname on the Hosts settings in the MorphOS preferences.
: [[File:NetworkDrives_NetFS5.png|480px]]

And let's try again with the '''NetMount pb Work: NetFS0: LOGIN=morphos PASS=rulez''' command.
: [[File:NetworkDrives_NetFS6.png|480px]]

If you want to unmount the shares with the Eject [[Screenbar_Modules|screenbar module]], you'll have to decide to use a certain pattern with device names you mount and add the pattern to the Eject module's settings. If you keep using device names like NetFS0, NetFS1, NetFS3, etc, you could add '''NetFS#[0-9]''' or '''NetFS#?''' or similar to the Unmount pattern.
: [[File:NetworkDrives_NetFS7.png|480px]] [[File:NetworkDrives_NetFS8.png|480px]]

Also if you like to have a new default icon for the previous devices, copy or create an icon named def_NetFSxdisk.info to the SYS:Prefs/Presets/Deficons/ directory. '''Copy SYS:Prefs/Presets/Deficons/def_SMBFSxdisk.info to SYS:Prefs/Presets/Deficons/def_NetFSxdisk.info''' would use the same icon with SmbFS and NetFS shares.

== RDesktop ==
The [[Applications/RDesktop|RDesktop]] application included in MorphOS displays a remote machine's desktop on your computer, but it can also mount a local directory on the remote machine. If you're using [[Applications/RDesktop|RDesktop]] to control a remote machine, it's a good way to share MorphOS files to the remote machine without needing to install any other services on your MorphOS computer.

Click the '''Options''' button on the RDesktopGUI window, open the '''Resources''' tab, and select a directory on the '''Mounted Directories''' group. The directory will be shown on the remote machine when you connect to it.
: [[File:MorphOS3_jPV_Rdesktop.png|320px]] [[File:RDesktop_netdisk_mount.png|320px|top]]

== Google Drive and Dropbox Handlers ==
The [http://aminet.net/package/comm/tcp/AmigaCloudHandlers Amiga Cloud Handlers] pack contains handlers to mount both Google Drive and Dropbox cloud storages. Write support for both handlers requires a licence key.

If you want mounted devices being activated immediately, and not when first accessed, change the wanted '''Activate = 0''' lines to '''Activate = 1''' lines in the DEVS:Cloud/cloud.mountlist file. And move mount lines from the S:user-startup file to the S:user-network-startup file, or somewhere else to be mounted later when the network connection is up for sure.

A registered version of Google Drive handler can also export Google documents to RTF, ODT, HTML, PDF, ZIP, DOCX, and TXT formats. It simply asks the desired format when copying a Google document file from a mounted volume to any other location.
: [[File:NetworkDrives_GoogleDrive1.png|320px]]

== NFS ==
There aren't any native clients or servers for Sun's NFS protocol on MorphOS, but you can still use old 68k binaries for it.

Read more about it [https://amiga23.wordpress.com/2014/11/21/how-to-use-nfs-shares-on-morphos/ here].

== FTPMount ==
FTP sites can be mounted as part of a filesystem with the FTPMount program.

An installation tutorial is found [https://amiga23.wordpress.com/2014/11/22/how-to-access-ftp-servers-via-the-filesystem-on-morphos/ here].

== Samba ==
There are few ports of the full Samba package, but they are quite old and usually just overkill in most cases. If [[Shell_Commands/SmbFS|SmbFS]] or [[Applications/RDesktop|RDesktop]] fills your needs, don't go for full Samba.

== Other ==

You might find other options and protocols to mount network drives, especially from 68k binaries. For example Envoy should work on MorphOS to some degree, but be prepared to google around and face some issues when setting it up.

Mounting Network Drives

2019-11-16T22:19:14Z

NewSense: /* Mounting as a Background Process */

== SmbFS ==
Windows shares, and Samba shares on other systems like Linux servers and NAS devices, can be mounted with the native [[Shell_Commands/SmbFS|SmbFS]] shell command which is included with MorphOS. You shouldn't install any third party versions, because the included command is the most up-to-date and compatible version available, and it also has 64-bit I/O support.

The ''SYS:MorphOS/Locale/Help/english/SmbFS.txt'' file contains a detailed description of all [[Shell_Commands/SmbFS|SmbFS]] options, but in most cases you'll be fine with just few basic options.

=== A simple example ran from the shell ===
'''SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
Connected '//win7/sharedstuff' to 'Win7_share:'; "Break 5" or [Ctrl-C] to stop...

The VOLUME option specifies a volume name for the mounted device. Without it the device would only be accessible with its device name and no icon would appear on the Ambient desktop. Any name you want will be fine.

The first part of the SERVICE option contains a remote file server's name as seen, for example, on the network computers list on Windows. It is followed by a share name, which would be seen if you'd open a network computer on Windows. The server name is ''win7'' and the share name is ''sharedstuff'' in this case.

The share can be unmounted by pressing ''CTRL C'' keyboard combination when started like this.

The server name should work as it is, but if the host can't be found for some reason, you could try to add it to the Hosts settings in the MorphOS preferences.
: [[File:MorphOS_Preferences_Hosts.png|320px]]

If you want to start the [[Shell_Commands/SmbFS|SmbFS]] command as a background process from the shell, the S:user-network-startup file, or anywhere else, you can launch it with the [[Shell_Commands/Run|Run]] command. The ''>NIL:'' redirect ensures that no output windows will pop up either.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''

There are several ways to unmount the share now, but the easiest is to use the Eject [[Screenbar_Modules|screenbar module]] or the [[Shell_Commands/UnMount|UnMount]] command.
: [[File:NetworkDrives_SmbFS_Eject.png]]

If you replace the PASSWORD option with the ASKPASSWORD option, you'll get a requester asking for the password.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=MorphOS_Rulez ASKPASSWORD VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
: [[File:NetworkDrives_SmbFS_PW.png]]

== Ssh2FS ==
The built-in [[Shell_Commands/Ssh2FS|Ssh2FS]] command can be used to mount a remote SFTP share on your local MorphOS machine. Practically all remote servers you can access using a SSH2 client can also be mounted as part of the filesystem with this command.

The ''SYS:MorphOS/Locale/Help/english/Ssh2FS.readme'' file contains a detailed description of all [[Shell_Commands/Ssh2FS|Ssh2FS]] the options.

=== Requirements ===
Ssh2FS needs a home directory for the user, and that directory must be set to ''MorphOS Preferences -> Users -> Home Dir'' or provided as a Command-Line argument to Ssh2FS (''HOME=path:dir/'').

It is recommended to set the home directory in the MorphOS Preferences for easier use later on.
# Create a new directory somewhere. ''SYS:Home'', for instance.
# Set this directory to ''MorphOS Preferences -> Users -> Home Dir'' and save settings. A ''HOME:'' assign is created automatically to point into this directory.

=== Examples ===
Here are some examples to run from the Shell. '''Bold lines''' are what you need to type into the Shell.

==== Mounting with the Password Prompt ====
This will ask for a password for the "linuxuser" account, and mounts the remote server with "Linux" as a volume name. A drive icon with that name will appear on the Ambient desktop.
'''ssh2fs linuxuser@192.168.1.4 Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Host '192.168.1.4' is not known!
Add host to known_hosts file ? (y/n)'''y'''
Enter password:
SFTP connection established.

Now you can unmount the share by pressing the ''CTRL C'' keyboard combination, by using the Eject [[Screenbar_Modules|screenbar module]], or with the [[Shell_Commands/UnMount|UnMount]] Shell command (''UnMount Linux:'').

The previous example mounted the root directory of the server, but this would only mount your own home directory.
'''ssh2fs linuxuser@192.168.1.4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

If you have mapped a hostname for your server's IP address from ''MorphOS Preferences -> Hosts'', that will also work, as well as any URL to remote servers on the Internet. Here we have ''linux4'' set for the LAN address 192.168.1.4.
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

==== Passwordless Mounting ====
If you prefer to avoid entering the password, and do more automatic mounting of shares, a public key can be generated and used for authentication.
# Set a hostname for your machine in ''MorphOS Preferences -> Network -> Host and DNS'' if not already set
# Open the Shell, type '''SYS:Applications/RemoteShell/Files/ssh-keygen -t rsa''', and press the Enter key a few times (don't set the passphrase).
# Copy the resulting files (''id_rsa'' and ''id_rsa.pub'') to the ''.ssh'' directory in your MorphOS home directory. For example, '''Copy SYS:Applications/RemoteShell/Files/conf/id_rsa#? HOME:.ssh/'''
# Append the contents of the ''id_rsa.pub'' file to the ''~/.ssh/authorized_keys'' file on the server. There are several ways to do that, such as, these two (pick only one, and notice the double > character):
## Copy the file to the server, connect by an SSH client, execute ''cat id_rsa.pub >> ~/.ssh/authorized_keys''
## Mount your own remote ''home directory'' with Ssh2FS and the password option as mentioned in the previous section, type in the MorphOS Shell: '''Type HOME:.ssh/id_rsa.pub >> Linux:.ssh/authorized_keys'''

Now you should be able to mount the server without encountering a password prompt with the ''pk'' argument:
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
SFTP connection established.

==== Mounting as a Background Process ====
The previous examples required user interaction in the Shell, but if you want to start Ssh2FS mounts as a background processes, you'll have to use the
[[Shell_Commands/RunFS|RunFS]] command. Normally you would do that with the Run command, but that has some limitations in this case and so that's why the RunFS command is provided.

Note that you'll have to provide a path to the Ssh2FS location (''C:''), otherwise RunFS won't find it. In this example we'll also disable the output with the ''Q=QUIET'' argument.
'''runfs Q C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

If you want to open a new Ambient window automatically for the newly mounted share, you can use the ''O=OPEN'' argument.
'''runfs Q O C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

With the previous lines you can mount SFTP shares, for example, automatically on each boot from ''S:user-network-startup'', or manually from the menus or keyboard shortcuts.

=== Unmounting ===
As mentioned earlier, mounted Ssh2FS shares can be unmounted in several ways.
* Use the Eject [[Screenbar_Modules|screenbar module]]
* Use the [[Shell_Commands/UnMount|UnMount]] Shell command: ''UnMount VolumeName:''
* Send a ''CTRL C'' signal to the Ssh2FS task, for example, by keyboard, using the [[Shell_Commands/Break|Break]] command, or using the [[Utilities/TaskManager|TaskManager]] utility.

== NetFS Revised ==
[http://aminet.net/package/comm/net/NetFS-revised NetFS Revised] allows to mount drives between MorphOS and AmigaOS systems. It is the best alternative to share files between Amiga compatible systems, because it preserves protection bits and other Amiga-like file properties. NetFS Revised also contains a tool to access ARexx ports remotely.

Here's a step-by-step guide how to install it on MorphOS.

# Copy contents of the '''NetFS/SYS.MorphOS/''' directory to your '''SYS:''' partition
# Copy '''NetFS/Prefs/Env-Archive/netfs-server.config''' to '''ENVARC:'''
# (Optionally) Copy '''NetFS/Devs/DOSDrivers/ANETFS0''' to '''SYS:Storage/DOSDrivers/''' (if you want to mount a drive with a mountlist later)
# (Optionally) Copy '''NetFS/Help/english/NetFS.guide''' to '''HELP:english/''' (to keep the documentation available)
# Add '''amiganetfs 2500/tcp''', '''amiganetfs 2500/udp''', and '''amiganetfsprobe 2501/udp''' lines to the '''ENVARC:sys/net/services''' file. [[File:NetworkDrives_NetFS1.png|480px]]
# Add '''amiganetfs stream tcp nowait root C:InetD/netfs-server''' and '''amiganetfs dgram udp wait root C:InetD/netfs-server''' lines to the '''ENVARC:sys/net/inetd.conf''' file. If you don't plan to use the system as a server, you may leave it commented by starting the line with the # character, but better add the line there for the future use. [[File:NetworkDrives_NetFS2.png|480px]]
# Edit the last line on the '''ENVARC:netfs-server.config''' file to your liking on the server machine. In this example we'll allow access to the Work: partition with certain login and password. [[File:NetworkDrives_NetFS3.png|480px]]
# '''Reboot''' the machine before trying it out.

The server works automatically, and you just need to connect to it from a client machine. We can mount server's Work: partition by running the NetMount command on the client machine. Server's IP address is 192.168.1.10 in this example.

'''NetMount 192.168.1.10 Work: NetFS0: LOGIN=morphos PASS=rulez''' mounts the remote Work: partition as a local device called NetFS0:. The local device name can be anything you want, but NetMount creates the volume name automatically by adding the address after the remote volume name.
: [[File:NetworkDrives_NetFS4.png|480px]]

A prettier solution is to add a hostname for the server IP address, if you haven't done that already, and use that instead of the numerical address. Let's remove the mount with the [[Shell_Commands/UnMount|UnMount]] command and add a hostname on the Hosts settings in the MorphOS preferences.
: [[File:NetworkDrives_NetFS5.png|480px]]

And let's try again with the '''NetMount pb Work: NetFS0: LOGIN=morphos PASS=rulez''' command.
: [[File:NetworkDrives_NetFS6.png|480px]]

If you want to unmount the shares with the Eject [[Screenbar_Modules|screenbar module]], you'll have to decide to use a certain pattern with device names you mount and add the pattern to the Eject module's settings. If you keep using device names like NetFS0, NetFS1, NetFS3, etc, you could add '''NetFS#[0-9]''' or '''NetFS#?''' or similar to the Unmount pattern.
: [[File:NetworkDrives_NetFS7.png|480px]] [[File:NetworkDrives_NetFS8.png|480px]]

Also if you like to have a new default icon for the previous devices, copy or create an icon named def_NetFSxdisk.info to the SYS:Prefs/Presets/Deficons/ directory. '''Copy SYS:Prefs/Presets/Deficons/def_SMBFSxdisk.info to SYS:Prefs/Presets/Deficons/def_NetFSxdisk.info''' would use the same icon with SmbFS and NetFS shares.

== RDesktop ==
The [[Applications/RDesktop|RDesktop]] application included in MorphOS displays a remote machine's desktop on your computer, but it can also mount a local directory on the remote machine. If you're using [[Applications/RDesktop|RDesktop]] to control a remote machine, it's a good way to share MorphOS files to the remote machine without needing to install any other services on your MorphOS computer.

Click the '''Options''' button on the RDesktopGUI window, open the '''Resources''' tab, and select a directory on the '''Mounted Directories''' group. The directory will be shown on the remote machine when you connect to it.
: [[File:MorphOS3_jPV_Rdesktop.png|320px]] [[File:RDesktop_netdisk_mount.png|320px|top]]

== Google Drive and Dropbox Handlers ==
The [http://aminet.net/package/comm/tcp/AmigaCloudHandlers Amiga Cloud Handlers] pack contains handlers to mount both Google Drive and Dropbox cloud storages. Write support for both handlers requires a licence key.

If you want mounted devices being activated immediately, and not when first accessed, change the wanted '''Activate = 0''' lines to '''Activate = 1''' lines in the DEVS:Cloud/cloud.mountlist file. And move mount lines from the S:user-startup file to the S:user-network-startup file, or somewhere else to be mounted later when the network connection is up for sure.

A registered version of Google Drive handler can also export Google documents to RTF, ODT, HTML, PDF, ZIP, DOCX, and TXT formats. It simply asks the desired format when copying a Google document file from a mounted volume to any other location.
: [[File:NetworkDrives_GoogleDrive1.png|320px]]

== NFS ==
There aren't any native clients or servers for Sun's NFS protocol on MorphOS, but you can still use old 68k binaries for it.

Read more about it [https://amiga23.wordpress.com/2014/11/21/how-to-use-nfs-shares-on-morphos/ here].

== FTPMount ==
FTP sites can be mounted as part of a filesystem with the FTPMount program.

An installation tutorial is found [https://amiga23.wordpress.com/2014/11/22/how-to-access-ftp-servers-via-the-filesystem-on-morphos/ here].

== Samba ==
There are few ports of the full Samba package, but they are quite old and usually just overkill in most cases. If [[Shell_Commands/SmbFS|SmbFS]] or [[Applications/RDesktop|RDesktop]] fills your needs, don't go for full Samba.

== Other ==

You might find other options and protocols to mount network drives, especially from 68k binaries. For example Envoy should work on MorphOS to some degree, but be prepared to google around and face some issues when setting it up.

Mounting Network Drives

2019-11-16T22:17:46Z

NewSense: /* Ssh2FS */

== SmbFS ==
Windows shares, and Samba shares on other systems like Linux servers and NAS devices, can be mounted with the native [[Shell_Commands/SmbFS|SmbFS]] shell command which is included with MorphOS. You shouldn't install any third party versions, because the included command is the most up-to-date and compatible version available, and it also has 64-bit I/O support.

The ''SYS:MorphOS/Locale/Help/english/SmbFS.txt'' file contains a detailed description of all [[Shell_Commands/SmbFS|SmbFS]] options, but in most cases you'll be fine with just few basic options.

=== A simple example ran from the shell ===
'''SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
Connected '//win7/sharedstuff' to 'Win7_share:'; "Break 5" or [Ctrl-C] to stop...

The VOLUME option specifies a volume name for the mounted device. Without it the device would only be accessible with its device name and no icon would appear on the Ambient desktop. Any name you want will be fine.

The first part of the SERVICE option contains a remote file server's name as seen, for example, on the network computers list on Windows. It is followed by a share name, which would be seen if you'd open a network computer on Windows. The server name is ''win7'' and the share name is ''sharedstuff'' in this case.

The share can be unmounted by pressing ''CTRL C'' keyboard combination when started like this.

The server name should work as it is, but if the host can't be found for some reason, you could try to add it to the Hosts settings in the MorphOS preferences.
: [[File:MorphOS_Preferences_Hosts.png|320px]]

If you want to start the [[Shell_Commands/SmbFS|SmbFS]] command as a background process from the shell, the S:user-network-startup file, or anywhere else, you can launch it with the [[Shell_Commands/Run|Run]] command. The ''>NIL:'' redirect ensures that no output windows will pop up either.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''

There are several ways to unmount the share now, but the easiest is to use the Eject [[Screenbar_Modules|screenbar module]] or the [[Shell_Commands/UnMount|UnMount]] command.
: [[File:NetworkDrives_SmbFS_Eject.png]]

If you replace the PASSWORD option with the ASKPASSWORD option, you'll get a requester asking for the password.

'''Run >NIL: SmbFS WORKGROUP=workgroup USER=MorphOS_Rulez ASKPASSWORD VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''
: [[File:NetworkDrives_SmbFS_PW.png]]

== Ssh2FS ==
The built-in [[Shell_Commands/Ssh2FS|Ssh2FS]] command can be used to mount a remote SFTP share on your local MorphOS machine. Practically all remote servers you can access using a SSH2 client can also be mounted as part of the filesystem with this command.

The ''SYS:MorphOS/Locale/Help/english/Ssh2FS.readme'' file contains a detailed description of all [[Shell_Commands/Ssh2FS|Ssh2FS]] the options.

=== Requirements ===
Ssh2FS needs a home directory for the user, and that directory must be set to ''MorphOS Preferences -> Users -> Home Dir'' or provided as a Command-Line argument to Ssh2FS (''HOME=path:dir/'').

It is recommended to set the home directory in the MorphOS Preferences for easier use later on.
# Create a new directory somewhere. ''SYS:Home'', for instance.
# Set this directory to ''MorphOS Preferences -> Users -> Home Dir'' and save settings. A ''HOME:'' assign is created automatically to point into this directory.

=== Examples ===
Here are some examples to run from the Shell. '''Bold lines''' are what you need to type into the Shell.

==== Mounting with the Password Prompt ====
This will ask for a password for the "linuxuser" account, and mounts the remote server with "Linux" as a volume name. A drive icon with that name will appear on the Ambient desktop.
'''ssh2fs linuxuser@192.168.1.4 Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Host '192.168.1.4' is not known!
Add host to known_hosts file ? (y/n)'''y'''
Enter password:
SFTP connection established.

Now you can unmount the share by pressing the ''CTRL C'' keyboard combination, by using the Eject [[Screenbar_Modules|screenbar module]], or with the [[Shell_Commands/UnMount|UnMount]] Shell command (''UnMount Linux:'').

The previous example mounted the root directory of the server, but this would only mount your own home directory.
'''ssh2fs linuxuser@192.168.1.4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

If you have mapped a hostname for your server's IP address from ''MorphOS Preferences -> Hosts'', that will also work, as well as any URL to remote servers on the Internet. Here we have ''linux4'' set for the LAN address 192.168.1.4.
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pw'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
Enter password:
SFTP connection established.

==== Passwordless Mounting ====
If you prefer to avoid entering the password, and do more automatic mounting of shares, a public key can be generated and used for authentication.
# Set a hostname for your machine in ''MorphOS Preferences -> Network -> Host and DNS'' if not already set
# Open the Shell, type '''SYS:Applications/RemoteShell/Files/ssh-keygen -t rsa''', and press the Enter key a few times (don't set the passphrase).
# Copy the resulting files (''id_rsa'' and ''id_rsa.pub'') to the ''.ssh'' directory in your MorphOS home directory. For example, '''Copy SYS:Applications/RemoteShell/Files/conf/id_rsa#? HOME:.ssh/'''
# Append the contents of the ''id_rsa.pub'' file to the ''~/.ssh/authorized_keys'' file on the server. There are several ways to do that, such as, these two (pick only one, and notice the double > character):
## Copy the file to the server, connect by an SSH client, execute ''cat id_rsa.pub >> ~/.ssh/authorized_keys''
## Mount your own remote ''home directory'' with Ssh2FS and the password option as mentioned in the previous section, type in the MorphOS Shell: '''Type HOME:.ssh/id_rsa.pub >> Linux:.ssh/authorized_keys'''

Now you should be able to mount the server without encountering a password prompt with the ''pk'' argument:
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
SFTP connection established.

==== Mounting as a Background Process ====
The previous examples required user interaction in the shell, but if you want to start Ssh2FS mounts as a background processes, you'll have to use the
[[Shell_Commands/RunFS|RunFS]] command. Normally you would do that with the Run command, but that has some limitations in this case and so that's why the RunFS command is provided.

Note that you'll have to provide a path to the Ssh2FS location (''C:''), otherwise RunFS won't find it. In this example we'll also disable the output with the ''Q=QUIET'' argument.
'''runfs Q C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

If you want to open a new Ambient window automatically for the newly mounted share, you can use the ''O=OPEN'' argument.
'''runfs Q O C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''

With the previous lines you can mount SFTP shares, for example, automatically on each boot from ''S:user-network-startup'', or manually from the menus or keyboard shortcuts.

=== Unmounting ===
As mentioned earlier, mounted Ssh2FS shares can be unmounted in several ways.
* Use the Eject [[Screenbar_Modules|screenbar module]]
* Use the [[Shell_Commands/UnMount|UnMount]] Shell command: ''UnMount VolumeName:''
* Send a ''CTRL C'' signal to the Ssh2FS task, for example, by keyboard, using the [[Shell_Commands/Break|Break]] command, or using the [[Utilities/TaskManager|TaskManager]] utility.

== NetFS Revised ==
[http://aminet.net/package/comm/net/NetFS-revised NetFS Revised] allows to mount drives between MorphOS and AmigaOS systems. It is the best alternative to share files between Amiga compatible systems, because it preserves protection bits and other Amiga-like file properties. NetFS Revised also contains a tool to access ARexx ports remotely.

Here's a step-by-step guide how to install it on MorphOS.

# Copy contents of the '''NetFS/SYS.MorphOS/''' directory to your '''SYS:''' partition
# Copy '''NetFS/Prefs/Env-Archive/netfs-server.config''' to '''ENVARC:'''
# (Optionally) Copy '''NetFS/Devs/DOSDrivers/ANETFS0''' to '''SYS:Storage/DOSDrivers/''' (if you want to mount a drive with a mountlist later)
# (Optionally) Copy '''NetFS/Help/english/NetFS.guide''' to '''HELP:english/''' (to keep the documentation available)
# Add '''amiganetfs 2500/tcp''', '''amiganetfs 2500/udp''', and '''amiganetfsprobe 2501/udp''' lines to the '''ENVARC:sys/net/services''' file. [[File:NetworkDrives_NetFS1.png|480px]]
# Add '''amiganetfs stream tcp nowait root C:InetD/netfs-server''' and '''amiganetfs dgram udp wait root C:InetD/netfs-server''' lines to the '''ENVARC:sys/net/inetd.conf''' file. If you don't plan to use the system as a server, you may leave it commented by starting the line with the # character, but better add the line there for the future use. [[File:NetworkDrives_NetFS2.png|480px]]
# Edit the last line on the '''ENVARC:netfs-server.config''' file to your liking on the server machine. In this example we'll allow access to the Work: partition with certain login and password. [[File:NetworkDrives_NetFS3.png|480px]]
# '''Reboot''' the machine before trying it out.

The server works automatically, and you just need to connect to it from a client machine. We can mount server's Work: partition by running the NetMount command on the client machine. Server's IP address is 192.168.1.10 in this example.

'''NetMount 192.168.1.10 Work: NetFS0: LOGIN=morphos PASS=rulez''' mounts the remote Work: partition as a local device called NetFS0:. The local device name can be anything you want, but NetMount creates the volume name automatically by adding the address after the remote volume name.
: [[File:NetworkDrives_NetFS4.png|480px]]

A prettier solution is to add a hostname for the server IP address, if you haven't done that already, and use that instead of the numerical address. Let's remove the mount with the [[Shell_Commands/UnMount|UnMount]] command and add a hostname on the Hosts settings in the MorphOS preferences.
: [[File:NetworkDrives_NetFS5.png|480px]]

And let's try again with the '''NetMount pb Work: NetFS0: LOGIN=morphos PASS=rulez''' command.
: [[File:NetworkDrives_NetFS6.png|480px]]

If you want to unmount the shares with the Eject [[Screenbar_Modules|screenbar module]], you'll have to decide to use a certain pattern with device names you mount and add the pattern to the Eject module's settings. If you keep using device names like NetFS0, NetFS1, NetFS3, etc, you could add '''NetFS#[0-9]''' or '''NetFS#?''' or similar to the Unmount pattern.
: [[File:NetworkDrives_NetFS7.png|480px]] [[File:NetworkDrives_NetFS8.png|480px]]

Also if you like to have a new default icon for the previous devices, copy or create an icon named def_NetFSxdisk.info to the SYS:Prefs/Presets/Deficons/ directory. '''Copy SYS:Prefs/Presets/Deficons/def_SMBFSxdisk.info to SYS:Prefs/Presets/Deficons/def_NetFSxdisk.info''' would use the same icon with SmbFS and NetFS shares.

== RDesktop ==
The [[Applications/RDesktop|RDesktop]] application included in MorphOS displays a remote machine's desktop on your computer, but it can also mount a local directory on the remote machine. If you're using [[Applications/RDesktop|RDesktop]] to control a remote machine, it's a good way to share MorphOS files to the remote machine without needing to install any other services on your MorphOS computer.

Click the '''Options''' button on the RDesktopGUI window, open the '''Resources''' tab, and select a directory on the '''Mounted Directories''' group. The directory will be shown on the remote machine when you connect to it.
: [[File:MorphOS3_jPV_Rdesktop.png|320px]] [[File:RDesktop_netdisk_mount.png|320px|top]]

== Google Drive and Dropbox Handlers ==
The [http://aminet.net/package/comm/tcp/AmigaCloudHandlers Amiga Cloud Handlers] pack contains handlers to mount both Google Drive and Dropbox cloud storages. Write support for both handlers requires a licence key.

If you want mounted devices being activated immediately, and not when first accessed, change the wanted '''Activate = 0''' lines to '''Activate = 1''' lines in the DEVS:Cloud/cloud.mountlist file. And move mount lines from the S:user-startup file to the S:user-network-startup file, or somewhere else to be mounted later when the network connection is up for sure.

A registered version of Google Drive handler can also export Google documents to RTF, ODT, HTML, PDF, ZIP, DOCX, and TXT formats. It simply asks the desired format when copying a Google document file from a mounted volume to any other location.
: [[File:NetworkDrives_GoogleDrive1.png|320px]]

== NFS ==
There aren't any native clients or servers for Sun's NFS protocol on MorphOS, but you can still use old 68k binaries for it.

Read more about it [https://amiga23.wordpress.com/2014/11/21/how-to-use-nfs-shares-on-morphos/ here].

== FTPMount ==
FTP sites can be mounted as part of a filesystem with the FTPMount program.

An installation tutorial is found [https://amiga23.wordpress.com/2014/11/22/how-to-access-ftp-servers-via-the-filesystem-on-morphos/ here].

== Samba ==
There are few ports of the full Samba package, but they are quite old and usually just overkill in most cases. If [[Shell_Commands/SmbFS|SmbFS]] or [[Applications/RDesktop|RDesktop]] fills your needs, don't go for full Samba.

== Other ==

You might find other options and protocols to mount network drives, especially from 68k binaries. For example Envoy should work on MorphOS to some degree, but be prepared to google around and face some issues when setting it up.

Open Firmware

2018-09-01T03:14:49Z

NewSense: /* Accessing the User Interface */

== Preface ==
'''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.

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.

Output texts in these examples have been truncated in most cases to show only the information of interest.

== Accessing the User Interface ==
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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

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.

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.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
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.

=== Listing Aliases ===
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.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can also be input combined, on a single line:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found in the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type that as well:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a sub-directory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

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:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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.

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 "System:" and the SYS: '''assign''' points to it as well.

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.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells you that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" 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.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be achieved with this single line:
0 > boot hd:,\boot.img

And the output should then look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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.

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.

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.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
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.

As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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.

If we wanted to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & 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.

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.

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.

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.

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.

If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

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.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Open Firmware

2018-09-01T03:07:53Z

NewSense: /* Booting MorphOS ISO from USB */

== Preface ==
'''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.

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.

Output texts in these examples have been truncated in most cases to show only the information of interest.

== Accessing the User Interface ==
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard ('''Option''' key is sometimes marked as '''Alt''' (with a symbol/icon below it) as on Windows keyboards or 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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

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.

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.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
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.

=== Listing Aliases ===
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.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can also be input combined, on a single line:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found in the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type that as well:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a sub-directory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

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:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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.

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 "System:" and the SYS: '''assign''' points to it as well.

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.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells you that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" 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.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be achieved with this single line:
0 > boot hd:,\boot.img

And the output should then look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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.

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.

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.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
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.

As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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.

If we wanted to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & 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.

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.

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.

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.

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.

If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

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.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Open Firmware

2018-09-01T02:58:27Z

NewSense: /* Booting from CD */

== Preface ==
'''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.

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.

Output texts in these examples have been truncated in most cases to show only the information of interest.

== Accessing the User Interface ==
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard ('''Option''' key is sometimes marked as '''Alt''' (with a symbol/icon below it) as on Windows keyboards or 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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

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.

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.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
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.

=== Listing Aliases ===
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.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can also be input combined, on a single line:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found in the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type that as well:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a sub-directory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

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:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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.

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 "System:" and the SYS: '''assign''' points to it as well.

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.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells you that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" 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.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be achieved with this single line:
0 > boot hd:,\boot.img

And the output should then look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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.

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.

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.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
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.

As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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.

If we wanted to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & Installation / Update Guide] describes the basics of the USB booting, but let's cover few special cases here. If you can't access your FAT formatted USB stick, refer the official guide how to re-format it in the 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 adviced in the official guide. If you still have issues with the USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get the system booted.

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 entering to the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs have it in different directories (mac_ppc32 vs mac_ppc64). The files can be named otherwise 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.

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.

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.

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.

If you have a new enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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 reveals the full path to the USB stick, which can be used instead of the ''ud'' alias.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

If a USB stick isn't recognized 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 exsisting 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 recognizes HFS partitions, boot.img can be loaded from those.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Open Firmware

2018-09-01T02:51:31Z

NewSense: /* Boot Arguments */

== Preface ==
'''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.

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.

Output texts in these examples have been truncated in most cases to show only the information of interest.

== Accessing the User Interface ==
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard ('''Option''' key is sometimes marked as '''Alt''' (with a symbol/icon below it) as on Windows keyboards or 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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

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.

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.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
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.

=== Listing Aliases ===
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.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can also be input combined, on a single line:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found in the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type that as well:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a sub-directory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

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:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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.

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 "System:" and the SYS: '''assign''' points to it as well.

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.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells you that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" 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.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be achieved with this single line:
0 > boot hd:,\boot.img

And the output should then look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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.

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.

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.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
MorphOS documentation usually advices to boot the machine with the ''c'' key pressed, but that method can be a bit unreliable for a reason or another and you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, and that results 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 this graphical boot menu. Pressing the F12 key in the menu will eject the CD.

Besides the previously mentioned methods, there are also ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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 subdirectories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.

If we'd want to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & Installation / Update Guide] describes the basics of the USB booting, but let's cover few special cases here. If you can't access your FAT formatted USB stick, refer the official guide how to re-format it in the 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 adviced in the official guide. If you still have issues with the USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get the system booted.

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 entering to the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs have it in different directories (mac_ppc32 vs mac_ppc64). The files can be named otherwise 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.

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.

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.

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.

If you have a new enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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 reveals the full path to the USB stick, which can be used instead of the ''ud'' alias.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

If a USB stick isn't recognized 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 exsisting 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 recognizes HFS partitions, boot.img can be loaded from those.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Open Firmware

2018-09-01T02:44:12Z

NewSense: /* Basics */

== Preface ==
'''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.

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.

Output texts in these examples have been truncated in most cases to show only the information of interest.

== Accessing the User Interface ==
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard ('''Option''' key is sometimes marked as '''Alt''' (with a symbol/icon below it) as on Windows keyboards or 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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

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.

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.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
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.

=== Listing Aliases ===
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.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can also be input combined, on a single line:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found in the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type that as well:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a sub-directory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

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:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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.

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 "System:" and the SYS: '''assign''' points to it as well.

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.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells you that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" 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.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be achieved with this single line:
0 > boot hd:,\boot.img

And the output should then look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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 the 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.

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 it's unnecessary to change these settings normally.

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) form.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
MorphOS documentation usually advices to boot the machine with the ''c'' key pressed, but that method can be a bit unreliable for a reason or another and you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, and that results 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 this graphical boot menu. Pressing the F12 key in the menu will eject the CD.

Besides the previously mentioned methods, there are also ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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 subdirectories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.

If we'd want to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & Installation / Update Guide] describes the basics of the USB booting, but let's cover few special cases here. If you can't access your FAT formatted USB stick, refer the official guide how to re-format it in the 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 adviced in the official guide. If you still have issues with the USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get the system booted.

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 entering to the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs have it in different directories (mac_ppc32 vs mac_ppc64). The files can be named otherwise 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.

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.

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.

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.

If you have a new enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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 reveals the full path to the USB stick, which can be used instead of the ''ud'' alias.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

If a USB stick isn't recognized 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 exsisting 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 recognizes HFS partitions, boot.img can be loaded from those.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Open Firmware

2018-09-01T02:32:27Z

NewSense: /* Examining Devices */

== Preface ==
'''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.

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.

Output texts in these examples have been truncated in most cases to show only the information of interest.

== Accessing the User Interface ==
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard ('''Option''' key is sometimes marked as '''Alt''' (with a symbol/icon below it) as on Windows keyboards or 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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

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.

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.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
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.

=== Listing Aliases ===
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.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can also be input combined, on a single line:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found in the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type that as well:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a sub-directory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

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:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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 somehow comparable to Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at the later stage.

The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known by Open Firmware in any case. The ''Boot:'' partition only contains 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 be even unmounted from 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 "System:" and the SYS: assign will be pointing to it.

When booting manually from OF, you'll see some output lines on screen. There are two important lines which tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" indicates that the file has been booted and machine is running under MorphOS now. Problems after this stage are MorphOS related and if the MorphOS boot picture doesn't appear soon, MorphOS might not find a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (ctrl-cmd-cmd, fn-alt-alt) do also work at this stage even if there would be some other problems halting the boot process.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be made with this single line:
0 > boot hd:,\boot.img

And the output will look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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 the 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.

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 it's unnecessary to change these settings normally.

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) form.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
MorphOS documentation usually advices to boot the machine with the ''c'' key pressed, but that method can be a bit unreliable for a reason or another and you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, and that results 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 this graphical boot menu. Pressing the F12 key in the menu will eject the CD.

Besides the previously mentioned methods, there are also ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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 subdirectories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.

If we'd want to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & Installation / Update Guide] describes the basics of the USB booting, but let's cover few special cases here. If you can't access your FAT formatted USB stick, refer the official guide how to re-format it in the 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 adviced in the official guide. If you still have issues with the USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get the system booted.

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 entering to the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs have it in different directories (mac_ppc32 vs mac_ppc64). The files can be named otherwise 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.

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.

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.

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.

If you have a new enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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 reveals the full path to the USB stick, which can be used instead of the ''ud'' alias.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

If a USB stick isn't recognized 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 exsisting 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 recognizes HFS partitions, boot.img can be loaded from those.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Open Firmware

2018-09-01T02:21:09Z

NewSense: /* Environment Variables */

== Preface ==
'''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.

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.

Output texts in these examples have been truncated in most cases to show only the information of interest.

== Accessing the User Interface ==
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard ('''Option''' key is sometimes marked as '''Alt''' (with a symbol/icon below it) as on Windows keyboards or 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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

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.

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.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information of the selected device. Note that it depends of the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and so on.

=== Listing Aliases ===
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see few examples how to list that information.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can be given combined in one line too:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found under the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type it too:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a subdirectory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected before entering to the OF interface), so this does the same as the previous example:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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 somehow comparable to Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at the later stage.

The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known by Open Firmware in any case. The ''Boot:'' partition only contains 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 be even unmounted from 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 "System:" and the SYS: assign will be pointing to it.

When booting manually from OF, you'll see some output lines on screen. There are two important lines which tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" indicates that the file has been booted and machine is running under MorphOS now. Problems after this stage are MorphOS related and if the MorphOS boot picture doesn't appear soon, MorphOS might not find a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (ctrl-cmd-cmd, fn-alt-alt) do also work at this stage even if there would be some other problems halting the boot process.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be made with this single line:
0 > boot hd:,\boot.img

And the output will look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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 the 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.

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 it's unnecessary to change these settings normally.

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) form.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
MorphOS documentation usually advices to boot the machine with the ''c'' key pressed, but that method can be a bit unreliable for a reason or another and you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, and that results 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 this graphical boot menu. Pressing the F12 key in the menu will eject the CD.

Besides the previously mentioned methods, there are also ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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 subdirectories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.

If we'd want to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & Installation / Update Guide] describes the basics of the USB booting, but let's cover few special cases here. If you can't access your FAT formatted USB stick, refer the official guide how to re-format it in the 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 adviced in the official guide. If you still have issues with the USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get the system booted.

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 entering to the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs have it in different directories (mac_ppc32 vs mac_ppc64). The files can be named otherwise 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.

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.

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.

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.

If you have a new enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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 reveals the full path to the USB stick, which can be used instead of the ''ud'' alias.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

If a USB stick isn't recognized 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 exsisting 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 recognizes HFS partitions, boot.img can be loaded from those.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Open Firmware

2018-09-01T02:16:53Z

NewSense: /* Useful Commands */

== Preface ==
'''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.

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.

Output texts in these examples have been truncated in most cases to show only the information of interest.

== Accessing the User Interface ==
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard ('''Option''' key is sometimes marked as '''Alt''' (with a symbol/icon below it) as on Windows keyboards or 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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

The first value in the list is the current value and the second value is the default value. It's quite rare that you have to change these values, but it's interesting to learn more about your computer nevertheless.

One common case is to make Startup Manager (the boot menu you get by booting with the option/alt key pressed) quicker by disabling the netboot option. Let's change that as an example, and check that we succeeded.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information of the selected device. Note that it depends of the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and so on.

=== Listing Aliases ===
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see few examples how to list that information.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can be given combined in one line too:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found under the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type it too:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a subdirectory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected before entering to the OF interface), so this does the same as the previous example:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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 somehow comparable to Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at the later stage.

The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known by Open Firmware in any case. The ''Boot:'' partition only contains 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 be even unmounted from 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 "System:" and the SYS: assign will be pointing to it.

When booting manually from OF, you'll see some output lines on screen. There are two important lines which tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" indicates that the file has been booted and machine is running under MorphOS now. Problems after this stage are MorphOS related and if the MorphOS boot picture doesn't appear soon, MorphOS might not find a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (ctrl-cmd-cmd, fn-alt-alt) do also work at this stage even if there would be some other problems halting the boot process.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be made with this single line:
0 > boot hd:,\boot.img

And the output will look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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 the 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.

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 it's unnecessary to change these settings normally.

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) form.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
MorphOS documentation usually advices to boot the machine with the ''c'' key pressed, but that method can be a bit unreliable for a reason or another and you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, and that results 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 this graphical boot menu. Pressing the F12 key in the menu will eject the CD.

Besides the previously mentioned methods, there are also ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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 subdirectories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.

If we'd want to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & Installation / Update Guide] describes the basics of the USB booting, but let's cover few special cases here. If you can't access your FAT formatted USB stick, refer the official guide how to re-format it in the 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 adviced in the official guide. If you still have issues with the USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get the system booted.

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 entering to the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs have it in different directories (mac_ppc32 vs mac_ppc64). The files can be named otherwise 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.

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.

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.

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.

If you have a new enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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 reveals the full path to the USB stick, which can be used instead of the ''ud'' alias.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

If a USB stick isn't recognized 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 exsisting 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 recognizes HFS partitions, boot.img can be loaded from those.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Open Firmware

2018-09-01T02:13:29Z

NewSense: /* Preface */

== Preface ==
'''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.

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.

Output texts in these examples have been truncated in most cases to show only the information of interest.

== Accessing the User Interface ==
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard ('''Option''' key is sometimes marked as '''Alt''' (with a symbol/icon below it) as on Windows keyboards or 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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (ELF binary image like MorphOS boot.img or Forth script, for instance) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (a bit like ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

The first value in the list is the current value and the second value is the default value. It's quite rare that you have to change these values, but it's interesting to learn more about your computer nevertheless.

One common case is to make Startup Manager (the boot menu you get by booting with the option/alt key pressed) quicker by disabling the netboot option. Let's change that as an example, and check that we succeeded.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information of the selected device. Note that it depends of the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and so on.

=== Listing Aliases ===
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see few examples how to list that information.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can be given combined in one line too:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found under the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type it too:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a subdirectory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected before entering to the OF interface), so this does the same as the previous example:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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 somehow comparable to Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at the later stage.

The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known by Open Firmware in any case. The ''Boot:'' partition only contains 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 be even unmounted from 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 "System:" and the SYS: assign will be pointing to it.

When booting manually from OF, you'll see some output lines on screen. There are two important lines which tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" indicates that the file has been booted and machine is running under MorphOS now. Problems after this stage are MorphOS related and if the MorphOS boot picture doesn't appear soon, MorphOS might not find a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (ctrl-cmd-cmd, fn-alt-alt) do also work at this stage even if there would be some other problems halting the boot process.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be made with this single line:
0 > boot hd:,\boot.img

And the output will look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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 the 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.

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 it's unnecessary to change these settings normally.

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) form.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
MorphOS documentation usually advices to boot the machine with the ''c'' key pressed, but that method can be a bit unreliable for a reason or another and you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, and that results 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 this graphical boot menu. Pressing the F12 key in the menu will eject the CD.

Besides the previously mentioned methods, there are also ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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 subdirectories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.

If we'd want to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & Installation / Update Guide] describes the basics of the USB booting, but let's cover few special cases here. If you can't access your FAT formatted USB stick, refer the official guide how to re-format it in the 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 adviced in the official guide. If you still have issues with the USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get the system booted.

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 entering to the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs have it in different directories (mac_ppc32 vs mac_ppc64). The files can be named otherwise 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.

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.

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.

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.

If you have a new enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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 reveals the full path to the USB stick, which can be used instead of the ''ud'' alias.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

If a USB stick isn't recognized 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 exsisting 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 recognizes HFS partitions, boot.img can be loaded from those.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Open Firmware

2018-09-01T02:04:50Z

NewSense: /* Accessing the User Interface */

== Preface ==
'''Open Firmware''' ('''OF''') is a computer firmware system, similar to BIOS on PC, found in all MorphOS compatible Macs. Pegasos, Pegasos II, and Efika also have an Open Firmware based firmware implementation, but with small differences to the Mac firmware.

Open Firmware has a command-line based user interface, which can be used to control the boot process and other things. This tutorial focuses on useful tips and tricks on the user interface by selected examples. The examples have been tested under PowerPC Macs, but may also work under bPlan machines to some degree.

Output texts in the examples have been truncated in most cases to show only the interesting information.

== Accessing the User Interface ==
Hold down the '''Command-Option-O-F''' key combination on a Mac keyboard ('''Option''' key is sometimes marked as '''Alt''' (with a symbol/icon below it) as on Windows keyboards or 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.

<nowiki>
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50
Copyright 1994-2005 Apple Computer, Inc.
All Rights Reserved.

Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11

To continue booting, type "mac-boot" and press return.
To shut down, type "shut-down" and press return.

Release keys to continue!

ok
0 > _
</nowiki>

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.

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].

== Useful Commands ==
* '''mac-boot''' - Continues booting from the current OF state
* '''reset-all''' - Resets the machine to the power-on state and reboots
* '''shut-down''' - Shuts down the machine
* '''load <file> <args>''' - Loads an OF code file (ELF binary image like MorphOS boot.img or Forth script, for instance) into memory
* '''go''' - Runs/boots the loaded file
* '''boot <file> <args>''' - Loads an OF code file and boots it
* '''printenv''' - Prints environment variable values
* '''setenv''' - Sets environment variable values
* '''devalias''' - Displays a list of ''aliases'' for devices (a bit like ''assigns'' on MorphOS)
* '''.properties''' - Displays a list of properties for the selected device
* '''ls''' - Displays contents of the current path in the device tree
* '''pwd''' - Displays the current path within the device tree
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)
* '''dir''' - Lists files on a partition

== Environment Variables ==
Use the ''printenv'' command to list all environment variable values.

<nowiki>
0 > printenv
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian? false false
real-mode? false false
auto-boot? true true
skip-netboot? false false
</nowiki>

The first value in the list is the current value and the second value is the default value. It's quite rare that you have to change these values, but it's interesting to learn more about your computer nevertheless.

One common case is to make Startup Manager (the boot menu you get by booting with the option/alt key pressed) quicker by disabling the netboot option. Let's change that as an example, and check that we succeeded.

<nowiki>
0 > setenv skip-netboot? true
0 > printenv skip-netboot?
-------------- Partition: common -------- Signature: 0x70 ---------------
skip-netboot? true false
</nowiki>

== Examining Devices ==
The ''dev'' command selects a device to be examined, and ''.properties'', ''ls'', and ''dir'' commands can be used to print information of the selected device. Note that it depends of the device type if these commands will print something. ''dir'' only works for devices containing a filesystem, and so on.

=== Listing Aliases ===
A special ''/aliases'' device contains information about shortcuts (aliases) to different hardware devices. Let's see few examples how to list that information.

The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:
<nowiki>
0 > dev /aliases
0 > .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

The commands can be given combined in one line too:
<nowiki>
0 > dev /aliases .properties
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:
<nowiki>
0 > devalias
name aliases
pci0 /pci@f0000000
agp /pci@f0000000
pci1 /pci@f2000000
pci2 /pci@f4000000
usb0 /pci@f2000000/@15
usb1 /pci@f2000000/@15,1
usb2 /pci@f2000000/@15,2
hd /pci@f4000000/ata-6@d/disk@0
cd /pci@f4000000/ata-6@d/disk@1
ud /pci@f2000000/usb@15,1/disk@1
</nowiki>

=== Other Useful Properties ===
''.properties'' on the root device shows the computer specs:
<nowiki>
0 > dev / .properties
model PowerBook5,9
compatible PowerBook5,9
MacRISC3
Power Macintosh

serial-number SX0
</nowiki>

The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:
<nowiki>
0 > dev enet .properties
vendor-id 0000106b
device-id 0000006b
name ethernet
device_type network
local-mac-address 001124e3 6666
</nowiki>

=== Listing Devices ===
The ''ls'' command lists devices found under the current device in the device tree:
<nowiki>
0 > dev usb1 ls
ff9e1650 /disk@1
ff9e1a28: /device@2
ff9e1c48: /keyboard@0
ff9e1f88: /mouse@1
ff9e2230: /interface@2
</nowiki>

=== Listing Files ===
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.

Syntax of the ''dir'' command is:
'''dir disk:partition,path'''

* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory

Listing the root (\) directory from the default partition on the default HD (this is usually the Boot: partition on a MorphOS system). The "," character could be omitted in certain cases, but it's safer to type it too:
<nowiki>
0 > dir hd:,\
</nowiki>

Listing the root directory from the first partition on the (default) HD:
<nowiki>
0 > dir hd:1,\
</nowiki>

Listing the root directory from a CD:
<nowiki>
0 > dir cd:,\
</nowiki>

Listing a subdirectory from a CD:
<nowiki>
0 > dir cd:,\mac_ppc32
</nowiki>

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):
<nowiki>
0 > dir usb1/disk@1:,\
</nowiki>

Newer firmware versions create the ''ud'' alias for a USB mass storage device connected to the machine (if it's been connected before entering to the OF interface), so this does the same as the previous example:
<nowiki>
0 > dir ud:,\
</nowiki>

== Booting MorphOS ==
=== Basics ===
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 somehow comparable to Amiga's Kickstart. Open Firmware just loads and boots the file, and the rest is handled by MorphOS after that. In case of errors, it's important to distinguish if loading of the boot image failed or does the error occur at the later stage.

The ''boot.img'' file usually resides on a special HFS formatted ''Boot:'' partition on Macs, or on a partition that has a filesystem known by Open Firmware in any case. The ''Boot:'' partition only contains 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 be even unmounted from 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 "System:" and the SYS: assign will be pointing to it.

When booting manually from OF, you'll see some output lines on screen. There are two important lines which tell you the boot stage. This can be demonstrated well with the ''load'' and ''go'' commands.

Type in this line (if you have a MorphOS installation on your HD):
0 > load hd:,\boot.img

And you'll see output like this:
<nowiki>
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF
ok
0 > _
</nowiki>

"Loading ELF" tells that the file has been found and loaded.

The file can be booted with the ''go'' command then:
<nowiki>
0 > go
DO-QUIESCE finished_
</nowiki>

"DO-QUIESCE finished" indicates that the file has been booted and machine is running under MorphOS now. Problems after this stage are MorphOS related and if the MorphOS boot picture doesn't appear soon, MorphOS might not find a device or image to boot from, or there might be driver or compatibility issues. MorphOS reset keys (ctrl-cmd-cmd, fn-alt-alt) do also work at this stage even if there would be some other problems halting the boot process.

A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.

The previous example can be made with this single line:
0 > boot hd:,\boot.img

And the output will look like this:
<nowiki>
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950

Loading ELF

DO-QUIESCE finished_
</nowiki>

=== Boot Arguments ===
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 the 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.

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 it's unnecessary to change these settings normally.

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) form.

* '''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 ":" character can be omitted. For example, "bootdevice=dh1" works, but "bootdevice=System" doesn't.
* '''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, "bootimage=umsd0:morphos-3.11.iso", "bootimage=dh2:morphos-3.11.iso".
* '''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.

=== Examples ===
==== Booting from CD ====
MorphOS documentation usually advices to boot the machine with the ''c'' key pressed, but that method can be a bit unreliable for a reason or another and you might end up in a situation where a boot image has been loaded from a HD and the actual system from a CD, and that results 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 this graphical boot menu. Pressing the F12 key in the menu will eject the CD.

Besides the previously mentioned methods, there are also ways to boot a CD from the Open Firmware prompt.

To boot any inserted CD that is bootable on Macs:
0 > boot cd:,\\:tbxi

"\\" 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 "Loading ELF" & "DO-QUIESCE finished" lines) if you need some debug output.

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.

List the contents of the CD:
<nowiki>
0 > dir cd:,\

Volume: MorphOSBoot
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
94 07/04/2018 04:54:42 ???? ???? .morphosid
2287135 07/04/2018 04:03:02 boot UNIX boot.img
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img
01/01/1904 00:00:00 *mac_ppc32
01/01/1904 00:00:00 mac_ppc64
</nowiki>

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 subdirectories, ''mac_ppc32'' contains the ''boot.img'' file for G4 Macs and ''mac_ppc64'' for G5 Macs. The ''blessed'' directory is marked with an asterisk.

If we'd want to boot the CD on a G5 Mac:
<nowiki>
0 > dir cd:,\mac_ppc64

Size/ GMT File/Dir
bytes date time TYPE CRTR Name
1499688 07/04/2018 04:03:02 boot UNIX boot.img

ok
0 > boot cd:,\mac_ppc64\boot.img bd cd0
</nowiki>

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.

To boot into the MorphOS boot menu on a G5 Mac:
0 > boot cd:,\mac_ppc64\boot.img bm

And the same for a G4 Mac:
0 > boot cd:,\mac_ppc32\boot.img bm

On a G4 Mac you could also use the ''blessed'' directory as a shortcut:
0 > boot cd:,\\boot.img bm

==== Booting MorphOS ISO from USB ====
The [http://www.morphos.de/guide/usb-boot Official MorphOS USB Boot & Installation / Update Guide] describes the basics of the USB booting, but let's cover few special cases here. If you can't access your FAT formatted USB stick, refer the official guide how to re-format it in the 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 adviced in the official guide. If you still have issues with the USB stick detection in OF or can't format the stick properly, this section of the tutorial provides some alternative methods to get the system booted.

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 entering to the OF user interface. The boot.img file can be obtained from a MorphOS installation CD/ISO, but remember that G4 and G5 Macs have it in different directories (mac_ppc32 vs mac_ppc64). The files can be named otherwise 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.

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.

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.

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.

If you have a new enough Open Firmware, booting the ISO file from a USB stick is easy:
0 > boot ud:,\boot.img bi umsd0:morphos.iso

If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:
0 > dir ud:,\

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 reveals the full path to the USB stick, which can be used instead of the ''ud'' alias.

<nowiki>
0 > dev usb0 ls
ok
0 > dev usb1 ls
ff9e1650: /disk@1
0 > dir usb1/disk@1:,\
Volume: USB
258048000 07-24-2018 18:34:24 morphos.iso
1501436 07-04-2018 04:03:02 boot.img
ok
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso
</nowiki>

If the stick is connected to a USB hub, the path just gets deeper in the OF tree:
<nowiki>
0 > dev usb1 ls
ff9e1650: /hub@1
ff9e1860: /disk@4
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso
</nowiki>

If a USB stick isn't recognized 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 exsisting 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 recognizes HFS partitions, boot.img can be loaded from those.

List the contents of the partitions until you find the correct partition where you copied the new boot.img file.
<nowiki>
0 > dir hd:1,\
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device
ok
0 > dir hd:2,\

Volume: OSX
Size/ GMT File/Dir
bytes date time TYPE CRTR Name
07/22/2017 07:27:40 Applications
09/27/2016 09:59:40 bin
1501436 07-04-2018 04:03:02 ???? UNIX boot.img
ok
0 > boot hd:2,\boot.img bi umsd0:morphos.iso
</nowiki>

Hardware Compatibility

2018-08-01T06:51:16Z

NewSense: /* Keyboards */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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 let us know so correction(s) can be made.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Apple A1016 Wireless BlueTooth (BT) keyboard - Works in 3.11 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Logitech T-RB22 Wireless Trackball (USB2) - Works in 3.11
* Labtec Optical Mouse 800 - Works in 3.10
* MicroSoft Trackball Explorer v1.0 (USB2) - Works in 3.11 (PS/2->USB2 adapter required)
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* HP 2500 Color LaserJet - Works in 3.11 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.11 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)
* C-Media soundcard (USB2) - Works partially in 3.11 (Output distorted/input untested, device exit locks-up USB)
* Griffin iMic (USB2) - Works partially in 3.11 (Output distorted, input untested, on device exit USB system freezes)

Printing

2018-07-14T01:47:01Z

NewSense: /* USBPAR: */

== General Information ==
MorphOS has two separate printing systems... etc etc

== Output Devices ==
=== USBPAR: ===
This option allows any '''Hardware Compatible''' PostScript printer, with a printer's compatible PPD file installed in the System:Preferences/ '''Printers''' (which is '''NOT''' the '''PRINTER''' Preferences option) with a USB2 port to be able to direct its output as PostScript data using the '''USBPAR''': device, which is by default '''NOT installed''' in the default setup of MorphOS, and requires the USBPAR: device to be transferred from the MOSSYS: (MorphOS root directory inside the '''System''': otherwise known as '''SYS''': folder) from within the MorphOS/Storage/DOSDrivers folder to the DEVS:DOSDrivers folder of the main System (SYS:) partition.

=== NETPAR: ===
The NETPAR: device can be used to print directly to network attached printers...

Configure a network connected printer from the NetPrinter settings in the MorphOS Preferences application...

Mount the NETPAR: device by....

=== PS: ===
PostScript output via TurboPrint by using GhostScript...

== Setting Up a Printer ==
=== TurboPrint ===
Open the '''Printer''' preferences from the MorphOS Preferences application...

=== PostScript ===
Open the '''Printers''' preferences from the MorphOS Preferences application...

== Printing From Applications ==

Printing

2018-07-14T01:34:34Z

NewSense: /* USBPAR: */

== General Information ==
MorphOS has two separate printing systems... etc etc

== Output Devices ==
=== USBPAR: ===
This option allows any '''Hardware Compatible''' PostScript printer, with a printer's compatible PPD file installed in the System:Preferences/ '''Printers''' (which is '''NOT''' the '''PRINTER''' Preferences option) with a USB2 port to be able to direct its output as PostScript data using the '''USBPAR''': device, which is by default '''NOT installed''' in the default setup of MorphOS, and requires the USBPAR: device to be transferred from the MOSSYS: (MorphOS root directory inside the '''System''': otherwise known as '''SYS''': folder) from within the Storage/DOSDrivers folder to the DEVS:DOSDrivers folder of the main System (SYS:) partition.

=== NETPAR: ===
The NETPAR: device can be used to print directly to network attached printers...

Configure a network connected printer from the NetPrinter settings in the MorphOS Preferences application...

Mount the NETPAR: device by....

=== PS: ===
PostScript output via TurboPrint by using GhostScript...

== Setting Up a Printer ==
=== TurboPrint ===
Open the '''Printer''' preferences from the MorphOS Preferences application...

=== PostScript ===
Open the '''Printers''' preferences from the MorphOS Preferences application...

== Printing From Applications ==

Printing

2018-07-14T01:09:12Z

NewSense: /* PS: */

== General Information ==
MorphOS has two separate printing systems... etc etc

== Output Devices ==
=== USBPAR: ===

=== NETPAR: ===
The NETPAR: device can be used to print directly to network attached printers...

Configure a network connected printer from the NetPrinter settings in the MorphOS Preferences application...

Mount the NETPAR: device by....

=== PS: ===
PostScript output via TurboPrint by using GhostScript...

== Setting Up a Printer ==
=== TurboPrint ===
Open the '''Printer''' preferences from the MorphOS Preferences application...

=== PostScript ===
Open the '''Printers''' preferences from the MorphOS Preferences application...

== Printing From Applications ==

Hardware Compatibility

2018-07-11T05:13:49Z

NewSense: /* USB Audio Devices */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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 let us know so correction(s) can be made.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.11 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Logitech T-RB22 Wireless Trackball (USB2) - Works in 3.11
* Labtec Optical Mouse 800 - Works in 3.10
* MicroSoft Trackball Explorer v1.0 (USB2) - Works in 3.11 (PS/2->USB2 adapter required)
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* HP 2500 Color LaserJet - Works in 3.11 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.11 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)
* C-Media soundcard (USB2) - Works partially in 3.11 (Output distorted/input untested, device exit locks-up USB)
* Griffin iMic (USB2) - Works partially in 3.11 (Output distorted, input untested, on device exit USB system freezes)

Hardware Compatibility

2018-07-11T05:11:33Z

NewSense: /* USB Audio Devices */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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 let us know so correction(s) can be made.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.11 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Logitech T-RB22 Wireless Trackball (USB2) - Works in 3.11
* Labtec Optical Mouse 800 - Works in 3.10
* MicroSoft Trackball Explorer v1.0 (USB2) - Works in 3.11 (PS/2->USB2 adapter required)
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* HP 2500 Color LaserJet - Works in 3.11 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.11 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* C-Media soundcard (USB2) - Works partially in 3.11 (Output distorted/input untested, device exit locks-up USB)
* Griffin iMic (USB2) - Works partially in 3.11 (Output distorted, input untested, on device exit USB system freezes)
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-07-11T04:31:16Z

NewSense: /* Mice */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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 let us know so correction(s) can be made.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.11 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Logitech T-RB22 Wireless Trackball (USB2) - Works in 3.11
* Labtec Optical Mouse 800 - Works in 3.10
* MicroSoft Trackball Explorer v1.0 (USB2) - Works in 3.11 (PS/2->USB2 adapter required)
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* HP 2500 Color LaserJet - Works in 3.11 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.11 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-07-11T04:25:36Z

NewSense: /* Scanners */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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 let us know so correction(s) can be made.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.11 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* HP 2500 Color LaserJet - Works in 3.11 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.11 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-07-11T04:24:09Z

NewSense: /* User Provided Reports */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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.

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 let us know so correction(s) can be made.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.11 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* HP 2500 Color LaserJet - Works in 3.11 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-07-11T04:18:17Z

NewSense: /* Printers */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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. This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.11 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* HP 2500 Color LaserJet - Works in 3.11 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-07-11T04:16:00Z

NewSense: /* Keyboards */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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. This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.11 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-07-11T04:14:49Z

NewSense: /* Game Controllers */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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. This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-07-11T04:00:09Z

NewSense: /* Keyboards */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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. This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards === (A to Z listed)
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-07-11T03:57:38Z

NewSense: /* Game Controllers */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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. This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library.

=== Game Controllers ===
* Logitech Rumble Pad wired (USB2) - Works in 3.11
* Saitek P380 Dual Analog wired (USB2) - Works in 3.11
* Sony Dualshock 3 (PS3) - Not working in 3.10
* Sony Dualshock 4 (PS4) - Works in 3.10
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)

=== Keyboards ===
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-06-30T01:21:09Z

NewSense: /* User Provided Reports */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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. This is as much '''your''' list, as it is also part of '''your''' Official MorphOS Library.

=== Game Controllers ===
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Sony Dualshock 4 (PS4) - Works in 3.10
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)
* Sony Dualshock 3 (PS3) - Not working in 3.10

=== Keyboards ===
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-06-28T03:23:52Z

NewSense: /* User Provided Reports */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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. This is as much '''your''' list, as it is part of '''our''' Official MorphOS Library.

=== Game Controllers ===
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Sony Dualshock 4 (PS4) - Works in 3.10
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)
* Sony Dualshock 3 (PS3) - Not working in 3.10

=== Keyboards ===
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-06-28T03:19:30Z

NewSense: /* User Provided Reports */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

'''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. This is as much '''your''' list, as it is part of '''our''' Official MorphOS Library.

=== Game Controllers ===
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Sony Dualshock 4 (PS4) - Works in 3.10
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)
* Sony Dualshock 3 (PS3) - Not working in 3.10

=== Keyboards ===
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-06-25T04:14:59Z

NewSense: /* Printers */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

=== Game Controllers ===
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Sony Dualshock 4 (PS4) - Works in 3.10
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)
* Sony Dualshock 3 (PS3) - Not working in 3.10

=== Keyboards ===
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For the '''Printers''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-06-25T04:06:02Z

NewSense: /* Scanners */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

=== Game Controllers ===
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Sony Dualshock 4 (PS4) - Works in 3.10
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)
* Sony Dualshock 3 (PS3) - Not working in 3.10

=== Keyboards ===
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in either '''Printer''' or '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For either '''Printer/s''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10 Including recent support for its ADF (Automatic Document Feeder).

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-06-25T04:03:11Z

NewSense: /* Printers */

== Official Information ==
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]].

== User Provided Reports ==
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 this] thread at MorphZone, or request an account to the MorphOS Library so you can edit the list yourself.

=== Game Controllers ===
* Speedlink Competition Pro USB - Works in 3.10
* Thrustmaster 360 Modena Pro Racing Wheel - Works in 3.10 (needs some setup for the ranges from the Poseidon prefs)
* Sony Dualshock 4 (PS4) - Works in 3.10
* Xbox 360 wired and wireless pads - Works in 3.10 (using a PC USB adapter)
* Sony Dualshock 3 (PS3) - Not working in 3.10

=== Keyboards ===
* Logitech UltraX Premium - Works in 3.10
* Rapoo E6300 Ultra-Slim BT keyboard for iPad - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)
* Apple A1016 Wireless (BlueTooth) keyboard - Works in 3.10 (NOTE: requires a machine which supports paired BT input devices, like Mac mini)

=== Mice ===
* Logitech M180 - Works in 3.10
* Logitech M185 - Works in 3.10
* Labtec Optical Mouse 800 - Works in 3.10
* Targus AMU3102EU - Works in 3.10

=== Printers ===
Please mention if the printer is tested with '''Printer''' preferences (TurboPrint) or '''Printers''' preferences (PPD based direct PostScript printing)
* Lexmark E342n - Works in 3.10 (HP_LaserJet5series in Printer and [http://support.lexmark.com/index?productCode=LEXMARK_E340&segment=SUPPORTproductCode%3D&viewlocale=pt_BR&page=content&searchid=1378996742336&actp=search&id=DR13234&locale=EN&userlocale=EN_US Lexmark_E342n_en.PPD] in Printers)
* HP 2500 Color LaserJet - Works in 3.10 (HP_Color LaserJet '''PostScript''' capable series, and works in either '''Printer''' or '''Printers''' with options of '''NETPAR:''', '''USBPAR:'''. For either '''Printer/s''' system it requires the Windows NT (2002) PPD file - '''HP2500_6.PPD''' or any other compatible PPD file. Available via these links, either in: [http://www.artica.fr/download/ppd/hp-en-hp2500_6.ppd.gz ENGLISH] or [http://www.artica.fr/download/ppd/hp-de-hp2500_6.ppd.gz DEUTSCH] or [http://www.artica.fr/download/ppd/hp-es-hp2500c2.ppd.gz ESPANIA] or [http://www.artica.fr/download/ppd/hp-fr-hp2500_6.ppd.gz FRANCAIS] or [http://www.artica.fr/download/ppd/hp-it-hp2500_6.ppd.gz ITALIANO].

=== Scanners ===
* Epson Perfection 1640SU - Works in 3.10

=== USB Audio Devices ===
* "[http://www.dx.com/p/virtual-5-1-surround-usb-2-0-external-sound-card-22475 3D Sound]" USB sound card - Works partially in 3.10 (Output works, input doesn't)

Hardware Compatibility

2018-06-25T03:10:13Z

NewSense: /* Printers */

Hardware Compatibility

2018-06-23T03:15:54Z

NewSense: /* User Provided Reports */

Hardware Compatibility

2018-06-23T03:09:58Z

NewSense: /* User Provided Reports */