MorphOS Library - User contributions [en]

Reggae tutorial: Playing a sound from file

2025-05-12T11:39:24Z

Polluks: /* Opening a sound file */ link

''Grzegorz Kraszewski''

Playing a sound file from disk is one of most common media related tasks. Reggae can perform it with a few lines of code. Using Reggae for audio playback has several advantages:
* Wide range of supported audio formats. A codec is selected and loaded by Reggae automatically.
* Playback is asynchronous. Reggae offloads decoding and playback to a dedicated process. The main application may perform other tasks during playback. It gets informed when the playback ends.
* Reggae streams audio from disk, so it does not load the whole file to memory. Doublebuffering is fully automatic.
* Audio is played through selected unit of [[AHI]]. Multiple sounds (up to 32, depending on user settings of [[AHI]]) may be played simultaneously.
Playing audio directly from disk is best suited for long sounds without low latency requirements. A typical example is music player or playing background music in the game.

From Reggae point of view, the task of playing audio from disk can be divided in two major parts. The first one is to get raw audio samples out of encoded file. The second task is to feed audio data to the output.

==Opening a sound file==
This part of the job is highly automated. Reggae recognizes the file format and builds complete decoding pipeline for the file with a single function call. The result is returned to the application as one, opaque object (it may contain many objects inside, but it is irrelevant for application programmer).

<tt>Object* media; media = MediaNewObject(   MMA_StreamType, (ULONG)"file.stream",   MMA_StreamName, (ULONG)"RAM:sound",   MMA_MediaType, MMT_SOUND, TAG_END);</tt>

This single call creates a complete decoding infrastructure for a specified file. Data source is specified by two tags, ''MMA_StreamName'' and ''MMA_StreamType''. The first one is the name of the source. In case of files it is just path to the file, which may be absolute (as in the example), relative to the current directory, or relative to program executable location (using ''PROGDIR:'' [[Shell Commands/Assign|assign]]). ''MMA_StreamType'' is used to specify which Reggae stream class (or "transport") should be used. Of course ''file.stream'' is for disk based files (and other things recognized by DOS as filesystems).

The last tag is a kind of filter. If Reggae recognizes the file, but it is not sound, the file will be rejected, and the function will return NULL. Of course if file is not recognized at all, NULL will be returned as well. Checking the result of ''MediaNewObject()'' against NULL is a very good idea.

In case of success ''media'' contains a pointer to Reggae object, having at least one output data port, port 0.

==Creating output==
The second step is to add audio output object to the Reggae processing pipeline. Then one can "run" the pipeline, which results in playing the file. The output object belongs to ''audio.output'' class. Before an object can be created, the class must be loaded from disk. It is done by opening the class with ''OpenLibrary()''.

<tt>struct Library* AudioOutputBase; AudioOutputBase = OpenLibrary("multimedia/audio.output", 51);</tt>

It is worth noting that ''audio.output'' has no specific functions in its shared library API (it is true for all Reggae classes except of the main ''multimedia.class''). Then, the name of variable holding the library base is completely irrelevant (as the name is never used implicitly), and may be anything, "hja76_d62eg" for example. The name used in the example is a bit more readable however.

After class opening, an instance of the class may be created:

<tt>Object* play; play = NewObject(NULL, "audio.output", TAG_END);</tt>

The instance is created with generic ''NewObject()'' call. There are no tags for attributes. The output object will read all sound properties from media object when they are connected together. I remind again that checking return value here may be a good idea. If objects are ready, let's connect them:

<tt>MediaConnectTagList(media, 0, play, 0, NULL);</tt>

Output port 0 of ''media'' object is connected with input port 0 of ''play'' object. Both the objects form a complete Reggae processing pipeline. Now we are ready to play sound. The whole playback control is done by talking to ''output'' object.

==Making noise==
Playback is controlled with three methods: ''MMM_Play()'', ''MMM_Stop()'' and '' MMM_Pause()'' performed on the ''audio.output'' instance.

*'''''MMM_Play()''''' starts playback if object is stopped, is ignored when object is playing.

*'''''MMM_Stop()''''' stops playback and rewinds the audio stream to the start (if possible).

*'''''MMM_Pause()''''' (available since version 51.14 of ''audio.output'') stops playback, but does not rewind audio stream. Following ''MMM_Play()'' will continue from paused position.

All the methods are performed immediately, so just

<tt>DoMethod(play, MMM_Play);</tt>

starts the playback and

<tt>DoMethod(play, MMM_Stop);</tt>

stops it at any time. All methods are asynchronous to the caller and return immediately. Even if ''MMM_Play()'' setup time is long (because of prebuffering for example), calling process is not stopped because setup is done by ''audio.output'' process.

==Waiting for end of sound==
Because ''audio.output'' plays the sound asynchronously, there must be a way to inform the main process about sound end. By "sound end" I mean either actual audio stream end, or calling ''MMM_Stop()''. Then the application programmer need not to write separate code for handling natural and forced playback stop.

The class offers two methods for signalling sound end event, namely audio process can send a '''signal''' or can reply a '''message'''. Application specifies method choosen and its parameters by performing one of the two methods described below on ''audio.output'' object. Methods are usually called before the playback is started, but may be also called when object is already playing. The later solution is tricky however, as the sound may be very short, so a method may be called '''after''' the sound end. In this case signalling requests will be never triggered.

'''''MMM_SignalAtEnd()''''' method should be used, when we want to receive a signal to be Wait()-ed. It has two parameters, pointer to process to be signalled and signal number (not mask!) to be sent. We usually want to be signalled ourselves, but it is not a requirement, so process A can start playback, but signal may be received by process B. A typical usage may look like this:

<tt>DoMethod(play, MMM_SignalAtEnd, FindTask(NULL), SIGBREAKB_CTRL_C); 
DoMethod(play, MMM_Play); 
Wait(SIGBREAKF_CTRL_C);</tt>

In this code we send a request to be signalled themselves with system CTRL-C signal. It can be of course allocated private signal. Note that ''MMM_SignalAtEnd()'' method expect '''signal number''' while following ''Wait()'' needs a '''signal mask'''.

[http://krashan.ppa.pl/reggae/library/playaudio_signal.c A complete example source code using a signal]

'''''MMM_ReplyMsgAtEnd()''''' signals the end of sound by sending a system message prepared by application to some message port set up by application as well. This method is useful especially when an application uses multiple sounds at once. Number of signals available to a process is very limited. Number of created messages is limited only by available memory. The method is also useful if application creates
message port for other purposes. Then audio end messages can be directed to this port and distinguished by message contents. Typical usage looks as follows:

<tt>struct MsgPort *port; /* created elsewhere */ 
struct Message *msg; /* allocated elsewhere */ 
 
msg->mn_Node.ln_Type = NT_MESSAGE; 
msg->mn_Length = sizeof(struct Message); 
msg->mn_ReplyPort = port; 
 
DoMethod(play, MMM_Sound_ReplyMsgAtEnd, msg); 
DoMethod(play, MMM_Play); 
WaitPort(port); 
GetMsg(port);</tt>

The main difference between these two methods is that message signalling is "one-shot". After the message is sent to application's port, it must be got from the port and reinitialized before it can be reused again. Signal method may be used repeatedly, which is comfortable when a short sound is triggered multiple times.

[http://krashan.ppa.pl/reggae/library/playaudio_message.c A complete example source code using a message]

Shell Commands/RXCmd

2024-10-03T22:13:40Z

Polluks: Undo revision 4350 by Polluks (talk)

'''RXCmd''' - Executes an ARexx command on a given ARexx port directly

PORT/A,COMMAND/A
<nowiki>
PORT - Name of an ARexx port (case sensitive)
COMMAND - ARexx command to be executed</nowiki>

RXCmd can be used to send single ARexx commands to a program. It even works with the dummy rexxsyslib.library file provided with the standard MorphOS installation, while the traditional RX command requires installation of a 3rd party rexxsyslib.library file.

Examples:
RXCmd OWB.1 FULLSCREEN
RXCmd JUKEBOX "GET TITLE"

Shell Commands/RXCmd

2024-09-30T14:57:28Z

Polluks: restriction

'''RXCmd''' - Executes an ARexx command on a given ARexx port directly

PORT/A,COMMAND/A
<nowiki>
PORT - Name of an ARexx port (case sensitive)
COMMAND - ARexx command to be executed</nowiki>

RXCmd can be used to send single ARexx commands to a program. It even works with the dummy rexxsyslib.library file provided with the standard MorphOS installation, while the traditional RX command requires installation of a 3rd party rexxsyslib.library file.
However RXCmd does not support "result" of a command, for example with CygnusEd's port.

Examples:
RXCmd OWB.1 FULLSCREEN
RXCmd JUKEBOX "GET TITLE"

Reggae: MorphOS multimedia framework

2024-09-05T07:35:25Z

Polluks: /* Overview */ ReggaeList

''Grzegorz Kraszewski''
==Introduction==
'''Reggae''' is the name for modular MorphOS subsystem for handling media files (currently pictures and sounds, video and other contents will come in the future). Reggae is implemented as a large set of MorphOS shared libraries stored in ''MOSSYS:Classes/Multimedia/'' directory. Third party Reggae classes may be copied to ''SYS:Classes/Multimedia/''. Using Reggae an application developer can easily perform following tasks related to media processing:
* Recognizing media type and format.
* Streaming media via different transports.
* Demultiplexing compound media streams.
* Decoding media to plain, uncompressed format.
* Processing by applying filters.
* Presenting media to the user.
* Encoding and multiplexing.
Reggae is an object oriented framework. Every media processing task creates a pipe (or tree) of Reggae objects connected to each other. Media data travel along this structure in relatively small chunks. This pipelined processing allows for handling very big data, much bigger than available system memory.
==Overview==
This section contains general Reggae information, its design principles, usage patterns and rules.
* [[Kinds of Reggae classes]].
* [[Reggae common formats]].
See also [https://www.morphos-storage.net/?id=1532522 ReggaeList].

==Tutorials==
This section contains Reggae programming tutorials with example code.
===General===
* [[Reggae tutorial: Accessing Reggae in applications|Accessing Reggae in applications]]
* [[Downloading web resources with http.stream - basics]]
* [[Downloading web resources with http.stream - advanced]]
* [[Writing Reggae classes]]
* [[Reggae and XPK]]

===Audio===
* [[Reggae tutorial: Playing a sound from file|Playing a sound from file]].
* [[Reggae tutorial: Playing a sound from memory|Playing a sound from memory]].
* [[Reggae tutorial: Playing a synthesized, continuous wave|Playing a continuous, synthesized wave]].
* [[Reggae tutorial: Saving audio in user selected format|Saving audio in user selected format]].

Writing Custom Startup Code

2024-08-04T16:56:43Z

Polluks: /* A Complete Example */

''Grzegorz Kraszewski''

One can find in every C programming handboook, that program execution starts from ''main()'' function. In fact we have such an impression, when we write a program. There is no evidence to disprove it. In fact however, this is not true. There are at least a few, and sometimes even a few teens of kilobytes of code between the start of program execution and the first line of ''main()''. Most of this code is not really needed in most cases.

What is being done by this code? Let's say for the start, it is perfectly possible to have a program without any startup code at all. The system can jump into ''main()'' right away. Unfortunately such a program would run only from commandline window. It would crash, when started from Ambient. It is because Ambient sends a special message to a message port of a freshly created process. This message serves two purposes. Firstly, it contains Ambient launch parameters, namely program icon descriptor and optionally descriptors of other icons, which have been shift-clicked, or dropped onto a panel. Secondly, a reply for the message is a signal for Ambient that the program finished its execution. Sending a reply is obligatory. This is the minimal set of things to be done by startup code. In practice it also should open required shared libraries. When one wants to use the C standard library, either with ''libnix'' or ''ixemul.library'', the startup code also creates a "standard environment" for the C standard library and POSIX functions ([[Installation of Software Development Kit and its basic usage#Standard C and C++ Libraries|more on this]]). Because of this, startup code linked when using one of these libraries is quite complex, so also long.

=Reasons for Writing Own Startup=

The main advantage of an own startup is its shortness. Reducing program startup time is negligible. Very short startup is good for very short programs (for example shell commands), a few kB in size. In this case the standard startup may be easily longer than the program code itself. One can also use own startup just for satisfaction of making the program shorter by those few kilobytes. Custom startup code cannot be used, when the program uses ''ixemul.library''. When the program is linked with ''libnix'', the possibility of using own startup depends on the standard C library functions used. Most of them do not need any preparations and will work with any startup. Some more complex functions however require constructors to be executed in startup. If we use such functions, we will get linker errors of unresolved symbols. In such a case there is a simple choice – one either must replace these functions with something else, or just use the standard startup code. Own startup is then useful mostly when standard C library is not used at all (in favour of the native MorphOS API), or only simple functions from it are used.

If we are still determined to use own startup, it is the time to tell the compiler about it. Skipping standard startup is done with '''−nostartfiles''' argument. Then when we try to use our startup with ''libnix'', we use '''−nostartfiles''' together with '''−noixemul'''. Programmers wanting to go the pure MorphOS API way (without the C library), should use '''−nostdlib''' option, which also implies '''−nostartfiles'''.

=Let's Write It=

Before we start to write the code, note that except things executed before calling the ''main()'' function, some code must be also called '''after''' it returns. Then we also have "cleanup code". As this code is usually placed in the same function (the one that calls ''main()''), both the parts are commonly called just startup code.

As mentioned before, program execution does not really start from the ''main()'' function. Where does it start then? When an ELF executable is loaded from disk, a section named ".text" is found and operating system jumps to the start of its contents. When a program is written in C, it means start of the first function in code, as in C there is no way to write code outside of a function. It must be noted, that C compiler may reorder functions in a single object file. The GCC 2.95.3 compiler never does it, but aggressive optimizer of GCC 4 can change order of functions. Fortunately it is done only inside a single source file. To make sure that our startup function will be the first, it must be placed in a separate file. Then resulting object file must be linked as the first one, as linking order is always preserved. After this important note it is time for the code:

#include <proto/exec.h>
#include <proto/dos.h>
#include <dos/dos.h>
#include <workbench/startup.h>

The thing starts with including needed header files. We will need two basic system libraries: ''exec.library'' and ''dos.library''. It explains why standard startup code, be it ''libnix'' or ''ixemul.library'', opens these two libraries – it simply needs them for itself.

struct Library *SysBase;
struct Library *DOSBase;

As our code will use these two libaries, we need to define their bases.

extern ULONG Main(struct WBStartup *wbmessage);

This is a declaration of the main function of our program. As the object file containing startup code should contain only one function (the entry one), the rest of code has to be moved to other object files, for reasons explained above. That is why the main function has to be declared here, as we call it from the startup code. Alternatively its declaration may be placed in some header file and included here. The name ''Main()'' is arbitrary, it can be anything. I've just called it typically, capitalizing the first letter to avoid possible name confilct with the standard library. The argument of ''Main()'' is startup message (mentioned above) being sent by Ambient. If we do not plan to use it inside ''Main()'', we can just declare it this way:

extern ULONG Main(void);

The next important thing is to define a mysterious global symbol ''__abox__''.

ULONG __abox__ = 1;

While not needed in the code, this symbol is used by the system executable loader to differentiate between MorphOS ELF executables and other possible PowerPC ELF binaries. If there is no ''__abox__'' defined, the executable will be recognized as PowerUP one and executed through ''ppc.library'', with unpredictable results.

ULONG Start(void)
{
struct Process *myproc = 0;
struct Message *wbmessage = 0;
BOOL have_shell = FALSE;
ULONG return_code = RETURN_OK;

''Start()'' is the code entry point. Again, name of this function is not important, it may be anything. It just has to be the first function in the linked executable. Some local variables are declared here, which will be needed later. ''myproc'' will contain a pointer to our process, ''wbmessage'' will hold the Ambient startup message pointer. Variable ''have_shell'' will be used to detect if the program has been started from shell console or from Ambient. Finally ''return_code'' is just the return code of the program, it will be returned to the system. The return value is usually 0 when the program executed succesfully and ''RETURN_OK'' constant is just 0.

SysBase = *(struct Library**)4L;

Time for initialization of the ''SysBase'', the base of ''exec.library''. The library is always open. For historical and backward compatibility reasons the base pointer is always placed by the system at address $00000004, so we just take it from there. Having ''exec.library'' available, our code can check whether it has been started from shell or from Ambient:

myproc = (struct Process*)FindTask(0);
if (myproc->pr_CLI) have_shell = TRUE;

This information is taken from the ''Process'' structure being just system process descriptor. The ''exec.library'' call ''FindTask()'' returns the calling task's own descriptor if 0 is passed as its argument. In case we are started from Ambient, receiving its message is compulsory:

if (!have_shell)
{
WaitPort(&myproc->pr_MsgPort);
wbmessage = GetMsg(&myproc->pr_MsgPort);
}

The startup message is being sent to process system port, so we receive it there. The message may be then passed to our ''Main()'' function, if we plan to make some use of it, like handling additional icon arguments.

if (DOSBase = OpenLibrary((STRPTR)"dos.library", 0))
{

The next step is opening ''dos.library'', this library is opened in a pretty standard way. In fact this minimal startup code does not need it. There are two reasons to open it anyway. First, it is hard to imagine a program, which does not need ''dos.library'' – even "Hello world!" needs it. Secondly, all standard startup codes open it, so usually main code takes it for granted. Then my startup behaves conventionally and opens ''dos.library'' as well.

return_code = Main((struct WBStartup*)wbmessage);

Yes, after these few lines we are ready to call the main code. As stated above, passing the startup message from Ambient is optional. On the other hand, receiving the result and passing it back to the system later is obligatory.

CloseLibrary(DOSBase);
}
else return_code = RETURN_FAIL;

From this point the startup code becomes cleanup one. Note also that proper error handling must be done. ''dos.library'' is being closed, but if its opening failed before, the result of execution is changed to ''RETURN_FAIL''. This is the hardest fail and means total inability to execute. In practice MorphOS can't boot if ''dos.library'' is not present in the system. But ''OpenLibrary()'' may fail for other reasons, for example simple lack of free memory. Then the startup code has to handle it in some reasonable way.

if (wbmessage)
{
Forbid();
ReplyMsg(wbmessage);
}

This snippet of code handles the Ambient startup message. Even if we make no use of it, it '''must''' be replied at exit. But what does ''Forbid()'' do here? This function halts system multitasking, specifically it prevents the system process scheduler to switch our process away. Usually it may be done for a very short period of time only and followed by a matching ''Permit()''. At the first glance this code makes no sense then, a process stops process switching and... exits. We have to know one important thing however: process switching is automatically reenabled when the process which called ''Forbid()'' ends. Then here is what happens:
* Our task calls ''Forbid()'', so no other process can interrupt it.
* It replies the Ambient startup message. As multitasking is stopped, Ambient is unable to receive yet. The message just waits at its message port.
* Our task exits. Then the system restores multitasking.
* Ambient gets CPU time and receives the message. Note that at this point it is absolutely certain, that our task does not exist anymore. Possibility of a race condition is eliminated. Without ''Forbid()'' it could be possible that our process is removed from the system while it still executes.
Of course multitasking halt period is extremely short, because our cleanup code ends immediately after replying to Ambient:

return return_code;
}

=$VER: – program identification string=

This topic is not strictly related to startup code, but the version string is usually placed in it, so I've decided to write a few words about it. The version string is a short text in some defined format. This string contains the program name, version and revision number, compilation date and optionally copyrigth or author info. The version string is decoded by many applications including Ambient, the system command ''version'', the Installer program and more. The text starts with '''$VER:''', so it can be easily found in the program executable. As version tools search for the version string from the start of the executable file, it is best if version string is placed as close to the beginning of the file as possible. If the version string is declared as a simple string constant, it is unfortunately placed in one of the ELF data sections. These sections are placed after the code section by the linker. However we can force the version string to be placed in the code section:

__attribute__ ((section(".text"))) UBYTE VString[] =
"$VER: program 1.0 (21.6.2011) © 2011 morphos.pl\r\n";

Using a GCC specific extension ''__attribute__'' we can push the string into the ELF section named ''.text'', which is the code section. As the startup code object is linked as the first object, the version string will appear at the beginning of the executable, just after the code of the ''Start()'' function. Why after? It is simple, if we place it before the real code, the operating system will jump "into" the string, trying to execute it, and then of course it will crash.

=A Complete Example=

A complete "Hello world!" [http://krashan.ppa.pl/mph/files/helloworld.lha example] with custom startup code shows the described ideas at work. It only uses the MorphOS API, so is compiled with '''−nostdlib''' option. Executable size is 1,592 bytes. For comparision, ''libnix'' startup and ''printf()'' gives 30,964 bytes, when one replaces ''printf()'' with MorphOS ''Printf()'' from ''dos.library'' it is still 13,500 bytes.

As the project consists of two *.c files, a simple makefile is added to it. Example may be compiled just by entering ''make'' in a console.

Reggae and XPK

2024-06-18T17:55:24Z

Polluks: /* Introduction */ author

''Grzegorz Kraszewski''

== Introduction ==

XPK is a modular system for data compression. It consists of the main library, xpkmaster.library, and sublibraries stored in LIBS:Compressors/ directory. The main library provides API, while sublibraries provide compression algorithms. XPK has been designed for classic AmigaOS, then it has been ported to MorphOS and is now a native system component with 5 sublibs delivered with the system. Old sublibraries, compiled for M680x0 processors may be installed and used as well. XPK package provides also a set of shell based tools to compress, decompress and manipulate the data.

While XPK tools work only for files, the API itself supports generalized stream concept, which fits Reggae nicely. Reggae interfaces to XPK with a demultiplexer class named xpk.demuxer. The class features not only interface, but also automatic recognition of streams compressed with XPK. It also hides some XPK API problems, like forcing application to decompress whole data chunks.

== How Reggae uses xpk.demuxer automatically ==

The xpk.demuxer class has been designed to be transparent for application in most common cases. It means, when Reggae decoding tree is created with MediaNewObject(), a programmer does not need to care if data are compressed with XPK, or not. In case data are compressed, the first pass of format detection and demultiplexer matching will match xpk.demuxer. Then, xpk.demuxer object announces raw data stream on its output, which will cause the second pass of format detection, on decompressed data this time.

Let's assume a stream containing XPK compressed PCM WAVE audio file. Reggae will cascade xpk.demuxer with wave.demuxer, then add audiopcm.decoder as usual. The file will be then decoded the same way as not compressed one. There is no change in application code, all this is fully automatic. It is worth noting, that XPK support in MediaNewObject() is 100% transparent and all applications, even those written before xpk.demuxer release will gain XPK support with no changes in code or recompilation.

Example 1 (see a frame on the left) loads an XPK packed BMP image (It is a Reggae logo, 512 × 512 pixels, 24-bit) from a file and displays it in a window using picture.output. As BMP format has no compression and the image has big areas of solid colors, the compression ratio is very good (98.48% of gain, from 786 486 to 11 992 bytes). The file is compressed with GZIP packer. What is interesting in this code, it really does not matter if the file reggae512.bmp.xpk is compressed or not. One can try to decompress the file leaving the original name. The .xpk extension does not matter, as Reggae does not rely on extension in format recognition code. The example will load and display uncompressed image with no single character changed in the code. This is how transparency of XPK support works.

A few words about the code. The main() function opens needed libraries and creates a Reggae decoding tree starting from file stream of given name. There is MMT_PICTURE filter added to avoid loading files not being pictures. Then display_picture() function gets picture dimensions and opens a window of needed size. Finally blit_picture() creates picture.output object, connects it with processing tree, sets destinaion RastPort to the window one and specifies offsets, so the image is displayed inside window borders. MMM_Play() method causes the picture to be drawn. Note that picture.output does it in strips, so memory footprint is kept low. Function wait_for_closing() is nothing more than a plain Intuition message handling loop, which exits after window close gadget is clicked.

== Compressed data in memory ==

Instead of loading image from a file, one can convert compressed data into link object or C source and then link it with executable. This is useful for things like program logo or some specific gadget imagery. Example 2 program demonstrates this technique. The code is almost identical to example 1 (that is why the code is not repeated here). The first, obvious difference is addition of large table containing compressed data. The table has been generated with BinToC tool. The second difference is data source specification for MediaNewObject(). Stream type is now memory.stream. Instead of passing stream name, stream handle is specified, which for memory streams is just address of the data. Memory stream needs also length specification (as there is no such thing as stream end) with MMA_StreamLength attribute. The rest of code is unchanged. XPK decompression is fully automatic, as in the previous example.

== Using xpk.demuxer for raw data ==

Sometimes it may be feasible to compress some raw data with XPK. For example storing images as BMP files has a disadvantage of inverted scanline order, which forces Reggae to buffer the whole image in memory. Both example programs above allocate 786 432 bytes for image buffer. It may be avoided by storing the image as raw data with proper top-to-bottom scanline order (in fact it may be avoided also by using some sane image format with strong internal compression like PNG, so the whole XPK game is not worth playing...). The class may be also used for any data not to be decoded by Reggae, just as a comfortable wrapper over XPK API. One may be surprised that XpkRead() and XpkSeek() are not counterparts of Read() and Seek() respectively. XpkRead() forces to read decompressed data in big chunks, size of chunk depends on packing method used and varies typically from 32 to 256 kB. XpkSeek() seeks to the chunk boundary and returns position in the next uncompressed chunk yet to be read.

Using xpk.demuxer as a standalone component, one can avoid these XPK API obstacles. The class provides MMM_Pull() and MMM_Seek() methods with single byte resolution, all buffering needed is handled internally. The example 3 illustrates the usage of xpk.demuxer for raw data. The example is a fully featured file fragments cutter. Because of this the source code is a bit longer, but still compact. Because we can't use MediaNewObject() automation here, file.stream and xpk.demuxer classes have to be opened manually with OpenLibrary() in Main(). Then, after parsing commandline arguments, perform_action() creates Reggae processing pipeline by hand. Stream object and xpk.demuxer instance are created and then connected together with MediaConnectTagList() call. When the pipeline is ready and an output file is opened with usual Open(), pump_data() function is called for every fragment. The pump_data() function could consist of a single MMM_Seek(), MMM_Pull and Write(), but data copying has been programmed in a loop with 64 kB buffer. Then cutting large data chunks is not memory demanding. Thanks to wrapping XPK with xpk.demuxer, data can be pulled with arbitrary amounts every time independently of any previous MMM_Seek() or compressor natural chunk size.

In this example XPK support is transparent as well, as uncompressed files are handled just fine. Note however that this is done other way than in previous examples. When Reggae creates a processing tree automatically with MediaNewObject(), an xpk.demuxer object is created only if datastream is compressed. In the last example, xpk.demuxer instance is always created and data always go through it. Then XPK itself is instructed to pass uncompressed data through. This feature of XPK may cause some troubles however. When xpkmaster.library detects uncompressed data and is requested to pass them through, it wants to know the length of data first. Then, if a stream object connected to an xpk.demuxer instance reports unknown stream length, connecting stream and demuxer with MediaConnect() will fail. Most of stream classes report known stream length. At the time of writing, the only stream able to return 0 (unknown) length is http.stream when using chunked transfer (see RFC 2616 for details).

<pre>
#define __NOLIBBASE__
#define USE_INLINE_STDARG

#include <proto/exec.h>
#include <proto/intuition.h>
#include <proto/multimedia.h>
#include <classes/multimedia/video.h>

extern struct Library *SysBase, *DOSBase;
struct Library *IntuitionBase, *MultimediaBase;

void wait_for_closing(struct Window *window)
{
BOOL running = TRUE;
struct IntuiMessage *imsg;

while (running)
{
WaitPort(window->UserPort);

while (imsg = (struct IntuiMessage*)GetMsg(window->UserPort))
{
if (imsg->Class == IDCMP_CLOSEWINDOW) running = FALSE;
ReplyMsg(&imsg-;>ExecMessage);
}
}
}

void blit_picture(Object *picture, struct Window *window)
{
Object *pic_output;
struct Library *picture_output_base;

if (picture_output_base = OpenLibrary("multimedia/picture.output", 51))
{
if (pic_output = NewObject(NULL, "picture.output",
MMA_Video_DestOffsetX, window->BorderLeft,
MMA_Video_DestOffsetY, window->BorderTop,
MMA_Video_RastPort, (ULONG)window->RPort,
TAG_END))
{
if (MediaConnectTagList(picture, 0, pic_output, 0, TAG_END))
{
DoMethod(pic_output, MMM_Play);
}
DisposeObject(pic_output);
}
CloseLibrary(picture_output_base);
}
}

void display_picture(Object *picture)
{
LONG width, height;

width = MediaGetPort(picture, 0, MMA_Video_Width);
height = MediaGetPort(picture, 0, MMA_Video_Height);

if (width && height)
{
struct Window *window;

if (window = OpenWindowTags(NULL,
WA_InnerWidth, width,
WA_InnerHeight, height,
WA_Title, (ULONG)"Reggae and XPK tutorial, example 1",
WA_DragBar, TRUE,
WA_DepthGadget, TRUE,
WA_CloseGadget, TRUE,
WA_IDCMP, IDCMP_CLOSEWINDOW,
TAG_END))
{
blit_picture(picture, window);
wait_for_closing(window);
CloseWindow(window);
}
}
}

int main(void)
{
if (IntuitionBase = OpenLibrary("intuition.library", 50))
{
if (MultimediaBase = OpenLibrary("multimedia/multimedia.class", 52))
{
Object *picture;

if (picture = MediaNewObjectTags(
MMA_StreamType, (ULONG)"file.stream",
MMA_StreamName, (ULONG)"reggae512.bmp.xpk",
MMA_MediaType, MMT_PICTURE,
TAG_END))
{
display_picture(picture);
DisposeObject(picture);
}
CloseLibrary(MultimediaBase);
}
CloseLibrary(IntuitionBase);
}
return 0;
}
</pre>

Reggae and XPK

2024-06-18T17:49:30Z

Polluks: Created page with "== Introduction == XPK is a modular system for data compression. It consists of the main library, xpkmaster.library, and sublibraries stored in LIBS:Compressors/ directory. T..."

== Introduction ==

XPK is a modular system for data compression. It consists of the main library, xpkmaster.library, and sublibraries stored in LIBS:Compressors/ directory. The main library provides API, while sublibraries provide compression algorithms. XPK has been designed for classic AmigaOS, then it has been ported to MorphOS and is now a native system component with 5 sublibs delivered with the system. Old sublibraries, compiled for M680x0 processors may be installed and used as well. XPK package provides also a set of shell based tools to compress, decompress and manipulate the data.

While XPK tools work only for files, the API itself supports generalized stream concept, which fits Reggae nicely. Reggae interfaces to XPK with a demultiplexer class named xpk.demuxer. The class features not only interface, but also automatic recognition of streams compressed with XPK. It also hides some XPK API problems, like forcing application to decompress whole data chunks.

== How Reggae uses xpk.demuxer automatically ==

The xpk.demuxer class has been designed to be transparent for application in most common cases. It means, when Reggae decoding tree is created with MediaNewObject(), a programmer does not need to care if data are compressed with XPK, or not. In case data are compressed, the first pass of format detection and demultiplexer matching will match xpk.demuxer. Then, xpk.demuxer object announces raw data stream on its output, which will cause the second pass of format detection, on decompressed data this time.

Let's assume a stream containing XPK compressed PCM WAVE audio file. Reggae will cascade xpk.demuxer with wave.demuxer, then add audiopcm.decoder as usual. The file will be then decoded the same way as not compressed one. There is no change in application code, all this is fully automatic. It is worth noting, that XPK support in MediaNewObject() is 100% transparent and all applications, even those written before xpk.demuxer release will gain XPK support with no changes in code or recompilation.

Example 1 (see a frame on the left) loads an XPK packed BMP image (It is a Reggae logo, 512 × 512 pixels, 24-bit) from a file and displays it in a window using picture.output. As BMP format has no compression and the image has big areas of solid colors, the compression ratio is very good (98.48% of gain, from 786 486 to 11 992 bytes). The file is compressed with GZIP packer. What is interesting in this code, it really does not matter if the file reggae512.bmp.xpk is compressed or not. One can try to decompress the file leaving the original name. The .xpk extension does not matter, as Reggae does not rely on extension in format recognition code. The example will load and display uncompressed image with no single character changed in the code. This is how transparency of XPK support works.

A few words about the code. The main() function opens needed libraries and creates a Reggae decoding tree starting from file stream of given name. There is MMT_PICTURE filter added to avoid loading files not being pictures. Then display_picture() function gets picture dimensions and opens a window of needed size. Finally blit_picture() creates picture.output object, connects it with processing tree, sets destinaion RastPort to the window one and specifies offsets, so the image is displayed inside window borders. MMM_Play() method causes the picture to be drawn. Note that picture.output does it in strips, so memory footprint is kept low. Function wait_for_closing() is nothing more than a plain Intuition message handling loop, which exits after window close gadget is clicked.

== Compressed data in memory ==

Instead of loading image from a file, one can convert compressed data into link object or C source and then link it with executable. This is useful for things like program logo or some specific gadget imagery. Example 2 program demonstrates this technique. The code is almost identical to example 1 (that is why the code is not repeated here). The first, obvious difference is addition of large table containing compressed data. The table has been generated with BinToC tool. The second difference is data source specification for MediaNewObject(). Stream type is now memory.stream. Instead of passing stream name, stream handle is specified, which for memory streams is just address of the data. Memory stream needs also length specification (as there is no such thing as stream end) with MMA_StreamLength attribute. The rest of code is unchanged. XPK decompression is fully automatic, as in the previous example.

== Using xpk.demuxer for raw data ==

Sometimes it may be feasible to compress some raw data with XPK. For example storing images as BMP files has a disadvantage of inverted scanline order, which forces Reggae to buffer the whole image in memory. Both example programs above allocate 786 432 bytes for image buffer. It may be avoided by storing the image as raw data with proper top-to-bottom scanline order (in fact it may be avoided also by using some sane image format with strong internal compression like PNG, so the whole XPK game is not worth playing...). The class may be also used for any data not to be decoded by Reggae, just as a comfortable wrapper over XPK API. One may be surprised that XpkRead() and XpkSeek() are not counterparts of Read() and Seek() respectively. XpkRead() forces to read decompressed data in big chunks, size of chunk depends on packing method used and varies typically from 32 to 256 kB. XpkSeek() seeks to the chunk boundary and returns position in the next uncompressed chunk yet to be read.

Using xpk.demuxer as a standalone component, one can avoid these XPK API obstacles. The class provides MMM_Pull() and MMM_Seek() methods with single byte resolution, all buffering needed is handled internally. The example 3 illustrates the usage of xpk.demuxer for raw data. The example is a fully featured file fragments cutter. Because of this the source code is a bit longer, but still compact. Because we can't use MediaNewObject() automation here, file.stream and xpk.demuxer classes have to be opened manually with OpenLibrary() in Main(). Then, after parsing commandline arguments, perform_action() creates Reggae processing pipeline by hand. Stream object and xpk.demuxer instance are created and then connected together with MediaConnectTagList() call. When the pipeline is ready and an output file is opened with usual Open(), pump_data() function is called for every fragment. The pump_data() function could consist of a single MMM_Seek(), MMM_Pull and Write(), but data copying has been programmed in a loop with 64 kB buffer. Then cutting large data chunks is not memory demanding. Thanks to wrapping XPK with xpk.demuxer, data can be pulled with arbitrary amounts every time independently of any previous MMM_Seek() or compressor natural chunk size.

In this example XPK support is transparent as well, as uncompressed files are handled just fine. Note however that this is done other way than in previous examples. When Reggae creates a processing tree automatically with MediaNewObject(), an xpk.demuxer object is created only if datastream is compressed. In the last example, xpk.demuxer instance is always created and data always go through it. Then XPK itself is instructed to pass uncompressed data through. This feature of XPK may cause some troubles however. When xpkmaster.library detects uncompressed data and is requested to pass them through, it wants to know the length of data first. Then, if a stream object connected to an xpk.demuxer instance reports unknown stream length, connecting stream and demuxer with MediaConnect() will fail. Most of stream classes report known stream length. At the time of writing, the only stream able to return 0 (unknown) length is http.stream when using chunked transfer (see RFC 2616 for details).

<pre>
#define __NOLIBBASE__
#define USE_INLINE_STDARG

#include <proto/exec.h>
#include <proto/intuition.h>
#include <proto/multimedia.h>
#include <classes/multimedia/video.h>

extern struct Library *SysBase, *DOSBase;
struct Library *IntuitionBase, *MultimediaBase;

void wait_for_closing(struct Window *window)
{
BOOL running = TRUE;
struct IntuiMessage *imsg;

while (running)
{
WaitPort(window->UserPort);

while (imsg = (struct IntuiMessage*)GetMsg(window->UserPort))
{
if (imsg->Class == IDCMP_CLOSEWINDOW) running = FALSE;
ReplyMsg(&imsg-;>ExecMessage);
}
}
}

void blit_picture(Object *picture, struct Window *window)
{
Object *pic_output;
struct Library *picture_output_base;

if (picture_output_base = OpenLibrary("multimedia/picture.output", 51))
{
if (pic_output = NewObject(NULL, "picture.output",
MMA_Video_DestOffsetX, window->BorderLeft,
MMA_Video_DestOffsetY, window->BorderTop,
MMA_Video_RastPort, (ULONG)window->RPort,
TAG_END))
{
if (MediaConnectTagList(picture, 0, pic_output, 0, TAG_END))
{
DoMethod(pic_output, MMM_Play);
}
DisposeObject(pic_output);
}
CloseLibrary(picture_output_base);
}
}

void display_picture(Object *picture)
{
LONG width, height;

width = MediaGetPort(picture, 0, MMA_Video_Width);
height = MediaGetPort(picture, 0, MMA_Video_Height);

if (width && height)
{
struct Window *window;

if (window = OpenWindowTags(NULL,
WA_InnerWidth, width,
WA_InnerHeight, height,
WA_Title, (ULONG)"Reggae and XPK tutorial, example 1",
WA_DragBar, TRUE,
WA_DepthGadget, TRUE,
WA_CloseGadget, TRUE,
WA_IDCMP, IDCMP_CLOSEWINDOW,
TAG_END))
{
blit_picture(picture, window);
wait_for_closing(window);
CloseWindow(window);
}
}
}

int main(void)
{
if (IntuitionBase = OpenLibrary("intuition.library", 50))
{
if (MultimediaBase = OpenLibrary("multimedia/multimedia.class", 52))
{
Object *picture;

if (picture = MediaNewObjectTags(
MMA_StreamType, (ULONG)"file.stream",
MMA_StreamName, (ULONG)"reggae512.bmp.xpk",
MMA_MediaType, MMT_PICTURE,
TAG_END))
{
display_picture(picture);
DisposeObject(picture);
}
CloseLibrary(MultimediaBase);
}
CloseLibrary(IntuitionBase);
}
return 0;
}
</pre>

Reggae: MorphOS multimedia framework

2024-06-18T17:37:40Z

Polluks: /* General */ Reggae and XPK

''Grzegorz Kraszewski''
==Introduction==
'''Reggae''' is the name for modular MorphOS subsystem for handling media files (currently pictures and sounds, video and other contents will come in the future). Reggae is implemented as a large set of MorphOS shared libraries stored in ''MOSSYS:Classes/Multimedia/'' directory. Third party Reggae classes may be copied to ''SYS:Classes/Multimedia/''. Using Reggae an application developer can easily perform following tasks related to media processing:
* Recognizing media type and format.
* Streaming media via different transports.
* Demultiplexing compound media streams.
* Decoding media to plain, uncompressed format.
* Processing by applying filters.
* Presenting media to the user.
* Encoding and multiplexing.
Reggae is an object oriented framework. Every media processing task creates a pipe (or tree) of Reggae objects connected to each other. Media data travel along this structure in relatively small chunks. This pipelined processing allows for handling very big data, much bigger than available system memory.
==Overview==
This section contains general Reggae information, its design principles, usage patterns and rules.
* [[Kinds of Reggae classes]].
* [[Reggae common formats]].

==Tutorials==
This section contains Reggae programming tutorials with example code.
===General===
* [[Reggae tutorial: Accessing Reggae in applications|Accessing Reggae in applications]]
* [[Downloading web resources with http.stream - basics]]
* [[Downloading web resources with http.stream - advanced]]
* [[Writing Reggae classes]]
* [[Reggae and XPK]]

===Audio===
* [[Reggae tutorial: Playing a sound from file|Playing a sound from file]].
* [[Reggae tutorial: Playing a sound from memory|Playing a sound from memory]].
* [[Reggae tutorial: Playing a synthesized, continuous wave|Playing a continuous, synthesized wave]].
* [[Reggae tutorial: Saving audio in user selected format|Saving audio in user selected format]].

Printing

2024-06-14T11:58:20Z

Polluks: /* General Information */

== General Information ==
MorphOS has two separate printing systems, see [https://www.morphos-storage.net/?id=1588365 this PDF]
.

== Output Devices ==
=== USBPAR: ===
This option allows any '''Hardware Compatible''' PostScript printer, with a printer's compatible PPD file installed in the System:Preferences/ '''Printers''' (which is '''NOT''' the '''PRINTER''' Preferences option) with a USB2 port to be able to direct its output as PostScript data using the '''USBPAR''': device, which is by default '''NOT installed''' in the default setup of MorphOS, and requires the USBPAR: device to be transferred from the MOSSYS: (MorphOS root directory inside the '''System''': otherwise known as '''SYS''': folder) from within the MorphOS/Storage/DOSDrivers folder to the DEVS:DOSDrivers folder of the main System (SYS:) partition.

''copy Mossys:Storage/DOSDrivers/USBPAR to sys:Devs/DOSDrivers/ move''

=== NETPAR: ===
The NETPAR: device can be used to print directly to network attached printers...

Configure a network connected printer from the NetPrinter settings in the MorphOS Preferences application...

Mount the NETPAR: device by....

=== PS: ===
PostScript output via TurboPrint by using GhostScript...

== Setting Up a Printer ==
=== TurboPrint ===
Open the '''Printer''' preferences from the MorphOS Preferences application...

=== PostScript ===
Open the '''Printers''' preferences from the MorphOS Preferences application...

== Printing From Applications ==

Applications/VNCServer

2023-12-15T14:25:50Z

Polluks: /* Autostart */ why?!

== Description ==
Remote access server allowing clients to connect using the VNC protocol.

== Usage ==

=== Autostart ===

Add to <nowiki>S:Network-User-Startup</nowiki>:

Run >NIL: SYS:Applications/VNCServer/VNCServer

Once started VNCServer will be available in the Exchange ([[Utilities/Commodities#Exchange.C2.A0]]).

=== Without GFX card ===

Copy Virtual driver with its icon (MOSSYS:Storage/Devs/Virtual) to SYS:Devs/Monitors/.
Edit its icon information to enable wanted screenmodes.

== Screenshot ==
: [[File:MorphOS3_jPV_Vncserver.png]]

"Hello world!" in MUI

2023-12-11T14:30:32Z

Polluks: Fixed link

''Grzegorz Kraszewski''
----
This article in other languages: [["Hello world!" w MUI|Polish]]

[[File:helloworld.png|left]] This is the window of the example MUI application. It is very simple, it contains only one static text object and no gadgets, except for window border gadgets. Note that the number of gadgets on the right side of the window depends on user MUI settings. The source code of the application is very simple too and fits into 60 lines, including proper vertical spacing. It is cut in pieces in the article for better reading. A complete, ready to compile version [https://web.archive.org/web/20160730092654/http://krashan.ppa.pl/mph/files/helloworld-mui.c is available] too.

#include <proto/muimaster.h>
#include <proto/intuition.h>

Header files for ''muimaster.library'' and ''intuition.library'' are included. Note that these libraries will be [[MorphOS_API_and_Its_Organization#How_to_Use_a_Library_in_an_Application|opened and closed automatically]].

Object *App, *Win;

Global pointers for the application object and the window object. While using many global variables is considered inelegant, having globals for the most important objects is handy, especially in such a small project.

Object* build_gui(void)
{
App = MUI_NewObject(MUIC_Application,
MUIA_Application_Author, (ULONG)"Grzegorz Kraszewski",
MUIA_Application_Base, (ULONG)"HELLOWORLD",
MUIA_Application_Copyright, (ULONG)"© 2010 Grzegorz Kraszewski",
MUIA_Application_Description, (ULONG)"Hello World in MUI.",
MUIA_Application_Title, (ULONG)"Hello World",
MUIA_Application_Version, (ULONG)"$VER: HelloWorld 1.0 (16.11.2010)",
MUIA_Application_Window, (ULONG)(Win = MUI_NewObject(MUIC_Window,
MUIA_Window_Title, (ULONG)"Hello World",
MUIA_Window_RootObject, MUI_NewObject(MUIC_Group,
MUIA_Group_Child, MUI_NewObject(MUIC_Text,
MUIA_Text_Contents, (ULONG)"Hello world!",
TAG_END),
TAG_END),
TAG_END)),
TAG_END);
}

The above function creates the complete object tree for ''HelloWorld''. The master object is the ''Application'' class instance. It has a ''Window'' object. The window root is a ''Group'' object containing one ''Text'' object. The application object has 6 attributes working as descriptors used in different places in the system. They are not required for running the program, but help integrating it with the system. The meaning of these attributes is explained in the autodoc of ''Application'' class in the SDK. The rest of the attributes are self-explaining, please refer to the autodocs of respective MUI classes for details.

The function illustrates a typical way of creating a MUI interface. The complete object tree is created in one big ''MUI_NewObject()'' call containing nested sub-calls. The order of code execution is different to the order of reading. The most nested objects are created first and passed to constructors of their parents. The application object is created last. This way of creating the application also ensures automatic error handling. If any of constructors fails, it passes ''NULL'' to a parent constructor, making it fail too and then dispose all successfully constructed child objects. Finally the application constructor fails and returns ''NULL''. Then only two states of the application are possible: either the application is fully constructed, or it is not constructed at all. This behaviour greatly simplifies error handling.

void notifications(void)
{
DoMethod(Win, MUIM_Notify, MUIA_Window_CloseRequest, TRUE, App, 2,
MUIM_Application_ReturnID, MUIV_Application_ReturnID_Quit);
}

The next step is to make [[Event Driven Programming, Notifications#Notifications in MUI|notifications]]. This simple program contains only one notification, which terminates the program after the window close gadget is clicked. MUI maps a left mouse button click on the gadget to a change of ''MUIA_Window_CloseRequest'' attribute. The notification target is the application, the ''MUIM_Application_ReturnID()'' method then passes the quit action identifier to the main loop.

void main_loop(void)
{
ULONG signals = 0;

set(Win, MUIA_Window_Open, TRUE);

while (DoMethod(App, MUIM_Application_NewInput, &signals) != MUIV_Application_ReturnID_Quit)
{
signals = Wait(signals | SIGBREAKF_CTRL_C);
if (signals & SIGBREAKF_CTRL_C) break;
}

set(Win, MUIA_Window_Open, FALSE);
}

The standard main loop has been discussed in the [[Event_Driven_Programming,_Notifications#The_Ideal_MUI_Main_Loop|previous chapter]]. The only addition is opening the window before the loop and closing it after.

int main(void)
{
App = build_gui();

if (App)
{
notifications();
main_loop();
MUI_DisposeObject(App);
}

return 0;
}

Finally, the main function of the program. It builds the object tree first and checks if it succeeded. In case of a fail, the program ends immediately. After all the objects are created, notifications are added and the program enters the main loop. When the loop finishes, the application object is disposed. It also disposes all its sub-objects.

Links

2023-10-19T15:01:57Z

Polluks: /* File Repositories */

==Official MorphOS Website==
* http://www.morphos-team.net

==Community Portals & Forums==
* http://morph.zone

* https://www.morphos-forum.de

* http://www.pegasos.org

* http://www.pegasos.hu

* http://www.ppa.pl

* http://saku.bbs.fi/foorumi

* http://www.warmup-asso.org

* http://www.warmup-asso.fr

* http://www.morphos-store.com - A website to buy and sell MorphOS hardware and software.

==File Repositories==

* http://mos.aminet.net - Aminet MorphOS Section

* http://www.morphos-storage.net - MorphOS Storage by WArMUp

* <s>http://morphos-files.ppa.pl</s> - MorphOS File Hosting Service (abandoned)

* http://morphos.lukysoft.cz - MorphOS Software Database

==Shops==

* https://www.morphos-store.com

==Software==

Demoscene

* http://amiga.bbs.fi/demopack_morphos/ - MorphOS Demopack

Emulation

* http://www.amidog.com/amiga/fpse/ - Free PlayStation Emulator, ported by Mathias 'AmiDog' Roslund

* http://ace.cpcscene.net/en:introduction - The acidulous CPC/CPC+ emulator.

Internet & Network

* http://www.amipodder.com - AmiPodder, free podcast client

* http://www.heightanxiety.com/AmiSSL/ - Port of OpenSSL for legacy applications

* http://amitradecenter.net - AmiTradeCenter, FTP client

* http://www.students.tut.fi/~komsa/amiga/beehive/ - Home of Beehive, a BitTorrent client

* http://sourceforge.net/projects/simplemail/ - SimpleMail, open source email client

* http://www.yam.ch - YAM, open source email client

* http://www.amirc.org - The famous IRC client

Music

* http://www.digiboosterpro.de/en/ - Home of Digibooster Pro

* http://jahjah.free.fr/morphos/ - Home of Ripper, a CD music ripping and conversion tool

* http://amigadev.free.fr/songplayer/index_en.html - Home of SongPlayer, a music player

* http://tcheko.binaryriot.org/soundbankster/ - A realtime audio mixing application dedicated to DJ enthusiasts

Office

* http://amigadev.free.fr/pointrider/ - PowerPoint viewer application

* http://www.grasshopperllc.com - Home of Pagestream, a commercial desktop publishing / page layout software

* http://beebase.sourceforge.net - Home of BeeBase aka MUIBase, Steffen Gutmann's relational programmable database (with GUI)

* http://shinkuro.altervista.org/amiga/software/nowined.htm - Home of NoWinEd, text editor

* http://www.winfield.demon.nl - Free MS Word reader

Package Management

* http://www.geit.de/eng_grunch.html - Search, download, install, update, and uninstall programs

System

* http://morphosambient.sourceforge.net - Ambient 'desktop' environment

* http://scalos.noname.fr - Scalos desktop, an alternative to Ambient

* http://sourceforge.net/projects/snoopium/ - System monitor application.

* http://sourceforge.net/projects/backman/ - Backman, open source backup program

* http://amigazeux.net/diavolo/ - Diavolo Backup, formerly commercial backup program

==Developers==

* http://amigazeux.org - AmiNet Radio, Dragon, Wetter, SkinClock, and much more.

* http://polymere.free.fr/index_en.html - Home of PolyNet (icon bar), PolyOrganizer and PolyGlot (MSN messenger)

* http://members.shaw.ca/realstar/ - Developer of the Aqua, Eve and HyperCannon game titles.

* http://fabportnawak.free.fr - MPlayer, ScummVM, Odyssey Web Browser, MAME, and more.

* http://krashan.ppa.pl - DigiBooster 3, MorphOS Programmer's Handbook, audio tools, and more.

* http://tbs-software.com/morgoth/

* http://khtml.ppa.pl

* http://bigfoot.morphos-team.net

* http://dreamolers.binaryriot.org

* http://tokai.binaryriot.org

* http://www.biclodon.com

* http://www.iki.fi/sintonen

* http://www.tbs-software.com/stefkos/

* http://home.elka.pw.edu.pl/~mszyprow/programy/ - Author of SFSDoctor.

* http://kiero.binaryriot.org - Freespace 1&2, Foobilliard, Homeworld, scube, szoom, and more.

* http://www.geit.de - Home of Grunch, MagicBeacon, MMKeyboard, and more.

* http://yellowblue.free.fr - Home of Yomgui, who maintains Blender, Python, PyMUI and Helios (Firewire)

* http://www.orel.rekom.ru/~imax/ - Maxim Ilyin ported VirtualJaguar, Mike Steed's FlashPlayer, and more.

* http://haru.at/ - Creator of MorphUp packagement system, ported VLC, MLDonkey, and more.

* http://www.amirus.org.ru - Various utilities such a KeyMorpher, a MUI-based key mapper. (Website is in Russian.)

* http://tbs-software.com/mark/ - Developer of PowerD, various utilities.

* http://tbs-software.com/powerd/ - PowerD programming language

* http://www.lukysoft.cz - Home of Lukáš Stehlík (AmiGod benchmark)

* http://dasixk.free.fr - Home of SixK, who ported a multitude of apps

* http://alfie.altervista.org - Home of Alfonso 'alfie' Ranieri, creator of RxMUI, AmRSS (RSS client), and much more.

* http://morphware.schwarzes.net - Various small tools made by Andreas Schwarz.

* http://www.onyxsoft.se - Home of Onyxsoft who have released a number of applications and games.

* http://www.mguc.ppa.pl - Marian Guc's website, developer of PciTool, AutoDoc Reader and the unfinished Nemesis desktop.

* http://brain.umcs.lublin.pl/~rzookol/ - Michał Żukowski's website, developer of SCANdal (scanner software)

* http://www.igracki.de - gTranslator, yWeather, CRABUM, and more.

* http://www.morguesoft.eu - Various screen savers.

* http://tcheko.binaryriot.org/ - SoundBankster, commodities, utils.

* http://bszili.morphos.me/ - Home of BSzili, who has ported numerous games.

* http://jpv.wmhost.com/jpv_software/ - Hollywood applications and Lua, ARexx, and shell scripts.

==Misc==

* http://www.via-altera.de/mid.htm - some documents about MorphOS (German/English)
* https://morphosuser.wordpress.com - Yasu's MorphOS Blog
* http://pegasos.lena-johannson.de/ - Otti website with many Deutsch translations

Utilities/KeyExplorer

2023-10-16T15:01:44Z

Polluks: /* Screenshot */ 2nd screenshot

== Description ==
A utility showing ascii and hex values for characters. The utility also shows the keyboard combination for a character.

Useful for finding codes when typing unsupported characters on limited keyboards. You may also open the virtual keyboard from the menu bar.

== Usage ==
* Click any character to show information about it in the Details area.
* The selected character can be copied to the clipboard with the context menu.

== Screenshot ==
:[[File:KeyExplorer.png]]
:[[File:MorphOS 3.10 Screenbar Keyinput.png]]

Utilities/KeyExplorer

2023-10-16T14:50:17Z

Polluks: /* Description */ virtual keyboard

How to Install Directory Opus Magellan II

2023-10-06T06:55:43Z

Polluks: /* Misc */ Fixed link

''Author: jPV/RNO''

== Preface ==

This is a tutorial how to install the original Amiga version of '''Directory Opus 5.82 Magellan II''' filemanager on a MorphOS machine. There are newer [http://sourceforge.net/projects/dopus5allamigas/ open source] versions of the program [http://www.dopus5.org/ available] nowadays too, but at least MorphOS ports are a bit unstable at the moment and you might prefer to use the original version.

== Installation ==

=== Installing from the Pre-installed Archive ===

The easy method is to install from the pre-installed archive found [http://kas1e.mikendezign.com/misc/dopus5/opus_installed_original_582.lha here].
# Download [http://kas1e.mikendezign.com/misc/dopus5/opus_installed_original_582.lha the archive] and extract it to the location you want.
# Edit the S:user-startup file with correct Assign and Path lines. It is important that DOpus5: assign points to the correct directory where you extracted the archive. Here's how it looks after the original installer: [[File:Dopus5_assigns.png|320px]]
# Reboot (or set both assign and path manually on the shell).
# Remove the supplied LHA archive, LZX archive, and Sound Module filetypes, because they don't work properly on MorphOS. Delete them from DOpus5:Filetypes/ directory or move them to the DOpus5:Storage/ directory. Or use Filetypes Settings on the program itself to remove or store them.
You can now jump to the [http://library.morph.zone/How_to_Install_Directory_Opus_Magellan_II#Registration Registration] section of this tutorial.

=== Installing from Floppy Images ===

Nothing prevents from installing the program from scratch either. It just has more steps and requires original floppy images in ADF format.
# Download [http://amiga.unikko.org/DOpus5-MagellanII/disks/adf/ ADF images] or convert [http://sourceforge.net/projects/dopus5allamigas/files/Dopus5.82/release/dms/ DMS images] to ADF with [http://morphos-files.net/download/xDMS xDMS], for example.
# Download two patch archives from [http://sourceforge.net/projects/dopus5allamigas/files/Dopus5.82/release/patches_to_5.82/ SourceForge] or [http://aminet.net/search?query=dopuspatch8 Aminet]. These will be used to update from the initial Magellan II release (5.80) to the latest 5.82 version.
# Start the Tools/FileImageCtrl program and insert "Opus55_Install" and "Opus55_Extras" ADF files into it (you can drag&drop the files or use the Insert button).
# Mount the images by selecting "Amiga FFS" filesystem and clicking the Mount button for each file. FileImageCtrl window can be closed after successful mounting. [[File:Dopus5_adf_mount.png|320px]]
# Open the Opus55_Install disk from the desktop and double click the InstallOpus icon. Only the important options are covered in the following steps, otherwise just follow the instructions and make your preferred selections.
# Select "Install or Update Opus 5.5". [[File:Dopus5_adf_install.png|320px]]
# Do '''not''' install ArcDir, because it's broken under MorphOS! We will replace it with XADopus instead. [[File:Dopus5_adf_install_arcdir.png|320px]]
# Select "'''Do not start Directory Opus on boot'''" in startup options selection. [[File:Dopus5_adf_install_not_on_boot.png|320px]]
# '''Reboot''' the machine after the installation is done.
# Start the Tools/FileImageCtrl program again, insert the MagellanII_Install ADF image, and mount it.
# Open the disk on the desktop, double click the Install_Opus_MagellanII icon, and select "Update Opus to Magellan-II". Installation should be straightforward to finish. [[File:Dopus5_adf_magellan2_update.png|320px]]
# After successful Magellan II update, extract the two patch archive files (5.81 and 5.82 updates) to a temporary directory, like "Ram Disk:" for example.
# Navigate to "PCH581" drawer, double click the Opus_Patch580-581 file, and do the installation. [[File:Dopus5_adf_581_patch.png|320px]]
# Navigate to "PCH582" drawer, double click the Opus_Patch581-582 file, and start the installation. [[File:Dopus5_adf_582_patch.png|320px]]
# When it asks to update the OS 3.5 icon.library, select "'''Skip This Part'''". [[File:Dopus5_adf_582_patch_skip_iconlibrary.png|320px]]
The base installation is now done and you can start the program from the location you originally chose.

== Registration ==

You can use a free serial number (4456BLJEM4616474390) to finalize the installation and to prevent the registration window popping up on program startup. Registration window may cause debug hits on MorphOS if it doesn't accept the data you entered. If that happens, reboot the machine before continuing.

:: [[File:Dopus5 registration.png|320px]]

== Workarounds for Graphical Issues on MorphOS ==

When the program is run with default settings, it opens on its own screen and some quite visible graphical issues are seen. A custom screen title and two window gadgets don't seem to fit with the rest, and Ambient's PNG icons don't work.

:: [[File:Dopus5 firstrun.png|320px]]

The custom screen title can be removed with the DOpus/WorkbenchTitle env variable. Type in the shell:

<tt>Setenv SAVE DOpus/WorkbenchTitle 1</tt>

One of the problematic gadgets can be removed with the following command:

<tt>Setenv SAVE DOpus/HidePadLock 1</tt>

:: [[File:Dopus5_env_set.png|320px]]

The other gadget (iconify) can be removed only by patching the original DirectoryOpus executable. A suitable patch for it can be found inside the [http://jpv.wmhost.com/magellan2ambient/d2a.lha D2A] program's archive. Extract the [http://jpv.wmhost.com/magellan2ambient/d2a.lha D2A] archive and run D2A/Patch/Script file. It will make a backup of the original executable and replace it with a new patched one.

:: [[File:Dopus5 gadget patch.png|320px]]

Your Directory Opus screen should look like this now:

:: [[File:Dopus5 gadgets patched.png|320px]]

== Integrating with Ambient ==

PNG icons can't be shown on the Directory Opus screen, but Directory Opus and its functionality can be integrated quite seamlessly to the Ambient screen. It's convenient to select which way you want to manage the files when both Ambient and Directory Opus are on the same screen. You can open Ambient windows when wanting to view by PNG icons and unleash the power of Directory Opus in many other cases.

The integration can be taken a step further by hiding the Directory Opus's main window and enabling the pop up of its listers when clicking on the Ambient screen. This can be achieved with [http://jpv.wmhost.com/magellan2ambient/d2a.lha D2A] or [http://jpv.wmhost.com/magellan2ambient/magellambient.lha Magellambient] programs.

D2A will be used in this tutorial and it requires a working ARexx environment. If you haven't enabled ARexx in your system yet, install rexxsyslib.library with Grunch or [http://library.morph.zone/Tips_and_Tricks#Modifying_the_System_Directory manually].

# Download and extract [http://jpv.wmhost.com/magellan2ambient/d2a.lha D2A] to some temporary directory if you haven't done it already.
# Disable (uncheck) the Backdrop mode from the pulldown menu on Directory Opus. [[File:Dopus5 disable backdrop.png|320px]] Main window will show up in full screen size: [[File:Dopus5 main window.png|320px]]
# Resize the main window as small as possible. [[File:Dopus5 main window resized.png|320px]]
# Select "Settings/Save Layout" from the pulldown menu to snapshot window positions. [[File:Dopus5 save layout.png|320px]]
# Open Environment settings from the "Settings/Environment..." pulldown menu and select "Workbench: Use" to a display mode. Click "Save" button. [[File:Dopus5 display mode.png|320px]] Directory Opus uses the Ambient screen now: [[File:Dopus5 on ambient screen.png|320px]]
# Open the D2A drawer and copy the D2A program to your WBStartup drawer (to be started on boot). [[File:Dopus5 d2a to wbstartup.png|320px]]
# (Optional step) By defalut D2A will open a DOpus lister when doing the double click on the desktop, but it may clash with the similar function in Ambient if you have enabled it. D2A can be configured to open the DOpus lister with a single middle (wheel) click instead. Open the icon information window of the D2A in your WBStartup drawer (right click on it and select "Information..." or left click to select the icon and lcommand-i from the keyboard). Double click the "MIDDLE" tooltype so that parentheses around it are removed. Click "Save" button. [[File:Dopus5 d2a tooltypes.png|320px]]
# (Optional step) If you want to disable the progress bar on the program startup, you can tune it with the D2A tooltypes too. Add a new tooltype <tt>DOPUS_COMMAND=Run DETACH QUIET DOpus5:DirectoryOpus QUIET</tt> and save it. The last QUIET disables the progress bar. [[File:Dopus5 disabling progressbar.png|320px]]

If you now have Directory Opus quitted and double click the D2A icon on the WBStartup drawer (or reboot the computer), Directory Opus will load and it shows the little main window for a few seconds until it gets hidden. The rest of DOpus windows will stay visible on the Ambient screen and you can open new DOpus listers by middle click on empty space on the Ambient desktop (or double left click if you skipped the first optional step).

:: [[File:Dopus5 main window hidden.png|320px]]

The main window can be moved somewhere else on the screen to be less noticeable at the boot. For example to the lower right corner where it doesn't pop up over the drive icons. You can unhide the hidden window with ctrl-alt-u or ctrl-alt-a keyboard combinations if you want to move it after the hiding. I also like to close all DOpus windows to let it be more under the hood on the startup. Use "Save Layout" again to snapshot the window setup and positions.

:: [[File:Dopus5 saving layout with everything hidden.png|320px]]

Directory Opus running under the hood after a reboot, available with a one click:

:: [[File:Dopus5 hidden on boot.png|320px]]

== Configuration ==

=== Enabling the Archive Browsing with XADopus ===

# Make sure that you don't have any archive filetypes enabled. The File Types window in Directory Opus should look like this after the initial installation: [[File:Dopus5 filetypes cleared.png|320px]]
# Download [http://aminet.net/package/util/dopus/XADopus.lha XADopus] archive from Aminet.
# Copy '''Modules/XADopus.module''' file from the downloaded archive to DOpus5:Modules/ directory.
# Copy contents of the '''Filetypes''' directory from the downloaded archive to the DOpus5:Filetypes/ directory. [[File:Dopus5 copy xadopus filetypes.png|320px]] Your File Types window should look like this after that and you're ready to browse archives: [[File:Dopus5 filetypes xadopus.png|320px]]

=== Environment variables ===

Type this in the shell to view certain pictures in more MorphOS friendly way:

<tt>Setenv SAVE DOpus/ShowUseDatatypesFirst 1</tt>

=== Environment Settings ===

The default settings are very modest in Directory Opus and you should go through the settings and read the documentation to get an impression what could be useful for you. Here are the most significant environment settings which should at least be enabled.

# Filename Length should be increased to the maximum of 107 characters. [[File:Dopus5 filename length.png|320px]]
# It's probably a good idea to enable the RTG Mode for NewIcons. [[File:Dopus5_rtg_mode.png|320px]]
# Name Mode PopUp (RMB contextual menus on name mode listers) and Inline Editing (realtime filename/date/protectionbit/comment/etc renaming) are very powerful options which should be enabled always. [[File:Dopus5_namemodepopup_inlineedit.png|320px]]
# Thin Gadget Borders will look better on 1x1 pixel displays nowadays. Enabling "Mouse buttons over inactive banks" did cause some issues on MorphOS 1.x, but quickly tried it wouldn't look like that anymore, but keep it in mind if you decide to enable it. [[File:Dopus5_tgb.png|320px]]

=== Filetypes ===

Filetypes system is the heart of Directory Opus in practise. Filetypes will identify the type of a file and define actions available for it. Every user should create new filetypes according the other software, needs, and configurations they have and prefer, but [http://jpv.wmhost.com/files/dopus_filetypes_morphos.lha here] is a small collection for starters. It should work generally under any MorphOS setup. Copy the filetypes found in it to your DOpus5:Filetypes/ directory.

The [http://jpv.wmhost.com/files/dopus_filetypes_morphos.lha collection] includes the next filetypes:

'''All''' - a filetype for all files
* Double click (with Ctrl key pressed): SmartRead
* Double click (Alt): Version
* Drag&drop: Copy MOVEWHENSAME
* Context menu: Duplicate, SmartRead, Version, Open with XAD
'''All, Directories''' - a filetype for all directories
* Double click (Ctrl): GetSizes
* Drag&drop: Copy MOVEWHENSAME
* Context menu: Get size, Find file, Burn to Disc
'''Archive, LHA'''
* Double click: browse the archive with XADopus
* Drag&drop: extracts to the destination
* Context menu: Extract to, Extract to RAM:, Extract here
'''Archive, XZ'''
* Double click: browse the archive with XADopus
* Context menu: Extract here
'''ASCII'''
* Double click: Multiview
* Context menu: Edit with Ed, Edit with Scribble
'''Audio, MP3'''
* Double click: Play in Jukebox
'''Document, AmigaGuide'''
* Double click: Multiview
'''Document, HTML'''
* Double click: OpenURL
'''Document, PDF'''
* Double click: View with VPDF
* Context menu: View with APDF
'''Executable, ELF''' - Recognizes MorphOS PPC native executable files
* Double click: runs the file as shell command and asks arguments for it
* Double click (Ctrl): runs the program with WBRun, like you'd clicked the icon
* Context menu: Execute with WBRun
'''Image file, ADF'''
* Double click: browse the image with XADopus
'''Image file, ISO'''
* Double click: browses the image on Ambient
* Context menu: Mount, Burn to Disc
'''Picture''' - a filetype for all picture files recognized by the datatypes
* Double click: views the picture by Ambient definitions
* Context menu: View in Showgirls
'''Version'''
* Double click: shows the version information for the following type of files: library, device, gadget, datatype, handler, mcp, mcc, mui
* This is very simple output from the Version command. For a more advanced version I'd use the WB-Version command or Severin's cool [http://www.amigans.net/modules/xforum/viewtopic.php?post_id=82855#forumpost82855 script] for example.
'''Video'''
* Double click: plays the popular video formats by Ambient definitions

[[File:Dopus5_filetypes_example.png|320px]]

=== Misc ===

Directory Opus is a very flexible and configurable program. Play around, learn, and remember RMB menus and ctrl key options in many places. Button banks and Start Menus do work over Ambient screen, hotkeys do also work fine and with the global hotkeys option you can use Directory Opus as a general purpose hotkey manager too.

Graphical tuning requires mostly icon files or IFF images, but when converted to the correct formats you'll get the look you want.

Here's an example video how you can tune Start Menus on MorphOS for example: https://www.youtube.com/watch?v=lRrIi0datLs

And here are some examples of different lister toolbar images. MagicWB one comes with the install disk and others can be found from Aminet for example.

[[File:Dopus5_listerbuttons_mwb.png]] [[File:Dopus5_listerbuttons.png]]

3rd party modules should work generally, but of course ones hitting the original Amiga hw (like some audio players) won't work. I'd recommend for example CycleMode (for cycling lister view modes from the keyboard), RootParent (to view the device list if going parent from the root level), and CutNPaste (copy/cut/paste files).

Directory Opus manuals are available at least in these places:

[http://aminet.net/package/util/dopus/dopus_5_pdf_manual Remastered manuals in Aminet]

[http://amiga.unikko.org/DOpus5-MagellanII/ Original scanned manuals]

Happy tuning! :)

Supported HD cards

2023-08-21T11:06:38Z

Polluks: https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12785&forum=53&start=7

Supported HD cards for PCIe-based [[Supported_Computers#Power_Macintosh_G5|PowerMac G5]] by user experience:
* HD3450 works
* HD3650 works
* HD4550 works
* HD4650 works
* HD5450 works
* HD6450 doesn't work
* HD6570 doesn't work
''NB working conditions may depend on detailed info on memory size and/or vendor plus output connector options.''

Main Page

2023-08-21T10:55:02Z

Polluks: /* Articles */ Supported HD cards

__NOTOC__

<div id="siteLogo" style="float: right;"></div>

<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#274572;">Welcome to the MorphOS Library,</div>
<div style="top:+0.2em; font-size:95%; margin-bottom: 30px;">the wiki based library of MorphOS related documentation.</div>

Would you like to contribute and edit articles? 
Please contact us to set up an account via:
<div style="margin-top: -10px; margin-bottom: 20px;">https://morph.zone/message2library.png</div>
'''Important notes to editors:''' [[Basic Guidelines]] - [[List of Wanted Articles]]
----
This page in other languages: [[Strona główna|Polish]] [[Page principale|Français]]

==About MorphOS==
MorphOS - The Lightning OS
<div class="threecolumns">
* [[What is MorphOS?]]
* [[Hardware Platforms]]
* [[Installation]]
* [[Characteristic features]]
* [[MorphOS integration]]
* [[MorphOS Development]]
* [[Developer tools]]
* [[3D graphics]]
* [[Games]]
* [[MorphOS key applications]]
* [[Platform expansion]]
* [[Who needs MorphOS?]]
* [[Conclusions]]
* [[Useful links]]
* [[F.A.Q.]]
* [[Historical notes]]
* [[Contributors]]</div>
A five minute read for users familiar with the Commodore Amiga
*[[MorphOS in 5 minutes]]

==Articles==
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.

* [[Fundamentals of MorphOS]]
* [[Dictionary of Terms]]
* [[First_Steps_Using_MorphOS | First Steps Using MorphOS]]
* [[Volume Names]]
* [[Applications|Applications Included with MorphOS]]
* [[Tools|Tools Included with MorphOS]]
* [[Utilities|Utilities Included with MorphOS]]
* [[Screenbar_Modules|Screenbar Modules Included with MorphOS]]
* [[Bundled_Games|Games Included with MorphOS]]
* [[Blankers|Blankers Included with MorphOS]]
* [[Shell Commands|Shell: Commands]]
* [[Pattern matching|Shell: Pattern Matching]]
* [[Filesystems | File Systems]]
* [[Supported Computers]]
* [[Supported HD cards]]
* [[Hardware Compatibility]]
* [[MIDI | MIDI Support]]
* [[Tips and Tricks]]

==Tutorials==
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.

*[[Getting_Started | Getting Started - A Beginner's Guide to MorphOS]]
*[[Modifying the User-Startup file]]
*[[Configuring_Network | Configuring a Network Connection]]
*[[Installing_software | Installing Third Party Software]]
*[[Dual-boot MorphOS and MacOS X on a Mac Mini G4]]
*[[How to write Mails with SimpleMail]]
*[[Creating Backups]]
*[[MorphOS External USB Drive Backup Guide]]
*[[Scanning with SCANdal]]
*[[Recording an LP with Audio Evolution 4]]
*[[Passwordless SSH login with RemoteShell]]
*[[How to Install Directory Opus Magellan II]]
*[[How to Make MorphOS Look Like OS4]]
*[[How to Use Game Controllers]]
*[[Preparing_an_Amiga_Hard_Drive]]
*[[Mounting_Network_Drives]]
*[[How to translate program with SimpleCat]]
*[[Creating_Ambient_Filetypes]]
*[[Open_Firmware | Using Open Firmware]]
*[[Print_System | Using the New Printing System]]
*[[Multi-display | Using Multi-display Setups]]

==Development==
In the development section of the MorphOS Library, you can find a collection of helpful articles and tutorials focused on MorphOS software development.

*[[First steps in MorphOS programming]]
*[[Magic User Interface Programming]]
*[[In-depth: The New MorphOS Memory System]]
*[[Reggae: MorphOS multimedia framework]]
*[[An Introduction to MorphOS PPC Assembly]]
*[[Advanced Topics]]
*[[Getting Started with Lua]]
*[[Crash_Course_to_Hollywood_Programming]]

==Benchmarks, Reports & Reviews==
*[[jPV's MorphOS 2 Review]]
*[[What's New in MorphOS 3]]
*[[What's New in MorphOS 3.10]]
*[[What's New in MorphOS 3.16]]

==Links==
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.

*[[Links#Community_Portals_.26_Forums|Community Portals]]
*[[Links#File_Repositories|File Repositories]]
*[[Links#Shops|Shops]]
*[[Links#Software|Software]]
*[[Links#Developers|Developers]]
*[[Links#Misc|Misc]]

==Work in Progress==
*[[ReTooled]]

Shell Commands/Break

2023-08-02T11:09:34Z

Polluks: See also

'''Break''' - Allows to send a signal (for eg. CTRL+C) to a process

PROCESS/N, PORT, ALL/S, C/S, D/S, E/S, F/S
<nowiki>
PROCESS - number of the process to send a signal to
PORT - public port name of the process to send a signal to
ALL - sends all signals to the process (see below)
C - sends a CTRL+C
D - sends a CTRL+D
E - sends a CTRL+E
F - sends a CTRL+F</nowiki>
Break sets the specified attention flags in the PROCESS indicated.
Use the Status command to display the current process numbers.
By default, only the Ctrl+C flag is set.

Break acts the same as selecting the relevant process by clicking
in its window and pressing the appropriate Ctrl+key combinations.

Ctrl+C is the default for sending a Break signal to halt a process.
A process that has been aborted this way displays ***Break
in the Shell window. Ctrl+D halts execution of a script file. Ctrl+E closes a process' window. Ctrl+F activates the process' window.

See also: [[Shell_Commands/Status | Status]] command.

Shell Commands/TaskList

2023-08-02T11:04:59Z

Polluks:

'''TaskList''' - Displays a detailed list of all running tasks

VERBOSE/S
<nowiki>
VERBOSE - Be verbose for each task</nowiki>
When using the VERBOSE switch, a lot of details, including
the 68k and PPC stack pointers, Wait signals,... are reported.

See also: [[Shell_Commands/Status | Status]] and [[Shell_Commands/Break | Break]] commands.

Applications/Jalapeno

2023-07-15T19:15:30Z

Polluks: /* Description */ mkisofs

== Description ==

Very user friendly CD/DVD authoring and imaging tool.
Supports burning ISO files to disc, burning data files to disc and creating image files from CD/DVDs and [http://library.morph.zone/Tips_and_Tricks#Creating_an_ISO_Image from filesystem]. It's a frontend of mkisofs.

== Screenshots ==

: [[File:MorphOS3_jPV_Jalapeno1.png|300px]] [[File:MorphOS3_jPV_Jalapeno2.png|300px]] [[File:MorphOS3_jPV_Jalapeno3.png|300px]]

Utilities/ArchiveIt

2023-06-19T22:48:20Z

Polluks: /* Description */ zip.library

== Description ==
An archive creator and extractor application, which currently supports ZIP archives using zip.library (with the password support).

== Screenshots ==
: [[File:ArchiveIt_1.png]]
: [[File:ArchiveIt_2.png]]

Utilities/TaskManager

2023-06-15T14:40:00Z

Polluks: /* Notes */ DEVELOPERMODE

== Description ==
System monitoring tool.

Lists running processes and tasks, allows adjusting the priority of tasks and sending break signals.

== Usage ==

== Notes ==
The tooltype DEVELOPERMODE enables a menu item "Dump State", see [[Applications/LogTool|LogTool]].

== Screenshot ==
: [[File:TaskManager.png]]

Tools/PFSDoctor

2023-05-04T14:28:56Z

Polluks: Screenshot

== Description ==
Diagnostic and repair tool for PFS formatted partitions.

== Usage ==

== Notes ==

== Screenshot ==
: [[File:PFSDoctor.png]]

Links

2022-09-19T12:34:48Z

Polluks: /* Software */ new name of MUIBase

==Official MorphOS Website==
* http://www.morphos-team.net

==Community Portals & Forums==
* http://morph.zone

* https://www.morphos-forum.de

* http://www.pegasos.org

* http://www.pegasos.hu

* http://www.ppa.pl

* http://saku.bbs.fi/foorumi

* http://www.warmup-asso.org

* http://www.warmup-asso.fr

* http://www.morphos-store.com - A website to buy and sell MorphOS hardware and software.

==File Repositories==

* http://mos.aminet.net - Aminet MorphOS Section

* http://www.morphos-storage.net - MorphOS Storage by WArMUp

* http://morphos-files.ppa.pl - MorphOS File Hosting Service (abandoned)

* http://morphos.lukysoft.cz - MorphOS Software Database

==Shops==

* https://www.morphos-store.com

==Software==

Demoscene

* http://amiga.bbs.fi/demopack_morphos/ - MorphOS Demopack

Emulation

* http://www.amidog.com/amiga/fpse/ - Free PlayStation Emulator, ported by Mathias 'AmiDog' Roslund

* http://ace.cpcscene.net/en:introduction - The acidulous CPC/CPC+ emulator.

Internet & Network

* http://www.amipodder.com - AmiPodder, free podcast client

* http://www.heightanxiety.com/AmiSSL/ - Port of OpenSSL for legacy applications

* http://amitradecenter.net - AmiTradeCenter, FTP client

* http://www.students.tut.fi/~komsa/amiga/beehive/ - Home of Beehive, a BitTorrent client

* http://sourceforge.net/projects/simplemail/ - SimpleMail, open source email client

* http://www.yam.ch - YAM, open source email client

* http://www.amirc.org - The famous IRC client

Music

* http://www.digiboosterpro.de/en/ - Home of Digibooster Pro

* http://jahjah.free.fr/morphos/ - Home of Ripper, a CD music ripping and conversion tool

* http://amigadev.free.fr/songplayer/index_en.html - Home of SongPlayer, a music player

* http://tcheko.binaryriot.org/soundbankster/ - A realtime audio mixing application dedicated to DJ enthusiasts

Office

* http://amigadev.free.fr/pointrider/ - PowerPoint viewer application

* http://www.grasshopperllc.com - Home of Pagestream, a commercial desktop publishing / page layout software

* http://beebase.sourceforge.net - Home of BeeBase aka MUIBase, Steffen Gutmann's relational programmable database (with GUI)

* http://shinkuro.altervista.org/amiga/software/nowined.htm - Home of NoWinEd, text editor

* http://www.winfield.demon.nl - Free MS Word reader

Package Management

* http://www.geit.de/eng_grunch.html - Search, download, install, update, and uninstall programs

System

* http://morphosambient.sourceforge.net - Ambient 'desktop' environment

* http://scalos.noname.fr - Scalos desktop, an alternative to Ambient

* http://sourceforge.net/projects/snoopium/ - System monitor application.

* http://sourceforge.net/projects/backman/ - Backman, open source backup program

* http://amigazeux.net/diavolo/ - Diavolo Backup, formerly commercial backup program

==Developers==

* http://amigazeux.org - AmiNet Radio, Dragon, Wetter, SkinClock, and much more.

* http://polymere.free.fr/index_en.html - Home of PolyNet (icon bar), PolyOrganizer and PolyGlot (MSN messenger)

* http://members.shaw.ca/realstar/ - Developer of the Aqua, Eve and HyperCannon game titles.

* http://fabportnawak.free.fr - MPlayer, ScummVM, Odyssey Web Browser, MAME, and more.

* http://krashan.ppa.pl - DigiBooster 3, MorphOS Programmer's Handbook, audio tools, and more.

* http://tbs-software.com/morgoth/

* http://khtml.ppa.pl

* http://bigfoot.morphos-team.net

* http://dreamolers.binaryriot.org

* http://tokai.binaryriot.org

* http://www.biclodon.com

* http://www.iki.fi/sintonen

* http://www.tbs-software.com/stefkos/

* http://home.elka.pw.edu.pl/~mszyprow/programy/ - Author of SFSDoctor.

* http://kiero.binaryriot.org - Freespace 1&2, Foobilliard, Homeworld, scube, szoom, and more.

* http://www.geit.de - Home of Grunch, MagicBeacon, MMKeyboard, and more.

* http://yellowblue.free.fr - Home of Yomgui, who maintains Blender, Python, PyMUI and Helios (Firewire)

* http://www.orel.rekom.ru/~imax/ - Maxim Ilyin ported VirtualJaguar, Mike Steed's FlashPlayer, and more.

* http://haru.at/ - Creator of MorphUp packagement system, ported VLC, MLDonkey, and more.

* http://www.amirus.org.ru - Various utilities such a KeyMorpher, a MUI-based key mapper. (Website is in Russian.)

* http://tbs-software.com/mark/ - Developer of PowerD, various utilities.

* http://tbs-software.com/powerd/ - PowerD programming language

* http://www.lukysoft.cz - Home of Lukáš Stehlík (AmiGod benchmark)

* http://dasixk.free.fr - Home of SixK, who ported a multitude of apps

* http://alfie.altervista.org - Home of Alfonso 'alfie' Ranieri, creator of RxMUI, AmRSS (RSS client), and much more.

* http://morphware.schwarzes.net - Various small tools made by Andreas Schwarz.

* http://www.onyxsoft.se - Home of Onyxsoft who have released a number of applications and games.

* http://www.mguc.ppa.pl - Marian Guc's website, developer of PciTool, AutoDoc Reader and the unfinished Nemesis desktop.

* http://brain.umcs.lublin.pl/~rzookol/ - Michał Żukowski's website, developer of SCANdal (scanner software)

* http://www.igracki.de - gTranslator, yWeather, CRABUM, and more.

* http://www.morguesoft.eu - Various screen savers.

* http://tcheko.binaryriot.org/ - SoundBankster, commodities, utils.

* http://bszili.morphos.me/ - Home of BSzili, who has ported numerous games.

* http://jpv.wmhost.com/jpv_software/ - Hollywood applications and Lua, ARexx, and shell scripts.

==Misc==

* http://www.via-altera.de/mid.htm - some documents about MorphOS (German/English)
* https://morphosuser.wordpress.com - Yasu's MorphOS Blog
* http://pegasos.lena-johannson.de/ - Otti website with many Deutsch translations

Reggae tutorial: Accessing Reggae in applications

2022-04-26T14:34:35Z

Polluks:

Reggae is operated from application with two APIs. One of them is generic object oriented BOOPSI API with its ''DoMethod()'', ''GetAttr()'', ''SetAttrs()'' etc. The second API is just a shared MorphOS library one, provided by ''multimedia.class'' and is, of course, Reggae specific. To use Reggae one must open ''multimedia.class'' as every shared library. For BOOPSI API ''intuition.library'' must be opened, which almost all programs do anyway.

==Opening and closing multimedia.class==
The first step is to add needed includes:

#include <proto/multimedia.h>
#include <proto/exec.h>
#include <proto/intuition.h>
#include <clib/alib_protos.h>

The first file contains definition of multimedia.class library API. It also includes ''<classes/multimedia/multimedia.h>'', containing Reggae structures, constants, tags and macros. The rest of includes are not Reggae specific, in fact most projects include them anyway, as they define basic system services. There are also additional Reggae headers, their including depends on application and will be covered in further tutorials.

Now we are ready for Reggae initialization. All what has to be done is opening ''multimedia.class'' just like an ordinary MorphOS shared library. The only noticeable difference is that library name contains path part, as Reggae classes are not directly on library search path:

struct Library* MultimediaBase;

if (MultimediaBase = OpenLibrary("multimedia/multimedia.class", 52))
{
  /* Now Reggae is ready to use until the library is closed. */
  CloseLibrary(MultimediaBase);
}

As with every library, the name of the base is important, as it is implicitly used in all calls to the library API as a hidden parameter. Note also the usual error handling, ''multimedia.class'' is disk-based and also performs some disk activity at startup, then checking the library base against NULL is recommended. 52 is the current ''multimedia.class'' version. Applications should request this version, as previous ones have some important features missing. Reggae cleanup is done with classic ''CloseLibrary()'' call.

'''Note:''' Some programmers use automatic library opening and closing by linking with ''libauto''. ''multimedia.class'' can be added to the list of automatically opened libraries, but it is not added by default.

A complete [http://krashan.ppa.pl/reggae/files/tutorial_basic.c example code] shows Reggae initialization. The example opens ''multimedia.class'' and, if it succeeded, prints the version and revision of ''multimedia.class'' to the console.
==Opening and closing individual classes==
Typical Reggae usage is just calling ''MediaNewObject()'' to get a data stream recognized, demultiplexed and decoded down to [[Reggae_common_formats|common formats]] automatically. In this case Reggae opens (and later closes) all needed classes automatically. Things change, when application builds processing chain by hand, or just uses single components. Then every used class must be opened and closed explicitly. It is done in the same way as with ''multimedia.class''. Let's assume our application uses just ''http.stream'' object to download some data from the net. Before object creation class must be opened. It is typically done in application setup code:

struct Library *HttpStreamBase;

HttpStreamBase = OpenLibrary("multimedia/http.stream", 51);

As for every disk based library, checking the base against NULL is highly recommended. The class must be unloaded after use, for example in application cleanup:

CloseLibrary(HttpStreamBase);

Reggae classes are handled just like ordinary shared libraries. Note that "multimedia/" path is added to the class name, reason for this has been explained above. When a class is not used constantly in application, it may be a good idea to open it just before it is needed and close right after it is not needed anymore. For example if ''http.stream'' is used only for automatic application updates, there is no need to keep it opened after update checking/downloading. The last remark concerns names of library bases for classes. No Reggae class '''except of ''multimedia.class''''' has library-style API. Because of this library base name is not used for anything else than opening and closing the class. That is why, the name is not important and can be anything. In these tutorials, bases names derived from classes names are used, just for improved code readability.

==I don't like C/C++, what now?==
Reggae can be used from any programming language. It has to fulfill some minimal set of features however. The first one is ability to call functions from standard MorphOS shared libraries, ''intuition.library'' and ''exec.library'' at least. Then ability to call functions from ''multimedia.class''. Many programming languages used on MorphOS have tools for creating bindings (or stubs, or whatever it is called) to shared libraries, based on C headers and *.fd files. Creating bindings for ''multimedia.class'' should not be difficult then. Then the language must have ''DoMethod()'' call. For C/C++ this call is provided by ''libabox'', a static library. Another important feature is ability to handle tag-based functions in some sane way. Taglist can be always built by hand, but passing tags as arguments to variable args functions is convenient.

==NewObject() and MediaNewObject()==
These two functions have similar names, but they are different. Programmers using MUI may think that MediaNewObject() is some kind of wrapper around NewObject(), similarly to MUI_NewObject() being such a wrapper. This is not true for MediaNewObject() however. NewObject() is a basic BOOPSI call, and just creates an object of specified class. Reggae objects are created with this function as well.

MediaNewObject() creates a complete tree of objects needed to decode a media stream to basic formats. The tree consists of stream object, one or more demultiplexer objects, one or more decoder objects and a few auxiliary ones like multiread buffers or processblocks. The whole tree is presented to the application as a single object delivering decoded streams on its output ports.

Another difference between the two functions is automatic loading of Reggae classes. NewObject() call does not load a disk based BOOPSI class into memory automatically. Then an application must load such a class manually with OpenLibrary() before object creation (and unload it after use with CloseLibrary()). On the other hand MediaNewObject() opens all needed classes automatically and takes care of their unloading.

==Error Checking==
Many operations on Reggae objects may fail for different reasons. It may be just memory shortage, I/O error, wrong arguments passed by application etc. A good programming practice is to verify results of operations and take appropriate actions in case of failure. The first step of verification is checking method return value. Its exact meaning depends on the method itself, and is described in autodocs. The common cases are described below. The second stage of error checking is to get an error code of operation. This is done by getting a MMA_ErrorCode attribute value from an object. Error code values are defined in <classes/multimedia/multimedia.h> header file. The usual way is just getting the attribute from an object, which is done with BOOPSI call GetAttr().

LONG error;

GetAttr(object, MMA_ErrorCode, (ULONG)&error);

Alternatively, one can get the attribute through any of object's port (input or output, it does not matter):

error = MediaGetPort(object, 0, MMA_ErrorCode);

==Errors During Object Creation==
Creation of an object is a special case in error handling for two reasons. Firstly, this is the most probable place for errors, as creating a new Reggae object may be a complex operation involving creation of many basic objects, connecting them, performing I/O operations on data source, parsing stream headers etc. Secondly – if object creation fails, there is no object to ask for MMA_ErrorCode attribute. That is why MMA_ErrorCode can be passed to OM_NEW() method (that means NewObject() and MediaNewObject() accept it), and its tag value contains a pointer to a variable, where error code will be placed. An example code below shows error handling during object creation:

Object *obj;
LONG error = 0; /* initialization is recommended */

if (obj = MediaNewObjectTags( /* any tags here */ , MMA_ErrorCode, (IPTR)&error, TAG_END))
{
/* use object */
}
else
{
/* error code is in 'error' variable, take some action, inform user etc. */
}

==Errors During Data Pulling==
The first stage of error checking in this case is checking the return value of MMM_Pull() method. When there is no error, it should be equal to the amount of bytes requested. If it is not the case, one should get MMA_ErrorCode value, as described above. There is one case however, when the value returned by MMM_Pull() will be not equal to the request size, and MMA_ErrorCode will be zero. It can happen, when the request size is not aligned to the smallest chunk allowed by Reggae. This chunk is a single pixel for video, and a single sample frame for audio. Such a misaligned pull request is truncated silently and only the whole chunks are returned. That is why aligning request size to the size of a pixel or sample frame should be a rule of thumb while programming Reggae. A code fragment below demonstrates error checking after MMM_Pull():

if ((pulled = DoMethod(MMM_Pull, object, port, buffer, length)) == length)
{
/* Data pull has been succesfull. */
}
else
{
LONG error = 0;

GetAttr(object, MMA_ErrorCode, (IPTR)&error);

/* Data pull failed, some data can be valid however (number of valid
data bytes is stored in 'pulled'). Error code is in 'error'. */
}

==Displaying Error Messages==
Some of Reggae errors (especially those, which are somehow expected, like file or network I/O errors) should be reported to user. Note that for less probable errors advanced users may use MediaLogger, which shows Reggae event log. Basic problems however should be reported by application. Of course displaying some cryptic error code is not recommended. The simplest way is to use MediaFault() function to convert these codes into text messages. A big advantage of MediaFault() is that its messages are localized, so it automatically returns texts in user's preferred language. The function may be for example used as follows:

LONG error;

GetAttr(object, MMA_ErrorCode, (IPTR)&error);

if (error) Printf("Operation failed: %s.\n", MediaFault(error));

This simple example prints message to a console, GUI based programs will pass it to ''MUI_Request()'' for example. Strings returned by ''MediaFault()'' are not capitalized and have no dot at the end.

Shell Commands/DRadioTool

2022-04-19T22:44:56Z

Polluks: typo

'''DRadioTool''' - Controls a USB Radio manufactured by D-Link or GemTek

ON/S, OFF/S, FREQ/K/N, SCAN/S, AUTO/S, SIGNAL/S, UNIT/N/K
<nowiki>
ON - turns the radio ON
OFF - turns the radio OFF again
FREQ - sets the current frequency to the given value. It must be
given in kHz and range between 87 MHz and 108 MHz.
SCAN - starts a frequency scan. It starts at 87 MHz, if no FREQ value
had been given and stops at 107 MHz. If a radio channel is
detected it will output its frequency in KHz on the shell.
The last found channel will be kept. The scan can be aborted
at any time using Ctrl-C.
AUTO - only useful in conjunction with the SCAN switch. If a station
is found, the program will pause for three seconds, asking the
user to press Ctrl-C to keep the radio station found.
SIGNAL - sets the shell return value to WARN (5), if no radio station
is detected on the current frequency. If there's a stereo
signal, it will return OK (0). This switch can be used to
implement a manual scan routine.
UNIT - if multiple radios are connected, you can choose the right
unit with this argument. Defaults to unit 0 of course.

Examples: DRadioTool ON SCAN AUTO
DRadioTool FREQ 104000</nowiki>

Shell Commands/SonixCamTool

2022-04-19T22:44:13Z

Polluks: typo

'''SonixCamTool''' - Read out images from a USB webcam using the Sonix Technologies chipset with OV7630 sensors.

TO/A, INTERVAL/N, UPTO/N/K, GAMMA/K, SHARPEN/S, TEXT/K, FONT/K, FONTSIZE/N/K, UNIT/N/K
<nowiki>
TO/A - mandatory filename to save the picture to. This filename
may also contain a format string such as "%ld" (do not
forget the 'l') to generate a number when using the
INTERVAL option.

INTERVAL/N - if this numeric parameter is given, SonixcamTool will loop
and take pictures at the given interval (in ticks, 50
ticks is one second). Use Ctrl-C to abort the
SonixcamTool.

UPTO/N/K - if specified, multiple pictures can be grabbed in one go,
stopping after the UPTO pictures. Be sure to give a format
string such as "%ld" inside the filename or you will write
all pictures to the same image. Only useful together with
INTERVAL.

GAMMA/K - enable white balance and gamma correction with the given
floating point gamma value. 0.45 is a good setting. If you
only want white balance and no gamma correction, use a
value of 1.0.

SHARPEN/S - apply a highly optimized 5x5 sharpen filter on the image.

TEXT/K - optionally adds the given line of text to the bottom of
the picture. If the line is too long to fit, it will be
truncated.

FONT/K - name of the font to use (e.g. xen.font). If this parameter
is missing, the default system font will be used.

FONTSIZE/N/K - size of the font in pixels

UNIT/N/K - if several cameras are connected, specify the unit to use.
Defaults to unit 0.
</nowiki>
Examples:
<nowiki>
SonixcamTool Snap.ppm
SonixcamTool Snap.ppm GAMMA 0.45 SHARPEN
SonixcamTool Movie%04ld.ppm INTERVAL 0 GAMMA 0.5
SonixcamTool Webcam.ppm GAMMA 0.45 SHARPEN TEXT "Platon's Cam"
FONT small.font FONTSIZE 6
SonixcamTool Shotseries%03ld.ppm INTERVAL 0 UPTO 79 GAMMA 0.45 SHARPEN
</nowiki>

Filesystems

2022-04-08T21:29:10Z

Polluks: /* Disk File Systems */

== About ==
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]]).

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

== Disk File Systems ==

{| class="wikitable"
! style="text-align:left;"| Name
! style="text-align:left;"| Location
! style="text-align:left;"| Bootable
! style="text-align:left;"| Native File Properties
! style="text-align:left;"| Max File Name Length
! style="text-align:left;"| Max File Size
! style="text-align:left;"| Max Partition Size
! style="text-align:left;"| Notes
|-
| Smart File System (SFS)
| Built-in (boot.img)
| Yes
| Yes
| 107
| 4 GiB - 2 bytes
| 128 GiB
| The default file system
|-
| Professional File System III (PFS3)
| Built-in (boot.img)
| Yes
| Yes
| 107
| 2 GiB
| 104 GiB
| Legacy support for PFS2 and AFS1
|-
| Fast File System 2 (FFS)
| Built-in (boot.img)
| Yes
| Yes
| 107
| 4 GiB - 2 bytes
| 2 TiB to 128 TiB
| Legacy support for OFS and FFS
|-
| FAT File System (FAT)
| Built-in (boot.img)
| Yes
| No
| 255* (UCS-2)
| 4 GiB
| 2 TiB
| Supports FAT12, FAT16, and FAT32 with LFN
|-
| Mac File System (HFS)
| Built-in (MOSSYS:L)
| No
| No
| 31
| 2 GiB
| 2 TiB
|
|-
| Hierarchical File System (HFS+)
| Built-in (MOSSYS:L)
| No
| No
| 255* (UTF-16)
| 2 TiB**
| 2 TiB**
| Read-only
|-
| Second Extended File System (ext2, ext3, ext4)
| Built-in (MOSSYS:L)
| No
| No
| 255*
| 16 GiB to 2 TiB
| 2 TiB
| Limited read-only support for ext4
|-
| NT File System (NTFS)
| Built-in (MOSSYS:L)
| No
| No
| 255*
| 2 TiB**
| 2 TiB**
| Read-only
|-
| SGI X File System (XFS)
| Built-in (MOSSYS:L)
| No
| No
| 255*
| 2 TiB**
| 2 TiB**
| Read-only
|-
| Ice File System (IceFS)
| 3rd party ([http://blubbedev.net/icefs/ link])
| Yes/No
| Yes
| 107 (255)
| 9 EB
| 9 EB
| Bootable on Pegasos and Efika, but not on Macs
|-
| ExFAT File System (ExFAT)
| 3rd party ([http://www.morphos-storage.net/?page=System/Devices/HD/Filesystems&file=exFAT-FS_1.1.lha link])
| No
| No
| 255 UTF-16
| 128 PiB
| 128 PiB
|
|-
| NT File System 3G (NTFS-3G)
| 3rd party ([http://blubbedev.net/filesysbox/ link])
| No
| No
| 255
| 16 EiB
| 16 EiB
| Can't be placed on RDB
|-
| FS1541
| 3rd party ([http://aminet.net/package/disk/misc/FS1541-MorphOS link])
| No
| No
| 16
| 164 KiB
| 170 KiB
| For CBM 1541 disks/images
|-
| CDRive File System (CDFS)
| Built-in (boot.img)
| Yes
| Yes
| 255*
|
|
| ISO 9660/Amiga Rock Ridge/Joliet, audio as WAV files, ISO file support
|}

<nowiki>* </nowiki>Filenames over 107 characters will be stripped

<nowiki>** </nowiki>Theoretical sizes may be bigger, but filesystems using deviceio.library are limited to 2 TiB

== Network File Systems ==

{| class="wikitable"
! style="text-align:left;"| Name
! style="text-align:left;"| Location
! style="text-align:left;"| Native File Properties
! style="text-align:left;"| Notes
|-
| [http://library.morph.zone/Mounting_Network_Drives#SmbFS SmbFS]
| Built-in (MOSSYS:C)
| No
| For mounting Windows shares or Samba shares on other platforms
|-
| [https://library.morph.zone/Mounting_Network_Drives#Ssh2FS Ssh2FS]
| Built-in (MOSSYS:C)
| No
| For mounting SFTP shares on other platforms
|-
| [http://library.morph.zone/Mounting_Network_Drives#NetFS_Revised NetFS Revised]
| 3rd party ([http://aminet.net/package/comm/net/NetFS-revised link])
| Yes
| For mounting partitions between MorphOS and/or AmigaOS systems
|-
| [http://library.morph.zone/Mounting_Network_Drives#FTPMount FTPMount]
| 3rd party ([http://aminet.net/package/comm/tcp/FTPMount_MOS link])
| No
| For mounting FTP sites as part of a filesystem
|-
| [http://library.morph.zone/Mounting_Network_Drives#Google_Drive_and_Dropbox_Handlers Amiga Cloud Handlers]
| 3rd party ([http://aminet.net/package/comm/tcp/AmigaCloudHandlers link])
| No
| For mounting Google Drive and Dropbox storage
|}

Supported Computers

2022-02-11T08:34:23Z

Polluks: /* iMac */ 17-Inch

''Originally published at: http://www.amiga.org/forums/showthread.php?t=65055''

''Author: takemehomegrandma''

This is a list of complete computer setups for MorphOS use. More detailed harware support information is available at http://morphos-team.net/hardware

MorphOS has certain limits for the main memory on all supported systems. Quark kernel can use up to 2GiB of memory and ABox up to 1.7GiB. If more than 2GiB of memory is installed, it is just ignored. Some systems also have lower physical limits.

== Genesi Hardware ==

In the beginning of the MorphOS journey, Genesi and bPlan played an important role of the early MorphOS development in many fundamental ways. Providing resources was one, providing a new HW platform was another. Although Genesi and the MorphOS Team later moved in separate directions, a legacy remains in the shape of two official Genesi systems that MorphOS runs on, and a few mainboards (motherboards) besides that.

Of course, those mainboards were also used as a central component by *several* third party resellers when they put together their own various systems (of various configurations) for their customers that probably still is available from time to time on the second hand market. Those systems are not listed here though.

These mainboards that MorphOS runs on are:

* Pegasos 1 ("original"/unfixed), 750CXe G3 @ 600MHz
* Pegasos 1 (April 1), 750CXe G3 @ 600MHz
* Pegasos 1 (April 2), 750CXe G3 @ 600MHz
* Pegasos 2, 750CXe G3 @ 600MHz
* Pegasos 2, MPC7447 G4 @ 1.0GHz
* Efika 5200B

As previously mentioned, many systems were put together by numerous third party dealers based on these motherboards.

Official systems based on these were:

* [http://www.genesi-tech.com/products/opendesktop Open Desktop Workstation (ODW)]
* [http://www.genesi-tech.com/products/openclient/5200b EFIKA Open Client]

(BTW, The Efika mainboard, the case, and a bundle of board and case, can still be purchased new from [http://search.directron.com/newsearch.php?find=efika&x=-250&y=-93 Directron.com])

== Mac mini ==

We are many who has fallen in love with the Mac Mini, a very small footprint, highly integrated, silent, yet very powerful G4 computer. All models works fine with MorphOS, but if you can, you should look for the 1.5GHz silent upgrade version that has 64MB Video Memory. You *can* use MorphOS with the 32MB coming with the other versions (depending on how you use the computer, you may want to turn off some visual "bells and whistles" that MorphOS offers), but with 64MB you will have your back covered in a better way. And this is not something specific to the Mac Mini, but to MorphOS in general — if you have the option to get 64MB or more of Video Memory, do it!

Here is a list of supported Mac Mini machines, with links to the great "everymac.com" site with loads of additional, detailed information on each and every one of these:

* [http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.25.html Mac Mini G4/1.25]
* [http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.42.html Mac Mini G4/1.42]
* [http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.33.html Mac Mini G4/1.33] (silent upgrade)
* [http://www.everymac.com/systems/apple/mac_mini/specs/mac_mini_g4_1.5.html Mac Mini G4/1.5] (silent upgrade, '''with 64MB VRAM''')

== eMac ==

The eMac line, originally released exclusively to the education market and later available to the consumer market as well, features an all-in-one case design and affordable performance. It's especially "affordable" today, when you most certainly will pick one up for $0 (or thereabout). It has a CRT built in, which may show some blurry signs of age by now. But hey, its extremely low cost in combination with MorphOS and a G4 performance that "traditional Amigan's" only dreamt of, may very well make this machine interesting.

Here is a list of the supported eMac machines (those not listed here aren't supported), with links to the great "everymac.com" site with loads of additional, detailed information on each and every one of these:

* [http://www.everymac.com/systems/apple/emac/specs/emac_1.25.html eMac G4/1.25 (USB 2.0)] (This was also sold as 1.0 GHz version to educational market and it is supported too, but don't mix it to 1.0 GHz PowerMac4,4 which doesn't work.)
* [http://www.everymac.com/systems/apple/emac/specs/emac_1.42.html eMac G4/1.42 (2005)]

== Power Macintosh G4 ==

NVIDIA cards are not supported by MorphOS and would need to be replaced with a suitable Radeon card instead. Special Mac versions of Radeon cards should be used. A GFX card with 64MB or more VMEM is recommended.

Audio is currently only supported for PowerMac3,4 to 3,6 models.

DP = Dual Processors, but MorphOS only supports using one CPU, the other one will be sitting idle.

"Mac Server" is essentially the same HW as PowerMac but with server SW bundled. Doesn't matter if you are going to use it with MorphOS (right?).

Here is a list of supported Power Macintosh G4 machines, with links to the great "everymac.com" site with loads of additional, detailed information on each and every one of these:

* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_350_agp.html Power Macintosh G4 350 (AGP)], PowerMac3,1
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_400_agp.html Power Macintosh G4 400 (AGP)], PowerMac3,1
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_450.html Power Macintosh G4 450 (AGP)], PowerMac3,1
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_500.html Power Macintosh G4 500 (AGP)], PowerMac3,1
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_350.html Mac Server G4 350 (AGP)], PowerMac3,1
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_400.html Mac Server G4 400 (AGP)], PowerMac3,1
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_450.html Mac Server G4 450 (AGP)], PowerMac3,1
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_500.html Mac Server G4 500 (AGP)], PowerMac3,1
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_400_2.html Power Macintosh G4 400 (Gigabit)], PowerMac3,3
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_450_dp.html Power Macintosh G4 450 DP (Gigabit)], PowerMac3,3
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_500_dp.html Power Macintosh G4 500 DP (Gigabit)], PowerMac3,3
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_450_dp.html Mac Server G4 450 DP (Gigabit)], PowerMac3,3
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_500_dp.html Mac Server G4 500 DP (Gigabit)], PowerMac3,3
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_466.html Power Macintosh G4 466 (Digital Audio)], PowerMac3,4
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_533.html Power Macintosh G4 533 (Digital Audio)], PowerMac3,4, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_667.html Power Macintosh G4 667 (Digital Audio)], PowerMac3,4, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_733.html Power Macintosh G4 733 (Digital Audio)], PowerMac3,4, NVIDIA card
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_533.html Mac Server G4 533 (Digital Audio)], PowerMac3,4, NVIDIA card
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_533_dp.html Mac Server G4 533 DP (Digital Audio)], PowerMac3,4, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_733_qs.html Power Macintosh G4 733 (Quicksilver)], PowerMac3,5, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_800_dp_qs.html Power Macintosh G4 800 DP (Quicksilver)], PowerMac3,5, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_800_qs.html Power Macintosh G4 800 (QS 2002)], PowerMac3,5
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_867_qs.html Power Macintosh G4 867 (Quicksilver)], PowerMac3,5, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_933_qs.html Power Macintosh G4 933 (QS 2002)], PowerMac3,5, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1ghz_dp_qs.html Power Macintosh G4 1.0 DP (QS 2002)], PowerMac3,5, NVIDIA card
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_733_qs.html Mac Server G4 733 (Quicksilver)], PowerMac3,5, NVIDIA card
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_800_dp_qs.html Mac Server G4 800 DP (Quicksilver)], PowerMac3,5, NVIDIA card
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_933_qs.html Mac Server G4 933 (QS 2002)], PowerMac3,5
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_1ghz_dp_qs.html Mac Server G4 1.0 DP (QS 2002)], PowerMac3,5
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_867_dp_mdd.html Power Macintosh G4 867 DP (MDD)], PowerMac3,6, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.0_dp_mdd.html Power Macintosh G4 1.0 DP (MDD)], PowerMac3,6
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.25_dp_mdd.html Power Macintosh G4 1.25 DP (MDD)], PowerMac3,6
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.0_mdd.html Power Macintosh G4 1.0 (FW 800)], PowerMac3,6, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.25_dp_mdd_fw800.html Power Macintosh G4 1.25 DP (FW 800)], PowerMac3,6
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.42_dp_mdd.html Power Macintosh G4 1.42 DP (FW 800)], PowerMac3,6
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.25_mdd.html Power Macintosh G4 1.25 (MDD 2003)], PowerMac3,6
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_1.0_dp_mdd.html Mac Server G4 1.0 DP (MDD)], PowerMac3,6, NVIDIA card
* [http://www.everymac.com/systems/apple/mac_server_g4/specs/macserver_g4_1.25_dp_mdd.html Mac Server G4 1.25 DP (MDD)], PowerMac3,6

== PowerBook ==

MorphOS supports all G4 PowerBooks equipped with a Radeon graphics card. Audio isn't currently supported on Titanium (Ti) models.

The MorphOS PowerBook support includes most of the things you would need/expect from an OS supporting Laptops. Touchpad has some extra functionality on models 5,6-5,9.

Here is a list of supported PowerBook G4 machines, with links to the great "everymac.com" site with loads of additional, detailed information on each and every one of these:

* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_867.html PowerBook G4 867 (Ti)], PowerBook3,5 - A1025
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.0.html PowerBook G4 1.0 (Ti)], PowerBook3,5 - A1025
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.0_15.html PowerBook G4 1.0 15" (FW800 - Al)], PowerBook5,2 - A1046
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.25_15.html PowerBook G4 1.25 15" (FW800 - Al)], PowerBook5,2 - A1046
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.33_17.html PowerBook G4 1.33 17" (Al)], PowerBook5,3 - A1052
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.33_15.html PowerBook G4 1.33 15" (Al)], PowerBook5,4 - A1095
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.5_15.html PowerBook G4 1.5 15" (Al)], PowerBook5,4 - A1095
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.5_17.html PowerBook G4 1.5 17" (Al)], PowerBook5,5 - A1085
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.5_15_2.html PowerBook G4 1.5 15" (SMS/BT2 - Al)], PowerBook5,6 - A1106
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.67_15.html PowerBook G4 1.67 15" (Al)], PowerBook5,6 - A1106
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.67_17.html PowerBook G4 1.67 17" (Al)], PowerBook5,7 - A1107
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.67_15_hr.html PowerBook G4 1.67 15" (DLSD/HR - Al)], PowerBook5,8 - A1138
* [http://www.everymac.com/systems/apple/powerbook_g4/specs/powerbook_g4_1.67_17_hr.html PowerBook G4 1.67 17" (DLSD/HR - Al)], PowerBook5,9 - A1139

== iBook ==

Here is a list of supported iBook machines (in short: all G4 iBooks), with links to the great "everymac.com" site with loads of additional, detailed information on each and every one of these:

* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_800_12.html iBook G4/800 12-Inch (Original - Op)]
* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_933_14.html iBook G4/933 14-Inch (Original - Op)]
* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_1.0_14.html iBook G4/1.0 14-Inch (Original - Op)]
* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_1.0_12.html iBook G4/1.0 12-Inch (Early 2004 - Op)]
* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_1.0_14_2.html iBook G4/1.0 14-Inch (Early 2004 - Op)]
* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_1.2_14.html iBook G4/1.2 14-Inch (Early 2004 - Op)]
* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_1.2_12.html iBook G4/1.2 12-Inch (Late 2004 - Op)]
* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_1.33_14.html iBook G4/1.33 14-Inch (Late 2004 - Op)]
* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_1.33_12.html iBook G4/1.33 12-Inch (Mid-2005 - Op)]
* [http://www.everymac.com/systems/apple/ibook/specs/ibook_g4_1.42_14.html iBook G4/1.42 14-Inch (Mid-2005 - Op)]

== Power Macintosh G5 ==

NVIDIA cards are not supported by MorphOS and would need to be replaced with a suitable Radeon card instead. Special Mac versions of Radeon cards should be used.

DP = Dual Processors (MorphOS only supports using one CPU though)

Here is a list of supported Power Macintosh G5 machines, oldest models first, then ascending in performance:

* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_1.6.html Power Macintosh G5 1.6 (PCI)], PowerMac7,2, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_1.8.html Power Macintosh G5 1.8 (PCI-X)], PowerMac7,2, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_1.8_dp.html Power Macintosh G5 1.8 DP (PCI-X)], PowerMac7,2, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_1.8_dp_2.html Power Macintosh G5 1.8 DP (PCI)], PowerMac'''7,3''', NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_2.0_dp.html Power Macintosh G5 2.0 DP (PCI-X)], PowerMac7,2
* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_2.0_dp_2.html Power Macintosh G5 2.0 DP (PCI-X 2)], PowerMac7,3, NVIDIA card
* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_2.5_dp.html Power Macintosh G5 2.5 DP (PCI-X)], PowerMac7,3
* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_2.0_dp_pci.html Power Macintosh G5 2.0 DP (PCI)], PowerMac7,3
* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_2.3_dp.html Power Macintosh G5 2.3 DP (PCI-X)], PowerMac7,3
* [http://www.everymac.com/systems/apple/powermac_g5/specs/powermac_g5_2.7_dp.html Power Macintosh G5 2.7 DP (PCI-X)], PowerMac7,3
* [https://everymac.com/systems/apple/powermac_g5/specs/powermac_g5_dual_2.0.html Power Macintosh G5 2.0 Dual Core], PowerMac11,2, NVIDIA card, unofficially supported machine ([https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12716&forum=11 more info])
* [https://everymac.com/systems/apple/powermac_g5/specs/powermac_g5_dual_2.3.html Power Macintosh G5 2.3 Dual Core], PowerMac11,2, NVIDIA card, unofficially supported machine ([https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12716&forum=11 more info])
* [https://everymac.com/systems/apple/powermac_g5/specs/powermac_g5_quad_2.5.html Power Macintosh G5 2.5 Quad Core], PowerMac11,2, NVIDIA card, unofficially supported machine ([https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=12716&forum=11 more info])

== Power Macintosh G4 Cube ==

MorphOS runs on "the Cube", but some HW features are not supported. Network can be made working with some tweaks, but the USB audio presents a problem ([http://www.morphzone.org/modules/newbb_plus/viewtopic.php?forum=11&topic_id=6835&start=27 link]).

Here is a list of the Cube machines, with links to the great "everymac.com" site with loads of additional, detailed information:

* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_450_cube.html Power Macintosh G4 450 Cube], PowerMac5,1
* [http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_500_cube.html Power Macintosh G4 500 Cube], PowerMac5,1

== ACube Systems Hardware ==

MorphOS 3.8 added the support for Sam460cr and Sam460ex mainboards.

Official systems based on these are:

* [http://www.acube-systems.biz/index.php?page=hardware&pid=7 AmigaOne 500 (Old/Sam460ex)]
* [https://acube-systemsbiz.serversicuro.it/shop/en/14-case-systems AmigaOne 500 (New/Sam460cr)]

== A-EON Technology Hardware ==

MorphOS 3.10 added the support for AmigaOne X5000 mainboard.

* [http://www.a-eon.com/?page=x5000 AmigaOne X5000]

== iMac ==

Support for this particular iMac model (with the 20" display, the 17" one does not boot) was unofficially enabled in MorphOS 3.12.

* [https://everymac.com/systems/apple/imac/specs/imac_g5_2.1_20.html iMac G5/2.1 20-Inch (iSight)], PowerMac12,1, unofficially supported machine
* [https://everymac.com/systems/apple/imac/specs/imac_g5_1.9_17.html iMac G5 1.9 17-Inch (iSight)], PowerMac12,1, supported machine since 3.16

The Style Guide

2022-02-08T09:09:18Z

Polluks: Scripts

''Stefan Haubenthal''

== Short Cuts ==
Shift should invert an action.
* Navigate
** page down: Space
** page up: Shift Space

* Find: Amiga-F (should toggle, avoid Shift Esc)
** find next: Return
** find previous: Shift Return

* Settings: Amiga-, (or its own menu, avoid "S" or "P")

* Scripts: Amiga-.

The Style Guide

2022-02-08T09:07:30Z

Polluks: /* Short Cuts */ Settings

Shell Commands/Play

2021-12-18T22:36:05Z

Polluks:

'''Play''' - Plays audio files supported by the Reggae multimedia framework

FILE/A, VOLUME/N, AHIUNIT/N, LOOP/S, QUIET/S
<nowiki>
FILE - File to play
VOLUME - Audio volume
AHIUNIT - AHI unit to output
LOOP - Plays the file in loop
QUIET - Disables playing information displaying</nowiki>

Shell Commands/PlayMidi

2021-12-18T22:34:02Z

Polluks:

'''PlayMidi''' - CAMD Midi player

FILE/A, MIDICLUSTERNAME/A
<nowiki>
FILE - File to play
MIDICLUSTERNAME - CAMD cluster</nowiki>

The Style Guide

2021-11-28T18:38:56Z

Polluks: Navigate

Shell Commands/Ssh2FS

2021-09-11T21:07:54Z

Polluks: link

'''Ssh2FS''' - Mounts a SFTP share

REMOTE/A, VOLUME/A, AUTH/A, DCMAX/N, ACMAX/N, CTIME/N, VERBOSE/S, PORT/N, HOME/K, NTIME/N, ALIVE/N, MINBUF/N, RAHEAD/S, MAXBUFS/N, REMPASS/S, RECONN/S, DISCONN/N, NODEV/S
<nowiki>
REMOTE - [user@]host[:/dir]
VOLUME - VolumeName:
AUTH - pw | ia | pk | pkp
DCMAX - Maximum # of dirs to cache at one time. Default: 10.
ACMAX - Maximum # of attrs to cache at one time. Default: 64.
CTIME - Cache timeout for dirs and attrs (seconds). Default: 300.
VERBOSE - Print extra information
PORT - Use different port number. Default: 22.
HOME - Change where to look for .ssh/ directory. Default: $HOME.
NTIME - Network timeout in milli seconds. Default: 0 = no timeout.
ALIVE - Keep alive rate in seconds. Default: 10.
MINBUF - Minimum number of buffers (per open file). Default: ?.
BUFSIZE - Minimum size of io buffers. Default: 32768.
RAHEAD - Enable speculative read-ahead.
MAXBUFS - Maximum number of buffers (per open file). Default: 4.
REMPASS - Remember password for reconnects
RECONN - Reconnect on lost connection.
DISCONN - Disconnect?
NODEV - No not create a device node automatically.</nowiki>

Example:
Ssh2FS user@server UserHome: pw

See also: [[Shell_Commands/RunFS | RunFS]]

Shell Commands/RunFS

2021-09-11T21:07:10Z

Polluks: link

'''RunFS''' - Runs/mounts a network filesystem in background

PRI=PRIORITY/K/N, Q=QUIET/S, O=OPEN/S, A=ALIAS/K, WV=WAITVOLUME/K, INVOCATION/F
<nowiki>
PRIORITY - Priority of filesystem (default 0)
QUIET - Be quiet, don't output messages from filesystem in shell
OPEN - Automatically open Ambient window for the filesystem's volume
ALIAS - Start filesystem based on connection description file in "Sys:Prefs/Network Connections/", mutually exclusive with INVOCATION
INVOCATION - Rest of line, filesystem invocation (Ex: mydir/myfilesystem args...)
WAITVOLUME - Waits for a volume to become ready in doslist. This is mainly for non filesysbox filesystems. Give name of volume here, without ":"</nowiki>

Example:
RunFS OPEN ssh2fs user@bla.foo.bar Foo:

See also: [[Shell_Commands/Ssh2FS | Ssh2FS]]

The Style Guide

2021-06-06T16:42:08Z

Polluks: /* Short Cuts */

''Stefan Haubenthal''

== Short Cuts ==
* Find: Amiga-F (should toggle, avoid Shift Esc)
** next: Return
** previous: Shift Return

Text Class: Buttons, Textfields, Labels

2021-06-05T09:32:12Z

Polluks: /* Introduction */

''Grzegorz Kraszewski''
----
This article in other languages: [[Klasa "Text": przyciski, pola tekstowe, etykiety|Polish]]

==Introduction==
The ''Text'' class is the most commonly used one for creating gadgets. This is because it not only creates plain labels (also called "static text" in other GUI engines), but also framed read-only text gadgets and textual buttons. In fact MUI has no special class for buttons, a button is just a ''Text'' object with a proper frame and background and user input activated. This versatility can have the disadvantage of allowing for creation of [[The_Style_Guide|style guide]] nonconforming interfaces.

The ''Text'' class uses the [[MUI Text Rendering Engine]] for text output. It allows for multiline text, using styles (bold, italic), colors and inlined images. These features should be used sparingly to keep user interfaces consistent and comfortable to use. The rendering engine is controlled by inserting escape sequences in the text. Another engine feature is aligning the text inside the object rectangle (left, right, centered).

==Common Attributes==
*'''''MUIA_Background''''' and '''''MUIA_Frame''''' are attributes inherited from the ''Area'' class. They specify a background and frame used for an object.
*'''''MUIA_Text_Contents''''' specifies the text. It may contain formatting engine escape sequences. The text is buffered internally, so the value of this attribute may point to a local variable or a dynamically allocated buffer.
*'''''MUIA_Text_PreParse''''' may be considered a fixed prefix, which is always added at the start of text before rendering. It is usually used for applying constant styles and formatting, for example setting it to "\33c" will always center the text. This attribute simplifies text handling when the text displayed is not constant (for example is loaded from a locale catalog).
*'''''MUIA_Font''''' is another attribute inherited from the ''Area'' class and specifies a font to be used for text rendering. In most cases it is one of the fonts predefined by the user in MUI settings.

For more attributes and detailed descriptions refer to the ''Text'' class autodoc in the SDK.

==Labels==
Labels are the simplest form of ''Text'' instances. They have no frame and inherit their background from the parent object (neither ''MUIA_Frame'' nor ''MUIA_Background'' is specified). They use the standard MUI font in most cases, so ''MUIA_Font'' does not need to be specified either. An important (and often forgotten) detail is a proper text baseline align when a label is used with some framed gadget also containing text (a ''String'' gadget for example). The default MUI behaviour for vertical text positioning is to center it. If the framed gadget uses uneven vertical padding, baselines of the label and the gadget may be unaligned. A special attribute ''MUIA_FramePhantomHoriz'' solves this problem. It is specified for a label with a ''TRUE'' value. The label also has ''MUIA_Frame'' specified with the same frame type as the gadget. Then the label gets an invisible frame of this type (frame horizontal parts to be exact, hence the attribute name) and the text is laid out accordingly. As a result the label and the gadget text are always aligned vertically, assuming they use the same font.

[[File:Label_align.png|center]]

The magnified screenshot above illustrates the label align problem. The string gadget uses uneven padding (top padding is 2 pixels, bottom padding is 0 pixels), which causes the text baseline to misalign by 1 pixel shown on the left. The label on the right has been defined with two additional tags:

MUIA_FramePhantomHoriz, TRUE,
MUIA_Frame, MUIV_Frame_String,

A label can have one character underlined with the ''MUIA_Text_HiChar'' attribute. It is used to create a visual hint for a hotkey of a labeled gadget. See [[#Buttons|Buttons]] section below for details.

==Textfields==
A textfield is a read-only framed area showing some (usually changing at runtime) text. The difference between a label and a textfield is that the latter has a frame and a background specified:

MUIA_Frame, MUIV_Frame_Text,
MUIA_Background, MUII_TextBack,

==Buttons==
A text button is an instance of the ''Text'' class too. It has more attributes than a plain label however, because it handles user input. MUI has a predefined background and frame for buttons:

MUIA_Frame, MUIV_Frame_Button,
MUIA_Background, MUII_ButtonBack,

These attributes also specify a frame and background for the "pressed" state. MUI also has separate font settings for buttons. Forgetting the ''MUIA_Font'' attribute for buttons is one of most common errors in MUI design.

MUIA_Font, MUIV_Font_Button,

Many users (and programmers) just have the default font defined for buttons, so the bug is not visible. It is recommended to always test a GUI with some unusual font settings for buttons, so the problem is easily visible. Button text is usually centered, which may be done either by inserting the "\33c" sequence at the start of the button label, or using ''MUIA_Text_PreParse''.

MUIA_Text_PreParse, "\33c",

After definition of the button appearance it is time to handle user input. The button behaviour is defined by the ''MUIA_InputMode'' attribute with three values:
*'''''MUIV_InputMode_None''''' – The default value, button does not react on anything.
*'''''MUIV_InputMode_RelVerify''''' – A simple pushbutton activated by a left mouse button click.
*'''''MUIV_InputMode_Toggle''''' – A two-state button, one click switches it on, another one switches it off.

Another common bug with MUI buttons is to omit keyboard handling. The mouse is not everything. The first, obligatory step is to enter the button into the window's TAB key cycle chain:

MUIA_CycleChain, TRUE,

Any gadget entered into the chain may be selected by pressing the TAB key (for default MUI keyboard settings). The selected object has a special frame drawn around it. Then it may be activated by some key set in MUI preferences. For buttons the default "pressing" key is the return key. A rule of thumb for cycle chaining:

<big><center>'''Every''' gadget accepting user input '''must''' be added to the TAB cycle chain.</center></big>

Another keyboard handling feature provided by MUI is hotkeys. A hotkey just activates a button associated to it. Hotkeys have the following features:
*MUI provides a visual hint of a button hotkey by underlining the hotkey letter in the button label. It implies that the hotkey letter must exist in the label.
*There is visual feedback for using a hotkey, the button is pressed as if it has been clicked with the mouse.
Not every button in a GUI has to have a hotkey. The best practice is to assign hotkeys only for the most used buttons, especially if there are many buttons in a window. A hotkey is defined with two attributes:
*'''''MUIA_Text_HiChar''''' – this attribute specifies a letter to be underlined in the label. It is case insensitive.
*'''''MUIA_ControlChar''''' – this attribute specifies a hotkey. Of course it should be the same as the above one. It should be a lowercase letter, as uppercase forces a user to press SHIFT, making the hotkey less comfortable to use. There is also no visual hint for SHIFT requirement. Digits may be also used as hotkeys if the label contains them. Using punctuation and other characters should be avoided. An example of use:

MUIA_Text_Contents, "Destroy All",
MUIA_Text_HiChar, 'a',
MUIA_Text_ControlChar, 'a'

Note that these attributes take a single char, not a string.

The Style Guide

2021-06-05T09:26:17Z

Polluks: Created page with "''Stefan Haubenthal'' == Short Cuts == * Find: Amiga-F (should toggle) ** next: Return ** previous: Shift Return"

''Stefan Haubenthal''

== Short Cuts ==
* Find: Amiga-F (should toggle)
** next: Return
** previous: Shift Return

Magic User Interface Programming

2021-06-05T09:21:55Z

Polluks: /* The First Steps */

''Grzegorz Kraszewski''
----
This article in other languages: [[Programowanie w MUI|Polish]]

==Introduction==
Magic User Interface (MUI for short) is the MorphOS toolkit for creating applications with a graphical user interface. It provides a broad set of gadgets (controls) as well as a complete framework for designing event driven programs. MUI is object oriented, but does not rely on any specific programming language. A BOOPSI (''Basic Object Oriented System for Intuition'') is used as the foundation of MUI object oriented design.

MUI offers a dynamic layout as its basic mode of operation. The placement of gadgets is determined by grouping them in horizontal, vertical or matrix groups. Pixel coordinates of gadgets adapt dynamically to user preferences like font sizes, spacing between gadgets, objects' frames and backgrounds. The two screenshots below show '''the same''' example application. The only difference is that user MUI settings are different.

[[File:digiroller1.png|center]]

The first settings are plain and clean. They may even be called a bit oldschool for using simple, vector frames and uniform color backgrounds. A simple window skin, named ''Mahalaxmi'' fits this design nicely.

[[File:digiroller2.png|center]]

The second example uses some MUI 4 features, like bitmap frames with transparency masks. This dark design is achieved by using the ''Nox'' window skin. All gadget position calculations are done automatically, accounting for a larger font and fancy frames. The programmer need not care about user taste and preferences (a good programmer would test the program appearance with a few different settings however).

==The First Steps==
* [[Short BOOPSI Overview]]
* [[Event Driven Programming, Notifications]]
* [["Hello world!" in MUI]]
* [[The Style Guide]]

==Subclassing==
* [[General Rules and Purpose of Subclassing]]
* Overriding General Methods
** [[Overriding Constructors]]
** [[Overriding Destructors]]
** [[Overriding OM_SET()]]
** [[Overriding OM_GET()]]
* [[Subclassing Application Class]]
* [[Subclassing List Class]]
* [[Subclassing Numeric Class and its Subclasses]]
* [[Subclassing Area Class]]
* [[MUI Subclassing Tutorial: SciMark2 Port]]

==Useful Techniques==
* [[Locating Objects in the Object Tree]]
* [[Text Class: Buttons, Textfields, Labels]]
* [[MUI Text Rendering Engine]]

Multi-display

2020-12-16T08:57:44Z

Polluks: /* Basics */ blankers

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

WirelessManager

2020-11-23T01:16:57Z

Polluks: disconnect

Interface of MOSSYS:Net/WirelessManager
* DEVICE/K for example atheros5000.device or prism2.device
* UNIT/K/N
* CONFIG/K
* VERBOSE/S

<code>rxcmd WLANMNGR.1 "reassociate"</code>

<code>rxcmd WLANMNGR.1 "disconnect"</code>

WirelessManager

2020-11-21T22:46:14Z

Polluks: Created page with "Interface of MOSSYS:Net/WirelessManager * DEVICE/K for example atheros5000.device * UNIT/K/N * CONFIG/K * VERBOSE/S <code>rxcmd WLANMNGR.1 "reassociate"</code>"

Interface of MOSSYS:Net/WirelessManager
* DEVICE/K for example atheros5000.device
* UNIT/K/N
* CONFIG/K
* VERBOSE/S

<code>rxcmd WLANMNGR.1 "reassociate"</code>

How to translate program with SimpleCat

2020-10-14T11:39:42Z

Polluks: just a hint

''Hint: SimpleCat does not support the negative stringNum of ObjC catalogs.''

Passwordless SSH login with RemoteShell

2020-08-24T10:48:18Z

Polluks: markup

There are lots of tutorials about this for linux, but not much for MorphOS, even if the process is mostly the same. So when I started doing this, I decided to write down all steps, in case someone else needs to do it in the future. I assume you already have a suitable unix / linux system properly configured. If not, google for some linux tutorial.

While "passwordless login" might sound terribly insecure, it's actually often more secure than traditional passworded login. Oversimplified, you "create a really secure & random password, which you upload to the server". In practice, this is of course quite a bit more complex (and more secure). Of course this can be combined with a password for even more protection.

Also note that MorphOS SDK comes with own SSH, SCP etc. which have their own config file. These instructions are for RemoteShell. Commands in SDK have their own config files, to which you can do the same changes.

Step 1: Set hostname
You might want to set your hostname in Settings => Network => Host and DNS

Step 2: Create public & private key pair

<code>SYS:Applications/RemoteShell/Files/ssh-keygen -t rsa</code>

When asked for password, just press enter for none.
Enter same password again.

Step 3: Get the public key to server
Doesn't matter how you do it. With USB massstorage device:

<code>copy sys:Applications/RemoteShell/Files/conf/id_rsa.pub UMSD0:</code>

Move the USB device to the server.

Step 4: Add key to authorized keys 
Mount the USB disk (if not done automatically) 
Append the key to your list of authorized keys:

<code>cat /media/disk/id_rsa.pub >> ~/.ssh/authorized_keys</code>

NOTE: Use the path where the disk is mounted.

Step 5: RemoteShell configuration 
Preferences => Servers => Add 
Alias: Whatever you like 
Server: Address of the server 
Login: User name (on the server) 
Password: Empty (unless you use one) 
Port: Whatever the server is using.

When connecting to the server for the first time, RemoteShell asks if you want to continue connecting (as the host isn't yet marked as known). After answering yes, the connection will be done automatically.

Tips and Tricks

2020-04-12T15:25:52Z

Polluks: /* Copying a CD/DVD to an ISO Image */ typo

''Originally published at: http://jpv.wmhost.com/morphos/tips/''

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.
== Basic Features ==

=== Modifying the System Directory ===
: 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.

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

=== Keyboard Commands ===

: At first, check the default ones and define your favourites in '''System Settings -> IControl -> Hotkeys''' and in '''Ambient Settings -> Keyboard'''.

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

: Other keys:
:* To zoom Ambient icons in icon mode: keep CTRL pressed and use the mouse wheel.
:* To find and select files in Ambient windows by letter: start typing the wanted name when the window is active. Keep shift-key pressed for directories.
:* To enter a path manually (for example for hidden dirs like .recycled): press the / key in an Ambient window and type in the path.
:* Command-f activates the find function in most programs.
:* The r-key rotates the pictures in Ambient's internal viewer and page up/down keys select previous and next images in a dir
:* Check the keyboard commands of the shell, like by default, commands can be completed with CTRL-tab, devices with ALT-tab, history with shift-tab etc.
:* Keeping the alt-key pressed while double clicking drawer gives you different ways to open drawers.

=== Enabling/Disabling Icon Tooltypes ===

: Double click single tooltypes to enable and disable them in the icon information window.

=== Browsing History in Ambient ===

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

=== Sync the Clock from Internet at Boot ===

: Add this line to S:user-network-startup file:
: <tt>Run DETACH MOSSYS:C/SetClockNTP SAVE</tt>

=== Redirecting AHI Music Unit ===

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

=== Keeping AHI Audio Quality Better ===

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

=== Mime Type Configuration ===

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

=== Inline Editing ===

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

: File comments can also be edited with the inline editing.

: [[File:Tips_Inlineedit.png|280px]]

=== Batch Renaming in Ambient ===

# Select files you want to be in the range of renaming.
# Hit rename button or command-r keyboard shortcut.
# 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).

=== Don't Forget RMB/Long-LMB Gadget Menus ===

: You get menus from zoom and depth gadgets with right mouse button or by holding left mouse button pressed on them.

: [[File:Tips_Zoommenu.png]] [[File:Tips_Windowdepthmenu.png]] [[File:Tips_Screendepthmenu.png]]

=== How to Use RMB with One-button Mouse ===

: The right mouse button can be emulated in several different ways:
:* 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.
:* 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.
:* 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.
:* 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.
:* A multi button USB mouse works always!

=== Starting Programs Iconified ===

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

: [[File:Tips_Iconify.png]]

=== Checking the Debug Log ===

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

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

: [[File:Tips_Debug1.png|x64px]] [[File:Tips_Debug2.png|x64px]]

=== Printing to a PostScript Compatible Network Printer ===

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

: "Mount NETPAR:" can be added to S:user-startup, for example.

=== .recycled Directory ===

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

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

: You shouldn't modify any files in it, but you can recover deleted files by copying them to some other path.

: The PFS3 filesystem has a similar directory, but its name is ".deldir".

=== How to Reduce Graphics Memory Usage ===

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

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

: To reduce its memory usage, you may:
:* 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.
:* 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.

: Other ways to reduce graphics memory usage:
:* Lower the color depth of screens from the Screens settings. 16-bit might be enough sometimes.
:* Don't use too many separate screens at the same time.

=== How to Open MUI Programs on Their Own Screens ===

: 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.
: [[FIle:MorphOS3_jPV_Newscreen.png|120px]]

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

: 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).
: [[File:Tips_Screendepthmenu.png]]

== Advanced Features ==

=== Default Device Icons ===

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

: For example the deficon for SMBFS devices would be called def_SMBFSxdisk.info.

=== Default Icon for Ambient Windows ===

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

=== Old Style Preferences Icons ===

[[File:Separate_prefs_in_MorphOS.png|thumb|Example of separate system prefs in MorphOS]]
: 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".

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

=== Hilight Options in Listers ===

: 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.
: Type in shell:
: <tt>Setenv MUI/fastppa SAVE 1</tt>

=== Copy Selected Filenames ===

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

: User may find it very useful to paste around the names selected in the Ambient windows in many situations.

=== Using ARexx Ports from Lua ===

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

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

:* ipc.address(port) - sets the default ARexx port. Port "COMMAND" executes commands as DOS shell commands.
:* ipc.checkport(port) - checks if ARexx port is available.
:* ipc.rx(command) - sends command to a port set with ipc.address. It returns ARexx RESULT.
:* ipc.waitforport(name[, interval]) - Waits for a ARexx port. Script is aborted if the port isn't found.

: Few examples can be found from [http://jpv.wmhost.com/morphos/ here].

=== Copying a Whole Disk As an Image File ===

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

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

: 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):
: <tt>Copy DIRECT RAWDISK:Devices/usbscsi.device/3/rawdisk work:sdcard.img</tt>

: And to copy the image back to the SD card (removes all existing data, be careful!):
: <tt>Copy DIRECT work:sdcard.img RAWDISK:Devices/usbscsi.device/3/rawdisk</tt>

: This works with all raw disk image files like Raspberry Pi's OS distributions etc.

: Single partitions can also be copied from the RAWDISK:Disks directory.

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

=== Using WLAN with Hidden SSID ===

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

: Contents should look something like this:

: <tt>network={
:   ssid="ThatHiddenSSID"
:   scan_ssid=1
:   psk="password"
: }</tt>

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

=== Modifying Screen and Keyboard Brightness on a Laptop without Using KB Shortcuts ===

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

=== Opening Ambient Windows from the Shell or Scripts ===

: Directories can be opened with the [[Shell_Commands/Open|Open]] command, but it only opens them in the default view mode:
: <tt>Open SYS:Applications</tt>

: 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:
:* 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''.
:* NEW=NEWWIN/S: opens a new window even if similar window would already be opened
:* RELOAD/S: reloads the URI
:* FORCE/S: forces full reloading
:* BROWSER/N: forces the browser mode on (1) or off (0)
:* VIEWID/N: specifies view/window ID

: Use the ''AMBIENT'' port in ARexx scripts.

: 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:
: <tt>'LoadURI "file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600" NEW'</tt>

: 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:
: <tt>'LoadURI "file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400" BROWSER=0'</tt>

: 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):
: <tt>RXCmd AMBIENT "LoadURI *"file://SYS:Libs?view=list&mode=all&top=50&left=350&width=440&height=600*" NEW"
: RXCmd AMBIENT "LoadURI *"file://MOSSYS:Prefs/Wallpapers/1280x1024?view=icon&mode=thumbs&top=50&left=350&width=500&height=400*" BROWSER=0"</tt>

== Bundled Software ==

=== Flacapella Settings for MP3 Encoding ===

: Example of a custom encoder setting in Flacapella:

: <tt>Compress Command: c:lame -V0 --tt "{title}" --ta "{artist}" --tl "{album}" --tn {track} {?coverfile:--ti "{coverfile}"} {input} {output}
: File Extension: mp3</tt>

: 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.
: Example assumes you have [http://morphos-files.net/find.php?find=lame LAME] installed in C:

=== Jukebox Tips ===

:* 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.
:* You can adjust volume in Jukebox by using mouse wheel over its screenbar module.
:* Displayed columns can be configured on the fly by right clicking the column title.
:* Jukebox can be better integrated into Ambient and its contextual menus with the [http://aminet.net/package/mus/play/JukeboxAdder JukeboxAdder] script.
:* Two new tooltypes were presented in MorphOS 3.8:
:** '''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.
:** '''STREAMBUFFER=YES''' activates the Reggae streambuffer class which reduces stuttering, but causes lag on track change and seeking.

=== How to Reduce OWB's HD Writes ===

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

:* 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.
:* Disable the Website Icons feature. Open the Interface settings and uncheck all Website Icons checkmarks.
:* Disable all saving options from the Privacy settings.

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

=== Alternative YouTube Script for OWB ===

: [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.

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

=== Watching Videos with Less CPU Load in OWB ===

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

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

=== Problems with YouTube Videos ===

:* 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. [[File:OWB_ContentBlockingYT.png]]

:* 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.

:* 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:
:** Remove the file from use if you don't need flash anywhere. The plugin doesn't work too well generally anyway.
:** 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.
:** Disable it temporarily from "Settings->Plugins->Disable", and reload the page.
:** 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.

=== OWB Doesn't Work or Stopped Working with Certain Web Pages ===

:* 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.

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

=== Creating an ISO Image ===

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

: An option to create an ISO image is found on the pulldown menu in the Burn Files section.

: [[File:Tips_Create_ISO.png|200px]]

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

=== Copying a CD/DVD to an ISO Image ===

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

: Do these steps from the shell to read a CD/DVD into a standard ISO image:
:# Find your CD drive device by typing: MOSSYS:Data/Jalapeno/readcd -scanbus
:# 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

=== Disabling the Default UTF-8 Mode with Scribble ===

: 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.
: [[File:Scribble_ascii1.png|128px]]

: 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).
: [[File:Scribble_ascii2.png|205px]]

== 3rd Party Software ==

=== Where to Get Software? ===
:* Check [http://library.morph.zone/Links#File_Repositories file repositories] for manual installing
:* [http://www.geit.de/eng_grunch.html Grunch] is a good packet manager for automatic installation and updating of selected software
:* [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])

=== Custom Ambient Menus with AREXX ===

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

=== Help with Shell Commands ===

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

=== Utilizing Your Keyboard's Multimedia Keys ===

:* 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.
:* The [http://aminet.net/package/mus/play/MultiMeedio MultiMeedio] script provides a unified control for all popular media players.

== Hardware Related ==

=== Removing Startup Sound on Macs ===

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

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

=== Speeding Up the Startup Manager on Macs ===

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

=== Booting MorphOS ISO from USB Stick ===

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

: If you have only one mass storage device connected, you can just boot into Open Firmware prompt (command-alt-o-f) and type:

: <tt>boot ud:,\boot.img bi umsd0:morphos.iso</tt>

: (Remember to have both boot.img and morphos.iso on the stick)

=== Keyboard Reboot on ADB Laptops ===

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

=== Blackouts or Graphical Flickering on Mac mini ===

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

: One option to get around it is to use a VGA adapter/cable, because it doesn't seem to happen with it.

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

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

=== Disabling the Internal Touchpad on Laptops ===
==== From the Touchpad Settings (Preferred)====
: 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.

: [[File:MorphOS_Preferences_disabling_touchpad.png|200px]]

==== From the USB Settings ====
: 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.

: To remove the binding, open the USB settings from the MorphOS Preferences application and go to the Devices list.
:* If you have "Apple Internal Trackpad" alone in the list, you can just select it and click the Unbind button.
:: [[File:Disabling touchpad ibook.png|200px]]
:* 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.
:: [[File:Disabling touchpad powerbook.png|200px]]

==== Removing the Driver at Boot Time ====
: 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.

: 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!'''

: 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!'''

=== MorphOS Boot Arguments on U-boot Systems ===
: 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).

: On the U-boot systems the boot arguments have to be set in the '''morphosargs''' environment variable in the U-boot console.

: To check if you already have the variable set:
: <tt>printenv morphosargs</tt>

: 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):
: <tt>setenv morphosargs mf=symbios.device</tt>
: <tt>saveenv</tt>

: To edit an existing variable:
: <tt>editenv morphosargs</tt>
: <tt>saveenv</tt>

User:Polluks

2019-12-28T03:34:42Z

Polluks: Some uploads

[https://www.google.com/search?q=polluks%2Baminet%40sdf.lonestar.org Some uploads]

Shell Commands/Ssh2FS

2019-12-28T03:11:32Z

Polluks: 3.12 update

How to write Mails with SimpleMail

2019-11-19T21:41:11Z

Polluks: typo

'''Download:'''
---------------
The homepage is:
http://simplemail.sourceforge.net

'''Installing'''
---------------
Just unarchive the previously downloaded archive and place it wherever you want.

'''Setup'''
---------------
[[File:SM Main.png|200px|thumb|left|Main window]]
Start the program.
Open the configuration via the rightmost button in the mainmenu.
Or open it via the contextmenu. Rightclick within the mainwindow and go to settings.

[[File:SM Conf.png|200px|thumb|left|Configuration]]
You can setup multiple mailaccounts in the 2nd entry.

[[File:SM Conf Account.png|200px|thumb|center|Account]]

In the screenshot you will notice white areas, there you have to enter your respective values.
Please note that servers subdomain is mostoften called "pop3" or "mail".
However each mailprovider is free to use its own value.
You need to find out the value in the FAQ of your mailprovider.

'''Systemsettings'''
---------------
[[File:OpenURL.png|200px|thumb|left|OpenURL]]
With included OpenURL each application can support preparing and sending mails systemwide.
See the screenshot on how to setup SimpleMail and change the path to your local settings.

'''First steps'''
---------------
Now that you have setup the Mailclient it seems to be a good idea to try out some of the functions.

Setting up the addressbook to your needs.
Fill in your contacts or import them with the filemenu.

You can send/receive a set of existing mails via button in the main window.

For creating mails please stick to some simple rules that can be found here:
[http://learn.to/quote/ link How to quote]
[http://esl.about.com/od/businessenglishwriting/a/bizdocs_3.htm link Writing a mail]

Shell Commands/Debug

2019-09-23T09:44:44Z

Polluks: word wrap

'''Debug''' - Sets debug options

LOG/K,LOGFILE/K,LOGKPRINTF/K,EXT=EXTENDEDLOG/K,MT=MEMTRACK/K,PMT=PERMMEMTRACK/K,
IZP=INVZEROPAGE/K,INIT/K,CYBERGUARD/K,CGX=CYBERGRAPHICS/K,LOADSEG/K,UNLOADSEG/K,
PPCSTART/K,INITRESIDENT/K,INITCODE/K,FINDRESIDENT/K,CREATELIBRARY/K,SETFUNCTION/K,
NEWSETFUNCTION/K,CHIPRAM/K,ADDTASK/K,REMTASK/K,GETTASKATTR/K,SETTASKATTR/K,
EXCEPTHANDLER/K,ADDDOSNODE/K,PCI/K,RAMLIB/K,NOLOGSERVER/K,NOLOGWINDOW/K,QUIET/S

The command shows the state of all debug options if ran without arguments.