FWIW - i don't know if this is interesting to the group but i'm pretty happy i just got an AROS environment running on Linux x86_64 using github/deadwood2 setup and Claude directing me. I have a Workbench window!
I was an old time Amiga user and came across a video AROS on a RPi3 last week. That prompted me to investigate more. I always wanted to write a BOOPSI program, and now I can, and I'll be able to use a coding agent to help too. Wow - This is cool.
Great to see you picking up development! I actually prepared a setup to coding agents that might be intersting for you, check it here: https://arosworld.org/infusions/forum/viewthread.php?thread_id=1933&rowstart=0#post_11881 It using diffent coding agent (opencode) but must of the things are transferable to Claude Code I think. Good luck with your coding endevour!
Welcome! I'm glad you successfully installed your AROS test system. :-)
It took me a month to setup my 64bit cross compiler on Ubuntu 24.04 but I think I'm a slow learner!
I also purchased a Raspberry Pi 400. It arrived a few days ago. I look forward to compiling some of my own software to test on AROS Pi.
That's what I call it, for lack of a better name. I have some small graphics programs that I'm going to re-write and compile for Amiga 68k using the same code for AROS. I'd like to compile them for Raspberry.
I suppose they are written in BOOPSI code. It's the traditional Amiga code that uses intuition windows, menus & Datatypes to use for graphics ops.
Anyhow, that's a long-worded "Hello'.
Edited by miker1264 on 05-09-2026 13:23, 1 month ago
Latest update installed to my i5 laptop; no issue with boot or starting OWB.
My USB audio adapter arrived in time to try with the new release. It's recognised bu Posiedon, bound to usbaudio.class and is visible in AHI prefs. Unfortunately, it fails to produce an audio output on pressing 'Play a test sound', with Trident reporting an endpoint stall. It's the same behaviour in both USB2 and USB3 ports. I've attached the Trident log in case that is of any help.
Cheers,
Nigel.
Edit: More tests:
If the device is plugged in before boot into a USB2 port, it works.
If the device is plugged into a USB2 port after boot, it does not work.
With USB3, neither plugging in before or after boot works.
Saying that, that fact it works at all is really good news. No need to stress if a laptop has supported audio or not, since if the latter there's now the USB audio option.
Edited by ntromans on 05-09-2026 19:34, 1 month ago
Looking at code I don't see how this can be stable, unless it defaults to running all tasks on same core. Does it?
For example there are certain (legal/documented/official) ways to do things that require Forbid()/Permit() protection. Like closing window safely if msgport is shared among multiple windows. Like Zune/MUI is doing for example in workbench/libs/muimaster/classes/window.c. If the Forbid() in there only blocks tasks on 1 core, but not all cores, then that code is not safe in SMP as Intuition InputHandler (input.device task) from other core could still send messages to the port.
Also task exit code/procedure often relies on Forbid() to block all tasks from running. Otherwise it is not safe.
Looking at code I don't see how this can be stable, unless it defaults to running all tasks on same core. Does it?
For example there are certain (legal/documented/official) ways to do things that require Forbid()/Permit() protection. Like closing window safely if msgport is shared among multiple windows. Like Zune/MUI is doing for example in workbench/libs/muimaster/classes/window.c. If the Forbid() in there only blocks tasks on 1 core, but not all cores, then that code is not safe in SMP as Intuition InputHandler (input.device task) from other core could still send messages to the port.
Also task exit code/procedure often relies on Forbid() to block all tasks from running. Otherwise it is not safe.
It would be best if you take it up with Kalamatee. He is not a member of this forum though. He can be reached via linen/slack channel. You can find links to this channel in developer section of www.aros.org.
Edited by deadwood on 09-09-2026 00:43, 1 month ago
@deadwood
It seems that on AROS 64-bit, DiskImageGUI doesn't support .cue CDs; the 32-bit version works—see screenshot. I used the same configuration and the same .cue file.
Could you tell me how I should name the def_icon files for .cue CDs and audio CDs? AROS assigns ugly, corrupted icons—see screenshot.
Can you explain what exactly happens with 64-bit version? It only has a few more changes compared to 32-bit and they should not impact image support at first sight.
As for default icons for AudioCDs - I don't think those are handled via def_icons. def_icons handle file associations and those whole disks. I think disks are either handled by icon.library itself or Wanderer and it looks like code for handling AudioCDs is missing from either of them.
64-Bit:
.cue files are not supported; Data+Audio CDs and Audio-only CDs are not mounted.
PlayCDDA cannot find tracks; if you eject the CD, AROS crashes, sees screnshot
32-Bit:
The .cue file is handled perfectly; Data+Audio CDs and Audio-only CDs are mounted correctly.
PlayCDDA plays tracks and ejects the CD correctly, see screenshot
OS3
This concerns the Icons; on OS3, both Data+Audio CDs and Audio CDs are supported.
On OS3, depending on the type of CDFS, it can even display the tracks!, see screenshot
@deadwood - Ok, I understand now. Thanks for explanation and screenshots.
Are real Audio CDs (real CDs in CDROM, not .cue images) detected and playable on 64-bit AROS?
On 68k I managed to play Audio CDs
You mean physical Audio CDs on nightly 68k AROS? Which tool did you use? What icon does a physical Audio CD get when inserted? (can you make a screenshot?)
We're talking about CD images, not actual physical CDs.
CD images don't work on AROS 68k either.
I'll add that if you're testing AROS 68k, you need to disable CD support in WinUAE!!!
We're off-topic—start a new thread if you want to talk about AROS 68k.
@deadwood
Physical CDs work on AROS 64-bit v11, but PlayCDDA does not work
AROS 64-bit associates one of my def_Icons with physical CDs (unknown volume, no file access); see screenshot
It's actually important for me to understand if CD images (.cue files) can be mounted under AROS ABIv1 and whether Audio CDs can be played there - since AROS 68k is ABIv1 then it can be used to report on those things (like x86_64 or aarch64). If they can be played then it's a possible regression in my tree or not synchronized new feature.
You can view all discussion threads in this forum. You cannot start a new discussion thread in this forum. You cannot reply in this discussion thread. You cannot start on a poll in this forum. You cannot upload attachments in this forum. You cannot download attachments in this forum.
. I'll give it a try on ABI1; I presume the standard version rather than SMP?
AMIGASYSTEMDistro Maintainer