Deadwood, there is an old problem with some binaries when executed from an icon, when the ‘Tool and CLI’ parameters are not present in the tool types icon.

For example, if you try to execute the numeric binary files inside the Bitmap Font folders without the aforementioned parameters, you will receive a Guru, see screenshot.

Question: Are the Datatypes Font and Bitmap_Font descriptors duplicates?

I don't quite get it - why would you want to execute font files?

As for Font vs Bitmap_Font datatypes - the Font datatype was removed and then two new one were added Bitmap_Font and Outline_Font.

EDIT: unfortunatelly I have no way of "removing" a file in an update package.

I don't want to run font files, it was just an example to point out this issue when clicking on some ‘Dos’ binaries that are incompatible with Wanderer.

Regarding font data types, I had already removed this ‘duplicate’ descriptor from AROS One, I reported it because it is still present in the latest builds.

There is a new Nightly build which I would like to ask you to re-test.

[url]https://build.axrt.org/download/builds/AROS-ABIv11/pc-x86_64-20251017-125050.tar.gz[/url]

Please read this post [url]https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1707#post_9254[/url] before proceeding.

History:
- integrated ~60 changes from Kalamatee end of September period

Areas to test:
- There were some internal changes to AROSTCP which should have no impact on existing software - check if network software from archives/Odyssey still works correctly

Everything seems to be working fine on VMware at the moment.

As in previous demo builds, I encountered an old problem with the Palette application: once launched, the edges of the window turn pink, as shown in the attached old video, but occasionally this also happens with other apps!

https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1707&getfiles=1148

Looking fine so far on my native i5 machine; wifi looks to be working well

Cheers,
Nigel.

P.S. with the new developments in arostcp and realtek8180.device authentification through DHCP is much, much quicker

It works, I tried Amitube

The new lasso works correctly on VBox and VMWare, but graphic artifacts appear on real hardware.

I checked it on two devices
- ASUS P8Z68-V LX
- MSI H81M-E34

and on both there are graphical artifacts when selecting and rotating the mouse wheel, as can be seen in the video:
https://youtu.be/pLtCqQ_xJyg

Can anyone confirm that they have the same glitches on their hardware?

Just had a crash with the new build - please see attached. I was using OWB at the time and this error was preceeded by a curl thread error, alhough I didn't record that one as I thought OWB is not the focus at the moment. This was on my i5 laptop.

Cheers,
Nigel.

Just had a crash with the new build - please see attached. I was using OWB at the time and this error was preceeded by a curl thread error, alhough I didn't record that one as I thought OWB is not the focus at the moment. This was on my i5 laptop.

Cheers,
Nigel.

That error looks like an effect of earlier error. When the curl error happens again, please capture it

There is a new Nightly build which I would like to ask you to re-test.

[url]https://build.axrt.org/download/builds/AROS-ABIv11/pc-x86_64-20251107-175100.tar.gz[/url]

Please read this post [url]https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1707#post_9254[/url] before proceeding.

History:
- integrated ~30 changes from Kalamatee from October period

Areas to test:
- a number of stability fixes have been done to sound.datatype, it should now not crash when playing two sounds at the same time

Build 20251107-175100 seems to work well, no problems encountered on VMware.

I would just like to point out that the window bar is still coloured “pink” after running the “Palette” Application.

Quickpart is still read-only!

[quote name=AMIGASYSTEM post=10033]@AMIGASYSTEM

Quickpart is still read-only![/quote]

Well, you'd have to talk to Kalamatee about this if you wish it to be more functional.

There is a new Nightly build which I would like to ask you to re-test.

[url]https://build.axrt.org/download/builds/AROS-ABIv11/pc-x86_64-20251109-032703.tar.gz[/url]

Please read this post [url]https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1707#post_9254[/url] before proceeding.

History:
- integrated ~40 changes from Kalamatee from October period

Areas to test:
- does it still boot on your hardware
- does mouse and keyboard still work (especially PS/2 devices)
- changes to muiscreen/muimaster for public screens previously tested by NathanH are now integrated
- changes to ntfs-handler, check if there are no regressions

Tested on ‘WMware’ the new Build 20251109-032703, tonight I will try it on Native!

- boot -> Works well
- mouse and keyboard -> Works well
- changes to muiscreen/muimaster (I don't know with which software and how to test it)

- ntfs-handler -> Copy from NTFS-AROS if you use Wanderer Copy Blocking
- ntfs-handler -> Copy from NTFS-AROS if you use Dopus4. Copying works well
- ntfs-handler -> Problem also present in previous versions. If the hard disk is initially mounted on VMware, volume ‘L’ is requested and mounting fails

With Build 20251109-032703 Pendrive Live, I ran a test on my Samsung PC R730 laptop with Win10 installed:

- boot -> Works well, Safe Mode 2 starts up on VESA 1024x768x240 BGR0 screen (Excellent)

- boot -> To start in Default Mode or Safe Mode 1, I had to add ‘noacpi’, which I also did with the reference Build.

- ntfs-handler -> System startup error, probably a conflict with the internal NTFS hard disk where Win 10 is installed

With the reference build (AROS One 64) there are no problems with ntfs-handler, NTFS partitions are detected on Wanderer and it is possible to copy data from the NTFS partition

I also successfully tested the version of Dopus4 where I removed “trackdisk.device” from the binary, no Guru after copying a lot of data from the network share

Ok, thanks for the tests. So essentially you are saying there is a regression in new ntfs-handler?

At least in my tests, there is a regression on both VMware and Native. Remember that ‘ntfs-handler’ is read-only, while ‘ntfs3g-handler’ allows both reading and writing. ‘ntfs3g-handler’ does not currently exist in 64-bit.

There is a new Nightly build which I would like to ask you to re-test.

[url]https://build.axrt.org/download/builds/AROS-ABIv11/pc-x86_64-20251110-021008.tar.gz[/url]

Please read this post [url]https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1707#post_9254[/url] before proceeding.

History:
- integrated ~50 changes from Kalamatee from end of October till "now"

Areas to test:
- does it still boot on your hardware
- does mouse and keyboard still work (especially PS/2 devices)
- does cold/warm reboot work the same way or better then previously
- are ahci/nvme disks still working are previously or better
- is vmware video driver still working as previously