deadwood On the Build Demo folder, there is "IconScale" which allows you to set the size of all operating system icons, just put IconScale" in the User-startup or startup-sequence.

The problem is that the second side of the icon is corrupted, see screenshot, it also slightly worsens the quality of the icon.

How IconScale works is mentioned here: https://en.wikibo.../User/Docs

Well, if someone implementes it then I'd say yes - I don't see technical reasons for not having that.

On the other hand I personally like the large icons - it kind of reminds me how things were on Amigas

@deadwood

Is it possible in the future to have automatic resizing of icons "in percentage" on Wanderer, as happens on OS4 and MOS?

I ask this in order to have the icons always the same size, even when some developers use very large icons! This is to avoid a mismatch between the distances between the icons!

I could do it via Installer, although I might miss something about the changes and corrections I made !

The problem is that users if they have changed paths or moved something, the update via "Installer" might fail !

Eventually next time I organize is I keep stored separately all the changes !

BTW, for AROSOne 2.5, are you planning to release an update package so that people don't have to re-install?

Ok thank you !

You can use either - they are built from the same source. The difference is size comes from some debug information which contains part of the build directory path (which is different between ISO build and contrib build)

deadwood is about the archive "AROS-any-i386-contrib.tar.bz2 v20220318-1 " which is located in "https://www.axrt.org/downloads-aros", land two libraries are located in the Libs folder.

The libraries are different in size from those included in Build AROS-pc-i386-boot-iso.zipper v20220318-1

Can you provide more context of your question? Which specific files do you indicate as "contrib" and "Build" - can you provide links to them?

What I released was just an update archive: AROS-20220318-1-U1-any-i386-update.zip. There is no contrib there.

deadwood, in the contrib there are two libraries (freetype2.library and popupmenu.library) which have a different size from the Build, are there any differences, which one should be used?

many thanks deadwood

Update 1 is now officially released. For binaries and change log check these locations:

https://github.com/deadwood2/AROS/releases/tag/ABIv0_20220318-1
https://www.axrt.org/downloads-aros

Created bug report for this issue: https://github.com/deadwood2/AROS/issues/144

deadwood, is it possible to correct the graphic artifacts when dragging an Icon ?

If you try to drag a native AROS Icon but also a DualPNG Icon, around the Icon you notice black graphic artifacts, see screenshot

I specify that on AROS 68k the problem does not exist, especially the DualPNG Icon when dragged and clean and clear !

I don't find any anomalies

Ok so I can proceed to build the new AROS One 2.5.

Regarding the USB image I will probably still use Rufus v3.2 and VHD format, unless in the meantime the new version of Rufus 4.5 will be released (like v4.4 It will only work on Win10/11).

Meanwhile, yesterday the developer of Rufus informed me by e-mail that he has finally located the Bug that I had reported to him on the AROS One Images with Rufus v4, referred to by him as "benign error, Read error: [0x0000001B] " and that it will be fixed in the next version.

Thanks.

There are no more changes planned for U1 update. Unless some problems are found, the archive above will be the official release.

deadwood, actually I had already tested part of these updates, anyway everything seems to be fine !

In the Build you are going to release will there be more new update ?

Ok, corrected.

@deadwood link don't work ?