a musician blog | amiga aros & music related
This applies to all version of Icaros starting from 1.5.2.
Read this first : https://sourceforge.net/projects/janus-uae/files/janus-uae/janus-uae%20v1.4/ (download and extract the archive, it contains a “coherency guide” to help understanding and configuring janus-uae as a service for icaros).
This applies to versions :
There is not point using older versions.
http://www.icarosdesktop.com/icarosfiles/IcarosDesktop_manual.pdf
https://en.wikibooks.org/wiki/Aros/User/AmigaLegacy
other docs are listed inside the sections below. Continue reading “icaros installation advices, tip&tricks”
After a fresh installation of 2.1.0, 2.1.1, 2.1.2 or 2.1.3, you try to save SMB (samba) share mount parameters on your ahci/sata/ata drive, and you get a crash.
[Note : is it coming from the fact it is a guest only samba share ? Must try to configure an AROS samba share with username/password]
Continue reading “troubleshooting icaros SMB crash “exec housekeeper””
I had a problem this morning when booting my machine. Screen stayed blank at the first step of the boot, instead of displaying the grub screen. This comes from the dma on my computer. So I disabled dma with “nodma” option in grub, now. I don’t have anymore problems.
So, here is the way if your system don’t boot up in case of a messed up grub.
Test your hardrive is still ok, booting with an installation DVD or pendrive.
If the hard drive still appears in wanderer, so it’s is certainly you did something wrong with your grub.
Aros comes with a nice little utility that allows us to reinstall the grub : http://aros.sourceforge.net/documentation/users/shell/install-grub2-i386-pc.php
First we have to know the device and the unit of your hard drive. Right click on the icon and get to “Informations”. Here are the device and the unit. For me it is : ata.device unit 4.
Open a shell window, and type (change device and unit so it fits your system config) :
for regular icaros 1.5.2.2 (and previous) :
install-grub2-i386-pc DEVICE=ata.device UNIT=4 GRUB=DH0:boot/grub
for icaros 1.5.2 WIP5 (and future releases) :
install-grub2-i386-pc DEVICE=ata.device UNIT=4 GRUB=DH0:Arch/pc/grub
Restart, stuffs should have been resolved.
So you have an ISO file and want to access it without having to burn a DVD ?
Here is what you have to do :
– copy the file (iso) to the drawer “AROS:Diskimages”
– rename it as Unit0
– add this into the file AROS:Devs/Mountlist
ISO:
FileSystem = cdrom.handler
Device = fdsk.device
Unit = 0
LowCyl = 0
HighCyl = 0
Surfaces = 1
BlocksPerTrack = 1
DOSType = 0x41434400
Activate = 1
– open a shell window and type :
mount ISO:
In regular IcAROS 1.5.2.2, the device doesn’t show up in Wanderer, but you can access it using “ISO:” in a shell, or in DOpus.
Tadaaa.
Introduction :
Yepa, that’s fantastic : DOpus 5.9 has finally been released, 15 years after the 5.89.
http://aros-exec.org/modules/news/index.php?storytopic=4
That’s really fantastic, and I can hear the sounds of many people saying, I want it running on my IcAros !
There are two main ways to get DOpus running on IcAROS :
– Install DOpus package on the official IcAROS 1.5.2.2, and update core files : this is what I do in this article
– or Install IcAROS 1.5.2 WIP5 : WIP5 tuto there.
Both ways have good and bad points :
This article is about those software versions :
– Odyssey Web Browser (OWB) v 1.16.2
– IcAROS 1.5.2-2
I have problem surfing in https with OWB. It says that he has a problem with the SSL CA certificate.
This can be an error 60 :
Unable to connect to "https://www.facebook.com"
Error 60 : Peer certificate cannot be authenticated with known CA certificates
or maybe an error 77, like this :
Unable to open https://www.facebook.com/....
Error 77 : Problem with the SSL CA cert (path? access rights?).
Continue reading “OWB problem with the SSL CA cert on IcAROS”
Sharing files over the network is something like an obligation nowadays.
I personnally don’t like Windows, so I won’t speak about this side. I prefer the dark side : linux, especially ubuntu (here 12.04LTS). Anyway, samba is samba, so it should work with every linux distrib.
As we speak about computering @home, we will stay in a VERY SIMPLE config.
So, we have for this example :
– One machine running IcAros 1.5.2-2
– One machine running Ubuntu 12.04LTS
– let’s assume the ubuntu samba server is called “HADES”,
– in a WORKGROUP called “PHLEGETON”,
– with the IP adress, let’s assume it is “192.168.173“. Ofcourse, you must change this to fit your ones.
– let’s assume the path to share is “/media/data”
– let’s assume the share name will be “styx”
We also have a local user. Let’s assume it is “jess”. Continue reading “share over the network between IcAROS and Ubuntu”
I gives this to you to explain how you can play with graphical modes (cf this post) and switch between VESA and NATIVE modes under IcAROS.
The first menu entry is begining at the line menuentry “Icaros Desktop”. The first entry in the list is the one that will be used by default.
There is no driver given in the command line (no “nouveau.hidd” or VESA appearing), so it takes the last config saved inside IcAROS. If you want to be sure to boot in VESA mode your have to write down something like “vesa=1600×1200@60” in the boot line.
You can change the background image with the “background_image” option. Why isn’t it as simple in linux ?
Continue reading “my IcAROS /boot/grub/grub.cfg file (only icaros before 1.5.2)”
VESA is perfect for compatibility with ALL the gfx cards. For more informations about VESA : http://en.wikipedia.org/wiki/VESA
But it is slow, and Warp 3D is badly supported.
Also, you can have problems changing graphical modes (need to restart the comp’), or even finding a mode that fits your needs and your screen (for me, I had issues with my wide 22′ monitor)
To know the list of VESA modes supported by the graphic card, on the grub screen type “c” to get into the “grub command line”, then type : Continue reading “playing with graphical modes inside IcAROS (VESA/native nouveau.hidd)”