deadwood When I run the update (InstallerNG) on AROS One Hosted Linux 64Bit, I get a Guru (even with the reference build), see screenshot.

On Native vMware, no Guru, the update (InstallerNG) works fine and updates the system!

Please prepare me a smallest installation package that triggers this. Looks like something related to creating icon for directory.

In fact, there was a problem in the installation script. In practice, the native installer created icons for all system directories that did not have an icon :) (which is really strange; I need to study the script I used in the past for the update without having this problem).

I have now replaced the script, and the installation works perfectly even on AROS One Hosted, with no icons being generated!

If you want to test the update, I can send it to you in a PM. On AROS One 1.0, installerNG does not exist, so in order for the installer to work, I included it in the same path as the update folder.

I think I've discovered who created the icons:

In the script there was this sentence [b](infos)[/b]:

[code]
; Update Aros One v1.1 x86 64Bit v11

; Generated by InstallerGen 1.5!

(complete 0)
(set @app-name "Update AROS One 64Bit v1.1")
(set @default-dest "RAM:")
; Update Update-ArosOne
(welcome "")

; Update AROS One 64Bit v1.1
(copyfiles
(prompt "")
(help @copyfiles-help)
(infos)
(source "")
(dest "SYS:")
(choices "Update-ArosOne/")
)
[/code]

[quote name=deadwood post=8814]@deadwood - I will need more information TBH. On your screen shot you are copying from disk to pendrive, both being SFS I guess. Each time this happens please take a screnshot from the requester with "More.." clicked if possible and note what was the source (which device: ahci, ata, usbscsi, which file system) and same for destination. If after 3-4 instance of this problem we can see some pattern I can start looking for cause.[/quote]
It seems that the GURU on copying/moving Dopus4 is due to network sharing. I suspect that my 64-bit compilation of ‘smb2-handler’ was not compiled correctly, as this also happens with the previous version.

The Guru also appears on AROS One Hosted Linux

With AROS One 32-bit, the problem does not seem to occur, so this made me think that the 64-bit version of ‘smb2-handler’ did not work properly. Can someone check or recompile SMB2? Here are the sources:

https://github.com/salass00/smb2fs/releases/tag/V53.10

EDIT:

It seems that copying data from Shared on Wanderer, the Guru is not present, I continue to make copies for further verification!

Thanks for invastigating this further. Interested to see if Wanderer+smb2-handler works.

Hi All,

An update to 64-bit release is now available:

[url]https://axrt.org/download/aros/v11/AROS-20250418-1-U1.B-any-x86_64-update.zip[/url]

Below you can find changes included in this update. Also, if you hare running AROS One 1.0, AMIGASYSTEM is working on an update to 1.1 which will containt this base system update.

IMPORTANT: an issues has been detected with original update that causes failure to boot on IvyBridge Intel CPUs with VESA driver. If you already applied the original update and are experiening this issues, please boot in VGA mode and install the below patch:

[url]https://axrt.org/download/aros/v11/AROS-20250418-1-U1-P1-any-x86_64-update.zip[/url]

[code]
AROS ABIv11 20250418-1-U1 changes:

Functionalities:
C library extended with several wide char functions (Deremon)
SSE2/SS3/AVX accelerated pixel conversion routines (Kalamatee)
Updated several network drivers to work on 64-bit (Neil)


Updates:
Multiview (Russell Shaw, Mazze)
Kernel (Johan G)
basque.language (jalaguero)
Codacy detected fixes (Mazze)
Locale files refreshed
Prefs/ScreenMode (Kalamatee)
etherlink3.device (Neil)
AROSTCP (Neil)
SAD debugger (Johan G)


64-bit support:
mesa3dgl.library, gallium.hidd, softpipe.hidd, IntelGMA
vwmwaresvga.hidd, gallium.library (fixed to work on pre-SSE4.1 CPUs) (deadwood)
Prefs/OpenURL (fixed to work on 64-bit) (Kalamatee)
nvidianet.device (fixed to work on 64-bit) (Neil)


Functional fixes:
icon.library (Russell Shaw)
reqtools.library (bugs: Window pointer check) (Josef Wegner)
Calculator (bugs: trailing 0) (Ivan G.)
gadtools.library (bugs: wrong position of left-aligned object, wrong slider behavior) (ronybeck, r3dbug)
C:Copy (bugs: #179) (jalaguero)
AROSTCP (bugs: fails with fd == -1) (deadwood)
stdlib.library (bugs: wrong value of DST field) (deadwood)


Stability fixes:
Prefs/Wanderer (bugs: crash when closing advanced tab) (deadwood)
crt.library (bugs: seeking on directory handle possible) (deadwood)
intuition.library (bugs: crash when invalid pixfmt) (Kalamatee)


68k support:
exec.library (bugs: wrong CHIP memory alignment for AllocPooled) (Johan G)
sagagfx.hidd updates (Willem Drijver)
Sprites support (DerThore, Johan G, deadwood)
keyboard.device (fix for older games) (ronybeck)
Interleaved bitmap support (DerThore)
Fix handling Copper1 (Johan G)


ARM support:

[/code]

Hi All,

SDK update is also available:

[url]https://axrt.org/download/aros/v11/SDK-20250418-1-U1-any-x86_64-update.zip[/url]

Changes:

[code]
SDK ABIv11 20250418-1-U1 changes:

collect-aros
Corrected ABI version being written to ELF objects

libpthread.a
Fixed bug triggered by new task getting the same address as one being shutdown

libcrt.a
libstdlib.a
Exposed newly ported wide char functions: fgetwc, fgetws, fputwc, fwprintf, mbrlen, mbrtowc, mbsnrtowcs,
mbsrtowcs, putwchar, vfwprintf, vwprintf, wcrtomb, wcsnrtombs, wcsrtombs, wprintf

libcurl.a
Updated to 7.76.0

libsqlite3.a
Updated to 3.48.0
[/code]

They are currently being tested, and if there are no problems today, AROS One v1.1 ISO/USB and AROS One Update v1.0 To v1.1 will probably be released.

Regarding the problem of copying Dopus4 from a network drive, it is very difficult to understand when and where the Guru will occur. The same file is often copied, but other times it generates Guru. With Wanderer, no Guru has appeared so far, but as mentioned on DOpus4, sometimes no Guru appears, then it suddenly returns.

As mentioned, in the 32-bit version of Dopus, the Guru problem with the Network Drive does not exist!

Does it make a difference if it is a large size file vs a small size file?

Could there be a stack size problem involved?

It can also happen with a single small file, even Guru can be different! Today I tried to copy folders full of files and Guru did not appear.

The problem does not only concern the Copy command, but also the Copy As command. I will try to increase the Stack on Dopus4 and see if Guru disappears.

EDIT :

I increased the stack to 120,000 on Dopsu4. i don't have Guru at the moment, let's hope for the best!

Tried the lastest version on DELL D520. The IntelGMA does not work. I can always take a picture of the error message when booting if it is not a know issue. VESA work as normal.

Thanks Nikos. IntelGMA is a known issue. Didn't yet had time to work on this.

@All

If you have issues after update read important note in this post: [url]https://www.arosworld.org/infusions/forum/viewthread.php?thread_id=1411&rowstart=160&pid=9149#post_9149[/url]

@AMIGASYSTEM

Try this updated bzip2 and bz2.library:

[url]https://axrt.org/development/UPD20250819.x86_64.zip[/url]

I can now list the files from archive you used multiple times.

@AMIGASYSTEM

I have a question about OpenURL. If I program (like Odyssey) needs a high stack value, where do you set it in Prefs/OpenURL so that this higher stack is used when starting the application? I don't see such settings in Prefs/OpenURL.

Regarding bz2 archives, the problem seems to have been resolved, and it is now possible to unpack an archive multiple times.

Regarding OpenURL on Aros One 32-bit, I added the Stack for AmiFox in the developers' Info file, but with OWB I always got a Guru.

On 64-bit, OpenURL AmiFox does not start, browser opening error! Furthermore, on 64-bit, OpenURL does not save to ENVARC, it only saves to ENV.

Update:

[url]https://axrt.org/development/UPD20250820.x86_64.zip[/url]

Several fixes for OpenURL which allow me to pass an url (tested with amigaguide document) to Odyssey either with starting it or passing it to already running browser on new tab.

Here is configuration of OpenURL that I use:

With Update UPD20250820, OpenURL works and OWB starts normally.

The only odd thing is that AmiFox does not start with OpenURL, which is strange because AmiFox worked fine with AROS 32Bit. I also used the same settings that I have on 32bit.

AmiFox still doesn't start with that today's update? What command path are you using for AmiFox?

I run a ‘Link’ script that some developers include in their software.

It is a simple script that executes a link via the OpenURL icon, see attached script.

With the update, OWB works today, but I have to add a stack of 8192000 to the script.

The same script does not work if I configure and activate AmiFox in OpenURL Prefs.

On AROS One 32Bit, the same script AmiFox works fine even without a stack in the script.