UEFI and GPT

• Check that UEFI (the new BIOS) has options set for UEFI boot and not CSM bois mbr boot
• SATA drive is set for AHCI and not Legacy

though this can have issues with any OS already installed on the hard disk. If in doubt, do nothing and seek advice.

BIOS and msdos

• It might require some adjustments to the BIOS setup (usually by pressing DEL or F2 or F1 F12 or ESC on the very early boot up of the computer). Then either one of the options will enable booting from CDROM, as it is quite often disabled by default. Or the other way to is re-arrange the boot order so that CD or DVD comes out on top. Try looking here Windows or Bios or Boot or web search "BIOS BOOT CDROM"

The easiest way to boot from the AROS installation CD or DVD is if you have a computer that supports booting from an optical drive. Most Pentium 2's and above have that BIOS option but...

• At the SAME time, check if the SATA/AHCI option is set to Emulate or IDE Legacy, though this can have issues with any OS already on the hard disk. If in doubt, do nothing and seek advice.

• check that under BIOS settings you DO NOT have plug&play OS selected as Aros at this point is unable to route interrupts on its own and needs the BIOS to do that.

Save options changed at the end.

Advice for various machines

Stages involved in a typical AROS boot start up but be aware that VESA mode gives no visual output whilst booting. Use vga (4bit mode - safe mode).

ACPI: ????
[HPET] 
[Kernel:????]
[PCI] Everything OK
[AHCI]
[ACPI]
[BattClock] Got RTC century offset 0x32 from ACPI 

[Vesa]  only if vesa is chosen as graphics option 

[ATA] detect hd & cd drives 
[ATA0?] ata-identity 
[Boot] choose suitable boot option 
[packet] 
[DOS] 

waiting for bootable media 

[MSS] usb setup
[drm] nouveau 
[ATI]

If boot fails, please give us some indication where the boot stops and the message(s) on screen.

The "noacpi" boot option causes all [PCI] devices to be invisible to AROS. Although disk drives may still work, network, sound etc. drivers won't.

Options in GRUB menus to disable certain other components for debugging:

Disable ATA: "ATA=off"
ATA safe mode: "ATA=nodma,32bit"
Disable AHCI/SATA: remove ahci.device line with Ctrl-K.
Disable USB: remove pciusb.device and poseidon.library lines with Ctrl-K.
Disable native graphics: "nomonitors"

Disabling audio can't be done in GRUB, but disabling the startup sound in Icaros prefs should prevent it from starting (unless you plug an USB device in or out, which may play a sound).

Timeout while waiting for device to complete operations

with BIOS set to AHCI mode stops at "waiting for bootable media" screen, changing BIOS back to IDE mode boots up all the way to the desktop.

The native SATA/AHCI driver doesn't always work. If you get errors related to ahci.device, try disabling it. Press E when your chosen boot entry is highlighted in the GRUB menu, scroll down to the ahci.device entry, and delete it with Ctrl-K. Then press Ctrl-X to boot. If your disk isn't accessible at all with this change, you might need to change the SATA controller to IDE legacy mode in the BIOS: however, making this change will likely cause problems booting Windows on the same machine (if it's already installed). To disable ahci.device permanently, edit the text file "SYS:Arch/pc/grub/grub/cfg", and remove the ahci.device line from all boot entries you intend to use.

The ATA driver doesn't always work. If you get errors related to ata.device, try using the alternative in sys:devs/alt which is an older version. Press E when your chosen boot entry is highlighted in the GRUB menu, scroll down to the ata.device entry, and change it to read "module /Devs/Alt/ata.device". Then press Ctrl-X to boot. To make this change permanent, edit the text file "SYS:Arch/pc/grub/grub/cfg", and change the path to ata.device in all boot entries you intend to use.

error code (-6) when ahci.device (has writing to disk problem but not reading) is enabled. change this line in your grub and reboot if that helps

#module /Devs/ahci.device      << disable
module /Devs/Alt/ata.device    << add this line instead

and sata controller can be ahci in bios

If all else fails, try a nightly and add the option sysdebug=all to the grub line as that is able to report more feedback.

• A laptop may also have an internal WLAN/Bluetooth-adapter and a hardware switch to switch it off.
• If you have a USB mouse connected, try using a PS2 mouse. If you have one just for testing, or removing the USB mouse and put back later on in the boot
• BEWARE of hubs. Moving them to the ports on the back of the machine allowed everything to start working in a "enableusb" removed situation - ie. execute s:poseidon-startup later
• Legacy mode sometimes is only available on e.g. the front or just only the back ports.

Mac Intel x86 64bit

• If you use VESA mode, you can see the debug log if you add 'vesahack' to the command line. This will set up split-screen mode. In the upper half you'll see AROS screen, in the bottom - debug log.
• If you get crashes at early boot, try adding 'NOACPI' to the command line. ACPI stuff is very poorly tested because discovery fails on Mac (different ROM).

if freezes/stops at [ATA--] ata_Scan Waiting for Buses to finish Initialising

• ATA=32bit,nodma
• ATA=32bit,nosata2pata
• ATA=nopci,nolegacy (This should disable ATA).

if old VIA or SIS chipset motherboards with cdrom read io errors or ATA or the start up just freezes

• ATA=nodma,nopoll

Press Ctrl and X together (or F10) to exit and boot with the new options. Just experiment with different variations until successful. Those working options will need to be reused with every reboot of AROS until you can edit the grub.cfg and make it permanent ie. install to hard disk or usb.

Other useful grub command line options - nomonitors, noacpi, vesahack, nopoll 

Also, how is the dvd drive connected (do you use hubs ? = no-no), and what usb version is used ? usb sometimes has issues with certain devices connected to the same header, try another one in such cases. Furthermore sata dvd seems to have problems spinning up again

Pre year 2000 computers which do not have USB boot options can use the floppy disk boot method (either AROS or Plop change Setup->Bootmanager->Force USB 1.1) which will continue booting from the USB afterwards.

Pre year 1996 computer does not support booting directly from CDROM you can create a boot floppy (either AROS or Plop) and use it together with the CDROM. Simply insert both the boot floppy and the CD into their respective drives and reboot. AROS will start booting from the floppy, but after the most important things have been loaded (including the CDROM filesystem handler) it will continue booting from the CDROM.

switch to one of these modes, or in fact something as simple as 1024x768@60hz using the Intel Driver then the screen corrupts on the next system boot (As a reboot is needed after saving the settings) AROS -> prefs -> Env-Archive and look for screenmode.prefs file. Just delete it.

SysExplorer should hopefully show the correct information for devices, SysMon should hopefully show the correct task info and cpu load. Some virtual machines will result in some info not working (e.g. the CPU frequency in SysMon).

Also make sure the machine restarts correctly using the menu options, and if you have it running Native please check if the power button shuts down the machine when you briefly press it (as opposed to having to hold it for 10secs).

You may also want to see if USB is working if it didn't before, have experienced issues so far on the SMP build when writing to USB or copying files (so don't use something with files you don't want to lose ... better safe than sorry)

Debugging capture serial debug at all (especially with sysdebug=all or --sysdebug=all) to see it displayed on screen

• yes, usb -> rs232 adapters can work most of the time, some of the cheapest ones are not fully compatible with all rs232 devices to capture to another device
• you will need a null modem cable (or a null modem adapter usually female to female) in addition to the usb -> rs232 adapter (usb adapter is a normal modem ie. the pins are not crossed over)

Normal modem cable - straight connection DCE

Pin 2 -> Pin 2  RXD
Pin 3 -> Pin 3  TXD 
Pin 5 -> Pin 5  GND

Null modem cable connections DTE

Pin 2 -> Pin 3
Pin 3 -> Pin 2
Pin 5 -> Pin 5

(9pole SUB-D)

serial  ser: (amiga/aros)  tty2 tty1USB0 (linux)  COM1 (windows)  (depends on the os being used) 
speed baud transfer rate 9600 38400     lower baud might be more successful 
data bits 8
stop bits 1
parity none
handshaking flow control - none xon/xoff (most likely)  rts/cts  dsr/dtr (pins not connected so should not work) 

Additional solutions can be found here.

Common Keyboard Shortcuts

RAlt Right Alt Key 
LAlt Left Alt Key 
RWinKey Right Windows Key 
LWinKey Left Windows Key 
RAmiga Right Amiga Key (if one)
LAmiga Left Amiga Key (if one)

Bootup Options

Spacebar during boot, enters the bootmenu which allows a boot without startup sequence, etc

Left Click

LAmiga = LWinKey = F11

Right Click

RAmiga = RWinKey = F12

Mark

RAmiga and B

Cut

RAmiga and X

Copy

RAmiga and C

Paste

RAmiga and V

Search

RAmiga and S

Mouse Movement

LAmiga and together with arrow keys - shift as well at the same time as well to move faster

Mouse Selection

LAmiga and LAlt to select

Screen Switching

LAmiga and M or N

HELP key

Can sometimes be mapped to F11 but can be changed see FKey below

FKey

Exchange can be opened with alt, ctrl, h

In Tools/Commodities, there's an FKey commodity which allows you to make actions assigned to some combinations of keys.

run QUIET sys:Tools/Commodities/ClickToFront >Nil: 
run QUIET sys:Tools/Commodities/DepthMenu >Nil: 
run QUIET sys:Tools/Commodities/Blanker seconds=300 >Nil: 

In Icaros, Alt Ctrl F opens FKey app and show already assigned key-presses shortcuts

Open Prefs                 = LAmiga F2
Finder                         = LAmiga F3 
Alt Tab                        = Cycle Windows
LAmiga Tab  or M       = Cycle Screens
Enlarge Window         = Alt Up arrow 
Shrink Window           = Alt Down arrow 
Toggle Window Size   = Alt Home 
Insert Text
Run Program             = LAmiga ESC 
Run Arexx Script

Drag and drop sys:Tools/Commodities/Fkey into your Workbench Startup drawer, double click on it and assign some programs to the keys. You could have F1 key set up to run the command "Avail Flush", which is always a quick handy way of flushing the RAM without needing to run any extra apps or patches to do it for you. You can also just press Left-Amiga & "e" to execute a command, then you can just type in ed or ced, or cli. Or just set it up as an F-Key.

If your FKey GUI pops up when you start your Workbench up and you don't want it to, click once on the icon, go to the Icons-Information in the menu and make sure it has the tooltype set "CX_POPUP=NO".

Although there are heaps of docks, menus and other launcher programs on the Amiga, this has got to be one of the quickest and less complicated ways to launch programs, and it comes with the OS.

Now let's launch it and assign the locale switching. After you double-click on FKey icon, launch the Exchange, choose the FKey from list and click the Show button. This will invoke the FKey window. You can see the ALT TAB in list assigned to window switching. Now enter the first key combination, say, ALT Z and go to the right panel. Choose Launch the program from pulldown menu and enter SYS:Prefs/Input as an argument. Append the USE switch and english preset name to the string as shown:

SYS:Prefs/Input USE SYS:Prefs/Presets/english

Click on the New Button to add the another combination. Now set the combination for your locale as shown above, replacing english name with your preset name. Click New button again and then Save Settings. Now you can use defined combinations to switch the layouts.

Cycle Windows
Cycle Screens
Enlarge Window
Shrink Window
Toggle Window Size
Insert Text
Run Program
Run Arexx Script

Joystick/Joypad

Poseidon is the USB stack with Trident adding a GUI (graphical user interface) prefs. 

Just plug in your digital/analogue joystick or gamepad into USB port. The device will be handled by Poseidon USB stack.

the context sensitive page would come up right on pressing the help key inside the relevant window. The manual is in this archive, just in case it isn't in SYS:Locale/Help

DOpus 5 Directory Magellan

Dopus 5.x was a whole desktop replacement on the Amiga Workbench (Desktop).

Left mouse button clicked twice on the desktop background brings up the Device List window. Green strip notifies SRCE (source) and if another is open it may be red for DEST (destination). clicking on the red strip changes to green Word list of actions with a left mouse click on the DOWN Arrow and directory stuff with < button next to it

Right Mouse click and Settings - select the top option of Clock which adds a Date/Clock to the title bar

Right Win key together with 4 for the Environment (shortcut for Right Mouse Click - Settings - Environment) - Change the Backgrounds, etc

Right Win Key together with 1 for the Button Bank Editor (toolbar icons) described the icons associated with Dopus 5.

Settings - Themes i.e. D5THEMES: assign for DOPUS5:Themes

Each Dopus5 themes are stored in a separate directory, named appropriately, which contains further sub directories for

• Screens (jpg or anything supported by datatypes)
• Sounds (wav iff snd svx supported)
• Icons (png newicons glowicons )
• Desktop Patterns (iff )

Shift and click on the icon - runs the icon

Closing shutting down the computer and restarting rebooting - F12 and E and put in reboot cold

arexx scripts (see dopus5/arexx/

arcdir

Wanderer

• icon text sizes, colors, etc with wanderer prefs

Provides a way to hide the old Workbench 3.1 style of windows and screens. The default content of Prefs/Env-Archive/SYS/themes.var should be "themes:ice". When using the theme prefs, please do NOT click the Use button. Its useless. As you know, it will ask for the theme volume. Just pick the theme you want, click on Save, then reboot.

• Decoration is on. Any time trying to change theme, you get: "Please insert volume Theme: in any drive"?

You could check if you find SYS:System/Themes or if it is missing. Than you could open startup-sequence which you can find in drawer "S". There should be a line: Assign THEMES: SYS:SYSTEM/THEMES >Nil: This does the trick. Open a shell and run: Assign THEMES: SYS:SYSTEM/THEMES Than start the Theme prefs again... this should work

• The theme is the only thing that I know to slow the system a bit, but It's not that performance impacting on most uses, and you can switch it of completely. Remove C:Decoration from the bottom of the file sys:s/startup-sequence.

ALua/Zulu script built for faster Wanderer skin management. You can modify config files, install new (wdz format/zipped skin files) and delete skins via the Theme Manager.

Global.Prefs

Scalos

Import your ToolsDaemon configs for top pull down menus for apps, etc.

DOpus 4 Directory Opus

Many users prefer the simplicity of DOpus and the following added to the bottom of the user-startup script in S: drawer/directory

run DOPUS:DirectoryOpus -i >NIL

makes DOpus starts up in Iconified state at the top of Wanderer's screen. Left click on this to highlight and right mouse click to open.

Just click on the sides of either outer edges of DOpus windows and it will display the parent device/volume list.

DOpus saves it features in a CFG file which can be edited to suit anyones' needs by reading the Dopus Manual which is in Guide format.

AmiStart

• how to disable annoying zune/mui 'bubbles'?

try a right-click on AmiStart and release on Global settings. Then click on the bubbles gadget. Move the Show Bubbles slider all the way to the left.

Boing Bar

drag icons to ends of the bar and move them on the Bar using the Prefs/BoingIconBar

IControl and Windows

; run shell
if ${Icaros/autoshell} EQ true
  run QUIET c:newshell >NIL:
EndIF

Icons

Icons are png pictures renamed as .info e.g. any Office app would have a Office.png renamed as Office.info or MyApp.png as MyApp.info, etc.

To select multiple icons and save their positions, click on the first icon and after while you hold the Shift key down select further icons and don't release it before SnapShot is finished. You can also select a whole group of icons by pressing the LMB at the top left of the icons and while keeping the LMB down moving the power towards the bottom right. A expanding bounding box will appear and all the icons within it will be selected.

Clean Up menu option (right mouse button -> Icons) rearranges icons in a drawer or disk window into a neater condition. To use, open the window to rearrange and select Clean Up. To keep the icons in the new positions, select all the icons (shift key or mouse selection) and select 'Snapshot'.

Btw, are your icons, the #?.info files, writable, is the W flag set ?

Is there any way in AROS to change an icon type from Project to Tool or vice versa? Either the SIT option of ProcessIcon, or the TYPE option of HandleInfo (not sure if this one works at all, please test with care).

processicon sys:pathoftheicon SIT=Project 

SIT Set type of ICON. Allowed types are: "Disk", "Drawer", "Tool", "Project", "Garbage", "Device", "Kick" and "AppIcon".

C:Join Image1.png Image2.png TO MyFile.info is enough to make a dual state icon from two png images. You can then use Wanderer's menu Icon/Information on it to edit its fields and tooltypes.

Amiga OS 3.x AfA icons thread, Later DualPNG and OS4 icons thread and Alternative Icons sets like ClassicWB

AISS toolbar images unpack unarc them into RAM: and copy Images directory to SYS:Prefs/Presets/

AISS icons are looked for in PROGDIR:, PROGDIR:Images, SYS:Prefs/Presets/Images and then in TBImages: according to Open Amiga guidelines.

there is Demos/iconscale which could be launched from S:User-Startup with two arguments, telling it the horizontal and vertical size. IE something like

Demos/iconscale 40 40

It will shrink icons... not sure if it will be very nice though. it doesn't work for the icons on the main desktop.

there is an option to scale an icon to a bounding box afair but i dont remember exactly how to activate it in user-startup. try perhans iconsize followed by two numbers, like: iconsize 32 32

;******************************************************************************
;                            16 color palette
;* Please note: when using HEX values you need to provide colors in BGR order 
;* (meaning: Blue-Green-Red) _not_ RGB  (endianness heritage from 68K code?)    
;******************************************************************************


;PEN 0 - RGB 153-153-153 (DEC) | BGR 99-99-99 (HEX)
c:setpencolor SCREEN="Workbench" PEN=0 COLOR=$999999 >NIL:

;PEN 1 - RGB 17-17-17 (DEC) | BGR 11-11-11 (HEX)
c:setpencolor SCREEN="Workbench" PEN=1 COLOR=$111111 >NIL:

;PEN 2 - RGB 238-238-238 (DEC) | BGR EE-EE-EE (HEX)
c:setpencolor SCREEN="Workbench" PEN=2 COLOR=$EEEEEE >NIL:

;PEN 3 - RGB 68-68-204 (DEC) | BGR 44-44-CC (HEX)
c:setpencolor SCREEN="Workbench" PEN=3 COLOR=$CC4444 >NIL:

;PEN 4 - RGB 119-119-199 (DEC) | BGR 77-77-77 (HEX)
c:setpencolor SCREEN="Workbench" PEN=4 COLOR=$777777 >NIL:

;PEN 5 - RGB 187-187-187 (DEC) | BGR BB-BB-BB (HEX)
c:setpencolor SCREEN="Workbench" PEN=5 COLOR=$BBBBBB >NIL:

;PEN 6 - RGB 204-170-119 (DEC) | BGR CC-AA-77 (HEX)
c:setpencolor SCREEN="Workbench" PEN=6 COLOR=$77AACC >NIL:

;PEN 7 - RGB 221-102-153 (DEC) | BGR DD-66-99 (HEX)
c:setpencolor SCREEN="Workbench" PEN=7 COLOR=$9966DD >NIL:

;PEN 8 - RGB 34-119-51 (DEC) | BGR 22-77-33 (HEX)
c:setpencolor SCREEN="Workbench" PEN=8 COLOR=$337722 >NIL:

;PEN 9 - RGB 119-68-17 (DEC) | BGR 77-44-11 (HEX)
c:setpencolor SCREEN="Workbench" PEN=9 COLOR=$114477 >NIL:

;PEN 10 - RGB 238-204-34 (DEC) | BGR EE-CC-22 (HEX)
c:setpencolor SCREEN="Workbench" PEN=10 COLOR=$22CCEE >NIL:

;PEN 11 - RGB 68-68-68 (DEC) | BGR 44-44-44 (HEX)
c:setpencolor SCREEN="Workbench" PEN=11 COLOR=$444444 >NIL:

;PEN 12 - RGB 187-34-51 (DEC) | BGR BB-22-33 (HEX)
c:setpencolor SCREEN="Workbench" PEN=12 COLOR=$3322BB >NIL:

;PEN 13 - RGB 51-170-68 (DEC) | BGR 33-AA-44 (HEX)
c:setpencolor SCREEN="Workbench" PEN=13 COLOR=$44AA33 >NIL:

;PEN 14 - RGB 68-119-238 (DEC) | BGR 44-77-EE (HEX)
c:setpencolor SCREEN="Workbench" PEN=14 COLOR=$EE7744 >NIL:

;PEN 15 - RGB 204-119-51 (DEC) | BGR CC-77-33 (HEX)
c:setpencolor SCREEN="Workbench" PEN=15 COLOR=$3377CC >NIL: 

Fonts

Install the #?.ttf files to SYS:Fonts/TrueType. Use SYS:System/FTManager to "Install Font" each #?.ttf file which will generate associated #?.otag and #?.font in SYS:Fonts. Use SYS:Prefs/Fonts to change system fonts and SYS:Prefs/Zune to change others.

To achieve our goal we will use the Setup Locale, Input, Zune and Fonts, as well as The FTManager.

Begin

The first step you should do is to get the system to know that we speak and write in another language. What you need to do is to open the setup program and choose Locale country, and list "preferred languages" to put it first and then English. If you want the tab "Time Zone" and select city of residence to set the clock correctly. Of course we save our changes and continue opening the setup program Input. This sets the keyboard language as our beginning. When the language layout was created there was no option to switch to Aros keyboard (layout switching), so to write in the language you had to hold down Alt, something you encounter in other functions, such as AmigaOS 4 and MorphOS. This time working with the team of Aros to create a new keyboard layout to replace the old so we can get rid of the button Alt. For now though let only selected this layout and do not turn the switch on the keyboard.

On the occasion of the article, write in the comments below if you'd prefer to keep both layouts, the new words that are in development and this requires the Alt button pressed.

Installing fonts

In this step you need to download some fonts that can support the Greek encoding in our system. The easiest way is to run the script "Download Fonts" you'll find in the folder AROS: Utilities / OWB. This script downloads from the Internet, and unpacks some fonts for OWB, which is placed under the folder Fonts: TrueType. But as these can only be used by OWB and not the system, which unfortunately does not see. To make them available to the rest of the system, open the program FTManager, you will find the folder AROS: System /. From there select the field "Codepage" option "ISO-8859-7" and list the font "Arial" and "Regular" form in which you must double-click with the mouse. In the window that appears, select the bottom right the checkbox "Anti-aliasing" button and then "Install". Immediately folder Fonts: created files "arialregular.font" and "arialregular.otag", which are necessary in order to see the system font. Do the same steps if you wish for other fonts.

Final stages

After completing the above, open the folder AROS: Prefs / and run the program settings Fonts. In the new window, select the fields "Icons" and "Screen" as the font "ArialRegular" to the size you want. In the field "System" to give "s_courier", which, however, because it is not True Type Font support Antialising, and may seem a little broken. You can also use the CourierNew, if you have installed the above procedure. After you save the changes and open the Zune program settings. In this set the "ArialRegular" font fields in tabs "Windows" and "Groups", and save the changes. Reboot the system. To make sure that the above worked properly run NoWinED, which you will find under the folder AROS: Tools /. If that everything is working correctly you will see the menu and the settings window with Greek letters. You can also write in the language using the button Alt. Second program that you can try, which is fully localized, is WookieChat, which you will find in the folder AROS: Extras / Networking. And in this place all the menu and settings window works.

Wired

Please use Prefs/Network to set up wired, wireless or usb networking 

The top half of the IPv4 Configuration tab on the Network Prefs deals with the network card/usb and the lower half the router part.

Aros network setup diagnostics - why does it not work?

DHCP Settings

Upper part of IPv4 tab

• Click Add on the top right of the Prefs which opens a window called Interface
• Enter Name as net0 (but can be anything as long as it is consistently used in other sections)
• check mark on Active
• select device to be used using the right hand-side gadget of the box where the device name will go
• set Unit to 0
• IP Mode is default set to Get address from DHCP

• IP Mode set to Manual if DHCP does not work
• IP Address of network card = Take the Gateway (router IP address) below and adjust higher the last digit out of a string of four
• Subnet netmask = 255.255.255.0

• click OK

Manual Settings

Lower part of IPv4 tab

• IP Mode Get address from DHCP (default)

• or changing to Manual if automatic DHCP set up does not work
• Gateway (Router Internal LAN-IP) = 192.168.0.1 (D-Link Netgear), 192.168.1.1 (Linksys 3com), 192.168.2.1 (SMC Microsoft), 192.168.1.254 (Belkin), 192.168.123.254 (USRobotics) else check with your router manual
• first DNS = use 208.67.222.222 (opendns) or Gateway number above (to test web browser access to router) or 212.50.160.100 (google) i.e. or whatever your ISP needs you to set
• second DNS = use 208.67.220.220 (opendns) or Gateway number above (to test web browser access to router) or 213.249.130.100 (google) i.e. or whatever your ISP needs you to set

• At the bottom of IPv4 tab, check mark the Start networking during system boot option
• Save and reboot (sometimes Network restart fails, so reboot every time to be sure)

an alternative way is to take the settings from an OS already using the same internet connection. Another connection will have different settings.

e.g. From Windows, ipconfig /all and note down the IP, subnet mask, default gateway, and DNS servers values and put these values in "manually" into AROS Network prefs.

e.g. From Linux via dhcp router have a look at etc/dhcpc/dhcpcd-eth0.info

• for manual input look at /etc/networks (IP or Gateway) and /etc/resolv.conf (DNS)

Please note that all in one routers (wired+wireless) or separate routers may need different settings 

Wireless

Why does it not work?

Shell commands to work out what is happening

We must first make certain you have a Atheros chip inside acting as the wireless wifi option. Open PCITool in Tools directory. Down left hand side are a series of numbers 0.00.0 etc. Click on some at the bottom and hopefully one of them will say Atheros AR5??? or AR242?.

or a RTL8187B which we use Prefs/Trident to check as this one is usb based

There are many similarities with the above Wired set up so please read the above section as well

• open Network/Prefs
• In IPv4 Configuration tab - click Add - enter net0 / active tick / #?.device / Unit 0 / IP Mode = manual (important if default DHCP does not work automatically)

Make sure that any extra network names (e.g. eth1 or net1) should be deleted. If net0 already st previously, change net0 so that it shows associated with the appropriate device name like atheros5000.device or realtek8180.device. Having two entries here will cause sub-net problems.

• Go to Wireless tab and click on "Add" button.
• Insert network name (SSID your wireless network name use wirelessmanager to get it), select right "encyption" that is most likely "WPA".
• Key Type set as "Passphrase". i.e. type in your password for your router (aka access key).
• Unselect (no tick) "hidden" if it is selected, then apply. You may have to tick it if wireless does not work.
• Finally, Save and reboot.

For the best chance of success, set networking to start at boot, and then reboot with the USB adapter plugged in.

Program Error C:WirelessManager

• Test with another OS
• Check that Wifi works before changeover (if possible)
• Check that socket and card are working
• Check if card is too new for laptop (date code on card MMYY blue askey date 2005-2007 etc)

USB Ethernet

Open Network Prefs and in the IPv4 Configuration tag (top table covers your usb stick)

• click Add button
• set Name as net0
• Tick Active box
• enter the usb-ethernet.device e.g. dm9601eth.device, usbpegasus.device or usbasixeth.device use SYS:c/devlist, Scout or trident prefs to get the correct spelling
• set Unit to 0 (which is usual but check the messages from the bottom of the Trident prefs whilst plugging the device in to determine the unit number otherwise)
• IP Mode is set to Get address from DHCP (make sure your router is set right for that)

or manual

• IP Address of network card, i.e. 192.168.0.xx or 192.168.1.xx (xx being greater than 1)
• Subnet netmask = 255.255.255.0
• click OK

There can be sometimes be boot failures when using usb ethernet - plug the usb device in after boot and save the network prefs to make it work again.

Lower part of IPv4 tab covers the router information

• IP Mode Get address from DHCP

or if manual settings

• Gateway (IP Address of router) = usually 192.168.0.1 or 192.168.1.1 but see router manual to make sure.
• first DNS = use 194.168.xx.100 or 208.67.222.222 (opendns) or 212.50.160.100 or 192.168.0.1 (no internet access?)
• second DNS = use 194.168.xx.100 or 208.67.220.220 (opendns) or 213.249.130.100

PPP over RNDIS mobile broadband

Tethering via your smart phone...

Enable and configure at Android --->settings -->>more networks -->>Tethering and portable hotspot

add or name your wifi Network SSID set Security [WPA2 PSK] and password.

and save..

Goto AROS and add your NetWork SSID and password and save..

reboot AROS, make sure your tethering is enabled from android side than magic you have it running..

Same way how you set your home router but this time from your data or wifi via your smartphone or tablet

Network Preferences (Prefs) settings

device usbrndis.device
unit 0
IP mode:DHCP
set "Start networking during system boot" to OFF

In Icaros,edit s/user-startup and add line

addusbclasses > nil:

AROS Screenshot PPP Mobile Prefs

plug in USB cable, enable usb tethering from phone, and AFTER this start arostcp.

make sure DHCP is disabled for both DNS/gateway and for the interface. If the DHCP client is running, it will undo some PPP settings when it gives up (after a few minutes or so)

The advice is different for the new network prefs (Icaros 1.4.1). "Automatic" works for both Ethernet/Wireless and PPP, so you should choose it for PPP now

GUI1

Solving Issues

; $VER: AROSTCP-startnet 1.0 (01/08/06)
; AROSTCP-startnet (c) The AROS Dev Team.
;
Run <NIL: >NIL: AROSTCP
WaitForPort AROSTCP
If NOT Warn
  ; echo "Stack online"
Else
  echo "Wait for Stack Failed"
EndIf

; stop and restart
execute "sys:system/network/AROSTCP/s/stopnet"

Run <NIL: >NIL: AROSTCP
WaitForPort AROSTCP
If NOT Warn
  ; echo "Stack online"
Else
  echo "Wait for Stack Failed"
EndIf

run <NIL: >NIL: wirelessmanager realtek8180.device

echo ${AROSTCP/AutoRun}
echo ${AROSTCP/WirelessAutoRun}
echo ${AROSTCP/WirelessDevice}

ENV:sys/packages/AROSTCP 

ping www.google.com
ifconfig net0

C:wirelessmanager atheros5000.device verbose 

C:wirelessmanager realtek8180.device verbose 

if ${AROSTCP/WirelessAutoRun} eq "True"
Run QUIET "C:WirelessManager ${AROSTCP/WirelessDevice} >T:wifi.log"
wait 5
EndIf

c:wirelessmanager atheros5000.device verbose
Initializing interface 'atheros5000.device:0' conf 'ENV:Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Wireless.prefs' -> 'ENV:Wireless.prefs'
Reading configuration file 'ENV:Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=7)
65 63 68 65 6c 6f 6e echelon
PSK (ASCII passphrase) - hexdump_ascii(len=14): [REMOVED]
key_mgmt: 0x2
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='echelon'


Then it just sits there. Not sure what a normal dump looks like, I don't see anything that looks wrong in the configuration.

Initializing interface 'atheros5000.device:0' conf 'ENV:Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Wireless.prefs' -> 'ENV:Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=7):
65 63 68 65 6c 6f 6e echelon
PSK (ASCII passphrase) - hexdump_ascii(len=14): [REMOVED]
key_mgmt: 0x2
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='echelon'
*** [wpa_sm_init] sm->pmksa=02c66fd4 ***
Own MAC adress: 00:01:36:15:ae:0c
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
Added interface atheros5000.device:0
State: DISCONNECTED -> SCANNING
Started AP scan for wildcard SSID
MLME: starting scan
MLME: scan channel 1 (2412 MHz)
sana2: sending MLME frame


Then it stops. Does this mean the router is not authorizing this NIC?

IRQ 4 (A)

Devs/Networks/atheros5000.device:0
Initializing interface 'Devs/Networks/atheros5000.device:0' conf 'ENV:Wireless.prefs' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'ENV:Wireless.prefs' -> 'ENV:Wireless.prefs'
Reading configuration file 'ENV:Wireless.prefs'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=12):
41 69 72 4c 69 6e 6b 35 39 33 30 30 AirLink59300
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
key_mgmt: 0x2
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='AirLink59300'
*** [wpa_sm_init] sm->pmksa=0224e444 ***
Own MAC address: 00:1f:e1:42:e3:7a
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
[eloop_reg_timeout] Timeout is at 1317686594.160000
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
[eloop_reg_timeout] Timeout is at 1317686595.060000
[eloop_reg_timeout] Timeout is at 1317686604.060000
Added interface Devs/Networks/atheros5000.device:0
[eloop_run] Starting
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
MLME: starting scan
[eloop_reg_timeout] Timeout is at 1317686594.160001
MLME: scan channel 1 (2412 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.193000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.233000
MLME: scan channel 2 (2417 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.253000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.293000
MLME: scan channel 3 (2422 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.333000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.373000
MLME: scan channel 4 (2427 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.393000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.433000
MLME: scan channel 5 (2432 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.473000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.513000
MLME: scan channel 6 (2437 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.553000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.573000
MLME: scan channel 7 (2442 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.613000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.653000
MLME: scan channel 8 (2447 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.693000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.713000
MLME: scan channel 9 (2452 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.753000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.793000
MLME: scan channel 10 (2457 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.833000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.853000
MLME: scan channel 11 (2462 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.893000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686594.933000
MLME: scan channel 12 (2467 MHz)
[eloop_reg_timeout] Timeout is at 1317686594.973000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.013000
MLME: scan channel 13 (2472 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.033000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.073000
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
MLME: scan channel 14 (2484 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.113000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.153000
MLME: scan channel 1 (2412 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.193000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.213000
MLME: scan channel 2 (2417 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.253000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.293000
MLME: scan channel 3 (2422 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.333000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.353000
MLME: scan channel 4 (2427 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.393000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.433000
MLME: scan channel 5 (2432 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.473000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.493000
MLME: scan channel 6 (2437 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.533000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.573000
MLME: scan channel 7 (2442 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.613000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.653000
MLME: scan channel 8 (2447 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.673000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.713000
MLME: scan channel 9 (2452 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.753000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.793000
MLME: scan channel 10 (2457 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.833000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.853000
MLME: scan channel 11 (2462 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.893000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.933000
MLME: scan channel 12 (2467 MHz)
[eloop_reg_timeout] Timeout is at 1317686595.973000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686595.993000
MLME: scan channel 13 (2472 MHz)
[eloop_reg_timeout] Timeout is at 1317686596.033000
sana2: sending MLME frame
[eloop_reg_timeout] Timeout is at 1317686596.073000
MLME: scan completed

"ENV:sys/wireless.prefs" looks like this:
network={
ssid="testadhoc"
key_mgmt=NONE
wep_key0="12345"
wep_tx_keyidx=0
}

scan_ssid=1

ap_scan=1

network={
ssid="YOURESSID"
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP
group=CCMP
psk=YOURPASSWORD
}

filter_ssids=1
ap_scan=2

network={
ssid="REMOVED"
scan_ssid=1
bssid=REMOVED
priority=100
mode=0
proto=RSN
key_mgmt=WPA-PSK
auth_alg=OPEN
pairwise=CCMP
group=CCMP
psk=REMOVED
}

SYS:Prefs/Env-Archive/Wireless.prefs
SYS:Prefs/Env-Archive/Zune/OWB.config
SYS:Prefs/Env-Archive/Zune/global.config
SYS:Prefs/Env-Archive/AROSTCP/WirelessDevice
SYS:Prefs/Env-Archive/AROSTCP/db/Interfaces

Execute SYS:System/Network/AROSTCP/s/startnet

 ping <router-address> e.g 192.168.0.1 (aka inet) or 80.237.146.33 (www.amiganews.de) 
 ifconfig net0
 ifconfig net0 up
 extras:networking/utils/sanautil/sanautil -d atheros5000.device status
 WirelessManager atheros5000.device verbose >RAM:wifi.log
 ;to send the log to RAM disk to be read easier or if detected, 
 Run WirelessManager atheros5000.device >NIL:
 Run WirelessManager atheros5000.device ssid="mynet1" >NIL: 
 C:WirelessManager realtek8180.device unit 0 

Network Basics

Firstly, let's take a look at what your setup most likely looks like, assuming you use a router. See diagram below:

Internet <---------> home router <---------> computer 
-----------external IP------------------internal IP-------------

Okay, so what am I trying to show you with that diagram. A few things. Firstly, the IP address that connects you to the Internet is not the same one that connects you to your router. What happens is that your computer doesn't have a direct connection to the Internet, instead your router connects to the Internet, and your computer connects to the router.

You can see the external and internal IP addresses in these example settings...

• Default Gateway : 76.91.64.1 (external IP for ISP/Internet host)
• IP Address : 76.91.71.184 (external IP for home router)

• IP Address : 192.168.0.1 (internal IP for home router)
• Address = 192.168.0.161 (internal IP for computer)

As you can see, there are two internal IP addresses and two external IP addresses. This is because there is a client/server relationship, effectively one address is for the service (server) and one address is for the device trying to access that service (client).

The server addresses in your case are 76.91.64.1 (your ISP's address, serving the Internet), and 192.168.0.1 (your home router's address, serving your home network). The term gateway applies here, they are your gateway to those services.

Subnet masks are used along with IP addresses to determine which IP addresses are allowed access to a network. I did learn the more in-depth rules about subnet masks once (watched a CCNA vid), but I've forgotten about it. The basic level of understanding you'll need is easy to remember though. A subnet mask value of 255 means that portion of the IP address must stay constant, whereas a subnet value of 0 means any unassigned value up to 255 is allowed in the IP address.

By far the most common subnet value is 255.255.255.0. What this means is that the first three parts of the IP address you use to connect to a service must stay the same as the server/gateway address, and only the last section can change.

So if your router's internal IP address is 192.168.0.1, and the subnet mask is 255.255.255.0, the only addresses that will be allowed to be used on that network are between 192.168.0.2 to 192.168.0.255 (I think 192.168.0.0 is reserved for other uses).

Final point to make is about DHCP (a.k.a. dynamic IP) vs static IP. A server/router using DHCP gives a device that connects to it an address within the acceptable range. It usually starts with the lowest numbered free address, so with your router it'll give the first device that connects to it 192.168.0.2, the next device 192.168.0.3, and so on. Static IP addresses are where you set the IP address you want to connect with in advance.

When using static IP addresses on a router where DHCP is active, it's good to use a high number to avoid conflicts with other devices that are connected to your network, to reduce the risk that both devices will try using the same IP. That's why your current choice of 192.168.0.161 is good, unless you have over 159 devices connected on your current network!

Okay, so what's the next step. Well, if you can use ping, I'd suggest pinging 192.168.0.1. If you get a positive response it means you're connected to your router, if you don't get a response it means the connection between your router and your computer is at fault.

Documentation on configuring the AROSTCP environment further can be found here

Postscript

Best to set Printer Prefs in the Prefs drawer to print-to-file or parallel/usb port

Save document in postscript or convert picture/text to postscript

Print using compatible Ghostscript printer or Postscript printer

GutenPrint

Some work has been done in this aros-exec thread

IPP Printer support

There are no individual drivers yet for HP's Photosmart, EPSON's EPL, CANON's, Lexmark, CUPS PPD, etc

AirPrint

AirPrint is basically IPP (Internet Printing Protocol) combined with discovery via mDNS (Bonjour) or DNS-SD. So basically those AirPrint enabled printers host an IPP server and announce some service (the printer) via mDNS.

Client side (OS) it would only require an IPP client. Basically it's just some IPP headers and you send a Print-Job command with attached PS or PDF data (depending on what the printer understands natively) to the printer on port 631. No driver required. Pretty much any printer can be made AirPrint enabled. Linux usually comes with CUPS and then Avahi can be used to announce the printer service. iOS can then pick it up.

File endings and datatypes

• Check if the file has his own .info icon file with a tool set to open it. IIRC this has higher priority over the def_XYZ.info file association.
• In ENVARC:SYS/def_Text.info or whatever def_ file needs changing, use Wanderer's menu Icon -> Information and change the def_XYZ.info there. If you're on ABIv0 and want it to be applied immediately, you might have to copy it to ENV:SYS/ (or to reboot).
• Identifying file types by file ending is only a fallback. Far better it is to search for magic words, for flac files this would be "flaC" according to this documentation.

For instance, to open PDFs with arospdf not localised in the default drawer of Icaros (Work:Extras/Applications/arospdf) but localised in a custom drawer in AROS. The default tools are defined in the icons in sys:prefs/env-archive/sys e.g. def_PDF.

File type identification is done by datatype descriptors which you can find in Devs/Datatypes. The AROS build system has a tool which creates such datatype descriptors.

Changing of default tools of existing icons is easy as shown above. Adding of new file types is not hard, but needs knowledge of the AROS build system.

Read more here

The enduser way would be to download the attached file, which contained two executables: 1) createdtdesc, to make a new datatype description 2) examinedtdesc, to read/show existing datatype descriptions

use 2 to get an idea on how it things are currenty done in aros by providing this executable a file from the drawer sys:devs/datatypes/ (alternatively you can find the original .dtd files here).

use 1 to make your new datatype. Use the accompanied FORMAT file (also here) to read how to make your own datatype descriptor. use 2 to get hints from other datatype descriptors.

Note: When creating a new descriptor would advise against using the pattern property, but instead use the default pattern of #? and create a Mask that matches your filetype. This requires some research in order to discover how your filetype can be recognized properly. Of course with making something like a descriptor for an ascii textfile, you would fallback to using the pattern (e.g. #?.text as the filetype cannot be determined easily otherwise).

# name - choose wisely and informative. also used for icon's name.
# version - choose as you like as long as it complies with version rules
# basename - the 'root' datatype class. be aware that e.g. it can influence behaviour. for example when choosing binary and using tool multiview in project icon, the file will be viewed as binary file (choosing sound would tell mulitview to view the file as a soundfile). So this can influence the underlying tool being used. Could become messy if users started to modify the tool manually. 
# pattern - This is the file pattern match e.g. #?.text
# Mask - A mask to identify the file. Requires knowledge of the actual file structure. For example 'M' 'Z' for an msdos executable.
# GroupdID - not supported (AROS native) files - use syst as that would be the least intrusive in case an AROS tool/program tries to load such datatyped file.
# ID - In your case, the first four characters of the name at subchapter 1 (in lower case) (or less if name is shorter).
# flags - How the mask needs to be interpreted. In your case would be mostly DTF_BINARY in combination with (wanted or not) DTF_CASE (to tell if mask used letters are case sensitive or not)
# priority - the priority of how the type is handled so that on datatype could have precedence over another? In any case, document tells it to be mostly 0. 

Now that you know each field and what it does (more or less), you write this fields in a text file for your own invented datatype, save it and create the actual dt with the tool in 1. in the end the created dt must reside in sys:devs/datatypes/ drawer.

Then you would create a default icon in sys:prefs/Env-archive/SYS drawer. Don't forget to reboot or copy .info file to ram:env/sys in order to test. also don't forget to set which tool to start f.e. c:lx or dh4:emulators/mycoolemulator

To test, open Wanderer then show all files and doubleclick on a file of type you just created. Alternatively you could use the 'open' command from shell (with file of datatype you just created as parameter).

And as a last note. it would perhaps be welcome to have a program like xicon and/or runprglist for AROS (unfortunately both without source, but something similar could be created for AROS).

Sounds complicated ?

Perhaps... but OS like windows needs a complete registry to be able to do things like this. And yes, i am aware windows has gui tools that does it (more or less) for you (by manipulating the registry). Same could be done for AROS (without integrating a registry in AROS that is ).

Would that suffice ?

red1+2: typos, reformatting.

disclaimer: please note that using these tools can screw up your currently installed support for datatypes when used incorrectly. Do not use if you do not understand what you are doing. Use at own risk.

File Sharing

As AROS knows only a few filesystems (FFS, OFS, SFS, PFS (amiga only), FAT12, 16, 32, Microsoft NTFS (windows), UDF (bluray)). The remaining ones in regular use like MacOSX hfs+, Linux ext2/ext3 and ext4, Haiku BeFS provide a problem in transferring files between each other.

Linux can access SFS partitions but it needs to be compiled. The latest full source are here. It compiled fine with a 2.6.30 kernel in Puppy Linux 4.31.

An alternative, is to use a FAT32 partition. AROS could be installed on to a 4GB USB-key, with 512MB FAT32 partition for sharing, and the rest SFS. It works very well.

An hosted Linux or Windows install relieves some of the problems.

Files could be transferred Sending via TCP network.

Setup ISO images within AROS

Use DiskImage which supports many cd image formats ISO, CCD, MDF/MDS, CUE/BIN, NRG and UIF. To mount CD or DVD images use below....

# Rename your iso 'Unit0' (note no extension).
# Do 'View/All files' on you Aros partition. You should now see a folder called 'Diskimages'. Copy your renamed iso to there. 
(Alternatively, you could type at the shell 'assign FDSK: xxx', where xxx is the location of your iso.) 
# From the shell, type 'mount CD0:' and the iso should appear on the Wanderer desktop. You can now access it like a real disk.

If you are using an IcAros install, the startup scripts are set up to wipe the Diskimages directory on boot, so its worth keeping a second copy of the iso somewhere else. Alternatively, you could set up extra mountlists for additional iso images. I've made a file called iso1 in the Aros:devs directory that contains the following text:

/* Entry for ISO image */

ISO1:
FileSystem = cdrom.handler
Device = fdsk.device
Unit = 1
LowCyl = 0
HighCyl = 0
Surfaces = 1
BlocksPerTrack = 1
DOSType = 0x41434400
Activate = 1
#

Then I just need an iso called 'Unit1' (corresponding to the 'Unit = 1' entry in the mountlist) in Diskimages (or wherever I assign FDSK: to) and to mount I type in at the shell:

Mount iso1: from devs:iso1

Of course, if you create mountlists for ISO2, ISO3:, etc. (with the corresponding change to the 'Unit = ' line) you can have as many isos mounted as you wish. I just call mine ISO1: etc. to distinguish them from the real CD drives.