[quote name=AMIGASYSTEM post=10171]@AMIGASYSTEM - 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![/quote]

That was previosly reported: https://github.com/deadwood2/AROS/issues/218

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

@ 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.

Thanks, bug report created:

[url]https://github.com/deadwood2/AROS/issues/224[/url]

@AMIGASYSTEM

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

Version C:WirelessManager FULL

@ 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!

A small update from me:

I'm wrapping up current work on EmuV0 and once done, I will start working on releasing the U3 update.

FYI, as mentioned earlier, now that EmuV0 1.0 is released, I will be focusing on preparing the U3 update. If nothing bad happens, I expect the update to be available in next 2-3 weeks.

I would like to report that BeeBase v1.2 on AROS 64Bit v11 crashes the system if you use the native VMware video card on VMware.

The crash occurs when using the menu! With VESA resolution, the problem does not seem to exist.

Some questions:

1) Did you try if the same crash happens with VMWARE driver on QEMU?
2) Is it enought to right-click to have a crash or do you actually need to select any of the menu options.
3) Does it happen in both pop-up and pull down menu modes?
4) What was the system you were using for tests? Official release + U2? Some nightly build?
5) Please post the screenshot of the error requester

The crash appears with the reference build only on VMware and when using the pop-up menu (see attached video). With QEmu + VMware video drive, there does not seem to be a problem.

Ok, I see. What do you mean by reference build? Is this the 20250418-1 release ISO? Is update U2 applied on this? Or is this one of the nightly build ISOs?

By Reference Builds, I mean your Updated Builds (9 October 2025) 20250418-1 + U2.

I'm not able to replicate this problem with my local U3 build. Possibly it has been solved in the meantime.

Here is an updated vmware driver which should fix the "black desktop" after exiting full screen under VMWARE:

[url]https://axrt.org/development/vmwaresvga.hidd.46.0.x86_64-aros.zip[/url]

If you still have crashes in BeeBase with this driver, please check if they are also present with this build from yesterday:

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

Even with these two new Driver, Se BeeBase continues to crash!

We then need to see if it crashes for other people as well. Like I mentioned, I can't replicate this on my setup (VMWARE 16). What you can do is to add a serial port to your VM configuration, redirect it to file and then start AROS with additional 'debug=serial' grub argument. Then when the crash happens, maybe there is some information in the serial file.

Deadwood, I tested Beebase on VMware 17 and the problem is still there!

Question: Did you run Beebase after assign the Beebase path? I ask this because otherwise the problem does not appear, as the GUI background does not load. In my opinion, it is the background that has problems with the VMware video card.

Yes, I added the assign and the red background image loaded. Please try capturing serial debug output.

After debugging with the serial port, I am attaching two files. I hope they have been done correctly!

Yes, the debug was captured correctly but unfortunatelly it doesn't show any log of crash. It might be that this is not a crash but infinite loop. I did notice however something else: you are having DMA errors for ATA driver. I don't have such errors on my setup. Try changing your disk to use SATA instead of IDE.

I tried using the hard disk as SATA, but the problem persists.
I noticed that increasing the stack improves things a little; the crash occurs after using the menu for a longer period of time.