Thanks for the update

@derfs
Quote:

Very interesting... I once wrote my opinion on AI. Do you profile your knowledge to AI only for yourself or for others (paid versions and for corporations - any provisions in the license agreement)?
I'm just asking out of curiosity

@kas1e

https://github.com/derfsss/dopus5-os4/releases/tag/v5.93beta1

@kas1e
Quote:
Yes, it works quickly. You can easily copy/modify/delete files on both systems and it will be visible immediately. There are no space limitations. The only limitation is the disk capacity on your computer/host.
I recorded a video for you because maybe the last one was not clear enough. “SHARED” is my folder on MacOS $HOME/Dowload.
I no longer use “-drive file=fat” under QEMU AOS4 - it was terribly outdated and had a lot of limitations.
video - > https://youtu.be/kfIYRTeHaOc

If you need any other information, let me know.
ps
The command line for Linux and PEG2 for Virtio9PFS-handler also works on macOS.

@derfs
Quote:

With grok it was the same just only exception that i had always to repeat the same and the same because sessions is small, context window is small, and once it start to get how to do os4 code, memory of context end, it start act, and you start from begining, so i end up with just some small tasks which fits well into.

It's still quite cool how far ai come today. It's of course not autopilot, but helps very much, especially if you can code, and stuck sometime on something which crash your head.

@kas1e

Each AI agent has its positives and negatives, but I have found with Claude (especially the new Opus 4.6) that it is easier to train it with the correct way to make a program for AmigaOS4. Especially libraries and devices.

Even with this, it is still mostly about the initial prompt you give the AI agent, as it needs to cover all the points you want it to hit, and make it create documentation recording what it has done and what its going to do.

I use VScode with the Claude plugin, but the people that pay for the highest level use the Claude API directly otherwise they would never use up their allotted quota.

What you don't see is the last few months of testing and trying things out to get the Claude 'memory' to a point where it has learned a lot of things and I don't need to teach it from nothing every time.

Hi everyone,

A bit delayed, but here is the AmigaOS 4 Monthly Roundup for February 2026.

https://oldschoolgameblog.com/2026/03/ ... ly-roundup-february-2026/

Hope you'll enjoy the news!

Thanks everyone! Changing the CMOS battery worked a treat. The old one was down to 1 Volt!

Thankfully I didn't have to re-enter any settings after the battery change either.

@smarkusg
Still can't get myself to test, but is it works as expected? I.e. you can copy/modify/delete files in realtime from both os4 and from linux without restriction ? No size limitations of shared partition, and no speed issues ?

@derfs
Btw, you say you use claude ai, is it anyhow better than others ? I just used before grok and gpt, but for simple things like to fix some of code, or find for errors, but today tried claude ai (web version, just a chat window), and it write me quite good code from start (with usage of interfaces, correct allocvectags() instead of deprecated allocvec() , for grok and gpt i had to explain it before). Probably you use it from some IDE where you point on the SDK, and claude make a code based on the SDK examples ? Because i see your AmiBench tool quite rich on reaction stuff (buttons and co) and looks pretty correct .. (while grok and gpt wrote pretty sucky reaction code by default).

@derfs
On QEMU Peg2 under Linux, the Virtio9PFS-handler works for me in this way.



Here is Virtio9PFS-handler and virtioscsi.device on Linux QEMU PEG2
*) The vtlspci command comes from a package by Falke, who is working on QEmu VirtualVGA Device.

@kas1e
Quote:

Thats correct on Windows, but if you use the WSL2 subsystem on Windows then you can get it to work as its essentially linux.

P.S. virtfs is also available on macOS.

@msteed

Thanks for the feedback - please can you test https://github.com/derfsss/AmigaDiskBench/releases/tag/v2.5.4 to see if it solves your issues? The 2nd crash will probably still happen for now.

On the Benchmarking tab, if you right-click on a test name you can now use the menu to see a full description of that test.

@derfs

First, thanks for a very nice looking, full-featured and useful program (though it would be helpful to have a bit more detail on what the different benchmark tests do, so one knows what exactly is being benchmarked).

However, I get a recoverable DSI when I run the two most recent versions of AmigaDiskBench (v. 2.5.3 and 2.5.2) on my X1000 running FE Update 3. The DSI occurs soon after I start the program, apparently while it's scanning the drives. I can click on 'Ignore DSI Errors' and the program then appears to run normally (but see below for a different problem).


There is also a second, more fatal, crash. Because it's very similar to a crash in the most recent version of Rave, I posted the details of this crash in the Rave thread, where the problem has been discussed at some length.

@trixie

The latest version of AmigaDiskBench (v. 2.5.3) seems to have a very similar bug as Rave: When I run the program, select the Disk Info tab, and then click on "Fixed Drives/sb600sata.device" in the listview the program stops responding, along with much of the OS. (There is a recoverable DSI when I first run the program; that DSI doesn't seem related to the lockup bug.)

Like Rave, the crash happens when the program is working with ReAction gadgets, and the stack trace shows the crash occurs during a series of nested calls to the layout.gadget, followed by a call to the button.gadget. The first part of the crash log, including the general info and the register dump, seems to go missing. But what remains is enough to get an idea what was happening when the crash occurred:


The exact code where the crash occurs is different than Rave. There are some other differences as well: unlike Rave, the crash occurs under FE Update 2, as well as under Update 3. And unlike Rave, the crash occurs even if AmigaDiskBench is run from the RAM disk. While the crash occurs most of the time, it occasionally doesn't, unlike Rave where it is always repeatable. Since I have only an X1000, I can't say if the crash only occurs on the X1000, as it does with Rave.

AmigaDiskBench isn't your responsibility, but the fact that a very similar bug occurs there is some evidence that it's not caused by your code doing anything wrong, and may in fact be a system problem of some sort. And perhaps the differences between the Rave crash and the AmigaDiskBench crash provide some clues as to where the problem lies.

I don't use the mui file requester since many years because of some problem it gave me that i could not live with.

I should ofcourse have reported it but never got around to do so.

Does anyone know what kind of problem it gave and have it been fixed?
I can't remember what it was.

@bennyQuote:

Is there a timeline for that?

@n3m3

Problably when Mos 3.20 is ready

@C16Oli

In MUI you can choose what buttons shall be shown in the Window-border. Snapshot is the option that you are looking for.

@Tuvok

but names are strings and no numbers. they will be sorted alphabetically.
so this is the expected result.

regards...
michael

@Tuvok

next is 100,000 mark