What happens when you start Sashimi?

when i open sashimi nothing happens wait i open some software mplayer works fine but when i open owb the whole system slows down i think it's the graphics drivers

So the slowdown is cause by Odyssey or it starts right after booting? What network driver are you using and are you autostarting it?

the slowdown already occurs at system startup

I have notebook with w10pro and VBox version 6.1. When I the run AROS OS 64bit so they not work still. Why? Boot menu is Ok, I'll chooce the safe mode and it show "UNHANDLED EXCEPTION".
The notebook have the cpu core i3 -1115-G4 (11th generation)
My settings is:
64bit unknow
Two cores
APCI- I/O is ON
PEA/NX is ON
2048 GB Ram
AHCI disk
sound off
Net off

thanks for advice

Can you update your VIrtualBox version to 7.x? That UNHANDLED EXCEPTION is not a good sign - something breaks very early in boot process.

Try adding 'noacpi' to grub command line parameters.

does not change the result maybe my computer is the problem

@mmartinka

Also make sure you have "Nested paging" (Acceleration tab) enabled. Without it, I can't boot AROS under VirtualBox.

deadwood noacpi option disable my keybord and mouse

Deadwood I did a quick test on VMware and everything works fine, the SDL.library of the Contrib must be replaced with the fix "SDL.library.x86_64" otherwise applications that make use of this library go into GURU.

Later I will do some tests on Qemu to verify that OWB works fine, with D10 OWB on QEmu went into Guru!

Concerning applications compiled on WMware, how can I tell that they are not compiled well? They worked fine on Hosted Linux!

Unfortunatelly you really can't. If you don't have problems with them and others are not reporting random crashes then most likely everything is fine.

Deadwood on another computer works is a laptop

Deadwood I did a quick test on QEmu with 64D11, the Network works fine, but with OWB I get the usual Guru on the z1.library, see screenshot.

Now I try if 64D11 starts on my VirualBox

That's weird - I never saw that error. Can you please try a clean release od Odyssey without any constomizations (like changed icons). If the error happens there as well, please click "More" on the requester and make anyther screenshot.

On my VirtualBox 7 even with 64D11 it does not start, probably a more up-to-date CPU is required

What message are you getting when trying to start under VirtualBox 7?

From the screen shots you can see the error on VirualBox.

On QEmu I used Build 64D11 with standard OWB and received the same error, I only encountered this error on QEmu also with 64D10

For QEMU:

1) What is the command line you are using (what are QEMU parameters)
2) When you get the crash, click on More... and make screenshot of updated crash window.
3) Make me a screenshot of output of Tools/ShowConfig

For VirtualBox:

This is weird. I get this behavior when I don't have "Nested paging" enabled, but you actually have it enabled.
Suggestions:
1) Change base memory to 4096
2) Change audio to Intel HD Audio
3) Change graphics controller to VMSVGA
4) Add "noacpi" to grub command line

With VirtualBox I tried your suggestions but nothing changed!

On QEmu if I click on "More" Qemu does a reboot


I attach screenshot of ShoConfig, probably there is some error in my script ?




EDIT:

I replaced the z.library with the one included in the Contrib and now OWB seems to work fine !

Regarding the USB port, is there any way to activate it on QEmu, Trident Prefs seems to see the USB Device !