Can you share with me this minimal ISO with "enought" themes that Appearance cause crash after installation?

With Odyssey I don't enter particular sites, I try to enter sites stored in the "Bookmark" of AROS One, always the same ones, the Guru appears on one of them, but it doesn't always happen on the same site. I created a minimal ISO of AROS One with no data in Development, no data in Extras, and with only 5 themes (the ones that usually went in Guru). Started AROS One Appearance did not go into Guru, then I tried adding the other Themes and Guru reappeared.

The errors in the screenshots are coming from Odyssey itself. What page are you visiting to trigger those? With regards to Appearance, the file system might be getting corrupted during installation - maybe it's somehoe related to number of files. Try these two tests: 1) delete all but 2-3 themes on ISO, install and check Appearnace 2) delete all files in Extras on ISO, install and check Apperance

On WMvare tested the 4 versions of z1.library, all cause a Guru but seems not to be caused by z1.library, I attach archive with the 4 Gurus. Regarding Guru with Appearance, this morning I did 3 installations, also tried formatting first from Wanderer and deactivating Formatting from InstallAROS, Appearance always goes to Guru with many Themes. Confirmation that it is the Filesistem can be deduced from the fact that if I start Appearance from the ISO "without Hardisk" the Guru does not appear.

@AMIGASYSTEM @Amiwell79 You both reported crashes with z1.library when using Odyssey. Since I can't reproduce this on my side, I prepared a few test builds for you. Please let me know which of those versions crash and which don't. [url]https://axrt.org/development/z.zip[/url]

I no longer have a crash when switching off, on AROS One I had already integrated P04 and i8042. Regarding the Filesystem I had suspected it, strange things happen from time to time, for example a Theme works fine again. Or, after forcing a folder to be moved, the folder and its contents disappeared and were not present in .Recycled On Dopus4 opening a folder of a Theme, inside I found another complete folder of another theme, but it was fake because on reboot this folder was no longer present :)

@AMIGASYSTEM @Amiwell79 Continuing with bug reports, you also reported that there is a crash when shutting down. Please try version 64D11 with P04 applied. P04 has a fix to i8042.hidd which should hopefull resolve the issue - let me know.

[quote name=AMIGASYSTEM post=7951]@AMIGASYSTEM It's about the Guru with Appearance, this only happens on my Distribution, on the Build the offending Themes work fine, I'm trying to figure it out, in the screenshot you can see the error shown by "Sashimi", if you have any idea what might be causing it, thanks. [/quote] The error on the screen shot actually comes from file system, not from Prefs/Apperance. You might have a corrupted file system or there is a 64-bit bug in sfs-handler. Try installing your distribution three times to disk (formatting disk each time) and check if the issues happens each time.

[quote name=AMIGASYSTEM post=7951]@AMIGASYSTEM I've noticed other oddities on V11, I recreated a new ISO of AROS One v11 with the new updates included and found an error in the Guru, after some trial and error, the resolution was in front of my eyes, basically the Grub doesn't support the "boot" folder named with the first letter in capital letters "Boot", I renamed "boot" and everything worked fine.[/quote] Most likely grub, having its own file system implementation, expects case-sensitive names.

[quote name=AMIGASYSTEM post=7951]@AMIGASYSTEM BoingIconBar goes to Guru at system startup if one of the Applications placed on the bar has been suposted or missed, sometimes the Guru does not appear, other times the message that the application is missing appears. [/quote] Ok, this sounds as edge case scenario. I created a report for it: [url]https://github.com/deadwood2/AROS/issues/189[/url] Can you share a config for BoingIconBar? Nothing happens when I double click it from Tools so I assume there is some sort of config missing and I don't have idea how to configure BoingIconBar.

@deadwood BoingIconBar goes to Guru at system startup if one of the Applications placed on the bar has been suposted or missed, sometimes the Guru does not appear, other times the message that the application is missing appears. It's about the Guru with Appearance, this only happens on my Distribution, on the Build the offending Themes work fine, I'm trying to figure it out, in the screenshot you can see the error shown by "Sashimi", if you have any idea what might be causing it, thanks. Appearance with same themes work well on AROS One 32Bit and AROS One 68k I've noticed other oddities on V11, I recreated a new ISO of AROS One v11 with the new updates included and found an error in the Guru, after some trial and error, the resolution was in front of my eyes, basically the Grub doesn't support the "boot" folder named with the first letter in capital letters "Boot", I renamed "boot" and everything worked fine.

native mode x86_64 D10 boingiconbar works do not remember prefs/appearance in this moment i cannot run D11 because is very slow in my system and do not have another computer

With the 32-bit release planned this week, we are now getting back to testing 64-bit release. @AMIGASYSTEM You reported two issues earlier: a) BoingIconBar is crashing - I tried running from SYS:Tools it but nothing happens. Is there some configuration needed? b) Your themes are crashing Prefs/Appearance - can you send me a single theme that causes such crash

OK, I hadn't noticed that InstallAROS looks for icons in its own path, on AROS One InstallAROS is located in Utilities that's why. On AROS One I customised the files in a slightly different way to the standard. Regarding "Installer" I preferred to keep InstallerLG which is much more compatible with the standard Amiga scripts and my update scripts. It would be useful to port InstallerLG to v11 64Bit, I tried to compile it but it is too complicated for me.

Hmm, InstallAROS is also located in SYS:Tools and it reads icons from PROGDIR:IA-Icons, so the location of icons is correct.

I have successfully integrated all the updates on the new AROS One 2.8, next step I have to install the fixed parts of the Contrib including the contents of the development folder, and test all the Applications or at least the most set up ones, I noticed a wrong path for the IA-Icons folder, in the Builds this folder is located in SYS:Tools, while InstallAros should be located in SYS:Utilities, so the icons will be shown by InstallAROS.

[quote name=AMIGASYSTEM post=7942]@AMIGASYSTEM - Thanks deadwood, I will do some careful testing, are there any particular changes in this update ?[/quote] I'm not sure I understand. There are a lot of changes in this update - this update is mean to upgrade existing previous release (20220318-1) into next release(20250313-1). So it containes new and changed files from 20250313-1 release which should overwrite existing files from 20220318-1 release. In addition, here are files from 20220318-1 which should be deleted when updating to 20250313-1: [code] Prefs (dir) Env-Archive (dir) SYS (dir) def_ADF.info def_Busydisk.info def_Busyharddisk.info def_FAT.info def_NDOSdisk.info def_NDOSharddisk.info def_PFS.info def_SFS.info Development (dir) Debug (dir) Tests (dir) Library (dir) peropenertest singletest singletest_auto usereltest cunit (dir) genmodule (dir) library (dir) cunit-genmodule-autoopen cunit-genmodule-library cunit-genmodule-relbase Bifteck Libs (dir) debug.library Storage (dir) Networks (dir) e1000_debug.device [/code] [quote name=AMIGASYSTEM post=7942]@AMIGASYSTEM - Question on AROS 68k has something changed? I noticed that the executables are no longer of the "ELF" type, I assume they are "Amiga Hunk", in any case they are not compatible with Amiga OS, if run on Amiga OS3 the "stdc.library" is required[/quote] I believe AROS programs in general are not expected to run under AmigaOS even if they are converted to AmigaHunk file format. Only a handful of programs, needed to boot a floopy and load AROS ROMs into RAM are expected to run under Amiga original ROMs.

Thanks deadwood, I will do some careful testing, are there any particular changes in this update ? Question on AROS 68k has something changed? I noticed that the executables are no longer of the "ELF" type, I assume they are "Amiga Hunk", in any case they are not compatible with Amiga OS, if run on Amiga OS3 the "stdc.library" is required

And here is last part of release, an update package that will change 20220318-1 into 20250313-1 [url]https://axrt.org/development/tmp/AROS-20220318-1-U3-any-i386-update.zip[/url] If you run into issues applying this update, let me know. If no major issues are found, the release will be made offical by end of this week.

I have to change computers for aros x86_64 even though I have an old laptop where it works for me