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.