@n3m3
No updates as much as I know, but I have just released a new version of Kyvos, with plenty of improvements.

You can read more about this new version at
https://ko-fi.com/post/Kyvos-v1-8-0-released-C0C01P93IV
And here is a list of the changes

## 1.8.0 [2025-11-27]
### Added
- Added a check for error when VM files are deleted. If that fails an information requester appears
- Added the Debug level field under the Hardware tab, which is related to the Serial output
- Added a new tab and a text field to add custom Qemu arguments in the arguments window.
- Added a check if a VM is running when Kyvos starts, and change its icon in the list
- Added the "Check for updates..." and "Roadmap" options under the "Help" menu

### Fixed
- Fixed an issue with mounting the third hard disk, which conflicted with the CD
- Fixed the reset of the custom paths when the setup run

The new version can be downloaded at https://ko-fi.com/s/6476fdadd2

@saimo

Yeap. I was kidding, actually. Your games are so well-made, that I doubt after all these years, there are bugs that you haven't squashed.

@AMIGASYSTEM

I will try to add it in one of my future releases. Thank you for the info. Added in my todo list https://pms.walkero.gr/issues/63

@Tuvok
Oh, that was so close. I was missing keys as well. And it looks like the same stage. Maybe there is a bug :D :D :D

Awesome gaming guys

@AmigaNG

I am so sorry I missed your message and didn't reply yet. But I will try now.
When you set the AHI configuration, set also the Music Unit 0. Some software uses that for music. Maybe that is the reason of failure.
On my system I use AmigaAmp and I know it works fine. I haven't tested tunenet to be honest.

@AMIGASYSTEM

These are great news. I am sure that this will improve the user experience considerably. Would it need any changes on how the qemu emulated system run?

@smarkusg
That's an interesting topic to discuss. For not derailing this thread, would you like to open another and discuss it there?

We need an updated port of Flare. It seems 1.14 is the latest released 3 years ago.
Anyone up to the task?

absolutely. That looks very nice and challenging

@AlfredOne
Thank you so much for that link.

@afxgroup
If that is the case, that means that the X5000 as sold by A-Eon, are broken.
But why this happens only with some cards and not every card?
Did Luigi Burdo shared that information anywhere, where I could have a look at?

@joerg
In the system information screen though, I see more devices, and the 3132 is not visible there as well. Does that mean there is a hardware issue that prevents these cards to be even visible in the u-boot?

@joerg
The list has only one record and that is the processor and nothing else, although I have an audio card (pci), a Sil3112 (pci) and the Sil3132 (pcie x1) connected. And of course, the gfx card.

Today I received the Sil3132 cards I ordered, which are the same like sailor shared at https://www.amigans.net/modules/newbb/ ... id=157694#forumpost157694

Unfortunately, they didn't work on my X5000 either, as they are not recognised at all. I tested them on both PCIe x1 my system has, and used Ranger and lspci to see if they are available.

I am using U-Boot aeon-2022-02-07 (Feb 07 2022 - 00:28:23)

I wonder if this is a hardware problem I guess that no PCIe card would work on these expansion slots. Does anyone have any card working on PCIe x1, like an audio card or nvme card?

Try to change the renderer that is used from the SDL prefs. And let me know if there is any of them working for you

Thank you for the amazing report. Well done.

Maybe it would make sense for you guys to share the version of UBoot you are using with your system because that might be useful to track the problem. What do you say?

I ordered two cards to test with my system, and waiting to receive them next week. Then I will report back.

Yeap, I can confirm it is there.

@AmigaNG
Quote:

Fair point. I will do that.

Quote:

Usually, the <> in guides mean that this whole section need to be changed. You shouldn't include those characters. I am sorry I didn't make it clear. I will update the manual.

Quote:

Fair point as well. I will update the manual.

Quote:

I appreciate your feedback, and I want to assure you that I will improve it based on it. And thank you for taking the time to read the manual. This has information that I believe it is useful for everyone who would like to emulate AmigaOS 4 using QEMU and not only for those who use Kyvos.

@ilbarbax
nah. That is happening with all the Hollywood based applications as much as I know (https://forums.hollywood-mal.com/viewtopic.php?p=18158). I have some info about it in the FAQ section of the manual.

@everyone
A new version of Kyvos 1.7.0 just got released. Read more about it at https://ko-fi.com/post/Kyvos-1-7-0-released-R6R81NHQWD

Here is what changed

## 1.7.0 [2025-10-27]
### Added
- Added binary for Linux 32bit Arm systems, like a RaspberryPi
- Added a way to duplicate a VM in the right-click menu

### Changed
- Changed the "AmigaOS4.1 FinalEdition Update 3" to be mandatory when AmigaOS 4.1FE Pegasos2 or AmigaOne system is created
- Changed the hash of the "AmigaOS4.1FinalEditionUpdate2-53.14.lha" to be the latest one from Hyperion's website
- In the welcome window, the Continue button remains enabled even if a dependency is missing. This is necessary for 32bit systems which do not have the qemu-system-x64 available. It is up to the user to take the risk to continue, instead of blocking him.

### Updated
- Updated the manual fixing issues, made the usage of update3 more clear in various places, added more sections and more questions in the FAQ section

Kyvos and its manual is provided free of charge, but if you like it, please consider a donation. You can get Kyvos at https://ko-fi.com/s/6476fdadd2

There are plenty of things in my to-do list, which can be found at https://pms.walkero.gr/projects/kyvos/roadmap