What the fastest possible x64 emulation way of OS4 today ?

@Reth

Quote:

For the Display Manager GTK you can use “-display gtk,zoom-to-fit=on” this will solve your problems.

You can also tell Qemu to switch the machine to full screen on startup. I do this myself when I use Qemu because I don't want to see everything that happens in the background.

."-display gtk,zoom-to-fit=on –full-screen"

Unfortunately now I am getting another error when trying to copy files to the exchange directory to have them in windows:



Next to that it seems whatever I copy into the share drive from AOS4 side does not occur on Windows side anymore.

Any idea what might be wrong here?

@Reth

For this I would need to know the line you passed to Qemu and where the share folder is located under Windows.

Otherwise there is a first class tool called WormHole, I haven't tested it myself under Qemu because I use SMB2 for file transfer which works fine.

WormHole has to be started under AmigaOs4.1 and of course under Windows, if it works you have a very fast way to transfer data. Unfortunately Wormhole cannot handle several files at the same time, so it is best to pack everything beforehand.

Here you can get some information about WormHole

https://www.amigans.net/modules/newbb/viewtopic.php?post_id=153599

@Reth
You have too much of something in the shared folder. It's not meant to be used as a general file exchange just a way to quickly share a few files such as updates for install or setup files. For copying large amount of data use a network share, ftp, scp or something like that.

IC. Thank you. So far it worked fine so I thought it might be usable like a normal folder. After that problems it never worked again - even after a restart of QEmu which is really strange.

I can use FTP as a workaround though.

@Reth
That it's not working even after QEMU restart should not happen. Maybe something broke in the folder you're sharing. If you can still reproduce it and can run QEMU under debugger (which needs gdb on the host): just adding gdb --args before the qemu-system-ppc command then enter run from (gdb) then you could get a backtrace with bt after it stops on the assert to see where exactly it's failing. That could be reported on the QEMU list, bugtracker or at least here.