Yes, I tried those too OWB for 68k is probably faster because it uses the JIT in WinUAE.
I doubt the WinUAE x86/x64 host m68k target JIT is (much, if at all) faster than Almos' AmigaOS 4.x (Petunia) and E-UAE PPC host m68k target JIT implementations. I guess the MorphOS Trance m68k JIT is much better than the WinUAE one as well. But in any case PPC native code, like the one in my and Andrea's AmigaOS 4.x/PPC ports of OWB, is faster than any m68k emulation on PPC Amigas. Odyssey is something completöy different, not a direct AmigaOS 4.x port of OWB itself at all, but at best an AROS or MorphOS port of it, with tons of limits: At best the common AmigaOS 3.1 API compatibility, but none of the AmigaOS 4.x parts I implemented, nor my system independent improvements and bug fixes, used.
I'll have a look at Remote Desktop but can we only use a browser ou this the whole remote desktop that is displayed?
Whole remote desktop, but if you run the host browser (Edge, FireFox, Chrome, Opera, Vivaldi, Brave, etc.) in full screen mode there is next to no difference. For other host systems (Linux, MacOS, etc.) you can use VNC instead, severs are available for all OSes (even AmigaOS) and several clients for AmigaOS.
I tried to surf like that but it still feels I'm using another computer.
Of course it does, because you are.
As I wrote in the Amibrowser thread. This is my solution for now, until something OS4 native comes along.
Up until recently I was running RemoteDesktop on my X1000 to connect to a very old laptop, running Windows 10, to do things I couldn't do under AmgiaOS4. It worked pretty well with a couple of things to avoid. (like it would freeze if I tried to copy the URL from the URL field of the Windows browser.)
Recently I purchased this TRIGKEY Mini PC Ryzen 5 5500U for $230, which runs Windows 11 Pro, but I couldn't get RemoteDesktop to work with it.
So...I switched to runiing TightVNC server on the Windows side and TwinVNC client on the X1000 side. I have to say it runs better than RemoteDesktop. No more little things to avoid. It runs smooth and fast enough to watch YouTube videos in Brave or Edge browser. I'm very satisified with this setup but it would still be great to have a better AmigaOS4 browser!
Thanks, I was just reinstalling the Radeon R9 280 GPU. I'll try again to see if I can fix the audio issue without using the "sudo" command. I was looking at ChatGPT suggested solutions
But I don't think ChatGPT really understood what I meant.
This doesn't seem to work: sudo usermod -aG audio $USER
If only there was something normal in AmigaOS if audio was supported in the AmigaOS-side HDMI driver, I'd already solved it.
Obviously I tried Walkero program (Kyvos) but things don't change as soon as I use SUDO to switch the GPU vfio the audio is no longer heard.
Michael Battilana also gave me an AmigaForever license some time ago, but I didn't split it or give it to anyone.
My goal is just to test the driver, nothing else.
And there's no sign of Virtio-GPU. I sent a message to @AmigaKit, but it didn't even read it. Why won't it let me try the driver ? I've been emulating AmigaOS 4.1 for years and I've tested it in every way possible
Also releasing a driver RadeonHD that supports audio through HDMI would be a good solution.
Thanks for the Browservice script.
Edited by white on 2025/8/17 11:23:37 Edited by white on 2025/8/17 11:24:17 Edited by white on 2025/8/17 11:43:00
Just as a day well spent brings a happy sleep, so a life well used brings a happy death.
@white The reason you don't get help is not because of language barrier or other people being selfish but because it seems a bit futile to try to help you. We have had a lengthy discussion of your audio issue before and established that it has nothing to do with QEMU or AmigaOS but you seem to ignore this crucial point and still try to solve it that way. Since it's not related to QEMU or AmigaOS it's also not possible to fix it with QEMU or AmigaOS options or settings. Instead, just make audio work as root on your Linux host with the audio backend that QEMU uses and then it will work with QEMU too. The problem is not specific to QEMU and is a Linux settings issue not related to QEMU. Ask ChatGPT about that and not about vfio, QEMU or AmigaOS and then it might give you a solution. The issue you have to solve is just how to make pipewire or whatever audio server you have accessible as the root user. We have found the solution to that for you before (I forgot but you can dig up the old thread) but you kept trying other things then gave up on it before trying the solution that would work. (Don't bother to answer, that's all I plan to add to this topic as if it does not go across I can't explain it any better so I won't try more.)
---------------------------------------------------------------------------------------------------- WARNING: The Verdana font is not installed in ‘/home/maijestro/.browservice/appimage/fonts/Verdana.ttf’ Browservice GUI appearance will be suboptimal. Run ‘./browservice-v0.9.12.0-aarch64.AppImage --install-verdana’ to install it. --------------------------------------------------------------------------------------------------- - ./browservice-v0.9.12.0-aarch64.AppImage: error while loading shared libraries: libcef.so: ELF load command address/offset not page-aligned
Yeah! I managed to do this with my Mac mini M1 as a VM, and it's faster than my late 2012 Mac mini.
I used Kali Linux, but I think Ubuntu should also work. All this with VMWare Fusion. In VMWare, you have to choose Virtual Machine, Settings, Network Adapters, Auto-Detect from the menu bar. So, for the VM to have a consistent address, not something like 172.168.0.40 or something else, the IP address must match your network. Mine has something like this: 192.168.0.xxx.
I'm watching a YouTube video, and it's a bit slow, but it's okay. I'll make a video.
However, as soon as you go to the Odyssey window, it messes up the video. You have to wait a bit for it to return to normal.
Regarding the right click, I tried with a version of OWB and the right click works but not much else.
About the Verdana issue, Browservice readme says the following
Quote:
The graphical user interface of Browservice is designed for use with the Verdana font. Due to licensing restrictions, the AppImage does not directly bundle it; instead, it uses a free font that works just as well but does not look as good. To install Verdana to $HOME/.browservice/appimage/fonts where Browservice will find it, run the following command and type yes to accept the license agreement: