Kyvos was updated

Just bought it and tried to download the win64 file. My windows said the archive contains a virus (Trojan:Script/Wacatac.C!ml) and threw it out.

Is it just me who have trouble with the archive and windows security?

@Menthos
Thank you for buying Kyvos. Please, have a look in the guide and the FAQ section. It is already covered.

Thanks for the GUI!
Here's everything in one place, ideal for beginners!

I also wrote a few GUIs a while back, but they didn't get much attention:

QEmu AmigaOS4 GUI (Windows/Linux)
https://github.com/Falke3434/QEmu-PPC- ... 1.1/QEmu.AmigaOS4.GUI.zip

Pegasos2 und AmigaOne Kickstart Creator (Windows)
https://github.com/Falke3434/QEmu-PPC-GUI

Buildscript-QEmu-PPC (Powershell Windows)
https://github.com/Falke3434/Buildscript-QEmu-PPC

@walkero

LOL! Never got that far in the documentation. Thanks for the fast reply!

Using last Kyvos 1.2.2 with Qemu 10.0.3 on Mac M2 silicon processor and Pegasos2 config I have issues with graphics in some games I'd tested. Workbench windows and system friendly apps works correct.

I'dont know if it's a problem of Qemu on M2 or need change some parameters on AmigaOS4 or Kyvos.

@kikems
You need to change the CPU emulation to G3 instead of G4 (-cpu G3). There is a known issue with some graphics errors when using Pegasos2 CPU G4+ sm502(16bit) + SLD1. The error seems to be related to the AOS4 kernel for PEG2.

@smarkusg

Thanks a lot, now works good, Kyvos should be add a chooser for CPU at least for Pegasos2 setup. I do it coping qemu arguments from Kyvos and pasting in a terminal window adding -cpu G3.

@walkero

Quote:

You don't have to apologize for anything

Okay, tested with version 1.2.2. Here, too, the paths are not recognized, and I don't know why. If there's anything I can do to help you solve this problem, let me know.

@smarkusg

Could you run a few quick tests on your MacMini M1 with Kyvos 1.2.2 to confirm the problem?

@Falke_34
Your GUI does not work with systems lower than Win10.
Close OT

@Maijestro
Please, create an issue at https://github.com/walkero-gr/kyvos/issues and add there as much information as possible. For example, a screenshot of the folder list would be useful. Also a screenshot of the setup window in kyvos

@kikems
Quote:

I will have a look so to add a cpu option. But if you want to make it permanent, edit the vm config file. Check the manual, where I have a section providing further information about it.

@smarkusg
Do you have in mind other shenanigans like that I could add to Kyvos?

@Maijestro
Quote:
@kikems uses Mac M2 silicon, and it works fine for him. I think it's better to report this problem, as @walkero wrote.

@walkero
Quote:
Currently, I don't remember anything important. As soon as I find something, I'll let you know.

@noXLar
Quote:
See my page at the URL in my signature below on what works. QEMU emulates NG Amigas, for the classic you need UAE instead. The sam460ex should work but a bit slower than amigaone or pegasos2. If you consider purchasing a new version better go with amigaone as pegasos2 version has some issues even on real machine which might be fixed in an update but nobody seems to know when that might be released so amigaone is better for now.

With sam460ex you might see crashes in nvgetvar (e.g. sysinfo calls it). You might be able to fix it by adding a text file with name=value pairs for setting env vars called nvram.config to Kickstart.zip (also add as a MODULE in Kicklayout), or you can replace C:NVGetVar with a script that does nothing to avoid these crashes.

@balaton
Quote:Only possible if you replace the Sam460 nvram.resource.kmod with the classic Amiga version (used on the Pegasos2 as well because nobody ever implemented a Pegasos2 version).
All other versions of nvram.resource.kmod (A1, Sam440, Sam460, X1000, X5000 and A1222) read/write the firmware env variables and don't support a nvram.config kickstart module.

@joerg
Have you checked that? It looks like nvram.config is read by newer versions of nonvolatile.library.kmod (which the sam460ex 4.1FE seems to have). This can be used to override nvram settings but can also be used to provide default values if no nvram is available. Maybe it's not documented, I've discovered it while experimenting. I did not test the sam460ex version but maybe it works without replacing anything but the file needs to be called nvram.config there and added as a module in Kicklayout. The pegasos2 version has older nonvolatile.library.kmod that does not support this but there nvram.resource.kmod can read a file named nvrom.txt the same way. Maybe this was first implemented for pegasos2 but then added to other versions in case variables need to be overridden or defaults provided for settings like IDE DMA or similar. Not returning anything or not handling the error if neither nvram or nvram.config/nvrom.txt is available is probably a bug that went unnoticed as all machines have nvram.