Who's Online |
47 user(s) are online ( 26 user(s) are browsing Forums)
Members: 0
Guests: 47
more...
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/26 19:13
#61
|
Site Builder 
|
@Boabster Firstly, thank you for using Kyvos. Quote: However I am not sure to why the automatic VM creation wizard did not automatically install Update 1,2 and 3 as I had the files in the same directory as the ISO file. Kyvos is a frontend for qemu, that helps users to create a virtual environment to run AmigaOS 4, MorphOS and AROS. It is not possible for Kyvos to access the virtual hard disks and make any changes to them. That's why Kyvos cannot (for now) make any changes to the OS that is running in the Virtual Machine, which means it cannot apply the updates. The updates are needed for the required kickstart.zip file to be created so that the users do not need to do it themselves. Quote: Question 1: Any ideas how to get the Kyvos VM creation wizard to automatically install update 1,2 and 3? Not possible for now. If that was possible, the manual would say so, wouldn't it? Quote: I tried various attempts to configure the MacOS file sharing settings and checking Homebrew to install Samba but I still cant get OS4.1 to detect a shared folder on my Mac. I am sorry but I cannot help you much with it. Maybe someone who might have already done something like that. Quote: Question 2: Any ideas on how to get SMB working in OS4 under Kyvos? There are some generic guidelines in the manual but as stated there, this is something that can vary from system to system, and the user needs to figure it out how it can be done. Generally speaking, if you make a folder available using samba then it should be accessible by the qemu as well as described in the Kyvos manual. Quote: ...instead I created partition as DH2 using SFS00 and check marking auto mount, bootable and boot priority is still 0. If you do not intend to install the system on that partition, and boot from it, there is no need to set it as bootable. Quote: Each time I reboot the VM, OS4.1 still cannot detect DH2 for some unknown reason. Did you format this partition? From the System > Format utility, if you see the partition there, you could format it. Also check the System > Mounter and see if that is showing up there as well. Quote: Question 3: Any ideas on what I am doing wrong in getting the 2nd hard drive to be detected in OS4.1. I tried various size of 2GB, 4GB and 20GB but still no luck? I cannot be sure, to be honest. If you could share any screenshots of the mediatoolbox and the configuration you did there, that would be helpful.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/25 20:00
#62
|
Site Builder 
|
@balaton Quote: Maybe we need a simpler way to update Kickstart.zip but it should not be too difficult to do that after each update. At least users would be trained to not forget that after the next update. To be honest with you, I do not expect that users will do it, as they haven't done it the past 2 years. If the whole process would be easy, tools like Kyvos would not be necessary. In my view the errors that need to be ignored are minor, against doing the kickstart.zip file manually, knowing what exactly to change and updating the kicklayout as well. I do not know if there could be a version of bboot that could boot the system and let the kickstart modules to be loaded from the OS hard disk. This way, no mambo jumbo would be needed. Quote: I can't easily have a look at the Kyvos docs if it can't be downloaded freely without hassle so don't know what's in the latest version. I've only seen an early version once but I forgot that too. The manual as well as the Kyvos application are freely available to everyone. Now, sure, it requires you to use a fake email to get access to the files. You know, the most requested feature is that Kyvos do all the installation automatically without the user needing to do anything, just provide the files. This is something I am thinking to add at some point as soon as I solve some blocks. Users need as less manual steps as possible, and I believe that Kyvos provides that, but it can get better. But it is also a new tool, with just a few months being released.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/25 19:37
#63
|
Site Builder 
|
@cloverskull You can buy the Pegasos 2 digital version from https://hyperion-entertainment.com/ind ... final-edition-for-pegasos@balaton As derfs said, that error with the USBCtrl was there even with the update2 files in the kickstart.zip. Sure, the best thing would be the kickstart.zip file to follow the installed system files, but that would require the user to update the zip file 4 times manually, which is not ideal. The ideal situation would be Hyperion to release a new ISO that include all the updates, but that is also not something available right now. So I work with what I have. The installation is working with all 3 updates just fine, except of these small hickups here and there, that are clearly described in the manual that comes with Kyvos, which needs a good update now that Update 3 is released. Furthermore, I would like to thank you for providing help to people who use Kyvos, although as you said you do not know how it works, and clearly you haven't used it. That shows to me how useful you find my tool. I hope one day to see a reference to Kyvos in your website, pointing more users to find and use it. @AmigaNG Thank you for confirming that it works now for you. And thank you for reporting the issue. When you use it again, if you have any issues, do me a favour and have a look in the manual first. Especially the FAQ section.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/25 12:46
#64
|
Site Builder 
|
@AmigaNG I just released the Kyvos 1.6.1 with the following changes
## 1.6.1 [2025-10-25] ### Fixed - Fixed an issue with the SiliconMotion502 driver being used when the HOME path had spaces
@balaton The problem was not in the qemu arguments, but in the process of creating the kickstart.zip file.
Some of the qemu arguments are breaking the execution on Windows when the path is escaped. At least that's what happened when I last tested it. That's why some paths are not escaped. I will try again with the latest version and I will see whether this is working better or not.
Thank you for your recommendation and your help.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/25 12:08
#65
|
Site Builder 
|
@AmigaNG I managed to reproduce the issue. That has to do with the spaces in the HOME path. I will have a fixed version as soon as possible for you. I will let you know here when it is released.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/25 11:39
#66
|
Site Builder 
|
@AmigaNG Can you please create a new VM using the automated way and let me know if the siliconmotion driver is inside the kickstart.zip file? The only I can think for this being missing is that there is a bug with Kyvos when the HOME folder has spaces, like yours. I am going to try to reproduce it and will get back to you. That was not reported before by anyone else, that's why I am asking you try that again, if possible.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/24 17:59
#67
|
Site Builder 
|
@AmigaNG The kickstart.zip file is created in the VM folder. That path is mentioned in Kyvos in the information tab, when you select a VM. There is also an icon beside it to open that folder automatically for you.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/24 15:10
#68
|
Site Builder 
|
@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) I believe there is a mention in the FAQ section
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/24 13:42
#69
|
Site Builder 
|
@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.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/24 11:26
#70
|
Site Builder 
|
@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.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/24 10:17
#71
|
Site Builder 
|
@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. Please let me know the results you got.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/24 9:45
#72
|
Site Builder 
|
@dwolfman Thank you for that information. I will double-check today if there is an issue and I will get back to you
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/23 19:04
#73
|
Site Builder 
|
@dwolfman Quote: 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. Yeap, this is on my roadmap list https://pms.walkero.gr/projects/kyvos/roadmap for the next version.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/23 14:02
#74
|
Site Builder 
|
@ilbarbax Thank you for your proposal. I will add that information.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/22 15:15
#75
|
Site Builder 
|
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.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/22 9:42
#76
|
Site Builder 
|
@Vulture Quote: Is it possible to support molk... Can you please share a little bit more information what molk is and where can I find it? @ilbarbax Quote: That means that I have to create a different directory for any OS/VM? I guess you used the advanced method of creating the VMs, right? The Automatic method always creates a separate folder for each VM, and that's where it puts the config.json file for each VM. I have some information about that file and the differences between Automatic and Advanced method in the manual that is provided as a separate download with Kyvos.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/20 21:47
#77
|
Site Builder 
|
@ilbarbax I have never seen that issue. I apologize for that experience. As you can imagine, I am switching between multiple VMs on my test environment all the time, especially when I am introducing new features.
Can you please write me down the steps that I need to follow to reproduce it? Try to create a new VM and write me what steps you followed until that breaks. That would be quite helpful.
@joerg Thank you for that clarification and for explaining to me how it works. Quite helpful.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/20 7:49
#78
|
Site Builder 
|
@ilbarbax Quote: Another issue I got is that on my real Sam I have two hd one for os4 and the second for mos, I can see the mos hd from os4 and vice versa. Here I tried to load the mos hd img under os4 emulation using the 2nd hd or third hd but they are not mounted How did you make the images from the hard disks? The AmigaOS 4 should see the MOS partitions just fine as long as they are based on SFS. Maybe the way the disk images were created prevents them to be mounted properly. Or, if you do not see them on workbench, try the Mounter tool under the System drawer, in case they are not auto-mounted. @dwolfman Quote: A suggestion for future versions would be to have a button show somewhere to re-run that kickstart.zip creation process on an existing instance. That is a great idea. I will add it in my todo list. At least for now there is a workaround to do that as you described it. Create another VM and copy the kickstart.zip file, as long as you create the same type of system, i.e. create an AmigaOS 4 - Pegasos 2 to replace the same type of kickstart. I am really sorry for your experience with Ko-fi page. Unfortunately, internet is getting worse every year. I hope that they will resolve these issues as soon as possible.
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/19 16:13
#79
|
Site Builder 
|
@AMIGASYSTEM I will have a look into that. Thank you for your continuous work.
@ilbarbax Thank you so much for you suggestions. Please have a look at my answers below.
1. Unfortunately, I haven't found a way to set boot priorities that it actually works. Whenever the AmigaOS ISO is used, it boots from that. It might be a limitation of using bboot, but I can be completely wrong on that.
2. In general, the path should not change. But if you move it somewhere else, you need to set up a new VM using the Advanced method and set everything based on the new place. But I will note that as a feature for a later release. At least to make it easier for the users. How crucial is it for you?
|
|
|
|
|
|
Re: Kyvos was updated
|
Posted on: 2025/10/16 18:39
#80
|
Site Builder 
|
I am delighted to inform you that I just released a new version of Kyvos, with the following changes: ## 1.6.0 [2025-10-16] ### Added - Added pid files to be saved in the .kyvos folder. This will be set on VM creation or update - Added support for the "AmigaOS4.1 FinalEdition Update 3", if that is available (optional). Kyvos is looking for a file named "AmigaOS4.1FinalEditionUpdate3.lha". If that exists in the same folder as the AmigaOS 4.1 FE ISO, then it will be used when the kickstart.zip file is created. ### Changed - Enabled the virtio-gpu options for Sam460 systems. This driver is not coming with Kyvos - Changed old pidfile arguments to be saved to the ./kyvos folder under HOME This can be found at https://ko-fi.com/s/6476fdadd2
|
|
|
|
|
|