Can you please share a little bit more information what molk is and where can I find it?
I think it was a stripped down Linux distro with MacOnLinux for Pegasos: this here (there may be other versions). I have never tried if it works but if you want to run MacOS on QEMU maybe go to emaculation.com instead and install MacOS on mac99 which may run better (we even enabled SMP for it but that's not in upstream QEMU and does not help AmigaOS or MorphOS anyway). So I don't know how molk would be generally usful other than historical peculiarity. It may be overkill to add it to Kyvos just so you can try it once or do you have a use for it other than it would be cool to see it running? By the way if you want more users you may consider adding MacOS and MacOSX support and announce it on emaculation.com, they might be interested in a QEMU GUI too.
@balaton MacOnLinux was available for the AmigaOne XE as well (using Debian Linux), but as you wrote it doesn't make any sense on emulation. If you want to run PPC MacOS emulate some PPC Mac hardware with QEmu, instead of using the much slower MOL on top of PPC AmigaOne or Pegasos emulation.
Thank guys for your replies. If you are right and MacOnLinux is the one that is requested, I will unfortunately have to pass, as it is not my target at all. Kyvos is meant to help users get on OS4 easily and for developers to create different OS4 environments for testing their applications.
Yes I used the advanced method having the img disks already created and configured. I suggest to add a statement in the manual to avoid using a single directory as I did, or you could rename the config file to VMname&_config.json so it remain unique.
@walkero Finally got the ko-fi page to work. I have several extensions running in Edge, and apparently one or more of those was interfering with how the Cloudflare part of it loads. That let the login and the download of the new version work correctly. And now that they work, I've turned all the extensions back on and it still works (for now). Need to figure out which one is blocking the Cloudflare stuff and make some adjustments, I guess.
But, on to the Update 3 and Kickstart update. Seems kyvos is not recognizing the LHA file for Update 3 even though I've named it like the update text says to do, AmigaOS4.1FinalEditionUpdate3.lha. I also tried it without renaming it, as AmigaOS4.1FinalEditionUpdate3-53.34.lha, but it's still not including it in the Kickstart files.
I know because if I look for some of the specific updated files in the new kickstart.lha file, the dos, intuition, and other files for Update 3 are not there, with files dated in 2021 instead of 2025.
Also, the manual needs updated too, as it doesn't mention Update 3 in it.
Yes that's what molk is, sorry for the late reply. I get it, it's out of scope as I expected and I know it's basically pointless, but I thought I'd ask
dwolfman wrote:@walkero Seems kyvos is not recognizing the LHA file for Update 3 even though I've named it like the update text says to do, AmigaOS4.1FinalEditionUpdate3.lha. I also tried it without renaming it, as AmigaOS4.1FinalEditionUpdate3-53.34.lha, but it's still not including it in the Kickstart files.
I know because if I look for some of the specific updated files in the new kickstart.lha file, the dos, intuition, and other files for Update 3 are not there, with files dated in 2021 instead of 2025.
I can only add that im using Kyvos 1.6.0 for Windows x64, and it worked for me when creating an AmigaOne machine config using the "Automatic" option.
Are you using the "Advanced" option to create the virtual machine? and if so, what settings are you using? I can try and recreate the issue to help track it down.
But, on to the Update 3 and Kickstart update. Seems kyvos is not recognizing the LHA file for Update 3 even though I've named it like the update text says to do, AmigaOS4.1FinalEditionUpdate3.lha. I also tried it without renaming it, as AmigaOS4.1FinalEditionUpdate3-53.34.lha, but it's still not including it in the Kickstart files.
Kyvos will use the update only when you create a new VM using the automatic method.
What are the steps you took to create your VM and how did you check that this didn't work? I need a description of the exact steps.
Quote:
Also, the manual needs updated too, as it doesn't mention Update 3 in it.
First, I made sure the Update 3 lha was in the same folder as the A1 os 4.1 install ISO and the other update lha files. Then in kyvos I click the button to make a new instance and chose automatic. I then made sure to pick a new path and VM name so it wasn't trying to use anything from the original VM. Once I had that all set up I let it do its work and build the files.
Since I'm doing this on Windows, I just double clicked the new kickstart.zip to check the files. The dos, intuition, and other new files in Update 3 were not in it, as all those files in the new kickstart.zip had dates from 2021 and weren't the right size.
I tried it with the original name for the Update 3 lha as Hyperion named it and renamed to the name you mentioned in the update text on the ko-fi site for kyvos, but it made the same set of files both times.
This is as close as I remember. Later today, once I'm done fixing my car's engine, I'll try it again and keep track of the details.
@dwolfman I don't know what Kyvos does but if it follows the steps written in my docs page at this link that only takes the updated kernel for the siliconmotion502.chip driver to run to be able to install from the CD that does not have the SM502 driver on the amigaone/pegasos2 versions (the sam460ex does not need this step as that already has the SM502 driver on the CD). After installing AmigaOS you still need to install the updates and then regenerate the Kickstart.zip from the updated Kickstart directory from the VM to reach the newest version. Kyvos probably can't do this because it can't install the update in the VM and the Kickstart.zip should match the version on the harddisk or CD that you boot from so these should be updated together otherwise the CD might not boot with updated Kickstart. First install update in the VM then make new Kickstart.zip from the updated system before rebooting it and use that afterwards and do this after each update that changes Kickstart files (you may need to re-add the siliconmotion502.chip driver to Kicklayout if it's removed by the update so check that first before making a zip). I don't know how much of this Kyvos can automate but maybe it only uses the update for the initial Kickstart creation so the only new file you should see there is the kernel.
@dwolfman I just tested it and it seems to work fine. The kickstart.zip file has the right files included.
To test it properly, boot into your emulated OS4 and open a new shell. Then check the version of the kickstart libraries, like below:
> version full kernel
kernel 54.57 (07/29/2023)
> version full elf.library
elf.library 54.5 (09/04/2025)
> version full dos.library
dos.library 54.136 (09/24/2025)
> version full newlib.library
newlib.library 53.87 (09/07/2025)
This should work with new VMs by starting them booting from the ISOs. Then start the workbench from the CD and open a shell, typing the above commands.
Hello walkero, I would like to share some suggestions that I believe are important.
-The ability to use different paths for CDs and hard disks, which would allow the same hard disks and CDs/DVDs to be used for multiple applications that use them.
-ISO name and CD-DVD name, this is also important. For example, the name of the default AROS DVD does not exist, and AROS distributions have different names. It would be useful to be able to choose the path and name of the ISO as desired.
A less experienced user would certainly have problems installing an AROS distribution. Furthermore, AROS 64-bit should have 6GB of RAM by default, but inexperienced users will ignore this very important setting for 64-bit (errors/Guru not shown in case of poorly compiled software).
Another request, if possible, is to be able to install the OS on or use a RAW format hard disk. To use my AROS/OS4.1 hard files Created with my Qemu GUI, I had to modify the config.json.
@AMIGASYSTEM I will try to answer your comments below and please excuse me if I do not get what you request right. Thank you for sharing all of them.
Quote:
-The ability to use different paths for CDs and hard disks, which would allow the same hard disks and CDs/DVDs to be used for multiple applications that use them.
When a system is created there is a way to attach hard disk images and ISOs from anywhere in the system.
Quote:
-ISO name and CD-DVD name, this is also important. For example, the name of the default AROS DVD does not exist, and AROS distributions have different names. It would be useful to be able to choose the path and name of the ISO as desired.
This can already be done through the Advanced method of creating a new VM, where the users can define the actual ISO they want to use.
Quote:
A less experienced user would certainly have problems installing an AROS distribution.
In my view, a less experienced user should follow the guide and the automated way of setting up an emulated system.
Quote:
Furthermore, AROS 64-bit should have 6GB of RAM by default, but inexperienced users will ignore this very important setting for 64-bit (errors/Guru not shown in case of poorly compiled software).
I will have a look on that
Quote:
Another request, if possible, is to be able to install the OS on or use a RAW format hard disk. To use my AROS/OS4.1 hard files Created with my Qemu GUI, I had to modify the config.json.
You do not need to edit the config.json file. The only thing you need to do is to create the HD image and then use the Advanced mode on creating a VM. Then you select the HD you created and use that when the VM is created. Otherwise, you create a VM with the Automated mode, then you create a HD image in the same folder where the VM files are stored, and then you change the primary hard disk from the media tab. Either way should work fine.
@AmigaNG Thank you for testing Kyvos. Yeah, Hyperion made some changes in the update2 and as a result the hash changed. In the form at the left there is a checkbox "Disable hash check". Enable it and the hash checks will not run. That will let you continue.
That hash check will be updated in the next release of Kyvos.
@AmigaNG When you first run Kyvos it downloads some packages. The silicon motion 502 driver is one of them. Did you download everything?
Also, do not try to enable the virtio-gpu if you do not have the drivers. They are not coming with Kyvos. So, in the display tab you should have "sm501" selected.
Quote:
Right, got pass that part using the not the hash (maybe make that tip in the doc)
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
