https://library.morph.zone/api.php?action=feedcontributions&feedformat=atom&user=JPV
MorphOS Library - User contributions [en]
2026-04-22T18:11:26Z
User contributions
MediaWiki 1.30.0
https://library.morph.zone/index.php?title=Shell_Commands/Copy&diff=4392
Shell Commands/Copy
2026-04-20T10:51:58Z
<p>JPV: </p>
<hr />
<div>'''Copy''' - Copies a source file or directory to another directory<br />
<br />
FROM/M, TO, PAT=PATTERN/K, BUF=BUFFER/K/N, ALL/S, DIRECT/S, <br />
CLONE/S, DATES/S, NOPRO/S, PROX/S, COM=COMMENT/S, QUIET/S, NOREQ/S, <br />
ERRWARN/S, MAKEDIR/S, MOVE/S, DELETE/S, HARD=HARDLINK/S, <br />
SOFT=SOFTLINK/S, FOLNK=FORCELINK/S, FODEL=FORCEDELETE/S, <br />
FOOVR=FORCEOVERWRITE/S,DONTOVR=DONTOVERWRITE/S,FORCE/S <br />
<nowiki><br />
FROM - files or directory to copy. <br />
TO - destination path-name or file<br />
PATTERN - when FROM is a directory, only files matching this pattern<br />
will be copied.<br />
BUFFER - size of the buffer (multiple of 512 bytes)to use during the copy<br />
ALL - includes sub-directories if FROM is a directory<br />
DIRECT - copy file without any tests or options<br />
CLONE - keeps timestamp, comments, and protec. bits of the FROM file.<br />
DATES - the timestamp of the FROM file is copied to the TO file.<br />
NOPRO - The protection bits of the FROM file are not copied<br />
to the TO file. The TO file is given standard protection bits<br />
or r, w, e, and d.<br />
PROX - only copy X,S,P protection bits<br />
COMMENT - the comments of the FROM file are copied to the TO file.<br />
QUIET - suppresses output messages/errors and requesters.<br />
NOREQ - errors such as disk full, or assign not existing will cause<br />
the display of a requester. Using this switch will remove them.<br />
ERRWARN - do not proceed when one file failed.<br />
MAKEDIR - produce directories.<br />
MOVE - delete source files after the copying successful.<br />
DELETE - do not copy but delete the source files.<br />
HARD - make a hardlink to source instead of copying.<br />
SOFT - make a sourcelink to source instead of copying.<br />
FOLNK - also makes links to directories.<br />
FODEL - delete protected files as well.<br />
FOOVR - also overwrites protected files.<br />
DONTOVR - do not overwrite files if they already exist<br />
FORCE - DEPRECIATED: if files already exist and are write-protected,<br />
this option will force them to be overwritten</nowiki><br />
Copy copies the file or directory specified with the FROM argument<br />
to the file or directory specified by the TO argument.<br />
You can copy several items at once by giving more than one name/pattern<br />
in the FROM argument; they should be separated by spaces.<br />
If the FROM argument is a pattern or consists of multiple names,<br />
the TO argument must be a directory.<br />
If a TO file name already exists, Copy overwrites the TO file with<br />
the FROM file. You can use a pair of double quotation marks ("")<br />
to refer to the current directory. When used as the FROM argument,<br />
"" copies all the files in the current directory.<br />
Do not put any spaces between the double quotation marks.<br />
<br />
Examples:<br />
<br />
<nowiki>Ram Disk:> Copy System: Work:System/ ALL CLONE QUIET</nowiki><br />
Creates a backup of the whole System partition. The CLONE option preserves original file attributes and dates.<br />
<br />
<nowiki>Ram Disk:> Copy file.txt "file (copy).txt" DIRECT</nowiki><br />
Creates a destination file using unrecommended characters, like wildcard characters, in the file name.</div>
JPV
https://library.morph.zone/index.php?title=Shell_Commands/Copy&diff=4391
Shell Commands/Copy
2026-04-20T10:50:24Z
<p>JPV: </p>
<hr />
<div>'''Copy''' - Copies a source file or directory to another directory<br />
<br />
FROM/M, TO, PAT=PATTERN/K, BUF=BUFFER/K/N, ALL/S, DIRECT/S, <br />
CLONE/S, DATES/S, NOPRO/S, PROX/S, COM=COMMENT/S, QUIET/S, NOREQ/S, <br />
ERRWARN/S, MAKEDIR/S, MOVE/S, DELETE/S, HARD=HARDLINK/S, <br />
SOFT=SOFTLINK/S, FOLNK=FORCELINK/S, FODEL=FORCEDELETE/S, <br />
FOOVR=FORCEOVERWRITE/S,DONTOVR=DONTOVERWRITE/S,FORCE/S <br />
<nowiki><br />
FROM - files or directory to copy. <br />
TO - destination path-name or file<br />
PATTERN - when FROM is a directory, only files matching this pattern<br />
will be copied.<br />
BUFFER - size of the buffer (multiple of 512 bytes)to use during the copy<br />
ALL - includes sub-directories if FROM is a directory<br />
DIRECT - copy file without any tests or options<br />
CLONE - keeps timestamp, comments, and protec. bits of the FROM file.<br />
DATES - the timestamp of the FROM file is copied to the TO file.<br />
NOPRO - The protection bits of the FROM file are not copied<br />
to the TO file. The TO file is given standard protection bits<br />
or r, w, e, and d.<br />
PROX - only copy X,S,P protection bits<br />
COMMENT - the comments of the FROM file are copied to the TO file.<br />
QUIET - suppresses output messages/errors and requesters.<br />
NOREQ - errors such as disk full, or assign not existing will cause<br />
the display of a requester. Using this switch will remove them.<br />
ERRWARN - do not proceed when one file failed.<br />
MAKEDIR - produce directories.<br />
MOVE - delete source files after the copying successful.<br />
DELETE - do not copy but delete the source files.<br />
HARD - make a hardlink to source instead of copying.<br />
SOFT - make a sourcelink to source instead of copying.<br />
FOLNK - also makes links to directories.<br />
FODEL - delete protected files as well.<br />
FOOVR - also overwrites protected files.<br />
DONTOVR - do not overwrite files if they already exist<br />
FORCE - DEPRECIATED: if files already exist and are write-protected,<br />
this option will force them to be overwritten</nowiki><br />
Copy copies the file or directory specified with the FROM argument<br />
to the file or directory specified by the TO argument.<br />
You can copy several items at once by giving more than one name/pattern<br />
in the FROM argument; they should be separated by spaces.<br />
If the FROM argument is a pattern or consists of multiple names,<br />
the TO argument must be a directory.<br />
If a TO file name already exists, Copy overwrites the TO file with<br />
the FROM file. You can use a pair of double quotation marks ("")<br />
to refer to the current directory. When used as the FROM argument,<br />
"" copies all the files in the current directory.<br />
Do not put any spaces between the double quotation marks.<br />
<br />
Examples:<br />
<br />
<nowiki>Ram Disk:> Copy System: Work:System/ ALL CLONE QUIET</nowiki><br />
Creates a backup of the whole System partition. The CLONE option preserves original file attributes and dates.<br />
<br />
<nowiki>Ram Disk:> Copy file.txt "file (copy).txt" DIRECT</nowiki><br />
Creates a destination file using non-recommended characters, like wildcard characters, in the file name.</div>
JPV
https://library.morph.zone/index.php?title=Screenbar_Modules&diff=4390
Screenbar Modules
2026-04-10T10:50:43Z
<p>JPV: Updated the MorphOS Storage link</p>
<hr />
<div>Screenbar modules are plugins which can populate the empty area on the screen title bar with some useful information and functionality. The modules are visible on every (MUI) [[Fundamentals_of_MorphOS#Screens | screen]], which makes them more useful than, for example, Panel Objects which are only seen on the Ambient screen and can be left under some other windows.<br />
<br />
Screenbar modules can be enabled and disabled from the screen depth gadget menu. The menu also contains options to arrange the order of the modules and to change their settings. The menu can be accessed by right clicking, or with a long left press, over the [[Fundamentals_of_MorphOS#Screen_Depth_Gadget | screen depth gadget]].<br />
<br />
Here is a list of the built-in modules and their characteristics.<br />
<br />
<br />
== Standard Modules ==<br />
{|<br />
|[[File:Sbar_Clock.png]]<br/>'''Clock'''<br />
* A customizable string to show date-related values in every possible way.<br />
* A left click opens a calendar window.<br />
|style="text-align:right;width:96px"|[[File:Sbar_Clock_calendar.png|96px]]<br />
|style="width:130px"|[[File:Sbar_Clock_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_CPU_Monitor.png]]<br/>'''CPU Monitor'''<br />
* A CPU load graph with task filtering options.<br />
* Double click opens the [[Utilities/TaskManager | Task Manager]] utility.<br />
||<br />
||[[File:Sbar_CPU_Monitor_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Debug.png]]<br/>'''Debug'''<br />
* Opens a debug menu with the left mouse click.<br />
* "Show Log..." is a useful option to check if everything has behaved OK in your system.<br />
|style="text-align:right;"|[[File:Sbar_Debug_menu.png|96px]]<br />
||[[File:Sbar_Debug_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Drivelamps.png]]<br/>'''Drivelamps'''<br />
* Shows activity lamps for any mass storage devices connected via IDE, SATA, USB, or SCSI.<br />
* Separates reads and writes by different colors.<br />
||<br />
||[[File:Sbar_Drivelamps_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Eject.png]]<br/>'''Eject'''<br />
* Ejects and/or unmounts devices when clicked with the left mouse button.<br />
* Ejects the CD drive if there isn't anything else to unmount, but otherwise gives an eject menu.<br />
* Can unmount mounted ISO images, SMBFS mounts, Kryptos and other fileimages, USB drives, etc.<br />
|style="text-align:right;"|[[File:Sbar_Eject_menu.png|96px]]<br />
||[[File:Sbar_Eject_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Energy.png]]<br/>'''Energy'''<br />
* Shows the battery charge on laptops.<br />
* Double click opens an Energy Information window with detailed information about the battery and the current drain.<br />
|style="text-align:right;"|[[File:Sbar_Energy_window.png|96px]]<br />
||[[File:Sbar_Energy_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Grabber.png]]<br/>'''Grabber'''<br />
* Grabs screenshots of screens, windows, or user defined areas of the screen.<br />
* Opens a popup menu with the left mouse click.<br />
* User defineable keyboard shortcuts for grabbing.<br />
* Automatic naming of files.<br />
|style="text-align:right;"|[[File:Sbar_Grabber_menu.png|68px]]<br />
||[[File:Sbar_Grabber_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Graphicsmemory.png]]<br/>'''Graphicsmemory'''<br />
* Shows the graphics memory usage.<br />
* Can show the information as percentage or megabytes, and/or as a graphical gauge bar.<br />
* Double click opens the [[Utilities/GraphicBoards | GraphicBoards]] utility.<br />
||<br />
||[[File:Sbar_Graphicsmemory_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_KeyInput.png]]<br/>'''Key input'''<br />
* Can be used to select a keymap, open a [https://library.morph.zone/File:MorphOS_3.10_Screenbar_Keyinput.png virtual keyboard], or launch the [[Utilities/KeyExplorer | Key Explorer]] utility.<br />
|style="text-align:right;"|[[File:Sbar_KeyInput_menu.png|84px]]<br />
||[[File:Sbar_KeyInput_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Memory.png]]<br/>'''Memory'''<br />
* Shows the usage of system RAM and/or graphics memory.<br />
* Can show the information as percentages or megabytes, and/or as graphical gauge bars.<br />
||<br />
||[[File:Sbar_Memory_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Network.png]]<br/>'''Netlamps'''<br />
* Shows activity lamps for a network device.<br />
* Double click opens the Network Statistics window with comprehensive information and graphs about the network traffic.<br />
|style="text-align:right;"|[[File:Sbar_Network_window.png|96px]]<br />
||[[File:Sbar_Network_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Preferences.png]]<br/>'''Preferences'''<br />
* Contains shortcuts to all Ambient, System, and MUI settings.<br />
* User selectable favourites.<br />
|style="text-align:right;"|[[File:Sbar_Preferences_menu.png|76px]]<br />
||[[File:Sbar_Preferences_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Thermal.png]]<br/>'''Thermal'''<br />
* Monitors the temperature sensors.<br />
* Can show or cycle between CPU, NorthBridge, GPU, and Trackpad sensors.<br />
||<br />
||[[File:Sbar_Thermal_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Titlebar.png]]<br/>'''Titlebar'''<br />
* The screen title works as a screenbar module too, although it's always enabled.<br />
* Can be configured to show much more than just the original information. For example memory and battery information, contents of ENV variables, etc.<br />
||<br />
||[[File:Sbar_Titlebar_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Volume.png]]<br/>'''Volume'''<br />
* Controls the audio output volume.<br />
* Using the mouse wheel over the module adjusts the volume and a left mouse click opens the volume slider.<br />
* Pressing the alt key while clicking on the module will launch the Mixer program.<br />
* The "Save mixer settings" setting defines if the volume level is saved permanently every time you change it.<br />
|style="text-align:right;"|[[File:Sbar_Volume_menu.png|37px]]<br />
||[[File:Sbar_Volume_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_Wireless.png]]<br/>'''Wireless'''<br />
* Shows the wireless network status.<br />
* A left mouse click scans for nearby WLANs and shows the results in a popup menu when the scanning is complete.<br />
||<br />
|style="text-align:right;"|[[File:Sbar_Wireless_menu.png|108px]]<br />
|-<br />
|<br />
<br />
<br />
== Run Time Modules ==<br />
These screenbar modules are only shown in runtime with certain programs.<br />
<br />
|- <br />
|[[File:Sbar_Ambient_SoundPlayer.png]]<br/>'''Ambient SoundPlayer'''<br />
* Shown if an audio file is played with the Ambient's internal sound player.<br />
* Can be used to pause or stop (quit) the playback.<br />
* Shows the filename in a text scroller.<br />
|style="height:128px;"|<br />
|-<br />
|[[File:Sbar_Jukebox_small.png]] [[File:Sbar_Jukebox_wide.png]]<br/>'''Jukebox'''<br />
* The [[Utilities/Jukebox | Jukebox]] music player has two options for a screenbar module: small and wide.<br />
* Both modules give a control menu when clicked with the left mouse button.<br />
* Jukebox's volume setting can be adjusted with the mouse wheel over the module.<br />
* The wide module has control buttons and a fully configurable text scroller.<br />
|style="text-align:right;"|[[File:Sbar_Jukebox_small_menu.png|70px]]<br />
||[[File:Sbar_Jukebox_settings.png|128px]]<br />
|-<br />
|[[File:Sbar_ZVNC.png]]<br/>'''ZVNC'''<br />
* The [[Applications/ZVNC | ZVNC]] application creates a screenbar module with a popup menu for controlling it.<br />
|style="height:111px;"|<br />
|style="text-align:right;"|[[File:Sbar_ZVNC_menu.png|70px]]<br />
|}<br />
<br />
<br />
== 3rd Party Modules ==<br />
<br />
3rd party modules should always be installed in the SYS:Classes/Screenbar directory. The Modules->Rescan option from the screen depth menu activates the newly installed modules without a reboot.<br />
<br />
There's a good amount of 3rd party modules ranging from small funny gadgets to more serious and informative ones, and they can be found for example [https://www.morphos-storage.net/?page=Ambient/Screenbar here].</div>
JPV
https://library.morph.zone/index.php?title=Advanced_Topics&diff=4389
Advanced Topics
2026-02-04T10:22:46Z
<p>JPV: </p>
<hr />
<div>*[[Writing Custom Startup Code]]<br />
*[[Vfork_and_fork_with_ixemul | vfork and fork with ixemul]]</div>
JPV
https://library.morph.zone/index.php?title=Vfork_and_fork_with_ixemul&diff=4388
Vfork and fork with ixemul
2026-02-04T10:19:38Z
<p>JPV: </p>
<hr />
<div>''Originally published at: https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=14169&forum=12''<br />
<br />
''Author: Harry Sintonen''<br />
<br />
<br />
Contrary to some misconceptions '''ixemul.library''' does have a working ''vfork()'', and assisted ''fork()''.<br />
<br />
==vfork==<br />
Generally ''vfork()'' should be directly usable in situations where ''fork()'' + ''exec*()'' is used. In this case ''vfork()'' can used instead. Any potential ''exit()'' calls in the child code path should be replaced with ''_exit()''.<br />
<br />
==fork==<br />
Replacing ''fork()'' is doable, but might require significant work. First, the application and all its dependencies should be built with '''-mresident32''' flag. The application must manually duplicate the context at the time of the ''fork()'' call by doing the following:<br />
#Perform the first part of the fork by calling ''ix_vfork()''. A new child is spawned and the parent's execution is paused. pid == 0 indicates child codepath, the parent will get returned the pid of the child.<br />
#In child: Duplicate static data segment and initialize the child memory allocator and other internal structures: ''ix_vfork_setup_child();''<br />
#In child: copy the parent's state to the child. Generally this requires use of static variables to relay values over to the child. Any ''malloc()'' memory and local variables and structures that are used by the child must be cloned before the parent is let to continue. This always requires manual work to construct the necessary code to perform the state cloning, as each use of ''fork()'' is unique in regards of what state is present and how the child will be using it after the call.<br />
#In child: Indicate that parent can continue with ''ix_vfork_resume();''<br />
<br />
At this stage both parent and child are executing the same code segment, concurrently. Both have their own copies of static variables and can use them freely.<br />
<br />
If everything is done correctly this works fine. It is successfully used by for example the ixemul shell (pdksh).</div>
JPV
https://library.morph.zone/index.php?title=Vfork_and_fork_with_ixemul&diff=4387
Vfork and fork with ixemul
2026-02-04T10:18:51Z
<p>JPV: Created page with "''Originally published at: https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=14169&forum=12'' ''Author: Harry Sintonen'' Contrary to some misconceptions '''ixemu..."</p>
<hr />
<div>''Originally published at: https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=14169&forum=12''<br />
<br />
''Author: Harry Sintonen''<br />
<br />
<br />
Contrary to some misconceptions '''ixemul.library''' does have a working vfork(), and assisted fork().<br />
<br />
==vfork==<br />
Generally ''vfork()'' should be directly usable in situations where ''fork()'' + ''exec*()'' is used. In this case ''vfork()'' can used instead. Any potential ''exit()'' calls in the child code path should be replaced with ''_exit()''.<br />
<br />
==fork==<br />
Replacing ''fork()'' is doable, but might require significant work. First, the application and all its dependencies should be built with '''-mresident32''' flag. The application must manually duplicate the context at the time of the ''fork()'' call by doing the following:<br />
#Perform the first part of the fork by calling ''ix_vfork()''. A new child is spawned and the parent's execution is paused. pid == 0 indicates child codepath, the parent will get returned the pid of the child.<br />
#In child: Duplicate static data segment and initialize the child memory allocator and other internal structures: ''ix_vfork_setup_child();''<br />
#In child: copy the parent's state to the child. Generally this requires use of static variables to relay values over to the child. Any ''malloc()'' memory and local variables and structures that are used by the child must be cloned before the parent is let to continue. This always requires manual work to construct the necessary code to perform the state cloning, as each use of ''fork()'' is unique in regards of what state is present and how the child will be using it after the call.<br />
#In child: Indicate that parent can continue with ''ix_vfork_resume();''<br />
<br />
At this stage both parent and child are executing the same code segment, concurrently. Both have their own copies of static variables and can use them freely.<br />
<br />
If everything is done correctly this works fine. It is successfully used by for example the ixemul shell (pdksh).</div>
JPV
https://library.morph.zone/index.php?title=Shell_Commands/Date&diff=4386
Shell Commands/Date
2026-02-03T18:25:49Z
<p>JPV: </p>
<hr />
<div>'''Date''' - Displays or sets the date and time of the system<br />
<br />
DAY, DATE, TIME, TO=VER/K<br />
<nowiki><br />
DAY - sets the day to DAY <br />
DATE - sets the date to DATE<br />
TIME - sets the time to TIME<br />
TO - sets the date to that of the TO file<br />
LFORMAT - defines a string to specially format the output</nowiki><br />
Date with no argument displays the currently set system time and date,<br />
including the day of the week. Time is displayed using a 24-hour clock.<br />
<br />
Date DATE sets only the date. The format for entry and display of DATE<br />
is DD-MMM-YY (day-month-year). The hyphens between the arguments<br />
are required. A leading zero in the date is not necessary.<br />
The number or the first three letters of the month (in English)<br />
must be used, as well as the last two digits of the year.<br />
<br />
The LFORMAT option modifies the output of Date. The available substitution operators are:<br />
<nowiki><br />
%a - Abbreviated weekday name<br />
%A - Weekday name<br />
%b - Abbreviated month name<br />
%B - Month name<br />
%c - The same as "%a %b %d %H:%M:%S %Y"<br />
%C - The same as "%a %b %e %T %Y"<br />
%d - Day number with leading zeros<br />
%D - The same as "%m/%d/%y"<br />
%e - Day number with leading spaces<br />
%F - The same as "%Y-%m-%d"<br />
%h - Abbreviated month name<br />
%H - Hour using 24 hour style with leading zeros<br />
%I - Hour using 12 hour style with leading zeros<br />
%j - Julian date<br />
%m - Month number with leading zeros<br />
%M - The number of minutes with leading zeros<br />
%n - Linefeed<br />
%p - AM or PM string in upper- or lowercase depending on the country selection<br />
%P - "%p" in lowercase<br />
%q - Hour using 24 hour style<br />
%Q - Hour using 12 hour style<br />
%r - The same as "%I:%M:%S %p"<br />
%R - The same as "%H:%M"<br />
%S - The number of seconds with leading zeros<br />
%t - Tab<br />
%T - The same as "%H:%M:%S"<br />
%U - The week number, taking Sunday as the first day of the week<br />
%w - The weekday number<br />
%W - The week number, taking Monday as the first day of the week<br />
%x - The same as "%m/%d/%y"<br />
%X - The same as "%H:%M:%S"<br />
%y - The year using two digits with leading zeros<br />
%Y - The year using four digits with leading zeros</nowiki><br />
<br />
Example:<br />
<nowiki><br />
Ram Disk:> Date LFORMAT="Today is %A."<br />
Today is Tuesday.</nowiki></div>
JPV
https://library.morph.zone/index.php?title=Shell_Commands/Date&diff=4385
Shell Commands/Date
2026-02-03T13:28:02Z
<p>JPV: Added the LFORMAT option</p>
<hr />
<div>'''Date''' - Displays or sets the date and time of the system<br />
<br />
DAY, DATE, TIME, TO=VER/K<br />
<nowiki><br />
DAY - sets the day to DAY <br />
DATE - sets the date to DATE<br />
TIME - sets the time to TIME<br />
TO - sets the date to that of the TO file<br />
LFORMAT - defines a string to specially format the output</nowiki><br />
Date with no argument displays the currently set system time and date,<br />
including the day of the week. Time is displayed using a 24-hour clock.<br />
<br />
Date DATE sets only the date. The format for entry and display of DATE<br />
is DD-MMM-YY (day-month-year). The hyphens between the arguments<br />
are required. A leading zero in the date is not necessary.<br />
The number or the first three letters of the month (in English)<br />
must be used, as well as the last two digits of the year.<br />
<br />
The LFORMAT option modifies the output of Date. The available substitution operators are:<br />
<nowiki><br />
%a - Abbreviated weekday name<br />
%A - Weekday name<br />
%b - Abbreviated month name<br />
%B - Month name<br />
%c - The same as "%a %b %d %H:%M:%S %Y"<br />
%C - The same as "%a %b %e %T %Y"<br />
%d - Day number with leading zeros<br />
%D - The same as "%m/%d/%y"<br />
%e - Day number with leading spaces<br />
%F - The same as "%Y-%m-%d"<br />
%h - Abbreviated month name<br />
%H - Hour using 24 hour style with leading zeros<br />
%I - Hour using 12 hour style with leading zeros<br />
%j - Julian date<br />
%m - Month number with leading zeros<br />
%M - The number of minutes with leading zeros<br />
%n - Linefeed<br />
%p - AM or PM string<br />
%P - am or pm string<br />
%q - Hour using 24 hour style<br />
%Q - Hour using 12 hour style<br />
%r - The same as "%I:%M:%S %p"<br />
%R - The same as "%H:%M"<br />
%S - The number of seconds with leading zeros<br />
%t - Tab<br />
%T - The same as "%H:%M:%S"<br />
%U - The week number, taking Sunday as the first day of the week<br />
%w - The weekday number<br />
%W - The week number, taking Monday as the first day of the week<br />
%x - The same as "%m/%d/%y"<br />
%X - The same as "%H:%M:%S"<br />
%y - The year using two digits with leading zeros<br />
%Y - The year using four digits with leading zeros</nowiki><br />
<br />
Example:<br />
<nowiki><br />
Ram Disk:> Date LFORMAT="Today is %A."<br />
Today is Tuesday.</nowiki></div>
JPV
https://library.morph.zone/index.php?title=Crash_Course_to_Hollywood_Programming/Example_3_-_System-Friendly_GUI&diff=4384
Crash Course to Hollywood Programming/Example 3 - System-Friendly GUI
2026-01-17T10:33:32Z
<p>JPV: </p>
<hr />
<div>== System-Friendly GUI Example ==<br />
=== Preface ===<br />
Standard Hollywood applications are somewhat limited when implementing GUI functionality into them. System menus and all kinds of<br />
requesters can be made, but if you want buttons or other GUI elements inside the Hollywood display, you have to draw them with<br />
your own graphics and handle them in custom ways.<br />
<br />
But luckily Hollywood has a powerful cross-platform plugin system, and there are many nice plugins [http://www.hollywood-mal.com/docs/html/hollywood/PluginsObtaining_.html available] for it. Some of the<br />
most impressive ones are [http://forums.hollywood-mal.com/viewtopic.php?f=19&t=618 MUI Royale] and [http://forums.hollywood-mal.com/viewtopic.php?f=19&t=1381 RapaGUI] plugins, which can be used to create native system-friendly GUIs for applications.<br />
Both are official plugins by the author of Hollywood, and thus well supported and [http://www.hollywood-mal.com/help.html documented].<br />
<br />
'''MUI Royale''', as its name suggests, allows you to create MUI GUIs for Amiga compatible platforms. '''RapaGUI''', on the other hand, is a<br />
beast at its own level, because it allows you to create GUIs that work on several completely different platforms using the<br />
underlying GUI toolkit on each platform. Be it Windows, Linux, Mac, or Amiga compatible, you just write one GUI definition and<br />
it'll work on every OS without modifications. When you run a RapaGUI application, it will look and feel just like other<br />
programs on each platform, because it uses MUI on Amiga compatibles, GTK on Linux, and so on.<br />
<br />
Both MUI Royale and RapaGUI are very similar - the definition of a GUI is created by writing an '''XML''' file, which is then included into your<br />
Hollywood program. The following example is made with MUI Royale, because we are now focusing on Hollywood programming under<br />
MorphOS, and MUI Royale offers a bit more operating system specific features than the more generic RapaGUI. In any case, when you<br />
have learned one of these, it's easy to jump to the other too.<br />
<br />
The most important thing to learn now is to look at information about [http://www.hollywood-mal.com/docs/html/muiroyale/Applicability_.html applicability] in the [http://www.hollywood-mal.com/docs/html/muiroyale/ documentation]. Every available<br />
object attribute has its applicability described on its documentation page. Applicability is simply marked with four letters: I, S, G,<br />
and N. If there's '''I''', you can use the attribute at initialization, which means it can be used when writing the XML file.<br />
'''S''' (set value of a MUI object attribute) and '''G''' (get value of a MUI object attribute) can be used from the actual Hollywood script<br />
at runtime. '''N''' can be used in both to handle notifications of attributes.<br />
<br />
<br />
=== XML File ===<br />
==== Source Code ====<br />
<nowiki><br />
<?xml version="1.0" encoding="iso-8859-1"?><br />
<application base="HWEXAMPLE" id="app" dropobject="disp" icon="muiexample.info"><br />
<menustrip id="examplemenustrip"><br />
<menu title="Project"><br />
<item id="menu_about" notify="selected">About...</item><br />
<item id="menu_about_mui" notify="selected">About MUI...</item><br />
<item id="menu_about_muiroyale" notify="selected">About MUI Royale...</item><br />
<item/><br />
<item id="menu_quit" notify="selected" shortcut="Q">Quit</item><br />
</menu><br />
<menu title="Settings"><br />
<item id="menu_muisettings" notify="selected">MUI...</item><br />
</menu><br />
</menustrip><br />
<window id="win" muiid="MAIN" title="Hollywood MUI Example" screentitle="Hollywood MUI Example 1.0" notify="closerequest" menustrip="examplemenustrip" appwindow="true"><br />
<vgroup><br />
<hgroup><br />
<button id="button1" notify="pressed" cyclechain="true" shorthelp="Displays brush 1">Brush _1</button><br />
<button id="button2" notify="pressed" cyclechain="true" shorthelp="Displays brush 2">Brush _2</button><br />
</hgroup><br />
<hgroup><br />
<button id="button_random" notify="pressed" cyclechain="false" shorthelp="Displays a random brush">_Random</button><br />
<rectangle/><br />
<text id="clock" preparse="\33r">00:00:00</text><br />
</hgroup><br />
<hollywood id="disp" display="1" minwidth="32" minheight="32" maxwidth="16384" maxheight="16384" notify="appmessage"/><br />
</vgroup><br />
</window><br />
</application><br />
</nowiki><br />
<br />
==== Description ====<br />
Let's have a look at the '''XML file''' first. Create a text file and save it as '''muigui.xml'''.<br />
<br />
<br />
<?xml version="1.0" encoding="iso-8859-1"?><br />
<br />
This is a standard XML prologue line, and the file should start with it. ISO-8859-1 might be a safer bet than UTF-8 in our case.<br />
Version means the version of the XML markup language, not the application version. Just copy and paste this line as is.<br />
<br />
<br />
<application base="HWEXAMPLE" id="app" dropobject="disp" icon="muiexample.info"><br />
<br />
The application object is the master object, and all other definitions should be under it in the [http://www.hollywood-mal.com/docs/html/muiroyale/ApplicationTree_.html object tree].<br />
<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/ApplicationBase_.html base] attribute (applicability IG) is important here, because it defines what name is used when saving MUI preferences and it's also used when<br />
creating an ARexx port for the application. Don't use spaces or special characters, and try to pick a unique name that won't be<br />
used by other programs.<br />
<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/NotifyID_.html id] attribute (I) is needed for every object you plan to access later from the Hollwood script. It's good to have it set for the<br />
application object too.<br />
<br />
The last two attributes are pretty much optional, but let's have them as examples, because they're quite useful in general. The<br />
[http://www.hollywood-mal.com/docs/html/muiroyale/ApplicationDropObject_.html dropobject] attribute (IS) defines which object gets notified if you drag and drop a file onto its appicon. In this case the object<br />
called "disp", which we'll define later, gets the notification.<br />
<br />
A program's application icon can be defined with the [http://www.hollywood-mal.com/docs/html/muiroyale/ApplicationIcon_.html icon] attribute (I). Without a path it takes the file from the directory the program<br />
was launched from.<br />
<br />
As you can see, all of these attributes have I in their applicability information. When you browse the documentation and look for new<br />
attributes or how to do things, applicability tells if you can use them in the XML file or during the program execution.<br />
<br />
<br />
<menustrip id="examplemenustrip"><br />
<menu title="Project"><br />
<item id="menu_about" notify="selected">About...</item><br />
<item id="menu_about_mui" notify="selected">About MUI...</item><br />
<item id="menu_about_muiroyale" notify="selected">About MUI Royale...</item><br />
<item/><br />
<item id="menu_quit" notify="selected" shortcut="Q">Quit</item><br />
</menu><br />
<menu title="Settings"><br />
<item id="menu_muisettings" notify="selected">MUI...</item><br />
</menu> <br />
</menustrip><br />
<br />
[[File:HollywoodCourse-Example3-Menu.png|right]]<br />
Every MUI application should contain a pull-down menu with items to open '''About MUI''' and '''About MUI Royale''' windows, and also an item<br />
to open the '''MUI preferences''' program. We define a menu here and assign it later to the main window of our program. Remember to define<br />
'''id''' attributes for all functional items as well as for the [http://www.hollywood-mal.com/docs/html/muiroyale/Menustrip_.html menustrip] object itself. Let's also add our own about window as the first<br />
item in the "Project" menu and a quit option as the last item. The '''<item/>''' line adds a separator bar to the menu.<br />
<br />
If we want to get informed when the user has selected a menu item, we have to add notify tags to the items. Read more about the notification<br />
mechanism [http://www.hollywood-mal.com/docs/html/muiroyale/Notifications_.html here]. When we read the '''Menuitem class''' chapter from the [http://www.hollywood-mal.com/docs/html/muiroyale/Menuitem_.html documentation], we can find out that the [http://www.hollywood-mal.com/docs/html/muiroyale/MenuitemSelected_.html Selected] attribute has<br />
the applicability of N, and that means we can setup a notification for it. So, '''notify="selected"''' does the trick.<br />
<br />
You can also define keyboard shortcuts for any of the menu items with the [http://www.hollywood-mal.com/docs/html/muiroyale/MenuitemShortcut_.html Shortcut] attribute. In this example we can quit the program<br />
by pressing the command-q key combination.<br />
<br />
Remember the traditional Amiga style guide too. If an item opens a new interactive window or requester, add '''...''' at the end of it.<br />
<br />
<br />
<window id="win" muiid="MAIN" title="Hollywood MUI Example" screentitle="Hollywood MUI Example 1.0" notify="closerequest" menustrip="examplemenustrip" appwindow="true"><br />
<br />
Then it's time to define our application [http://www.hollywood-mal.com/docs/html/muiroyale/Window_.html window]. The most important attribute here is [http://www.hollywood-mal.com/docs/html/muiroyale/WindowMuiID_.html muiid], because without it users can't snapshot<br />
window size or position. [http://www.hollywood-mal.com/docs/html/muiroyale/WindowMuiID_.html muiid] has to be exactly four characters long, and each window in your program must have a different [http://www.hollywood-mal.com/docs/html/muiroyale/WindowMuiID_.html muiid] value.<br />
It doesn't matter if you use the same ID (like "MAIN") in different programs, because they save their settings to different files.<br />
<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/WindowTitle_.html title] attribute sets the text in the window title bar of our program, and the [http://www.hollywood-mal.com/docs/html/muiroyale/WindowScreenTitle_.html screentitle] attribute sets the text shown in the<br />
screen title bar when our window is active.<br />
<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/WindowCloseRequest_.html closerequest] notify will tell us if the window's close gadget has been clicked, and we can react to it in our main Hollywood script.<br />
<br />
The menu object we defined earlier can be specified for this window with the [http://www.hollywood-mal.com/docs/html/muiroyale/WindowMenustrip_.html menustrip] attribute. If you use multiple windows in<br />
an application and would like to see the same menu in all of them, move this attribute from the '''<window>''' definition to the '''<application>'''<br />
definition.<br />
<br />
The last [http://www.hollywood-mal.com/docs/html/muiroyale/WindowAppWindow_.html appwindow] attribute lets us listen if an icon (a file) is dragged and dropped onto our program window. It can be left out<br />
if you don't need it.<br />
<br />
<br />
<vgroup><br />
<hgroup><br />
<button id="button1" notify="pressed" cyclechain="true" shorthelp="Displays brush 1">Brush _1</button><br />
<button id="button2" notify="pressed" cyclechain="true" shorthelp="Displays brush 2">Brush _2</button><br />
</hgroup><br />
<br />
[[File:HollywoodCourse-Example3.png|280px|thumb|Our MUI GUI example]]<br />
The objects in our window can be organized in vertical or horizontal [http://www.hollywood-mal.com/docs/html/muiroyale/Groups_.html groups]. Here we create a vertical group with smaller horizontal<br />
groups inside it. On these lines we define that we get two buttons next to each other horizontally.<br />
<br />
If we read the '''Button class''' [http://www.hollywood-mal.com/docs/html/muiroyale/Button_.html documentation], we see that we can get notified by the [http://www.hollywood-mal.com/docs/html/muiroyale/ButtonPressed_.html Pressed] attribute. We could also get notified<br />
by the [http://www.hollywood-mal.com/docs/html/muiroyale/ButtonSelected_.html Selected] attribute if we created a [http://www.hollywood-mal.com/docs/html/muiroyale/ButtonToggle_.html toggle] button.<br />
<br />
[http://www.hollywood-mal.com/docs/html/muiroyale/AreaCycleChain_.html cyclechain] and [http://www.hollywood-mal.com/docs/html/muiroyale/AreaShortHelp_.html shorthelp] attributes are interesting, because they aren't button specific. They are actually attributes<br />
of the '''Area class''', which is a super class for almost everything else, and you can use its attributes with about all objects. When<br />
you are defining an object, you could also check the attributes from the '''Area class''' [http://www.hollywood-mal.com/docs/html/muiroyale/Area_.html documentation].<br />
<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/AreaCycleChain_.html cyclechain] attribute defines if you can activate the object from the keyboard by using the '''tab''' key. You should usually allow this.<br />
<br />
The contents of the MUI bubble help text can be defined with the [http://www.hollywood-mal.com/docs/html/muiroyale/AreaShortHelp_.html shorthelp] attribute. A bubble help window opens if you keep the mouse pointer<br />
over an object for a while.<br />
<br />
An '''underscore''' in the button label makes the following character a keyboard shortcut. We can press "1" or "2" from the keyboard to make a<br />
button press now.<br />
<br />
<br />
<hgroup><br />
<button id="button_random" notify="pressed" cyclechain="false" shorthelp="Displays a random brush">_Random</button><br />
<rectangle/><br />
<text id="clock" preparse="\33r">00:00:00</text><br />
</hgroup><br />
<br />
Here we define another horizontal group whose objects are shown below the previous group.<br />
<br />
The new button here is removed from the cyclechain as an example; you can't activate it with the tab key.<br />
<br />
'''<rectangle/>''' adds some dynamic space between two objects. This can be quite useful when designing a GUI, and especially if you have some<br />
resizing problems.<br />
<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/Text_.html text] object just displays some text, but we plan to update the text later with the current time. Let's put something as its initial<br />
value anyway. The [http://www.hollywood-mal.com/docs/html/muiroyale/TextPreParse_.html preparse] attribute contains a format code for the text, and we use it to right align the text now.<br />
<br />
<br />
<hollywood id="disp" display="1" minwidth="32" minheight="32" maxwidth="16384" maxheight="16384" notify="appmessage"/><br />
<br />
This object isn't inside of any horizonal group and takes the whole window width itself.<br />
<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/Hollywood_.html hollywood] object embeds a complete Hollywood display inside the GUI. [http://www.hollywood-mal.com/docs/html/muiroyale/HollywoodDisplay_.html display] defines the ID number of the Hollywood display you want<br />
show in the object. Defining the sizes makes it resizeable too. If you want to make MUI programs without the graphical display of<br />
Hollywood, that's fine too.<br />
<br />
<br />
</vgroup><br />
</window><br />
</application> <br />
<br />
After finishing our definitions we have working code for the GUI part of our program!<br />
<br />
<br />
=== Hollywood Script ===<br />
==== Source Code ====<br />
<nowiki><br />
@VERSION 5,2<br />
@APPTITLE "Hollywood MUI Example"<br />
@APPVERSION "$VER: HollywoodMUIExample 1.0 (31.10.17)"<br />
@APPDESCRIPTION "A Hollywood example program."<br />
@REQUIRE "muiroyale", {Version=1, Revision=7}<br />
@DISPLAY {Hidden=True, Width=400, Height=300, Sizeable=True, Layers=True, ScaleMode=#SCALEMODE_LAYER, SmoothScale=True}<br />
@BRUSH 1, "MOSSYS:Data/Jalapeno/ReadMode.png", {LoadAlpha=True}<br />
@FILE 1, "muigui.xml"<br />
<br />
Function p_DrawGfx(brush_number)<br />
If Not brush_number Then brush_number = Rnd(2) + 1<br />
If LayerExists("gfx") Then RemoveLayerFX("gfx")<br />
mui.Set("win", "title", "Brush " .. brush_number)<br />
DisplayBrushFX(brush_number, #CENTER, #CENTER)<br />
SetLayerName(0, "gfx")<br />
EndFunction<br />
<br />
Function p_Input(msg)<br />
DebugPrint("Input event!", msg.Action)<br />
Switch(msg.Action)<br />
Case "OnKeyDown":<br />
DebugPrint(msg.Key, "key was pressed.")<br />
Switch(msg.Key)<br />
Case " ":<br />
p_DrawGfx()<br />
Case "ESC":<br />
DebugPrint("Quitting...")<br />
End<br />
EndSwitch<br />
Case "OnMouseDown":<br />
p_DrawGfx()<br />
EndSwitch<br />
EndFunction<br />
<br />
Function p_MUIEvent(msg)<br />
DebugPrint("MUI event!", " Class:", msg.Class, " ID:", msg.ID, " Attribute:", msg.Attribute)<br />
Switch msg.Class<br />
Case "Window":<br />
Switch msg.Attribute<br />
Case "CloseRequest":<br />
End<br />
EndSwitch<br />
Case "Menuitem":<br />
Switch msg.ID<br />
Case "menu_about":<br />
Local reqtext$ = "\27c\27bHollywood MUI Example\n\27nFor a tutorial at the MorphOS Library."<br />
If mui.Request("About", reqtext$, "Open tutorial|*OK") Then OpenURL("http://library.morph.zone/Crash_Course_to_Hollywood_Programming")<br />
Case "menu_about_mui":<br />
mui.DoMethod("app", "AboutMUI")<br />
Case "menu_about_muiroyale":<br />
mui.DoMethod("app", "AboutMUIRoyale")<br />
Case "menu_quit":<br />
End<br />
Case "menu_muisettings":<br />
mui.DoMethod("app", "OpenConfigWindow")<br />
EndSwitch<br />
Case "Button":<br />
Switch msg.ID<br />
Case "button1":<br />
p_DrawGfx(1)<br />
Case "button2":<br />
p_DrawGfx(2)<br />
Case "button_random":<br />
p_DrawGfx()<br />
EndSwitch<br />
EndSwitch<br />
EndFunction<br />
<br />
Function p_UpdateClock()<br />
mui.Set("clock", "contents", GetTime(True))<br />
EndFunction<br />
<br />
mui.CreateGUI(ReadString(1))<br />
<br />
InstallEventHandler({OnKeyDown = p_Input, OnMouseDown = p_Input, MUIRoyale = p_MUIEvent})<br />
SetInterval(1, p_UpdateClock, 1000)<br />
<br />
LoadBrush(2, "MOSSYS:Data/Jalapeno/TrackMode.png", {LoadAlpha = True})<br />
p_DrawGfx()<br />
<br />
Repeat<br />
WaitEvent<br />
Forever<br />
</nowiki><br />
<br />
==== Description ====<br />
<br />
Let's modify our previous example ([[Crash_Course_to_Hollywood_Programming/Example_2_-_Hollywood_Programming|Example 2: Hollywood Programming]]) script to work with the MUI GUI now, and add some fancy new features as well.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/atREQUIRE_.html @REQUIRE] "muiroyale", {Version=1, Revision=7}<br />
<br />
With this [http://www.hollywood-mal.com/docs/html/hollywood/PrgPreproc_.html preprocessor] statement we can ensure that we have new enough version of the MUI Royale plugin available. In this case we make sure that<br />
we have at least MUI Royale 1.7 in use.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/atDISPLAY_.html @DISPLAY] {Hidden=True, Width=400, Height=300, Sizeable=True, Layers=True, ScaleMode=#SCALEMODE_LAYER, SmoothScale=True}<br />
<br />
Hollywood opens its initial display window automatically, but when we plan to open a separate MUI window with the Hollywood display<br />
inside it, we can tell Hollywood to keep its display hidden at startup. Let's add a '''Hidden=True''' item to the [http://www.hollywood-mal.com/docs/html/hollywood/atDISPLAY_.html @DISPLAY] preprocessor table.<br />
<br />
We can also remove the ''Title'' and ''ScreenTitle'' items, because we have defined them in the XML file for the MUI GUI already.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/atFILE_.html @FILE] 1, "muigui.xml"<br />
<br />
This preprocessor command opens our GUI definition file for later use. We could open or load the file by other means later too, but when<br />
it's opened with the preprocessor command the file gets '''linked''' into the executable when we compile the program. This way we don't have<br />
to have a plaintext GUI definition file distributed with our compiled software.<br />
<br />
<br />
Function p_DrawGfx(brush_number)<br />
If Not brush_number Then brush_number = Rnd(2) + 1<br />
If [http://www.hollywood-mal.com/docs/html/hollywood/LayerExists_.html LayerExists]("gfx") Then [http://www.hollywood-mal.com/docs/html/hollywood/RemoveLayerFX_.html RemoveLayerFX]("gfx")<br />
[http://www.hollywood-mal.com/docs/html/muiroyale/muiSet_.html mui.Set]("win", "title", "Brush " .. brush_number)<br />
[http://www.hollywood-mal.com/docs/html/hollywood/DisplayBrushFX_.html DisplayBrushFX](brush_number, #CENTER, #CENTER)<br />
[http://www.hollywood-mal.com/docs/html/hollywood/SetLayerName_.html SetLayerName](0, "gfx")<br />
EndFunction<br />
<br />
Let's change our drawing function a bit as well.<br />
<br />
Now we accept a brush number as a parameter for it and assign a random value only if nothing was given.<br />
<br />
We'll also use MUI to change the window title text. The '''Window class''' section in the MUI Royale [http://www.hollywood-mal.com/docs/html/muiroyale/Window_.html documentation] reveals that there<br />
is a [http://www.hollywood-mal.com/docs/html/muiroyale/WindowTitle_.html Title] attribute, which can be changed from our script, because it has '''S''' (set) marked in its applicability information.<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/muiSet_.html mui.Set] function can be used to set values of attributes, and we pass to it the ID of our MUI window, the name of the argument we want<br />
to change, and a new value for it.<br />
<br />
<br />
Function p_MUIEvent(msg)<br />
[http://www.hollywood-mal.com/docs/html/hollywood/DebugPrint_.html DebugPrint]("MUI event!", " Class:", msg.Class, " ID:", msg.ID, " Attribute:", msg.Attribute)<br />
<br />
Here is a new function to handle MUI events. We could handle them in the same input event handler we made earlier, but let's keep them<br />
separated for clarity now.<br />
<br />
The [http://www.hollywood-mal.com/docs/html/hollywood/DebugPrint_.html DebugPrint]() line shows us the class that triggered the event, the ID of the object, and the attribute that changed.<br />
<br />
<br />
Switch msg.Class<br />
Case "Window":<br />
Switch msg.Attribute<br />
Case "CloseRequest":<br />
[http://www.hollywood-mal.com/docs/html/hollywood/End_.html End]<br />
EndSwitch<br />
<br />
If the class was '''Window''' and the attribute was [http://www.hollywood-mal.com/docs/html/muiroyale/WindowCloseRequest_.html CloseRequest] (the close gadget was pressed), we quit the whole program with the [http://www.hollywood-mal.com/docs/html/hollywood/End_.html End]()<br />
function. Hollywood closes the MUI window and frees the resources automatically.<br />
<br />
<br />
Case "Menuitem":<br />
Switch msg.ID<br />
<br />
If the event came from the '''Menuitem''' class, it's enough to check which object triggered it. The IDs are the same we defined in the XML file.<br />
<br />
<br />
Case "menu_about":<br />
[http://www.hollywood-mal.com/docs/html/hollywood/PrgLocals_.html Local] reqtext$ = "\27c\27bHollywood MUI Example\27n\nFor a tutorial at the MorphOS Library."<br />
If [http://www.hollywood-mal.com/docs/html/muiroyale/muiRequest_.html mui.Request]("About", reqtext$, "Open tutorial|*OK") Then [http://www.hollywood-mal.com/docs/html/hollywood/OpenURL_.html OpenURL]("http://library.morph.zone/Crash_Course_to_Hollywood_Programming")<br />
<br />
[[File:HollywoodCourse-Example3-About.png|right|247px]]<br />
This is our own about window for the program. We declare a [http://www.hollywood-mal.com/docs/html/hollywood/PrgLocals_.html local variable] with a string in it, and because it's a '''string variable''' we use<br />
a '''dollar sign''' as the last character of the variable name. It would work without the dollar sign too, but it's a [http://www.hollywood-mal.com/docs/html/hollywood/PrgStyleguideSuggestions_.html style guide] suggestion<br />
in Hollywood to separate '''strings ($)''' and '''floating point values (!)''' from integer values.<br />
<br />
The string itself may look a bit cryptic, because we have used some [http://www.hollywood-mal.com/docs/html/muiroyale/TextFormat_.html formatting codes] as an example here. '''\27c''' centers the text,<br />
'''\27b''' makes the text bold, '''\27n''' resets the text style back to normal, and '''\n''' starts a new line. Notice that we use '''\27''' here while<br />
we used '''\33''' in the XML file.<br />
<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/muiRequest_.html mui.Request]() function is an easy way to pop up a MUI system requester. We have only two buttons in it this time, so we can directly<br />
check the result with the [http://www.hollywood-mal.com/docs/html/hollywood/PrgIf_.html If statement] on the same line. If the user selects the "Open tutorial" button, the result will be "1" and we open<br />
the web page with the [http://www.hollywood-mal.com/docs/html/hollywood/OpenURL_.html OpenURL]() function. The "OK" button will return 0 and nothing happens then. '''*''' can be used to mark which button<br />
is pre-selected by default.<br />
<br />
<br />
Case "menu_about_mui":<br />
[http://www.hollywood-mal.com/docs/html/muiroyale/muiDoMethod_.html mui.DoMethod]("app", "[http://www.hollywood-mal.com/docs/html/muiroyale/ApplicationAboutMUI_.html AboutMUI]")<br />
Case "menu_about_muiroyale":<br />
[http://www.hollywood-mal.com/docs/html/muiroyale/muiDoMethod_.html mui.DoMethod]("app", "[http://www.hollywood-mal.com/docs/html/muiroyale/ApplicationAboutMUIRoyale_.html AboutMUIRoyale]")<br />
Case "menu_quit":<br />
[http://www.hollywood-mal.com/docs/html/hollywood/End_.html End]<br />
Case "menu_muisettings":<br />
[http://www.hollywood-mal.com/docs/html/muiroyale/muiDoMethod_.html mui.DoMethod]("app", "[http://www.hollywood-mal.com/docs/html/muiroyale/ApplicationOpenConfigWindow_.html OpenConfigWindow]")<br />
EndSwitch<br />
<br />
Opening other about windows is pretty automatic with the MUI methods provided by the Application class. The methods can be run using the<br />
[http://www.hollywood-mal.com/docs/html/muiroyale/muiDoMethod_.html mui.DoMethod]() function.<br />
<br />
<br />
Case "Button":<br />
Switch msg.ID<br />
Case "button1":<br />
p_DrawGfx(1)<br />
Case "button2":<br />
p_DrawGfx(2)<br />
Case "button_random":<br />
p_DrawGfx()<br />
EndSwitch<br />
EndSwitch<br />
EndFunction<br />
<br />
Finally we handle button presses. We can now select which brush to show, or press the random button to call our drawing function without<br />
a defined brush number.<br />
<br />
<br />
Function p_UpdateClock()<br />
[http://www.hollywood-mal.com/docs/html/muiroyale/muiSet_.html mui.Set]("clock", "contents", GetTime(True))<br />
EndFunction<br />
<br />
We also created a text object to our GUI with the ID "clock". Here is a short function to set its contents to the result we get<br />
from the [http://www.hollywood-mal.com/docs/html/hollywood/GetTime_.html GetTime]() function. [http://www.hollywood-mal.com/docs/html/hollywood/GetTime_.html GetTime]() is found in the Time library, and if you set its optional argument to '''True''', it will return<br />
the time in the '''hh:mm:ss''' format instead of the '''hh:mm''' format.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/muiroyale/muiCreateGUI_.html mui.CreateGUI]([http://www.hollywood-mal.com/docs/html/hollywood/ReadString_.html ReadString](1))<br />
<br />
The [http://www.hollywood-mal.com/docs/html/muiroyale/muiCreateGUI_.html mui.CreateGUI]() function creates the actual GUI from an XML source code string. You could put the string into a Hollywood script too,<br />
but it's more comfortable to have the XML source in a separate file for any bigger projects.<br />
<br />
As we already opened the file with the [http://www.hollywood-mal.com/docs/html/hollywood/atFILE_.html @FILE] preprocessor command, we can just use the [http://www.hollywood-mal.com/docs/html/hollywood/ReadString_.html ReadString]() function with the file ID number as an<br />
argument to get the file returned as a string.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/InstallEventHandler_.html InstallEventHandler]({OnKeyDown = p_Input, OnMouseDown = p_Input, MUIRoyale = p_MUIEvent})<br />
<br />
We'll have to install the '''MUIRoyale''' event handler to get MUI related notifications to our '''p_MUIEvent()''' function.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/SetInterval_.html SetInterval](1, p_UpdateClock, 1000)<br />
<br />
The [http://www.hollywood-mal.com/docs/html/hollywood/SetInterval_.html SetInterval]() function can be used to trigger events periodically. Here we create a new '''interval''' function which calls our '''p_UpdateClock()'''<br />
function repeatedly at 1000 ms intervals. Our clock gets updated once per second now.<br />
<br />
<br />
And there it is! Our first MUI program made with Hollywood. If you have saved the Hollwood script as, for example, '''muiexample.hws''',<br />
and you have '''muigui.xml''' and '''muiroyale.hwp''' files in the same directory, you can run the program with the <code>Hollywood muiexample.hws -quiet</code> command<br />
from the shell or with the F4 key in Cubic IDE. And if you '''compile''' the program, you don't need the '''muigui.xml''' file in the same directory any more.<br />
<br />
The '''muiroyale.hwp''' [http://www.hollywood-mal.com/download.html plugin] file can be installed into the '''SYS:Libs/Hollywood/''' directory to be always available for your programs, but when<br />
distributing them I'd advice to have a copy of it '''in the same directory with the executable'''. That way users don't need to install<br />
anything and it doesn't matter if they don't have the correct version in their Libs directory.<br />
<br />
<br />
< [[Crash_Course_to_Hollywood_Programming#Summary|Proceed to the summary chapter]]</div>
JPV
https://library.morph.zone/index.php?title=Crash_Course_to_Hollywood_Programming/Example_2_-_Hollywood_Programming&diff=4383
Crash Course to Hollywood Programming/Example 2 - Hollywood Programming
2026-01-17T10:31:22Z
<p>JPV: </p>
<hr />
<div>== Hollywood Programming Example ==<br />
=== Source Code ===<br />
<nowiki><br />
@VERSION 6,0<br />
@APPTITLE "Hollywood Example"<br />
@APPVERSION "$VER: HollywoodExample 1.0 (31.10.17)"<br />
@APPDESCRIPTION "A Hollywood example program."<br />
@DISPLAY {Title="Hollywood Example", ScreenTitle="Hollywood Example", Width=400, Height=300, Sizeable=True, Layers=True, ScaleMode=#SCALEMODE_LAYER, SmoothScale=True}<br />
@BRUSH 1, "MOSSYS:Data/Jalapeno/ReadMode.png", {LoadAlpha=True}<br />
<br />
Function p_DrawGfx()<br />
Local brush_number = Rnd(2) + 1<br />
If LayerExists("gfx") Then RemoveLayerFX("gfx")<br />
SetDisplayAttributes({Title = "Brush " .. brush_number})<br />
DisplayBrushFX(brush_number, #CENTER, #CENTER)<br />
SetLayerName(0, "gfx")<br />
EndFunction<br />
<br />
Function p_Input(msg)<br />
DebugPrint("Input event!", msg.Action)<br />
Switch(msg.Action)<br />
Case "OnKeyDown":<br />
DebugPrint(msg.Key, "key was pressed.")<br />
Switch(msg.Key)<br />
Case " ":<br />
p_DrawGfx()<br />
Case "ESC":<br />
DebugPrint("Quitting...")<br />
End<br />
EndSwitch<br />
Case "OnMouseDown":<br />
p_DrawGfx()<br />
EndSwitch<br />
EndFunction<br />
<br />
LoadBrush(2, "MOSSYS:Data/Jalapeno/TrackMode.png", {LoadAlpha=True})<br />
p_DrawGfx()<br />
<br />
InstallEventHandler({OnKeyDown = p_Input, OnMouseDown = p_Input})<br />
<br />
Repeat<br />
WaitEvent<br />
Forever<br />
</nowiki><br />
<br />
=== Description ===<br />
<br />
The previous example ([[Crash_Course_to_Hollywood_Programming/Example_1_-_The_First_Test|Example 1: The First Test]]) could be extended to have more commands to be executed in batch, which could be fine for<br />
presentations or slideshows, but let's take a more practical approach and create an interactive script whose<br />
structure looks like a real program.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/atVERSION_.html @VERSION] 6,0<br />
<br />
This preprocessor command defines which Hollywood version is required to run the script. If you want to run this example with an earlier version of Hollywood, remove the ScreenTitle attribute from the @DISPLAY preprocessor line.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/atAPPTITLE_.html @APPTITLE] "Hollywood Example"<br />
[http://www.hollywood-mal.com/docs/html/hollywood/atAPPVERSION_.html @APPVERSION] "$VER: HollywoodExample 1.0 (26.10.17)"<br />
[http://www.hollywood-mal.com/docs/html/hollywood/atAPPDESCRIPTION_.html @APPDESCRIPTION] "A Hollywood example program."<br />
<br />
There are several preprocessor commands for adding informative strings to an application. These three are especially<br />
useful for Amiga and MorphOS programs, because Hollywood programs act like commodities and you'll see this information<br />
in, for example, the Exchange program. The @APPVERSION format should respect the standard version string rules,<br />
which means that the date should be given in the DD.MM.YY format etc.<br />
<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/atDISPLAY_.html @DISPLAY] {Title="Hollywood Example", ScreenTitle="Hollywood Example", Width=400, Height=300, Sizeable=True, Layers=True, ScaleMode=#SCALEMODE_LAYER, SmoothScale=True}<br />
<br />
This time we don't use the [http://www.hollywood-mal.com/docs/html/hollywood/atBGPIC_.html @BGPIC] preprocessor, but define the display size manually and add some extra<br />
attributes too.<br />
<br />
'''Title''' defines what will be shown in the window title bar, and '''ScreenTitle''' what is shown in the screen title bar<br />
when our program window is active.<br />
<br />
The '''Width''' and '''Height''' attributes define the actual drawing area (display) for our application. The application window<br />
itself will be a bit larger with the standard OS window borders added around a Hollywood display. It is also<br />
possible to open borderless and fullscreen windows without the standard window borders.<br />
<br />
The '''Sizeable''' attribute defines if the application window is resizeable by the user.<br />
<br />
'''Layers=True''' enables Hollywood's [http://www.hollywood-mal.com/docs/html/hollywood/LayersIntroduction_.html layer system]. It depends on the program you're developing whether you want to enable<br />
layers or not. With layers enabled all drawing operations get their own layer that can be moved, removed, and<br />
otherwise processed. When they're disabled, all graphics are just painted over each other on the display and it's<br />
harder to change or undo things. But if you're just drawing fullscreen graphics to the display or something like<br />
that, it's better to keep layers disabled.<br />
<br />
'''ScaleMode''' sets if display contents are scaled automatically when the display size changes. Many times<br />
it's better to keep this disabled and recalculate your own graphics after a resize event to keep the aspect<br />
ratio intact and to avoid slowdowns, but let's enable this now to get more functionality into our application without<br />
extra lines of code.<br />
<br />
'''SmoothScale''' makes the scaling output prettier at the expense of speed.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/atBRUSH_.html @BRUSH] 1, "MOSSYS:Data/Jalapeno/ReadMode.png", {LoadAlpha=True}<br />
<br />
Brushes are the most common way to load, process, and display graphics in Hollywood. This preprocessor line loads<br />
a PNG image as a brush with ID number 1. All brush handling operations are done by referring to the ID number from<br />
now on. The last argument is an optional table containing any extra options for loading. We are using graphics<br />
with an alpha channel (transparency) now, so we tell Hollywood to load alpha channel values too.<br />
<br />
<br />
Function p_DrawGfx()<br />
[http://www.hollywood-mal.com/docs/html/hollywood/PrgLocals_.html Local] brush_number = [http://www.hollywood-mal.com/docs/html/hollywood/Rnd_.html Rnd](2) + 1<br />
If [http://www.hollywood-mal.com/docs/html/hollywood/LayerExists_.html LayerExists]("gfx") Then [http://www.hollywood-mal.com/docs/html/hollywood/RemoveLayerFX_.html RemoveLayerFX]("gfx")<br />
[http://www.hollywood-mal.com/docs/html/hollywood/SetDisplayAttributes_.html SetDisplayAttributes]({Title = "Brush " .. brush_number})<br />
[http://www.hollywood-mal.com/docs/html/hollywood/DisplayBrushFX_.html DisplayBrushFX](brush_number, #CENTER, #CENTER)<br />
[http://www.hollywood-mal.com/docs/html/hollywood/SetLayerName_.html SetLayerName](0, "gfx")<br />
EndFunction<br />
<br />
[[File:HollywoodCourse-Example2.png|thumb|Hollywood Example running]]<br />
This is how you create your own [http://www.hollywood-mal.com/docs/html/hollywood/PrgFunctions_.html functions] in Hollywood. Our own function names should always start with the '''p_''' prefix<br />
to distinguish them from Hollywood's internal functions. In this case the function doesn't take any parameters and<br />
doesn't return any values, it can just be called from the program with p_DrawGfx() to run the lines inside it.<br />
<br />
The purpose of this function is to show one of the two brushes we have in memory. The brush ID numbers are 1 and 2, and<br />
we randomly pick one of them. Because we have the [http://www.hollywood-mal.com/docs/html/hollywood/LayersIntroduction_.html layer system] enabled, we get a new layer every time we draw a brush<br />
into the display. To avoid ending up with unlimited number of layers we remove an existing layer first. We also<br />
change the window title bar text to show the number of the shown brush.<br />
<br />
The first line of the function declares a new local variable called brush_number and assigns a random value (1 or 2)<br />
to it. You should declare new variables as local whenever possible; read more about it [http://www.hollywood-mal.com/docs/html/hollywood/PrgLocals.html here].<br />
<br />
The second line checks if we already have a specific layer created, and removes it with a fancy random effect if we do.<br />
This line is just skipped when the function is called the first time, because we don't have the specific layer yet.<br />
<br />
The third line changes the window title text to the brush number we got on the first line. Almost all display attributes<br />
can be changed on the fly, and you aren't restricted to the ones you defined with the [http://www.hollywood-mal.com/docs/html/hollywood/atDISPLAY_.html @DISPLAY] preprocessor command.<br />
Here you can also see how you can combine a string from other strings or variables with the '''..''' operator, which is<br />
familiar from Lua.<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/DisplayBrushFX_.html DisplayBrushFX]() shows the selected brush and creates a new layer on the layer stack. The position of the brush can be given<br />
in pixels, but also using [http://www.hollywood-mal.com/docs/html/hollywood/PrgInbuiltCst_.html inbuilt constants] like '''#CENTER'''. '''FX''' at the end of the function name indicates that there's a<br />
transition effect displayed when the function is called. In most cases they are a bit over the top, and you probably<br />
end up using [http://www.hollywood-mal.com/docs/html/hollywood/DisplayBrush_.html DisplayBrush]() or other options to render the graphics.<br />
<br />
Layers get ID numbers automatically and they are assigned dynamically, which means that removing a layer changes the ID<br />
numbers of the layers on top of it. To make life easier we can name the layers and handle them by their names<br />
instead of their ID numbers. [http://www.hollywood-mal.com/docs/html/hollywood/SetLayerName_.html SetLayerName]() is one way to do that, and we use it to name the layer with the brush here.<br />
The function accepts a layer ID number and name as parameters. Our displayed brush creates the first layer on the layer<br />
stack and its ID number will thus be 1. [http://www.hollywood-mal.com/docs/html/hollywood/SetLayerName_.html SetLayerName](1,"gfx") would work in this case, and our layer would get the name "gfx"<br />
as intended. But to make life even easier we can give '''ID number 0''' as the first parameter, and the name will be given to the last<br />
created layer. This way you don't have to keep count of layers at all.<br />
<br />
<br />
Function p_Input(msg)<br />
[http://www.hollywood-mal.com/docs/html/hollywood/DebugPrint_.html DebugPrint]("Input event!", msg.Action)<br />
Switch(msg.Action)<br />
Case "OnKeyDown":<br />
[http://www.hollywood-mal.com/docs/html/hollywood/DebugPrint_.html DebugPrint](msg.Key, "key was pressed.")<br />
Switch(msg.Key)<br />
Case " ":<br />
p_DrawGfx()<br />
Case "ESC":<br />
[http://www.hollywood-mal.com/docs/html/hollywood/DebugPrint_.html DebugPrint]("Quitting...")<br />
End<br />
EndSwitch<br />
Case "OnMouseDown":<br />
p_DrawGfx()<br />
EndSwitch<br />
EndFunction<br />
<br />
Here's another function created by us. It is used to handle user input events. Event handling functions will get a<br />
message table as their parameter, and we'll get it as a local variable called "msg".<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/DebugPrint_.html DebugPrint]() is a useful function for checking what values we have in certain variables during the program execution. Don't<br />
hesitate to use it temporarily to learn what results you get from different functions and what values you have in variables.<br />
Here it is used to print the '''Action''' field from the message table, which tells us the name of the event that occured.<br />
<br />
If the user presses a key, we get an '''OnKeyDown''' event, and if the user presses the left mouse button, we get an '''OnMouseDown''' event.<br />
A full list of standard events can be found [http://www.hollywood-mal.com/docs/html/hollywood/InstallEventHandler_.html here].<br />
<br />
We handle different events with a [http://www.hollywood-mal.com/docs/html/hollywood/PrgSwitch_.html Switch-Case] statement in this example, but feel free to handle it in other ways if you please. It<br />
is also possible to have a separate function for each event.<br />
<br />
If we take a look at the [http://www.hollywood-mal.com/docs/html/hollywood/InstallEventHandler_.html documentation], we see that the '''OnKeyDown''' event contains the exact key that was pressed in its '''Key'''<br />
field. It can be accessed with the '''msg.Key''' table item in our function.<br />
<br />
The inner [http://www.hollywood-mal.com/docs/html/hollywood/PrgSwitch_.html Switch-Case] statement checks if the pressed key was space or escape. If it was '''space''', our previous drawing function<br />
is called and you get new graphics on the display, whereas pressing the '''escape''' key quits the program with a message. Pressing any<br />
other keys will just print the key without doing anything else.<br />
<br />
Pressing the '''left mouse button''' also calls our previous drawing function, and the display gets refreshed.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/LoadBrush_.html LoadBrush](2, "MOSSYS:Data/Jalapeno/TrackMode.png", {LoadAlpha=True})<br />
<br />
The first image in our example program was loaded with the [http://www.hollywood-mal.com/docs/html/hollywood/atBRUSH_.html @BRUSH] preprocessor command, but let's load the second image separately.<br />
The difference between them is that by doing the latter the image doesn't get linked into our executable file when we compile the program. The image<br />
is loaded from the filesystem every time you run the program, no matter if it's compiled or not.<br />
<br />
<br />
p_DrawGfx()<br />
<br />
Now that we have both images loaded as brushes, we can call the function we defined earlier, and we get some graphics shown in<br />
the application window.<br />
<br />
<br />
[http://www.hollywood-mal.com/docs/html/hollywood/InstallEventHandler_.html InstallEventHandler]({OnKeyDown = p_Input, OnMouseDown = p_Input})<br />
<br />
Our previously defined p_Input() function doesn't get any events unless we install event handlers. A table passed to the<br />
[http://www.hollywood-mal.com/docs/html/hollywood/InstallEventHandler_.html InstallEventHandler]() function defines which events are listened to and what functions they call when triggered. Here<br />
we define both '''OnKeyDown''' and '''OnMouseDown''' events to call our own '''p_Input()''' function, and user input will work from now on.<br />
As you can see, events can call the same function or they can be made to call other functions if necessary.<br />
<br />
<br />
Repeat<br />
[http://www.hollywood-mal.com/docs/html/hollywood/WaitEvent_.html WaitEvent]<br />
Forever <br />
<br />
This is the main loop of the program. The [http://www.hollywood-mal.com/docs/html/hollywood/WaitEvent_.html WaitEvent] function is called repeatedly as long as our program is running and it only<br />
waits for any event to happen. The program just sleeps and doesn't waste any CPU time when there aren't any events.<br />
<br />
Save the script as '''hwexample.hws''' and run it with the <code>Hollywood hwexample.hws -quiet</code> command from the shell or with the F4 key in Cubic IDE.<br />
<br />
<br />
> [[Crash_Course_to_Hollywood_Programming/Example_3_-_System-Friendly_GUI|Proceed to the next example]]</div>
JPV
https://library.morph.zone/index.php?title=Style_Guide&diff=4382
Style Guide
2025-11-30T15:05:30Z
<p>JPV: Fixed capitalization on menu items.</p>
<hr />
<div>This article presents fundamental recommendations for developing high-quality MorphOS software. Many applications do not fail because of missing functionality, but because of details that negatively affect the user experience. The following guidelines help avoid common pitfalls and ensure that applications integrate consistently into the MorphOS environment.<br />
<br />
== Structure of the Software Archive ==<br />
<br />
A professional first impression begins with the structure of the distributed archive. A program should always be delivered inside its own directory without version numbers in the directory or file names. This makes handling software packages easier for both the user and the system.<br />
<br />
Example:<br />
<br />
The fictional tool ''Brawny'' is distributed as an archive named ''Brawny.lha'', containing a folder ''Brawny'' with all relevant files, including a program icon. Subfolders such as ''Help'' or language directories should each have their own .info file; purely system-related folders like ''Catalogs'' do not need one.<br />
<br />
<nowiki><br />
Ram Disk:> lha x Brawny.lha<br />
<br />
Extracting from archive 'Brawny.lha':<br />
Extracting: ( 4716/ 4716) Brawny.info<br />
Extracting: ( 6567813/ 6567813) Brawny/Brawny<br />
Extracting: ( 30276/ 30276) Brawny/Brawny.info<br />
Extracting: ( 54414/ 54414) Brawny/Brawny.readme<br />
Extracting: ( 54/ 54) Brawny/Brawny.readme.info<br />
5 files extracted, all files OK.</nowiki><br />
<br />
A clean archive structure improves access via both the Shell and the graphical Ambient interface.<br />
<br />
== The Correct Version String ==<br />
<br />
MorphOS requires a strictly defined format for version strings. Only when applications follow this standard can tools such as [[Shell_Commands/Version | Version]], package managers, or file comparison utilities work reliably.<br />
<br />
Version string format:<br />
<br />
$VER: <ApplicationName> <Version>.<Revision> (<DD.MM.YY>) © <Year AuthorName> <optional additional info><br />
<br />
Important notes:<br />
<br />
* Version and revision consist of digits only.<br />
* No letters or further sub-versions.<br />
* The exact location in the program code is irrelevant, but it should appear early so it can be read quickly.<br />
<br />
An incorrect version string can cause scripts or system tools to malfunction and should therefore be avoided at all costs.<br />
<br />
== User Interface Principles ==<br />
=== Localization ===<br />
<br />
Supporting multiple languages should be standard practice today. MorphOS provides extensive mechanisms for this purpose, and developers should make use of them.<br />
<br />
=== Labeling of UI Elements ===<br />
<br />
Labels for input elements should always end with a colon. This clearly indicates their association to the user.<br />
:: [[File:styleguide_labels.png|frameless]]<br />
<br />
=== Buttons and Ellipses ===<br />
<br />
Ellipsis (three dots) is added to a button label to distinguish between direct and indirect actions.<br />
<br />
A clear rule applies to it:<br />
* Direct action: "Format" (action starts immediately)<br />
* Indirect action: "Format..." (opens a new window or confirmation dialog first)<br />
<br />
This convention increases predictability and safety for the user.<br />
:: [[File:styleguide_buttons.png|frameless]]<br />
<br />
Note that in some languages, like in German, a space character is added between labels and ellipses ("Formatieren ...").<br />
<br />
=== Checkboxes ===<br />
<br />
* The text is always placed to the right of the checkbox.<br />
* A uniform grid alignment creates a calm and consistent appearance.<br />
:: [[File:styleguide_checkmarks.png|frameless]]<br />
<br />
=== Compact Interfaces ===<br />
<br />
Even though modern systems support large screens, interfaces should remain scalable and fully usable on 1024×768 displays. MUI supports this largely automatically; nevertheless, developers should:<br />
* avoid unnecessarily wide buttons and text fields.<br />
* move explanatory content into tooltips if needed.<br />
<br />
== Keyboard Shortcuts ==<br />
<br />
Keyboard shortcuts improve operation speed and should be available everywhere. Especially in settings windows, language conventions apply: the underline is usually placed on the first letter of the term (e.g., Save: "S", Use: "U", Cancel: "C").<br />
<br />
If the number of available letters is insufficient, the interface should be redesigned, or rarely used options placed in the context menu of a MUI object or in the screen menu.<br />
:: [[File:styleguide_shortcuts.png|332px|frameless]]<br />
<br />
== Screen Menus ==<br />
<br />
=== Project vs. Application Menu ===<br />
<br />
A Project menu is only appropriate if the application can actually load or save project files. Otherwise, the menu should simply use the application's name.<br />
:: [[File:styleguide_project_menu.png|frameless]] [[File:styleguide_application_menu.png|frameless|top]]<br />
<br />
=== Settings ===<br />
<br />
Every application should include a ''Settings'' menu, even if it has no custom options.<br />
<br />
At minimum, it must contain the MUI entry, which provides access to the application's local UI settings.<br />
:: [[File:styleguide_settings_menu.png|frameless]]<br />
<br />
=== About Window ===<br />
<br />
MorphOS provides the Aboutbox.class, allowing developers to implement a uniform, professional about window with no extra effort.<br />
<br />
=== Standard Key Combinations ===<br />
<br />
There are established shortcuts (using the right Command key) that should be universal:<br />
<br />
* Q -> Quit<br />
* ? -> About<br />
* P -> Print<br />
* N -> New Project<br />
* O -> Open Project<br />
* S -> Save<br />
* A -> Save As<br />
* X -> Cut<br />
* C -> Copy<br />
* V -> Paste<br />
<br />
=== Direct and Indirect Actions ===<br />
<br />
As with buttons, if a menu entry opens a new window, it must end with an ellipsis ("...").<br />
<br />
== Learning from Existing MorphOS Programs ==<br />
<br />
It is worthwhile to study applications included with the system. While not perfect, they generally implement UI conventions very well and serve as best-practice references for your own software.<br />
<br />
== Summary ==<br />
<br />
By consistently following a few clear design principles, MorphOS applications can be developed professionally and system-conformantly without significant extra effort. Clean archive organization, correct version strings, consistent user interfaces, and adherence to established conventions result in applications that integrate seamlessly into the system and feel immediately familiar to users.</div>
JPV
https://library.morph.zone/index.php?title=Style_Guide&diff=4381
Style Guide
2025-11-27T10:06:01Z
<p>JPV: </p>
<hr />
<div>This article presents fundamental recommendations for developing high-quality MorphOS software. Many applications do not fail because of missing functionality, but because of details that negatively affect the user experience. The following guidelines help avoid common pitfalls and ensure that applications integrate consistently into the MorphOS environment.<br />
<br />
== Structure of the Software Archive ==<br />
<br />
A professional first impression begins with the structure of the distributed archive. A program should always be delivered inside its own directory without version numbers in the directory or file names. This makes handling software packages easier for both the user and the system.<br />
<br />
Example:<br />
<br />
The fictional tool ''Brawny'' is distributed as an archive named ''Brawny.lha'', containing a folder ''Brawny'' with all relevant files, including a program icon. Subfolders such as ''Help'' or language directories should each have their own .info file; purely system-related folders like ''Catalogs'' do not need one.<br />
<br />
<nowiki><br />
Ram Disk:> lha x Brawny.lha<br />
<br />
Extracting from archive 'Brawny.lha':<br />
Extracting: ( 4716/ 4716) Brawny.info<br />
Extracting: ( 6567813/ 6567813) Brawny/Brawny<br />
Extracting: ( 30276/ 30276) Brawny/Brawny.info<br />
Extracting: ( 54414/ 54414) Brawny/Brawny.readme<br />
Extracting: ( 54/ 54) Brawny/Brawny.readme.info<br />
5 files extracted, all files OK.</nowiki><br />
<br />
A clean archive structure improves access via both the Shell and the graphical Ambient interface.<br />
<br />
== The Correct Version String ==<br />
<br />
MorphOS requires a strictly defined format for version strings. Only when applications follow this standard can tools such as [[Shell_Commands/Version | Version]], package managers, or file comparison utilities work reliably.<br />
<br />
Version string format:<br />
<br />
$VER: <ApplicationName> <Version>.<Revision> (<DD.MM.YY>) © <Year AuthorName> <optional additional info><br />
<br />
Important notes:<br />
<br />
* Version and revision consist of digits only.<br />
* No letters or further sub-versions.<br />
* The exact location in the program code is irrelevant, but it should appear early so it can be read quickly.<br />
<br />
An incorrect version string can cause scripts or system tools to malfunction and should therefore be avoided at all costs.<br />
<br />
== User Interface Principles ==<br />
=== Localization ===<br />
<br />
Supporting multiple languages should be standard practice today. MorphOS provides extensive mechanisms for this purpose, and developers should make use of them.<br />
<br />
=== Labeling of UI Elements ===<br />
<br />
Labels for input elements should always end with a colon. This clearly indicates their association to the user.<br />
:: [[File:styleguide_labels.png|frameless]]<br />
<br />
=== Buttons and Ellipses ===<br />
<br />
Ellipsis (three dots) is added to a button label to distinguish between direct and indirect actions.<br />
<br />
A clear rule applies to it:<br />
* Direct action: "Format" (action starts immediately)<br />
* Indirect action: "Format..." (opens a new window or confirmation dialog first)<br />
<br />
This convention increases predictability and safety for the user.<br />
:: [[File:styleguide_buttons.png|frameless]]<br />
<br />
Note that in some languages, like in German, a space character is added between labels and ellipses ("Formatieren ...").<br />
<br />
=== Checkboxes ===<br />
<br />
* The text is always placed to the right of the checkbox.<br />
* A uniform grid alignment creates a calm and consistent appearance.<br />
:: [[File:styleguide_checkmarks.png|frameless]]<br />
<br />
=== Compact Interfaces ===<br />
<br />
Even though modern systems support large screens, interfaces should remain scalable and fully usable on 1024×768 displays. MUI supports this largely automatically; nevertheless, developers should:<br />
* avoid unnecessarily wide buttons and text fields.<br />
* move explanatory content into tooltips if needed.<br />
<br />
== Keyboard Shortcuts ==<br />
<br />
Keyboard shortcuts improve operation speed and should be available everywhere. Especially in settings windows, language conventions apply: the underline is usually placed on the first letter of the term (e.g., Save: "S", Use: "U", Cancel: "C").<br />
<br />
If the number of available letters is insufficient, the interface should be redesigned, or rarely used options placed in the context menu of a MUI object or in the screen menu.<br />
:: [[File:styleguide_shortcuts.png|332px|frameless]]<br />
<br />
== Screen Menus ==<br />
<br />
=== Project vs. Application Menu ===<br />
<br />
A Project menu is only appropriate if the application can actually load or save project files. Otherwise, the menu should simply use the application's name.<br />
:: [[File:styleguide_project_menu.png|frameless]] [[File:styleguide_application_menu.png|frameless|top]]<br />
<br />
=== Settings ===<br />
<br />
Every application should include a ''Settings'' menu, even if it has no custom options.<br />
<br />
At minimum, it must contain the MUI entry, which provides access to the application's local UI settings.<br />
:: [[File:styleguide_settings_menu.png|frameless]]<br />
<br />
=== About Window ===<br />
<br />
MorphOS provides the Aboutbox.class, allowing developers to implement a uniform, professional about window with no extra effort.<br />
<br />
=== Standard Key Combinations ===<br />
<br />
There are established shortcuts (using the right Command key) that should be universal:<br />
<br />
* Q -> Quit<br />
* ? -> About<br />
* P -> Print<br />
* N -> New project<br />
* O -> Open project<br />
* S -> Save<br />
* A -> Save As<br />
* X -> Cut<br />
* C -> Copy<br />
* V -> Paste<br />
<br />
=== Direct and Indirect Actions ===<br />
<br />
As with buttons, if a menu entry opens a new window, it must end with an ellipsis ("...").<br />
<br />
== Learning from Existing MorphOS Programs ==<br />
<br />
It is worthwhile to study applications included with the system. While not perfect, they generally implement UI conventions very well and serve as best-practice references for your own software.<br />
<br />
== Summary ==<br />
<br />
By consistently following a few clear design principles, MorphOS applications can be developed professionally and system-conformantly without significant extra effort. Clean archive organization, correct version strings, consistent user interfaces, and adherence to established conventions result in applications that integrate seamlessly into the system and feel immediately familiar to users.</div>
JPV
https://library.morph.zone/index.php?title=Main_Page&diff=4380
Main Page
2025-11-27T07:45:12Z
<p>JPV: /* Development */</p>
<hr />
<div>__NOTOC__<br />
<br />
<div id="siteLogo" style="float: right;"></div><br />
<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#274572;">Welcome to the MorphOS Library,</div><br />
<div style="top:+0.2em; font-size:95%; margin-bottom: 30px;">the wiki based library of MorphOS related documentation.</div><br />
<br />
<strong>Would you like to contribute and edit articles?</strong><br><br />
Please contact us to set up an account via:<br />
<div style="margin-top: -10px; margin-bottom: 20px;">https://morph.zone/message2library.png</div><br />
'''Important notes to editors:''' [[Basic Guidelines]] - [[List of Wanted Articles]]<br />
----<br />
<small>This page in other languages: [[Strona główna|Polish]] [[Page principale|Français]]</small><br />
<br />
==About MorphOS==<br />
MorphOS - The Lightning OS<br />
<div class="threecolumns"><br />
* [[What is MorphOS?]]<br />
* [[Hardware Platforms]]<br />
* [[Installation]]<br />
* [[Characteristic features]]<br />
* [[MorphOS integration]]<br />
* [[MorphOS Development]]<br />
* [[Developer tools]]<br />
* [[3D graphics]]<br />
* [[Games]]<br />
* [[MorphOS key applications]]<br />
* [[Platform expansion]]<br />
* [[Who needs MorphOS?]]<br />
* [[Conclusions]]<br />
* [[Useful links]]<br />
* [[F.A.Q.]]<br />
* [[Historical notes]]<br />
* [[Contributors]]</div><br />
A five minute read for users familiar with the Commodore Amiga<br />
*[[MorphOS in 5 minutes]]<br />
<br />
==Articles==<br />
The core of the MorphOS Library can be found here. Along with the provided manuals, there are several documents designed to help users get the most out of their MorphOS powered computer.<br />
<br />
* [[Fundamentals of MorphOS]]<br />
* [[Dictionary of Terms]]<br />
* [[First_Steps_Using_MorphOS | First Steps Using MorphOS]]<br />
* [[Volume Names]]<br />
* [[Applications|Applications Included with MorphOS]]<br />
* [[Tools|Tools Included with MorphOS]]<br />
* [[Utilities|Utilities Included with MorphOS]]<br />
* [[Screenbar_Modules|Screenbar Modules Included with MorphOS]]<br />
* [[Bundled_Games|Games Included with MorphOS]]<br />
* [[Blankers|Blankers Included with MorphOS]]<br />
* [[Shell Commands|Shell: Commands]]<br />
* [[Pattern matching|Shell: Pattern Matching]]<br />
* [[Filesystems | File Systems]]<br />
* [[Supported Computers]]<br />
* [[Supported HD cards]]<br />
* [[Hardware Compatibility]]<br />
* [[MIDI | MIDI Support]]<br />
* [[Tips and Tricks]]<br />
<br />
==Tutorials==<br />
Welcome to the Tutorials section of the MorphOS Library. In this aisle of the library you can find examples and step by step instructions to help get the most out of your MorphOS experience.<br />
<br />
*[[Getting_Started | Getting Started - A Beginner's Guide to MorphOS]]<br />
*[[Modifying the User-Startup file]]<br />
*[[Configuring_Network | Configuring a Network Connection]]<br />
*[[Installing_software | Installing Third Party Software]]<br />
*[[Dual-boot MorphOS and MacOS X on a Mac Mini G4]]<br />
*[[How to write Mails with SimpleMail]]<br />
*[[Creating Backups]]<br />
*[[MorphOS External USB Drive Backup Guide]]<br />
*[[Scanning with SCANdal]]<br />
*[[Recording an LP with Audio Evolution 4]]<br />
*[[Passwordless SSH login with RemoteShell]]<br />
*[[How to Install Directory Opus Magellan II]]<br />
*[[How to Make MorphOS Look Like OS4]]<br />
*[[How to Use Game Controllers]]<br />
*[[Preparing_an_Amiga_Hard_Drive]]<br />
*[[Mounting_Network_Drives]]<br />
*[[How to translate program with SimpleCat]]<br />
*[[Creating_Ambient_Filetypes]]<br />
*[[Open_Firmware | Using Open Firmware]]<br />
*[[Print_System | Using the New Printing System]]<br />
*[[Multi-display | Using Multi-display Setups]]<br />
<br />
==Development==<br />
In the development section of the MorphOS Library, you can find a collection of helpful articles and tutorials focused on MorphOS software development.<br />
<br />
*[[First steps in MorphOS programming]]<br />
*[[Magic User Interface Programming]]<br />
*[[In-depth: The New MorphOS Memory System]]<br />
*[[Reggae: MorphOS multimedia framework]]<br />
*[[An Introduction to MorphOS PPC Assembly]]<br />
*[[Advanced Topics]]<br />
*[[Getting Started with Lua]]<br />
*[[Crash_Course_to_Hollywood_Programming]]<br />
*[[Style_Guide | Design Guidelines for MorphOS Applications (Style Guide)]]<br />
<br />
==Benchmarks, Reports & Reviews==<br />
*[[jPV's MorphOS 2 Review]]<br />
*[[What's New in MorphOS 3]]<br />
*[[What's New in MorphOS 3.10]]<br />
*[[What's New in MorphOS 3.16]]<br />
<br />
==Links==<br />
The MorphOS Link Database is a collection of websites that are of interest to all current and potential future users of MorphOS. For easier navigation, we have separated the list of websites into multiple categories.<br />
<br />
*[[Links#Community_Portals_.26_Forums|Community Portals]]<br />
*[[Links#File_Repositories|File Repositories]]<br />
*[[Links#Shops|Shops]]<br />
*[[Links#Software|Software]]<br />
*[[Links#Developers|Developers]]<br />
*[[Links#Misc|Misc]]<br />
<br />
==Work in Progress==<br />
*[[ReTooled]]</div>
JPV
https://library.morph.zone/index.php?title=Style_Guide&diff=4379
Style Guide
2025-11-27T07:40:53Z
<p>JPV: </p>
<hr />
<div>''Author: Guido Mersmann''<br />
<br />
This article presents fundamental recommendations for developing high-quality MorphOS software. Many applications do not fail because of missing functionality, but because of details that negatively affect the user experience. The following guidelines help avoid common pitfalls and ensure that applications integrate consistently into the MorphOS environment.<br />
<br />
== Structure of the Software Archive ==<br />
<br />
A professional first impression begins with the structure of the distributed archive. A program should always be delivered inside its own directory without version numbers in the directory or file names. This makes handling software packages easier for both the user and the system.<br />
<br />
Example:<br />
<br />
The fictional tool ''Brawny'' is distributed as an archive named ''Brawny.lha'', containing a folder ''Brawny'' with all relevant files, including a program icon. Subfolders such as ''Help'' or language directories should each have their own .info file; purely system-related folders like ''Catalogs'' do not need one.<br />
<br />
<nowiki><br />
Ram Disk:> lha x Brawny.lha<br />
<br />
Extracting from archive 'Brawny.lha':<br />
Extracting: ( 4716/ 4716) Brawny.info<br />
Extracting: ( 6567813/ 6567813) Brawny/Brawny<br />
Extracting: ( 30276/ 30276) Brawny/Brawny.info<br />
Extracting: ( 54414/ 54414) Brawny/Brawny.readme<br />
Extracting: ( 54/ 54) Brawny/Brawny.readme.info<br />
5 files extracted, all files OK.</nowiki><br />
<br />
A clean archive structure improves access via both the Shell and the graphical Ambient interface.<br />
<br />
== The Correct Version String ==<br />
<br />
MorphOS requires a strictly defined format for version strings. Only when applications follow this standard can tools such as [[Shell_Commands/Version | Version]], package managers, or file comparison utilities work reliably.<br />
<br />
Version string format:<br />
<br />
$VER: <ApplicationName> <Version>.<Revision> (<DD.MM.YY>) © <Year AuthorName> <optional additional info><br />
<br />
Important notes:<br />
<br />
* Version and revision consist of digits only.<br />
* No letters or further sub-versions.<br />
* The exact location in the program code is irrelevant, but it should appear early so it can be read quickly.<br />
<br />
An incorrect version string can cause scripts or system tools to malfunction and should therefore be avoided at all costs.<br />
<br />
== User Interface Principles ==<br />
=== Localization ===<br />
<br />
Supporting multiple languages should be standard practice today. MorphOS provides extensive mechanisms for this purpose, and developers should make use of them.<br />
<br />
=== Labeling of UI Elements ===<br />
<br />
Labels for input elements should always end with a colon. This clearly indicates their association to the user.<br />
:: [[File:styleguide_labels.png|frameless]]<br />
<br />
=== Buttons and Ellipses ===<br />
<br />
Ellipsis (three dots) is added to a button label to distinguish between direct and indirect actions.<br />
<br />
A clear rule applies to it:<br />
* Direct action: "Format" (action starts immediately)<br />
* Indirect action: "Format..." (opens a new window or confirmation dialog first)<br />
<br />
This convention increases predictability and safety for the user.<br />
:: [[File:styleguide_buttons.png|frameless]]<br />
<br />
Note that in some languages, like in German, a space character is added between labels and ellipses ("Formatieren ...").<br />
<br />
=== Checkboxes ===<br />
<br />
* The text is always placed to the right of the checkbox.<br />
* A uniform grid alignment creates a calm and consistent appearance.<br />
:: [[File:styleguide_checkmarks.png|frameless]]<br />
<br />
=== Compact Interfaces ===<br />
<br />
Even though modern systems support large screens, interfaces should remain scalable and fully usable on 1024×768 displays. MUI supports this largely automatically; nevertheless, developers should:<br />
* avoid unnecessarily wide buttons and text fields.<br />
* move explanatory content into tooltips if needed.<br />
<br />
== Keyboard Shortcuts ==<br />
<br />
Keyboard shortcuts improve operation speed and should be available everywhere. Especially in settings windows, language conventions apply: the underline is usually placed on the first letter of the term (e.g., Save: "S", Use: "U", Cancel: "C").<br />
<br />
If the number of available letters is insufficient, the interface should be redesigned, or rarely used options placed in the context menu of a MUI object or in the screen menu.<br />
:: [[File:styleguide_shortcuts.png|332px|frameless]]<br />
<br />
== Screen Menus ==<br />
<br />
=== Project vs. Application Menu ===<br />
<br />
A Project menu is only appropriate if the application can actually load or save project files. Otherwise, the menu should simply use the application's name.<br />
:: [[File:styleguide_project_menu.png|frameless]] [[File:styleguide_application_menu.png|frameless|top]]<br />
<br />
=== Settings ===<br />
<br />
Every application should include a ''Settings'' menu, even if it has no custom options.<br />
<br />
At minimum, it must contain the MUI entry, which provides access to the application's local UI settings.<br />
:: [[File:styleguide_settings_menu.png|frameless]]<br />
<br />
=== About Window ===<br />
<br />
MorphOS provides the Aboutbox.class, allowing developers to implement a uniform, professional about window with no extra effort.<br />
<br />
=== Standard Key Combinations ===<br />
<br />
There are established shortcuts (using the right Command key) that should be universal:<br />
<br />
* Q -> Quit<br />
* ? -> About<br />
* P -> Print<br />
* N -> New project<br />
* O -> Open project<br />
* S -> Save<br />
* A -> Save As<br />
* X -> Cut<br />
* C -> Copy<br />
* V -> Paste<br />
<br />
=== Direct and Indirect Actions ===<br />
<br />
As with buttons, if a menu entry opens a new window, it must end with an ellipsis ("...").<br />
<br />
== Learning from Existing MorphOS Programs ==<br />
<br />
It is worthwhile to study applications included with the system. While not perfect, they generally implement UI conventions very well and serve as best-practice references for your own software.<br />
<br />
== Summary ==<br />
<br />
By consistently following a few clear design principles, MorphOS applications can be developed professionally and system-conformantly without significant extra effort. Clean archive organization, correct version strings, consistent user interfaces, and adherence to established conventions result in applications that integrate seamlessly into the system and feel immediately familiar to users.</div>
JPV
https://library.morph.zone/index.php?title=Style_Guide&diff=4378
Style Guide
2025-11-26T14:53:37Z
<p>JPV: </p>
<hr />
<div>''Author: Guido Mersmann''<br />
<br />
This article presents fundamental recommendations for developing high-quality MorphOS software. Many applications do not fail because of missing functionality, but because of details that negatively affect the user experience. The following guidelines help avoid common pitfalls and ensure that applications integrate consistently into the MorphOS environment.<br />
<br />
== Structure of the Software Archive ==<br />
<br />
A professional first impression begins with the structure of the distributed archive. A program should always be delivered inside its own directory without version numbers in the directory or file names. This makes handling software packages easier for both the user and the system.<br />
<br />
Example:<br />
<br />
The fictional tool ''Brawny'' is distributed as an archive named ''Brawny.lha'', containing a folder ''Brawny'' with all relevant files, including a program icon. Subfolders such as ''Help'' or language directories should each have their own .info file; purely system-related folders like ''Catalogs'' do not need one.<br />
<br />
<nowiki><br />
Ram Disk:> lha x Brawny.lha<br />
<br />
Extracting from archive 'Brawny.lha':<br />
Extracting: ( 4716/ 4716) Brawny.info<br />
Extracting: ( 6567813/ 6567813) Brawny/Brawny<br />
Extracting: ( 30276/ 30276) Brawny/Brawny.info<br />
Extracting: ( 54414/ 54414) Brawny/Brawny.readme<br />
Extracting: ( 54/ 54) Brawny/Brawny.readme.info<br />
5 files extracted, all files OK.</nowiki><br />
<br />
A clean archive structure improves access via both the Shell and the graphical Ambient interface.<br />
<br />
== The Correct Version String ==<br />
<br />
MorphOS requires a strictly defined format for version strings. Only when applications follow this standard can tools such as [[Shell_Commands/Version | Version]], package managers, or file comparison utilities work reliably.<br />
<br />
Version string format:<br />
<br />
$VER: <ApplicationName> <Version>.<Revision> (<DD.MM.YY>) © <Year AuthorName> <optional additional info><br />
<br />
Important notes:<br />
<br />
* Version and revision consist of digits only.<br />
* No letters or further sub-versions.<br />
* The exact location in the program code is irrelevant, but it should appear early so it can be read quickly.<br />
<br />
An incorrect version string can cause scripts or system tools to malfunction and should therefore be avoided at all costs.<br />
<br />
== User Interface Principles ==<br />
=== Localization ===<br />
<br />
Supporting multiple languages should be standard practice today. MorphOS provides extensive mechanisms for this purpose, and developers should make use of them.<br />
<br />
=== Labeling of UI Elements ===<br />
<br />
Labels for input elements should always end with a colon. This clearly indicates their association to the user.<br />
:: [[File:styleguide_labels.png|frameless]]<br />
<br />
=== Buttons and Ellipses ===<br />
<br />
To distinguish between direct and indirect actions, a clear rule applies:<br />
* Direct action: "Format" (action starts immediately)<br />
* Indirect action: "Format..." (opens a new window or confirmation dialog first)<br />
<br />
This convention increases predictability and safety for the user.<br />
:: [[File:styleguide_buttons.png|frameless]]<br />
<br />
=== Checkboxes ===<br />
<br />
* The text is always placed to the right of the checkbox.<br />
* A uniform grid alignment creates a calm and consistent appearance.<br />
:: [[File:styleguide_checkmarks.png|frameless]]<br />
<br />
=== Compact Interfaces ===<br />
<br />
Even though modern systems support large screens, interfaces should remain scalable and fully usable on 1024×768 displays. MUI supports this largely automatically; nevertheless, developers should:<br />
* avoid unnecessarily wide buttons and text fields.<br />
* move explanatory content into tooltips if needed.<br />
<br />
== Keyboard Shortcuts ==<br />
<br />
Keyboard shortcuts improve operation speed and should be available everywhere. Especially in settings windows, language conventions apply: the underline is usually placed on the first letter of the term (e.g., Save: "S", Use: "U", Cancel: "C").<br />
<br />
If the number of available letters is insufficient, the interface should be redesigned, or rarely used options placed in the context menu of a MUI object or in the screen menu.<br />
:: [[File:styleguide_shortcuts.png|frameless]]<br />
<br />
== Screen Menus ==<br />
<br />
=== Project vs. Application Menu ===<br />
<br />
A Project menu is only appropriate if the application can actually load or save project files. Otherwise, the menu should simply use the application's name.<br />
:: [[File:styleguide_project_menu.png|frameless]] [[File:styleguide_application_menu.png|frameless|top]]<br />
<br />
=== Settings ===<br />
<br />
Every application should include a ''Settings'' menu, even if it has no custom options.<br />
<br />
At minimum, it must contain the MUI entry, which provides access to the application's local UI settings.<br />
:: [[File:styleguide_settings_menu.png|frameless]]<br />
<br />
=== About Window ===<br />
<br />
MorphOS provides the Aboutbox.class, allowing developers to implement a uniform, professional about window with no extra effort.<br />
<br />
=== Standard Key Combinations ===<br />
<br />
There are established shortcuts (using the right Command key) that should be universal:<br />
<br />
* Q -> Quit<br />
* ? -> About<br />
* P -> Print<br />
* N -> New project<br />
* O -> Open project<br />
* S -> Save<br />
* A -> Save As<br />
* X -> Cut<br />
* C -> Copy<br />
* V -> Paste<br />
<br />
=== Direct and Indirect Actions ===<br />
<br />
As with buttons, if a menu entry opens a new window, it must end with "...".<br />
<br />
== Learning from Existing MorphOS Programs ==<br />
<br />
It is worthwhile to study applications included with the system. While not perfect, they generally implement UI conventions very well and serve as best-practice references for your own software.<br />
<br />
== Summary ==<br />
<br />
By consistently following a few clear design principles, MorphOS applications can be developed professionally and system-conformantly without significant extra effort. Clean archive organization, correct version strings, consistent user interfaces, and adherence to established conventions result in applications that integrate seamlessly into the system and feel immediately familiar to users.</div>
JPV
https://library.morph.zone/index.php?title=File:Styleguide_application_menu.png&diff=4377
File:Styleguide application menu.png
2025-11-26T14:44:23Z
<p>JPV: </p>
<hr />
<div></div>
JPV
https://library.morph.zone/index.php?title=File:Styleguide_shortcuts.png&diff=4376
File:Styleguide shortcuts.png
2025-11-26T14:27:51Z
<p>JPV: </p>
<hr />
<div></div>
JPV
https://library.morph.zone/index.php?title=File:Styleguide_settings_menu.png&diff=4375
File:Styleguide settings menu.png
2025-11-26T14:11:17Z
<p>JPV: </p>
<hr />
<div></div>
JPV
https://library.morph.zone/index.php?title=File:Styleguide_project_menu.png&diff=4374
File:Styleguide project menu.png
2025-11-26T14:11:05Z
<p>JPV: </p>
<hr />
<div></div>
JPV
https://library.morph.zone/index.php?title=File:Styleguide_labels.png&diff=4373
File:Styleguide labels.png
2025-11-26T14:10:45Z
<p>JPV: </p>
<hr />
<div></div>
JPV
https://library.morph.zone/index.php?title=File:Styleguide_checkmarks.png&diff=4372
File:Styleguide checkmarks.png
2025-11-26T14:10:31Z
<p>JPV: </p>
<hr />
<div></div>
JPV
https://library.morph.zone/index.php?title=File:Styleguide_buttons.png&diff=4371
File:Styleguide buttons.png
2025-11-26T14:10:01Z
<p>JPV: </p>
<hr />
<div></div>
JPV
https://library.morph.zone/index.php?title=Style_Guide&diff=4370
Style Guide
2025-11-26T13:14:58Z
<p>JPV: Created page with "''Author: Guido Mersmann'' This article presents fundamental recommendations for developing high-quality MorphOS software. Many applications do not fail because of missing fu..."</p>
<hr />
<div>''Author: Guido Mersmann''<br />
<br />
This article presents fundamental recommendations for developing high-quality MorphOS software. Many applications do not fail because of missing functionality, but because of details that negatively affect the user experience. The following guidelines help avoid common pitfalls and ensure that applications integrate consistently into the MorphOS environment.<br />
<br />
== Structure of the Software Archive ==<br />
<br />
A professional first impression begins with the structure of the distributed archive. A program should always be delivered inside its own directory without version numbers in the directory or file names. This makes handling software packages easier for both the user and the system.<br />
<br />
Example:<br />
<br />
The fictional tool ''Brawny'' is distributed as an archive named ''Brawny.lha'', containing a folder ''Brawny'' with all relevant files, including a program icon. Subfolders such as ''Help'' or language directories should each have their own .info file; purely system-related folders like ''Catalogs'' do not need one.<br />
<br />
<nowiki><br />
Ram Disk:> lha x Brawny.lha<br />
<br />
Extracting from archive 'Brawny.lha':<br />
Extracting: ( 4716/ 4716) Brawny.info<br />
Extracting: ( 6567813/ 6567813) Brawny/Brawny<br />
Extracting: ( 30276/ 30276) Brawny/Brawny.info<br />
Extracting: ( 54414/ 54414) Brawny/Brawny.readme<br />
Extracting: ( 54/ 54) Brawny/Brawny.readme.info<br />
5 files extracted, all files OK.</nowiki><br />
<br />
A clean archive structure improves access via both the Shell and the graphical Ambient interface.<br />
<br />
== The Correct Version String ==<br />
<br />
MorphOS requires a strictly defined format for version strings. Only when applications follow this standard can tools such as [[Shell_Commands/Version | Version]], package managers, or file comparison utilities work reliably.<br />
<br />
Version string format:<br />
<br />
$VER: <ApplicationName> <Version>.<Revision> (<DD.MM.YY>) © <Year AuthorName> <optional additional info><br />
<br />
Important notes:<br />
<br />
* Version and revision consist of digits only.<br />
* No letters or further sub-versions.<br />
* The exact location in the program code is irrelevant, but it should appear early so it can be read quickly.<br />
<br />
An incorrect version string can cause scripts or system tools to malfunction and should therefore be avoided at all costs.<br />
<br />
== User Interface Principles ==<br />
<br />
=== Localization ===<br />
<br />
Supporting multiple languages should be standard practice today. MorphOS provides extensive mechanisms for this purpose, and developers should make use of them.<br />
<br />
=== Labeling of UI Elements ===<br />
<br />
* Labels for input elements should always end with a colon. This clearly indicates their association to the user.<br />
<br />
=== Buttons and Ellipses ("...") ===<br />
<br />
To distinguish between direct and indirect actions, a clear rule applies:<br />
<br />
* Direct action: "Format" (action starts immediately)<br />
* Indirect action: "Format..." (opens a new window or confirmation dialog first)<br />
<br />
This convention increases predictability and safety for the user.<br />
<br />
=== Checkboxes ===<br />
<br />
* The text is always placed to the right of the checkbox.<br />
* A uniform grid alignment creates a calm and consistent appearance.<br />
<br />
=== Compact Interfaces ===<br />
<br />
Even though modern systems support large screens, interfaces should remain scalable and fully usable on 1024×768 displays. MUI supports this largely automatically; nevertheless, developers should:<br />
<br />
* avoid unnecessarily wide buttons and text fields.<br />
* move explanatory content into tooltips if needed.<br />
<br />
== Keyboard Shortcuts ==<br />
<br />
Keyboard shortcuts improve operation speed and should be available everywhere. Especially in settings windows, language conventions apply: the underline is usually placed on the first letter of the term (e.g., Save: "S", Use: "U", Cancel: "C").<br />
<br />
If the number of available letters is insufficient, the interface should be redesigned, or rarely used options placed in the context menu of a MUI object or in the screen menu.<br />
<br />
== Screen Menus ==<br />
<br />
=== Project vs. Application Menu ===<br />
<br />
A Project menu is only appropriate if the application can actually load or save project files. Otherwise, the menu should simply use the application's name.<br />
<br />
=== Settings ===<br />
<br />
Every application should include a ''Settings'' menu, even if it has no custom options.<br />
<br />
At minimum, it must contain the MUI entry, which provides access to the application's local UI settings.<br />
<br />
=== About Window ===<br />
<br />
MorphOS provides the Aboutbox.class, allowing developers to implement a uniform, professional about window with no extra effort.<br />
<br />
=== Standard Key Combinations ===<br />
<br />
There are established shortcuts (using the right Command key) that should be universal:<br />
<br />
* Q -> Quit<br />
* ? -> About<br />
* P -> Print<br />
* N -> New project<br />
* O -> Open project<br />
* S -> Save<br />
* A -> Save As<br />
* X -> Cut<br />
* C -> Copy<br />
* V -> Paste<br />
<br />
As with buttons, if a menu entry opens a new window, it must end with "...".<br />
<br />
== Learning from Existing MorphOS Programs ==<br />
<br />
It is worthwhile to study applications included with the system. While not perfect, they generally implement UI conventions very well and serve as best-practice references for your own software.<br />
<br />
== Summary ==<br />
<br />
By consistently following a few clear design principles, MorphOS applications can be developed professionally and system-conformantly without significant extra effort. Clean archive organization, correct version strings, consistent user interfaces, and adherence to established conventions result in applications that integrate seamlessly into the system and feel immediately familiar to users.</div>
JPV
https://library.morph.zone/index.php?title=Applications/RDesktop&diff=4369
Applications/RDesktop
2025-10-08T07:48:06Z
<p>JPV: </p>
<hr />
<div>== Description ==<br />
<br />
Remote Desktop client supporting the RDP protocol, as used by MS Windows. <br />
<br />
The application directory contains RDesktop (the tool itself) and RDesktopGUI (a graphical user interface for setting various options and arguements when launching rdesktop).<br />
<br />
<br />
== Usage ==<br />
<br />
<br />
== Notes ==<br />
<br />
To be able to connect to a Windows 10/11 (Pro) computer, enable the Remote Desktop setting and disable the requirement of Network Level Authentication on the remote computer. If the NLA setting is enabled, you get a CredSSP error when trying to connect on the remote machine.<br />
<br />
To prepare a Windows 11 Pro setup for connecting from MorphOS:<br />
# Open Settings -> System -> Remote Desktop<br />
# Toggle the Remote Desktop setting On<br />
# Click the arrow on the right side of the toggle button to get more settings<br />
# Disable the "Require devices to use Network Level Authentication to connect" setting<br />
<br />
Now you should be able to connect to the Windows computer if you set the Experience/Encryption setting to TLS 1.2 in the MorphOS RDesktop client.<br />
<br />
If you're using a Microsoft account for an enabled user, enter the email address as the username in the RDesktop GUI.<br />
<br />
If you want to use other encryption settings, or disable it completely, you can use this solution at the server side ([https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/remote-desktop-connection-not-workin-after-win-10/f45c1446-5059-4ac3-90e5-81580f3f95d6 source]):<br />
<br />
# Open a Run dialog using Win-R. Type "gpedit.msc" and hit Enter.<br />
# On the left tree view, click on Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security<br />
# Double-click on the "Require use of specific security layer for remote (RDP) connections" setting on the right.<br />
# Select the "Enabled" radio button<br />
# Select "Negotiate" (or "RDP") from the "Security Layer" drop-down and click OK.<br />
<br />
<br />
<br />
== Screenshot ==<br />
: [[File:MorphOS3_jPV_Rdesktop.png|320px]]</div>
JPV
https://library.morph.zone/index.php?title=Open_Firmware&diff=4368
Open Firmware
2025-08-20T09:08:17Z
<p>JPV: </p>
<hr />
<div>== Preface ==<br />
'''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.<br />
<br />
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.<br />
<br />
Output texts in these examples have been truncated in most cases to show only the information of interest.<br />
<br />
== Accessing the User Interface ==<br />
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.<br />
<br />
<nowiki><br />
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50<br />
Copyright 1994-2005 Apple Computer, Inc.<br />
All Rights Reserved.<br />
<br />
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11<br />
<br />
To continue booting, type "mac-boot" and press return.<br />
To shut down, type "shut-down" and press return.<br />
<br />
Release keys to continue!<br />
<br />
ok<br />
0 > _</nowiki><br />
<br />
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.<br />
<br />
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].<br />
<br />
== Useful Commands ==<br />
* '''mac-boot''' - Continues booting from the current OF state<br />
* '''reset-all''' - Resets the machine to the power-on state and reboots<br />
* '''shut-down''' - Shuts down the machine<br />
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory<br />
* '''go''' - Runs/boots the loaded file<br />
* '''boot <file> <args>''' - Loads an OF code file and boots it<br />
* '''printenv''' - Prints environment variable values<br />
* '''setenv''' - Sets environment variable values<br />
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)<br />
* '''.properties''' - Displays a list of properties for the selected device<br />
* '''ls''' - Displays contents of the current path in the device tree<br />
* '''pwd''' - Displays the current path within the device tree<br />
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)<br />
* '''dir''' - Lists files on a partition<br />
<br />
== Environment Variables ==<br />
Use the ''printenv'' command to list all environment variable values.<br />
<br />
<nowiki><br />
0 > printenv<br />
-------------- Partition: common -------- Signature: 0x70 ---------------<br />
little-endian? false false<br />
real-mode? false false<br />
auto-boot? true true<br />
skip-netboot? false false<br />
use-nvramrc? false false</nowiki><br />
<br />
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.<br />
<br />
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.<br />
<br />
<nowiki><br />
0 > setenv skip-netboot? true<br />
0 > printenv skip-netboot?<br />
-------------- Partition: common -------- Signature: 0x70 ---------------<br />
skip-netboot? true false</nowiki><br />
<br />
== Examining Devices ==<br />
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.<br />
<br />
=== Listing Aliases ===<br />
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.<br />
<br />
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:<br />
<nowiki><br />
0 > dev /aliases<br />
0 > .properties<br />
name aliases <br />
pci0 /pci@f0000000<br />
agp /pci@f0000000<br />
pci1 /pci@f2000000<br />
pci2 /pci@f4000000<br />
usb0 /pci@f2000000/@15<br />
usb1 /pci@f2000000/@15,1<br />
usb2 /pci@f2000000/@15,2<br />
hd /pci@f4000000/ata-6@d/disk@0<br />
cd /pci@f4000000/ata-6@d/disk@1<br />
ud /pci@f2000000/usb@15,1/disk@1</nowiki><br />
<br />
The commands can also be input combined, on a single line:<br />
<nowiki><br />
0 > dev /aliases .properties<br />
name aliases <br />
pci0 /pci@f0000000<br />
agp /pci@f0000000<br />
pci1 /pci@f2000000<br />
pci2 /pci@f4000000<br />
usb0 /pci@f2000000/@15<br />
usb1 /pci@f2000000/@15,1<br />
usb2 /pci@f2000000/@15,2<br />
hd /pci@f4000000/ata-6@d/disk@0<br />
cd /pci@f4000000/ata-6@d/disk@1<br />
ud /pci@f2000000/usb@15,1/disk@1</nowiki><br />
<br />
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:<br />
<nowiki><br />
0 > devalias<br />
name aliases <br />
pci0 /pci@f0000000<br />
agp /pci@f0000000<br />
pci1 /pci@f2000000<br />
pci2 /pci@f4000000<br />
usb0 /pci@f2000000/@15<br />
usb1 /pci@f2000000/@15,1<br />
usb2 /pci@f2000000/@15,2<br />
hd /pci@f4000000/ata-6@d/disk@0<br />
cd /pci@f4000000/ata-6@d/disk@1<br />
ud /pci@f2000000/usb@15,1/disk@1</nowiki><br />
<br />
=== Other Useful Properties ===<br />
''.properties'' on the root device shows the computer specs:<br />
<nowiki><br />
0 > dev / .properties<br />
model PowerBook5,9<br />
compatible PowerBook5,9<br />
MacRISC3<br />
Power Macintosh<br />
<br />
serial-number SX0</nowiki><br />
<br />
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:<br />
<nowiki><br />
0 > dev enet .properties<br />
vendor-id 0000106b<br />
device-id 0000006b<br />
name ethernet<br />
device_type network<br />
local-mac-address 001124e3 6666</nowiki><br />
<br />
=== Listing Devices ===<br />
The ''ls'' command lists devices found in the current device in the device tree:<br />
<nowiki><br />
0 > dev usb1 ls<br />
ff9e1650 /disk@1<br />
ff9e1a28: /device@2<br />
ff9e1c48: /keyboard@0<br />
ff9e1f88: /mouse@1<br />
ff9e2230: /interface@2</nowiki><br />
<br />
To list a complete list of all devices in the system:<br />
<nowiki><br />
0 > dev / ls</nowiki><br />
<br />
=== Listing Files ===<br />
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.<br />
<br />
Syntax of the ''dir'' command is:<br />
'''dir disk:partition,path'''<br />
<br />
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /<br />
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank<br />
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory<br />
<br />
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:<br />
<nowiki><br />
0 > dir hd:,\</nowiki><br />
<br />
Listing the root directory from the first partition on the (default) HD:<br />
<nowiki><br />
0 > dir hd:1,\</nowiki><br />
<br />
Listing the root directory from a CD:<br />
<nowiki><br />
0 > dir cd:,\</nowiki><br />
<br />
Listing a sub-directory from a CD:<br />
<nowiki><br />
0 > dir cd:,\mac_ppc32</nowiki><br />
<br />
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):<br />
<nowiki><br />
0 > dir usb1/disk@1:,\</nowiki><br />
<br />
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:<br />
<nowiki><br />
0 > dir ud:,\</nowiki><br />
<br />
== Adding Custom Aliases ==<br />
The ''devalias'' command adds temporary user defined aliases.<br />
<br />
<nowiki><br />
0 > devalias dh /pci@f4000000/ata-6@d/disk@0</nowiki><br />
<br />
''nvalias'' stores an alias in NVRAMRC. Variable ''use-nvramrc?'' needs to be set to true in order to execute NVRAMRC script at startup.<br />
<br />
<nowiki><br />
0 > nvalias dh /pci@f4000000/ata-6@d/disk@0</nowiki><br />
<br />
''nvunalias'' deletes an alias.<br />
<br />
<nowiki><br />
0 > nvunalias dh</nowiki><br />
<br />
You can replace existing aliases with your own ones. Removing them will revert to original values.<br />
<br />
=== Creating an Alias for a USB Disk ===<br />
If your firmware version doesn't create the ''ud'' alias by default, you can add the alias by yourself. The only drawback is that you'll have to use the same physical USB port always, or create several aliases for each port.<br />
<br />
1. Check that the alias doesn't exist alredy<br />
<nowiki><br />
0 > devalias</nowiki><br />
<br />
2. List all devices (press the Space Bar to see them all)<br />
<nowiki><br />
0 > dev / ls</nowiki><br />
<br />
3. Look for a USB device that contains your disk (''disk@1'', for instance), and combine list tree entries to a full path. The path can be verified, for example, by listing files on the disk.<br />
<nowiki><br />
0 > dir /pci@f2000000/usb@1b,1/disk@1:,\</nowiki><br />
<br />
4. Create a permanent alias with the ''nvalias'' command (and/or a temporary alias with ''devalias'' instead of ''nvalias'' for testing it before a reboot)<br />
<nowiki><br />
0 > nvalias ud /pci@f2000000/usb@1b,1/disk@1</nowiki><br />
<br />
5. Make sure the ''use-nvramrc?'' env variable is set<br />
<nowiki><br />
0 > setenv use-nvramrc? true</nowiki><br />
<br />
6. Reboot the computer and the ''ud'' alias should be available on the firmware now<br />
<nowiki><br />
0 > reset-all</nowiki><br />
<br />
== Booting MorphOS ==<br />
=== Basics ===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Type in this line (if you have a MorphOS installation on your HD):<br />
<br />
0 > load hd:,\boot.img<br />
<br />
And you'll see output like this:<br />
<nowiki><br />
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950<br />
<br />
Loading ELF<br />
ok<br />
0 > _</nowiki><br />
<br />
"Loading ELF" tells you that the file has been found and loaded.<br />
<br />
The file can be booted with the ''go'' command then:<br />
<nowiki><br />
0 > go<br />
DO-QUIESCE finished_</nowiki><br />
<br />
"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.<br />
<br />
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.<br />
<br />
The previous example can be achieved with this single line:<br />
<nowiki><br />
0 > boot hd:,\boot.img</nowiki><br />
<br />
And the output should then look like this:<br />
<nowiki><br />
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950<br />
<br />
Loading ELF<br />
<br />
DO-QUIESCE finished_</nowiki><br />
<br />
=== Boot Arguments ===<br />
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. Note that Sam460ex/cr and AmigaOne X5000 systems don't use Open Firmware, but the boot arguments can be given on them too by setting an environment variable in their [[Tips_and_Tricks#MorphOS_Boot_Arguments_on_U-boot_Systems | U-boot console]].<br />
<br />
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.<br />
<br />
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.<br />
<br />
* '''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.[[File:MorphOS-BootMenu.png|thumb|MorphOS bootmenu]]<br />
* '''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".<br />
* '''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, the '''F1''' key, or the '''left mouse button''' during the MorphOS boot process (you'll have to try which option works on your hardware). 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.<br />
<br />
=== Examples ===<br />
==== Booting from CD ====<br />
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.<br />
<br />
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.<br />
<br />
To boot any inserted CD that is bootable on Macs:<br />
0 > boot cd:,\\:tbxi<br />
<br />
"\\" 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.<br />
<br />
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.<br />
<br />
List the contents of the CD:<br />
<nowiki><br />
0 > dir cd:,\<br />
<br />
Volume: MorphOSBoot<br />
Size/ GMT File/Dir<br />
bytes date time TYPE CRTR Name<br />
94 07/04/2018 04:54:42 ???? ???? .morphosid<br />
2287135 07/04/2018 04:03:02 boot UNIX boot.img<br />
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img<br />
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img<br />
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img<br />
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img<br />
01/01/1904 00:00:00 *mac_ppc32<br />
01/01/1904 00:00:00 mac_ppc64</nowiki><br />
<br />
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.<br />
<br />
If we wanted to boot the CD on a G5 Mac:<br />
<nowiki><br />
0 > dir cd:,\mac_ppc64<br />
<br />
Size/ GMT File/Dir<br />
bytes date time TYPE CRTR Name<br />
1499688 07/04/2018 04:03:02 boot UNIX boot.img<br />
<br />
ok<br />
0 > boot cd:,\mac_ppc64\boot.img bd cd0</nowiki><br />
<br />
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.<br />
<br />
To boot into the MorphOS boot menu on a G5 Mac:<br />
0 > boot cd:,\mac_ppc64\boot.img bm<br />
<br />
And the same for a G4 Mac:<br />
0 > boot cd:,\mac_ppc32\boot.img bm<br />
<br />
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:<br />
0 > boot cd:,\\boot.img bm<br />
<br />
==== Booting MorphOS ISO from USB ====<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:<br />
0 > boot ud:,\boot.img bi umsd0:morphos.iso<br />
<br />
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:<br />
0 > dir ud:,\<br />
<br />
If you don't have the ''ud'' alias, you'll have to search usb* aliases for a correct path in the OF tree (or [[Open_Firmware#Creating_an_Alias_for_a_USB_Disk | create a new alias]]). 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.<br />
<br />
<nowiki><br />
0 > dev usb0 ls<br />
ok<br />
0 > dev usb1 ls<br />
ff9e1650: /disk@1<br />
0 > dir usb1/disk@1:,\<br />
Volume: USB<br />
258048000 07-24-2018 18:34:24 morphos.iso<br />
1501436 07-04-2018 04:03:02 boot.img<br />
ok<br />
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso</nowiki><br />
<br />
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:<br />
<nowiki><br />
0 > dev usb1 ls<br />
ff9e1650: /hub@1<br />
ff9e1860: /disk@4<br />
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso</nowiki><br />
<br />
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.<br />
<br />
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.<br />
<nowiki><br />
0 > dir hd:1,\<br />
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device<br />
ok<br />
0 > dir hd:2,\<br />
<br />
Volume: OSX<br />
Size/ GMT File/Dir<br />
bytes date time TYPE CRTR Name<br />
07/22/2017 07:27:40 Applications<br />
09/27/2016 09:59:40 bin<br />
1501436 07-04-2018 04:03:02 ???? UNIX boot.img<br />
ok<br />
0 > boot hd:2,\boot.img bi umsd0:morphos.iso</nowiki></div>
JPV
https://library.morph.zone/index.php?title=Open_Firmware&diff=4367
Open Firmware
2025-08-20T08:57:53Z
<p>JPV: Added an example to add the UD alias for USB disks</p>
<hr />
<div>== Preface ==<br />
'''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.<br />
<br />
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.<br />
<br />
Output texts in these examples have been truncated in most cases to show only the information of interest.<br />
<br />
== Accessing the User Interface ==<br />
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.<br />
<br />
<nowiki><br />
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50<br />
Copyright 1994-2005 Apple Computer, Inc.<br />
All Rights Reserved.<br />
<br />
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11<br />
<br />
To continue booting, type "mac-boot" and press return.<br />
To shut down, type "shut-down" and press return.<br />
<br />
Release keys to continue!<br />
<br />
ok<br />
0 > _</nowiki><br />
<br />
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.<br />
<br />
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].<br />
<br />
== Useful Commands ==<br />
* '''mac-boot''' - Continues booting from the current OF state<br />
* '''reset-all''' - Resets the machine to the power-on state and reboots<br />
* '''shut-down''' - Shuts down the machine<br />
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory<br />
* '''go''' - Runs/boots the loaded file<br />
* '''boot <file> <args>''' - Loads an OF code file and boots it<br />
* '''printenv''' - Prints environment variable values<br />
* '''setenv''' - Sets environment variable values<br />
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)<br />
* '''.properties''' - Displays a list of properties for the selected device<br />
* '''ls''' - Displays contents of the current path in the device tree<br />
* '''pwd''' - Displays the current path within the device tree<br />
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)<br />
* '''dir''' - Lists files on a partition<br />
<br />
== Environment Variables ==<br />
Use the ''printenv'' command to list all environment variable values.<br />
<br />
<nowiki><br />
0 > printenv<br />
-------------- Partition: common -------- Signature: 0x70 ---------------<br />
little-endian? false false<br />
real-mode? false false<br />
auto-boot? true true<br />
skip-netboot? false false<br />
use-nvramrc? false false</nowiki><br />
<br />
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.<br />
<br />
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.<br />
<br />
<nowiki><br />
0 > setenv skip-netboot? true<br />
0 > printenv skip-netboot?<br />
-------------- Partition: common -------- Signature: 0x70 ---------------<br />
skip-netboot? true false</nowiki><br />
<br />
== Examining Devices ==<br />
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.<br />
<br />
=== Listing Aliases ===<br />
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.<br />
<br />
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:<br />
<nowiki><br />
0 > dev /aliases<br />
0 > .properties<br />
name aliases <br />
pci0 /pci@f0000000<br />
agp /pci@f0000000<br />
pci1 /pci@f2000000<br />
pci2 /pci@f4000000<br />
usb0 /pci@f2000000/@15<br />
usb1 /pci@f2000000/@15,1<br />
usb2 /pci@f2000000/@15,2<br />
hd /pci@f4000000/ata-6@d/disk@0<br />
cd /pci@f4000000/ata-6@d/disk@1<br />
ud /pci@f2000000/usb@15,1/disk@1</nowiki><br />
<br />
The commands can also be input combined, on a single line:<br />
<nowiki><br />
0 > dev /aliases .properties<br />
name aliases <br />
pci0 /pci@f0000000<br />
agp /pci@f0000000<br />
pci1 /pci@f2000000<br />
pci2 /pci@f4000000<br />
usb0 /pci@f2000000/@15<br />
usb1 /pci@f2000000/@15,1<br />
usb2 /pci@f2000000/@15,2<br />
hd /pci@f4000000/ata-6@d/disk@0<br />
cd /pci@f4000000/ata-6@d/disk@1<br />
ud /pci@f2000000/usb@15,1/disk@1</nowiki><br />
<br />
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:<br />
<nowiki><br />
0 > devalias<br />
name aliases <br />
pci0 /pci@f0000000<br />
agp /pci@f0000000<br />
pci1 /pci@f2000000<br />
pci2 /pci@f4000000<br />
usb0 /pci@f2000000/@15<br />
usb1 /pci@f2000000/@15,1<br />
usb2 /pci@f2000000/@15,2<br />
hd /pci@f4000000/ata-6@d/disk@0<br />
cd /pci@f4000000/ata-6@d/disk@1<br />
ud /pci@f2000000/usb@15,1/disk@1</nowiki><br />
<br />
=== Other Useful Properties ===<br />
''.properties'' on the root device shows the computer specs:<br />
<nowiki><br />
0 > dev / .properties<br />
model PowerBook5,9<br />
compatible PowerBook5,9<br />
MacRISC3<br />
Power Macintosh<br />
<br />
serial-number SX0</nowiki><br />
<br />
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:<br />
<nowiki><br />
0 > dev enet .properties<br />
vendor-id 0000106b<br />
device-id 0000006b<br />
name ethernet<br />
device_type network<br />
local-mac-address 001124e3 6666</nowiki><br />
<br />
=== Listing Devices ===<br />
The ''ls'' command lists devices found in the current device in the device tree:<br />
<nowiki><br />
0 > dev usb1 ls<br />
ff9e1650 /disk@1<br />
ff9e1a28: /device@2<br />
ff9e1c48: /keyboard@0<br />
ff9e1f88: /mouse@1<br />
ff9e2230: /interface@2</nowiki><br />
<br />
To list a complete list of all devices in the system:<br />
<nowiki><br />
0 > dev / ls</nowiki><br />
<br />
=== Listing Files ===<br />
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.<br />
<br />
Syntax of the ''dir'' command is:<br />
'''dir disk:partition,path'''<br />
<br />
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /<br />
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank<br />
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory<br />
<br />
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:<br />
<nowiki><br />
0 > dir hd:,\</nowiki><br />
<br />
Listing the root directory from the first partition on the (default) HD:<br />
<nowiki><br />
0 > dir hd:1,\</nowiki><br />
<br />
Listing the root directory from a CD:<br />
<nowiki><br />
0 > dir cd:,\</nowiki><br />
<br />
Listing a sub-directory from a CD:<br />
<nowiki><br />
0 > dir cd:,\mac_ppc32</nowiki><br />
<br />
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):<br />
<nowiki><br />
0 > dir usb1/disk@1:,\</nowiki><br />
<br />
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:<br />
<nowiki><br />
0 > dir ud:,\</nowiki><br />
<br />
== Adding Custom Aliases ==<br />
The ''devalias'' command adds temporary user defined aliases.<br />
<br />
<nowiki><br />
0 > devalias dh /pci@f4000000/ata-6@d/disk@0</nowiki><br />
<br />
''nvalias'' stores an alias in NVRAMRC. Variable ''use-nvramrc?'' needs to be set to true in order to execute NVRAMRC script at startup.<br />
<br />
<nowiki><br />
0 > nvalias dh /pci@f4000000/ata-6@d/disk@0</nowiki><br />
<br />
''nvunalias'' deletes an alias.<br />
<br />
<nowiki><br />
0 > nvunalias dh</nowiki><br />
<br />
You can replace existing aliases with your own ones. Removing them will revert to original values.<br />
<br />
=== Creating an Alias for a USB Disk ===<br />
If your firmware version doesn't create the ''ud'' alias by default, you can add the alias by yourself. The only drawback is that you'll have to use the same physical USB port always, or create several aliases for each port.<br />
<br />
1. Check that the alias doesn't exist alredy<br />
<nowiki><br />
0 > devalias</nowiki><br />
<br />
2. List all devices (press the Space Bar to see them all)<br />
<nowiki><br />
0 > dev / ls</nowiki><br />
<br />
3. Look for a USB device that contains your disk (''disk@1'', for instance), and combine list tree entries to a full path. The path can be verified, for example, by listing files on the disk.<br />
<nowiki><br />
0 > dir /pci@f2000000/usb@1b,1/disk@1:,\</nowiki><br />
<br />
4. Create a permanent alias with the ''nvalias'' command (and/or a temporary alias with ''devalias'' instead of ''nvalias'' for testing it before a reboot)<br />
<nowiki><br />
0 > nvalias ud /pci@f2000000/usb@1b,1/disk@1</nowiki><br />
<br />
5. Make sure the ''use-nvramrc?'' env variable is set<br />
<nowiki><br />
0 > setenv use-nvramrc? true</nowiki><br />
<br />
6. Reboot the computer and the ''ud'' alias should be available on the firmware now<br />
<nowiki><br />
0 > reset-all</nowiki><br />
<br />
== Booting MorphOS ==<br />
=== Basics ===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Type in this line (if you have a MorphOS installation on your HD):<br />
<br />
0 > load hd:,\boot.img<br />
<br />
And you'll see output like this:<br />
<nowiki><br />
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950<br />
<br />
Loading ELF<br />
ok<br />
0 > _</nowiki><br />
<br />
"Loading ELF" tells you that the file has been found and loaded.<br />
<br />
The file can be booted with the ''go'' command then:<br />
<nowiki><br />
0 > go<br />
DO-QUIESCE finished_</nowiki><br />
<br />
"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.<br />
<br />
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.<br />
<br />
The previous example can be achieved with this single line:<br />
<nowiki><br />
0 > boot hd:,\boot.img</nowiki><br />
<br />
And the output should then look like this:<br />
<nowiki><br />
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950<br />
<br />
Loading ELF<br />
<br />
DO-QUIESCE finished_</nowiki><br />
<br />
=== Boot Arguments ===<br />
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. Note that Sam460ex/cr and AmigaOne X5000 systems don't use Open Firmware, but the boot arguments can be given on them too by setting an environment variable in their [[Tips_and_Tricks#MorphOS_Boot_Arguments_on_U-boot_Systems | U-boot console]].<br />
<br />
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.<br />
<br />
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.<br />
<br />
* '''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.[[File:MorphOS-BootMenu.png|thumb|MorphOS bootmenu]]<br />
* '''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".<br />
* '''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, the '''F1''' key, or the '''left mouse button''' during the MorphOS boot process (you'll have to try which option works on your hardware). 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.<br />
<br />
=== Examples ===<br />
==== Booting from CD ====<br />
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.<br />
<br />
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.<br />
<br />
To boot any inserted CD that is bootable on Macs:<br />
0 > boot cd:,\\:tbxi<br />
<br />
"\\" 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.<br />
<br />
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.<br />
<br />
List the contents of the CD:<br />
<nowiki><br />
0 > dir cd:,\<br />
<br />
Volume: MorphOSBoot<br />
Size/ GMT File/Dir<br />
bytes date time TYPE CRTR Name<br />
94 07/04/2018 04:54:42 ???? ???? .morphosid<br />
2287135 07/04/2018 04:03:02 boot UNIX boot.img<br />
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img<br />
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img<br />
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img<br />
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img<br />
01/01/1904 00:00:00 *mac_ppc32<br />
01/01/1904 00:00:00 mac_ppc64</nowiki><br />
<br />
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.<br />
<br />
If we wanted to boot the CD on a G5 Mac:<br />
<nowiki><br />
0 > dir cd:,\mac_ppc64<br />
<br />
Size/ GMT File/Dir<br />
bytes date time TYPE CRTR Name<br />
1499688 07/04/2018 04:03:02 boot UNIX boot.img<br />
<br />
ok<br />
0 > boot cd:,\mac_ppc64\boot.img bd cd0</nowiki><br />
<br />
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.<br />
<br />
To boot into the MorphOS boot menu on a G5 Mac:<br />
0 > boot cd:,\mac_ppc64\boot.img bm<br />
<br />
And the same for a G4 Mac:<br />
0 > boot cd:,\mac_ppc32\boot.img bm<br />
<br />
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:<br />
0 > boot cd:,\\boot.img bm<br />
<br />
==== Booting MorphOS ISO from USB ====<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:<br />
0 > boot ud:,\boot.img bi umsd0:morphos.iso<br />
<br />
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:<br />
0 > dir ud:,\<br />
<br />
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.<br />
<br />
<nowiki><br />
0 > dev usb0 ls<br />
ok<br />
0 > dev usb1 ls<br />
ff9e1650: /disk@1<br />
0 > dir usb1/disk@1:,\<br />
Volume: USB<br />
258048000 07-24-2018 18:34:24 morphos.iso<br />
1501436 07-04-2018 04:03:02 boot.img<br />
ok<br />
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso</nowiki><br />
<br />
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:<br />
<nowiki><br />
0 > dev usb1 ls<br />
ff9e1650: /hub@1<br />
ff9e1860: /disk@4<br />
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso</nowiki><br />
<br />
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.<br />
<br />
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.<br />
<nowiki><br />
0 > dir hd:1,\<br />
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device<br />
ok<br />
0 > dir hd:2,\<br />
<br />
Volume: OSX<br />
Size/ GMT File/Dir<br />
bytes date time TYPE CRTR Name<br />
07/22/2017 07:27:40 Applications<br />
09/27/2016 09:59:40 bin<br />
1501436 07-04-2018 04:03:02 ???? UNIX boot.img<br />
ok<br />
0 > boot hd:2,\boot.img bi umsd0:morphos.iso</nowiki></div>
JPV
https://library.morph.zone/index.php?title=Tools/SFSDoctor&diff=4366
Tools/SFSDoctor
2025-07-02T13:59:07Z
<p>JPV: </p>
<hr />
<div>== Description ==<br />
Diagnostic and repair tool for SFS formatted partitions. <br />
<br />
== Usage ==<br />
The '''Check Disk''' option checks for errors, but doesn't modify the filesystem data. The '''Scan Disk''' option can be used to repair filesystems.<br />
<br />
== Notes ==<br />
Read the extensive information about filesystem errors and solutions by selecting the '''Help''' option from the pull-down menus.<br />
<br />
== Screenshot ==<br />
: [[File:SFSDoctor.png]]</div>
JPV
https://library.morph.zone/index.php?title=User:JPV&diff=4359
User:JPV
2025-05-22T08:07:35Z
<p>JPV: </p>
<hr />
<div>A long-term Amiga and MorphOS user, who has difficulties to produce grammatically correct English, but tries to do his best to support the community by writing articles. Feel free to correct anything I've written and please visit my software/MorphOS pages [https://jpv.amigaaa.com/ here] :)</div>
JPV
https://library.morph.zone/index.php?title=Tips_and_Tricks&diff=4358
Tips and Tricks
2025-05-22T07:57:14Z
<p>JPV: </p>
<hr />
<div>''Originally published at: http://jpv.wmhost.com/morphos/tips/''<br />
<br />
Miscellaneous tips and tricks for MorphOS use. Some may even be hackish and not officially encouraged by MorphOS Team. Everyone is welcome to make additions and corrections here.<br />
== Basic Features ==<br />
<br />
=== Modifying the System Directory ===<br />
: Tip #1: NEVER modify anything in the MOSSYS: (SYS:MorphOS/) path! All changes are lost in a system upgrade. If you need to add any 3rd party drivers or libraries, add them to SYS:. If there isn't a correct directory by default, make one.<br />
<br />
: There's only one exception (of course there is one) to this: you can rename MOSSYS:Libs/rexxsyslib.library to MOSSYS:Libs/rexxsyslib.library_disabled when you copy a 68k version of rexxsyslib.library to SYS:Libs/ in order to get the ARexx environment working.<br />
<br />
<br />
=== Keyboard Commands ===<br />
<br />
: At first, check the default ones and define your favourites in '''System Settings -> IControl -> Hotkeys''' and in '''Ambient Settings -> Keyboard'''.<br />
<br />
: For example IControl has "Active Window: Activate Next" and "All Windows: Depth Menu" options, which can be used to achieve alt/ctrl/command-tab style window cycling functionality familiar from other operating systems.<br />
<br />
: Other keys: <br />
:* To zoom Ambient icons in the icon mode: keep CTRL pressed and use the mouse wheel or just roll the wheel over the Viewmode button.<br />
:* To find and select files in Ambient windows by letters: start typing a name when the window is active. Keep the Shift key pressed for directories. <br />
:* To enter a path manually (for example for hidden dirs like .recycled): press the / key in an Ambient window and type in the path. <br />
:* Command-f activates the find function in most programs. <br />
:* The r key rotates the pictures in Ambient's internal viewer and Page Up/Down keys select previous and next images in a dir <br />
:* Check keyboard commands of the Shell, like by default, commands can be completed with CTRL-tab, devices with ALT-tab, history with shift-tab etc. <br />
:* Keeping the Alt key pressed while double clicking a drawer gives you different ways to open drawers.<br />
:* Keeping the Alt key pressed while dragging files on the same partition copies files instead of moving, or vice versa depending on your Ambient settings.<br />
<br />
=== Enabling/Disabling Icon Tooltypes ===<br />
<br />
: Double click single tooltypes to enable and disable them in the icon information window.<br />
<br />
<br />
=== Browsing History in Ambient ===<br />
<br />
: Clicking the parent button ([[File:Tips_Parent.png|middle]]) on an Ambient window (in browser mode) with the right mouse button gives you a browsing history popup menu for quick jumping between locations.<br />
<br />
<br />
=== Sync the Clock from Internet at Boot ===<br />
<br />
: Add this line to S:user-network-startup file:<br />
: <tt>Run DETACH MOSSYS:C/SetClockNTP SAVE</tt><br />
<br />
<br />
=== Redirecting AHI Music Unit ===<br />
<br />
: You can select Unit 0 as the Music Unit in AHI to be able hear audio output from multiple programs at the same time, with a slight decrease in quality.<br />
<br />
: [[File:MorphOS_System_settings_Music_Unit.png|280px]]<br />
<br />
<br />
=== Keeping AHI Audio Quality Better ===<br />
<br />
: Audio quality with AHI will be better if you reduce available channels for its shared modes (Unit 0 usually). Available channels will limit the amount of simultaneus playback of sounds, but you really don't need the default 32 channels and even two channels can be quite enough. Should there be more concurrent sounds, some of them just get muted until the other have been finished.<br />
<br />
: [[File:MorphOS_System_settings_Change_Unit.png|280px]] [[File:MorphOS_System_settings_Unit_0.png|280px]]<br />
<br />
<br />
=== Mime Type Configuration ===<br />
<br />
: Learn to configure mime types from the Ambient settings. It really gives so much for your system and your user experience. [http://jpv.wmhost.com/pics/mimemplayer.png Here] is one example of how to configure MPlayer for all the video files.<br />
<br />
<br />
=== Inline Editing ===<br />
<br />
: Inline editing is a quick way to edit filenames by clicking them with the mouse wheel or with the long left mouse click. Its behaviour can be configured from the Lister settings in Ambient Settings.<br />
<br />
: File comments can also be edited with the inline editing.<br />
<br />
: [[File:Tips_Inlineedit.png|280px]]<br />
<br />
<br />
=== Batch Renaming in Ambient ===<br />
<br />
# Select files you want to be in the range of renaming.<br />
# Hit rename button or command-r keyboard shortcut.<br />
# Use pattern to rename. For example renaming all files which begin with "mod." to files which end with ".mod", use "mod.*" as source and "*.mod" as destination (quotation marks not needed).<br />
<br />
<br />
=== Don't Forget RMB/Long-LMB Gadget Menus ===<br />
<br />
: You get menus from zoom and depth gadgets with right mouse button or by holding left mouse button pressed on them.<br />
<br />
: [[File:Tips_Zoommenu.png]] [[File:Tips_Windowdepthmenu.png]] [[File:Tips_Screendepthmenu.png]]<br />
<br />
<br />
=== How to Use RMB with One-button Mouse ===<br />
<br />
: The right mouse button can be emulated in several different ways:<br />
:* The '''System Settings -> Mouse -> Open menus by clicking...''' setting lets your mouse button act as the right mouse button if you hold a qualifier key pressed while clicking. The qualifier key can be configured for your preferences, but it's the shift key by default.<br />
:* Press right alt and right command keys together. This probably doesn't work on systems with ADB keyboard, like on older Mac laptops. The ADB keyboard doesn't make difference between left and right keys.<br />
:* With non-ADB laptops (PowerBook 5,6-5,9 and 6,7 (iBook)) you can also use two finger tap or two finger hold + button combination on the touchpad for RMB.<br />
:* You can define a hotkey for menu launching on the IControl preferences (the default one is rcommand+space). It doesn't work exactly as the RMB everywhere, but works if you're mostly using the RMB for menus.<br />
:* A multi button USB mouse works always!<br />
<br />
<br />
=== Starting Programs Iconified ===<br />
<br />
: MUI has an option to start programs in iconified mode. It's useful for example for programs like Synergy, which you'd like to start on background without their main window jumping up. The option can be found from program's MUI Settings (Windows -> Iconify on startup).<br />
<br />
: [[File:Tips_Iconify.png]]<br />
<br />
<br />
=== Checking the Debug Log ===<br />
<br />
: If you want a stable system, you need to check the debug log periodically to see if any program misbehaves when used, especially when running new software.<br />
<br />
: An easy way to do it is to enable Debug screenbar module from the screen depth gadget menu. Bug looking Debug button on the screenbar will then give you a debug menu where you can view the log etc. If "Show Log..." option is ghosted, there's nothing in the log and everything is fine, but if it shows hundreds of cryptic lines (it's called a hit), then you have something to worry and the system probably isn't stable anymore. Some programs may output their own harmless debug information to the log too, but it's usually limited to few or tens of lines maximum. You'll recognize a real hit for sure.<br />
<br />
: [[File:Tips_Debug1.png|x64px]] [[File:Tips_Debug2.png|x64px]]<br />
<br />
<br />
=== Printing to a PostScript Compatible Network Printer ===<br />
<br />
: You should mount the NETPAR: device and print to that device from programs like VPDF and OWB, which can output PostScript. NETPAR: is faster than printing through Turboprint (PRT:) and doesn't need Ghostscript installed (PS:).<br />
<br />
: "Mount NETPAR:" can be added to S:user-startup, for example.<br />
<br />
<br />
=== .recycled Directory ===<br />
<br />
: SFS is the default filesystem on MorphOS. It can have a special directory which contains recently deleted files. The directory is named as .recycled and it resides at the root level of every SFS partition (SYS:.recycled for example). Depending the format options it may be disabled, hidden but accessible, or visible.<br />
<br />
: If it's hidden, you can't see it even with "View All Files" option, but you can access it from the shell or Ambient (for example by pressing / key and then writing it to the path string after the volume name).<br />
<br />
: You shouldn't modify any files in it, but you can recover deleted files by copying them to some other path.<br />
<br />
: The PFS3 filesystem has a similar directory, but its name is ".deldir".<br />
<br />
<br />
=== How to Reduce Graphics Memory Usage ===<br />
<br />
: MorphOS can use graphics memory quite extensively which can cause slowdowns or glitches if you run out of it. It usually isn't an issue if you have 64MB or more graphics memory, but lower spec systems with today's resolutions may need some tuning. There are several ways to reduce memory usage and you have to decide or try which is the best for you.<br />
<br />
: MorphOS has an "Enhanced Display" mode, which uses the graphics card's 3D functions to draw graphic layers. It consumes more memory than the traditional 2D mode, but it provides some eyecandy, tearless moving etc.<br />
<br />
: To reduce its memory usage, you may:<br />
:* Change its buffering settings on the DisplayEngine settings in MorphOS Preferences. You need to reboot or switch screens for the new settings to take effect.<br />
:* Disable it completely from the Screens settings in MorphOS Preferences for some or all screens. It may also help if you let it be enabled for Ambient screen, but disable it on other screens you might have.<br />
<br />
: Other ways to reduce graphics memory usage:<br />
:* Lower the color depth of screens from the Screens settings. 16-bit might be enough sometimes.<br />
:* Don't use too many separate screens at the same time.<br />
<br />
<br />
=== How to Open MUI Programs on Their Own Screens ===<br />
<br />
: 1) An easy way is to select "Jump to Screen -> New" from the MUI popup menu gadget in program's window border. It always opens in an enhanced mode and clones the resolution from the Ambient screen. Open and save program's MUI settings to save it permanently.<br />
: [[FIle:MorphOS3_jPV_Newscreen.png|120px]]<br />
<br />
: 2) A more configurable method is to open program's MUI settings, select the Screen tab, and create a totally new screen definition there. You can edit the screen name and the title to suit your use (you can use program's name for those for example), select any resolution and depth, enable or disable the enhanced mode etc. In many cases this is a better method, because you can save graphics memory by not using the enhanced mode for screens which you're going to use for full screen apps only or so.<br />
<br />
: You can switch between the screens with lamiga-m (lcommand-m) keyboard shortcut, or by clicking the screen depth gadget (left click switches to the next screen, right click gives you a menu where you can select any open screen).<br />
: [[File:Tips_Screendepthmenu.png]]<br />
<br />
<br />
== Advanced Features ==<br />
<br />
=== Default Device Icons ===<br />
<br />
: If you want a certain default icon for all the units of a certain device, you can create an icon named def_DEVICENAMExdisk.info to your default icons path (SYS:Prefs/Presets/Deficons/ by default).<br />
<br />
: For example the deficon for SMBFS devices would be called def_SMBFSxdisk.info.<br />
<br />
<br />
=== Default Icon for Ambient Windows ===<br />
<br />
: By default there isn't a default icon file for the icon you see when iconifying an Ambient window (a view). If you want to override the built-in icon, create or copy a new icon file to your default icons path and name it to '''def_view.info'''. <br />
<br />
<br />
=== Old Style Preferences Icons ===<br />
<br />
[[File:Separate_prefs_in_MorphOS.png|thumb|Example of separate system prefs in MorphOS]]<br />
: You can have separate preferences icons in the SYS:Prefs/ directory in the old Amiga style for MorphOS system prefs. Make or copy icons named with a corresponding sub preference name into the SYS:Prefs/ dir and edit their Default Tool to ":MorphOS/Prefs/Preferences".<br />
<br />
: There's already a main preferences icon in SYS:Prefs, so here's an easy example: "copy SYS:Prefs/Preferences.info SYS:Prefs/Network.info", after which double clicking the new Network icon opens the network preferences directly.<br />
<br />
<br />
=== Hilight Options in Listers ===<br />
<br />
: If you want to use "Alternated rows" and "Hilighted sorting column" options in the Lister settings with a grapchics card that doesn't support 3D acceleration.<br />
: Type in shell:<br />
: <tt>Setenv MUI/fastppa SAVE 1</tt><br />
<br />
<br />
=== Copy Selected Filenames ===<br />
<br />
: You can use the internal Ambient command "copyselectiontoclipboard" to copy selected filenames with or without path information to the clipboard. For example, create a new custom hotkey in the Ambient Settings and define "copyselectiontoclipboard VIEWID=%Si FULLPATH" as an internal command for it.<br />
<br />
: User may find it very useful to paste around the names selected in the Ambient windows in many situations.<br />
<br />
<br />
=== Using ARexx Ports from Lua ===<br />
<br />
: MorphOS comes with a native implementation of the Lua scripting language. It can be used for script writing with application interacting instead of the emulated 3rd party ARexx. Lua can use existing ARexx ports with its ipc.module.<br />
<br />
: Load the IPC module first with the '''require 'ipc'''' line (unlike the standard Lua distribution, all modules have to be loaded with the ''require'' function on MorphOS. Check available modules from the ''MOSSYS:Libs/Lua/'' directory.)<br />
<br />
:* ipc.'''address(port)''' - sets the default ARexx port. Port "COMMAND" executes commands as DOS shell commands. <br />
:* '''ipc.checkport(port)''' - checks if an ARexx port is available. <br />
:* ipc.'''rx(command)''' - sends a command to a port set with ipc.address. It returns ARexx RESULT. <br />
:* '''ipc.waitforport(name[, interval])''' - Waits for an ARexx port. Script is aborted if the port isn't found.<br />
<br />
: More about the topic [[Getting_Started_with_Lua|here]].<br />
<br />
<br />
=== Copying a Whole Disk As an Image File ===<br />
<br />
: You can access raw data of drives by MorphOS's RAWDISK: device. Partitions or whole disk can be copied in or out with it, but be careful to write to the correct destination! For copying you need to use SDK's cp command or standard Copy command with the DIRECT option.<br />
<br />
: You can browse available disks and devices by opening RAWDISK: device from the shell (just type RAWDISK: on the shell) or from Ambient (hit the / key, clear existing text, and write RAWDISK: to the string line). Browse to the Devices directory and then to the wanted device and unit to see the actual disk image file (rawdisk) and partition files in a separate partition table directory. Partition files let you recognize more easily that you're accessing the wanted disk. They also have information like device and filesystem names told in file comments (use the List command or Ambient to see them).<br />
<br />
: As an example, to make a backup of a whole SD card which is placed in a USB reader (the card is found in usbscsi.device unit 3):<br />
: <tt>Copy DIRECT RAWDISK:Devices/usbscsi.device/3/rawdisk work:sdcard.img</tt><br />
<br />
: And to copy the image back to the SD card (removes all existing data, be careful!):<br />
: <tt>Copy DIRECT work:sdcard.img RAWDISK:Devices/usbscsi.device/3/rawdisk</tt><br />
<br />
: This works with all raw disk image files like Raspberry Pi's OS distributions etc.<br />
<br />
: Single partitions can also be copied from the RAWDISK:Disks directory.<br />
<br />
: If you want to access the data in saved image files without needing to write them back to any device, you can mount them with help of [[Tools/FileImageCtrl]] and [[Tools/Mounter]] programs. You can either mount partitions directly with the [[Tools/FileImageCtrl|FileImageCtrl]] tool or insert disk images on it and mount the wanted partitions with the [[Tools/Mounter|Mounter]] tool.<br />
<br />
<br />
=== Using WLAN with Hidden SSID ===<br />
<br />
: If you have to use wireless network with hidden SSID, you can add "scan_ssid=1" line in your ENVARC:sys/Wireless.prefs file's network block.<br />
<br />
: Contents should look something like this:<br />
<br />
: <tt>network={<br />
: &nbsp;&nbsp;ssid="ThatHiddenSSID"<br />
: &nbsp;&nbsp;scan_ssid=1<br />
: &nbsp;&nbsp;psk="password"<br />
: }</tt><br />
<br />
: Note: It's not recommended to hide the SSID, because it doesn't add security in practise. Use this only if you can't control the network you're connecting.<br />
<br />
<br />
=== Modifying Screen and Keyboard Brightness on a Laptop without Using KB Shortcuts ===<br />
<br />
: Brightness values can be modified by editing the ENVARC:sys/laptopquick.conf file with a text editor. The values are taken in use after a reboot.<br />
<br />
<br />
=== Opening Ambient Windows from the Shell or Scripts ===<br />
<br />
: Directories can be opened with the [[Shell_Commands/Open|Open]] command, but it only opens them in the default view mode:<br />
: <tt>Open SYS:Applications</tt><br />
<br />
: If you need to open windows with certain location, size, position, and mode, you can use the LoadURI ARexx command. LoadURI accepts the following parameters:<br />
:* URI which contains a path and attributes with values. The attributes are given after a question mark and they are separated with the & delimiter. Possible attributes are ''view'' (icon or list), ''mode'' (all, icons, or thumbs), ''top'' (pixels from the top border), ''left'' (pixels from the left border), ''width'', and ''height''.<br />
:* NEW=NEWWIN/S: opens a new window even if similar window would already be opened<br />
:* RELOAD/S: reloads the URI<br />
:* FORCE/S: forces full reloading<br />
:* BROWSER/N: forces the browser mode on (1) or off (0)<br />
:* VIEWID/N: specifies view/window ID<br />
<br />
: Use the ''AMBIENT'' port in ARexx scripts.<br />
<br />
: To open the SYS:Libs directory in the list mode showing all files in a 440x600 window at position x=350, y=50, no matter if it has been opened previously:<br />
: <tt>'LoadURI "file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600" NEW'</tt><br />
<br />
: To open a directory in the icon mode showing thumbnails in a 500x400 window at position x=350, y=50, the window is also opened in the spatial (non browser) mode:<br />
: <tt>'LoadURI "file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400" BROWSER=0'</tt><br />
<br />
: If you don't want to write full ARexx scripts but would like to run them just as single shell commands, you can use the [[Shell_Commands/RXCmd|RXCmd]] shell command (notice that you have to escape the inner quotation marks with the asterisks):<br />
: <tt>RXCmd AMBIENT "LoadURI *"file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600*" NEW"<br />
: RXCmd AMBIENT "LoadURI *"file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400*" BROWSER=0"</tt><br />
<br />
<br />
== Bundled Software ==<br />
<br />
=== Flacapella Settings for MP3 Encoding ===<br />
<br />
: Example of a custom encoder setting in Flacapella:<br />
<br />
: <tt>Compress Command: c:lame -V0 --tt "{title}" --ta "{artist}" --tl "{album}" --tn {track} {?coverfile:--ti "{coverfile}"} {input} {output}<br />
: File Extension: mp3</tt><br />
<br />
: This will encode tracks to mp3 files with title, artist, album and track number tags. It also embeds fetched cover image in files, if image was found. <br />
: Example assumes you have [https://www.morphos-storage.net/?find=lame LAME] installed in C:<br />
<br />
<br />
=== Jukebox Tips ===<br />
<br />
:* If you select any song in playlist by clicking it just once, it's played next no matter if you have random or sequential mode in use. <br />
:* You can adjust volume in Jukebox by using mouse wheel over its screenbar module. <br />
:* Displayed columns can be configured on the fly by right clicking the column title.<br />
:* Jukebox can be better integrated into Ambient and its contextual menus with the [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script.<br />
:* Two new tooltypes were presented in MorphOS 3.8: <br />
:** '''FRAMESCAN=NO''' disables the Reggae framescanning for tracks that have unknown duration. It speeds up the loading of such tracks, but you'll lose the seeking ability with them. <br />
:** '''STREAMBUFFER=YES''' activates the Reggae streambuffer class which reduces stuttering, but causes lag on track change and seeking.<br />
<br />
<br />
=== How to Reduce OWB's HD Writes ===<br />
<br />
: OWB writes a lot of data to the hard drive by default. You might want to reduce it if you're paranoid about SFS fragmentation, filesystem corruption, privacy, or you'd like to avoid certain databases getting too big (which can cause slowdowns). Or you just want your .recycled dir to have other than the OWB files. One option is to use the Private Browsing mode always, but here are tips if you don't want to activate that always or you want to restrict certain writes only.<br />
<br />
:* Disable the TopSites feature. This makes a write for every page you visit, it's an awful amount. Its database (conf/TopSites.db) can also grow to hundreds of megabytes, which causes very noticeable slowdowns to browsing. You can disable it with the "Setenv SAVE OWB_DISABLE_TOPSITES 1" command in the shell, and if the database file has already grown too big, you can remove it.<br />
:* Disable the Website Icons feature. Open the Interface settings and uncheck all Website Icons checkmarks. <br />
:* Disable all saving options from the Privacy settings.<br />
<br />
: If you still need some option enabled, because some site requires it, you can soft link its configuration file to Ram Disk. I, for example, still have Local Storage enabled, but I have linked its dir to ENV: (which resides in Ram Disk). To do that, make LocalStorage directories to both ENV: and ENVARC: (that ensures that it's created after a reboot too), open the shell and cd into your OWB/Conf/ dir, rename or delete the old LocalStorage dir, type "makelink LocalStorage ENV:LocalStorage". Using ENV: gives the advantage to have some files saved so that those settings are restored in every boot. If you're happy with a certain setting, copy the corresponding file to ENVARC: and it will be preserved without being messed up with the later usage. If you just want to have the configuration files enabled, but cleared on every boot, you could soft link them to T: for example.<br />
<br />
<br />
=== Alternative YouTube Script for OWB ===<br />
<br />
: [http://www.morphzone.info/modules/newbb_plus/viewtopic.php?forum=9&topic_id=9799&post_id=109979&viewmode=flat&sortorder=0&showonepost=1 YouTube Center] is a feature rich configureable userscript for improving YouTube experience. It's made for mainstream browsers, but it also works on OWB! All videos can be forced to HTML5 to get them work in OWB. It's heavier than Fab's official OWB script, but works fine as an option or as a backup plan :). Script saves its settings to LocalStorage to #?www.youtube.com#? files.<br />
<br />
: Note: YouTube defaults to the HTML5 player nowadays and you might be fine without any Flash->HTML5 converter scripts. It's probably better to install this script only if you want some other features from it.<br />
<br />
<br />
=== Watching Videos with Less CPU Load in OWB ===<br />
<br />
: When watching a video in OWB, the fullscreen mode makes a lot less CPU load than the default embedded mode, because the fast overlay mode is used then. CPU load may drop from 100% to 40% for example. Wait until the video really starts playing before clicking the fullscreen button on it, or it may fail and you have to reload the video to be able to try it again. Some videos may have a fullscreen option in their contextual menu too. Remember to have Fullscreen Fix scripts added and enabled from the Scripts window ("Windows->Scripts..." pulldown menu entry) for YouTube, Dailymotion, and Vimeo.<br />
<br />
: Note: check that you really have the latest YouTube fullscreen fix script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js in your OWB/Scripts/ directory. Grunch doesn't get updated for the latest version always for example.<br />
<br />
<br />
=== Problems with YouTube Videos ===<br />
<br />
:* Now that YouTube defaults to HTML5, our days of ad-free videos have ended. It also means that the Content Blocking (AdBlock) option in the OWB's settings can block some videos. If you have some videos which won't start playing, try to disable the Content Blocking option and try again. If that was the problem, but you want to keep the content blocking enabled, add an allow rule to the Content Blocking settings. Open "Windows->Content Blocking..." from the OWB's pulldown menus, click the Add button, and write "youtube.com" to the Rule line. Close the window and try the video again.<br />[[File:OWB_ContentBlockingYT.png]]<br />
<br />
:* If all videos refuse to play, check if you have any YouTube converter scripts enabled in the "Windows->Scripts..." settings. The Fullscreen Fix script is the only one needed and you should disable all converter scripts.<br />
<br />
:* Flash plugins can also break compatibility with YouTube, so if you have the swfdec_plugin.library file in your OWB/Plugins/ directory, you have the following options to choose from:<br />
:** Remove the file from use if you don't need flash anywhere. The plugin doesn't work too well generally anyway.<br />
:** Keep the file, but disable it for all pages by unchecking the "Settings->Preferencfes->Content->Allow plugins" option. You can then enable it temporarily from "Settings->Plugins->Enable" if needed.<br />
:** Disable it temporarily from "Settings->Plugins->Disable", and reload the page.<br />
:** Disable it just for YouTube by adding a new URL setting from "Windows->URL Settings...". Click the Add button, edit the URL line to for example "youtube.com", and uncheck the Plugins option.<br />
<br />
<br />
=== OWB Doesn't Work or Stopped Working with Certain Web Pages ===<br />
<br />
:* Sometimes it helps to change the "Spoof as" setting in OWB. Web pages may offer different kind of content depending on what browser they think you are using. Some popular CAPTCHAs don't work with the default spoofing, but do work when spoofed as iPad for instance. iPad is generally a good option to start trying the spoofing, because you probably get the page in its simpliest form then.<br />
<br />
:* There are some bugs in the JavaScript engine in the latest available OWB version (1.24 at the time of writing) and that causes problems with some web pages, but there's a chance that these pages would still work with an earlier OWB version. You can download earlier OWB versions from [http://fabportnawak.free.fr/owb/ Fab's homepage] and install them, for example, to a different directory than your current OWB installation. There's no problem having two or even several OWB installations on your system, you can just launch whichever you want. As an example, Google Maps stopped working with OWB 1.24 in autumn 2017, but it still continued to work with [http://fabportnawak.free.fr/owb/owb-morphos-1.23.lha OWB 1.23].<br />
<br />
<br />
=== Creating an ISO Image ===<br />
<br />
: Jalapeno can also create and save ISO images which will preserve MorphOS/AmigaOS file attributes and comments. Images can be used for backups or even be booted from USB devices.<br />
<br />
: An option to create an ISO image is found on the pulldown menu in the Burn Files section.<br />
<br />
: [[File:Tips_Create_ISO.png|200px]]<br />
<br />
: If the resulting image file will be bigger than 1GB, Jalapeno splits it into 1GB parts. Those parts can be joined into one big image file with the Join command in the shell, but remember the filesize limits of your target [https://library.morph.zone/Filesystems filesystem] when doing that.<br />
<br />
<br />
=== Copying a CD/DVD to an ISO Image ===<br />
<br />
: If you want to make a standard, easily mountable, ISO image out of an existing CD or DVD, a good way to achieve it is to use the ReadCD program provided with the Jalapeno program on the standard MorphOS installation. Jalapeno itself can also create image files of optical media by selecting "Save as..." from the "Copy Tracks" pull-down menu, but resulting images aren't mountable by the system, because Jalapeno uses options that include more data into the images, for error checking etc.<br />
<br />
: Do these steps from the shell to read a CD/DVD into a standard ISO image:<br />
:# Find your CD drive device by typing: MOSSYS:Data/Jalapeno/readcd -scanbus<br />
:# Create an ISO image by typing (replace "1,1,0" to what you saw in the previous step, and the image path to what you want): MOSSYS:Data/Jalapeno/readcd -dev 1,1,0 f=ram:image.iso<br />
<br />
=== Disabling the Default UTF-8 Mode with Scribble ===<br />
<br />
: Scribble uses UTF-8 encoding by default, but you might prefer to default to the traditional ASCII format instead. The UTF-8 mode can be disabled from the pulldown menu in Scribble, but the setting isn't saved if you save the program settings.<br />
: [[File:Scribble_ascii1.png|128px]]<br />
<br />
: If you want to disable it by default, you have to open the "Save As..." requester, enable the "Make Default" option (also check that Encoding is set to ASCII), and save a file (can be any file anywhere).<br />
: [[File:Scribble_ascii2.png|205px]]<br />
<br />
<br />
== 3rd Party Software ==<br />
<br />
=== Where to Get Software? ===<br />
:* Check [http://library.morph.zone/Links#File_Repositories file repositories] for manual installing<br />
:* [http://www.geit.de/eng_grunch.html Grunch] is a good packet manager for automatic installation and updating of selected software<br />
:* [http://www.meta-morphos.org/WArMUp/chrysalis_en.pdf Chrysalis] is a preconfigured environment and software distribution package ([http://www.warmup-asso.org/download/pack/chrysalis.iso Download ISO image])<br />
<br />
<br />
=== Custom Ambient Menus with AREXX ===<br />
<br />
: You can add own menu items to Ambient pulldown menus with AREXX. Read SYS:MorphOS/Ambient/docs/arexx.txt for more info about AREXX usage or download the [http://morphos-files.net/remote/CRABUM CRABUM] program, which helps you to create correct AREXX lines ([http://library.morph.zone/Getting_Started#Creating_Menus_with_CRABUM tutorial]).<br />
<br />
<br />
=== Help with Shell Commands ===<br />
<br />
: MorphOS Library contains descriptions of all [http://library.morph.zone/Shell_Commands shell commands] and the descriptions can be displayed on the shell with the [http://aminet.net/package/util/batch/Chelp Chelp] script. The script can be used to replace older [http://aminet.net/package/util/cli/Help Help] program (which would otherwise be nice still, but it only contains help for MorphOS 1.x commands).<br />
<br />
<br />
=== Utilizing Your Keyboard's Multimedia Keys ===<br />
<br />
:* The [http://www.geit.de/eng_mmkeyboard.html MMKeyboard] software can be used to assign different kinds of functions to extra keys found on some keyboards.<br />
:* The [http://aminet.net/package/mus/play/MultiMeedio MultiMeedio] script provides a unified control for all popular media players.<br />
<br />
<br />
== Hardware Related ==<br />
<br />
=== Removing Startup Sound on Macs ===<br />
<br />
: The annoying startup sound can be removed from the '''Sound preferences''' on MorphOS nowadays. Set the '''Boot Chime Volume''' to zero to mute it.<br />
<br />
: Other (now obsolete) methods to mute it:<br />
:* If you plan to use Mac as MorphOS only system, but you still have OSX installed, you can mute the audio from OSX before wiping it out by installing MorphOS. Startup sound doesn't come back if you won't boot into OSX anymore.<br />
:* If you don't have OSX anymore, you could try to remove sound with some Linux distribution's live/installation CD. More info [http://www.meta-morphos.org/faq.php?id_cat=2&myfaq=yes&categories=Installation+et+d%E9marrage#74 here] and [https://morphosuser.wordpress.com/2014/12/28/removing-the-boot-sound/ here].<br />
:* If you use OSX and MorphOS as a dualboot system you can install [http://www5e.biglobe.ne.jp/~arcana/StartupSound/index.en.html StartupSound.prefPane] for OSX.<br />
<br />
<br />
=== Speeding Up the Startup Manager on Macs ===<br />
<br />
: Startup Manager (the boot menu you get by booting with option/alt key pressed) can be slow when it tries to find network boot devices. To speed it up go to the OF prompt and type "'''setenv skip-netboot? true'''". Funnily enough, it only affects if you have network cable plugged in.<br />
<br />
<br />
=== Booting MorphOS ISO from USB Stick ===<br />
<br />
: MorphOS Team has released an [http://www.morphos-team.net/guide/usb-boot official guide] for USB booting, but I've also noticed that at least some Macs (Mac mini and Powerbook for example) have certain ud alias for USB drive. You can use that as a shortcut and get the booting done with less work (no need to search the correct path, works even when USB stick is in a hub, less typing and less to remember).<br />
<br />
: If you have only one mass storage device connected, you can just boot into Open Firmware prompt (command-alt-o-f) and type:<br />
<br />
: <tt>boot ud:,\boot.img bi umsd0:morphos.iso</tt><br />
<br />
: (Remember to have both boot.img and morphos.iso on the stick)<br />
<br />
<br />
=== Keyboard Reboot on ADB Laptops ===<br />
<br />
: The traditional Ctrl-Command-Command (Ctrl-Amiga-Amiga) keyboard combination doesn't work on laptops using the ADB interface for the keyboard, because ADB doesn't make difference between the left and right command keys. You can reboot them with an alternative Fn-Alt-Alt keyboard combination.<br />
<br />
<br />
=== Blackouts or Graphical Flickering on Mac mini ===<br />
<br />
: Mac minis suffer from short blackouts with some monitors when the connection is made with a DVI cable. The screen gets usually blanked for few seconds, and depending of the monitor it may happen more or less frequently. Issue may also show up as flickering lines on the screen and it may get worse and worse until the monitor is unable to sync to the signal anymore.<br />
<br />
: One option to get around it is to use a VGA adapter/cable, because it doesn't seem to happen with it.<br />
<br />
: An another option is to try to lower the pixel clock value for the used screenmode from the Monitors settings in the MorphOS preferences. If your default mode has for example vertical frequency of 75 Hz, going to 60 Hz mode may help. Sometimes even a small change can help, and lowering just couple clicks from 60 Hz does the trick.<br />
<br />
: This seems to be a common problem with Mac minis and "non-coherent" displays as discussed for example [https://discussions.apple.com/thread/2723110 here].<br />
<br />
<br />
=== Disabling the Internal Touchpad on Laptops ===<br />
==== From the Touchpad Settings (Preferred)====<br />
: An internal touchpad can be disabled from the MorphOS system settings nowadays, and this is the preferred method. Open '''System Settings -> Touchpad''' and disable the '''Enable the Touchpad driver''' setting.<br />
<br />
: [[File:MorphOS_Preferences_disabling_touchpad.png|200px]]<br />
<br />
==== From the USB Settings ====<br />
: The touchpad can be disabled temporarily by removing its binding in the USB settings. This setting is reverted back next time the machine is booted or if USB class scanning is done otherwise.<br />
<br />
: To remove the binding, open the USB settings from the MorphOS Preferences application and go to the Devices list.<br />
:* If you have "Apple Internal Trackpad" alone in the list, you can just select it and click the Unbind button.<br />
:: [[File:Disabling touchpad ibook.png|200px]]<br />
:* If your machine has a combined internal keyboard and trackpad device, double click it ("Apple Internal Keyboard / Trackpad"). Select Touchpad from the newly opened window and then click the Release Binding button.<br />
:: [[File:Disabling touchpad powerbook.png|200px]]<br />
<br />
==== Removing the Driver at Boot Time ====<br />
: Touchpad can also be disabled permanently by removing touchpad.library from use. Removing it is a bit tricky, because it resides in "ROM" and not as a file in system directories, but it can be done with the mf (module filter) boot command argument.<br />
<br />
: The boot command arguments can be edited by editing the bootinfo.txt file on Macs. The bootinfo.txt file is found on the Boot: partition, which also contains the boot.img file. If you don't see the partition, you probably need to mount it first by using, for example, the [[Tools/Mounter | Mounter]] tool. '''Note that if you edit the bootinfo.txt file, you must bless the file with the [[Shell_Commands/HFSSetMacBoot | HFSSetMacBoot]] command or the system won't be bootable anymore!'''<br />
<br />
: To add the mf argument, open the bootinfo.txt file with a text editor, find the line between <BOOT-SCRIPT> and </BOOT-SCRIPT> lines (it starts with "boot"), and add ''mf=touchpad.library'' at the end of the boot line. Save the file and '''remember to bless it with the ''HFSSetMacBoot Boot:bootinfo.txt'' command from the shell or your system won't boot again!'''<br />
<br />
<br />
=== MorphOS Boot Arguments on U-boot Systems ===<br />
: To boot into MorphOS, hardware has to load a MorphOS boot image file that contains the kernel and core drivers. The boot image file also accepts arguments to control the boot procedure before the actual operating system is loaded from the system partition. The boot arguments usage on [[Open Firmware]] systems is well [[Open_Firmware#Boot_Arguments | documented]], but they must be given in a different way on [http://www.intuitionbase.com/static.php?section=uboot U-boot] systems (Sam460ex/cr, AmigaOne X5000).<br />
<br />
: On the U-boot systems the boot arguments have to be set in the '''morphosargs''' environment variable in the U-boot console.<br />
<br />
: To check if you already have the variable set:<br />
: <tt>printenv morphosargs</tt><br />
<br />
: To set an argument (in this example we'd disable an unsupported SCSI controller by removing the SCSI driver from the boot image by using the ''module filter (mf)'' boot argument):<br />
: <tt>setenv morphosargs mf=symbios.device</tt><br />
: <tt>saveenv</tt><br />
<br />
: To edit an existing variable:<br />
: <tt>editenv morphosargs</tt><br />
: <tt>saveenv</tt><br />
<br />
<br />
=== FireWire Debugging ===<br />
<br />
: It's possible to transfer MorphOS debug logs to another computer via a FireWire connection. Please read [https://morph.zone/modules/newbb_plus/viewtopic.php?forum=11&topic_id=12759&post_id=143825&viewmode=flat&sortorder=0&showonepost=1 this post at MorphZone] for more information.</div>
JPV
https://library.morph.zone/index.php?title=Open_Firmware&diff=4357
Open Firmware
2025-05-22T07:49:39Z
<p>JPV: </p>
<hr />
<div>== Preface ==<br />
'''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.<br />
<br />
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.<br />
<br />
Output texts in these examples have been truncated in most cases to show only the information of interest.<br />
<br />
== Accessing the User Interface ==<br />
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.<br />
<br />
<nowiki><br />
Apple PowerBook5,9 4.9.6f0 BootROM built on 10/05/05 at 16:45:50<br />
Copyright 1994-2005 Apple Computer, Inc.<br />
All Rights Reserved.<br />
<br />
Welcome to Open Firmware, the system time and date is: 07/24/2018 21:07:11<br />
<br />
To continue booting, type "mac-boot" and press return.<br />
To shut down, type "shut-down" and press return.<br />
<br />
Release keys to continue!<br />
<br />
ok<br />
0 > _</nowiki><br />
<br />
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.<br />
<br />
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].<br />
<br />
== Useful Commands ==<br />
* '''mac-boot''' - Continues booting from the current OF state<br />
* '''reset-all''' - Resets the machine to the power-on state and reboots<br />
* '''shut-down''' - Shuts down the machine<br />
* '''load <file> <args>''' - Loads an OF code file (e.g. ELF binary image like MorphOS boot.img or Forth script) into memory<br />
* '''go''' - Runs/boots the loaded file<br />
* '''boot <file> <args>''' - Loads an OF code file and boots it<br />
* '''printenv''' - Prints environment variable values<br />
* '''setenv''' - Sets environment variable values<br />
* '''devalias''' - Displays a list of ''aliases'' for devices (similar to ''assigns'' on MorphOS)<br />
* '''.properties''' - Displays a list of properties for the selected device<br />
* '''ls''' - Displays contents of the current path in the device tree<br />
* '''pwd''' - Displays the current path within the device tree<br />
* '''dev''' - Selects a device (using either the alias or absolute/relative device tree path)<br />
* '''dir''' - Lists files on a partition<br />
<br />
== Environment Variables ==<br />
Use the ''printenv'' command to list all environment variable values.<br />
<br />
<nowiki><br />
0 > printenv<br />
-------------- Partition: common -------- Signature: 0x70 ---------------<br />
little-endian? false false<br />
real-mode? false false<br />
auto-boot? true true<br />
skip-netboot? false false<br />
use-nvramrc? false false</nowiki><br />
<br />
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.<br />
<br />
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.<br />
<br />
<nowiki><br />
0 > setenv skip-netboot? true<br />
0 > printenv skip-netboot?<br />
-------------- Partition: common -------- Signature: 0x70 ---------------<br />
skip-netboot? true false</nowiki><br />
<br />
== Examining Devices ==<br />
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.<br />
<br />
=== Listing Aliases ===<br />
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.<br />
<br />
The device can be selected with the ''dev'' command and then the aliases can be listed with the ''.properties'' command:<br />
<nowiki><br />
0 > dev /aliases<br />
0 > .properties<br />
name aliases <br />
pci0 /pci@f0000000<br />
agp /pci@f0000000<br />
pci1 /pci@f2000000<br />
pci2 /pci@f4000000<br />
usb0 /pci@f2000000/@15<br />
usb1 /pci@f2000000/@15,1<br />
usb2 /pci@f2000000/@15,2<br />
hd /pci@f4000000/ata-6@d/disk@0<br />
cd /pci@f4000000/ata-6@d/disk@1<br />
ud /pci@f2000000/usb@15,1/disk@1</nowiki><br />
<br />
The commands can also be input combined, on a single line:<br />
<nowiki><br />
0 > dev /aliases .properties<br />
name aliases <br />
pci0 /pci@f0000000<br />
agp /pci@f0000000<br />
pci1 /pci@f2000000<br />
pci2 /pci@f4000000<br />
usb0 /pci@f2000000/@15<br />
usb1 /pci@f2000000/@15,1<br />
usb2 /pci@f2000000/@15,2<br />
hd /pci@f4000000/ata-6@d/disk@0<br />
cd /pci@f4000000/ata-6@d/disk@1<br />
ud /pci@f2000000/usb@15,1/disk@1</nowiki><br />
<br />
There's also a shorter ''devalias'' command available on most firmware versions, and it does the same as the previous example:<br />
<nowiki><br />
0 > devalias<br />
name aliases <br />
pci0 /pci@f0000000<br />
agp /pci@f0000000<br />
pci1 /pci@f2000000<br />
pci2 /pci@f4000000<br />
usb0 /pci@f2000000/@15<br />
usb1 /pci@f2000000/@15,1<br />
usb2 /pci@f2000000/@15,2<br />
hd /pci@f4000000/ata-6@d/disk@0<br />
cd /pci@f4000000/ata-6@d/disk@1<br />
ud /pci@f2000000/usb@15,1/disk@1</nowiki><br />
<br />
=== Other Useful Properties ===<br />
''.properties'' on the root device shows the computer specs:<br />
<nowiki><br />
0 > dev / .properties<br />
model PowerBook5,9<br />
compatible PowerBook5,9<br />
MacRISC3<br />
Power Macintosh<br />
<br />
serial-number SX0</nowiki><br />
<br />
The ''enet'' device shows the MAC address of the computer. ''00:11:24:e3:66:66'' in this case:<br />
<nowiki><br />
0 > dev enet .properties<br />
vendor-id 0000106b<br />
device-id 0000006b<br />
name ethernet<br />
device_type network<br />
local-mac-address 001124e3 6666</nowiki><br />
<br />
=== Listing Devices ===<br />
The ''ls'' command lists devices found in the current device in the device tree:<br />
<nowiki><br />
0 > dev usb1 ls<br />
ff9e1650 /disk@1<br />
ff9e1a28: /device@2<br />
ff9e1c48: /keyboard@0<br />
ff9e1f88: /mouse@1<br />
ff9e2230: /interface@2</nowiki><br />
<br />
=== Listing Files ===<br />
If a device (disk) contains a supported filesystem ('''HFS(+), FAT, ISO9660'''), its contents can be listed with the ''dir'' command.<br />
<br />
Syntax of the ''dir'' command is:<br />
'''dir disk:partition,path'''<br />
<br />
* ''disk'' is a device path to a disk, aliases can be used here and the delimiter in the device tree is /<br />
* ''partition'' is a partition number (starting from 1), the default partition is used if left blank<br />
* ''path'' is a path in the filesystem, the directory delimiter is \ and the same character is also used to access the root directory<br />
<br />
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:<br />
<nowiki><br />
0 > dir hd:,\</nowiki><br />
<br />
Listing the root directory from the first partition on the (default) HD:<br />
<nowiki><br />
0 > dir hd:1,\</nowiki><br />
<br />
Listing the root directory from a CD:<br />
<nowiki><br />
0 > dir cd:,\</nowiki><br />
<br />
Listing a sub-directory from a CD:<br />
<nowiki><br />
0 > dir cd:,\mac_ppc32</nowiki><br />
<br />
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):<br />
<nowiki><br />
0 > dir usb1/disk@1:,\</nowiki><br />
<br />
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:<br />
<nowiki><br />
0 > dir ud:,\</nowiki><br />
<br />
== Adding Custom Devaliases ==<br />
The ''devalias'' command adds temporary user defined devaliases.<br />
<br />
<nowiki><br />
0 > devalias dh /pci@f4000000/ata-6@d/disk@0</nowiki><br />
<br />
''nvvalias'' stores a devalias in NVRAMRC. Variable ''use-nvramrc?'' needs to be set to true in order to execute NVRAMRC script at startup.<br />
<br />
<nowiki><br />
0 > nvalias dh /pci@f4000000/ata-6@d/disk@0</nowiki><br />
<br />
''nvunalias'' deletes an alias.<br />
<br />
<nowiki><br />
0 > nvunalias dh</nowiki><br />
<br />
You can replace existing devaliases with your own ones. Removing them will revert to original values.<br />
<br />
== Booting MorphOS ==<br />
=== Basics ===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Type in this line (if you have a MorphOS installation on your HD):<br />
<br />
0 > load hd:,\boot.img<br />
<br />
And you'll see output like this:<br />
<nowiki><br />
0 > load hd:,\boot.img load-size=16e8fc adler32=bd628950<br />
<br />
Loading ELF<br />
ok<br />
0 > _</nowiki><br />
<br />
"Loading ELF" tells you that the file has been found and loaded.<br />
<br />
The file can be booted with the ''go'' command then:<br />
<nowiki><br />
0 > go<br />
DO-QUIESCE finished_</nowiki><br />
<br />
"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.<br />
<br />
A shorter, and usual, way to boot is to use the ''boot'' command, which combines both ''load'' and ''go'' commands.<br />
<br />
The previous example can be achieved with this single line:<br />
<nowiki><br />
0 > boot hd:,\boot.img</nowiki><br />
<br />
And the output should then look like this:<br />
<nowiki><br />
0 > boot hd:,\boot.img load-size=16e8fc adler32=bd628950<br />
<br />
Loading ELF<br />
<br />
DO-QUIESCE finished_</nowiki><br />
<br />
=== Boot Arguments ===<br />
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. Note that Sam460ex/cr and AmigaOne X5000 systems don't use Open Firmware, but the boot arguments can be given on them too by setting an environment variable in their [[Tips_and_Tricks#MorphOS_Boot_Arguments_on_U-boot_Systems | U-boot console]].<br />
<br />
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.<br />
<br />
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.<br />
<br />
* '''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.[[File:MorphOS-BootMenu.png|thumb|MorphOS bootmenu]]<br />
* '''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".<br />
* '''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, the '''F1''' key, or the '''left mouse button''' during the MorphOS boot process (you'll have to try which option works on your hardware). 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.<br />
<br />
=== Examples ===<br />
==== Booting from CD ====<br />
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.<br />
<br />
As well as the previously mentioned methods, there are other ways to boot a CD from the Open Firmware prompt.<br />
<br />
To boot any inserted CD that is bootable on Macs:<br />
0 > boot cd:,\\:tbxi<br />
<br />
"\\" 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.<br />
<br />
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.<br />
<br />
List the contents of the CD:<br />
<nowiki><br />
0 > dir cd:,\<br />
<br />
Volume: MorphOSBoot<br />
Size/ GMT File/Dir<br />
bytes date time TYPE CRTR Name<br />
94 07/04/2018 04:54:42 ???? ???? .morphosid<br />
2287135 07/04/2018 04:03:02 boot UNIX boot.img<br />
1454648 07/04/2018 04:03:02 boot UNIX bootcyrusplus.img<br />
2201986 07/04/2018 04:03:02 boot UNIX bootefika.img<br />
2286039 07/04/2018 04:03:02 boot UNIX bootpeg1.img<br />
1416944 07/04/2018 04:03:02 boot UNIX bootsam_ppc4x0.img<br />
01/01/1904 00:00:00 *mac_ppc32<br />
01/01/1904 00:00:00 mac_ppc64</nowiki><br />
<br />
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.<br />
<br />
If we wanted to boot the CD on a G5 Mac:<br />
<nowiki><br />
0 > dir cd:,\mac_ppc64<br />
<br />
Size/ GMT File/Dir<br />
bytes date time TYPE CRTR Name<br />
1499688 07/04/2018 04:03:02 boot UNIX boot.img<br />
<br />
ok<br />
0 > boot cd:,\mac_ppc64\boot.img bd cd0</nowiki><br />
<br />
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.<br />
<br />
To boot into the MorphOS boot menu on a G5 Mac:<br />
0 > boot cd:,\mac_ppc64\boot.img bm<br />
<br />
And the same for a G4 Mac:<br />
0 > boot cd:,\mac_ppc32\boot.img bm<br />
<br />
On a G4 Mac you could also use the ''blessed'' directory as a shortcut:<br />
0 > boot cd:,\\boot.img bm<br />
<br />
==== Booting MorphOS ISO from USB ====<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you have recent enough Open Firmware, booting the ISO file from a USB stick is easy:<br />
0 > boot ud:,\boot.img bi umsd0:morphos.iso<br />
<br />
If that doesn't work, try to list the contents of the USB stick to find out if it's in a compatible format:<br />
0 > dir ud:,\<br />
<br />
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.<br />
<br />
<nowiki><br />
0 > dev usb0 ls<br />
ok<br />
0 > dev usb1 ls<br />
ff9e1650: /disk@1<br />
0 > dir usb1/disk@1:,\<br />
Volume: USB<br />
258048000 07-24-2018 18:34:24 morphos.iso<br />
1501436 07-04-2018 04:03:02 boot.img<br />
ok<br />
0 > boot usb1/disk@1:,\boot.img bi umsd0:morphos.iso</nowiki><br />
<br />
If the stick is connected to a USB hub, the path just gets deeper in the OF tree:<br />
<nowiki><br />
0 > dev usb1 ls<br />
ff9e1650: /hub@1<br />
ff9e1860: /disk@4<br />
0 > boot usb1/hub@1/disk@4:,\boot.img bi umsd0:morphos.iso</nowiki><br />
<br />
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.<br />
<br />
List the contents of the partitions until you find the correct partition where you copied the new boot.img file.<br />
<nowiki><br />
0 > dir hd:1,\<br />
MAC-PARTS: specified MAC partition is not valid can't OPEN the DIR device<br />
ok<br />
0 > dir hd:2,\<br />
<br />
Volume: OSX<br />
Size/ GMT File/Dir<br />
bytes date time TYPE CRTR Name<br />
07/22/2017 07:27:40 Applications<br />
09/27/2016 09:59:40 bin<br />
1501436 07-04-2018 04:03:02 ???? UNIX boot.img<br />
ok<br />
0 > boot hd:2,\boot.img bi umsd0:morphos.iso</nowiki></div>
JPV
https://library.morph.zone/index.php?title=Shell_Commands/Copy&diff=4356
Shell Commands/Copy
2025-05-20T07:16:17Z
<p>JPV: </p>
<hr />
<div>'''Copy''' - Copies a source file or directory to another directory<br />
<br />
FROM/M, TO, PAT=PATTERN/K, BUF=BUFFER/K/N, ALL/S, DIRECT/S, <br />
CLONE/S, DATES/S, NOPRO/S, PROX/S, COM=COMMENT/S, QUIET/S, NOREQ/S, <br />
ERRWARN/S, MAKEDIR/S, MOVE/S, DELETE/S, HARD=HARDLINK/S, <br />
SOFT=SOFTLINK/S, FOLNK=FORCELINK/S, FODEL=FORCEDELETE/S, <br />
FOOVR=FORCEOVERWRITE/S,DONTOVR=DONTOVERWRITE/S,FORCE/S <br />
<nowiki><br />
FROM - files or directory to copy. <br />
TO - destination path-name or file<br />
PATTERN - when FROM is a directory, only files matching this pattern<br />
will be copied.<br />
BUFFER - size of the buffer (multiple of 512 bytes)to use during the copy<br />
ALL - includes sub-directories if FROM is a directory<br />
DIRECT - copy file without any tests or options<br />
CLONE - keeps timestamp, comments, and protec. bits of the FROM file.<br />
DATES - the timestamp of the FROM file is copied to the TO file.<br />
NOPRO - The protection bits of the FROM file are not copied<br />
to the TO file. The TO file is given standard protection bits<br />
or r, w, e, and d.<br />
PROX - only copy X,S,P protection bits<br />
COMMENT - the comments of the FROM file are copied to the TO file.<br />
QUIET - suppresses output messages/errors and requesters.<br />
NOREQ - errors such as disk full, or assign not existing will cause<br />
the display of a requester. Using this switch will remove them.<br />
ERRWARN - do not proceed when one file failed.<br />
MAKEDIR - produce directories.<br />
MOVE - delete source files after the copying successful.<br />
DELETE - do not copy but delete the source files.<br />
HARD - make a hardlink to source instead of copying.<br />
SOFT - make a sourcelink to source instead of copying.<br />
FOLNK - also makes links to directories.<br />
FODEL - delete protected files as well.<br />
FOOVR - also overwrites protected files.<br />
DONTOVR - do not overwrite files if they already exist<br />
FORCE - DEPRECIATED: if files already exist and are write-protected,<br />
this option will force them to be overwritten</nowiki><br />
Copy copies the file or directory specified with the FROM argument<br />
to the file or directory specified by the TO argument.<br />
You can copy several items at once by giving more than one name/pattern<br />
in the FROM argument; they should be separated by spaces.<br />
If the FROM argument is a pattern or consists of multiple names,<br />
the TO argument must be a directory.<br />
If a TO file name already exists, Copy overwrites the TO file with<br />
the FROM file. You can use a pair of double quotation marks ("")<br />
to refer to the current directory. When used as the FROM argument,<br />
"" copies all the files in the current directory.<br />
Do not put any spaces between the double quotation marks.<br />
<br />
Example:<br />
<br />
<nowiki>Ram Disk:> Copy System: Work:System/ ALL CLONE QUIET</nowiki><br />
Creates a backup of the whole System partition. The CLONE option preserves original file attributes and dates.</div>
JPV
https://library.morph.zone/index.php?title=Links&diff=4355
Links
2025-05-20T07:04:48Z
<p>JPV: </p>
<hr />
<div>==Official MorphOS Website==<br />
* http://www.morphos-team.net<br />
<br />
<br />
==Community Portals & Forums==<br />
* http://morph.zone<br />
<br />
* https://www.morphos-forum.de<br />
<br />
* http://www.pegasos.org<br />
<br />
* http://www.pegasos.hu<br />
<br />
* http://www.ppa.pl<br />
<br />
* http://saku.bbs.fi/foorumi<br />
<br />
* http://www.warmup-asso.org<br />
<br />
* http://www.warmup-asso.fr<br />
<br />
* http://www.morphos-store.com - A website to buy and sell MorphOS hardware and software.<br />
<br />
<br />
==File Repositories==<br />
<br />
* http://mos.aminet.net - Aminet MorphOS Section<br />
<br />
* https://www.morphos-storage.net - MorphOS Storage by WArMUp<br />
<br />
* <s>http://morphos-files.ppa.pl</s> - MorphOS File Hosting Service (abandoned)<br />
<br />
* http://morphos.lukysoft.cz - MorphOS Software Database<br />
<br />
<br />
==Software==<br />
<br />
<br />
Demoscene<br />
<br />
* https://jpv.amigaaa.com/demopack_morphos/ - MorphOS Demopack<br />
<br />
<br />
Emulation<br />
<br />
* http://www.amidog.com/amiga/fpse/ - Free PlayStation Emulator, ported by Mathias 'AmiDog' Roslund<br />
<br />
* http://ace.cpcscene.net/en:introduction - The acidulous CPC/CPC+ emulator.<br />
<br />
<br />
Internet & Network<br />
<br />
* http://www.amipodder.com - AmiPodder, free podcast client<br />
<br />
* http://www.heightanxiety.com/AmiSSL/ - Port of OpenSSL for legacy applications<br />
<br />
* http://amitradecenter.net - AmiTradeCenter, FTP client<br />
<br />
* http://www.students.tut.fi/~komsa/amiga/beehive/ - Home of Beehive, a BitTorrent client<br />
<br />
* http://sourceforge.net/projects/simplemail/ - SimpleMail, open source email client<br />
<br />
* http://www.yam.ch - YAM, open source email client<br />
<br />
* http://www.amirc.org - The famous IRC client<br />
<br />
<br />
Music<br />
<br />
* http://www.digiboosterpro.de/en/ - Home of Digibooster Pro<br />
<br />
* http://jahjah.free.fr/morphos/ - Home of Ripper, a CD music ripping and conversion tool<br />
<br />
* http://amigadev.free.fr/songplayer/index_en.html - Home of SongPlayer, a music player<br />
<br />
* http://tcheko.binaryriot.org/soundbankster/ - A realtime audio mixing application dedicated to DJ enthusiasts<br />
<br />
<br />
Office<br />
<br />
* http://amigadev.free.fr/pointrider/ - PowerPoint viewer application<br />
<br />
* http://www.grasshopperllc.com - Home of Pagestream, a commercial desktop publishing / page layout software<br />
<br />
* http://beebase.sourceforge.net - Home of BeeBase aka MUIBase, Steffen Gutmann's relational programmable database (with GUI)<br />
<br />
* http://shinkuro.altervista.org/amiga/software/nowined.htm - Home of NoWinEd, text editor<br />
<br />
* http://www.winfield.demon.nl - Free MS Word reader<br />
<br />
<br />
Package Management<br />
<br />
* http://www.geit.de/eng_grunch.html - Search, download, install, update, and uninstall programs<br />
<br />
<br />
System<br />
<br />
* http://morphosambient.sourceforge.net - Ambient 'desktop' environment<br />
<br />
* http://scalos.noname.fr - Scalos desktop, an alternative to Ambient<br />
<br />
* http://sourceforge.net/projects/snoopium/ - System monitor application.<br />
<br />
* http://sourceforge.net/projects/backman/ - Backman, open source backup program<br />
<br />
* http://amigazeux.net/diavolo/ - Diavolo Backup, formerly commercial backup program<br />
<br />
==Developers==<br />
<br />
* http://amigazeux.org - AmiNet Radio, Dragon, Wetter, SkinClock, and much more.<br />
<br />
* http://polymere.free.fr/index_en.html - Home of PolyNet (icon bar), PolyOrganizer and PolyGlot (MSN messenger)<br />
<br />
* http://members.shaw.ca/realstar/ - Developer of the Aqua, Eve and HyperCannon game titles.<br />
<br />
* http://fabportnawak.free.fr - MPlayer, ScummVM, Odyssey Web Browser, MAME, and more.<br />
<br />
* http://krashan.ppa.pl - DigiBooster 3, MorphOS Programmer's Handbook, audio tools, and more.<br />
<br />
* http://tbs-software.com/morgoth/<br />
<br />
* http://khtml.ppa.pl<br />
<br />
* http://bigfoot.morphos-team.net<br />
<br />
* http://dreamolers.binaryriot.org<br />
<br />
* http://tokai.binaryriot.org<br />
<br />
* http://www.biclodon.com<br />
<br />
* http://www.iki.fi/sintonen<br />
<br />
* http://www.tbs-software.com/stefkos/<br />
<br />
* http://home.elka.pw.edu.pl/~mszyprow/programy/ - Author of SFSDoctor.<br />
<br />
* http://kiero.binaryriot.org - Freespace 1&2, Foobilliard, Homeworld, scube, szoom, and more.<br />
<br />
* http://www.geit.de - Home of Grunch, MagicBeacon, MMKeyboard, and more.<br />
<br />
* http://yellowblue.free.fr - Home of Yomgui, who maintains Blender, Python, PyMUI and Helios (Firewire)<br />
<br />
* http://www.orel.rekom.ru/~imax/ - Maxim Ilyin ported VirtualJaguar, Mike Steed's FlashPlayer, and more.<br />
<br />
* http://haru.at/ - Creator of MorphUp packagement system, ported VLC, MLDonkey, and more.<br />
<br />
* http://www.amirus.org.ru - Various utilities such a KeyMorpher, a MUI-based key mapper. (Website is in Russian.)<br />
<br />
* http://tbs-software.com/mark/ - Developer of PowerD, various utilities.<br />
<br />
* http://tbs-software.com/powerd/ - PowerD programming language<br />
<br />
* http://www.lukysoft.cz - Home of Lukáš Stehlík (AmiGod benchmark)<br />
<br />
* http://dasixk.free.fr - Home of SixK, who ported a multitude of apps<br />
<br />
* http://alfie.altervista.org - Home of Alfonso 'alfie' Ranieri, creator of RxMUI, AmRSS (RSS client), and much more. <br />
<br />
* http://morphware.schwarzes.net - Various small tools made by Andreas Schwarz.<br />
<br />
* http://www.onyxsoft.se - Home of Onyxsoft who have released a number of applications and games.<br />
<br />
* http://www.mguc.ppa.pl - Marian Guc's website, developer of PciTool, AutoDoc Reader and the unfinished Nemesis desktop.<br />
<br />
* http://brain.umcs.lublin.pl/~rzookol/ - Michał Żukowski's website, developer of SCANdal (scanner software)<br />
<br />
* http://www.igracki.de - gTranslator, yWeather, CRABUM, and more.<br />
<br />
* http://www.morguesoft.eu - Various screen savers.<br />
<br />
* http://tcheko.binaryriot.org/ - SoundBankster, commodities, utils.<br />
<br />
* http://bszili.morphos.me/ - Home of BSzili, who has ported numerous games.<br />
<br />
* https://jpv.amigaaa.com/ - Hollywood applications and Lua, ARexx, and shell scripts.<br />
<br />
<br />
==Misc==<br />
<br />
* http://www.via-altera.de/mid.htm - some documents about MorphOS (German/English)<br />
* https://morphosuser.wordpress.com - Yasu's MorphOS Blog<br />
* http://pegasos.lena-johannson.de/ - Otti website with many Deutsch translations</div>
JPV
https://library.morph.zone/index.php?title=Hardware_Compatibility&diff=4353
Hardware Compatibility
2025-01-18T16:17:31Z
<p>JPV: /* Mice */</p>
<hr />
<div><div id="hardwareCompatibility"><br />
<br />
== Official Information ==<br />
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]].<br />
<br />
== User Provided Reports ==<br />
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.<br />
<br />
'''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. <br />
<br />
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.<br />
<br />
=== Game Controllers ===<br />
<table style="width:100%"><br />
<tr><th class="type">USB Device</th><th class="driver">USB driver</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>8bitdo SFC30 Pro Controller</td><td>hid</td><td>3.11</td></tr><br />
<tr><td>8bitdo SN30 Pro Controller</td><td>hid, xbox360</td><td>3.11</td><td>wired</td></tr><br />
<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><br />
<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><br />
<tr><td>Logitech Rumble Pad wired (USB2)</td><td>hid</td><td>3.11</td></tr><br />
<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><br />
<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><br />
<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><br />
<tr><td>Saitek P380 Dual Analog wired (USB2)</td><td>hid</td><td>3.11</td></tr><br />
<tr><td style="color:red;">Sony Dualshock 3 (PS3)</td><td>-</td><td>-</td><td>not supported</td></tr><br />
<tr><td>Sony Dualshock 4 (PS4)</td><td>xbox360</td><td>3.10</td></tr><br />
<tr><td>Speedlink Competition Pro USB</td><td>hid</td><td>3.11</td></tr><br />
<tr><td>Speedlink Xeox Gamepad</td><td>hid</td><td>3.11</td></tr><br />
<tr><td>[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)</td><td>hid</td><td>3.15</td></tr><br />
<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><br />
<tr><td>Xbox 360 wired and wireless pads</td><td>xbox360</td><td>3.11</td><td>wireless supported via PC adapter</td></tr><br />
<tr><td>Xbox One gamepad</td><td>xbox360</td><td>3.11</td><td>wired only</td></tr><br />
<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><br />
</table><br />
<br />
=== Keyboards ===<br />
<table style="width:100%;"><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>Apple A1016 Wireless BlueTooth</td><td>3.10</td><td>①</td></tr><br />
<tr><td>Apple Magic Keyboard (Version 1)</td><td>3.13</td><td>①</td></tr><br />
<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><br />
<tr><td>Ducky Zero Keyboard DK2108SZ</td><td>3.10</td><td></td></tr><br />
<tr><td>IBM SK-8815 Corded USB Keyboard</td><td>3.15</td><td></td></tr><br />
<tr><td>Logitech UltraX Premium</td><td>3.10</td><td></td></tr><br />
<tr><td>Microsoft Wired Keyboard 600</td><td>3.13</td><td>Model X880609-600</td></tr><br />
<tr><td>Microsoft Wireless 900 Keyboard</td><td>3.13</td><td>Mouse+kb combo</td></tr><br />
<tr><td>Rapoo E6300 Ultra-Slim BT keyboard for iPad</td><td>3.11</td><td>①</td></tr><br />
<tr><td>Rapoo E9050 Wireless Compact Ultra-Slim Keyboard</td><td>3.11</td><td></td></tr><br />
<tr><td>Rapoo E2710 Wireless Nano-USB Keyboard</td><td>3.11</td><td></td></tr><br />
<tr><td>Xenta Super Compact Black Wired Keyboard (RK 107)</td><td>3.13</td><td></td></tr><br />
</table><br />
① requires a machine which supports paired BT input devices, like Mac mini<br />
<br />
=== Mice ===<br />
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>A-Eon Technology MX-1000-1</td><td>3.13</td><td></td></tr><br />
<tr><td>Dacota Gaming Serpent Mouse</td><td>3.15</td><td>Wired, 809024</td></tr><br />
<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><br />
<tr><td>Logitech M180</td><td>3.11</td><td></td></tr><br />
<tr><td>Logitech M185</td><td>3.10</td><td></td></tr><br />
<tr><td>Logitech M190</td><td>3.15</td><td></td></tr><br />
<tr><td>Logitech M220 Silent</td><td>3.15</td><td></td></tr><br />
<tr><td>Logitech M330 Silent</td><td>3.14</td><td></td></tr><br />
<tr><td>Logitech M650</td><td>3.19</td><td></td></tr><br />
<tr><td>Logitech M650 L</td><td>3.19</td><td></td></tr><br />
<tr><td>Logitech T-RB22 Wireless Trackball</td><td>3.11</td><td></td></tr><br />
<tr><td>Logitech G203</td><td>3.10</td><td>No software control over RGB, DPI</td></tr><br />
<tr><td>Labtec Optical Mouse 800</td><td>3.10</td><td></td></tr><br />
<tr><td>Microsoft Compact Optical Mouse 500</td><td>3.14</td><td></td></tr><br />
<tr><td>Microsoft Trackball Explorer v1.0</td><td>3.11</td><td>PS2>USB adapter required</td></tr><br />
<tr><td>Microsoft Wireless Mouse 900</td><td>3.14</td><td>Mouse+kb combo</td></tr><br />
<tr><td style="color:red;">Microsoft Wireless Mouse 4000</td><td>3.13</td><td>Not working</td></tr><br />
<tr><td>Razer Viper Mini</td><td>3.15</td><td>No software control over RGB, DPI</td></tr><br />
<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><br />
<tr><td>Targus AMU3102EU</td><td>3.10</td><td></td></tr><br />
<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><br />
</table><br />
<br />
=== MIDI Devices ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard</td><td>3.13</td><td></td></tr><br />
<tr><td>[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard</td><td>3.13</td><td></td></tr><br />
<tr><td>Yamaha PSR-433 keyboard</td><td>3.14</td><td></td></tr><br />
</table><br />
<br />
=== Networking ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>TL-WR702N Nano Router</td><td></td><td></td></tr><br />
<tr><td>TL-WR802N Nano Router</td><td></td><td></td></tr><br />
</table><br />
<br />
=== Printers ===<br />
<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><br />
<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><br />
<tr><td>Konica Minolta Magicolor 4650</td><td>3.11</td><td></td><td>M4650PX.ppd</td><td></td></tr><br />
<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><br />
<tr><td>Xerox 3225 Workcentre</td><td>3.11</td><td></td><td></td><td>Reported to work with PS</td></tr><br />
<tr><td>HP Color LaserJet MFP M274n</td><td>3.15</td><td></td><td>hp-color_laserjet_mfp_m274-ps.ppd</td></tr><br />
<tr><td>Xerox B230</td><td>3.18</td><td>HP_LaserJet5series</td><td>[https://www.support.xerox.com/en-mu/product/xerox-b230-printer/content/152267 PPD at support page]</td><td>B225 & B235 should work too, maybe also C230 & C235</td></tr><br />
</table><br />
<br />
=== Scanners ===<br />
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>Epson Perfection 1640SU</td><td>3.11</td><td>Including recent support for its ADF (Automatic Document Feeder).</td></tr><br />
</table><br />
<br />
=== Storage ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<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><br />
</table><br />
<br />
=== USB Audio Devices ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th>Output</th><th>Input</th><th class="comments">Comments</th></tr><br />
<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><br />
<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><br />
<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><br />
<tr><td>C-Media soundcard</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr><br />
<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><br />
<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><br />
<tr><td>FX-Audio- DAC-X3</td><td>3.12</td><td>OK</td><td>N/A</td><td></td></tr><br />
<tr><td>Griffin iMic</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr><br />
<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><br />
<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><br />
<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><br />
<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><br />
<tr><td>Steelseries Arctis 7 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr><br />
<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><br />
<tr><td>Turtle Beach Stealth 520 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr><br />
</table><br />
<br />
</div></div>
JPV
https://library.morph.zone/index.php?title=Tips_and_Tricks&diff=4352
Tips and Tricks
2025-01-08T10:49:14Z
<p>JPV: FireWire Debugging</p>
<hr />
<div>''Originally published at: http://jpv.wmhost.com/morphos/tips/''<br />
<br />
Miscellaneous tips and tricks for MorphOS use. Some may even be hackish and not officially encouraged by MorphOS Team. Everyone is welcome to make additions and corrections here.<br />
== Basic Features ==<br />
<br />
=== Modifying the System Directory ===<br />
: Tip #1: NEVER modify anything in the MOSSYS: (SYS:MorphOS/) path! All changes are lost in a system upgrade. If you need to add any 3rd party drivers or libraries, add them to SYS:. If there isn't a correct directory by default, make one.<br />
<br />
: There's only one exception (of course there is one) to this: you can rename MOSSYS:Libs/rexxsyslib.library to MOSSYS:Libs/rexxsyslib.library_disabled when you copy a 68k version of rexxsyslib.library to SYS:Libs/ in order to get the ARexx environment working.<br />
<br />
<br />
=== Keyboard Commands ===<br />
<br />
: At first, check the default ones and define your favourites in '''System Settings -> IControl -> Hotkeys''' and in '''Ambient Settings -> Keyboard'''.<br />
<br />
: For example IControl has "Active Window: Activate Next" and "All Windows: Depth Menu" options, which can be used to achieve alt/ctrl/command-tab style window cycling functionality familiar from other operating systems.<br />
<br />
: Other keys: <br />
:* To zoom Ambient icons in the icon mode: keep CTRL pressed and use the mouse wheel or just roll the wheel over the Viewmode button.<br />
:* To find and select files in Ambient windows by letters: start typing a name when the window is active. Keep the Shift key pressed for directories. <br />
:* To enter a path manually (for example for hidden dirs like .recycled): press the / key in an Ambient window and type in the path. <br />
:* Command-f activates the find function in most programs. <br />
:* The r key rotates the pictures in Ambient's internal viewer and Page Up/Down keys select previous and next images in a dir <br />
:* Check keyboard commands of the Shell, like by default, commands can be completed with CTRL-tab, devices with ALT-tab, history with shift-tab etc. <br />
:* Keeping the Alt key pressed while double clicking a drawer gives you different ways to open drawers.<br />
:* Keeping the Alt key pressed while dragging files on the same partition copies files instead of moving, or vice versa depending on your Ambient settings.<br />
<br />
=== Enabling/Disabling Icon Tooltypes ===<br />
<br />
: Double click single tooltypes to enable and disable them in the icon information window.<br />
<br />
<br />
=== Browsing History in Ambient ===<br />
<br />
: Clicking the parent button ([[File:Tips_Parent.png|middle]]) on an Ambient window (in browser mode) with the right mouse button gives you a browsing history popup menu for quick jumping between locations.<br />
<br />
<br />
=== Sync the Clock from Internet at Boot ===<br />
<br />
: Add this line to S:user-network-startup file:<br />
: <tt>Run DETACH MOSSYS:C/SetClockNTP SAVE</tt><br />
<br />
<br />
=== Redirecting AHI Music Unit ===<br />
<br />
: You can select Unit 0 as the Music Unit in AHI to be able hear audio output from multiple programs at the same time, with a slight decrease in quality.<br />
<br />
: [[File:MorphOS_System_settings_Music_Unit.png|280px]]<br />
<br />
<br />
=== Keeping AHI Audio Quality Better ===<br />
<br />
: Audio quality with AHI will be better if you reduce available channels for its shared modes (Unit 0 usually). Available channels will limit the amount of simultaneus playback of sounds, but you really don't need the default 32 channels and even two channels can be quite enough. Should there be more concurrent sounds, some of them just get muted until the other have been finished.<br />
<br />
: [[File:MorphOS_System_settings_Change_Unit.png|280px]] [[File:MorphOS_System_settings_Unit_0.png|280px]]<br />
<br />
<br />
=== Mime Type Configuration ===<br />
<br />
: Learn to configure mime types from the Ambient settings. It really gives so much for your system and your user experience. [http://jpv.wmhost.com/pics/mimemplayer.png Here] is one example of how to configure MPlayer for all the video files.<br />
<br />
<br />
=== Inline Editing ===<br />
<br />
: Inline editing is a quick way to edit filenames by clicking them with the mouse wheel or with the long left mouse click. Its behaviour can be configured from the Lister settings in Ambient Settings.<br />
<br />
: File comments can also be edited with the inline editing.<br />
<br />
: [[File:Tips_Inlineedit.png|280px]]<br />
<br />
<br />
=== Batch Renaming in Ambient ===<br />
<br />
# Select files you want to be in the range of renaming.<br />
# Hit rename button or command-r keyboard shortcut.<br />
# Use pattern to rename. For example renaming all files which begin with "mod." to files which end with ".mod", use "mod.*" as source and "*.mod" as destination (quotation marks not needed).<br />
<br />
<br />
=== Don't Forget RMB/Long-LMB Gadget Menus ===<br />
<br />
: You get menus from zoom and depth gadgets with right mouse button or by holding left mouse button pressed on them.<br />
<br />
: [[File:Tips_Zoommenu.png]] [[File:Tips_Windowdepthmenu.png]] [[File:Tips_Screendepthmenu.png]]<br />
<br />
<br />
=== How to Use RMB with One-button Mouse ===<br />
<br />
: The right mouse button can be emulated in several different ways:<br />
:* The '''System Settings -> Mouse -> Open menus by clicking...''' setting lets your mouse button act as the right mouse button if you hold a qualifier key pressed while clicking. The qualifier key can be configured for your preferences, but it's the shift key by default.<br />
:* Press right alt and right command keys together. This probably doesn't work on systems with ADB keyboard, like on older Mac laptops. The ADB keyboard doesn't make difference between left and right keys.<br />
:* With non-ADB laptops (PowerBook 5,6-5,9 and 6,7 (iBook)) you can also use two finger tap or two finger hold + button combination on the touchpad for RMB.<br />
:* You can define a hotkey for menu launching on the IControl preferences (the default one is rcommand+space). It doesn't work exactly as the RMB everywhere, but works if you're mostly using the RMB for menus.<br />
:* A multi button USB mouse works always!<br />
<br />
<br />
=== Starting Programs Iconified ===<br />
<br />
: MUI has an option to start programs in iconified mode. It's useful for example for programs like Synergy, which you'd like to start on background without their main window jumping up. The option can be found from program's MUI Settings (Windows -> Iconify on startup).<br />
<br />
: [[File:Tips_Iconify.png]]<br />
<br />
<br />
=== Checking the Debug Log ===<br />
<br />
: If you want a stable system, you need to check the debug log periodically to see if any program misbehaves when used, especially when running new software.<br />
<br />
: An easy way to do it is to enable Debug screenbar module from the screen depth gadget menu. Bug looking Debug button on the screenbar will then give you a debug menu where you can view the log etc. If "Show Log..." option is ghosted, there's nothing in the log and everything is fine, but if it shows hundreds of cryptic lines (it's called a hit), then you have something to worry and the system probably isn't stable anymore. Some programs may output their own harmless debug information to the log too, but it's usually limited to few or tens of lines maximum. You'll recognize a real hit for sure.<br />
<br />
: [[File:Tips_Debug1.png|x64px]] [[File:Tips_Debug2.png|x64px]]<br />
<br />
<br />
=== Printing to a PostScript Compatible Network Printer ===<br />
<br />
: You should mount the NETPAR: device and print to that device from programs like VPDF and OWB, which can output PostScript. NETPAR: is faster than printing through Turboprint (PRT:) and doesn't need Ghostscript installed (PS:).<br />
<br />
: "Mount NETPAR:" can be added to S:user-startup, for example.<br />
<br />
<br />
=== .recycled Directory ===<br />
<br />
: SFS is the default filesystem on MorphOS. It can have a special directory which contains recently deleted files. The directory is named as .recycled and it resides at the root level of every SFS partition (SYS:.recycled for example). Depending the format options it may be disabled, hidden but accessible, or visible.<br />
<br />
: If it's hidden, you can't see it even with "View All Files" option, but you can access it from the shell or Ambient (for example by pressing / key and then writing it to the path string after the volume name).<br />
<br />
: You shouldn't modify any files in it, but you can recover deleted files by copying them to some other path.<br />
<br />
: The PFS3 filesystem has a similar directory, but its name is ".deldir".<br />
<br />
<br />
=== How to Reduce Graphics Memory Usage ===<br />
<br />
: MorphOS can use graphics memory quite extensively which can cause slowdowns or glitches if you run out of it. It usually isn't an issue if you have 64MB or more graphics memory, but lower spec systems with today's resolutions may need some tuning. There are several ways to reduce memory usage and you have to decide or try which is the best for you.<br />
<br />
: MorphOS has an "Enhanced Display" mode, which uses the graphics card's 3D functions to draw graphic layers. It consumes more memory than the traditional 2D mode, but it provides some eyecandy, tearless moving etc.<br />
<br />
: To reduce its memory usage, you may:<br />
:* Change its buffering settings on the DisplayEngine settings in MorphOS Preferences. You need to reboot or switch screens for the new settings to take effect.<br />
:* Disable it completely from the Screens settings in MorphOS Preferences for some or all screens. It may also help if you let it be enabled for Ambient screen, but disable it on other screens you might have.<br />
<br />
: Other ways to reduce graphics memory usage:<br />
:* Lower the color depth of screens from the Screens settings. 16-bit might be enough sometimes.<br />
:* Don't use too many separate screens at the same time.<br />
<br />
<br />
=== How to Open MUI Programs on Their Own Screens ===<br />
<br />
: 1) An easy way is to select "Jump to Screen -> New" from the MUI popup menu gadget in program's window border. It always opens in an enhanced mode and clones the resolution from the Ambient screen. Open and save program's MUI settings to save it permanently.<br />
: [[FIle:MorphOS3_jPV_Newscreen.png|120px]]<br />
<br />
: 2) A more configurable method is to open program's MUI settings, select the Screen tab, and create a totally new screen definition there. You can edit the screen name and the title to suit your use (you can use program's name for those for example), select any resolution and depth, enable or disable the enhanced mode etc. In many cases this is a better method, because you can save graphics memory by not using the enhanced mode for screens which you're going to use for full screen apps only or so.<br />
<br />
: You can switch between the screens with lamiga-m (lcommand-m) keyboard shortcut, or by clicking the screen depth gadget (left click switches to the next screen, right click gives you a menu where you can select any open screen).<br />
: [[File:Tips_Screendepthmenu.png]]<br />
<br />
<br />
== Advanced Features ==<br />
<br />
=== Default Device Icons ===<br />
<br />
: If you want a certain default icon for all the units of a certain device, you can create an icon named def_DEVICENAMExdisk.info to your default icons path (SYS:Prefs/Presets/Deficons/ by default).<br />
<br />
: For example the deficon for SMBFS devices would be called def_SMBFSxdisk.info.<br />
<br />
<br />
=== Default Icon for Ambient Windows ===<br />
<br />
: By default there isn't a default icon file for the icon you see when iconifying an Ambient window (a view). If you want to override the built-in icon, create or copy a new icon file to your default icons path and name it to '''def_view.info'''. <br />
<br />
<br />
=== Old Style Preferences Icons ===<br />
<br />
[[File:Separate_prefs_in_MorphOS.png|thumb|Example of separate system prefs in MorphOS]]<br />
: You can have separate preferences icons in the SYS:Prefs/ directory in the old Amiga style for MorphOS system prefs. Make or copy icons named with a corresponding sub preference name into the SYS:Prefs/ dir and edit their Default Tool to ":MorphOS/Prefs/Preferences".<br />
<br />
: There's already a main preferences icon in SYS:Prefs, so here's an easy example: "copy SYS:Prefs/Preferences.info SYS:Prefs/Network.info", after which double clicking the new Network icon opens the network preferences directly.<br />
<br />
<br />
=== Hilight Options in Listers ===<br />
<br />
: If you want to use "Alternated rows" and "Hilighted sorting column" options in the Lister settings with a grapchics card that doesn't support 3D acceleration.<br />
: Type in shell:<br />
: <tt>Setenv MUI/fastppa SAVE 1</tt><br />
<br />
<br />
=== Copy Selected Filenames ===<br />
<br />
: You can use the internal Ambient command "copyselectiontoclipboard" to copy selected filenames with or without path information to the clipboard. For example, create a new custom hotkey in the Ambient Settings and define "copyselectiontoclipboard VIEWID=%Si FULLPATH" as an internal command for it.<br />
<br />
: User may find it very useful to paste around the names selected in the Ambient windows in many situations.<br />
<br />
<br />
=== Using ARexx Ports from Lua ===<br />
<br />
: MorphOS comes with a native implementation of the Lua scripting language. It can be used for script writing with application interacting instead of the emulated 3rd party ARexx. Lua can use existing ARexx ports with its ipc.module.<br />
<br />
: Load the IPC module first with the '''require 'ipc'''' line (unlike the standard Lua distribution, all modules have to be loaded with the ''require'' function on MorphOS. Check available modules from the ''MOSSYS:Libs/Lua/'' directory.)<br />
<br />
:* ipc.'''address(port)''' - sets the default ARexx port. Port "COMMAND" executes commands as DOS shell commands. <br />
:* '''ipc.checkport(port)''' - checks if an ARexx port is available. <br />
:* ipc.'''rx(command)''' - sends a command to a port set with ipc.address. It returns ARexx RESULT. <br />
:* '''ipc.waitforport(name[, interval])''' - Waits for an ARexx port. Script is aborted if the port isn't found.<br />
<br />
: More about the topic [[Getting_Started_with_Lua|here]].<br />
<br />
<br />
=== Copying a Whole Disk As an Image File ===<br />
<br />
: You can access raw data of drives by MorphOS's RAWDISK: device. Partitions or whole disk can be copied in or out with it, but be careful to write to the correct destination! For copying you need to use SDK's cp command or standard Copy command with the DIRECT option.<br />
<br />
: You can browse available disks and devices by opening RAWDISK: device from the shell (just type RAWDISK: on the shell) or from Ambient (hit the / key, clear existing text, and write RAWDISK: to the string line). Browse to the Devices directory and then to the wanted device and unit to see the actual disk image file (rawdisk) and partition files in a separate partition table directory. Partition files let you recognize more easily that you're accessing the wanted disk. They also have information like device and filesystem names told in file comments (use the List command or Ambient to see them).<br />
<br />
: As an example, to make a backup of a whole SD card which is placed in a USB reader (the card is found in usbscsi.device unit 3):<br />
: <tt>Copy DIRECT RAWDISK:Devices/usbscsi.device/3/rawdisk work:sdcard.img</tt><br />
<br />
: And to copy the image back to the SD card (removes all existing data, be careful!):<br />
: <tt>Copy DIRECT work:sdcard.img RAWDISK:Devices/usbscsi.device/3/rawdisk</tt><br />
<br />
: This works with all raw disk image files like Raspberry Pi's OS distributions etc.<br />
<br />
: Single partitions can also be copied from the RAWDISK:Disks directory.<br />
<br />
: If you want to access the data in saved image files without needing to write them back to any device, you can mount them with help of [[Tools/FileImageCtrl]] and [[Tools/Mounter]] programs. You can either mount partitions directly with the [[Tools/FileImageCtrl|FileImageCtrl]] tool or insert disk images on it and mount the wanted partitions with the [[Tools/Mounter|Mounter]] tool.<br />
<br />
<br />
=== Using WLAN with Hidden SSID ===<br />
<br />
: If you have to use wireless network with hidden SSID, you can add "scan_ssid=1" line in your ENVARC:sys/Wireless.prefs file's network block.<br />
<br />
: Contents should look something like this:<br />
<br />
: <tt>network={<br />
: &nbsp;&nbsp;ssid="ThatHiddenSSID"<br />
: &nbsp;&nbsp;scan_ssid=1<br />
: &nbsp;&nbsp;psk="password"<br />
: }</tt><br />
<br />
: Note: It's not recommended to hide the SSID, because it doesn't add security in practise. Use this only if you can't control the network you're connecting.<br />
<br />
<br />
=== Modifying Screen and Keyboard Brightness on a Laptop without Using KB Shortcuts ===<br />
<br />
: Brightness values can be modified by editing the ENVARC:sys/laptopquick.conf file with a text editor. The values are taken in use after a reboot.<br />
<br />
<br />
=== Opening Ambient Windows from the Shell or Scripts ===<br />
<br />
: Directories can be opened with the [[Shell_Commands/Open|Open]] command, but it only opens them in the default view mode:<br />
: <tt>Open SYS:Applications</tt><br />
<br />
: If you need to open windows with certain location, size, position, and mode, you can use the LoadURI ARexx command. LoadURI accepts the following parameters:<br />
:* URI which contains a path and attributes with values. The attributes are given after a question mark and they are separated with the & delimiter. Possible attributes are ''view'' (icon or list), ''mode'' (all, icons, or thumbs), ''top'' (pixels from the top border), ''left'' (pixels from the left border), ''width'', and ''height''.<br />
:* NEW=NEWWIN/S: opens a new window even if similar window would already be opened<br />
:* RELOAD/S: reloads the URI<br />
:* FORCE/S: forces full reloading<br />
:* BROWSER/N: forces the browser mode on (1) or off (0)<br />
:* VIEWID/N: specifies view/window ID<br />
<br />
: Use the ''AMBIENT'' port in ARexx scripts.<br />
<br />
: To open the SYS:Libs directory in the list mode showing all files in a 440x600 window at position x=350, y=50, no matter if it has been opened previously:<br />
: <tt>'LoadURI "file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600" NEW'</tt><br />
<br />
: To open a directory in the icon mode showing thumbnails in a 500x400 window at position x=350, y=50, the window is also opened in the spatial (non browser) mode:<br />
: <tt>'LoadURI "file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400" BROWSER=0'</tt><br />
<br />
: If you don't want to write full ARexx scripts but would like to run them just as single shell commands, you can use the [[Shell_Commands/RXCmd|RXCmd]] shell command (notice that you have to escape the inner quotation marks with the asterisks):<br />
: <tt>RXCmd AMBIENT "LoadURI *"file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600*" NEW"<br />
: RXCmd AMBIENT "LoadURI *"file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400*" BROWSER=0"</tt><br />
<br />
<br />
== Bundled Software ==<br />
<br />
=== Flacapella Settings for MP3 Encoding ===<br />
<br />
: Example of a custom encoder setting in Flacapella:<br />
<br />
: <tt>Compress Command: c:lame -V0 --tt "{title}" --ta "{artist}" --tl "{album}" --tn {track} {?coverfile:--ti "{coverfile}"} {input} {output}<br />
: File Extension: mp3</tt><br />
<br />
: This will encode tracks to mp3 files with title, artist, album and track number tags. It also embeds fetched cover image in files, if image was found. <br />
: Example assumes you have [https://www.morphos-storage.net/?find=lame LAME] installed in C:<br />
<br />
<br />
=== Jukebox Tips ===<br />
<br />
:* If you select any song in playlist by clicking it just once, it's played next no matter if you have random or sequential mode in use. <br />
:* You can adjust volume in Jukebox by using mouse wheel over its screenbar module. <br />
:* Displayed columns can be configured on the fly by right clicking the column title.<br />
:* Jukebox can be better integrated into Ambient and its contextual menus with the [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script.<br />
:* Two new tooltypes were presented in MorphOS 3.8: <br />
:** '''FRAMESCAN=NO''' disables the Reggae framescanning for tracks that have unknown duration. It speeds up the loading of such tracks, but you'll lose the seeking ability with them. <br />
:** '''STREAMBUFFER=YES''' activates the Reggae streambuffer class which reduces stuttering, but causes lag on track change and seeking.<br />
<br />
<br />
=== How to Reduce OWB's HD Writes ===<br />
<br />
: OWB writes a lot of data to the hard drive by default. You might want to reduce it if you're paranoid about SFS fragmentation, filesystem corruption, privacy, or you'd like to avoid certain databases getting too big (which can cause slowdowns). Or you just want your .recycled dir to have other than the OWB files. One option is to use the Private Browsing mode always, but here are tips if you don't want to activate that always or you want to restrict certain writes only.<br />
<br />
:* Disable the TopSites feature. This makes a write for every page you visit, it's an awful amount. Its database (conf/TopSites.db) can also grow to hundreds of megabytes, which causes very noticeable slowdowns to browsing. You can disable it with the "Setenv SAVE OWB_DISABLE_TOPSITES 1" command in the shell, and if the database file has already grown too big, you can remove it.<br />
:* Disable the Website Icons feature. Open the Interface settings and uncheck all Website Icons checkmarks. <br />
:* Disable all saving options from the Privacy settings.<br />
<br />
: If you still need some option enabled, because some site requires it, you can soft link its configuration file to Ram Disk. I, for example, still have Local Storage enabled, but I have linked its dir to ENV: (which resides in Ram Disk). To do that, make LocalStorage directories to both ENV: and ENVARC: (that ensures that it's created after a reboot too), open the shell and cd into your OWB/Conf/ dir, rename or delete the old LocalStorage dir, type "makelink LocalStorage ENV:LocalStorage". Using ENV: gives the advantage to have some files saved so that those settings are restored in every boot. If you're happy with a certain setting, copy the corresponding file to ENVARC: and it will be preserved without being messed up with the later usage. If you just want to have the configuration files enabled, but cleared on every boot, you could soft link them to T: for example.<br />
<br />
<br />
=== Alternative YouTube Script for OWB ===<br />
<br />
: [http://www.morphzone.info/modules/newbb_plus/viewtopic.php?forum=9&topic_id=9799&post_id=109979&viewmode=flat&sortorder=0&showonepost=1 YouTube Center] is a feature rich configureable userscript for improving YouTube experience. It's made for mainstream browsers, but it also works on OWB! All videos can be forced to HTML5 to get them work in OWB. It's heavier than Fab's official OWB script, but works fine as an option or as a backup plan :). Script saves its settings to LocalStorage to #?www.youtube.com#? files.<br />
<br />
: Note: YouTube defaults to the HTML5 player nowadays and you might be fine without any Flash->HTML5 converter scripts. It's probably better to install this script only if you want some other features from it.<br />
<br />
<br />
=== Watching Videos with Less CPU Load in OWB ===<br />
<br />
: When watching a video in OWB, the fullscreen mode makes a lot less CPU load than the default embedded mode, because the fast overlay mode is used then. CPU load may drop from 100% to 40% for example. Wait until the video really starts playing before clicking the fullscreen button on it, or it may fail and you have to reload the video to be able to try it again. Some videos may have a fullscreen option in their contextual menu too. Remember to have Fullscreen Fix scripts added and enabled from the Scripts window ("Windows->Scripts..." pulldown menu entry) for YouTube, Dailymotion, and Vimeo.<br />
<br />
: Note: check that you really have the latest YouTube fullscreen fix script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js in your OWB/Scripts/ directory. Grunch doesn't get updated for the latest version always for example.<br />
<br />
<br />
=== Problems with YouTube Videos ===<br />
<br />
:* Now that YouTube defaults to HTML5, our days of ad-free videos have ended. It also means that the Content Blocking (AdBlock) option in the OWB's settings can block some videos. If you have some videos which won't start playing, try to disable the Content Blocking option and try again. If that was the problem, but you want to keep the content blocking enabled, add an allow rule to the Content Blocking settings. Open "Windows->Content Blocking..." from the OWB's pulldown menus, click the Add button, and write "youtube.com" to the Rule line. Close the window and try the video again.<br />[[File:OWB_ContentBlockingYT.png]]<br />
<br />
:* If all videos refuse to play, check if you have any YouTube converter scripts enabled in the "Windows->Scripts..." settings. The Fullscreen Fix script is the only one needed and you should disable all converter scripts.<br />
<br />
:* Flash plugins can also break compatibility with YouTube, so if you have the swfdec_plugin.library file in your OWB/Plugins/ directory, you have the following options to choose from:<br />
:** Remove the file from use if you don't need flash anywhere. The plugin doesn't work too well generally anyway.<br />
:** Keep the file, but disable it for all pages by unchecking the "Settings->Preferencfes->Content->Allow plugins" option. You can then enable it temporarily from "Settings->Plugins->Enable" if needed.<br />
:** Disable it temporarily from "Settings->Plugins->Disable", and reload the page.<br />
:** Disable it just for YouTube by adding a new URL setting from "Windows->URL Settings...". Click the Add button, edit the URL line to for example "youtube.com", and uncheck the Plugins option.<br />
<br />
<br />
=== OWB Doesn't Work or Stopped Working with Certain Web Pages ===<br />
<br />
:* Sometimes it helps to change the "Spoof as" setting in OWB. Web pages may offer different kind of content depending on what browser they think you are using. Some popular CAPTCHAs don't work with the default spoofing, but do work when spoofed as iPad for instance. iPad is generally a good option to start trying the spoofing, because you probably get the page in its simpliest form then.<br />
<br />
:* There are some bugs in the JavaScript engine in the latest available OWB version (1.24 at the time of writing) and that causes problems with some web pages, but there's a chance that these pages would still work with an earlier OWB version. You can download earlier OWB versions from [http://fabportnawak.free.fr/owb/ Fab's homepage] and install them, for example, to a different directory than your current OWB installation. There's no problem having two or even several OWB installations on your system, you can just launch whichever you want. As an example, Google Maps stopped working with OWB 1.24 in autumn 2017, but it still continued to work with [http://fabportnawak.free.fr/owb/owb-morphos-1.23.lha OWB 1.23].<br />
<br />
<br />
=== Creating an ISO Image ===<br />
<br />
: Jalapeno can also create and save ISO images which will preserve MorphOS/AmigaOS file attributes and comments. Images can be used for backups or even be booted from USB devices.<br />
<br />
: An option to create an ISO image is found on the pulldown menu in the Burn Files section.<br />
<br />
: [[File:Tips_Create_ISO.png|200px]]<br />
<br />
: If the resulting image file will be bigger than 1GB, Jalapeno splits it into 1GB parts. Those parts can be joined into one big image file with the Join command in the shell, but remember the filesize limits of your target [https://library.morph.zone/Filesystems filesystem] when doing that.<br />
<br />
<br />
=== Copying a CD/DVD to an ISO Image ===<br />
<br />
: If you want to make a standard, easily mountable, ISO image out of an existing CD or DVD, a good way to achieve it is to use the ReadCD program provided with the Jalapeno program on the standard MorphOS installation. Jalapeno itself can also create image files of optical media by selecting "Save as..." from the "Copy Tracks" pull-down menu, but resulting images aren't mountable by the system, because Jalapeno uses options that include more data into the images, for error checking etc.<br />
<br />
: Do these steps from the shell to read a CD/DVD into a standard ISO image:<br />
:# Find your CD drive device by typing: MOSSYS:Data/Jalapeno/readcd -scanbus<br />
:# Create an ISO image by typing (replace "1,1,0" to what you saw in the previous step, and the image path to what you want): MOSSYS:Data/Jalapeno/readcd -dev 1,1,0 f=ram:image.iso<br />
<br />
=== Disabling the Default UTF-8 Mode with Scribble ===<br />
<br />
: Scribble uses UTF-8 encoding by default, but you might prefer to default to the traditional ASCII format instead. The UTF-8 mode can be disabled from the pulldown menu in Scribble, but the setting isn't saved if you save the program settings.<br />
: [[File:Scribble_ascii1.png|128px]]<br />
<br />
: If you want to disable it by default, you have to open the "Save As..." requester, enable the "Make Default" option (also check that Encoding is set to ASCII), and save a file (can be any file anywhere).<br />
: [[File:Scribble_ascii2.png|205px]]<br />
<br />
<br />
== 3rd Party Software ==<br />
<br />
=== Where to Get Software? ===<br />
:* Check [http://library.morph.zone/Links#File_Repositories file repositories] for manual installing<br />
:* [http://www.geit.de/eng_grunch.html Grunch] is a good packet manager for automatic installation and updating of selected software<br />
:* [http://www.meta-morphos.org/WArMUp/chrysalis_en.pdf Chrysalis] is a preconfigured environment and software distribution package ([http://www.warmup-asso.org/download/pack/chrysalis.iso Download ISO image])<br />
<br />
<br />
=== Custom Ambient Menus with AREXX ===<br />
<br />
: You can add own menu items to Ambient pulldown menus with AREXX. Read SYS:MorphOS/Ambient/docs/arexx.txt for more info about AREXX usage or download the [http://morphos-files.net/remote/CRABUM CRABUM] program, which helps you to create correct AREXX lines ([http://library.morph.zone/Getting_Started#Creating_Menus_with_CRABUM tutorial]).<br />
<br />
<br />
=== Help with Shell Commands ===<br />
<br />
: MorphOS Library contains descriptions of all [http://library.morph.zone/Shell_Commands shell commands] and the descriptions can be displayed on the shell with the [http://aminet.net/package/util/batch/Chelp Chelp] script. The script can be used to replace older [http://aminet.net/package/util/cli/Help Help] program (which would otherwise be nice still, but it only contains help for MorphOS 1.x commands).<br />
<br />
<br />
=== Utilizing Your Keyboard's Multimedia Keys ===<br />
<br />
:* The [http://www.geit.de/eng_mmkeyboard.html MMKeyboard] software can be used to assign different kinds of functions to extra keys found on some keyboards.<br />
:* The [http://aminet.net/package/mus/play/MultiMeedio MultiMeedio] script provides a unified control for all popular media players.<br />
<br />
<br />
== Hardware Related ==<br />
<br />
=== Removing Startup Sound on Macs ===<br />
<br />
: Sadly there isn't any known way to disable that annoying startup sound from MorphOS itself or from Open Firmware, but there are few different ways to achieve it anyway.<br />
<br />
:* If you plan to use Mac as MorphOS only system, but you still have OSX installed, you can mute the audio from OSX before wiping it out by installing MorphOS. Startup sound doesn't come back if you won't boot into OSX anymore.<br />
:* If you don't have OSX anymore, you could try to remove sound with some Linux distribution's live/installation CD. More info [http://www.meta-morphos.org/faq.php?id_cat=2&myfaq=yes&categories=Installation+et+d%E9marrage#74 here] and [https://morphosuser.wordpress.com/2014/12/28/removing-the-boot-sound/ here].<br />
:* If you use OSX and MorphOS as a dualboot system you can install [http://www5e.biglobe.ne.jp/~arcana/StartupSound/index.en.html StartupSound.prefPane] for OSX.<br />
<br />
<br />
=== Speeding Up the Startup Manager on Macs ===<br />
<br />
: Startup Manager (the boot menu you get by booting with option/alt key pressed) can be slow when it tries to find network boot devices. To speed it up go to the OF prompt and type "'''setenv skip-netboot? true'''". Funnily enough, it only affects if you have network cable plugged in.<br />
<br />
<br />
=== Booting MorphOS ISO from USB Stick ===<br />
<br />
: MorphOS Team has released an [http://www.morphos-team.net/guide/usb-boot official guide] for USB booting, but I've also noticed that at least some Macs (Mac mini and Powerbook for example) have certain ud alias for USB drive. You can use that as a shortcut and get the booting done with less work (no need to search the correct path, works even when USB stick is in a hub, less typing and less to remember).<br />
<br />
: If you have only one mass storage device connected, you can just boot into Open Firmware prompt (command-alt-o-f) and type:<br />
<br />
: <tt>boot ud:,\boot.img bi umsd0:morphos.iso</tt><br />
<br />
: (Remember to have both boot.img and morphos.iso on the stick)<br />
<br />
<br />
=== Keyboard Reboot on ADB Laptops ===<br />
<br />
: The traditional Ctrl-Command-Command (Ctrl-Amiga-Amiga) keyboard combination doesn't work on laptops using the ADB interface for the keyboard, because ADB doesn't make difference between the left and right command keys. You can reboot them with an alternative Fn-Alt-Alt keyboard combination.<br />
<br />
<br />
=== Blackouts or Graphical Flickering on Mac mini ===<br />
<br />
: Mac minis suffer from short blackouts with some monitors when the connection is made with a DVI cable. The screen gets usually blanked for few seconds, and depending of the monitor it may happen more or less frequently. Issue may also show up as flickering lines on the screen and it may get worse and worse until the monitor is unable to sync to the signal anymore.<br />
<br />
: One option to get around it is to use a VGA adapter/cable, because it doesn't seem to happen with it.<br />
<br />
: An another option is to try to lower the pixel clock value for the used screenmode from the Monitors settings in the MorphOS preferences. If your default mode has for example vertical frequency of 75 Hz, going to 60 Hz mode may help. Sometimes even a small change can help, and lowering just couple clicks from 60 Hz does the trick.<br />
<br />
: This seems to be a common problem with Mac minis and "non-coherent" displays as discussed for example [https://discussions.apple.com/thread/2723110 here].<br />
<br />
<br />
=== Disabling the Internal Touchpad on Laptops ===<br />
==== From the Touchpad Settings (Preferred)====<br />
: An internal touchpad can be disabled from the MorphOS system settings nowadays, and this is the preferred method. Open '''System Settings -> Touchpad''' and disable the '''Enable the Touchpad driver''' setting.<br />
<br />
: [[File:MorphOS_Preferences_disabling_touchpad.png|200px]]<br />
<br />
==== From the USB Settings ====<br />
: The touchpad can be disabled temporarily by removing its binding in the USB settings. This setting is reverted back next time the machine is booted or if USB class scanning is done otherwise.<br />
<br />
: To remove the binding, open the USB settings from the MorphOS Preferences application and go to the Devices list.<br />
:* If you have "Apple Internal Trackpad" alone in the list, you can just select it and click the Unbind button.<br />
:: [[File:Disabling touchpad ibook.png|200px]]<br />
:* If your machine has a combined internal keyboard and trackpad device, double click it ("Apple Internal Keyboard / Trackpad"). Select Touchpad from the newly opened window and then click the Release Binding button.<br />
:: [[File:Disabling touchpad powerbook.png|200px]]<br />
<br />
==== Removing the Driver at Boot Time ====<br />
: Touchpad can also be disabled permanently by removing touchpad.library from use. Removing it is a bit tricky, because it resides in "ROM" and not as a file in system directories, but it can be done with the mf (module filter) boot command argument.<br />
<br />
: The boot command arguments can be edited by editing the bootinfo.txt file on Macs. The bootinfo.txt file is found on the Boot: partition, which also contains the boot.img file. If you don't see the partition, you probably need to mount it first by using, for example, the [[Tools/Mounter | Mounter]] tool. '''Note that if you edit the bootinfo.txt file, you must bless the file with the [[Shell_Commands/HFSSetMacBoot | HFSSetMacBoot]] command or the system won't be bootable anymore!'''<br />
<br />
: To add the mf argument, open the bootinfo.txt file with a text editor, find the line between <BOOT-SCRIPT> and </BOOT-SCRIPT> lines (it starts with "boot"), and add ''mf=touchpad.library'' at the end of the boot line. Save the file and '''remember to bless it with the ''HFSSetMacBoot Boot:bootinfo.txt'' command from the shell or your system won't boot again!'''<br />
<br />
<br />
=== MorphOS Boot Arguments on U-boot Systems ===<br />
: To boot into MorphOS, hardware has to load a MorphOS boot image file that contains the kernel and core drivers. The boot image file also accepts arguments to control the boot procedure before the actual operating system is loaded from the system partition. The boot arguments usage on [[Open Firmware]] systems is well [[Open_Firmware#Boot_Arguments | documented]], but they must be given in a different way on [http://www.intuitionbase.com/static.php?section=uboot U-boot] systems (Sam460ex/cr, AmigaOne X5000).<br />
<br />
: On the U-boot systems the boot arguments have to be set in the '''morphosargs''' environment variable in the U-boot console.<br />
<br />
: To check if you already have the variable set:<br />
: <tt>printenv morphosargs</tt><br />
<br />
: To set an argument (in this example we'd disable an unsupported SCSI controller by removing the SCSI driver from the boot image by using the ''module filter (mf)'' boot argument):<br />
: <tt>setenv morphosargs mf=symbios.device</tt><br />
: <tt>saveenv</tt><br />
<br />
: To edit an existing variable:<br />
: <tt>editenv morphosargs</tt><br />
: <tt>saveenv</tt><br />
<br />
<br />
=== FireWire Debugging ===<br />
<br />
: It's possible to transfer MorphOS debug logs to another computer via a FireWire connection. Please read [https://morph.zone/modules/newbb_plus/viewtopic.php?forum=11&topic_id=12759&post_id=143825&viewmode=flat&sortorder=0&showonepost=1 this post at MorphZone] for more information.</div>
JPV
https://library.morph.zone/index.php?title=Mounting_Network_Drives&diff=4349
Mounting Network Drives
2024-09-26T12:34:01Z
<p>JPV: </p>
<hr />
<div>== SmbFS ==<br />
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.<br />
<br />
'''Note that SmbFS works only with the obsoleted SMB1 protocol and isn't adviced to be used anymore. Please read the [https://library.morph.zone/Mounting_Network_Drives#Smb2FS Smb2FS] section for support for modern SMB2 and SMB3 protocols.'''<br />
<br />
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.<br />
<br />
Note that recent mainstream systems have started to drop support for older protocol versions on their default configurations, and you might need to enable the legacy support manually to get SmbFS connected to them.<br />
<br />
For example, on Windows 10 you might need to enable ''SMB 1.0/CIFS File Sharing Support'' options from the ''Turn Windows Features off and On'' settings in the Control Panel, and on Linux ''server min protocol = NT1'' and ''ntlm auth = yes'' lines may need to be added to the ''/etc/samba/smb.conf'' file.<br />
<br />
=== A simple example run from the Shell ===<br />
'''SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''<br />
Connected '//win7/sharedstuff' to 'Win7_share:'; "Break 5" or [Ctrl-C] to stop...<br />
<br />
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.<br />
<br />
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.<br />
<br />
The share can be unmounted by pressing ''CTRL C'' keyboard combination when started like this.<br />
<br />
<br />
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.<br />
: [[File:MorphOS_Preferences_Hosts.png|320px]]<br />
<br />
<br />
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.<br />
<br />
'''Run >NIL: SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''<br />
<br />
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.<br />
: [[File:NetworkDrives_SmbFS_Eject.png]]<br />
<br />
<br />
If you replace the PASSWORD option with the ASKPASSWORD option, you'll get a requester asking for the password.<br />
<br />
'''Run >NIL: SmbFS WORKGROUP=workgroup USER=MorphOS_Rulez ASKPASSWORD VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''<br />
: [[File:NetworkDrives_SmbFS_PW.png]]<br />
<br />
<br />
== Smb2FS ==<br />
While SmbFS works only with the SMB1 protocol, [[Shell_Commands/Smb2FS|Smb2FS]] works with SMB2 and SMB3 protocols. Smb2FS can be used with SmbFS's arguments, but it also supports the URL format:<br />
smb://[<domain;][<username>@]<host>[:<port>]/<share>/<path><br />
<br />
Since MorphOS 3.18 it's possible to browse and mount SMB2/3 shares directly from Ambient, which practically obsoletes the command-line usage of Smb2FS. Here's a [https://m.youtube.com/watch?v=YKmeI2aboUc demonstration video] of the Networks browsing and mounting.<br />
<br />
<br />
== Ssh2FS ==<br />
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.<br />
<br />
The ''SYS:MorphOS/Locale/Help/english/Ssh2FS.readme'' file contains a detailed description of all [[Shell_Commands/Ssh2FS|Ssh2FS]] the options.<br />
<br />
=== Requirements ===<br />
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/'').<br />
<br />
It is recommended to set the home directory in the MorphOS Preferences for easier use later on.<br />
# Create a new directory somewhere. ''SYS:Home'', for instance.<br />
# Set this directory to ''MorphOS Preferences -> Users -> Home Dir'' and save settings. A ''HOME:'' assign is created automatically to point into this directory.<br />
<br />
=== Examples ===<br />
Here are some examples to run from the Shell. '''Bold lines''' are what you need to type into the Shell.<br />
<br />
==== Mounting with the Password Prompt ====<br />
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.<br />
'''ssh2fs linuxuser@192.168.1.4 Linux: pw'''<br />
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3<br />
Host '192.168.1.4' is not known!<br />
Add host to known_hosts file ? (y/n)'''y'''<br />
Enter password:<br />
SFTP connection established.<br />
<br />
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:'').<br />
<br />
The previous example mounted the root directory of the server, but this would only mount your own home directory.<br />
'''ssh2fs linuxuser@192.168.1.4:/home/linuxuser Linux: pw'''<br />
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3<br />
Enter password:<br />
SFTP connection established.<br />
<br />
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.<br />
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pw'''<br />
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3<br />
Enter password:<br />
SFTP connection established.<br />
<br />
==== Passwordless Mounting ====<br />
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.<br />
# Set a hostname for your machine in ''MorphOS Preferences -> Network -> Host and DNS'' if not already set<br />
# 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).<br />
# 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/'''<br />
# 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):<br />
## Copy the file to the server, connect by an SSH client, execute ''cat id_rsa.pub >> ~/.ssh/authorized_keys''<br />
## 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'''<br />
<br />
Now you should be able to mount the server without encountering a password prompt with the ''pk'' argument:<br />
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''<br />
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3<br />
SFTP connection established.<br />
<br />
==== Mounting as a Background Process ====<br />
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 <br />
[[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.<br />
<br />
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.<br />
'''runfs Q C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''<br />
<br />
If you want to open a new Ambient window automatically for the newly mounted share, you can use the ''O=OPEN'' argument.<br />
'''runfs Q O C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''<br />
<br />
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.<br />
<br />
=== Unmounting ===<br />
As mentioned earlier, mounted Ssh2FS shares can be unmounted in several ways.<br />
* Use the Eject [[Screenbar_Modules|screenbar module]]<br />
* Use the [[Shell_Commands/UnMount|UnMount]] Shell command: ''UnMount VolumeName:''<br />
* 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.<br />
<br />
== NetFS Revised ==<br />
[http://aminet.net/package/comm/net/NetFS-revised NetFS Revised] allows 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.<br />
<br />
'''NOTE: There's an installer script provided with the latest version and no manual installation is required anymore. It also comes with graphical tools to create and mount shares.'''<br />
<br />
'''The manual installation procedure described below is also partly outdated for now. Please watch this [https://m.youtube.com/watch?v=SirKvJ03EnM video about NetFS Revised] if you need help using a recent version of the filesystem.<br />
'''<br />
<br />
Here's a step-by-step guide of how to install it manually on MorphOS.<br />
<br />
# Copy contents of the '''NetFS/SYS.MorphOS/''' directory to your '''SYS:''' partition<br />
# Copy '''NetFS/Prefs/Env-Archive/netfs-server.config''' to '''ENVARC:'''<br />
# (Optionally) Copy '''NetFS/Devs/DOSDrivers/ANETFS0''' to '''SYS:Storage/DOSDrivers/''' (if you want to mount a drive with a mountlist later)<br />
# (Optionally) Copy '''NetFS/Help/english/NetFS.guide''' to '''HELP:english/''' (to keep the documentation available)<br />
# Add '''amiganetfs 2500/tcp''', '''amiganetfs 2500/udp''', and '''amiganetfsprobe 2501/udp''' lines to the '''ENVARC:sys/net/services''' file.<br />[[File:NetworkDrives_NetFS1.png|480px]]<br />
# 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.<br />[[File:NetworkDrives_NetFS2.png|480px]]<br />
# 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.<br />[[File:NetworkDrives_NetFS3.png|480px]]<br />
# '''Reboot''' the machine before trying it out.<br />
<br />
<br />
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.<br />
<br />
'''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. <br />
: [[File:NetworkDrives_NetFS4.png|480px]]<br />
<br />
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.<br />
: [[File:NetworkDrives_NetFS5.png|480px]]<br />
<br />
So, let's try that again with the '''NetMount pb Work: NetFS0: LOGIN=morphos PASS=rulez''' command.<br />
: [[File:NetworkDrives_NetFS6.png|480px]]<br />
<br />
<br />
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.<br />
: [[File:NetworkDrives_NetFS7.png|480px]] [[File:NetworkDrives_NetFS8.png|480px]]<br />
<br />
<br />
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.<br />
<br />
<br />
== RDesktop ==<br />
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.<br />
<br />
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.<br />
: [[File:MorphOS3_jPV_Rdesktop.png|320px]] [[File:RDesktop_netdisk_mount.png|320px|top]]<br />
<br />
<br />
== Google Drive and Dropbox Handlers ==<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
: [[File:NetworkDrives_GoogleDrive1.png|320px]]<br />
<br />
<br />
== NFS ==<br />
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.<br />
<br />
Read more about it [https://amiga23.wordpress.com/2014/11/21/how-to-use-nfs-shares-on-morphos/ here].<br />
<br />
<br />
== FTPMount ==<br />
FTP sites can be mounted as part of a filesystem with the FTPMount program.<br />
<br />
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].<br />
<br />
<br />
== Samba ==<br />
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.<br />
<br />
<br />
== Other ==<br />
<br />
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.</div>
JPV
https://library.morph.zone/index.php?title=Mounting_Network_Drives&diff=4348
Mounting Network Drives
2024-09-26T12:28:29Z
<p>JPV: </p>
<hr />
<div>== SmbFS ==<br />
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.<br />
<br />
'''Note that SmbFS works only with the obsoleted SMB1 protocol and isn't adviced to be used anymore. Please read the [https://library.morph.zone/Mounting_Network_Drives#Smb2FS Smb2FS] section for support for modern SMB2 and SMB3 protocols.'''<br />
<br />
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.<br />
<br />
Note that recent mainstream systems have started to drop support for older protocol versions on their default configurations, and you might need to enable the legacy support manually to get SmbFS connected to them.<br />
<br />
For example, on Windows 10 you might need to enable ''SMB 1.0/CIFS File Sharing Support'' options from the ''Turn Windows Features off and On'' settings in the Control Panel, and on Linux ''server min protocol = NT1'' and ''ntlm auth = yes'' lines may need to be added to the ''/etc/samba/smb.conf'' file.<br />
<br />
=== A simple example run from the Shell ===<br />
'''SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''<br />
Connected '//win7/sharedstuff' to 'Win7_share:'; "Break 5" or [Ctrl-C] to stop...<br />
<br />
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.<br />
<br />
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.<br />
<br />
The share can be unmounted by pressing ''CTRL C'' keyboard combination when started like this.<br />
<br />
<br />
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.<br />
: [[File:MorphOS_Preferences_Hosts.png|320px]]<br />
<br />
<br />
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.<br />
<br />
'''Run >NIL: SmbFS WORKGROUP=workgroup USER=myusername PASSWORD=mypassword VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''<br />
<br />
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.<br />
: [[File:NetworkDrives_SmbFS_Eject.png]]<br />
<br />
<br />
If you replace the PASSWORD option with the ASKPASSWORD option, you'll get a requester asking for the password.<br />
<br />
'''Run >NIL: SmbFS WORKGROUP=workgroup USER=MorphOS_Rulez ASKPASSWORD VOLUME=Win7_share: SERVICE=//win7/sharedstuff'''<br />
: [[File:NetworkDrives_SmbFS_PW.png]]<br />
<br />
<br />
== Smb2FS ==<br />
While SmbFS works only with the SMB1 protocol, [[Shell_Commands/Smb2FS|Smb2FS]] works with SMB2 and SMB3 protocols. Smb2FS can be used with SmbFS's arguments, but it also supports the URL format:<br />
smb://[<domain;][<username>@]<host>[:<port>]/<share>/<path><br />
<br />
Since MorphOS 3.18 it's possible to browse and mount SMB2/3 shares directly from Ambient, which practically obsoletes the command-line usage of Smb2FS. Here's a [https://m.youtube.com/watch?v=YKmeI2aboUc demonstration video] of the Networks browsing and mounting.<br />
<br />
<br />
== Ssh2FS ==<br />
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.<br />
<br />
The ''SYS:MorphOS/Locale/Help/english/Ssh2FS.readme'' file contains a detailed description of all [[Shell_Commands/Ssh2FS|Ssh2FS]] the options.<br />
<br />
=== Requirements ===<br />
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/'').<br />
<br />
It is recommended to set the home directory in the MorphOS Preferences for easier use later on.<br />
# Create a new directory somewhere. ''SYS:Home'', for instance.<br />
# Set this directory to ''MorphOS Preferences -> Users -> Home Dir'' and save settings. A ''HOME:'' assign is created automatically to point into this directory.<br />
<br />
=== Examples ===<br />
Here are some examples to run from the Shell. '''Bold lines''' are what you need to type into the Shell.<br />
<br />
==== Mounting with the Password Prompt ====<br />
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.<br />
'''ssh2fs linuxuser@192.168.1.4 Linux: pw'''<br />
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3<br />
Host '192.168.1.4' is not known!<br />
Add host to known_hosts file ? (y/n)'''y'''<br />
Enter password:<br />
SFTP connection established.<br />
<br />
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:'').<br />
<br />
The previous example mounted the root directory of the server, but this would only mount your own home directory.<br />
'''ssh2fs linuxuser@192.168.1.4:/home/linuxuser Linux: pw'''<br />
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3<br />
Enter password:<br />
SFTP connection established.<br />
<br />
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.<br />
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pw'''<br />
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3<br />
Enter password:<br />
SFTP connection established.<br />
<br />
==== Passwordless Mounting ====<br />
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.<br />
# Set a hostname for your machine in ''MorphOS Preferences -> Network -> Host and DNS'' if not already set<br />
# 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).<br />
# 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/'''<br />
# 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):<br />
## Copy the file to the server, connect by an SSH client, execute ''cat id_rsa.pub >> ~/.ssh/authorized_keys''<br />
## 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'''<br />
<br />
Now you should be able to mount the server without encountering a password prompt with the ''pk'' argument:<br />
'''ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''<br />
Remote says: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3<br />
SFTP connection established.<br />
<br />
==== Mounting as a Background Process ====<br />
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 <br />
[[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.<br />
<br />
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.<br />
'''runfs Q C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''<br />
<br />
If you want to open a new Ambient window automatically for the newly mounted share, you can use the ''O=OPEN'' argument.<br />
'''runfs Q O C:ssh2fs linuxuser@linux4:/home/linuxuser Linux: pk'''<br />
<br />
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.<br />
<br />
=== Unmounting ===<br />
As mentioned earlier, mounted Ssh2FS shares can be unmounted in several ways.<br />
* Use the Eject [[Screenbar_Modules|screenbar module]]<br />
* Use the [[Shell_Commands/UnMount|UnMount]] Shell command: ''UnMount VolumeName:''<br />
* 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.<br />
<br />
== NetFS Revised ==<br />
[http://aminet.net/package/comm/net/NetFS-revised NetFS Revised] allows 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.<br />
<br />
'''NOTE: There's an installer script provided with the latest version and no manual installation is required anymore. The manual installation procedure described below is also partly outdated for now. Please watch this [https://m.youtube.com/watch?v=SirKvJ03EnM video about NetFS Revised] if you need help using a recent version of the filesystem.<br />
'''<br />
<br />
Here's a step-by-step guide of how to install it manually on MorphOS.<br />
<br />
# Copy contents of the '''NetFS/SYS.MorphOS/''' directory to your '''SYS:''' partition<br />
# Copy '''NetFS/Prefs/Env-Archive/netfs-server.config''' to '''ENVARC:'''<br />
# (Optionally) Copy '''NetFS/Devs/DOSDrivers/ANETFS0''' to '''SYS:Storage/DOSDrivers/''' (if you want to mount a drive with a mountlist later)<br />
# (Optionally) Copy '''NetFS/Help/english/NetFS.guide''' to '''HELP:english/''' (to keep the documentation available)<br />
# Add '''amiganetfs 2500/tcp''', '''amiganetfs 2500/udp''', and '''amiganetfsprobe 2501/udp''' lines to the '''ENVARC:sys/net/services''' file.<br />[[File:NetworkDrives_NetFS1.png|480px]]<br />
# 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.<br />[[File:NetworkDrives_NetFS2.png|480px]]<br />
# 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.<br />[[File:NetworkDrives_NetFS3.png|480px]]<br />
# '''Reboot''' the machine before trying it out.<br />
<br />
<br />
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.<br />
<br />
'''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. <br />
: [[File:NetworkDrives_NetFS4.png|480px]]<br />
<br />
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.<br />
: [[File:NetworkDrives_NetFS5.png|480px]]<br />
<br />
So, let's try that again with the '''NetMount pb Work: NetFS0: LOGIN=morphos PASS=rulez''' command.<br />
: [[File:NetworkDrives_NetFS6.png|480px]]<br />
<br />
<br />
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.<br />
: [[File:NetworkDrives_NetFS7.png|480px]] [[File:NetworkDrives_NetFS8.png|480px]]<br />
<br />
<br />
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.<br />
<br />
<br />
== RDesktop ==<br />
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.<br />
<br />
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.<br />
: [[File:MorphOS3_jPV_Rdesktop.png|320px]] [[File:RDesktop_netdisk_mount.png|320px|top]]<br />
<br />
<br />
== Google Drive and Dropbox Handlers ==<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
: [[File:NetworkDrives_GoogleDrive1.png|320px]]<br />
<br />
<br />
== NFS ==<br />
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.<br />
<br />
Read more about it [https://amiga23.wordpress.com/2014/11/21/how-to-use-nfs-shares-on-morphos/ here].<br />
<br />
<br />
== FTPMount ==<br />
FTP sites can be mounted as part of a filesystem with the FTPMount program.<br />
<br />
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].<br />
<br />
<br />
== Samba ==<br />
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.<br />
<br />
<br />
== Other ==<br />
<br />
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.</div>
JPV
https://library.morph.zone/index.php?title=Shell_Commands/FileWrite&diff=4345
Shell Commands/FileWrite
2024-07-19T20:49:51Z
<p>JPV: </p>
<hr />
<div>'''FileWrite''' - Writes data to a file<br />
<br />
FILE/A, SIZE/N/A, DATA/N, STRING, ADD/S<br />
<nowiki><br />
FILE - Filename to write data to<br />
SIZE - Amount of data in bytes to be written<br />
DATA - Data to be written in hex<br />
STRING - Data in the string format<br />
ADD - Adds data to an existing file instead of creating a new file<br />
</nowiki><br />
If the length of data is shorter than the size value, the file is filled by repeating the data contents. Strings get separated by null bytes then. Data entered in decimals gets converted to hex. If no data is given, the file is filled with null bytes.<br />
<br />
Examples:<br />
<nowiki><br />
Ram Disk:> FileWrite test 8 0x4d4f5321<br />
Ram Disk:> Type test HEX<br />
0000: 4D4F5321 4D4F5321 MOS!MOS!<br />
<br />
Ram Disk:> FileWrite test 32 STRING MorphOS<br />
Ram Disk:> Type test HEX<br />
0000: 4D6F7270 684F5300 4D6F7270 684F5300 MorphOS.MorphOS.<br />
0010: 4D6F7270 684F5300 4D6F7270 684F5300 MorphOS.MorphOS.<br />
<br />
Ram Disk:> FileWrite test 4 STRING MorphOS<br />
Ram Disk:> Type test HEX<br />
0000: 4D6F7270 Morp<br />
<br />
Ram Disk:> FileWrite test 4 STRING MorphOS ADD<br />
Ram Disk:> Type test HEX<br />
0000: 4D6F7270 4D6F7270 MorpMorp<br />
</nowiki><br />
<br />
To create an empty ADF image (which can then be mounted with [[Tools/FileImageCtrl]] and formatted with [[Tools/Format]] under MorphOS, or just be used in an Amiga emulator):<br />
<nowiki><br />
Ram Disk:> FileWrite empty.adf 901120<br />
</nowiki><br />
<br />
And similarly, creating an empty HDF image (100 megabytes in this case):<br />
<nowiki><br />
Ram Disk: FileWrite harddisk.hdf `eval 100*1024*1024`<br />
</nowiki></div>
JPV
https://library.morph.zone/index.php?title=Print_System&diff=4339
Print System
2024-05-24T06:50:25Z
<p>JPV: </p>
<hr />
<div>New printer system has been introduced in MorphOS 3.10 and extended in MorphOS 3.12. <br />
It is based on CUPS logic although it does not contain any CUPS code in its core. <br />
Drivers are represented using PPD [https://en.wikipedia.org/wiki/PostScript_Printer_Description (PostScript Printer Description)] files, which support both Postscript and non-Postscript printers. Previously Postscript printers could be used in MorphOS directly sending raw Postscript stream to the printer. It doesn't allow to set any settings and only Pagestream has decent settings for that. <br />
<br />
== Drivers == <br />
<br />
New preferences has been created to handle drivers and profiles. Driver is a binary form of PPD textual file. Profile is a driver which includes settings set by the user. <br />
[[File:Printers1.png|frameless|center|700px]]<br />
<br />
To have printer connected one has to provide PPD driver. Some of printers including EPSON ESC/PR and Samsung CLPs can be automatically found and driver will be added using '''Search driver''' button. If not please use '''Add...''' button to select PPD file. PPD files for Postscript printers will be added and they are ready to work. PPD files for other printers (PCL/SPL/ESCPR) contain reference to filter file (actual driver which translates data to printer binary format). If PPD file with filter not available in MorphOS is provided user will be asked what to do.<br />
[[File:Printers2.png|frameless|center|700px]]<br />
<br />
== Profiles == <br />
<br />
After adding the driver profile needs to be created. Please select Add... button. A window with driver selection will appear. User can create many profiles for one driver: one for color printing, one for b/w, etc.<br />
[[File:Printers3.png|frameless|center|700px]]<br />
After creating the profile you can make it as default and set the output path. Both file and device output is supported. So for printing to file you can set RAM:output_print. For network printing please use NETPAR: and for usb printers please use USBPAR:. A corresponding mountlist (USBPAR or NETPAR) needs to be copied from Storage/DosDrivers to the DEVS:DosDrivers, or add ''mount USBPAR:'' or ''mount NETPAR:'' somewhere in the S:user-startup file.<br />
<br />
[[File:Printers4.png|frameless|center|700px]]<br />
<br />
Under '''Options''' button printer options can be set for the profile. Each printer driver has own set of options. <br />
[[File:Printers5.png|frameless|center|700px]]<br />
<br />
== Current Applications ==<br />
<br />
The main application which makes use of the new printing system is VPDF - PDF files viewer from Application directory. When selecting Postscript option in Print window, a Profile selector is available where you can select between profiles defined earlier in Printers preferences. You can also use (To file) to get raw Postscript output.<br />
[[File:Printers7.png|frameless|center|700px]]<br />
<br />
<br />
== Printer.device support ==<br />
printer.device/TurboPrint like printing from old applications is not yet supported, although VPDF prints using TurboPrint when Postscript option is not active. <br />
<br />
<br />
<br />
== Printer-handler usage ==<br />
<br />
To get printing supported in any application (with Postscript support) please use <br />
PRINTER: device for storing Postscript output. printer-handler which control the PRINTER: device has such options:<br />
* PROFILE/K - name of the profile, get default profile from Printers preferences when not set<br />
* ARGS/K - CUPS compatible option set<br />
* FORMAT/K - defaults to PS for now<br />
* COPIES/N - how many copies should be printed<br />
<br />
When PRINTER: device is used it preformats raw Postscript output from application adding additional parameters set in Printers preferences and for example make multipage per sheet printing which is not available in raw printing. For non-Postscript printers internal Ghostscript 8.70 processing is done. This can take some seconds so Postscript printers are preffered.<br />
<br />
Shell Example:<br />
<br />
<code>copy FROM RAM:example.ps TO "PRINTER:profile='HP Color 6' ARGS=' ' COPIES=1 FORMAT=PS"</code><br />
<br />
== My printer does not work ==<br />
* Check connection (USB) in Poseidon or Netprinter (Network) <br />
* Check if your Postscript printer has correct PPD file provided. In most cases Postscript printers has also additional PPD drivers which use various filters (for example Postscript printer with PCL5 support may have also PPD file with PCL5 filter). PPD files just for Postscript printing are preffered.<br />
* Check free memory. Printing uses Ghostscript sometimes for converting the data and stores some temportary files in T: device. It may not work in low memory situations. You may use PRINTER_TEMPDIR environment variable to set the dir for storing temporary files although setting it to the disk will slow down printing process.<br />
* Printer is not supported by the current drivers.</div>
JPV
https://library.morph.zone/index.php?title=Hardware_Compatibility&diff=4338
Hardware Compatibility
2024-05-13T14:33:20Z
<p>JPV: /* Printers */</p>
<hr />
<div><div id="hardwareCompatibility"><br />
<br />
== Official Information ==<br />
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]].<br />
<br />
== User Provided Reports ==<br />
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.<br />
<br />
'''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. <br />
<br />
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.<br />
<br />
=== Game Controllers ===<br />
<table style="width:100%"><br />
<tr><th class="type">USB Device</th><th class="driver">USB driver</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>8bitdo SFC30 Pro Controller</td><td>hid</td><td>3.11</td></tr><br />
<tr><td>8bitdo SN30 Pro Controller</td><td>hid, xbox360</td><td>3.11</td><td>wired</td></tr><br />
<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><br />
<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><br />
<tr><td>Logitech Rumble Pad wired (USB2)</td><td>hid</td><td>3.11</td></tr><br />
<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><br />
<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><br />
<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><br />
<tr><td>Saitek P380 Dual Analog wired (USB2)</td><td>hid</td><td>3.11</td></tr><br />
<tr><td style="color:red;">Sony Dualshock 3 (PS3)</td><td>-</td><td>-</td><td>not supported</td></tr><br />
<tr><td>Sony Dualshock 4 (PS4)</td><td>xbox360</td><td>3.10</td></tr><br />
<tr><td>Speedlink Competition Pro USB</td><td>hid</td><td>3.11</td></tr><br />
<tr><td>Speedlink Xeox Gamepad</td><td>hid</td><td>3.11</td></tr><br />
<tr><td>[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)</td><td>hid</td><td>3.15</td></tr><br />
<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><br />
<tr><td>Xbox 360 wired and wireless pads</td><td>xbox360</td><td>3.11</td><td>wireless supported via PC adapter</td></tr><br />
<tr><td>Xbox One gamepad</td><td>xbox360</td><td>3.11</td><td>wired only</td></tr><br />
<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><br />
</table><br />
<br />
=== Keyboards ===<br />
<table style="width:100%;"><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>Apple A1016 Wireless BlueTooth</td><td>3.10</td><td>①</td></tr><br />
<tr><td>Apple Magic Keyboard (Version 1)</td><td>3.13</td><td>①</td></tr><br />
<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><br />
<tr><td>Ducky Zero Keyboard DK2108SZ</td><td>3.10</td><td></td></tr><br />
<tr><td>IBM SK-8815 Corded USB Keyboard</td><td>3.15</td><td></td></tr><br />
<tr><td>Logitech UltraX Premium</td><td>3.10</td><td></td></tr><br />
<tr><td>Microsoft Wired Keyboard 600</td><td>3.13</td><td>Model X880609-600</td></tr><br />
<tr><td>Microsoft Wireless 900 Keyboard</td><td>3.13</td><td>Mouse+kb combo</td></tr><br />
<tr><td>Rapoo E6300 Ultra-Slim BT keyboard for iPad</td><td>3.11</td><td>①</td></tr><br />
<tr><td>Rapoo E9050 Wireless Compact Ultra-Slim Keyboard</td><td>3.11</td><td></td></tr><br />
<tr><td>Rapoo E2710 Wireless Nano-USB Keyboard</td><td>3.11</td><td></td></tr><br />
<tr><td>Xenta Super Compact Black Wired Keyboard (RK 107)</td><td>3.13</td><td></td></tr><br />
</table><br />
① requires a machine which supports paired BT input devices, like Mac mini<br />
<br />
=== Mice ===<br />
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>A-Eon Technology MX-1000-1</td><td>3.13</td><td></td></tr><br />
<tr><td>Dacota Gaming Serpent Mouse</td><td>3.15</td><td>Wired, 809024</td></tr><br />
<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><br />
<tr><td>Logitech M180</td><td>3.11</td><td></td></tr><br />
<tr><td>Logitech M185</td><td>3.10</td><td></td></tr><br />
<tr><td>Logitech M190</td><td>3.15</td><td></td></tr><br />
<tr><td>Logitech M220 Silent</td><td>3.15</td><td></td></tr><br />
<tr><td>Logitech M330 Silent</td><td>3.14</td><td></td></tr><br />
<tr><td>Logitech T-RB22 Wireless Trackball</td><td>3.11</td><td></td></tr><br />
<tr><td>Logitech G203</td><td>3.10</td><td>No software control over RGB, DPI</td></tr><br />
<tr><td>Labtec Optical Mouse 800</td><td>3.10</td><td></td></tr><br />
<tr><td>Microsoft Compact Optical Mouse 500</td><td>3.14</td><td></td></tr><br />
<tr><td>Microsoft Trackball Explorer v1.0</td><td>3.11</td><td>PS2>USB adapter required</td></tr><br />
<tr><td>Microsoft Wireless Mouse 900</td><td>3.14</td><td>Mouse+kb combo</td></tr><br />
<tr><td style="color:red;">Microsoft Wireless Mouse 4000</td><td>3.13</td><td>Not working</td></tr><br />
<tr><td>Razer Viper Mini</td><td>3.15</td><td>No software control over RGB, DPI</td></tr><br />
<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><br />
<tr><td>Targus AMU3102EU</td><td>3.10</td><td></td></tr><br />
<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><br />
</table><br />
<br />
=== MIDI Devices ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard</td><td>3.13</td><td></td></tr><br />
<tr><td>[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard</td><td>3.13</td><td></td></tr><br />
<tr><td>Yamaha PSR-433 keyboard</td><td>3.14</td><td></td></tr><br />
</table><br />
<br />
=== Networking ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>TL-WR702N Nano Router</td><td></td><td></td></tr><br />
<tr><td>TL-WR802N Nano Router</td><td></td><td></td></tr><br />
</table><br />
<br />
=== Printers ===<br />
<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><br />
<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><br />
<tr><td>Konica Minolta Magicolor 4650</td><td>3.11</td><td></td><td>M4650PX.ppd</td><td></td></tr><br />
<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><br />
<tr><td>Xerox 3225 Workcentre</td><td>3.11</td><td></td><td></td><td>Reported to work with PS</td></tr><br />
<tr><td>HP Color LaserJet MFP M274n</td><td>3.15</td><td></td><td>hp-color_laserjet_mfp_m274-ps.ppd</td></tr><br />
<tr><td>Xerox B230</td><td>3.18</td><td>HP_LaserJet5series</td><td>[https://www.support.xerox.com/en-mu/product/xerox-b230-printer/content/152267 PPD at support page]</td><td>B225 & B235 should work too, maybe also C230 & C235</td></tr><br />
</table><br />
<br />
=== Scanners ===<br />
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>Epson Perfection 1640SU</td><td>3.11</td><td>Including recent support for its ADF (Automatic Document Feeder).</td></tr><br />
</table><br />
<br />
=== Storage ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<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><br />
</table><br />
<br />
=== USB Audio Devices ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th>Output</th><th>Input</th><th class="comments">Comments</th></tr><br />
<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><br />
<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><br />
<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><br />
<tr><td>C-Media soundcard</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr><br />
<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><br />
<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><br />
<tr><td>FX-Audio- DAC-X3</td><td>3.12</td><td>OK</td><td>N/A</td><td></td></tr><br />
<tr><td>Griffin iMic</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr><br />
<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><br />
<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><br />
<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><br />
<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><br />
<tr><td>Steelseries Arctis 7 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr><br />
<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><br />
<tr><td>Turtle Beach Stealth 520 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr><br />
</table><br />
<br />
</div></div>
JPV
https://library.morph.zone/index.php?title=Hardware_Compatibility&diff=4337
Hardware Compatibility
2024-05-13T14:31:54Z
<p>JPV: /* Printers */</p>
<hr />
<div><div id="hardwareCompatibility"><br />
<br />
== Official Information ==<br />
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]].<br />
<br />
== User Provided Reports ==<br />
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.<br />
<br />
'''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. <br />
<br />
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.<br />
<br />
=== Game Controllers ===<br />
<table style="width:100%"><br />
<tr><th class="type">USB Device</th><th class="driver">USB driver</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>8bitdo SFC30 Pro Controller</td><td>hid</td><td>3.11</td></tr><br />
<tr><td>8bitdo SN30 Pro Controller</td><td>hid, xbox360</td><td>3.11</td><td>wired</td></tr><br />
<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><br />
<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><br />
<tr><td>Logitech Rumble Pad wired (USB2)</td><td>hid</td><td>3.11</td></tr><br />
<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><br />
<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><br />
<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><br />
<tr><td>Saitek P380 Dual Analog wired (USB2)</td><td>hid</td><td>3.11</td></tr><br />
<tr><td style="color:red;">Sony Dualshock 3 (PS3)</td><td>-</td><td>-</td><td>not supported</td></tr><br />
<tr><td>Sony Dualshock 4 (PS4)</td><td>xbox360</td><td>3.10</td></tr><br />
<tr><td>Speedlink Competition Pro USB</td><td>hid</td><td>3.11</td></tr><br />
<tr><td>Speedlink Xeox Gamepad</td><td>hid</td><td>3.11</td></tr><br />
<tr><td>[https://tgsjoystick.wordpress.com/ The Greek Stick] (T.G.S.)</td><td>hid</td><td>3.15</td></tr><br />
<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><br />
<tr><td>Xbox 360 wired and wireless pads</td><td>xbox360</td><td>3.11</td><td>wireless supported via PC adapter</td></tr><br />
<tr><td>Xbox One gamepad</td><td>xbox360</td><td>3.11</td><td>wired only</td></tr><br />
<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><br />
</table><br />
<br />
=== Keyboards ===<br />
<table style="width:100%;"><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>Apple A1016 Wireless BlueTooth</td><td>3.10</td><td>①</td></tr><br />
<tr><td>Apple Magic Keyboard (Version 1)</td><td>3.13</td><td>①</td></tr><br />
<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><br />
<tr><td>Ducky Zero Keyboard DK2108SZ</td><td>3.10</td><td></td></tr><br />
<tr><td>IBM SK-8815 Corded USB Keyboard</td><td>3.15</td><td></td></tr><br />
<tr><td>Logitech UltraX Premium</td><td>3.10</td><td></td></tr><br />
<tr><td>Microsoft Wired Keyboard 600</td><td>3.13</td><td>Model X880609-600</td></tr><br />
<tr><td>Microsoft Wireless 900 Keyboard</td><td>3.13</td><td>Mouse+kb combo</td></tr><br />
<tr><td>Rapoo E6300 Ultra-Slim BT keyboard for iPad</td><td>3.11</td><td>①</td></tr><br />
<tr><td>Rapoo E9050 Wireless Compact Ultra-Slim Keyboard</td><td>3.11</td><td></td></tr><br />
<tr><td>Rapoo E2710 Wireless Nano-USB Keyboard</td><td>3.11</td><td></td></tr><br />
<tr><td>Xenta Super Compact Black Wired Keyboard (RK 107)</td><td>3.13</td><td></td></tr><br />
</table><br />
① requires a machine which supports paired BT input devices, like Mac mini<br />
<br />
=== Mice ===<br />
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>A-Eon Technology MX-1000-1</td><td>3.13</td><td></td></tr><br />
<tr><td>Dacota Gaming Serpent Mouse</td><td>3.15</td><td>Wired, 809024</td></tr><br />
<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><br />
<tr><td>Logitech M180</td><td>3.11</td><td></td></tr><br />
<tr><td>Logitech M185</td><td>3.10</td><td></td></tr><br />
<tr><td>Logitech M190</td><td>3.15</td><td></td></tr><br />
<tr><td>Logitech M220 Silent</td><td>3.15</td><td></td></tr><br />
<tr><td>Logitech M330 Silent</td><td>3.14</td><td></td></tr><br />
<tr><td>Logitech T-RB22 Wireless Trackball</td><td>3.11</td><td></td></tr><br />
<tr><td>Logitech G203</td><td>3.10</td><td>No software control over RGB, DPI</td></tr><br />
<tr><td>Labtec Optical Mouse 800</td><td>3.10</td><td></td></tr><br />
<tr><td>Microsoft Compact Optical Mouse 500</td><td>3.14</td><td></td></tr><br />
<tr><td>Microsoft Trackball Explorer v1.0</td><td>3.11</td><td>PS2>USB adapter required</td></tr><br />
<tr><td>Microsoft Wireless Mouse 900</td><td>3.14</td><td>Mouse+kb combo</td></tr><br />
<tr><td style="color:red;">Microsoft Wireless Mouse 4000</td><td>3.13</td><td>Not working</td></tr><br />
<tr><td>Razer Viper Mini</td><td>3.15</td><td>No software control over RGB, DPI</td></tr><br />
<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><br />
<tr><td>Targus AMU3102EU</td><td>3.10</td><td></td></tr><br />
<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><br />
</table><br />
<br />
=== MIDI Devices ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>[https://www.alesis.com/products/legacy/vi25 Alesis VI25] keyboard</td><td>3.13</td><td></td></tr><br />
<tr><td>[https://www.korg.com/us/products/computergear/nanokey2/ Korg nanoKEY2] keyboard</td><td>3.13</td><td></td></tr><br />
<tr><td>Yamaha PSR-433 keyboard</td><td>3.14</td><td></td></tr><br />
</table><br />
<br />
=== Networking ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>TL-WR702N Nano Router</td><td></td><td></td></tr><br />
<tr><td>TL-WR802N Nano Router</td><td></td><td></td></tr><br />
</table><br />
<br />
=== Printers ===<br />
<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><br />
<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><br />
<tr><td>Konica Minolta Magicolor 4650</td><td>3.11</td><td></td><td>M4650PX.ppd</td><td></td></tr><br />
<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><br />
<tr><td>Xerox 3225 Workcentre</td><td>3.11</td><td></td><td></td><td>Reported to work with PS</td></tr><br />
<tr><td>HP Color LaserJet MFP M274n</td><td>3.15</td><td></td><td>hp-color_laserjet_mfp_m274-ps.ppd</td></tr><br />
<tr><td>Xerox B230</td><td>3.18</td><td>HP_LaserJet5series</td><td>[https://www.support.xerox.com/en-mu/product/xerox-b230-printer/content/152267 Xerox_B225_B230_B235_5.810.0.0_PPD.zip]</td><td>B225 & B235 should work too, maybe also C230 & C235</td></tr><br />
</table><br />
<br />
=== Scanners ===<br />
<table><tr><th>Model</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<tr><td>Epson Perfection 1640SU</td><td>3.11</td><td>Including recent support for its ADF (Automatic Document Feeder).</td></tr><br />
</table><br />
<br />
=== Storage ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th class="comments">Comments</th></tr><br />
<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><br />
</table><br />
<br />
=== USB Audio Devices ===<br />
<table><tr><th>Device</th><th class="os">OS</th><th>Output</th><th>Input</th><th class="comments">Comments</th></tr><br />
<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><br />
<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><br />
<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><br />
<tr><td>C-Media soundcard</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr><br />
<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><br />
<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><br />
<tr><td>FX-Audio- DAC-X3</td><td>3.12</td><td>OK</td><td>N/A</td><td></td></tr><br />
<tr><td>Griffin iMic</td><td>3.11</td><td>OK</td><td>Untested</td><td>Distorted output</td></tr><br />
<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><br />
<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><br />
<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><br />
<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><br />
<tr><td>Steelseries Arctis 7 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr><br />
<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><br />
<tr><td>Turtle Beach Stealth 520 headset</td><td>3.13</td><td>OK</td><td>No</td><td></td></tr><br />
</table><br />
<br />
</div></div>
JPV
https://library.morph.zone/index.php?title=Applications/ShowCase&diff=4330
Applications/ShowCase
2024-02-08T11:00:03Z
<p>JPV: /* Description */</p>
<hr />
<div>== Description ==<br />
<br />
Powerful image viewer incorporating processing, editing and conversion tools. Support for a wide range of image file formats (via datatypes). <br />
<br />
*Easy browsing of directories (with mouse and keyboard)<br />
*Lots of supported file formats thanks to Datatypes system<br />
*Nice Magic User Interface GUI<br />
*Image processing options like resizing, color balance, smoothing, sharpening, cropping, glowing, noise reduction etc.<br />
*Saving of images in JPEG (with preview), PNG, TGA, TIFF or IFF<br />
*Loading/displaying images with alpha channel<br />
*Scaling image display to fit in the window (user controllable)<br />
*Scrolling/zooming of big images<br />
*Optional bilinear filtering of the displayed image<br />
*Drag&drop of files/directories to be displayed<br />
*DOS notifications support (refreshing of list of files when new files are copied in/ removed)<br />
*Thumbnails generator (with templates)<br />
*Lossless JPEG transformations (for photos from digital camera from example)<br />
*Automatic rotation of images taken from digital cameras (if camera provides needed informations).<br />
*2 directory browsing methods. Using "simple" list or list of thumbnails (miniature of image)<br />
*Thumbnails browser optimized for viewing pictures taken with digicam (very fast thumbnail creation)<br />
*Opus Magellan-like quick search function<br />
*Simple file management functions like copy, move, rename, delete<br />
*Text inserting function<br />
*Color picker<br />
*ARexx interface<br />
*3D View and slideshow for more eye candy<br />
*Displaying of EXIF information stored in images.<br />
*Image clipboard to ease file operations on images.<br />
*Slideshow<br />
*Batch processor<br />
*Image cataloging<br />
*Searching functionality<br />
<br />
== Usage ==<br />
<br />
<br />
<br />
== Screenshots ==<br />
: [[File:Review_jpv_Showgirls.png|640px]]<br />
: [[File:ShowGirls_Menus1.png|320px]] [[File:ShowGirls_Menus2.png|320px]] [[File:ShowGirls_Menus3.png|320px]] [[File:ShowGirls_Menus4.png|320px]] [[File:ShowGirls_Menus5.png|320px]]</div>
JPV
https://library.morph.zone/index.php?title=Tips_and_Tricks&diff=4327
Tips and Tricks
2023-11-27T07:07:12Z
<p>JPV: </p>
<hr />
<div>''Originally published at: http://jpv.wmhost.com/morphos/tips/''<br />
<br />
Miscellaneous tips and tricks for MorphOS use. Some may even be hackish and not officially encouraged by MorphOS Team. Everyone is welcome to make additions and corrections here.<br />
== Basic Features ==<br />
<br />
=== Modifying the System Directory ===<br />
: Tip #1: NEVER modify anything in the MOSSYS: (SYS:MorphOS/) path! All changes are lost in a system upgrade. If you need to add any 3rd party drivers or libraries, add them to SYS:. If there isn't a correct directory by default, make one.<br />
<br />
: There's only one exception (of course there is one) to this: you can rename MOSSYS:Libs/rexxsyslib.library to MOSSYS:Libs/rexxsyslib.library_disabled when you copy a 68k version of rexxsyslib.library to SYS:Libs/ in order to get the ARexx environment working.<br />
<br />
<br />
=== Keyboard Commands ===<br />
<br />
: At first, check the default ones and define your favourites in '''System Settings -> IControl -> Hotkeys''' and in '''Ambient Settings -> Keyboard'''.<br />
<br />
: For example IControl has "Active Window: Activate Next" and "All Windows: Depth Menu" options, which can be used to achieve alt/ctrl/command-tab style window cycling functionality familiar from other operating systems.<br />
<br />
: Other keys: <br />
:* To zoom Ambient icons in the icon mode: keep CTRL pressed and use the mouse wheel or just roll the wheel over the Viewmode button.<br />
:* To find and select files in Ambient windows by letters: start typing a name when the window is active. Keep the Shift key pressed for directories. <br />
:* To enter a path manually (for example for hidden dirs like .recycled): press the / key in an Ambient window and type in the path. <br />
:* Command-f activates the find function in most programs. <br />
:* The r key rotates the pictures in Ambient's internal viewer and Page Up/Down keys select previous and next images in a dir <br />
:* Check keyboard commands of the Shell, like by default, commands can be completed with CTRL-tab, devices with ALT-tab, history with shift-tab etc. <br />
:* Keeping the Alt key pressed while double clicking a drawer gives you different ways to open drawers.<br />
:* Keeping the Alt key pressed while dragging files on the same partition copies files instead of moving, or vice versa depending on your Ambient settings.<br />
<br />
=== Enabling/Disabling Icon Tooltypes ===<br />
<br />
: Double click single tooltypes to enable and disable them in the icon information window.<br />
<br />
<br />
=== Browsing History in Ambient ===<br />
<br />
: Clicking the parent button ([[File:Tips_Parent.png|middle]]) on an Ambient window (in browser mode) with the right mouse button gives you a browsing history popup menu for quick jumping between locations.<br />
<br />
<br />
=== Sync the Clock from Internet at Boot ===<br />
<br />
: Add this line to S:user-network-startup file:<br />
: <tt>Run DETACH MOSSYS:C/SetClockNTP SAVE</tt><br />
<br />
<br />
=== Redirecting AHI Music Unit ===<br />
<br />
: You can select Unit 0 as the Music Unit in AHI to be able hear audio output from multiple programs at the same time, with a slight decrease in quality.<br />
<br />
: [[File:MorphOS_System_settings_Music_Unit.png|280px]]<br />
<br />
<br />
=== Keeping AHI Audio Quality Better ===<br />
<br />
: Audio quality with AHI will be better if you reduce available channels for its shared modes (Unit 0 usually). Available channels will limit the amount of simultaneus playback of sounds, but you really don't need the default 32 channels and even two channels can be quite enough. Should there be more concurrent sounds, some of them just get muted until the other have been finished.<br />
<br />
: [[File:MorphOS_System_settings_Change_Unit.png|280px]] [[File:MorphOS_System_settings_Unit_0.png|280px]]<br />
<br />
<br />
=== Mime Type Configuration ===<br />
<br />
: Learn to configure mime types from the Ambient settings. It really gives so much for your system and your user experience. [http://jpv.wmhost.com/pics/mimemplayer.png Here] is one example of how to configure MPlayer for all the video files.<br />
<br />
<br />
=== Inline Editing ===<br />
<br />
: Inline editing is a quick way to edit filenames by clicking them with the mouse wheel or with the long left mouse click. Its behaviour can be configured from the Lister settings in Ambient Settings.<br />
<br />
: File comments can also be edited with the inline editing.<br />
<br />
: [[File:Tips_Inlineedit.png|280px]]<br />
<br />
<br />
=== Batch Renaming in Ambient ===<br />
<br />
# Select files you want to be in the range of renaming.<br />
# Hit rename button or command-r keyboard shortcut.<br />
# Use pattern to rename. For example renaming all files which begin with "mod." to files which end with ".mod", use "mod.*" as source and "*.mod" as destination (quotation marks not needed).<br />
<br />
<br />
=== Don't Forget RMB/Long-LMB Gadget Menus ===<br />
<br />
: You get menus from zoom and depth gadgets with right mouse button or by holding left mouse button pressed on them.<br />
<br />
: [[File:Tips_Zoommenu.png]] [[File:Tips_Windowdepthmenu.png]] [[File:Tips_Screendepthmenu.png]]<br />
<br />
<br />
=== How to Use RMB with One-button Mouse ===<br />
<br />
: The right mouse button can be emulated in several different ways:<br />
:* The '''System Settings -> Mouse -> Open menus by clicking...''' setting lets your mouse button act as the right mouse button if you hold a qualifier key pressed while clicking. The qualifier key can be configured for your preferences, but it's the shift key by default.<br />
:* Press right alt and right command keys together. This probably doesn't work on systems with ADB keyboard, like on older Mac laptops. The ADB keyboard doesn't make difference between left and right keys.<br />
:* With non-ADB laptops (PowerBook 5,6-5,9 and 6,7 (iBook)) you can also use two finger tap or two finger hold + button combination on the touchpad for RMB.<br />
:* You can define a hotkey for menu launching on the IControl preferences (the default one is rcommand+space). It doesn't work exactly as the RMB everywhere, but works if you're mostly using the RMB for menus.<br />
:* A multi button USB mouse works always!<br />
<br />
<br />
=== Starting Programs Iconified ===<br />
<br />
: MUI has an option to start programs in iconified mode. It's useful for example for programs like Synergy, which you'd like to start on background without their main window jumping up. The option can be found from program's MUI Settings (Windows -> Iconify on startup).<br />
<br />
: [[File:Tips_Iconify.png]]<br />
<br />
<br />
=== Checking the Debug Log ===<br />
<br />
: If you want a stable system, you need to check the debug log periodically to see if any program misbehaves when used, especially when running new software.<br />
<br />
: An easy way to do it is to enable Debug screenbar module from the screen depth gadget menu. Bug looking Debug button on the screenbar will then give you a debug menu where you can view the log etc. If "Show Log..." option is ghosted, there's nothing in the log and everything is fine, but if it shows hundreds of cryptic lines (it's called a hit), then you have something to worry and the system probably isn't stable anymore. Some programs may output their own harmless debug information to the log too, but it's usually limited to few or tens of lines maximum. You'll recognize a real hit for sure.<br />
<br />
: [[File:Tips_Debug1.png|x64px]] [[File:Tips_Debug2.png|x64px]]<br />
<br />
<br />
=== Printing to a PostScript Compatible Network Printer ===<br />
<br />
: You should mount the NETPAR: device and print to that device from programs like VPDF and OWB, which can output PostScript. NETPAR: is faster than printing through Turboprint (PRT:) and doesn't need Ghostscript installed (PS:).<br />
<br />
: "Mount NETPAR:" can be added to S:user-startup, for example.<br />
<br />
<br />
=== .recycled Directory ===<br />
<br />
: SFS is the default filesystem on MorphOS. It can have a special directory which contains recently deleted files. The directory is named as .recycled and it resides at the root level of every SFS partition (SYS:.recycled for example). Depending the format options it may be disabled, hidden but accessible, or visible.<br />
<br />
: If it's hidden, you can't see it even with "View All Files" option, but you can access it from the shell or Ambient (for example by pressing / key and then writing it to the path string after the volume name).<br />
<br />
: You shouldn't modify any files in it, but you can recover deleted files by copying them to some other path.<br />
<br />
: The PFS3 filesystem has a similar directory, but its name is ".deldir".<br />
<br />
<br />
=== How to Reduce Graphics Memory Usage ===<br />
<br />
: MorphOS can use graphics memory quite extensively which can cause slowdowns or glitches if you run out of it. It usually isn't an issue if you have 64MB or more graphics memory, but lower spec systems with today's resolutions may need some tuning. There are several ways to reduce memory usage and you have to decide or try which is the best for you.<br />
<br />
: MorphOS has an "Enhanced Display" mode, which uses the graphics card's 3D functions to draw graphic layers. It consumes more memory than the traditional 2D mode, but it provides some eyecandy, tearless moving etc.<br />
<br />
: To reduce its memory usage, you may:<br />
:* Change its buffering settings on the DisplayEngine settings in MorphOS Preferences. You need to reboot or switch screens for the new settings to take effect.<br />
:* Disable it completely from the Screens settings in MorphOS Preferences for some or all screens. It may also help if you let it be enabled for Ambient screen, but disable it on other screens you might have.<br />
<br />
: Other ways to reduce graphics memory usage:<br />
:* Lower the color depth of screens from the Screens settings. 16-bit might be enough sometimes.<br />
:* Don't use too many separate screens at the same time.<br />
<br />
<br />
=== How to Open MUI Programs on Their Own Screens ===<br />
<br />
: 1) An easy way is to select "Jump to Screen -> New" from the MUI popup menu gadget in program's window border. It always opens in an enhanced mode and clones the resolution from the Ambient screen. Open and save program's MUI settings to save it permanently.<br />
: [[FIle:MorphOS3_jPV_Newscreen.png|120px]]<br />
<br />
: 2) A more configurable method is to open program's MUI settings, select the Screen tab, and create a totally new screen definition there. You can edit the screen name and the title to suit your use (you can use program's name for those for example), select any resolution and depth, enable or disable the enhanced mode etc. In many cases this is a better method, because you can save graphics memory by not using the enhanced mode for screens which you're going to use for full screen apps only or so.<br />
<br />
: You can switch between the screens with lamiga-m (lcommand-m) keyboard shortcut, or by clicking the screen depth gadget (left click switches to the next screen, right click gives you a menu where you can select any open screen).<br />
: [[File:Tips_Screendepthmenu.png]]<br />
<br />
<br />
== Advanced Features ==<br />
<br />
=== Default Device Icons ===<br />
<br />
: If you want a certain default icon for all the units of a certain device, you can create an icon named def_DEVICENAMExdisk.info to your default icons path (SYS:Prefs/Presets/Deficons/ by default).<br />
<br />
: For example the deficon for SMBFS devices would be called def_SMBFSxdisk.info.<br />
<br />
<br />
=== Default Icon for Ambient Windows ===<br />
<br />
: By default there isn't a default icon file for the icon you see when iconifying an Ambient window (a view). If you want to override the built-in icon, create or copy a new icon file to your default icons path and name it to '''def_view.info'''. <br />
<br />
<br />
=== Old Style Preferences Icons ===<br />
<br />
[[File:Separate_prefs_in_MorphOS.png|thumb|Example of separate system prefs in MorphOS]]<br />
: You can have separate preferences icons in the SYS:Prefs/ directory in the old Amiga style for MorphOS system prefs. Make or copy icons named with a corresponding sub preference name into the SYS:Prefs/ dir and edit their Default Tool to ":MorphOS/Prefs/Preferences".<br />
<br />
: There's already a main preferences icon in SYS:Prefs, so here's an easy example: "copy SYS:Prefs/Preferences.info SYS:Prefs/Network.info", after which double clicking the new Network icon opens the network preferences directly.<br />
<br />
<br />
=== Hilight Options in Listers ===<br />
<br />
: If you want to use "Alternated rows" and "Hilighted sorting column" options in the Lister settings with a grapchics card that doesn't support 3D acceleration.<br />
: Type in shell:<br />
: <tt>Setenv MUI/fastppa SAVE 1</tt><br />
<br />
<br />
=== Copy Selected Filenames ===<br />
<br />
: You can use the internal Ambient command "copyselectiontoclipboard" to copy selected filenames with or without path information to the clipboard. For example, create a new custom hotkey in the Ambient Settings and define "copyselectiontoclipboard VIEWID=%Si FULLPATH" as an internal command for it.<br />
<br />
: User may find it very useful to paste around the names selected in the Ambient windows in many situations.<br />
<br />
<br />
=== Using ARexx Ports from Lua ===<br />
<br />
: MorphOS comes with a native implementation of the Lua scripting language. It can be used for script writing with application interacting instead of the emulated 3rd party ARexx. Lua can use existing ARexx ports with its ipc.module.<br />
<br />
: Load the IPC module first with the '''require 'ipc'''' line (unlike the standard Lua distribution, all modules have to be loaded with the ''require'' function on MorphOS. Check available modules from the ''MOSSYS:Libs/Lua/'' directory.)<br />
<br />
:* ipc.'''address(port)''' - sets the default ARexx port. Port "COMMAND" executes commands as DOS shell commands. <br />
:* '''ipc.checkport(port)''' - checks if an ARexx port is available. <br />
:* ipc.'''rx(command)''' - sends a command to a port set with ipc.address. It returns ARexx RESULT. <br />
:* '''ipc.waitforport(name[, interval])''' - Waits for an ARexx port. Script is aborted if the port isn't found.<br />
<br />
: More about the topic [[Getting_Started_with_Lua|here]].<br />
<br />
<br />
=== Copying a Whole Disk As an Image File ===<br />
<br />
: You can access raw data of drives by MorphOS's RAWDISK: device. Partitions or whole disk can be copied in or out with it, but be careful to write to the correct destination! For copying you need to use SDK's cp command or standard Copy command with the DIRECT option.<br />
<br />
: You can browse available disks and devices by opening RAWDISK: device from the shell (just type RAWDISK: on the shell) or from Ambient (hit the / key, clear existing text, and write RAWDISK: to the string line). Browse to the Devices directory and then to the wanted device and unit to see the actual disk image file (rawdisk) and partition files in a separate partition table directory. Partition files let you recognize more easily that you're accessing the wanted disk. They also have information like device and filesystem names told in file comments (use the List command or Ambient to see them).<br />
<br />
: As an example, to make a backup of a whole SD card which is placed in a USB reader (the card is found in usbscsi.device unit 3):<br />
: <tt>Copy DIRECT RAWDISK:Devices/usbscsi.device/3/rawdisk work:sdcard.img</tt><br />
<br />
: And to copy the image back to the SD card (removes all existing data, be careful!):<br />
: <tt>Copy DIRECT work:sdcard.img RAWDISK:Devices/usbscsi.device/3/rawdisk</tt><br />
<br />
: This works with all raw disk image files like Raspberry Pi's OS distributions etc.<br />
<br />
: Single partitions can also be copied from the RAWDISK:Disks directory.<br />
<br />
: If you want to access the data in saved image files without needing to write them back to any device, you can mount them with help of [[Tools/FileImageCtrl]] and [[Tools/Mounter]] programs. You can either mount partitions directly with the [[Tools/FileImageCtrl|FileImageCtrl]] tool or insert disk images on it and mount the wanted partitions with the [[Tools/Mounter|Mounter]] tool.<br />
<br />
<br />
=== Using WLAN with Hidden SSID ===<br />
<br />
: If you have to use wireless network with hidden SSID, you can add "scan_ssid=1" line in your ENVARC:sys/Wireless.prefs file's network block.<br />
<br />
: Contents should look something like this:<br />
<br />
: <tt>network={<br />
: &nbsp;&nbsp;ssid="ThatHiddenSSID"<br />
: &nbsp;&nbsp;scan_ssid=1<br />
: &nbsp;&nbsp;psk="password"<br />
: }</tt><br />
<br />
: Note: It's not recommended to hide the SSID, because it doesn't add security in practise. Use this only if you can't control the network you're connecting.<br />
<br />
<br />
=== Modifying Screen and Keyboard Brightness on a Laptop without Using KB Shortcuts ===<br />
<br />
: Brightness values can be modified by editing the ENVARC:sys/laptopquick.conf file with a text editor. The values are taken in use after a reboot.<br />
<br />
<br />
=== Opening Ambient Windows from the Shell or Scripts ===<br />
<br />
: Directories can be opened with the [[Shell_Commands/Open|Open]] command, but it only opens them in the default view mode:<br />
: <tt>Open SYS:Applications</tt><br />
<br />
: If you need to open windows with certain location, size, position, and mode, you can use the LoadURI ARexx command. LoadURI accepts the following parameters:<br />
:* URI which contains a path and attributes with values. The attributes are given after a question mark and they are separated with the & delimiter. Possible attributes are ''view'' (icon or list), ''mode'' (all, icons, or thumbs), ''top'' (pixels from the top border), ''left'' (pixels from the left border), ''width'', and ''height''.<br />
:* NEW=NEWWIN/S: opens a new window even if similar window would already be opened<br />
:* RELOAD/S: reloads the URI<br />
:* FORCE/S: forces full reloading<br />
:* BROWSER/N: forces the browser mode on (1) or off (0)<br />
:* VIEWID/N: specifies view/window ID<br />
<br />
: Use the ''AMBIENT'' port in ARexx scripts.<br />
<br />
: To open the SYS:Libs directory in the list mode showing all files in a 440x600 window at position x=350, y=50, no matter if it has been opened previously:<br />
: <tt>'LoadURI "file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600" NEW'</tt><br />
<br />
: To open a directory in the icon mode showing thumbnails in a 500x400 window at position x=350, y=50, the window is also opened in the spatial (non browser) mode:<br />
: <tt>'LoadURI "file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400" BROWSER=0'</tt><br />
<br />
: If you don't want to write full ARexx scripts but would like to run them just as single shell commands, you can use the [[Shell_Commands/RXCmd|RXCmd]] shell command (notice that you have to escape the inner quotation marks with the asterisks):<br />
: <tt>RXCmd AMBIENT "LoadURI *"file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600*" NEW"<br />
: RXCmd AMBIENT "LoadURI *"file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400*" BROWSER=0"</tt><br />
<br />
<br />
== Bundled Software ==<br />
<br />
=== Flacapella Settings for MP3 Encoding ===<br />
<br />
: Example of a custom encoder setting in Flacapella:<br />
<br />
: <tt>Compress Command: c:lame -V0 --tt "{title}" --ta "{artist}" --tl "{album}" --tn {track} {?coverfile:--ti "{coverfile}"} {input} {output}<br />
: File Extension: mp3</tt><br />
<br />
: This will encode tracks to mp3 files with title, artist, album and track number tags. It also embeds fetched cover image in files, if image was found. <br />
: Example assumes you have [https://www.morphos-storage.net/?find=lame LAME] installed in C:<br />
<br />
<br />
=== Jukebox Tips ===<br />
<br />
:* If you select any song in playlist by clicking it just once, it's played next no matter if you have random or sequential mode in use. <br />
:* You can adjust volume in Jukebox by using mouse wheel over its screenbar module. <br />
:* Displayed columns can be configured on the fly by right clicking the column title.<br />
:* Jukebox can be better integrated into Ambient and its contextual menus with the [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script.<br />
:* Two new tooltypes were presented in MorphOS 3.8: <br />
:** '''FRAMESCAN=NO''' disables the Reggae framescanning for tracks that have unknown duration. It speeds up the loading of such tracks, but you'll lose the seeking ability with them. <br />
:** '''STREAMBUFFER=YES''' activates the Reggae streambuffer class which reduces stuttering, but causes lag on track change and seeking.<br />
<br />
<br />
=== How to Reduce OWB's HD Writes ===<br />
<br />
: OWB writes a lot of data to the hard drive by default. You might want to reduce it if you're paranoid about SFS fragmentation, filesystem corruption, privacy, or you'd like to avoid certain databases getting too big (which can cause slowdowns). Or you just want your .recycled dir to have other than the OWB files. One option is to use the Private Browsing mode always, but here are tips if you don't want to activate that always or you want to restrict certain writes only.<br />
<br />
:* Disable the TopSites feature. This makes a write for every page you visit, it's an awful amount. Its database (conf/TopSites.db) can also grow to hundreds of megabytes, which causes very noticeable slowdowns to browsing. You can disable it with the "Setenv SAVE OWB_DISABLE_TOPSITES 1" command in the shell, and if the database file has already grown too big, you can remove it.<br />
:* Disable the Website Icons feature. Open the Interface settings and uncheck all Website Icons checkmarks. <br />
:* Disable all saving options from the Privacy settings.<br />
<br />
: If you still need some option enabled, because some site requires it, you can soft link its configuration file to Ram Disk. I, for example, still have Local Storage enabled, but I have linked its dir to ENV: (which resides in Ram Disk). To do that, make LocalStorage directories to both ENV: and ENVARC: (that ensures that it's created after a reboot too), open the shell and cd into your OWB/Conf/ dir, rename or delete the old LocalStorage dir, type "makelink LocalStorage ENV:LocalStorage". Using ENV: gives the advantage to have some files saved so that those settings are restored in every boot. If you're happy with a certain setting, copy the corresponding file to ENVARC: and it will be preserved without being messed up with the later usage. If you just want to have the configuration files enabled, but cleared on every boot, you could soft link them to T: for example.<br />
<br />
<br />
=== Alternative YouTube Script for OWB ===<br />
<br />
: [http://www.morphzone.info/modules/newbb_plus/viewtopic.php?forum=9&topic_id=9799&post_id=109979&viewmode=flat&sortorder=0&showonepost=1 YouTube Center] is a feature rich configureable userscript for improving YouTube experience. It's made for mainstream browsers, but it also works on OWB! All videos can be forced to HTML5 to get them work in OWB. It's heavier than Fab's official OWB script, but works fine as an option or as a backup plan :). Script saves its settings to LocalStorage to #?www.youtube.com#? files.<br />
<br />
: Note: YouTube defaults to the HTML5 player nowadays and you might be fine without any Flash->HTML5 converter scripts. It's probably better to install this script only if you want some other features from it.<br />
<br />
<br />
=== Watching Videos with Less CPU Load in OWB ===<br />
<br />
: When watching a video in OWB, the fullscreen mode makes a lot less CPU load than the default embedded mode, because the fast overlay mode is used then. CPU load may drop from 100% to 40% for example. Wait until the video really starts playing before clicking the fullscreen button on it, or it may fail and you have to reload the video to be able to try it again. Some videos may have a fullscreen option in their contextual menu too. Remember to have Fullscreen Fix scripts added and enabled from the Scripts window ("Windows->Scripts..." pulldown menu entry) for YouTube, Dailymotion, and Vimeo.<br />
<br />
: Note: check that you really have the latest YouTube fullscreen fix script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js in your OWB/Scripts/ directory. Grunch doesn't get updated for the latest version always for example.<br />
<br />
<br />
=== Problems with YouTube Videos ===<br />
<br />
:* Now that YouTube defaults to HTML5, our days of ad-free videos have ended. It also means that the Content Blocking (AdBlock) option in the OWB's settings can block some videos. If you have some videos which won't start playing, try to disable the Content Blocking option and try again. If that was the problem, but you want to keep the content blocking enabled, add an allow rule to the Content Blocking settings. Open "Windows->Content Blocking..." from the OWB's pulldown menus, click the Add button, and write "youtube.com" to the Rule line. Close the window and try the video again.<br />[[File:OWB_ContentBlockingYT.png]]<br />
<br />
:* If all videos refuse to play, check if you have any YouTube converter scripts enabled in the "Windows->Scripts..." settings. The Fullscreen Fix script is the only one needed and you should disable all converter scripts.<br />
<br />
:* Flash plugins can also break compatibility with YouTube, so if you have the swfdec_plugin.library file in your OWB/Plugins/ directory, you have the following options to choose from:<br />
:** Remove the file from use if you don't need flash anywhere. The plugin doesn't work too well generally anyway.<br />
:** Keep the file, but disable it for all pages by unchecking the "Settings->Preferencfes->Content->Allow plugins" option. You can then enable it temporarily from "Settings->Plugins->Enable" if needed.<br />
:** Disable it temporarily from "Settings->Plugins->Disable", and reload the page.<br />
:** Disable it just for YouTube by adding a new URL setting from "Windows->URL Settings...". Click the Add button, edit the URL line to for example "youtube.com", and uncheck the Plugins option.<br />
<br />
<br />
=== OWB Doesn't Work or Stopped Working with Certain Web Pages ===<br />
<br />
:* Sometimes it helps to change the "Spoof as" setting in OWB. Web pages may offer different kind of content depending on what browser they think you are using. Some popular CAPTCHAs don't work with the default spoofing, but do work when spoofed as iPad for instance. iPad is generally a good option to start trying the spoofing, because you probably get the page in its simpliest form then.<br />
<br />
:* There are some bugs in the JavaScript engine in the latest available OWB version (1.24 at the time of writing) and that causes problems with some web pages, but there's a chance that these pages would still work with an earlier OWB version. You can download earlier OWB versions from [http://fabportnawak.free.fr/owb/ Fab's homepage] and install them, for example, to a different directory than your current OWB installation. There's no problem having two or even several OWB installations on your system, you can just launch whichever you want. As an example, Google Maps stopped working with OWB 1.24 in autumn 2017, but it still continued to work with [http://fabportnawak.free.fr/owb/owb-morphos-1.23.lha OWB 1.23].<br />
<br />
<br />
=== Creating an ISO Image ===<br />
<br />
: Jalapeno can also create and save ISO images which will preserve MorphOS/AmigaOS file attributes and comments. Images can be used for backups or even be booted from USB devices.<br />
<br />
: An option to create an ISO image is found on the pulldown menu in the Burn Files section.<br />
<br />
: [[File:Tips_Create_ISO.png|200px]]<br />
<br />
: If the resulting image file will be bigger than 1GB, Jalapeno splits it into 1GB parts. Those parts can be joined into one big image file with the Join command in the shell, but remember the filesize limits of your target [https://library.morph.zone/Filesystems filesystem] when doing that.<br />
<br />
<br />
=== Copying a CD/DVD to an ISO Image ===<br />
<br />
: If you want to make a standard, easily mountable, ISO image out of an existing CD or DVD, a good way to achieve it is to use the ReadCD program provided with the Jalapeno program on the standard MorphOS installation. Jalapeno itself can also create image files of optical media by selecting "Save as..." from the "Copy Tracks" pull-down menu, but resulting images aren't mountable by the system, because Jalapeno uses options that include more data into the images, for error checking etc.<br />
<br />
: Do these steps from the shell to read a CD/DVD into a standard ISO image:<br />
:# Find your CD drive device by typing: MOSSYS:Data/Jalapeno/readcd -scanbus<br />
:# Create an ISO image by typing (replace "1,1,0" to what you saw in the previous step, and the image path to what you want): MOSSYS:Data/Jalapeno/readcd -dev 1,1,0 f=ram:image.iso<br />
<br />
=== Disabling the Default UTF-8 Mode with Scribble ===<br />
<br />
: Scribble uses UTF-8 encoding by default, but you might prefer to default to the traditional ASCII format instead. The UTF-8 mode can be disabled from the pulldown menu in Scribble, but the setting isn't saved if you save the program settings.<br />
: [[File:Scribble_ascii1.png|128px]]<br />
<br />
: If you want to disable it by default, you have to open the "Save As..." requester, enable the "Make Default" option (also check that Encoding is set to ASCII), and save a file (can be any file anywhere).<br />
: [[File:Scribble_ascii2.png|205px]]<br />
<br />
<br />
== 3rd Party Software ==<br />
<br />
=== Where to Get Software? ===<br />
:* Check [http://library.morph.zone/Links#File_Repositories file repositories] for manual installing<br />
:* [http://www.geit.de/eng_grunch.html Grunch] is a good packet manager for automatic installation and updating of selected software<br />
:* [http://www.meta-morphos.org/WArMUp/chrysalis_en.pdf Chrysalis] is a preconfigured environment and software distribution package ([http://www.warmup-asso.org/download/pack/chrysalis.iso Download ISO image])<br />
<br />
<br />
=== Custom Ambient Menus with AREXX ===<br />
<br />
: You can add own menu items to Ambient pulldown menus with AREXX. Read SYS:MorphOS/Ambient/docs/arexx.txt for more info about AREXX usage or download the [http://morphos-files.net/remote/CRABUM CRABUM] program, which helps you to create correct AREXX lines ([http://library.morph.zone/Getting_Started#Creating_Menus_with_CRABUM tutorial]).<br />
<br />
<br />
=== Help with Shell Commands ===<br />
<br />
: MorphOS Library contains descriptions of all [http://library.morph.zone/Shell_Commands shell commands] and the descriptions can be displayed on the shell with the [http://aminet.net/package/util/batch/Chelp Chelp] script. The script can be used to replace older [http://aminet.net/package/util/cli/Help Help] program (which would otherwise be nice still, but it only contains help for MorphOS 1.x commands).<br />
<br />
<br />
=== Utilizing Your Keyboard's Multimedia Keys ===<br />
<br />
:* The [http://www.geit.de/eng_mmkeyboard.html MMKeyboard] software can be used to assign different kinds of functions to extra keys found on some keyboards.<br />
:* The [http://aminet.net/package/mus/play/MultiMeedio MultiMeedio] script provides a unified control for all popular media players.<br />
<br />
<br />
== Hardware Related ==<br />
<br />
=== Removing Startup Sound on Macs ===<br />
<br />
: Sadly there isn't any known way to disable that annoying startup sound from MorphOS itself or from Open Firmware, but there are few different ways to achieve it anyway.<br />
<br />
:* If you plan to use Mac as MorphOS only system, but you still have OSX installed, you can mute the audio from OSX before wiping it out by installing MorphOS. Startup sound doesn't come back if you won't boot into OSX anymore.<br />
:* If you don't have OSX anymore, you could try to remove sound with some Linux distribution's live/installation CD. More info [http://www.meta-morphos.org/faq.php?id_cat=2&myfaq=yes&categories=Installation+et+d%E9marrage#74 here] and [https://morphosuser.wordpress.com/2014/12/28/removing-the-boot-sound/ here].<br />
:* If you use OSX and MorphOS as a dualboot system you can install [http://www5e.biglobe.ne.jp/~arcana/StartupSound/index.en.html StartupSound.prefPane] for OSX.<br />
<br />
<br />
=== Speeding Up the Startup Manager on Macs ===<br />
<br />
: Startup Manager (the boot menu you get by booting with option/alt key pressed) can be slow when it tries to find network boot devices. To speed it up go to the OF prompt and type "'''setenv skip-netboot? true'''". Funnily enough, it only affects if you have network cable plugged in.<br />
<br />
<br />
=== Booting MorphOS ISO from USB Stick ===<br />
<br />
: MorphOS Team has released an [http://www.morphos-team.net/guide/usb-boot official guide] for USB booting, but I've also noticed that at least some Macs (Mac mini and Powerbook for example) have certain ud alias for USB drive. You can use that as a shortcut and get the booting done with less work (no need to search the correct path, works even when USB stick is in a hub, less typing and less to remember).<br />
<br />
: If you have only one mass storage device connected, you can just boot into Open Firmware prompt (command-alt-o-f) and type:<br />
<br />
: <tt>boot ud:,\boot.img bi umsd0:morphos.iso</tt><br />
<br />
: (Remember to have both boot.img and morphos.iso on the stick)<br />
<br />
<br />
=== Keyboard Reboot on ADB Laptops ===<br />
<br />
: The traditional Ctrl-Command-Command (Ctrl-Amiga-Amiga) keyboard combination doesn't work on laptops using the ADB interface for the keyboard, because ADB doesn't make difference between the left and right command keys. You can reboot them with an alternative Fn-Alt-Alt keyboard combination.<br />
<br />
<br />
=== Blackouts or Graphical Flickering on Mac mini ===<br />
<br />
: Mac minis suffer from short blackouts with some monitors when the connection is made with a DVI cable. The screen gets usually blanked for few seconds, and depending of the monitor it may happen more or less frequently. Issue may also show up as flickering lines on the screen and it may get worse and worse until the monitor is unable to sync to the signal anymore.<br />
<br />
: One option to get around it is to use a VGA adapter/cable, because it doesn't seem to happen with it.<br />
<br />
: An another option is to try to lower the pixel clock value for the used screenmode from the Monitors settings in the MorphOS preferences. If your default mode has for example vertical frequency of 75 Hz, going to 60 Hz mode may help. Sometimes even a small change can help, and lowering just couple clicks from 60 Hz does the trick.<br />
<br />
: This seems to be a common problem with Mac minis and "non-coherent" displays as discussed for example [https://discussions.apple.com/thread/2723110 here].<br />
<br />
<br />
=== Disabling the Internal Touchpad on Laptops ===<br />
==== From the Touchpad Settings (Preferred)====<br />
: An internal touchpad can be disabled from the MorphOS system settings nowadays, and this is the preferred method. Open '''System Settings -> Touchpad''' and disable the '''Enable the Touchpad driver''' setting.<br />
<br />
: [[File:MorphOS_Preferences_disabling_touchpad.png|200px]]<br />
<br />
==== From the USB Settings ====<br />
: The touchpad can be disabled temporarily by removing its binding in the USB settings. This setting is reverted back next time the machine is booted or if USB class scanning is done otherwise.<br />
<br />
: To remove the binding, open the USB settings from the MorphOS Preferences application and go to the Devices list.<br />
:* If you have "Apple Internal Trackpad" alone in the list, you can just select it and click the Unbind button.<br />
:: [[File:Disabling touchpad ibook.png|200px]]<br />
:* If your machine has a combined internal keyboard and trackpad device, double click it ("Apple Internal Keyboard / Trackpad"). Select Touchpad from the newly opened window and then click the Release Binding button.<br />
:: [[File:Disabling touchpad powerbook.png|200px]]<br />
<br />
==== Removing the Driver at Boot Time ====<br />
: Touchpad can also be disabled permanently by removing touchpad.library from use. Removing it is a bit tricky, because it resides in "ROM" and not as a file in system directories, but it can be done with the mf (module filter) boot command argument.<br />
<br />
: The boot command arguments can be edited by editing the bootinfo.txt file on Macs. The bootinfo.txt file is found on the Boot: partition, which also contains the boot.img file. If you don't see the partition, you probably need to mount it first by using, for example, the [[Tools/Mounter | Mounter]] tool. '''Note that if you edit the bootinfo.txt file, you must bless the file with the [[Shell_Commands/HFSSetMacBoot | HFSSetMacBoot]] command or the system won't be bootable anymore!'''<br />
<br />
: To add the mf argument, open the bootinfo.txt file with a text editor, find the line between <BOOT-SCRIPT> and </BOOT-SCRIPT> lines (it starts with "boot"), and add ''mf=touchpad.library'' at the end of the boot line. Save the file and '''remember to bless it with the ''HFSSetMacBoot Boot:bootinfo.txt'' command from the shell or your system won't boot again!'''<br />
<br />
<br />
=== MorphOS Boot Arguments on U-boot Systems ===<br />
: To boot into MorphOS, hardware has to load a MorphOS boot image file that contains the kernel and core drivers. The boot image file also accepts arguments to control the boot procedure before the actual operating system is loaded from the system partition. The boot arguments usage on [[Open Firmware]] systems is well [[Open_Firmware#Boot_Arguments | documented]], but they must be given in a different way on [http://www.intuitionbase.com/static.php?section=uboot U-boot] systems (Sam460ex/cr, AmigaOne X5000).<br />
<br />
: On the U-boot systems the boot arguments have to be set in the '''morphosargs''' environment variable in the U-boot console.<br />
<br />
: To check if you already have the variable set:<br />
: <tt>printenv morphosargs</tt><br />
<br />
: To set an argument (in this example we'd disable an unsupported SCSI controller by removing the SCSI driver from the boot image by using the ''module filter (mf)'' boot argument):<br />
: <tt>setenv morphosargs mf=symbios.device</tt><br />
: <tt>saveenv</tt><br />
<br />
: To edit an existing variable:<br />
: <tt>editenv morphosargs</tt><br />
: <tt>saveenv</tt></div>
JPV
https://library.morph.zone/index.php?title=Tips_and_Tricks&diff=4326
Tips and Tricks
2023-11-27T06:58:08Z
<p>JPV: </p>
<hr />
<div>''Originally published at: http://jpv.wmhost.com/morphos/tips/''<br />
<br />
Miscellaneous tips and tricks for MorphOS use. Some may even be hackish and not officially encouraged by MorphOS Team. Everyone is welcome to make additions and corrections here.<br />
== Basic Features ==<br />
<br />
=== Modifying the System Directory ===<br />
: Tip #1: NEVER modify anything in the MOSSYS: (SYS:MorphOS/) path! All the changes are lost in the system upgrade. If you need to add any 3rd party drivers or libraries, add them to SYS:. If there isn't a correct directory by default, make one.<br />
<br />
: There's only one exception (of course there is one) to this: you can rename MOSSYS:Libs/rexxsyslib.library to MOSSYS:Libs/rexxsyslib.library_disabled when you copy 68k version of rexxsyslib.library to SYS:Libs/ in order to get the AREXX working.<br />
<br />
<br />
=== Keyboard Commands ===<br />
<br />
: At first, check the default ones and define your favourites in '''System Settings -> IControl -> Hotkeys''' and in '''Ambient Settings -> Keyboard'''.<br />
<br />
: For example IControl has "Active Window: Activate Next" and "All Windows: Depth Menu" options, which can be used to achieve alt/ctrl/command-tab style window cycling functionality familiar from other operating systems.<br />
<br />
: Other keys: <br />
:* To zoom Ambient icons in the icon mode: keep CTRL pressed and use the mouse wheel or just roll the wheel over the Viewmode button.<br />
:* To find and select files in Ambient windows by letters: start typing a name when the window is active. Keep the Shift key pressed for directories. <br />
:* To enter a path manually (for example for hidden dirs like .recycled): press the / key in an Ambient window and type in the path. <br />
:* Command-f activates the find function in most programs. <br />
:* The r key rotates the pictures in Ambient's internal viewer and Page Up/Down keys select previous and next images in a dir <br />
:* Check keyboard commands of the Shell, like by default, commands can be completed with CTRL-tab, devices with ALT-tab, history with shift-tab etc. <br />
:* Keeping the Alt key pressed while double clicking a drawer gives you different ways to open drawers.<br />
:* Keeping the Alt key pressed while dragging files on the same partition copies files instead of moving, or vice versa depending on your Ambient settings.<br />
<br />
=== Enabling/Disabling Icon Tooltypes ===<br />
<br />
: Double click single tooltypes to enable and disable them in the icon information window.<br />
<br />
<br />
=== Browsing History in Ambient ===<br />
<br />
: Clicking the parent button ([[File:Tips_Parent.png|middle]]) on an Ambient window (in browser mode) with the right mouse button gives you a browsing history popup menu for quick jumping between locations.<br />
<br />
<br />
=== Sync the Clock from Internet at Boot ===<br />
<br />
: Add this line to S:user-network-startup file:<br />
: <tt>Run DETACH MOSSYS:C/SetClockNTP SAVE</tt><br />
<br />
<br />
=== Redirecting AHI Music Unit ===<br />
<br />
: You can select Unit 0 as the Music Unit in AHI to be able hear audio output from multiple programs at the same time, with a slight decrease in quality.<br />
<br />
: [[File:MorphOS_System_settings_Music_Unit.png|280px]]<br />
<br />
<br />
=== Keeping AHI Audio Quality Better ===<br />
<br />
: Audio quality with AHI will be better if you reduce available channels for its shared modes (Unit 0 usually). Available channels will limit the amount of simultaneus playback of sounds, but you really don't need the default 32 channels and even two channels can be quite enough. Should there be more concurrent sounds, some of them just get muted until the other have been finished.<br />
<br />
: [[File:MorphOS_System_settings_Change_Unit.png|280px]] [[File:MorphOS_System_settings_Unit_0.png|280px]]<br />
<br />
<br />
=== Mime Type Configuration ===<br />
<br />
: Learn to configure mime types from the Ambient settings. It really gives so much for your system and your user experience. [http://jpv.wmhost.com/pics/mimemplayer.png Here] is one example of how to configure MPlayer for all the video files.<br />
<br />
<br />
=== Inline Editing ===<br />
<br />
: Inline editing is a quick way to edit filenames by clicking them with the mouse wheel or with the long left mouse click. Its behaviour can be configured from the Lister settings in Ambient Settings.<br />
<br />
: File comments can also be edited with the inline editing.<br />
<br />
: [[File:Tips_Inlineedit.png|280px]]<br />
<br />
<br />
=== Batch Renaming in Ambient ===<br />
<br />
# Select files you want to be in the range of renaming.<br />
# Hit rename button or command-r keyboard shortcut.<br />
# Use pattern to rename. For example renaming all files which begin with "mod." to files which end with ".mod", use "mod.*" as source and "*.mod" as destination (quotation marks not needed).<br />
<br />
<br />
=== Don't Forget RMB/Long-LMB Gadget Menus ===<br />
<br />
: You get menus from zoom and depth gadgets with right mouse button or by holding left mouse button pressed on them.<br />
<br />
: [[File:Tips_Zoommenu.png]] [[File:Tips_Windowdepthmenu.png]] [[File:Tips_Screendepthmenu.png]]<br />
<br />
<br />
=== How to Use RMB with One-button Mouse ===<br />
<br />
: The right mouse button can be emulated in several different ways:<br />
:* The '''System Settings -> Mouse -> Open menus by clicking...''' setting lets your mouse button act as the right mouse button if you hold a qualifier key pressed while clicking. The qualifier key can be configured for your preferences, but it's the shift key by default.<br />
:* Press right alt and right command keys together. This probably doesn't work on systems with ADB keyboard, like on older Mac laptops. The ADB keyboard doesn't make difference between left and right keys.<br />
:* With non-ADB laptops (PowerBook 5,6-5,9 and 6,7 (iBook)) you can also use two finger tap or two finger hold + button combination on the touchpad for RMB.<br />
:* You can define a hotkey for menu launching on the IControl preferences (the default one is rcommand+space). It doesn't work exactly as the RMB everywhere, but works if you're mostly using the RMB for menus.<br />
:* A multi button USB mouse works always!<br />
<br />
<br />
=== Starting Programs Iconified ===<br />
<br />
: MUI has an option to start programs in iconified mode. It's useful for example for programs like Synergy, which you'd like to start on background without their main window jumping up. The option can be found from program's MUI Settings (Windows -> Iconify on startup).<br />
<br />
: [[File:Tips_Iconify.png]]<br />
<br />
<br />
=== Checking the Debug Log ===<br />
<br />
: If you want a stable system, you need to check the debug log periodically to see if any program misbehaves when used, especially when running new software.<br />
<br />
: An easy way to do it is to enable Debug screenbar module from the screen depth gadget menu. Bug looking Debug button on the screenbar will then give you a debug menu where you can view the log etc. If "Show Log..." option is ghosted, there's nothing in the log and everything is fine, but if it shows hundreds of cryptic lines (it's called a hit), then you have something to worry and the system probably isn't stable anymore. Some programs may output their own harmless debug information to the log too, but it's usually limited to few or tens of lines maximum. You'll recognize a real hit for sure.<br />
<br />
: [[File:Tips_Debug1.png|x64px]] [[File:Tips_Debug2.png|x64px]]<br />
<br />
<br />
=== Printing to a PostScript Compatible Network Printer ===<br />
<br />
: You should mount the NETPAR: device and print to that device from programs like VPDF and OWB, which can output PostScript. NETPAR: is faster than printing through Turboprint (PRT:) and doesn't need Ghostscript installed (PS:).<br />
<br />
: "Mount NETPAR:" can be added to S:user-startup, for example.<br />
<br />
<br />
=== .recycled Directory ===<br />
<br />
: SFS is the default filesystem on MorphOS. It can have a special directory which contains recently deleted files. The directory is named as .recycled and it resides at the root level of every SFS partition (SYS:.recycled for example). Depending the format options it may be disabled, hidden but accessible, or visible.<br />
<br />
: If it's hidden, you can't see it even with "View All Files" option, but you can access it from the shell or Ambient (for example by pressing / key and then writing it to the path string after the volume name).<br />
<br />
: You shouldn't modify any files in it, but you can recover deleted files by copying them to some other path.<br />
<br />
: The PFS3 filesystem has a similar directory, but its name is ".deldir".<br />
<br />
<br />
=== How to Reduce Graphics Memory Usage ===<br />
<br />
: MorphOS can use graphics memory quite extensively which can cause slowdowns or glitches if you run out of it. It usually isn't an issue if you have 64MB or more graphics memory, but lower spec systems with today's resolutions may need some tuning. There are several ways to reduce memory usage and you have to decide or try which is the best for you.<br />
<br />
: MorphOS has an "Enhanced Display" mode, which uses the graphics card's 3D functions to draw graphic layers. It consumes more memory than the traditional 2D mode, but it provides some eyecandy, tearless moving etc.<br />
<br />
: To reduce its memory usage, you may:<br />
:* Change its buffering settings on the DisplayEngine settings in MorphOS Preferences. You need to reboot or switch screens for the new settings to take effect.<br />
:* Disable it completely from the Screens settings in MorphOS Preferences for some or all screens. It may also help if you let it be enabled for Ambient screen, but disable it on other screens you might have.<br />
<br />
: Other ways to reduce graphics memory usage:<br />
:* Lower the color depth of screens from the Screens settings. 16-bit might be enough sometimes.<br />
:* Don't use too many separate screens at the same time.<br />
<br />
<br />
=== How to Open MUI Programs on Their Own Screens ===<br />
<br />
: 1) An easy way is to select "Jump to Screen -> New" from the MUI popup menu gadget in program's window border. It always opens in an enhanced mode and clones the resolution from the Ambient screen. Open and save program's MUI settings to save it permanently.<br />
: [[FIle:MorphOS3_jPV_Newscreen.png|120px]]<br />
<br />
: 2) A more configurable method is to open program's MUI settings, select the Screen tab, and create a totally new screen definition there. You can edit the screen name and the title to suit your use (you can use program's name for those for example), select any resolution and depth, enable or disable the enhanced mode etc. In many cases this is a better method, because you can save graphics memory by not using the enhanced mode for screens which you're going to use for full screen apps only or so.<br />
<br />
: You can switch between the screens with lamiga-m (lcommand-m) keyboard shortcut, or by clicking the screen depth gadget (left click switches to the next screen, right click gives you a menu where you can select any open screen).<br />
: [[File:Tips_Screendepthmenu.png]]<br />
<br />
<br />
== Advanced Features ==<br />
<br />
=== Default Device Icons ===<br />
<br />
: If you want a certain default icon for all the units of a certain device, you can create an icon named def_DEVICENAMExdisk.info to your default icons path (SYS:Prefs/Presets/Deficons/ by default).<br />
<br />
: For example the deficon for SMBFS devices would be called def_SMBFSxdisk.info.<br />
<br />
<br />
=== Default Icon for Ambient Windows ===<br />
<br />
: By default there isn't a default icon file for the icon you see when iconifying an Ambient window (a view). If you want to override the built-in icon, create or copy a new icon file to your default icons path and name it to '''def_view.info'''. <br />
<br />
<br />
=== Old Style Preferences Icons ===<br />
<br />
[[File:Separate_prefs_in_MorphOS.png|thumb|Example of separate system prefs in MorphOS]]<br />
: You can have separate preferences icons in the SYS:Prefs/ directory in the old Amiga style for MorphOS system prefs. Make or copy icons named with a corresponding sub preference name into the SYS:Prefs/ dir and edit their Default Tool to ":MorphOS/Prefs/Preferences".<br />
<br />
: There's already a main preferences icon in SYS:Prefs, so here's an easy example: "copy SYS:Prefs/Preferences.info SYS:Prefs/Network.info", after which double clicking the new Network icon opens the network preferences directly.<br />
<br />
<br />
=== Hilight Options in Listers ===<br />
<br />
: If you want to use "Alternated rows" and "Hilighted sorting column" options in the Lister settings with a grapchics card that doesn't support 3D acceleration.<br />
: Type in shell:<br />
: <tt>Setenv MUI/fastppa SAVE 1</tt><br />
<br />
<br />
=== Copy Selected Filenames ===<br />
<br />
: You can use the internal Ambient command "copyselectiontoclipboard" to copy selected filenames with or without path information to the clipboard. For example, create a new custom hotkey in the Ambient Settings and define "copyselectiontoclipboard VIEWID=%Si FULLPATH" as an internal command for it.<br />
<br />
: User may find it very useful to paste around the names selected in the Ambient windows in many situations.<br />
<br />
<br />
=== Using ARexx Ports from Lua ===<br />
<br />
: MorphOS comes with a native implementation of the Lua scripting language. It can be used for script writing with application interacting instead of the emulated 3rd party ARexx. Lua can use existing ARexx ports with its ipc.module.<br />
<br />
: Load the IPC module first with the '''require 'ipc'''' line (unlike the standard Lua distribution, all modules have to be loaded with the ''require'' function on MorphOS. Check available modules from the ''MOSSYS:Libs/Lua/'' directory.)<br />
<br />
:* ipc.'''address(port)''' - sets the default ARexx port. Port "COMMAND" executes commands as DOS shell commands. <br />
:* '''ipc.checkport(port)''' - checks if ARexx port is available. <br />
:* ipc.'''rx(command)''' - sends command to a port set with ipc.address. It returns ARexx RESULT. <br />
:* '''ipc.waitforport(name[, interval])''' - Waits for a ARexx port. Script is aborted if the port isn't found.<br />
<br />
: More about the topic [[Getting_Started_with_Lua|here]].<br />
<br />
<br />
=== Copying a Whole Disk As an Image File ===<br />
<br />
: You can access raw data of drives by MorphOS's RAWDISK: device. Partitions or whole disk can be copied in or out with it, but be careful to write to the correct destination! For copying you need to use SDK's cp command or standard Copy command with the DIRECT option.<br />
<br />
: You can browse available disks and devices by opening RAWDISK: device from the shell (just type RAWDISK: on the shell) or from Ambient (hit the / key, clear existing text, and write RAWDISK: to the string line). Browse to the Devices directory and then to the wanted device and unit to see the actual disk image file (rawdisk) and partition files in a separate partition table directory. Partition files let you recognize more easily that you're accessing the wanted disk. They also have information like device and filesystem names told in file comments (use the List command or Ambient to see them).<br />
<br />
: As an example, to make a backup of a whole SD card which is placed in a USB reader (the card is found in usbscsi.device unit 3):<br />
: <tt>Copy DIRECT RAWDISK:Devices/usbscsi.device/3/rawdisk work:sdcard.img</tt><br />
<br />
: And to copy the image back to the SD card (removes all existing data, be careful!):<br />
: <tt>Copy DIRECT work:sdcard.img RAWDISK:Devices/usbscsi.device/3/rawdisk</tt><br />
<br />
: This works with all raw disk image files like Raspberry Pi's OS distributions etc.<br />
<br />
: Single partitions can also be copied from the RAWDISK:Disks directory.<br />
<br />
: If you want to access the data in saved image files without needing to write them back to any device, you can mount them with help of [[Tools/FileImageCtrl]] and [[Tools/Mounter]] programs. You can either mount partitions directly with the [[Tools/FileImageCtrl|FileImageCtrl]] tool or insert disk images on it and mount the wanted partitions with the [[Tools/Mounter|Mounter]] tool.<br />
<br />
<br />
=== Using WLAN with Hidden SSID ===<br />
<br />
: If you have to use wireless network with hidden SSID, you can add "scan_ssid=1" line in your ENVARC:sys/Wireless.prefs file's network block.<br />
<br />
: Contents should look something like this:<br />
<br />
: <tt>network={<br />
: &nbsp;&nbsp;ssid="ThatHiddenSSID"<br />
: &nbsp;&nbsp;scan_ssid=1<br />
: &nbsp;&nbsp;psk="password"<br />
: }</tt><br />
<br />
: Note: It's not recommended to hide the SSID, because it doesn't add security in practise. Use this only if you can't control the network you're connecting.<br />
<br />
<br />
=== Modifying Screen and Keyboard Brightness on a Laptop without Using KB Shortcuts ===<br />
<br />
: Brightness values can be modified by editing the ENVARC:sys/laptopquick.conf file with a text editor. The values are taken in use after a reboot.<br />
<br />
<br />
=== Opening Ambient Windows from the Shell or Scripts ===<br />
<br />
: Directories can be opened with the [[Shell_Commands/Open|Open]] command, but it only opens them in the default view mode:<br />
: <tt>Open SYS:Applications</tt><br />
<br />
: If you need to open windows with certain location, size, position, and mode, you can use the LoadURI ARexx command. LoadURI accepts the following parameters:<br />
:* URI which contains a path and attributes with values. The attributes are given after a question mark and they are separated with the & delimiter. Possible attributes are ''view'' (icon or list), ''mode'' (all, icons, or thumbs), ''top'' (pixels from the top border), ''left'' (pixels from the left border), ''width'', and ''height''.<br />
:* NEW=NEWWIN/S: opens a new window even if similar window would already be opened<br />
:* RELOAD/S: reloads the URI<br />
:* FORCE/S: forces full reloading<br />
:* BROWSER/N: forces the browser mode on (1) or off (0)<br />
:* VIEWID/N: specifies view/window ID<br />
<br />
: Use the ''AMBIENT'' port in ARexx scripts.<br />
<br />
: To open the SYS:Libs directory in the list mode showing all files in a 440x600 window at position x=350, y=50, no matter if it has been opened previously:<br />
: <tt>'LoadURI "file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600" NEW'</tt><br />
<br />
: To open a directory in the icon mode showing thumbnails in a 500x400 window at position x=350, y=50, the window is also opened in the spatial (non browser) mode:<br />
: <tt>'LoadURI "file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400" BROWSER=0'</tt><br />
<br />
: If you don't want to write full ARexx scripts but would like to run them just as single shell commands, you can use the [[Shell_Commands/RXCmd|RXCmd]] shell command (notice that you have to escape the inner quotation marks with the asterisks):<br />
: <tt>RXCmd AMBIENT "LoadURI *"file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600*" NEW"<br />
: RXCmd AMBIENT "LoadURI *"file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400*" BROWSER=0"</tt><br />
<br />
<br />
== Bundled Software ==<br />
<br />
=== Flacapella Settings for MP3 Encoding ===<br />
<br />
: Example of a custom encoder setting in Flacapella:<br />
<br />
: <tt>Compress Command: c:lame -V0 --tt "{title}" --ta "{artist}" --tl "{album}" --tn {track} {?coverfile:--ti "{coverfile}"} {input} {output}<br />
: File Extension: mp3</tt><br />
<br />
: This will encode tracks to mp3 files with title, artist, album and track number tags. It also embeds fetched cover image in files, if image was found. <br />
: Example assumes you have [https://www.morphos-storage.net/?find=lame LAME] installed in C:<br />
<br />
<br />
=== Jukebox Tips ===<br />
<br />
:* If you select any song in playlist by clicking it just once, it's played next no matter if you have random or sequential mode in use. <br />
:* You can adjust volume in Jukebox by using mouse wheel over its screenbar module. <br />
:* Displayed columns can be configured on the fly by right clicking the column title.<br />
:* Jukebox can be better integrated into Ambient and its contextual menus with the [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script.<br />
:* Two new tooltypes were presented in MorphOS 3.8: <br />
:** '''FRAMESCAN=NO''' disables the Reggae framescanning for tracks that have unknown duration. It speeds up the loading of such tracks, but you'll lose the seeking ability with them. <br />
:** '''STREAMBUFFER=YES''' activates the Reggae streambuffer class which reduces stuttering, but causes lag on track change and seeking.<br />
<br />
<br />
=== How to Reduce OWB's HD Writes ===<br />
<br />
: OWB writes a lot of data to the hard drive by default. You might want to reduce it if you're paranoid about SFS fragmentation, filesystem corruption, privacy, or you'd like to avoid certain databases getting too big (which can cause slowdowns). Or you just want your .recycled dir to have other than the OWB files. One option is to use the Private Browsing mode always, but here are tips if you don't want to activate that always or you want to restrict certain writes only.<br />
<br />
:* Disable the TopSites feature. This makes a write for every page you visit, it's an awful amount. Its database (conf/TopSites.db) can also grow to hundreds of megabytes, which causes very noticeable slowdowns to browsing. You can disable it with the "Setenv SAVE OWB_DISABLE_TOPSITES 1" command in the shell, and if the database file has already grown too big, you can remove it.<br />
:* Disable the Website Icons feature. Open the Interface settings and uncheck all Website Icons checkmarks. <br />
:* Disable all saving options from the Privacy settings.<br />
<br />
: If you still need some option enabled, because some site requires it, you can soft link its configuration file to Ram Disk. I, for example, still have Local Storage enabled, but I have linked its dir to ENV: (which resides in Ram Disk). To do that, make LocalStorage directories to both ENV: and ENVARC: (that ensures that it's created after a reboot too), open the shell and cd into your OWB/Conf/ dir, rename or delete the old LocalStorage dir, type "makelink LocalStorage ENV:LocalStorage". Using ENV: gives the advantage to have some files saved so that those settings are restored in every boot. If you're happy with a certain setting, copy the corresponding file to ENVARC: and it will be preserved without being messed up with the later usage. If you just want to have the configuration files enabled, but cleared on every boot, you could soft link them to T: for example.<br />
<br />
<br />
=== Alternative YouTube Script for OWB ===<br />
<br />
: [http://www.morphzone.info/modules/newbb_plus/viewtopic.php?forum=9&topic_id=9799&post_id=109979&viewmode=flat&sortorder=0&showonepost=1 YouTube Center] is a feature rich configureable userscript for improving YouTube experience. It's made for mainstream browsers, but it also works on OWB! All videos can be forced to HTML5 to get them work in OWB. It's heavier than Fab's official OWB script, but works fine as an option or as a backup plan :). Script saves its settings to LocalStorage to #?www.youtube.com#? files.<br />
<br />
: Note: YouTube defaults to the HTML5 player nowadays and you might be fine without any Flash->HTML5 converter scripts. It's probably better to install this script only if you want some other features from it.<br />
<br />
<br />
=== Watching Videos with Less CPU Load in OWB ===<br />
<br />
: When watching a video in OWB, the fullscreen mode makes a lot less CPU load than the default embedded mode, because the fast overlay mode is used then. CPU load may drop from 100% to 40% for example. Wait until the video really starts playing before clicking the fullscreen button on it, or it may fail and you have to reload the video to be able to try it again. Some videos may have a fullscreen option in their contextual menu too. Remember to have Fullscreen Fix scripts added and enabled from the Scripts window ("Windows->Scripts..." pulldown menu entry) for YouTube, Dailymotion, and Vimeo.<br />
<br />
: Note: check that you really have the latest YouTube fullscreen fix script from http://fabportnawak.free.fr/owb/scripts/YouTube_Fullscreen_Fix.js in your OWB/Scripts/ directory. Grunch doesn't get updated for the latest version always for example.<br />
<br />
<br />
=== Problems with YouTube Videos ===<br />
<br />
:* Now that YouTube defaults to HTML5, our days of ad-free videos have ended. It also means that the Content Blocking (AdBlock) option in the OWB's settings can block some videos. If you have some videos which won't start playing, try to disable the Content Blocking option and try again. If that was the problem, but you want to keep the content blocking enabled, add an allow rule to the Content Blocking settings. Open "Windows->Content Blocking..." from the OWB's pulldown menus, click the Add button, and write "youtube.com" to the Rule line. Close the window and try the video again.<br />[[File:OWB_ContentBlockingYT.png]]<br />
<br />
:* If all videos refuse to play, check if you have any YouTube converter scripts enabled in the "Windows->Scripts..." settings. The Fullscreen Fix script is the only one needed and you should disable all converter scripts.<br />
<br />
:* Flash plugins can also break compatibility with YouTube, so if you have the swfdec_plugin.library file in your OWB/Plugins/ directory, you have the following options to choose from:<br />
:** Remove the file from use if you don't need flash anywhere. The plugin doesn't work too well generally anyway.<br />
:** Keep the file, but disable it for all pages by unchecking the "Settings->Preferencfes->Content->Allow plugins" option. You can then enable it temporarily from "Settings->Plugins->Enable" if needed.<br />
:** Disable it temporarily from "Settings->Plugins->Disable", and reload the page.<br />
:** Disable it just for YouTube by adding a new URL setting from "Windows->URL Settings...". Click the Add button, edit the URL line to for example "youtube.com", and uncheck the Plugins option.<br />
<br />
<br />
=== OWB Doesn't Work or Stopped Working with Certain Web Pages ===<br />
<br />
:* Sometimes it helps to change the "Spoof as" setting in OWB. Web pages may offer different kind of content depending on what browser they think you are using. Some popular CAPTCHAs don't work with the default spoofing, but do work when spoofed as iPad for instance. iPad is generally a good option to start trying the spoofing, because you probably get the page in its simpliest form then.<br />
<br />
:* There are some bugs in the JavaScript engine in the latest available OWB version (1.24 at the time of writing) and that causes problems with some web pages, but there's a chance that these pages would still work with an earlier OWB version. You can download earlier OWB versions from [http://fabportnawak.free.fr/owb/ Fab's homepage] and install them, for example, to a different directory than your current OWB installation. There's no problem having two or even several OWB installations on your system, you can just launch whichever you want. As an example, Google Maps stopped working with OWB 1.24 in autumn 2017, but it still continued to work with [http://fabportnawak.free.fr/owb/owb-morphos-1.23.lha OWB 1.23].<br />
<br />
<br />
=== Creating an ISO Image ===<br />
<br />
: Jalapeno can also create and save ISO images which will preserve MorphOS/AmigaOS file attributes and comments. Images can be used for backups or even be booted from USB devices.<br />
<br />
: An option to create an ISO image is found on the pulldown menu in the Burn Files section.<br />
<br />
: [[File:Tips_Create_ISO.png|200px]]<br />
<br />
: If the resulting image file will be bigger than 1GB, Jalapeno splits it into 1GB parts. Those parts can be joined into one big image file with the Join command in the shell, but remember the filesize limits of your target [https://library.morph.zone/Filesystems filesystem] when doing that.<br />
<br />
<br />
=== Copying a CD/DVD to an ISO Image ===<br />
<br />
: If you want to make a standard, easily mountable, ISO image out of an existing CD or DVD, a good way to achieve it is to use the ReadCD program provided with the Jalapeno program on the standard MorphOS installation. Jalapeno itself can also create image files of optical media by selecting "Save as..." from the "Copy Tracks" pull-down menu, but resulting images aren't mountable by the system, because Jalapeno uses options that include more data into the images, for error checking etc.<br />
<br />
: Do these steps from the shell to read a CD/DVD into a standard ISO image:<br />
:# Find your CD drive device by typing: MOSSYS:Data/Jalapeno/readcd -scanbus<br />
:# Create an ISO image by typing (replace "1,1,0" to what you saw in the previous step, and the image path to what you want): MOSSYS:Data/Jalapeno/readcd -dev 1,1,0 f=ram:image.iso<br />
<br />
=== Disabling the Default UTF-8 Mode with Scribble ===<br />
<br />
: Scribble uses UTF-8 encoding by default, but you might prefer to default to the traditional ASCII format instead. The UTF-8 mode can be disabled from the pulldown menu in Scribble, but the setting isn't saved if you save the program settings.<br />
: [[File:Scribble_ascii1.png|128px]]<br />
<br />
: If you want to disable it by default, you have to open the "Save As..." requester, enable the "Make Default" option (also check that Encoding is set to ASCII), and save a file (can be any file anywhere).<br />
: [[File:Scribble_ascii2.png|205px]]<br />
<br />
<br />
== 3rd Party Software ==<br />
<br />
=== Where to Get Software? ===<br />
:* Check [http://library.morph.zone/Links#File_Repositories file repositories] for manual installing<br />
:* [http://www.geit.de/eng_grunch.html Grunch] is a good packet manager for automatic installation and updating of selected software<br />
:* [http://www.meta-morphos.org/WArMUp/chrysalis_en.pdf Chrysalis] is a preconfigured environment and software distribution package ([http://www.warmup-asso.org/download/pack/chrysalis.iso Download ISO image])<br />
<br />
<br />
=== Custom Ambient Menus with AREXX ===<br />
<br />
: You can add own menu items to Ambient pulldown menus with AREXX. Read SYS:MorphOS/Ambient/docs/arexx.txt for more info about AREXX usage or download the [http://morphos-files.net/remote/CRABUM CRABUM] program, which helps you to create correct AREXX lines ([http://library.morph.zone/Getting_Started#Creating_Menus_with_CRABUM tutorial]).<br />
<br />
<br />
=== Help with Shell Commands ===<br />
<br />
: MorphOS Library contains descriptions of all [http://library.morph.zone/Shell_Commands shell commands] and the descriptions can be displayed on the shell with the [http://aminet.net/package/util/batch/Chelp Chelp] script. The script can be used to replace older [http://aminet.net/package/util/cli/Help Help] program (which would otherwise be nice still, but it only contains help for MorphOS 1.x commands).<br />
<br />
<br />
=== Utilizing Your Keyboard's Multimedia Keys ===<br />
<br />
:* The [http://www.geit.de/eng_mmkeyboard.html MMKeyboard] software can be used to assign different kinds of functions to extra keys found on some keyboards.<br />
:* The [http://aminet.net/package/mus/play/MultiMeedio MultiMeedio] script provides a unified control for all popular media players.<br />
<br />
<br />
== Hardware Related ==<br />
<br />
=== Removing Startup Sound on Macs ===<br />
<br />
: Sadly there isn't any known way to disable that annoying startup sound from MorphOS itself or from Open Firmware, but there are few different ways to achieve it anyway.<br />
<br />
:* If you plan to use Mac as MorphOS only system, but you still have OSX installed, you can mute the audio from OSX before wiping it out by installing MorphOS. Startup sound doesn't come back if you won't boot into OSX anymore.<br />
:* If you don't have OSX anymore, you could try to remove sound with some Linux distribution's live/installation CD. More info [http://www.meta-morphos.org/faq.php?id_cat=2&myfaq=yes&categories=Installation+et+d%E9marrage#74 here] and [https://morphosuser.wordpress.com/2014/12/28/removing-the-boot-sound/ here].<br />
:* If you use OSX and MorphOS as a dualboot system you can install [http://www5e.biglobe.ne.jp/~arcana/StartupSound/index.en.html StartupSound.prefPane] for OSX.<br />
<br />
<br />
=== Speeding Up the Startup Manager on Macs ===<br />
<br />
: Startup Manager (the boot menu you get by booting with option/alt key pressed) can be slow when it tries to find network boot devices. To speed it up go to the OF prompt and type "'''setenv skip-netboot? true'''". Funnily enough, it only affects if you have network cable plugged in.<br />
<br />
<br />
=== Booting MorphOS ISO from USB Stick ===<br />
<br />
: MorphOS Team has released an [http://www.morphos-team.net/guide/usb-boot official guide] for USB booting, but I've also noticed that at least some Macs (Mac mini and Powerbook for example) have certain ud alias for USB drive. You can use that as a shortcut and get the booting done with less work (no need to search the correct path, works even when USB stick is in a hub, less typing and less to remember).<br />
<br />
: If you have only one mass storage device connected, you can just boot into Open Firmware prompt (command-alt-o-f) and type:<br />
<br />
: <tt>boot ud:,\boot.img bi umsd0:morphos.iso</tt><br />
<br />
: (Remember to have both boot.img and morphos.iso on the stick)<br />
<br />
<br />
=== Keyboard Reboot on ADB Laptops ===<br />
<br />
: The traditional Ctrl-Command-Command (Ctrl-Amiga-Amiga) keyboard combination doesn't work on laptops using the ADB interface for the keyboard, because ADB doesn't make difference between the left and right command keys. You can reboot them with an alternative Fn-Alt-Alt keyboard combination.<br />
<br />
<br />
=== Blackouts or Graphical Flickering on Mac mini ===<br />
<br />
: Mac minis suffer from short blackouts with some monitors when the connection is made with a DVI cable. The screen gets usually blanked for few seconds, and depending of the monitor it may happen more or less frequently. Issue may also show up as flickering lines on the screen and it may get worse and worse until the monitor is unable to sync to the signal anymore.<br />
<br />
: One option to get around it is to use a VGA adapter/cable, because it doesn't seem to happen with it.<br />
<br />
: An another option is to try to lower the pixel clock value for the used screenmode from the Monitors settings in the MorphOS preferences. If your default mode has for example vertical frequency of 75 Hz, going to 60 Hz mode may help. Sometimes even a small change can help, and lowering just couple clicks from 60 Hz does the trick.<br />
<br />
: This seems to be a common problem with Mac minis and "non-coherent" displays as discussed for example [https://discussions.apple.com/thread/2723110 here].<br />
<br />
<br />
=== Disabling the Internal Touchpad on Laptops ===<br />
==== From the Touchpad Settings (Preferred)====<br />
: An internal touchpad can be disabled from the MorphOS system settings nowadays, and this is the preferred method. Open '''System Settings -> Touchpad''' and disable the '''Enable the Touchpad driver''' setting.<br />
<br />
: [[File:MorphOS_Preferences_disabling_touchpad.png|200px]]<br />
<br />
==== From the USB Settings ====<br />
: The touchpad can be disabled temporarily by removing its binding in the USB settings. This setting is reverted back next time the machine is booted or if USB class scanning is done otherwise.<br />
<br />
: To remove the binding, open the USB settings from the MorphOS Preferences application and go to the Devices list.<br />
:* If you have "Apple Internal Trackpad" alone in the list, you can just select it and click the Unbind button.<br />
:: [[File:Disabling touchpad ibook.png|200px]]<br />
:* If your machine has a combined internal keyboard and trackpad device, double click it ("Apple Internal Keyboard / Trackpad"). Select Touchpad from the newly opened window and then click the Release Binding button.<br />
:: [[File:Disabling touchpad powerbook.png|200px]]<br />
<br />
==== Removing the Driver at Boot Time ====<br />
: Touchpad can also be disabled permanently by removing touchpad.library from use. Removing it is a bit tricky, because it resides in "ROM" and not as a file in system directories, but it can be done with the mf (module filter) boot command argument.<br />
<br />
: The boot command arguments can be edited by editing the bootinfo.txt file on Macs. The bootinfo.txt file is found on the Boot: partition, which also contains the boot.img file. If you don't see the partition, you probably need to mount it first by using, for example, the [[Tools/Mounter | Mounter]] tool. '''Note that if you edit the bootinfo.txt file, you must bless the file with the [[Shell_Commands/HFSSetMacBoot | HFSSetMacBoot]] command or the system won't be bootable anymore!'''<br />
<br />
: To add the mf argument, open the bootinfo.txt file with a text editor, find the line between <BOOT-SCRIPT> and </BOOT-SCRIPT> lines (it starts with "boot"), and add ''mf=touchpad.library'' at the end of the boot line. Save the file and '''remember to bless it with the ''HFSSetMacBoot Boot:bootinfo.txt'' command from the shell or your system won't boot again!'''<br />
<br />
<br />
=== MorphOS Boot Arguments on U-boot Systems ===<br />
: To boot into MorphOS, hardware has to load a MorphOS boot image file that contains the kernel and core drivers. The boot image file also accepts arguments to control the boot procedure before the actual operating system is loaded from the system partition. The boot arguments usage on [[Open Firmware]] systems is well [[Open_Firmware#Boot_Arguments | documented]], but they must be given in a different way on [http://www.intuitionbase.com/static.php?section=uboot U-boot] systems (Sam460ex/cr, AmigaOne X5000).<br />
<br />
: On the U-boot systems the boot arguments have to be set in the '''morphosargs''' environment variable in the U-boot console.<br />
<br />
: To check if you already have the variable set:<br />
: <tt>printenv morphosargs</tt><br />
<br />
: To set an argument (in this example we'd disable an unsupported SCSI controller by removing the SCSI driver from the boot image by using the ''module filter (mf)'' boot argument):<br />
: <tt>setenv morphosargs mf=symbios.device</tt><br />
: <tt>saveenv</tt><br />
<br />
: To edit an existing variable:<br />
: <tt>editenv morphosargs</tt><br />
: <tt>saveenv</tt></div>
JPV
https://library.morph.zone/index.php?title=Filesystems&diff=4314
Filesystems
2023-07-06T09:56:46Z
<p>JPV: Updated some links</p>
<hr />
<div>== About ==<br />
This page collects information about file systems working natively under MorphOS. In addition to these, Amiga 68k file systems can be used too ([[Preparing_an_Amiga_Hard_Drive|example]]).<br />
<br />
'''NOTE: this page is still under construction and many values would need to be verified!''' Any feedback is welcome to this [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12144&forum=3 thread].<br />
<br />
== Disk File Systems ==<br />
<br />
{| class="wikitable"<br />
! style="text-align:left;"| Name<br />
! style="text-align:left;"| Location<br />
! style="text-align:left;"| Bootable<br />
! style="text-align:left;"| Native File Properties<br />
! style="text-align:left;"| Max File Name Length<br />
! style="text-align:left;"| Max File Size<br />
! style="text-align:left;"| Max Partition Size<br />
! style="text-align:left;"| Notes<br />
|-<br />
| Smart File System (SFS)<br />
| Built-in (boot.img)<br />
| Yes<br />
| Yes<br />
| 107<br />
| 4 GiB - 2 bytes<br />
| 128 GiB<br />
| The default file system<br />
|-<br />
| Professional File System III (PFS3)<br />
| Built-in (boot.img)<br />
| Yes<br />
| Yes<br />
| 107<br />
| 2 GiB<br />
| 104 GiB<br />
| Legacy support for PFS2 and AFS1<br />
|-<br />
| Fast File System 2 (FFS)<br />
| Built-in (boot.img)<br />
| Yes<br />
| Yes<br />
| 107<br />
| 4 GiB - 2 bytes<br />
| 2 TiB to 128 TiB<br />
| Legacy support for OFS and FFS<br />
|-<br />
| FAT File System (FAT)<br />
| Built-in (boot.img)<br />
| Yes<br />
| No<br />
| 255* (UCS-2)<br />
| 4 GiB<br />
| 2 TiB<br />
| Supports FAT12, FAT16, and FAT32 with LFN<br />
|-<br />
| Mac File System (HFS)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 31<br />
| 2 GiB<br />
| 2 TiB<br />
|<br />
|-<br />
| Hierarchical File System (HFS+)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 255* (UTF-16) <br />
| 2 TiB**<br />
| 2 TiB**<br />
| Read-only<br />
|-<br />
| Second Extended File System (ext2, ext3, ext4)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 255*<br />
| 16 GiB to 2 TiB<br />
| 2 TiB<br />
| Limited read-only support for ext4<br />
|-<br />
| NT File System (NTFS)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 255*<br />
| 2 TiB**<br />
| 2 TiB**<br />
| Read-only<br />
|-<br />
| SGI X File System (XFS)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 255*<br />
| 2 TiB**<br />
| 2 TiB**<br />
| Read-only<br />
|-<br />
| Ice File System (IceFS)<br />
| 3rd party ([http://blubbedev.net/icefs/ link])([https://www.morphos-storage.net/?find=ice-fs link2])<br />
| Yes/No<br />
| Yes<br />
| 107 (255)<br />
| 9 EB<br />
| 9 EB<br />
| Bootable on Pegasos and Efika, but not on Macs<br />
|-<br />
| ExFAT File System (ExFAT)<br />
| 3rd party ([https://www.morphos-storage.net/?find=exfat link])<br />
| No<br />
| No<br />
| 255 UTF-16<br />
| 128 PiB<br />
| 128 PiB<br />
| <br />
|-<br />
| NT File System 3G (NTFS-3G)<br />
| 3rd party ([http://blubbedev.net/filesysbox/ link])([https://www.morphos-storage.net/?find=ntfs link2])<br />
| No<br />
| No<br />
| 255<br />
| 16 EiB<br />
| 16 EiB<br />
| Can't be placed on RDB<br />
|-<br />
| FS1541<br />
| 3rd party ([http://aminet.net/package/disk/misc/FS1541-MorphOS link])<br />
| No<br />
| No<br />
| 16<br />
| 164 KiB<br />
| 170 KiB<br />
| For CBM 1541 disks/images<br />
|-<br />
| CDRive File System (CDFS)<br />
| Built-in (boot.img)<br />
| Yes<br />
| Yes<br />
| 255*<br />
| <br />
| <br />
| ISO 9660/Amiga Rock Ridge/Joliet, audio as WAV files, ISO file support<br />
|}<br />
<br />
<nowiki>* </nowiki>Filenames over 107 characters will be stripped<br />
<br />
<nowiki>** </nowiki>Theoretical sizes may be bigger, but filesystems using deviceio.library are limited to 2 TiB<br />
<br />
== Network File Systems ==<br />
<br />
{| class="wikitable"<br />
! style="text-align:left;"| Name<br />
! style="text-align:left;"| Location<br />
! style="text-align:left;"| Native File Properties<br />
! style="text-align:left;"| Notes<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#SmbFS SmbFS]<br />
| Built-in (MOSSYS:C)<br />
| No<br />
| For mounting Windows shares or Samba shares (SMB1) on other platforms<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#Smb2FS Smb2FS]<br />
| Built-in (MOSSYS:C)<br />
| No<br />
| For mounting Windows shares or Samba shares (SMB2/3) on other platforms<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#Ssh2FS Ssh2FS]<br />
| Built-in (MOSSYS:C)<br />
| No<br />
| For mounting SFTP shares on other platforms<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#NetFS_Revised NetFS Revised]<br />
| 3rd party ([http://aminet.net/package/comm/net/NetFS-revised link])<br />
| Yes<br />
| For mounting partitions between MorphOS and/or AmigaOS systems<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#FTPMount FTPMount]<br />
| 3rd party ([http://aminet.net/package/comm/tcp/FTPMount_MOS link])<br />
| No<br />
| For mounting FTP sites as part of a filesystem<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#Google_Drive_and_Dropbox_Handlers Amiga Cloud Handlers]<br />
| 3rd party ([http://aminet.net/package/comm/tcp/AmigaCloudHandlers link])<br />
| No<br />
| For mounting Google Drive and Dropbox storage<br />
|}</div>
JPV
https://library.morph.zone/index.php?title=Main_Page&diff=4311
Main Page
2023-06-05T14:10:25Z
<p>JPV: /* Articles */</p>
<hr />
<div>__NOTOC__<br />
<br />
<div id="siteLogo" style="float: right;"></div><br />
<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#274572;">Welcome to the MorphOS Library,</div><br />
<div style="top:+0.2em; font-size:95%; margin-bottom: 30px;">the wiki based library of MorphOS related documentation.</div><br />
<br />
<strong>Would you like to contribute and edit articles?</strong><br><br />
Please contact us to set up an account via:<br />
<div style="margin-top: -10px; margin-bottom: 20px;">https://morph.zone/message2library.png</div><br />
'''Important notes to editors:''' [[Basic Guidelines]] - [[List of Wanted Articles]]<br />
----<br />
<small>This page in other languages: [[Strona główna|Polish]] [[Page principale|Français]]</small><br />
<br />
==About MorphOS==<br />
MorphOS - The Lightning OS<br />
<div class="threecolumns"><br />
* [[What is MorphOS?]]<br />
* [[Hardware Platforms]]<br />
* [[Installation]]<br />
* [[Characteristic features]]<br />
* [[MorphOS integration]]<br />
* [[MorphOS Development]]<br />
* [[Developer tools]]<br />
* [[3D graphics]]<br />
* [[Games]]<br />
* [[MorphOS key applications]]<br />
* [[Platform expansion]]<br />
* [[Who needs MorphOS?]]<br />
* [[Conclusions]]<br />
* [[Useful links]]<br />
* [[F.A.Q.]]<br />
* [[Historical notes]]<br />
* [[Contributors]]</div><br />
A five minute read for users familiar with the Commodore Amiga<br />
*[[MorphOS in 5 minutes]]<br />
<br />
==Articles==<br />
The core of the MorphOS Library can be found here. Along with the provided manuals, there are several documents designed to help users get the most out of their MorphOS powered computer.<br />
<br />
* [[Fundamentals of MorphOS]]<br />
* [[Dictionary of Terms]]<br />
* [[First_Steps_Using_MorphOS | First Steps Using MorphOS]]<br />
* [[Volume Names]]<br />
* [[Applications|Applications Included with MorphOS]]<br />
* [[Tools|Tools Included with MorphOS]]<br />
* [[Utilities|Utilities Included with MorphOS]]<br />
* [[Screenbar_Modules|Screenbar Modules Included with MorphOS]]<br />
* [[Bundled_Games|Games Included with MorphOS]]<br />
* [[Blankers|Blankers Included with MorphOS]]<br />
* [[Shell Commands|Shell: Commands]]<br />
* [[Pattern matching|Shell: Pattern Matching]]<br />
* [[Filesystems | File Systems]]<br />
* [[Supported Computers]]<br />
* [[Hardware Compatibility]]<br />
* [[MIDI | MIDI Support]]<br />
* [[Tips and Tricks]]<br />
<br />
==Tutorials==<br />
Welcome to the Tutorials section of the MorphOS Library. In this aisle of the library you can find examples and step by step instructions to help get the most out of your MorphOS experience.<br />
<br />
*[[Getting_Started | Getting Started - A Beginner's Guide to MorphOS]]<br />
*[[Modifying the User-Startup file]]<br />
*[[Configuring_Network | Configuring a Network Connection]]<br />
*[[Installing_software | Installing Third Party Software]]<br />
*[[Dual-boot MorphOS and MacOS X on a Mac Mini G4]]<br />
*[[How to write Mails with SimpleMail]]<br />
*[[Creating Backups]]<br />
*[[MorphOS External USB Drive Backup Guide]]<br />
*[[Scanning with SCANdal]]<br />
*[[Recording an LP with Audio Evolution 4]]<br />
*[[Passwordless SSH login with RemoteShell]]<br />
*[[How to Install Directory Opus Magellan II]]<br />
*[[How to Make MorphOS Look Like OS4]]<br />
*[[How to Use Game Controllers]]<br />
*[[Preparing_an_Amiga_Hard_Drive]]<br />
*[[Mounting_Network_Drives]]<br />
*[[How to translate program with SimpleCat]]<br />
*[[Creating_Ambient_Filetypes]]<br />
*[[Open_Firmware | Using Open Firmware]]<br />
*[[Print_System | Using the New Printing System]]<br />
*[[Multi-display | Using Multi-display Setups]]<br />
<br />
==Development==<br />
In the development section of the MorphOS Library, you can find a collection of helpful articles and tutorials focused on MorphOS software development.<br />
<br />
*[[First steps in MorphOS programming]]<br />
*[[Magic User Interface Programming]]<br />
*[[In-depth: The New MorphOS Memory System]]<br />
*[[Reggae: MorphOS multimedia framework]]<br />
*[[An Introduction to MorphOS PPC Assembly]]<br />
*[[Advanced Topics]]<br />
*[[Getting Started with Lua]]<br />
*[[Crash_Course_to_Hollywood_Programming]]<br />
<br />
==Benchmarks, Reports & Reviews==<br />
*[[jPV's MorphOS 2 Review]]<br />
*[[What's New in MorphOS 3]]<br />
*[[What's New in MorphOS 3.10]]<br />
*[[What's New in MorphOS 3.16]]<br />
<br />
==Links==<br />
The MorphOS Link Database is a collection of websites that are of interest to all current and potential future users of MorphOS. For easier navigation, we have separated the list of websites into multiple categories.<br />
<br />
*[[Links#Community_Portals_.26_Forums|Community Portals]]<br />
*[[Links#File_Repositories|File Repositories]]<br />
*[[Links#Shops|Shops]]<br />
*[[Links#Software|Software]]<br />
*[[Links#Developers|Developers]]<br />
*[[Links#Misc|Misc]]<br />
<br />
==Work in Progress==<br />
*[[ReTooled]]</div>
JPV
https://library.morph.zone/index.php?title=MIDI&diff=4310
MIDI
2023-06-05T14:07:04Z
<p>JPV: </p>
<hr />
<div>''Author: Antoine Dubourg'' - ''Proof-reading: Neil Pearson''<br />
<br />
MorphOS is able to make use of the MIDI protocol with various system components.<br />
<br />
To make best use of MIDI, it is advised to have some MIDI instruments be it physical devices or soft synthesis.<br />
<br />
== Low level components ==<br />
All the MIDI intricacies are handled by two system components:<br />
* '''camd.library''', which handles message parsing and delivery to applications<br />
* '''camdusbmidi.class''', which bridges MIDI messages from USB compliant MIDI devices to camd.library<br />
<br />
''camd.library'' is located in ''SYS:MorphOS/Libs/'' while ''camdusbmidi.class'' is located in ''SYS:MorphOS/Classes/USB/''.<br />
<br />
=== CAMD concepts ===<br />
CAMD library was designed in the 90s using the concept of delivery by copying of MIDI messages.<br />
<br />
When an application wants to use MIDI, it creates a ''MidiNode'', which is a type of area for storing messages.<br />
<br />
Once ''MidiNode'' is created by the application, this node is then linked to its destination name, the MIDI cluster.<br />
<br />
''MidiLink'' can be only a single type: sending or receiving. So, an application will send MIDI messages while some will receive MIDI messages. Some might do both.<br />
<br />
All the mechanics of CAMD is based around MIDI clusters: they provide a user friendly way to promote MIDI flux. Usually, clusters are presented to <br />
a user to configure access to MIDI instruments.<br />
<br />
Instrument(s) and application(s) can be started in any order. The cluster name is a collection point created by the first one joining the cluster.<br />
<br />
=== Understanding the MIDI cluster naming scheme ===<br />
When a MIDI instrument is connected to CAMD, it 'registers' itself to a MIDI cluster using a specific naming scheme.<br />
<br />
Usually, an instrument will create a two way communication link, one for sending MIDI messages and another one for receiving MIDI messages.<br />
<br />
The cluster name ending with '.out' is used to send MIDI messages '''to''' the instrument.<br />
<br />
The cluster name ending with .'in' is used to receive MIDI messages '''from''' the instrument.<br />
<br />
Those '.in' and '.out' are usually prefixed with a name. For example, you have a MIDI instrument of whatever brand, which will usually be shown similar to 'Brand-DeviceName.in' and 'Brand-DeviceName.out'.<br />
<br />
== Installing & testing MIDI gear ==<br />
Initial, first time, setup of MIDI gear can be quite intimidating. It has to be correctly wired if connected using legacy DIN connectors (inverting<br />
in and out isn't dangerous at all, it will just not work) and figuring out how to use an application often requires some getting used to.<br />
<br />
MorphOS features two handy applications that can help with testing and boot-strapping MIDI gear:<br />
<br />
* [[Utilities/MIDIPiano | MIDI Piano]], is a simple virtual MIDI keyboard for sending or receiving MIDI messages<br />
* [[Utilities/MIDI_Logger | MIDI Logger]], a tool for looking at MIDI messages<br />
<br />
Both tools are located in SYS:Utilities/MIDI/.<br />
<br />
== Using Virtual MIDI Keyboard ==<br />
Run it by double-clicking the [[Utilities/MIDIPiano | MIDI Piano]] icon. You'll get a window with a large piano keyboard. VMK (Virtual MIDI Keyboard) is able to receive or send MIDI messages.<br />
<br />
# Select the mode of operation with the first cycle, 'Receive' for ... receiving MIDI messages, 'Send' for ... you guessed it, sending MIDI messages.<br />
# Select the cluster to connect to. If you're sending, be sure to select a cluster with a name ending in '.out'. Inversly, select an '.in' cluster for receiving.<br />
# Select to which MIDI channels you want to send/receive MIDI messages. VMK will happily send/receive from multiple MIDI channels at once.<br />
# a) If you are in receive mode, the piano keyboard won't react to mouse events but will colour the keys as/when receiving note events from the cluster.<br>b) If in send mode, the piano keyboard will react to mouse event(s): clicking on the piano keys will emit MIDI messages to the selected cluster.<br />
<br />
'''Tip''': The MIDI instrument keeps emitting an annoying sound? <br />
If so, then send an 'All Notes Off' message with 'Send a MIDI message' using that menu option.<br />
<br />
== Using MIDI Logger ==<br />
[[Utilities/MIDI_Logger | MIDI Logger]] is an analysis tool for watching incoming MIDI messages. It is most helpful for debugging an application, or to simply check MIDI messages.<br />
<br />
This application is only able to receive MIDI messages.<br />
<br />
# Select the cluster you'd like to receive from<br />
# Select channels you'd like to view<br />
# Select the kind of MIDI message you'd like to view<br />
<br />
Any message meeting your filter criteria will be displayed in the list.<br />
<br />
== Playing a MIDI file ==<br />
MorphOS features a MIDI playback tool wisely named [[Shell_Commands/PlayMidi | PlayMIDI]]. This is a Shell only tool that features the minimum for playback '.smf' MIDI files.<br />
<br />
It takes a FILE argument that should point to a valid '.smf' MIDI file and a CLUSTERNAME argument that should point to an '.out' cluster name.<br />
<br />
For example:<br />
<br />
PlayMIDI FILE=song.smf CLUSTERNAME=myinstrument.out<br />
<br />
The song will be sent to the 'myinstrument.out' cluster.<br />
<br />
== Soft Synthesis ==<br />
MorphOS does not feature any soft synthesis application for MIDI. You'll have to rely on an external application for that. One tool is available for<br />
doing soft synthesis: FrozenLiquid (available at the [https://tcheko.binaryriot.org developer's page] or [https://www.morphos-storage.net/?find=frozenliquid MorphOS Storage]).<br />
<br />
FrozenLiquid needs a sound font for producing sound. Sound fonts are easy to find with any search engine.<br />
<br />
Soft synthesis is producing sound with the help of the CPU. It can consume a large amount of CPU capability depending on the number of MIDI events required to process, and the complexity of the sound font.<br />
<br />
Starting FrozenLiquid is just a single step:<br />
<br />
FrozenLiquid FILE=soundfontname.sf2<br />
<br />
By default, FrozenLiquid will create a MIDI cluster based on the filename of the sound font.<br />
<br />
With PlayMIDI and FrozenLiquid, you can experience MIDI without owning any actual hardware based MIDI instrument.</div>
JPV
https://library.morph.zone/index.php?title=MIDI&diff=4309
MIDI
2023-06-01T16:48:09Z
<p>JPV: </p>
<hr />
<div>''Author: Antoine Dubourg''<br />
<br />
MorphOS is able to make use of the MIDI protocol with various system components.<br />
<br />
To make best use of MIDI, it is advised to have some MIDI instruments be it physical devices or soft synthesis.<br />
<br />
== Low level components ==<br />
All the MIDI intricacies are handled by two system components:<br />
* '''camd.library''', which handles message parsing and delivery to applications<br />
* '''camdusbmidi.class''', which bridges MIDI messages from USB compliant MIDI devices to camd.library<br />
<br />
''camd.library'' is located in ''SYS:MorphOS/Libs/'' while ''camdusbmidi.class'' is located in ''SYS:MorphOS/Classes/USB/''.<br />
<br />
=== CAMD concepts ===<br />
CAMD library was designed in the 90s using the concept of delivery by copying of MIDI messages.<br />
<br />
When an application wants to use MIDI, it creates a ''MidiNode'', which is a type of area for storing messages.<br />
<br />
Once ''MidiNode'' is created by the application, this node is then linked to its destination name, the MIDI cluster.<br />
<br />
''MidiLink'' can be only a single type: sending or receiving. So, an application will send MIDI messages while some will receive MIDI messages. Some might do both.<br />
<br />
All the mechanics of CAMD is based around MIDI clusters: they provide a user friendly way to promote MIDI flux. Usually, clusters are presented to <br />
a user to configure access to MIDI instruments.<br />
<br />
Instrument(s) and application(s) can be started in any order. The cluster name is a collection point created by the first one joining the cluster.<br />
<br />
=== Understanding the MIDI cluster naming scheme ===<br />
When a MIDI instrument is connected to CAMD, it 'registers' itself to a MIDI cluster using a specific naming scheme.<br />
<br />
Usually, an instrument will create a two way communication link, one for sending MIDI messages and another one for receiving MIDI messages.<br />
<br />
The cluster name ending with '.out' is used to send MIDI messages '''to''' the instrument.<br />
<br />
The cluster name ending with .'in' is used to receive MIDI messages '''from''' the instrument.<br />
<br />
Those '.in' and '.out' are usually prefixed with a name. For example, you have a MIDI instrument of whatever make, which will usually be shown similar to 'Brand-DeviceName.in' and 'Brand-DeviceName.out'.<br />
<br />
== Installing & testing MIDI gear ==<br />
Initial, first time, setup of MIDI gear can be quite intimidating. It has to be correctly wired if connected using legacy DIN connectors (inverting<br />
in and out isn't dangerous at all, it will just not work) and figuring out how to use an application often requires some getting used to.<br />
<br />
MorphOS features two handy applications that can help with testing and boot-strapping MIDI gear:<br />
<br />
* [[Utilities/MIDIPiano | MIDI Piano]], is a simple virtual MIDI keyboard for sending or receiving MIDI messages<br />
* [[Utilities/MIDI_Logger | MIDI Logger]], a tool for looking at MIDI messages<br />
<br />
Both tools are located in SYS:Utilities/MIDI/.<br />
<br />
== Using Virtual MIDI Keyboard ==<br />
Run it by double-clicking the [[Utilities/MIDIPiano | MIDI Piano]] icon. You'll get a window with a large piano keyboard. VMK (Virtual MIDI Keyboard) is able to receive or send MIDI messages.<br />
<br />
# Select the mode of operation with the first cycle, 'Receive' for ... receiving MIDI messages, 'Send' for ... you guessed it, sending MIDI messages.<br />
# Select the cluster to connect to. If you're sending, be sure to select a cluster with a name ending in '.out'. Inversly, select an '.in' cluster for receiving.<br />
# Select to which MIDI channels you want to send/receive MIDI messages. VMK will happily send/receive from multiple MIDI channels at once.<br />
# a) If you are in receive mode, the piano keyboard won't react to mouse events but will colour the keys as/when receiving note events from the cluster.<br>b) If in send mode, the piano keyboard will react to mouse event(s): clicking on the piano keys will emit MIDI messages to the selected cluster.<br />
<br />
'''Tip''': The MIDI instrument keeps emitting an annoying sound? <br />
If so, then send an 'All Notes Off' message with 'Send a MIDI message' using that menu option.<br />
<br />
== Using MIDI Logger ==<br />
[[Utilities/MIDI_Logger | MIDI Logger]] is an analysis tool for watching incoming MIDI messages. It is most helpful for debugging an application, or to simply check MIDI messages.<br />
<br />
This application is only able to receive MIDI messages.<br />
<br />
# Select the cluster you'd like to receive from<br />
# Select channels you'd like to view<br />
# Select the kind of MIDI message you'd like to view<br />
<br />
Any message meeting your filter criteria will be displayed in the list.<br />
<br />
== Playing a MIDI file ==<br />
MorphOS features a MIDI playback tool wisely named [[Shell_Commands/PlayMidi | PlayMIDI]]. This is a Shell only tool that features the minimum for playback '.smf' MIDI files.<br />
<br />
It takes a FILE argument that should point to a valid '.smf' MIDI file and a CLUSTERNAME argument that should point to an '.out' cluster name.<br />
<br />
For example:<br />
<br />
PlayMIDI FILE=song.smf CLUSTERNAME=myinstrument.out<br />
<br />
The song will be sent to the 'myinstrument.out' cluster.<br />
<br />
== Soft Synthesis ==<br />
MorphOS does not feature any soft synthesis application for MIDI. You'll have to rely on an external application for that. One tool is available for<br />
doing soft synthesis: FrozenLiquid (available at the [https://tcheko.binaryriot.org developer's page] or [https://www.morphos-storage.net/?find=frozenliquid MorphOS Storage]).<br />
<br />
FrozenLiquid needs a sound font for producing sound. Sound fonts are easy to find with any search engine.<br />
<br />
Soft synthesis is producing sound with the help of the CPU. It can consume a large amount of CPU capability depending on the number of MIDI events required to process, and the complexity of the sound font.<br />
<br />
Starting FrozenLiquid is just a single step:<br />
<br />
FrozenLiquid FILE=soundfontname.sf2<br />
<br />
By default, FrozenLiquid will create a MIDI cluster based on the filename of the sound font.<br />
<br />
With PlayMIDI and FrozenLiquid, you can experience MIDI without owning any actual (hardware based) MIDI instrument.</div>
JPV
https://library.morph.zone/index.php?title=MIDI&diff=4308
MIDI
2023-06-01T16:46:12Z
<p>JPV: </p>
<hr />
<div>MorphOS is able to make use of the MIDI protocol with various system components.<br />
<br />
To make best use of MIDI, it is advised to have some MIDI instruments be it physical devices or soft synthesis.<br />
<br />
== Low level components ==<br />
All the MIDI intricacies are handled by two system components:<br />
* '''camd.library''', which handles message parsing and delivery to applications<br />
* '''camdusbmidi.class''', which bridges MIDI messages from USB compliant MIDI devices to camd.library<br />
<br />
''camd.library'' is located in ''SYS:MorphOS/Libs/'' while ''camdusbmidi.class'' is located in ''SYS:MorphOS/Classes/USB/''.<br />
<br />
=== CAMD concepts ===<br />
CAMD library was designed in the 90s using the concept of delivery by copying of MIDI messages.<br />
<br />
When an application wants to use MIDI, it creates a ''MidiNode'', which is a type of area for storing messages.<br />
<br />
Once ''MidiNode'' is created by the application, this node is then linked to its destination name, the MIDI cluster.<br />
<br />
''MidiLink'' can be only a single type: sending or receiving. So, an application will send MIDI messages while some will receive MIDI messages. Some might do both.<br />
<br />
All the mechanics of CAMD is based around MIDI clusters: they provide a user friendly way to promote MIDI flux. Usually, clusters are presented to <br />
a user to configure access to MIDI instruments.<br />
<br />
Instrument(s) and application(s) can be started in any order. The cluster name is a collection point created by the first one joining the cluster.<br />
<br />
=== Understanding the MIDI cluster naming scheme ===<br />
When a MIDI instrument is connected to CAMD, it 'registers' itself to a MIDI cluster using a specific naming scheme.<br />
<br />
Usually, an instrument will create a two way communication link, one for sending MIDI messages and another one for receiving MIDI messages.<br />
<br />
The cluster name ending with '.out' is used to send MIDI messages '''to''' the instrument.<br />
<br />
The cluster name ending with .'in' is used to receive MIDI messages '''from''' the instrument.<br />
<br />
Those '.in' and '.out' are usually prefixed with a name. For example, you have a MIDI instrument of whatever make, which will usually be shown similar to 'Brand-DeviceName.in' and 'Brand-DeviceName.out'.<br />
<br />
== Installing & testing MIDI gear ==<br />
Initial, first time, setup of MIDI gear can be quite intimidating. It has to be correctly wired if connected using legacy DIN connectors (inverting<br />
in and out isn't dangerous at all, it will just not work) and figuring out how to use an application often requires some getting used to.<br />
<br />
MorphOS features two handy applications that can help with testing and boot-strapping MIDI gear:<br />
<br />
* [[Utilities/MIDIPiano | MIDI Piano]], is a simple virtual MIDI keyboard for sending or receiving MIDI messages<br />
* [[Utilities/MIDI_Logger | MIDI Logger]], a tool for looking at MIDI messages<br />
<br />
Both tools are located in SYS:Utilities/MIDI/.<br />
<br />
== Using Virtual MIDI Keyboard ==<br />
Run it by double-clicking the [[Utilities/MIDIPiano | MIDI Piano]] icon. You'll get a window with a large piano keyboard. VMK (Virtual MIDI Keyboard) is able to receive or send MIDI messages.<br />
<br />
# Select the mode of operation with the first cycle, 'Receive' for ... receiving MIDI messages, 'Send' for ... you guessed it, sending MIDI messages.<br />
# Select the cluster to connect to. If you're sending, be sure to select a cluster with a name ending in '.out'. Inversly, select an '.in' cluster for receiving.<br />
# Select to which MIDI channels you want to send/receive MIDI messages. VMK will happily send/receive from multiple MIDI channels at once.<br />
# a) If you are in receive mode, the piano keyboard won't react to mouse events but will colour the keys as/when receiving note events from the cluster.<br>b) If in send mode, the piano keyboard will react to mouse event(s): clicking on the piano keys will emit MIDI messages to the selected cluster.<br />
<br />
'''Tip''': The MIDI instrument keeps emitting an annoying sound? <br />
If so, then send an 'All Notes Off' message with 'Send a MIDI message' using that menu option.<br />
<br />
== Using MIDI Logger ==<br />
[[Utilities/MIDI_Logger | MIDI Logger]] is an analysis tool for watching incoming MIDI messages. It is most helpful for debugging an application, or to simply check MIDI messages.<br />
<br />
This application is only able to receive MIDI messages.<br />
<br />
# Select the cluster you'd like to receive from<br />
# Select channels you'd like to view<br />
# Select the kind of MIDI message you'd like to view<br />
<br />
Any message meeting your filter criteria will be displayed in the list.<br />
<br />
== Playing a MIDI file ==<br />
MorphOS features a MIDI playback tool wisely named [[Shell_Commands/PlayMidi | PlayMIDI]]. This is a Shell only tool that features the minimum for playback '.smf' MIDI files.<br />
<br />
It takes a FILE argument that should point to a valid '.smf' MIDI file and a CLUSTERNAME argument that should point to an '.out' cluster name.<br />
<br />
For example:<br />
<br />
PlayMIDI FILE=song.smf CLUSTERNAME=myinstrument.out<br />
<br />
The song will be sent to the 'myinstrument.out' cluster.<br />
<br />
== Soft Synthesis ==<br />
MorphOS does not feature any soft synthesis application for MIDI. You'll have to rely on an external application for that. One tool is available for<br />
doing soft synthesis: FrozenLiquid (available at the [https://tcheko.binaryriot.org developer's page] or [https://www.morphos-storage.net/?find=frozenliquid MorphOS Storage]).<br />
<br />
FrozenLiquid needs a sound font for producing sound. Sound fonts are easy to find with any search engine.<br />
<br />
Soft synthesis is producing sound with the help of the CPU. It can consume a large amount of CPU capability depending on the number of MIDI events required to process, and the complexity of the sound font.<br />
<br />
Starting FrozenLiquid is just a single step:<br />
<br />
FrozenLiquid FILE=soundfontname.sf2<br />
<br />
By default, FrozenLiquid will create a MIDI cluster based on the filename of the sound font.<br />
<br />
With PlayMIDI and FrozenLiquid, you can experience MIDI without owning any actual (hardware based) MIDI instrument.</div>
JPV
https://library.morph.zone/index.php?title=MIDI&diff=4307
MIDI
2023-06-01T14:02:32Z
<p>JPV: An article by Antoine Dubourg, proof-reading by Neil Pearson</p>
<hr />
<div>MorphOS is able to make use of the MIDI protocol with various system components.<br />
<br />
To make best use of MIDI, it is advised to have some MIDI instruments be it physical devices or soft synthesis.<br />
<br />
== Low level components ==<br />
All the MIDI intricacies are handled by two system components:<br />
* camd.library, which handles message parsing and delivery to applications<br />
* camdusbmidi.class, which bridges MIDI messages from USB compliant MIDI devices to camd.library<br />
<br />
camd.library is located in SYS:MorphOS/Libs while camdusbmidi.class is located in SYS:MorphOS/Classes/USB.<br />
<br />
=== CAMD concepts ===<br />
CAMD library was designed in the 90s using the concept of delivery by copying of MIDI messages.<br />
<br />
When an application wants to use MIDI, it creates a 'MidiNode', which is a type of area for storing messages.<br />
<br />
Once MidiNode is created by the application, this node is then linked to its destination name, the MIDI cluster.<br />
<br />
MidiLink can be only a single type: sending or receiving. So, an application will send MIDI messages while some will receive MIDI messages. Some might do both.<br />
<br />
All the mechanics of CAMD is based around MIDI clusters: they provide a user friendly way to promote MIDI flux. Usually, clusters are presented to <br />
a user to configure access to MIDI instruments.<br />
<br />
Instrument(s) and application(s) can be started in any order. The cluster name is a collection point created by the first one joining the cluster.<br />
<br />
=== Understanding the MIDI cluster naming scheme ===<br />
When a MIDI instrument is connected to CAMD, it 'registers' itself to a MIDI cluster using a specific naming scheme.<br />
<br />
Usually, an instrument will create a two way communication link, one for sending MIDI messages and another one for receiving MIDI messages.<br />
<br />
The cluster name ending with '.out' is used to send MIDI messages TO the instrument.<br />
<br />
The cluster name ending with .'in' is used to receive MIDI messages FROM the instrument.<br />
<br />
Those '.in' and '.out' are usually prefixed with a name. For example, you have a MIDI instrument of whatever make, which will usually be shown similar to 'Brand-DeviceName.in' and 'Brand-DeviceName.out'.<br />
<br />
== Installing & testing MIDI gear ==<br />
Initial, first time, setup of MIDI gear can be quite intimidating. It has to be correctly wired if connected using legacy DIN connectors (inverting<br />
in and out isn't dangerous at all, it will just not work) and figuring out how to use an application often requires some getting used to.<br />
<br />
MorphOS features two handy applications that can help with testing and boot-strapping MIDI gear:<br />
<br />
- Virtual MIDI Keyboard, is a simple visual keyboard for sending or receiving MIDI messages,<br />
<br />
- MIDI Logger, a tool for looking at MIDI messages.<br />
<br />
Both tools are located in SYS:Tools/MIDI.<br />
<br />
== Using Virtual MIDI Keyboard ==<br />
Run it by double-clicking its icon. You'll get a window with a large piano keyboard. VMK (Virtual MIDI Keyboard) is able to receive or send MIDI messages.<br />
<br />
1. Select the mode of operation with the first cycle, 'Receive' for ... receiving MIDI messages, 'Send' for ... you guessed it, sending MIDI messages.<br />
<br />
2. Select the cluster to connect to. If you're sending, be sure to select a cluster with a name ending in '.out'. Inversly, select an '.in' cluster for receiving.<br />
<br />
3. Select to which MIDI channels you want to send/receive MIDI messages. VMK will happily send/receive from multiple MIDI channels at once.<br />
<br />
4a. If you are in receive mode, the piano keyboard won't react to mouse events but will colour the keys as/when receiving note events from the cluster.<br />
<br />
4b. If in send mode, the piano keyboard will react to mouse event(s): clicking on the piano keys will emit MIDI messages to the selected cluster.<br />
<br />
'''Tip''': The MIDI instrument keeps emitting an annoying sound? <br />
If so, then send an 'All Notes Off' message with 'Send a MIDI message' using that menu option.<br />
<br />
== Using MIDI Logger ==<br />
MIDI Logger is an analysis tool for watching incoming MIDI messages. It is most helpful for debugging an application, or to simply check MIDI messages.<br />
<br />
This application is only able to receive MIDI messages.<br />
<br />
1. Select the cluster you'd like to receive from<br />
<br />
2. Select channels you'd like to view<br />
<br />
3. Select the kind of MIDI message you'd like to view<br />
<br />
Any message meeting your filter criteria will be displayed in the list.<br />
<br />
== Playing a MIDI file ==<br />
MorphOS features a MIDI playback tool wisely named PlayMIDI. This is a Shell only tool that features the minimum for playback '.smf' MIDI files.<br />
<br />
It takes a FILE argument that should point to a valid '.smf' MIDI file and a CLUSTERNAME argument that should point to an '.out' cluster name.<br />
<br />
For example:<br />
<br />
PlayMIDI FILE=song.smf CLUSTERNAME=myinstrument.out<br />
<br />
The song will be sent to the 'myinstrument.out' cluster.<br />
<br />
See PlayMIDI (MZ library link to PlayMIDI page)<br />
<br />
== Soft Synthesis ==<br />
MorphOS does not feature any soft synthesis application for MIDI. You'll have to rely on an external application for that. One tool is available for<br />
doing soft synthesis: FrozenLiquid (available at https://tcheko.binaryriot.org or MorphOS Storage).<br />
<br />
FrozenLiquid needs a sound font for producing sound. Sound fonts are easy to find with any search engine.<br />
<br />
Soft synthesis is producing sound with the help of the CPU. It can consume a large amount of CPU capability depending on the number of MIDI events required to process, and the complexity of the sound font.<br />
<br />
Starting FrozenLiquid is just a single step:<br />
<br />
FrozenLiquid FILE=soundfontname.sf2<br />
<br />
By default, FrozenLiquid will create a MIDI cluster based on the filename of the sound font.<br />
<br />
With PlayMIDI and FrozenLiquid, you can experience MIDI without owning any actual (hardware based) MIDI instrument.</div>
JPV
https://library.morph.zone/index.php?title=Filesystems&diff=4306
Filesystems
2023-05-20T08:33:28Z
<p>JPV: </p>
<hr />
<div>== About ==<br />
This page collects information about file systems working natively under MorphOS. In addition to these, Amiga 68k file systems can be used too ([[Preparing_an_Amiga_Hard_Drive|example]]).<br />
<br />
'''NOTE: this page is still under construction and many values would need to be verified!''' Any feedback is welcome to this [https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12144&forum=3 thread].<br />
<br />
== Disk File Systems ==<br />
<br />
{| class="wikitable"<br />
! style="text-align:left;"| Name<br />
! style="text-align:left;"| Location<br />
! style="text-align:left;"| Bootable<br />
! style="text-align:left;"| Native File Properties<br />
! style="text-align:left;"| Max File Name Length<br />
! style="text-align:left;"| Max File Size<br />
! style="text-align:left;"| Max Partition Size<br />
! style="text-align:left;"| Notes<br />
|-<br />
| Smart File System (SFS)<br />
| Built-in (boot.img)<br />
| Yes<br />
| Yes<br />
| 107<br />
| 4 GiB - 2 bytes<br />
| 128 GiB<br />
| The default file system<br />
|-<br />
| Professional File System III (PFS3)<br />
| Built-in (boot.img)<br />
| Yes<br />
| Yes<br />
| 107<br />
| 2 GiB<br />
| 104 GiB<br />
| Legacy support for PFS2 and AFS1<br />
|-<br />
| Fast File System 2 (FFS)<br />
| Built-in (boot.img)<br />
| Yes<br />
| Yes<br />
| 107<br />
| 4 GiB - 2 bytes<br />
| 2 TiB to 128 TiB<br />
| Legacy support for OFS and FFS<br />
|-<br />
| FAT File System (FAT)<br />
| Built-in (boot.img)<br />
| Yes<br />
| No<br />
| 255* (UCS-2)<br />
| 4 GiB<br />
| 2 TiB<br />
| Supports FAT12, FAT16, and FAT32 with LFN<br />
|-<br />
| Mac File System (HFS)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 31<br />
| 2 GiB<br />
| 2 TiB<br />
|<br />
|-<br />
| Hierarchical File System (HFS+)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 255* (UTF-16) <br />
| 2 TiB**<br />
| 2 TiB**<br />
| Read-only<br />
|-<br />
| Second Extended File System (ext2, ext3, ext4)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 255*<br />
| 16 GiB to 2 TiB<br />
| 2 TiB<br />
| Limited read-only support for ext4<br />
|-<br />
| NT File System (NTFS)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 255*<br />
| 2 TiB**<br />
| 2 TiB**<br />
| Read-only<br />
|-<br />
| SGI X File System (XFS)<br />
| Built-in (MOSSYS:L)<br />
| No<br />
| No<br />
| 255*<br />
| 2 TiB**<br />
| 2 TiB**<br />
| Read-only<br />
|-<br />
| Ice File System (IceFS)<br />
| 3rd party ([http://blubbedev.net/icefs/ link])([https://www.morphos-storage.net/?find=ice-fs link2])<br />
| Yes/No<br />
| Yes<br />
| 107 (255)<br />
| 9 EB<br />
| 9 EB<br />
| Bootable on Pegasos and Efika, but not on Macs<br />
|-<br />
| ExFAT File System (ExFAT)<br />
| 3rd party ([http://www.morphos-storage.net/?page=System/Devices/HD/Filesystems&file=exFAT-FS_1.1.lha link])<br />
| No<br />
| No<br />
| 255 UTF-16<br />
| 128 PiB<br />
| 128 PiB<br />
| <br />
|-<br />
| NT File System 3G (NTFS-3G)<br />
| 3rd party ([http://blubbedev.net/filesysbox/ link])<br />
| No<br />
| No<br />
| 255<br />
| 16 EiB<br />
| 16 EiB<br />
| Can't be placed on RDB<br />
|-<br />
| FS1541<br />
| 3rd party ([http://aminet.net/package/disk/misc/FS1541-MorphOS link])<br />
| No<br />
| No<br />
| 16<br />
| 164 KiB<br />
| 170 KiB<br />
| For CBM 1541 disks/images<br />
|-<br />
| CDRive File System (CDFS)<br />
| Built-in (boot.img)<br />
| Yes<br />
| Yes<br />
| 255*<br />
| <br />
| <br />
| ISO 9660/Amiga Rock Ridge/Joliet, audio as WAV files, ISO file support<br />
|}<br />
<br />
<nowiki>* </nowiki>Filenames over 107 characters will be stripped<br />
<br />
<nowiki>** </nowiki>Theoretical sizes may be bigger, but filesystems using deviceio.library are limited to 2 TiB<br />
<br />
== Network File Systems ==<br />
<br />
{| class="wikitable"<br />
! style="text-align:left;"| Name<br />
! style="text-align:left;"| Location<br />
! style="text-align:left;"| Native File Properties<br />
! style="text-align:left;"| Notes<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#SmbFS SmbFS]<br />
| Built-in (MOSSYS:C)<br />
| No<br />
| For mounting Windows shares or Samba shares (SMB1) on other platforms<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#Smb2FS Smb2FS]<br />
| Built-in (MOSSYS:C)<br />
| No<br />
| For mounting Windows shares or Samba shares (SMB2/3) on other platforms<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#Ssh2FS Ssh2FS]<br />
| Built-in (MOSSYS:C)<br />
| No<br />
| For mounting SFTP shares on other platforms<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#NetFS_Revised NetFS Revised]<br />
| 3rd party ([http://aminet.net/package/comm/net/NetFS-revised link])<br />
| Yes<br />
| For mounting partitions between MorphOS and/or AmigaOS systems<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#FTPMount FTPMount]<br />
| 3rd party ([http://aminet.net/package/comm/tcp/FTPMount_MOS link])<br />
| No<br />
| For mounting FTP sites as part of a filesystem<br />
|-<br />
| [https://library.morph.zone/Mounting_Network_Drives#Google_Drive_and_Dropbox_Handlers Amiga Cloud Handlers]<br />
| 3rd party ([http://aminet.net/package/comm/tcp/AmigaCloudHandlers link])<br />
| No<br />
| For mounting Google Drive and Dropbox storage<br />
|}</div>
JPV