I read the Protrekkr error message on my laptop well and it concerns the Gallium.hidd on the HP Z400 it works though

but nvme m.2 pcie works?

That's relativelly recent development by Kalamatee. I haven't had a change to try how well it works.

I will make an attempt thank you

FYI: In January work on the release will slow down due to other topics I need to focus on. Hopefully we can resume in February. Right now "end of Q1" still looks like a reasonable time for completing this release.

Don't worry deadwood, thank you anyway for your work!

many thanks deadwood

FYI:

If you are re-compiling software for 64-bit, please do not port software using SDL at this time. There was an issue detected when having more than one SDL program running at the same time is causing the first program to stop responding. This can potentially be a serious bug. I will look into this in coming days.

Hi. Coming back from time to time. What is the latest stable version of AROS ABIv0? And what the best I could use today to update Icaros Desktop?

Are there obsolete files that must be removed?

thank you and sorry for being no active.

kind regards

p.bes

Paul, in a nutshell you must start by deleting or replacing from Icaros all software that makes use of libraries incompatible with the C library (those listed in the link), Core and Contrib binaries must be replaced 'all', and third-party software only those that use library.

I advise you to read the attached post and subsequent ones

https://www.arosw...#post_3281

After this you can update Icaros with the latest ABIv0 Build and 32Bit Contrib, you can find them here:

https://axrt.org/...loads-aros

Hello Paolo,

Nice to see you back. I think what AMIGASYSTEM wrote is a valid approach. In short, due to change of internal C library you need to replace all Core and Contrib software. There was also a few 3rd party programs on the Archoves which used that internal library (but should not have) and these are now re-compiled to use new library and re-uploaded to archives.

If you run into issues when updating let us know though I'd suggest creating a new, specific thread. This thread already mixies 32-bit and 64-bit work so adding Icaros update on top will make it confusing.

welcome back Paolo

hello Paolone

The issues is now solved:

https://axrt.org/development/SDL.library.x86_64.zip

It turned out be less seviere problem than I expected and existing SDL software is fine. Also porting SDL can now resume. This version also no longer opens gl.library at start, but only when requested. This means 64-bit AROS SDL games that don't use 3D can now be run under AxRuntime.

Ok thanks deadwood, now ProTrekkr the SDL demos also work on Aros Native on WMware, now I can compile demos on Native which is much faster !

Note: this is an inportant update.

There was a bug in native AROS kernel copy memory routine which was causing data damage during copy (around 1 byte for several MBs of copied data). It affected CPUs with AVX instructions (all Intel and AMD processors starting from 2011). The bug was complex, but how it could express itself (few of many cases):

1) program loaded from disk was sometimes working and sometimes crashing, becuase when loading program code was damaged
2) program installed on disk was corrupted during installation and was causing issues
3) program compiled (on native) could have been damanged during compilation and misbehave

Due to how many elements this issues could affect, there is no update package. You are requested to re-install your systems from new ISO (remember you need to boot from ISO to have fixed kernel copying files to disk). If you are unsure whether you are using fixed kernel, do 'version kernel.resource' from Shell - you should get version 4.0.

If you have programs which are "unstable", please retest under fixed kernel. If those programs were compiled by you on native and are still unstable with fixed kernel, please re-compile them. Programs from "contrib" and "ISO" are safe from this issue as they are cross-compiled on Linux (though they might have become damanged if extracted/copied under native). Hosted AROS is also unaffected.

This was a really complex bug to track and fix and I'm hoping going forward native 64-bit AROS will be much more stable. Please don't report anylonger issues on 64D10 or earlier builds - test only on 64D11.

https://axrt.org/development/AROS-20250206-64D11-pc-x86_64-boot-iso.zip

64D11 was tested for boot, installation to disk, playing video in MPlayer and playing YT with Odyssey on following configurations:

QEMU 8.2.2

"pc" template - (8GB RAM, 2 CORES, VESA, IDE, SB128, PCNET32)
"q35 template - (8GB RAM, 2 CORES, VESA, AHCI, SB128, PCNET32)

VMWARE 16
Other64 template - (1GB RAM, 1 CORE, VESA, IDE, SB128, NO NETWORK)
Other64 template - (1GB RAM, 1 CORE, VESA, AHCI, SB128, NO NETWORK)

VirtualBox 7.1.4
Other64 template - (8GB RAM, 2 CORES, VESA, IDE, HDAUDIO, PCNET32)
Other64 template - (8GB RAM, 2 CORES, VESA, AHCI, HDAUDIO, PCNET32)

in native mode the system is very slow I start for example mplayer and then owb and everything goes slow music hiccups owb struggles to load pages

already at startup it is slow when starting wanderer

What CPU/motherboard are you using?

After boot run AROS:Tools/Debug/Sashimi. Does it show some output? Start mplayer -> Does it show some output?

I'm using my hp z400 with d-10 no problem with this release everything is slow I can't make a video