@ ncafferkey

In the Wireless Test done with AROS One 64bit 1.2, I had Wireless Manager v1.6 from the reference build 20250418-1.

Now I have tried Wireless Manager v1.7 included in the Nightly Build Testing and I did not get any Guru.

Wireless Manager v1.7 works very well, I have updated Aros One, thank you!

@AMIGASYSTEM

Are you using the latest WirelessManager? Can you check this please?:

Version C:WirelessManager FULL

Thanks, bug report created:

https://github.com/deadwood2/AROS/issues/224

@ deadwood

A problem has been found with Wireless Manager. If you use it, a Guru may occasionally appear, see screenshot.

To get a Guru, just go to Network Prefs, disable ‘Start networking during system boot’ and then save.

Strangely, after saving, a second Wireless Manager icon appears on Wanderer.

The Guru may also appear if you reactivate ‘Start networking during system boot’ after a restart.

That was previosly reported: https://github.co...issues/218

Here is the list of open issues if you want to double-check something:
https://github.co...ROS/issues

MysticView 64Bit (Contrib) does not work; instead of images, it displays a white line on the screen, see screenshot.

No version of MysticView 64Bit has ever worked for me, and it has now been removed from AROS One 64Bit!

Yes, it's already reported here: https://github.co...issues/147

There is nothing that can be done to increase the download and upload speed regarding the TCP stack.

Yes, I confirm, but I don't know if it's the program or the system, it will be the program the context menu works, though

I meant the commands from the menu buttons. I suspected it depended on the programme.

However, the commands from the prompt work fine!

What do you mean by "menu icons"? The crash seems to be coming from VIM, not from system.

VIM 64bit crashes (Guru) when clicking on the menu icons. Can anyone confirm this?

The 32-bit version does not seem to have this problem.

I don't remember having already reported the ‘Move’ problem on Wanderer!

Basically, Wanderer does not allow you to move files or folders to overwrite existing files or folders, see screenshot.

If you change the function from Move to Copy in Wanderer preferences, the overwriting works correctly!

There is also another problem if you try to delete a folder full of files and folders in Wanderer. In some cases, you have to repeat the command. Basically, the first command empties the folder and the second command deletes the folder.

These problems are also present in the Builds to be tested.

At the moment, I haven't found any Guru in copying; among other things, Dopus4 now copies much faster.

Does this build fixes copying issues for you?

OK, thank you. I suspected that it might have something to do with asyncio.library. The solution I found by removing Trackdisk might work for those laptops where the floppy drive is not detected. In this case, Dopus4 cannot start, and the same thing happens if a floppy drive is not added to the configuration on VMware.

@AMIGASYSTEM

I reproduced your crash with smb2fs and locate the bug in asyncio.library. It was causing random memory to be used as buffer, damaging other software's data and would eventually lead to crash during or after copying data with DirectoryOpus.

Here is fixed library:
https://axrt.org/development/asyncio.library-40.1.x86_64.zip

Can you point me to where I can download the smb2fs you were using with your tests on hosted (the ones where it was very easy to replicate the crash when reading from network share).

Can you also page the configuration you are using with smb2fs?

This problem with DOpus4 looks to me like a subtle stack corruption problem (not too low stack, but damaged stack). This means different changes to how binary operates might hide or show the problem. Sometime even adding one line of debug in the right place can hide the problem (but not really solve it)

The GURU problem with Dopus4 could be ‘trackdisk.device’.
I tried modifying the Dopus4 binary by removing the ‘trackdisk.device’ entry, and at the moment the Guru has not appeared despite copying a lot of data from the network share. I will continue testing!

If, on the other hand, I remove only the ‘trackdisk.device’ from DEVS, the Guru appeared only once. I will continue testing here as well.