AmigaOS Documentation Wiki - User contributions [en]

UserDoc:Main

2014-11-03T21:16:36Z

Daniel Hutchinson: /* How does AmigaOS work? - Concepts */

== Welcome to AmigaOS ==

AmigaOS was born in 1985 and delivered what contemporary personal computer operating systems could only dream of. As the first "multimedia" operating system, it was trivial for AmigaOS computers to display animations while playing music and reading data from disks. Such multimedia and multitasking finesse drew many people to this system. Some of them are famous: [http://www.amigahistory.co.uk/warhol.html Andy Warhol], Sir Arthur C. Clarke, [http://www.polyphoto.com/upchug/AEcastro.html NASA], Hollywood and the TV broadcasting industry, and many others that thought [http://www.youtube.com/watch?v=PWeO5IkCssk only Amiga makes it possible].

Today many people still think AmigaOS has something special that makes it more interesting and rewarding than other systems. This system allows the user to control the computer, not the other way around. It is a system you fully understand that is easier and more flexible to use. In other words, AmigaOS is '''more fun'''.

=== AmigaOS: The flexible operating system ===
AmigaOS is an operating system: a collection of efficient programs written to start the computer, let the user control the computer, and present feedback to the user.

AmigaOS is designed with ease of use and flexibility in mind. To begin with, AmigaOS provides a clear view of your computer, your applications and files. A number of methods are available to let your computer serve you, whether graphically with a mouse, using the "Shell" command line, or by some other means the user prefers.

AmigaOS strives to avoid stupid limitations that can be found on other systems. AmigaOS users can organise their files the way they like. There are few limits on file hierarchy, locations and file names. Drives don't have to be named with a letter or cryptic names (such as C:, or sda1), your files don't have to reside in your "Documents" folder and your hard drives aren't hidden from you. If you're not writing to drives and you want to "shut down", why wait for the OS to allow that? With AmigaOS, just hit the power switch. Done.

An Amiga does not start with pre-installed applications serving some sales conglomerate, marketing organization or their big brother. AmigaOS does not do actions behind the user's back. As unique as it is today, the AmigaOS computer serves the user and not the other way around. With one of the largest proportions of user-programmers around, the trustworthy AmigaOS user-friendly ethic is mirrored in AmigaOS applications.

Since the first versions more than twenty-five years ago, AmigaOS has also been designed to serve efficiently. Optimizing applications and OS code has always been the goal of programmers and developers of this operating system. The result is an operating system and applications that take less space on your hard drives, waste less time loading, consume less memory, require less processing power, and respond more quickly to the user.

And every update of AmigaOS doesn't demand you must buy newer, more powerful hardware. AmigaOS currently runs on twenty year old 200MHz computers or brand new dual core 1,800MHz computers. It's the user's choice how they want to '''enjoy''' AmigaOS.

=== Some AmigaOS features ===
Here are some of the features of AmigaOS that make it easy to control your computer. Some of these concepts were copied by other operating systems which tend to show they are the correct way of doing things.

* '''Small footprint:''' AmigaOS can work with 64 MB of memory. On disk, a default installation only takes around 200 MB. The smaller footprint translates into a more responsive user experience given any hardware.

* '''Straightforward operating system design:''' With a clear layout and easy to understand names (Classes, Libs, Fonts, Prefs, Storage, etc.), you can easily understand what everything in AmigaOS is and what it does for you. Nothing is hidden from the user and the user is not restricted by AmigaOS.

*'''User configurable graphic interface:''' Using the provided "preferences editors," the user can dramatically reconfigure how AmigaOS looks, sounds, runs and responds to every user whim.

* '''File recognition based on file content:''' You can name a file '''whatever you want''', even without an extension. Examples: "my file" or "picture of Jay in Santa Clara". There is no need to add an extension to explain what the file is, like ".txt" or ".jpg". AmigaOS really examines the '''file content''' to recognise what type of file it is.

* '''Logical assignments:''' Easily set and use logical names names for directories located anywhere on your system. For example, "Auto:" can point to your directory "car show pictures" buried on your media drive.

* '''Ram disk concept:''' On AmigaOS there is a special disk called the '''Ram disk''' which represents a part of your computer memory. This area is not fixed. It automatically grows whenever you store files in it. For example, it's a great place to unpack files to install from there, greatly speeding up the installation.

* '''Command line and graphical user interfaces:''' Both the the graphical user interface (GUI) and command line interface (where you type commands into a window with the keyboard) can be used to manage AmigaOS, its programs and files. Both interfaces are intergated with each other so you can easily use command lines from the GUI or open graphical elements from a command line.

*'''ARexx Ports:''' Throughout AmigaOS and third party programs, "ARexx" message ports let one application talk with others so that apps work together to serve the user. AmigaOS also provides the lightweight ARexx and modern Python programming languages that can control AmigaOS and applications with ARexx ports.

* '''Resident Commands:''' Commands can be made resident, i.e., they are kept in memory so that they can be reused with no loading time.

* '''Restart only the operating system:''' if you feel the need to restart the system, you can do so by restarting '''only AmigaOS''' and not the whole computer.

=== AmigaOS platform targets ===

While the original versions of AmigaOS ran on computers of the eighties using Motorola 68k series CPU chips, the current AmigaOS runs on computers using PowerPC processor chips [http://www.amigaos.net/content/72/supported-hardware hardware]. These can be older Amiga computers (also called "Classic Amigas") with PPC "accelerator cards" or new generation Amiga PPC computers.

In this guide, we will concentrate on the current AmigaOS running on the supported hardware:

* [[AmigaOne X1000]] model by [http://www.a-eon.com A-Eon Technology]

* [[AmigaOne 500]], Sam460, Sam440ep and Sam440-flex models by [http://www.acube-systems.com ACube Systems]

* [[Pegasos II]] model by [http://www.bplan-gmbh.de bplan GmbH]

* AmigaOne XE and micro-A1 models by [http://en.wikipedia.org/wiki/Eyetech Eyetech Group Ltd].

* Amiga 4000(T), 3000(T) and 1200 models by Commodore Business Machines (when equipped with PowerPC accelerator cards).

== How does AmigaOS work? - Concepts ==

In this page we will discuss [[UserDoc:How AmigaOS Works|how AmigaOS works]]:

* [[UserDoc:How_AmigaOS_Works#The_most_important_components|The most important components]] (Exec, AmigaDOS, Intuition...)
* [[UserDoc:How_AmigaOS_Works#How_is_my_data_stored.3F|how files and data are stored]]
* [[UserDoc:How_AmigaOS_Works#All_AmigaOS_components|all AmigaOS components are described]]
* [[UserDoc:How_AmigaOS_Works#AmigaOS_boot_procedure|how AmigaOS is booted on your Amiga computer]]
* [[Workbench/Prefs|AmigaOS settings programs]]
* ...

== How to use AmigaOS? ==

AmigaOS is a collection of components that oversee the computer hardware & data and provide the user with easy, understandable tools to manage and use them.

In the following [[UserDoc:Introduction to AmigaOS|Introduction to AmigaOS pages]] we will discuss the basic concepts:

* how to use AmigaOS
* what the AmigaOS graphic user interface is composed of
* what interfaces AmigaOS provides, including the [[UserDoc:Workbench|Workbench]], the [[UserDoc:Shell|Shell]] or scripting languages.

From the introduction page, you can continue with more detailed pages on the [[UserDoc:Workbench|Workbench]] and the [[AmigaDOS manual]] . Now let's start with this [[UserDoc:Introduction to AmigaOS|Introduction to AmigaOS]].

== Manuals ==

[[UserDoc:AmigaOS File Systems|AmigaOS File Systems]] - AmigaOS File Systems

[[AmigaOS Manual]] - AmigaOS Manual

[[Bars & Pipes Professional]] - MIDI Sequencer

Workbench/Prefs/Pointer

2014-11-03T21:14:09Z

Daniel Hutchinson: Created page with "The Workbench's mouse pointer image can be edited using Pointer Prefs."

The Workbench's mouse pointer image can be edited using Pointer Prefs.

Workbench/Prefs

2014-11-03T21:12:14Z

Daniel Hutchinson:

[[File:Preferences.png|frame|center|A typical Prefs drawer]]

[[Workbench/Prefs/AHI|AHI]] (Audio Hardware Interface) - Allows for control over the audio functions of your Amiga

[[Workbench/Prefs/AmigaInput|AmigaInput]] - Setup for gamepads and joysticks

[[Workbench/Prefs/ASL|ASL]] - Allows for control over file requesters

[[Workbench/Prefs/Compatibility|Compatibility]] - Manages the 68K Just-in-time compiler settings

[[Workbench/Prefs/Console|Console]] - Controls the settings for the Amiga Shell

[[Workbench/Prefs/DefIcons|DefIcons]] - Interface to allow behaviour of default icons

[[Workbench/Prefs/DOS|DOS]] - Manages DOS settings

[[Workbench/Prefs/Font|Font]] - Controls Font selection for Workbench, Screens, and Windows

[[Workbench/Prefs/GUI|GUI]] - Used to control the look and feel of various elements of the AmigaOS 4 interface

[[Workbench/Prefs/Input|Input]] - Controls the settings for the keyboard and mouse

[[Workbench/Prefs/Internet|Internet]] - Contains settings for the computer's network connections

[[Workbench/Prefs/Locale|Locale]] - Sets the user's preferred languages

[[Workbench/Prefs/Notifications|Notifications]] - Controls the behaviour of Ringhio, the AmigaOS 4.1 pop-up notification system

[[Workbench/Prefs/Palette|Palette]] - Allows the user to adjust certain colours used for some on-screen elements

[[Workbench/Prefs/Picasso96Mode|Picasso96Mode]] - Advanced controls for creating and modifying graphics modes

[[Workbench/Prefs/Pointer|Pointer]] - Allows editing of the mouse pointer's image

[[Workbench/Prefs/PopUpMenu|PopupMenu]] - Settings controlling the look and behaviour of the system's pop-up menus

[[Workbench/Prefs/Printer|Printer]] -

[[Workbench/Prefs/PrinterGfx|PrinterGfx]] -

[[Workbench/Prefs/PrinterPS|PrinterPS]] -

[[Workbench/Prefs/ScreenBlanker|ScreenBlanker]] - Preferences for the system's screen saver / screen blanker

[[Workbench/Prefs/ScreenMode|ScreenMode]] - Settings for screen resolution and colour depth

[[Workbench/Prefs/Screens|Screens]] - Allows the setting up and control of custom screens for applications

[[Workbench/Prefs/Serial|Serial]] - Sets the default settings for the serial port

[[Workbench/Prefs/Time|Time]] - Allows the user to set the system's time and date

[[Workbench/Prefs/Timezone|Timezone]] - Allows the user to set their current timezone and Daylight Saving Time preferences

[[Workbench/Prefs/UBoot|UBoot]] - Advanced settings concerning the computer's initial booting system

[[Workbench/Prefs/USB|USB]] - Contains USB preferences and information

[[Workbench/Prefs/WBPattern|WBPattern]] - Settings for the background of the Workbench screen and directory windows

[[Workbench/Prefs/WBStartup|WBStartup]] - Controls which programs are launched when Workbench starts

[[Workbench/Prefs/Workbench|Workbench]] - Settings which control certain aspects of the Workbench's behaviour

Workbench/Prefs

2014-11-03T21:09:46Z

Daniel Hutchinson:

[[File:Preferences.jpg|frame|center|The Preferences Drawer]]

[[Workbench/Prefs/AHI|AHI]] (Audio Hardware Interface) - Allows for control over the audio functions of your Amiga

[[Workbench/Prefs/AmigaInput|AmigaInput]] - Setup for gamepads and joysticks

[[Workbench/Prefs/ASL|ASL]] - Allows for control over file requesters

[[Workbench/Prefs/Compatibility|Compatibility]] - Manages the 68K Just-in-time compiler settings

[[Workbench/Prefs/Console|Console]] - Controls the settings for the Amiga Shell

[[Workbench/Prefs/DefIcons|DefIcons]] - Interface to allow behaviour of default icons

[[Workbench/Prefs/DOS|DOS]] - Manages DOS settings

[[Workbench/Prefs/Font|Font]] - Controls Font selection for Workbench, Screens, and Windows

[[Workbench/Prefs/GUI|GUI]] - Used to control the look and feel of various elements of the AmigaOS 4 interface

[[Workbench/Prefs/Input|Input]] - Controls the settings for the keyboard and mouse

[[Workbench/Prefs/Internet|Internet]] - Contains settings for the computer's network connections

[[Workbench/Prefs/Locale|Locale]] - Sets the user's preferred languages

[[Workbench/Prefs/Notifications|Notifications]] - Controls the behaviour of Ringhio, the AmigaOS 4.1 pop-up notification system

[[Workbench/Prefs/Palette|Palette]] - Allows the user to adjust certain colours used for some on-screen elements

[[Workbench/Prefs/Picasso96Mode|Picasso96Mode]] - Advanced controls for creating and modifying graphics modes

[[Workbench/Prefs/Pointer|Pointer]] - Allows editing of the mouse pointer's image

[[Workbench/Prefs/PopUpMenu|PopupMenu]] - Settings controlling the look and behaviour of the system's pop-up menus

[[Workbench/Prefs/Printer|Printer]] -

[[Workbench/Prefs/PrinterGfx|PrinterGfx]] -

[[Workbench/Prefs/PrinterPS|PrinterPS]] -

[[Workbench/Prefs/ScreenBlanker|ScreenBlanker]] - Preferences for the system's screen saver / screen blanker

[[Workbench/Prefs/ScreenMode|ScreenMode]] - Settings for screen resolution and colour depth

[[Workbench/Prefs/Screens|Screens]] - Allows the setting up and control of custom screens for applications

[[Workbench/Prefs/Serial|Serial]] - Sets the default settings for the serial port

[[Workbench/Prefs/Time|Time]] - Allows the user to set the system's time and date

[[Workbench/Prefs/Timezone|Timezone]] - Allows the user to set their current timezone and Daylight Saving Time preferences

[[Workbench/Prefs/UBoot|UBoot]] - Advanced settings concerning the computer's initial booting system

[[Workbench/Prefs/USB|USB]] - Contains USB preferences and information

[[Workbench/Prefs/WBPattern|WBPattern]] - Settings for the background of the Workbench screen and directory windows

[[Workbench/Prefs/WBStartup|WBStartup]] - Controls which programs are launched when Workbench starts

[[Workbench/Prefs/Workbench|Workbench]] - Settings which control certain aspects of the Workbench's behaviour

Workbench/Prefs/Input

2014-11-03T21:08:14Z

Daniel Hutchinson: Created page with "Input is used to adjust the mouse speed, double click delay and to select the appropriate keyboard type."

Input is used to adjust the mouse speed, double click delay and to select the appropriate keyboard type.

Workbench/Prefs/Font

2014-11-03T21:07:09Z

Daniel Hutchinson: Created page with "Font is a preferences program used to change the font style, size and colour used on the Workbench."

Font is a preferences program used to change the font style, size and colour used on the Workbench.

Workbench/Prefs/ASL

2014-11-03T21:05:44Z

Daniel Hutchinson: Created page with "ASL provides file requesters in AmigaOS, these can be customised to a certain extent in ASL Prefs."

ASL provides file requesters in AmigaOS, these can be customised to a certain extent in ASL Prefs.

Workbench/Prefs/AmigaInput

2014-11-03T21:04:51Z

Daniel Hutchinson: Created page with "AmigaInput is a preferences program for managing input devices, such as mice and joysticks, connected to the Amiga. Using AmigaInput it is possible to calibrate USB joysticks ..."

AmigaInput is a preferences program for managing input devices, such as mice and joysticks, connected to the Amiga. Using AmigaInput it is possible to calibrate USB joysticks and other input devices.

Workbench/Prefs/AHI

2014-11-03T21:03:48Z

Daniel Hutchinson: Created page with "AHI is the AmigaOS audio subsystem. It was designed to be flexible, hardware independent, expandable and future proof. AHI allows multiple applications to share the audio hard..."

AHI is the AmigaOS audio subsystem. It was designed to be flexible, hardware independent, expandable and future proof. AHI allows multiple applications to share the audio hardware, so that different programs can play and record sound at the same time and without conflict.

The system's AHI settings can be adjusted using AHI Prefs.

Configuring Workbench and AmigaOS

2014-11-03T21:01:08Z

Daniel Hutchinson: /* The Save/Use/Test concept */

[[Category:Workbench]][[Category:Preferences]]
AmigaOS and the Workbench comes with a suite of program preferences to adjust Sound, Graphics, Text, Display, Font settings and more.

== Configuring through the User-startup ==

The user-startup is a simple AmigaDOS script containing commands that will be executed everytime AmigaOS starts.
It is optional but it is always used by the user as it is an easy way to add custom settings to the system.

The [[UserDoc:System_Scripts#startup-sequence|startup-sequence]] is so critical for the correct starting of the operating system that it is recommended to never modify it. Instead, users can edit the [[UserDoc:System_Scripts#user-startup|user-startup]] to start their own programs or set their own settings.

As an example, if you want to create an assign each time you boot AmigaOS, just add the following line to your user-startup:

''Assign myassign: Disk:mydirectory''

== Configuring through the Devs:... ==

== The Save/Use/Test concept==

[[File:Save-use-test-cancel.png|frame|Buttons at the bottom of the preferences programs]]
In AmigaOS you can modify some settings and test them '''without''' storing the modifications on disk. This is very handy because you can modify a lot of settings but you can always go back very easily to your saved configuration. You don't need to keep a list of all the changes you do and there is no fear you break something.
When you want to cancel all your tests, just restart the system and you automatically restore the previous (correct) settings.
This way it's up to the user to decide when the settings will be saved. The operating system will never store modifications by itself.

To reflect this mechanism all preferences programs have the following 4 buttons (if possible):

* Save
This will save on disk the current settings so they will become permanent. The preferences program will also close.

* Use
When you click this button, the current settings will be applied on the system but ''not saved'' on disk. The preferences program will also close.

* Test
This button will apply the current settings but the program will stay open. This way you can immediately see the result of your settings and you can modify them again and do another test.

* Cancel
This will cancel any modification you did since the program was opened. Changes will be reverted and the program will close.

== Preferences==

[[Workbench/Prefs|Prefs]] - List of all the preferences programs you can use to configure AmigaOS

Configuring Workbench and AmigaOS

2014-11-03T21:00:11Z

Daniel Hutchinson: /* List of all the preferences programs you can use */

[[Category:Workbench]][[Category:Preferences]]
AmigaOS and the Workbench comes with a suite of program preferences to adjust Sound, Graphics, Text, Display, Font settings and more.

== Configuring through the User-startup ==

The user-startup is a simple AmigaDOS script containing commands that will be executed everytime AmigaOS starts.
It is optional but it is always used by the user as it is an easy way to add custom settings to the system.

The [[UserDoc:System_Scripts#startup-sequence|startup-sequence]] is so critical for the correct starting of the operating system that it is recommended to never modify it. Instead, users can edit the [[UserDoc:System_Scripts#user-startup|user-startup]] to start their own programs or set their own settings.

As an example, if you want to create an assign each time you boot AmigaOS, just add the following line to your user-startup:

''Assign myassign: Disk:mydirectory''

== Configuring through the Devs:... ==

== The Save/Use/Test concept==

[[File:Save-use-test-cancel.png|frame|Buttons at the bottom of the preferences programs]]
In AmigaOS you can modify some settings and test them '''without''' storing the modifications on disk. This is very handy because you can modify a lot of settings but you can always go back very easily to your saved configuration. You don't need to keep a list of all the changes you do and there is no fear you break something.
When you want to cancel all your tests, just restart the system and you automatically restore the previous (correct) settings.
This way it's up to the user to decide when the settings will be saved. The operating system will never store modifications by itself.

To reflect this mechanism all preferences programs have the following 4 buttons (if possible):

* Save
This will save on disk the current settings so they will become permanent. The preferences program will also close.

* Use
When you click this button, the current settings will be applied on the system but ''not saved'' on disk. The preferences program will also close.

* Test
This button will apply the current settings but the program will stay open. This way you can immediately see the result of your settings and you can modify them again and do another test.

* Cancel
This will cancel any modification you did since the program was opened. Changes will be reverted and the program will close.

[[Workbench/Prefs|Prefs]] - List of all the preferences programs you can use

Workbench

2014-11-03T20:57:30Z

Daniel Hutchinson: Created page with "Prefs - details of the AmigaOS Preferences programs as found in the 'Prefs' drawer"

[[Prefs]] - details of the AmigaOS Preferences programs as found in the 'Prefs' drawer

Workbench/Prefs

2014-11-03T20:56:26Z

Daniel Hutchinson:

[[Workbench/Prefs/AHI|AHI]] (Audio Hardware Interface) - Allows for control over the audio functions of your Amiga

[[Workbench/Prefs/AmigaInput|AmigaInput]] - Setup for gamepads and joysticks

[[Workbench/Prefs/ASL|ASL]] - Allows for control over file requesters

[[Workbench/Prefs/Compatibility|Compatibility]] - Manages the 68K Just-in-time compiler settings

[[Workbench/Prefs/Console|Console]] - Controls the settings for the Amiga Shell

[[Workbench/Prefs/DefIcons|DefIcons]] - Interface to allow behaviour of default icons

[[Workbench/Prefs/DOS|DOS]] - Manages DOS settings

[[Workbench/Prefs/Font|Font]] - Controls Font selection for Workbench, Screens, and Windows

[[Workbench/Prefs/GUI|GUI]] - Used to control the look and feel of various elements of the AmigaOS 4 interface

[[Workbench/Prefs/Input|Input]] - Controls the settings for the keyboard and mouse

[[Workbench/Prefs/Internet|Internet]] - Contains settings for the computer's network connections

[[Workbench/Prefs/Locale|Locale]] - Sets the user's preferred languages

[[Workbench/Prefs/Notifications|Notifications]] - Controls the behaviour of Ringhio, the AmigaOS 4.1 pop-up notification system

[[Workbench/Prefs/Palette|Palette]] - Allows the user to adjust certain colours used for some on-screen elements

[[Workbench/Prefs/Picasso96Mode|Picasso96Mode]] - Advanced controls for creating and modifying graphics modes

[[Workbench/Prefs/Pointer|Pointer]] - Allows editing of the mouse pointer's image

[[Workbench/Prefs/PopUpMenu|PopupMenu]] - Settings controlling the look and behaviour of the system's pop-up menus

[[Workbench/Prefs/Printer|Printer]] -

[[Workbench/Prefs/PrinterGfx|PrinterGfx]] -

[[Workbench/Prefs/PrinterPS|PrinterPS]] -

[[Workbench/Prefs/ScreenBlanker|ScreenBlanker]] - Preferences for the system's screen saver / screen blanker

[[Workbench/Prefs/ScreenMode|ScreenMode]] - Settings for screen resolution and colour depth

[[Workbench/Prefs/Screens|Screens]] - Allows the setting up and control of custom screens for applications

[[Workbench/Prefs/Serial|Serial]] - Sets the default settings for the serial port

[[Workbench/Prefs/Time|Time]] - Allows the user to set the system's time and date

[[Workbench/Prefs/Timezone|Timezone]] - Allows the user to set their current timezone and Daylight Saving Time preferences

[[Workbench/Prefs/UBoot|UBoot]] - Advanced settings concerning the computer's initial booting system

[[Workbench/Prefs/USB|USB]] - Contains USB preferences and information

[[Workbench/Prefs/WBPattern|WBPattern]] - Settings for the background of the Workbench screen and directory windows

[[Workbench/Prefs/WBStartup|WBStartup]] - Controls which programs are launched when Workbench starts

[[Workbench/Prefs/Workbench|Workbench]] - Settings which control certain aspects of the Workbench's behaviour

Wiki Author Credits

2014-11-03T20:48:19Z

Daniel Hutchinson:

The following is a list of known contributors to this wiki:
* Adam Levin
* Alexandre Balaban
* [http://amigaak.org.nz/ Amiga Auckland]
* Andy Finkel
* Bart Whitebook
* Bill Borsari
* Bill Koester
* Bob Burns
* Bob Pariseau
* Bruce Barrett
* Bryce Nesbitt
* Carl Sassenrath
* Carolyn Scheppner
* Chris Green
* Chris Ludwig
* Chris Raymond
* Dale Luck
* Dan Baker
* [http://gtmooya.blogspot.com/ Daniel Hutchinson]
* Daniel Jedlicka
* Darius Taghavy
* Darren Greenwald
* Dave Berezowski
* Dave Lucas
* David Junod
* David Miller
* Don Cox
* Eric Cotton
* Ewout Walraven
* Frank Bunton, for his [http://aminet.net/package/docs/help/adosbegin AmigaDOS guide]
* Hans-Joerg Frieden
* James Jacobs
* Jerry Hartzler
* Jez San
* Jim Mackraz
* Joe Katz
* John Orr
* John Wiederhirn
* Karl Churchill
* Ken Farinsky
* Kevin Klop
* Larry Hildenbrand
* Leo Schwab
* [https://sites.google.com/site/takeaprogrammertolunch/ Lyle Hazelwood]
* Mark Barton
* Mark Ricci
* [http://wandel.ca/ Markus Wandel]
* Martin Taillefer
* Michael Sinz
* Nancy Rains
* Neil Kafferkey
* Neil Katin
* Olaf Barthel
* Paul Higginbottom
* Paul Sadlik
* Peter Cherna
* Philippe Ferrucci
* R.J. Mical
* Randell Jesup
* Ray Brand
* Rob Cranley
* Rob Peck
* Rob Wyesham
* Roman Kargin
* Sam Dicker
* Simon Archer
* Spencer Shanson
* Stan Shepard
* Steve Beats
* [http://www.solie.ca Steven Solie]
* Stuart Ferguson
* Susan Deyl
* Thomas Frieden
* Tom Pohorsky
* Tom Rokicki

Workbench/Prefs/DefIcons

2014-11-03T20:45:08Z

Daniel Hutchinson:

DefIcons manages what pseudo icon is assigned to a file without an icon, you can use DefIcons Prefs to set the default programs used to open different types of file.

[[File:DefIcons1.png|frame|center|DefIcons Preferences window]]

AmigaOS may well be a bit hard to understand if you come from the Windows/Mac/Linux world. There are lots of things that can be a little tricky to understand, and one of them is how to get a file such as a JPEG, AVI or even an MP3 file to open with a desired program when double clicking the file's icon in the Workbench. AmigaOS has an installed viewer called MultiView, however this program is somewhat limited and you may want to use a different program to view certain file types.

You could right click on an AVI or MP3 file and then select 'Information...', and from the icon menu browse to your program of choice, e.g. AmigaAMP for an MP3. The problem is that only that single file will then be associated with AmigaAMP. This is where DefIcons comes in. DefIcons allows you to manage and customise the default programs for opening different file types.

[[File:DefIcons2.png|frame|center|DefIcons Preferences window with filetype for 'jpeg' selected]]

On the left side of the window you will see the file types. In this example we are going to edit the program used to open all JPEG files that have a pseudo icon. Scroll down the list to jpeg, found under 'picture' and double click on 'jpeg'. Now a new window has appeared where you can make the necessary changes. Click the 'Icon' tab. Here you can change the file association by removing the current association with MultiView. Click to the button to the right of the text 'Default tool'. You now will now be asked to choose the ability which program you want to associate with the file type. You can choose any program on your computer, be sure to pick one that can load the file type, JPEG in this example. Browse to the program you wish the file type to open in, in this example the third party application 'LoView' is used. Click the 'Save' button and then also click 'Save' on the 'Deficons preferences' window.

[[File:DefIcons3.png|frame|center|Icon information window]]

Workbench/Prefs/DefIcons

2014-11-03T20:43:58Z

Daniel Hutchinson:

DefIcons manages what pseudo icon is assigned to a file without an icon, you can use DefIcons Prefs to set the default programs used to open different types of file.

[[File:DefIcons1.png|DefIcons Preferences window]]

AmigaOS may well be a bit hard to understand if you come from the Windows/Mac/Linux world. There are lots of things that can be a little tricky to understand, and one of them is how to get a file such as a JPEG, AVI or even an MP3 file to open with a desired program when double clicking the file's icon in the Workbench. AmigaOS has an installed viewer called MultiView, however this program is somewhat limited and you may want to use a different program to view certain file types.

You could right click on an AVI or MP3 file and then select 'Information...', and from the icon menu browse to your program of choice, e.g. AmigaAMP for an MP3. The problem is that only that single file will then be associated with AmigaAMP. This is where DefIcons comes in. DefIcons allows you to manage and customise the default programs for opening different file types.

[[File:DefIcons2.png|DefIcons Preferences window with filetype for 'jpeg' selected]]

On the left side of the window you will see the file types. In this example we are going to edit the program used to open all JPEG files that have a pseudo icon. Scroll down the list to jpeg, found under 'picture' and double click on 'jpeg'. Now a new window has appeared where you can make the necessary changes. Click the 'Icon' tab. Here you can change the file association by removing the current association with MultiView. Click to the button to the right of the text 'Default tool'. You now will now be asked to choose the ability which program you want to associate with the file type. You can choose any program on your computer, be sure to pick one that can load the file type, JPEG in this example. Browse to the program you wish the file type to open in, in this example the third party application 'LoView' is used. Click the 'Save' button and then also click 'Save' on the 'Deficons preferences' window.

[[File:DefIcons3.png|Icon information window]]

UserDoc:How AmigaOS Works

2014-11-03T20:42:50Z

Daniel Hutchinson: /* System components */

As already mentioned, AmigaOS was a pioneer in the early days of personal computing in delivering sophistication that contemporary systems could only have dreamt of and pretended to offer. Today, AmigaOS continues to offer a straightforward elegance that seems to be overlooked in the development of other platforms. Thanks to the concepts behind AmigaOS, the system is easy to understand and to use by everyone.

In this page we will explore all these concepts of AmigaOS. Also you will learn here the naming of all parts of the system.

= Introduction =

AmigaOS is made of different components which are either mandatory i.e. AmigaOS will not work without them or components the user can choose to use or not. All these components can have one or mutiple interfaces a user or a developer can use to operate with the components and through them to control the operating system.

= The most important components =

== Exec, the AmigaOS kernel ==

Exec is the kernel of AmigaOS. It is the component that pilots all other components. It is responsible of running programs, dealing with computer memory, managing low-level resources that programs may need. In other words, it organises everything to make the operating system run.

It is made of different parts that cannot be moved outside the kernel: the scheduler, the memory pager and the 68k interpretive emulator.

== AmigaDOS: the underlying system ==

The word "DOS" was originally an acronym for "Disk Operating System". Some say it should be "Disk Based Operating System" as it does a lot more than operate a disk and that it was really an operating system based (stored) on disks. Some say it should be "Device Operating System".

The whole AmigaDOS system includes things such as:

* A set of commands that can be used in the Shell window and elsewhere.
* A system for saving data to disk and retrieving it from disk.
* A system for filing data on disks.
* An interface for peripherals such as keyboards, monitors, printers, etc.
* A method of running programs
* A multitasking system for running more than one program at a time.
* etc. etc. etc.

Read the [[AmigaDOS manual]] to understand and learn everything about AmigaDOS.

== The Graphics library ==

The Graphics library handles every low level graphic operations like designing pixels on the monitor, creating graphic elements (bobs, sprites) and also writing text output.

== Intuition ==

The Intuition library is responsible for every graphical objects: windows, screens, gadgets, mouse pointers... It lays between any graphic program and the graphics library.

== The Workbench ==

The Workbench is the graphical place where you will manage your computer and all your files. The name was chosen because the user will use tools to create and work with the computer.

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

== The Shell ==

While some people prefer to control the operating system using their mouse, others prefer using the keyboard. The shell is a text based window when you can type commands to execute actions in the operating system. In the shell the commands will display the results of their execution.

== ARexx - inter-program communication by scripting ==

The ARexx scripting language can be used to operate the Workbench and the most important Amiga applications from a script containing ARexx commands. This is extremely useful to perform repetitive tasks or to do what the controlled application was not even design to do.
After a learning curve, everybody can use ARexx as it is built in the system and the scripts can be executed immediately like any other tool.

= How is my data stored? =
== Files ==
=== Executable files ===
Programs you can start are stored in executable files. They contain binary code directly understandable by the computer. They are files with an executable bit, a flag that shows AmigaOS that such file will do something when started.
An example is a music player. When you start this executable, the player opens and you can start playing music files.

AmigaOS can run two different kinds of executable files: the AmigaOS native programs made for the PowerPC processor and programs created for the Motorola 68k processors. The laters are executed inside an emulation that transcripts them into PowerPC code.

==== Scripts ====

Scripts are text files containing a list of commands. So they are not strictly executables like ''binary code'' files but they can be executed by AmigaOS like if they were.
This is the case with AmigaDOS and ARexx scripts. These files need to have the executable bit, and the script bit.

=== Data files ===
Files that are not executable are data files. These contain some data that will be manipulated by programs. Some examples are a music file, a video file or a text document.

== Directories/Drawers ==
In order to organise things a bit, files are not all of them in the same place. We create directories which like drawers of a cabinet will store different files of the same kind.
Often the name ''directory'' is used when talking about the directory which is stored on a disk. The graphical interface of AmigaOS being called the Workbench, directories are often called ''drawers''.

Note: directories are often called ''folders'' on other systems.

== Disks, partitions and volumes ==
=== Disks ===
Disks are storage medium you can purchase on a computer store. We use them to store our files. They can be internal hard disks, external ones or a USB disk drive.

=== Partitions ===
A disk is often very big and many users prefer to make it more organised. This is done virtually splitting the disk into several smaller parts. This operation is known as creating partitions on a disk.

[[File:Partitions.png|Small part of Media Toolbox showing different partitions on the harddisk]]

On this screenshot you can see one harddisk with many partitions. Each color corresponds to a different filesystem which defines how data is stored. Also you can see a greyed area which is a blank area on the disk i.e. no partition is defined at this position.

=== Volumes ===
A partition is a physical area on a disk. To access it with AmigaOS we could read the physical data off the partition but it's not an easy way. To make it easier AmigaOS uses the concept of volumes. These are virtual representations of a partition. The volumes have a name so AmigaOS and therefore the user can access all files/directories stored on it in a very practical way: just by using its name.

= How to identify files/directories =

== On the Workbench ==

The Workbench being graphical, a lot of things are understandable just by looking at them. That's why icons are often enough to understand what kind of object it represents: a file, a directory, a disk...

In case you have a doubt, just look at the information on an icon. The Workbench will tell you the type of the object. It is displayed next to its name.

== In a shell ==

In a shell you need to issue the command '''list''' to see if an object is a file or a directory.

[[File:Files-dirs-in-shell.png|The '''list''' command shows a file of 925678 bytes and two directories]]

A file will be displayed with its size, whereas a directory will be displayed with the text '''Dir''' next to it.

Also, as you can see on the screenshot, the list command displays other characteristics on these 3 items: the protection bits and the date they were updated the last time. The command also sums up what it just listed.

= All AmigaOS components =

AmigaOS is made of components that are needed as soon as the system starts or later when the user or the system needs them.

== Kickstart modules ==

These components are the heart of AmigaOS. Their duties is to do graphics, to handle discs or to handle all reads/writes to files. Also one of them is the AmigaOS kernel which is some kind of director handling the work of all other components.
These Kickstart modules are loaded at the beginning of the operating system boot process (read [[UserDoc:How_AmigaOS_Works#AmigaOS_boot_procedure|here]]). You can find all them in the '''Kickstart''' directory in the system volume. Here is a list:

=== Mandatory modules ===

The following modules are required in any AmigaOS system. Without one of these, the system will not start.

* kernel - The kernel works like a conductor in an orchestra. Its job is to make everything works together. It creates processes, handle memory usage, defines the way other components will access peripherals...etc. Note that the AmigaOS kernel is not based on any other kernel. It is a self made kernel that works since 1983.
* loader - this component handles the loading of all other kickstart modules
* battclock.resource.kmod - this module handles reading/writing the battery backed up clock which is used on all computers to keep the date and time
* bootimage - this is the boot picture. It is displayed during the start sequence of AmigaOS
* bootmenu.kmod - this component handles the Early Startup Menu the use can use to define some settings before starting AmigaOS
* con-handler.kmod - it directs the read and write requests to the console window, to a serial AUX: device or any other supported interface
* console.device.kmod - it opens a window and reads/writes text to and from that window
* diskboot.kmod - handles the booting of AmigaOS from a supported disk
* diskboot.config - this is a text file experienced users can modify to change the boot behaviour of AmigaOS
* dos.library.kmod - this module is a collection of functions that any program can use to perform actions on disks, files and directories
* elf.library.kmod - handles the loading of executable programs
* env-handler.kmod - handles the read/writes of environment variables
* FileSystem.resource.kmod - handles the use of the different filesystems
* gadtools.library.kmod - collection of functions used to create all graphic objects like gadgets, sliders, menus...
* gameport.device.kmod - handles the read/writes of game pads and joysticks
* graphics.library.kmod - collection of functions used to draw graphic elements on the monitor
* hunk.library.kmod - set of functions to read a data stream into memory
* input.device.kmod - handles of input events like keyboard events or mouse clicks
* intuition.library.kmod - collection of functions to create and handle all graphic elements (screens, windows, the mouse pointer...)
* layers.library.kmod - set of functions to be used to handle different layers in graphic operations
* keyboard.device.kmod - driver for the keyboard
* keymap.library.kmod - functions to handle different keymaps
* newlib.library.kmod - collection of functions to perform memory operations (allocating memory, copying memory areas... )
* nonvolatile.library.kmod - provides a simple means for an application developer to manage nonvolatile storage
* nvram.resource.kmod - handles the read/writes to the EEPROM chip present on many AmigaOS computers
* PCIGraphics.card - driver that supports the use of different graphic cards
* ram-handler.kmod - functions that handles the '''Ram disk:''' special disk
* ramdrive.device.kmod - device that allows the usage of the ramdrive device '''RAD:''' disk
* ramlib.kmod - loads disk based libraries and devices for exec.library
* rtg.library - library of functions perform lowlevel graphic operations on graphic cards
* shell.kmod - the AmigaOS command line interface
* strap.kmod - module that handles booting on different disk devices
* timer.device.kmod - driver to give access to timing functions

=== Filesystem support ===

These kickstart modules can be loaded or left aside. If you want to use a particular filesystem on your disk partitions, you need to load the corresponding filesystem module.

* CDFileSystem - handles the CD-ROM disks with data stored in different formats: ISO9660, HFS...
* SmartFilesystem - allows to store data on partitions in SFS0 and SFS2
* JXFileSystem - allows to create partitions in JXFS
* FastFileSystem - allows the usage of partitions in FFS and FFS2 layouts
* diskcache.library.kmod - component required by the SmartFileSystem and JXFileSystem modules

=== Hardware drivers ===

==== Graphic cards drivers ====

* 3dfxVoodoo.chip
* 3DLabsPermedia2.chip
* ATIRadeon.chip
* RadeonHD.chip
* siliconmotion502.chip

==== Disk drivers ====

Each of these drivers allow the use of disks connected to a disk controller. These files are named with the name of the controller they support. As an example, the '''sii3114ide.device.kmod''' allows to use disks connected on a '''Silicon Image SiI3114''' controller chip.

* it8212ide.device.kmod
* lsi53c8xx.device.kmod
* sam460sata.device.kmod
* sii3112ide.device.kmod
* sii3512ide.device.kmod
* sii3114ide.device.kmod
* sii0680ide.device.kmod
* sii3132ide.device.kmod

==== USB drivers ====

* hub.usbfd
* usbsys.device
* usbresource.library
* ehci.usbhcd
* ohci.usbhcd
* uhci.usbhcd
* massstorage.usbfd

==== Other drivers ====

* bootkeyboard.usbfd - allows a USB keyboard to be used even before the USB stack is loaded
* bootmouse.usbfd - allows a USB mouse to be used even before the USB stack is loaded
* fpga.resource.kmod - allows to use the FPGA components which are present on some Amiga computers
* i2c.resource.kmod - allows to use the i2c interface present on some Amiga computers
* xena.resource.kmod - provides access to the Xena chip on the AmigaOne X1000

=== Misc modules ===

* petunia.library.kmod - this module contains the Just-In-Time emulator that allows AmigaOS to run programs made for the Motorola 68k processor

== System components ==

[[File:Workbench_directory_listing.png|frame|right|List of directories and files present at the root of any AmigaOS system]]

Beside the kickstart modules, AmigaOS uses many different components that can be loaded only when used. These files are stored in different directories in the system volume.
Here is described a default AmigaOS installation.

* C
This directory contains AmigaDOS '''C'''ommands
* Classes
contains different object elements easy to be used in any program: gadgets, requesters, graphic table, windows...
* Devs
contains definition for '''Dev'''ices
* Emulation
contains files used for the 68k emulation (though E-UAE)
* Fonts
contains various systems fonts
* Internet
contains a dialer to connect to Internet
* Kickstart
contains the kickstart modules
* L
contains hand'''l'''ers and filesystems
* Libs
contains dynamic '''Libr'''airies of functions
* Locale
contains all files used to localise the system (catalogs, keymaps...)
* MUI
contains the needed files for programs that use the MUI third party graphic interface
* [[Prefs]]
contains the preference programs used to customise AmigaOS
* S
contains the '''S'''cripts
* SObjs
contains .so shared object library files
* Storage
contains other optional files
* System
contains some programs used by the system itself (i.e. you don't need to run them yourself) or low-level programs like disk tools
* [[Utilities]]
contains several programs you can use to achieve some tasks on AmigaOS

= Motorola 680x0 Emulators =

For a long time Amigas have had the famous Motorola 680x0 processors as the central unit for execution. Unfortunately the time of the 680x0 series is passing in favor of other architectures. The new era of processors reached the Amiga some time ago, when expansion boards became available for extending the Classic systems with the raw power of a PowerPC processor.

In the old operating system (AmigaOS 3.x) it was not possible to gain the full advantage of the new processors. The system itself and most of the applications required the original Motorola 680x0 processor. There was no 680x0 emulation available for the PowerPCs, so the 680x0 could not be "switched off".

Thus the new processors remained as a powerful, but mostly unused adjunct to the main 680x0 processor. "Native" PowerPC programs were rare, and every time a PowerPC program called the system, a so called "context switch" occurred between the 680x0 and PowerPC code, often causing a large performance penalty.

The new Amiga platform is based on the PowerPC processor family, therefore the new version of the AmigaOS has to smooth the transition from the 680x0 series, which is achieved by emulating the old processor architecture. The operating system itself is written almost 100 percent for the PowerPC processors, but the 680x0 legacy applications require an emulated 680x0 processor.

== Two 680x0 Emulators ==

In version 4.0 of AmigaOS, two different emulators were implemented; one is the successor of BlackBox emulation, it is an interpretive emulator, thus the emulation speed is mediocre. On the other hand it has a very low "reaction time", and is ideal for time critical parts, such as interrupts.

The other is Petunia, the "JIT emulator". A fast, but less compatible way of emulation of the legacy Motorola processors. It is intended mainly for emulating applications, and therefore, when execution of the application leaves the bounds of the application's code segment, emulation falls back to the interpretive method, where it does its job and returns to the JIT emulation again.

Dynamic recompilation (also called just-in-time compilation or simply JIT compilation) is a technique of translating foreign processor machine code to native machine code, "on the fly".

This technique is common nowadays, commonly applied in JAVA virtual machines, and it is also used with success in several emulators. In dynamic recompilation there is the possibility of runtime optimization of the emulated code by collecting statistics of the execution process. Therefore (theoretically) the final executed code can be even faster than the original code on its original processor.

== Features ==

Emulated opcodes:
* all user and supervisor level opcodes of the Motorola 68040
* all FPU opcodes of the Motorola 68881/68882

AmigaOS claims only 68020/68881 compatibility to applications because this is the safest compatibility level, but both emulators are compatible with the machine code up to the level of 68040/060 processors.

At compile time, a low level flag and branch control analysis allows on-the-fly optimizations of compiled code.

== Removing the JIT Emulator ==

Using the dynamic translation requires a lot more memory than the interpretive emulation. The translated code needs to be stored somewhere, not to mention the data collection tables.

If speed is not as important as the memory consumption of the system, then the JIT emulator can be removed, leaving the job to the interpretive emulator.

Thanks to the modular design of AmigaOS kickstart, all you need to do is edit the "Sys:Kickstart/Kicklayout" file, simply put a semicolon (;) at the beginning of the module line of Petunia.library.kmod. After rebooting the system from cold, the JIT emulator will not be reloaded. Make sure that you alter the appropriate configuration in the Kicklayout file, there may be several alternative configurations, with different names like "DefaultJIT", or "DefaultNoJIT".

== Configuring the Emulators ==

Petunia cooperates with a so called "black list". By default Petunia emulates every 680x0 program or library that is loaded by DOS.library/LoadSeg function, but if an executable or library shows incompatibilities with Petunia, then it can be explicitly inhibited from the dynamic recompilation by specifying it in a list file.

If an executable needs to be added to the list, then it can be done by extending the file "DEVS:applications.dos" with the '''Compatibility''' preferences program from the Prefs drawer of the system. Adding a program name to the list and checking it will prevent Petunia from emulating that program, and it will be interpreted instead by the built-in interpreter.

Removing a program from the list or unchecking (thus allowing Petunia to emulate it again) can be done with the same preferences program.

Please note: some programs consist of multiple executables (shared libraries, plugins). If you want to fully disable the translation of such programs, then every part must be added to the list.

For example to disable UnArc fully, you would have to add all files from libs:xad and also xadmaster.library to the list.

= AmigaOS boot procedure =

Basically a computer with AmigaOS does the following when the power button is pushed:

* [[File:Uboot.jpg|200px]]
the BIOS ([[UserDoc:BIOS|Uboot]] or [[UserDoc:BIOS|CFE]]) of the computer initialises the hardware: graphic card, USB ports... At this point, the monitor wakes up and the first information are displayed. This allows to see if hardware is correctly recognised. As an example you can see if a hard drive is correctly connected into the machine and your BIOS is correctly setup to make this drive useable.
* depending on how you setup the BIOS it will look on the harddisk to find the Second Level Booter (SLB). This program is stored on the first sectors of the disk. Whereas the BIOS does not know about AmigaOS disk structure, the SLB will be able to ''understand'' the AmigaOS partitions and files. In other words, it is the link between the BIOS and the rest of the boot procedure. Its goal is also to give you the ability to start several configurations present on the same drive.
* [[File:SLB.png|200px]]
the SLB will analyses all Amiga partitions on the disk it is installed on. It will read each [[UserDoc:kickstart_configuration|system configuration]] it finds on the partitions. It will show all available configurations for the user to select one to load.
The user can define many different kickstart configurations to choose from. Also both AmigaOS and Linux can be selected for boot.
* [[File:Kmods loading.png|200px]]
the SLB loads the kickstart files of the selected configuration and executes the '''Loader''' module
* '''Loader''' executes the kickstart modules (Exec, devices, libraries...)
* AmigaOS becomes alive displaying the AmigaOS boot picture on the monitor
* the AmigaDOS library executes the [[UserDoc:System_Scripts#startup-sequence|startup-sequence]] script found on the system volume
* the Startup-sequence will be executed and all commands it contains are executed. It means that starting from here the boot procedure is easy to follow and understand.
* the Workbench is started

At this point the user can use his/her computer.

= How to make a Bootable USB Memory Stick for AmigaOS 4.1 =

By Julian Margetson ("Spectre660")

Prerequisites:
* USB memory stick of 2 GB or less in size.
* It is best to only have one USB mass storage device connected while you are creating your bootable USB memory stick.
* Plug the USB memory stick into a USB port on your machine.
* Note that the device will be formatted so make sure that you use an empty memory stick or one that does not contain any data that you need or backup the contents before you begin.

Procedure:
# You use Media Toolbox in the System: drawer to prepare the USB stick. On starting Media Toolbox select ''usbdisk.device'' as the device to use.
# Make certain that you have selected usbdisk.device and not any other device.
# Click on "Start"
# You will see the usb mass storage unit connected in a list.
# Make sure that the Unit type displayed for the USB memory stick is "Removable hard disk"
# Select that Unit by clicking on it.
# The first thing that you need to do is to install the RDB onto the USB Memory Stick.
# Click on the "Install" button.
# A window Labeled "RDB/disk geometry editing" comes up.
## Towards the bottom of the window is the "AmigaOne boot code (SLB)" section.
## Select the "Install" button .
## A file requester "Select AmigaOne Boot Code" now comes up with the Drawer choice defaulting to "l:"
## Select file "slb_v2".
## Select Ok.
## You are now returned to the "RDB/disk geometry editing window".
## Select "Ok-accept changes".
# You are now returned to the display showing the attached USB unit.
# Select "Edit partitions and Filesystems". You will now see the Window 'Editing partitions for disk"
# Select "Add partition"
# This defaults to using the whole device as a single partition.
# It is possible to use create more partitions but for this tutorial we will only use one.
# You now need to give the partition a unique name (e.g. USB0 or something that is different from any of the existing partitions on your hard drive). This is done by changing the default DH0 in the "Name" box.
# Now make sure that the Boxes "Automount" and "Bootable" are selected and show the "Tick mark".
# You need to set "Boot priority" to higher than the boot priority of your hard drive boot partition(s). This is done by increasing Boot priority by clicking on the "+" to the right of the "boot priority" box. Normally you can set the boot priority to 2 .
# Next it is time to select the file system to use.
# Select "Select filesystem/edit details".
# The Window "Editing details for partition 'USB0'" ,or whatever partition name you used, comes up.
## Select the file system that you are going to use by selecting the pull down menu under "Filesystem chooser".
## Only filesystems SFS/00 or SFS/02 will work for a bootable device.
## The option that gives the most flexibility at the moment is SFS/00 as a USB stick in this format can be read and written to using another compatible system in the event that you need to make modifications after it is created without a booting AmigaOS 4.1 machine.
## Next select Blocksize from the "Blocksize" pull down menu. 512 is the correct size to use.
## Now Select "Ok-accept changes".
## Your are now returned to the "Edit partitions for disk" window.
## Again select "Ok-accept changes"
# You are now returned to the window showing the USB mass storage unit list.
# Select "Save to disk"
# A requester pops up with the options "Yes, Save." or "No!"
# Select the "Yes, save." option.
# You now close Media Toolbox by clicking on the close icon (X) on the left of the Media Toolbox window.
# This will give you a requester advising that you need to reboot the machine for the changes to take effect. At this point you need to remove the USB memory stick for the machine. If you do not then the Machine will attempt boot from it before it is formatted and the required Kickstart and AmigaOS 4.1 files are copied to it.
# Select "Yes, reboot NOW!".
# Once you have rebooted connect your USB Memory Stick to a USB port.
# A disk icon "USB0:Uninitialized" (or whatever partition name you used) appears on Workbench.
# You now need to format the device.
# To format Select this Icon and go to the Workbench "Icons" menu .
# Select "Format Disk"
# You can give the USB Memory Stick a unique name and select whether you want a Trashcan or not.
# You can use either a full Format or a Quick Format. Full Format may take a few minutes.
# Once formatted the USB Memory Stick is ready for you to copy the required files from you hard drive or AmigaOS Install CD to it in order to boot AmigaOS 4.1 from it.

Workbench/Prefs/DefIcons

2014-11-03T20:39:37Z

Daniel Hutchinson:

Workbench/Prefs/DefIcons

2014-11-03T20:38:06Z

Daniel Hutchinson:

DefIcons manages what pseudo icon is assigned to a file without an icon, you can use DefIcons Prefs to set the default programs used to open different types of file.

[[File:deficons1.png|frame|center|DefIcons Preferences window]]

AmigaOS may well be a bit hard to understand if you come from the Windows/Mac/Linux world. There are lots of things that can be a little tricky to understand, and one of them is how to get a file such as a JPEG, AVI or even an MP3 file to open with a desired program when double clicking the file's icon in the Workbench. AmigaOS has an installed viewer called MultiView, however this program is somewhat limited and you may want to use a different program to view certain file types.

You could right click on an AVI or MP3 file and then select 'Information...', and from the icon menu browse to your program of choice, e.g. AmigaAMP for an MP3. The problem is that only that single file will then be associated with AmigaAMP. This is where DefIcons comes in. DefIcons allows you to manage and customise the default programs for opening different file types.

[[File:deficons2.png|frame|center|DefIcons Preferences window with filetype for 'jpeg' selected]]

On the left side of the window you will see the file types. In this example we are going to edit the program used to open all JPEG files that have a pseudo icon. Scroll down the list to jpeg, found under 'picture' and double click on 'jpeg'. Now a new window has appeared where you can make the necessary changes. Click the 'Icon' tab. Here you can change the file association by removing the current association with MultiView. Click to the button to the right of the text 'Default tool'. You now will now be asked to choose the ability which program you want to associate with the file type. You can choose any program on your computer, be sure to pick one that can load the file type, JPEG in this example. Browse to the program you wish the file type to open in, in this example the third party application 'LoView' is used. Click the 'Save' button and then also click 'Save' on the 'Deficons preferences' window.

[[File:deficons3.png|frame|center|Icon information window]]

Workbench/Prefs/DefIcons

2014-11-03T20:26:09Z

Daniel Hutchinson:

DefIcons manages what pseudo icon is assigned to a file without an icon, you can use DefIcons Prefs to set the default programs used to open different types of file.

[[File:tutorial_deficons_1.png|frame|center|DefIcons Preferences window]]

AmigaOS may well be a bit hard to understand if you come from the Windows/Mac/Linux world. There are lots of things that can be a little tricky to understand, and one of them is how to get a file such as a JPEG, AVI or even an MP3 file to open with a desired program when double clicking the file's icon in the Workbench. AmigaOS has an installed viewer called MultiView, however this program is somewhat limited and you may want to use a different program to view certain file types.

You could right click on an AVI or MP3 file and then select 'Information...', and from the icon menu browse to your program of choice, e.g. AmigaAMP for an MP3. The problem is that only that single file will then be associated with AmigaAMP. This is where DefIcons comes in. DefIcons allows you to manage and customise the default programs for opening different file types.

[[File:tutorial_deficons_2.png|frame|center|DefIcons Preferences window with filetype for 'jpeg' selected]]

On the left side of the window you will see the file types. In this example we are going to edit the program used to open all JPEG files that have a pseudo icon. Scroll down the list to jpeg, found under 'picture' and double click on 'jpeg'. Now a new window has appeared where you can make the necessary changes. Click the 'Icon' tab. Here you can change the file association by removing the current association with MultiView. Click to the button to the right of the text 'Default tool'. You now will now be asked to choose the ability which program you want to associate with the file type. You can choose any program on your computer, be sure to pick one that can load the file type, JPEG in this example. Browse to the program you wish the file type to open in, in this example the third party application 'LoView' is used. Click the 'Save' button and then also click 'Save' on the 'Deficons preferences' window.

[[File:tutorial_deficons_3.png|frame|center|Icon information window]]

Workbench/Prefs/DefIcons

2014-11-03T20:25:41Z

Daniel Hutchinson:

Prefs

2014-11-03T20:09:19Z

Daniel Hutchinson: Daniel Hutchinson moved page Prefs to Workbench/Prefs

#REDIRECT [[Workbench/Prefs]]

Workbench/Prefs

2014-11-03T20:09:19Z

Daniel Hutchinson: Daniel Hutchinson moved page Prefs to Workbench/Prefs

[[Workbench/Prefs/AHI|AHI]] (Audio Hardware Interface) - Allows for control over the audio functions of your Amiga

[[Workbench/Prefs/amigainput|AmigaInput]] - Setup for gamepads and joysticks

[[Workbench/Prefs/asl|ASL]] - Allows for control over file requesters

[[Workbench/Prefs/compatibility|Compatibility]] - Manages the 68K Just-in-time compiler settings

[[Workbench/Prefs/console|Console]] - Controls the settings for the Amiga Shell

[[Workbench/Prefs/deficons|DefIcons]] - Interface to allow behaviour of default icons

[[Workbench/Prefs/dos|DOS]] - Manages DOS settings

[[Workbench/Prefs/font|Font]] - Controls Font selection for Workbench, Screens, and Windows

[[Workbench/Prefs/gui|GUI]] - Used to control the look and feel of various elements of the AmigaOS 4 interface

[[Workbench/Prefs/input|Input]] - Controls the settings for the keyboard and mouse

[[Workbench/Prefs/internet|Internet]] - Contains settings for the computer's network connections

[[Workbench/Prefs/locale|Locale]] - Sets the user's preferred languages

[[Workbench/Prefs/notifications|Notifications]] - Controls the behaviour of Ringhio, the AmigaOS 4.1 pop-up notification system

[[Workbench/Prefs/palette|Palette]] - Allows the user to adjust certain colours used for some on-screen elements

[[Workbench/Prefs/Picasso96Mode|Picasso96Mode]] - Advanced controls for creating and modifying graphics modes

[[Workbench/Prefs/pointer|Pointer]] - Allows editing of the mouse pointer's image

[[Workbench/Prefs/popupmenu|PopupMenu]] - Settings controlling the look and behaviour of the system's pop-up menus

[[Workbench/Prefs/printer|Printer]] -

[[Workbench/Prefs/printergfx|PrinterGfx]] -

[[Workbench/Prefs/printerps|PrinterPS]] -

[[Workbench/Prefs/screenblanker|ScreenBlanker]] - Preferences for the system's screen saver / screen blanker

[[Workbench/Prefs/ScreenMode|ScreenMode]] - Settings for screen resolution and colour depth

[[Workbench/Prefs/screens|Screens]] - Allows the setting up and control of custom screens for applications

[[Workbench/Prefs/serial|Serial]] - Sets the default settings for the serial port

[[Workbench/Prefs/time|Time]] - Allows the user to set the system's time and date

[[Workbench/Prefs/timezone|Timezone]] - Allows the user to set their current timezone and Daylight Saving Time preferences

[[Workbench/Prefs/uboot|UBoot]] - Advanced settings concerning the computer's initial booting system

[[Workbench/Prefs/usb|USB]] - Contains USB preferences and information

[[Workbench/Prefs/wbpattern|WBPattern]] - Settings for the background of the Workbench screen and directory windows

[[Workbench/Prefs/wbstartup|WBStartup]] - Controls which programs are launched when Workbench starts

[[Workbench/Prefs/workbench|Workbench]] - Settings which control certain aspects of the Workbench's behaviour

Workbench/Prefs/deficons

2014-11-03T20:07:51Z

Daniel Hutchinson: Daniel Hutchinson moved page Workbench/Prefs/deficons to Workbench/Prefs/DefIcons

#REDIRECT [[Workbench/Prefs/DefIcons]]

Workbench/Prefs/DefIcons

2014-11-03T20:07:51Z

Daniel Hutchinson: Daniel Hutchinson moved page Workbench/Prefs/deficons to Workbench/Prefs/DefIcons

DefIcons manages what pseudo icon is assigned to a file without an icon, you can use DefIcons Prefs to set the default programs used to open different types of file.

Workbench/Prefs

2014-11-03T17:59:32Z

Daniel Hutchinson: Created page with "AHI (Audio Hardware Interface) - Allows for control over the audio functions of your Amiga AmigaInput - Setup for gamep..."

Workbench/Prefs/gui

2014-11-03T17:53:33Z

Daniel Hutchinson: Created page with "The look of AmigaOS is highly customisable and you can change almost all elements of the GUI using GUI Prefs."

The look of AmigaOS is highly customisable and you can change almost all elements of the GUI using GUI Prefs.

Workbench/Prefs/input

2014-11-03T17:52:43Z

Daniel Hutchinson: Created page with "Input Prefs is used to adjust the mouse speed, double click delay and to select the appropriate keyboard type."

Input Prefs is used to adjust the mouse speed, double click delay and to select the appropriate keyboard type.

Workbench/Prefs/screenblanker

2014-11-03T17:51:20Z

Daniel Hutchinson: Created page with "ScreenBlanker preferences is used to configure the system's screen saver or screen blanker. ScreenBlanker can also be used to configure when the monitor should switch to an en..."

ScreenBlanker preferences is used to configure the system's screen saver or screen blanker. ScreenBlanker can also be used to configure when the monitor should switch to an energy saving standby mode.

ScreenBlanker is found in the Prefs drawer.

Workbench/Prefs/wbstartup

2014-11-03T17:48:40Z

Daniel Hutchinson: Created page with "WBStartup is a Preferences program found in the Prefs drawer that is used to manage which tools and commodities are loaded when Workbench starts up, for example a screen blank..."

WBStartup is a Preferences program found in the Prefs drawer that is used to manage which tools and commodities are loaded when Workbench starts up, for example a screen blanker or third party commodity such as AllKeys.

In earlier versions of AmigaOS there was a WBStartup drawer (SYS:WBStartup). AmigaOS 4.1 can still handle this directory, so if preferred you can create this drawer and put the programs you need in there and it will work as with earlier versions of AmigaOS.

Workbench/Prefs/DefIcons

2014-11-03T17:15:14Z

Daniel Hutchinson: Created page with "DefIcons manages what pseudo icon is assigned to a file without an icon, you can use DefIcons Prefs to set the default programs used to open different types of file."

DefIcons manages what pseudo icon is assigned to a file without an icon, you can use DefIcons Prefs to set the default programs used to open different types of file.