@khayoz

1. Grim Fandango
2. Secret of Monkey Island
3. Simon the Sorcerer
4. Indiana Jones 4 - Fate of Atlantis
5. Inherit the Earth - Quest for the Orb

6. The rest of Sierra games
7. The rest of LucasArts games

8. The Feeble Files

9. Discworld series
10. Broken Sword series

and all the games that i have in my back catalogue...too many games, so little time

@Maijestro
OK then it should be resolved with Akihiko Odaki's series. I think it was reviewed by Peter already but not yet merged. There's still 1-2 weeks until the freeze for QEMU 9.0 starts so it should be in a pull request by then. Since Peter Maydell is one of the master maintainers the right people already know about this series so likely it will be in 9.0 so just wait for it to land in master then.

I think @AlfredOne wrote before that QEMU's tablet should have a wheel but maybe the driver does not support it. But as I said you probably won't see much difference with the sm501 device that does not have host side hardware cursor support so this may only be good for preparation when some other graphics drivers would become available in the future.

@smarkusg
It's very possible nobody tried it with AmigaOS yet. The assert means that the condition should be true. If it's not then there's a problem somewhere, either the guest sent some unexpected commands or there's a problem with emulation. Commenting the assert won't help as it's there to make sure it won't break later. There's a trace in lsi_do_command that you could enable to see which SCSI command resulted in this problem with this QEMU option -trace enable=lsi_do_command which may give some more info on what's happening (but one needs to know how SCSI works to understand that; I don't know that so either somebody here knows or somebody have to read docs to learn).

QEMU actually only emulates lsi53c895a the lsi53c810 is just an alias with a different PCI device ID so if the AmigaOS driver works differently with actual lsi53c895a then you should used that and set the driver option accordigly which you could do by replacing nonvolatile.library to use nvram/nvrom.txt as @joerg said. Maybe that makes the driver send the correct commands for the hardware?

@MartinW
Quote:

That casual settings of the MUI prefs you should do (in mui prefs) telling it to "save size of the MUI window permanently". Or if you want it static, then resize as you need, and do "snapshoot".

@AmigaSociety did you get 4K going?

I put my RX580 in yesterday to get some more performance and noticed it's only auto-detecting up to 1440 (ironically that works for me out of the box). I'm like you and won't actually USE 4K but you know - maybe one day it might be useful for something so it would be nice to have it there as an option.

My monitor is 27" 4K Dell

The only issue I have with Odyssey which is on my list of "Things that don't work for me on OS4 and need looking into" is that every time it opens, it opens to the full width of the screen. That might have been fine 20 years ago when the average screen was small but on a 4K, 27" screen it's downright annoying. Multiview does the same.

I've not really looked into it as I've kind of just assumed it's the way it is, but if there is a solution, or a setting I'm missing, someone please tell me :D

@joerg
I did as you wrote.
QEMU Sam460 and Pegasos(pegasos.rom) when trying to initialise after loading the kernel and AOS4 modules from the cd it crashes.

EMU launch command line Sam460

!!!Just for a test I did a rem "assert"!!!
sam460 sees the card and the disk. The problem is on the QEMU side. Most people from what I have seen are tuning the lsi53c810 to run linux via QEMU. It is possible that no one has tried this on AOS before and it doesn't work and the lsi53c810 itself in QEMU needs to be checked.



Pegasos bboot hangs on something like this and booting AOS4 (debug) is stopped

@AmigaOldskooler

thank you for the monthly blog..was a pleasure to read

nox

@Raziel

What's the Top3/5/10 games that works with ScummVM in your opinion?

@Raziel

That's interesting. If this is the first time you've seen the compiler mention libpthread.so, then I'm guessing it's not being used by anything else and perhaps the reason for the crash wasn't libpthread.a being accidentally embedded in libcurl.so.12, but some other reason. Anyway, all that matters is the problem got solved! I'll update libcurl on OS4Depot within a couple of weeks, but keep the .so.12 you have because it uses DEVS:AmiSSL/Certs while the OS4Depot version will use curl-ca-bundle.crt

@balaton @AlfredOne

Ok, it is clearly due to the Display Manager Cocoa with the output SDL there are no problems and your driver does what it should.

Balaton I am using Qemu Master without the fullscreen Cocoa patch from Akihiko Odaki, I am not sure if the patch has made it into the Master sources yet as there were changes made by Peter Maydell shortly after the last series.

It seems that Akihiko Odaki's patch series is still not included in Qemu Master, so I added the patch series again. With the last patch series of Akihiko Odaki version 12 it works as under the SDL output. Thanks for the tip.

@AlfredOne

Thanks for this driver and the support of the tablet HID device it works What is of course missing is support for the mouse scroll wheel.

@AmigaOldskooler

Thanks for another update!


Edit: Font spacing? an oth er ?
Odyssey?

@AmigaOldskooler

Thanks for doing these! Very nice read and always something I did not know about. :)

That’s look like a datatype compatibility problem.

@Maijestro
This looks more related to QEMU display backend than to guest side driver. You could try with -display sdl to cross check if it happens with that too or only with -display cocoa. Is it with recent macOS full screen patches or with QEMU master? If it's related to the changes in cocoa backend you could ask on the QEMU mailing list cc-ing Akihiko Odaki (the patch author) but first check with -display sdl and using QEMU master without other patches.

@Maijestro

In fullscreen it should never happen. It is behaving as if it were window mode and the AmigaOS window ended one line before the screen border.
I tried both on my laptop screen and on an external 4k monitor and in fullscreen I can reach the edge without the host cursor appearing.
What options do you use to launch QEmu?

@Gregor

This is off topic now but here goes...

So far my issue with MultiView seems to only happen if I launch MultiView from my AmiDock. The file requester opens up as expected, I select a file and boom I get a DSI error. But it is totally random. Sometimes the file opens as expected. Sometimes I get a DSI error. Not related to any particular file, but so far only text files are affected.

Anyways, I'm slowly troubleshooting ...
- rolled back to MultiView 53.8
- made sure rear USB ports are in fact disabled,
- currently starting network port manually.

My system is a MicroA1 purchased in 2004 and it has some quirks that show up from time to time.

---
redfox

@MickJT

I just realized that your libcurl is asking for libpthread.so...which i don't have :-/



found it in sobjs: ... grmbl

@AlfredOne

Quote:

To understand the problem I have recorded a video...here you can clearly see the problems, via the title bar of AmigaOs4.1 it is still possible to call up the menus, but you are not allowed to move the mouse pointer to the edge of the screen. I am not sure if the problem can be solved....but see for yourself...

@Raziel


Quote:

I have tested your trial version a bit and recorded the whole start of ScummVM when creating the .ini file.

I am sure that if you use a freshly booted AmigaOs4.1 system and run ScummVM for the first time there are no problems with the creation of the .ini file.

But I could see some error messages in the log which did not lead to a crash.



The complete logs can be taken from here it only shows the execution of ScummVM at the first start without .ini.

https://pastecode.io/s/esucovwn

Then I did my usual tests Odyssey...YouTube the whole thing I repeated 3 times in one and the same session. There were no problems at all.... but on test 3 it turned out that I ran out of memory and it caused DSI and crashes. I am not sure but I suspect that Odyssey does not free the memory after quitting and it causes ScummVM to crash or show DSI error messages.



Maybe a problem only under Qemu/AmigaOs4.1, but I've never had a problem with insufficient memory. Can you report something similar? On my machine AmigaOs4.1 FE is up to date including all updates and also the latest version of elf.library is used which was/is recently available via AmiUpdate. I use Odyssey version 1.23...

Of course, it could also be that MPlayer (latest version Os4Depot) does not release the memory and continues to use it after exiting when using Odyssey/YT.rexx via MPlayer.