Kyvos, for the problems mentioned, the mystery has been solved as to why CDs, DVDs and HD images are not detected from other paths.
Basically, on Windows, if an ISO or HD image is located in ‘Program Files’ or another directory with a split name (with a space), Kyvos cannot find the file.
I tried adding the path in quotation marks, but it doesn't work!
Maybe within the directory you gave for the VM (or what Kyvos selects automatically, I don't know how it works, never tried)? But I'd look for it where other files like disk images are.
@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.
I opened the kickstart.zip it didnt have the silicomotion502.chip in it, so I added that.
still no change.
You also need to add it to Kicklayout, just adding the file won't load it. BBoot prints what it loads so you can check if siliconmotion502.chip was in the list.
Only needed for AmigaOS versions before 4.1FE (i.e. original 4.1) the final edition should have new enough PCIGraphics.card version.
Quote:
This is why I was hoping Kyvos made it easier, thanks for all your help so far. I dont know what I done wrong.
Maybe haven't read the right documentation. I've tried to make navigation easier by adding links at the top on my page. Go to https://qmiga.codeberg.page/ (in my signature in all my posts). Select OS and machine you want to run which should take you to AmigaOS section where there's a link saying See separate page describing the easiest way to install AmigaOS using BBoot Then just read that page and follow what's written there. I've already linked to this page above but you read a different page with a more complex older method (which should also work but the newer BBoot way is simpler).
this is commands that sent to qemu and check files locations that everything there, should vga say none?
Yes, -vga none disables the default VGA which does not work with AmigaOS and -device sm501 adds the sm501 which is functionally the same as sm502 that's found on sam460ex so AmigaOS has a driver for it but it's only on the Sam460EX install CD so has to be added manually for other machines. BBoot loads modules from the file specified in -initrd which is Kickstart.zip so the driver needs to be added there. All AmigaOS boot loaders read Kicklayout file from Kickstart dir to find what to load so only copying a file there is not enough it also has to be added to Kicklayout as described on my page.
Kyvos should do that so unless you somehow replaced the Kickstart.zip I don't know how could you break it. Or maybe you managed to get Kyvos generate a Kickstart.zip before you had the siliconmotion502 driver lha then it did not regenerate it when you downloaded that. Maybe delete the whole VM and start again now that you have all needed files.
@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.
@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.
@walkero The QEMU command line posted above by AmigaNG has some unquoted paths. You should make sure that all paths or strings provided by the user are quoted when passed on to something else (and check that there are no quotes inside the string that could unquote them and escape those too).
@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.
@walkero I don't know about Windows but -initrd should work with quotes and for -drive option I usually put file= at the end and this should also work: -drive media=disk,format=raw,file="what ever path here" If that does not work you could search for spaces in paths and add \ before them to escape them, I think that also works on Windows too. (Just don't \ escape and quote both as that won't work again; one or the other.)
Anyone know where I can buy a copy of AmigaOS4.1FE for AmigaONE XE? Or Pegasos II or Sam460ex? I can't find these CDs for sale anywhere and I need to use them to make Kyvos work. Ugh frustrating.
Anyone know where I can buy a copy of AmigaOS4.1FE for AmigaONE XE? Or Pegasos II or Sam460ex? I can't find these CDs for sale anywhere and I need to use them to make Kyvos work. Ugh frustrating.
Unfortunately the best AmigaOS 4.1 version for QEmu, the AmigaOne version, doesn't seem to be available anywhere any more.
so unfortunately dont have full time to install and play around with this now until Wens when I'm next off work, but I had to have a quick go to see if this fix worked, and happy to report....
(it does say USBCtrl error, but like I say i dont really have time to set it up today, but just wanted to see if the fix worked it did!!! Thank You!)
Quote:
AmigaOS 4.1 version for QEmu, the AmigaOne version, doesn't seem to be available anywhere any more
I know, the odd thing is I waited until Amiga Germany 40 to see if I could get a copy, I didnt see one for AmigaOne XE, only the Pegasos2 version that Hyperion said had sold out!? Which is odd, I saw about 7 copies for Pegasos2. So I bought one as it was 10 euro cheaper than buying from Hyperion. :)
@derfs The USB error seems to happen at booting the install CD so no updates are installed yet. Maybe it's result of Kyvos taking files from Update 3 other than kernel (maybe the new kernel does not work without those)? I can imagine, because Update 3 is just released, using it at install is not well tested. So maybe it's safer to install with only Update 2 as before that is known to work. That will still result in an unapdated system at 4.1FE which only has new kernel from Update 2 for the siliconmotion502.chip driver so one may then need to go through Update 1, Update 2 and only then install Update 3. This might confuse new users a lot. Even I'm not sure what is the right way to do this so I could be wrong. Having version numbers like 4.1 Update 3 and 4.1FE Update 3 that refer to completely different versions probably also does not help. So setting up AmigaOS is a challenge but may be part of the fun for some to feel they achieve something when it finally succeeds
@joerg thanks for the response. I'll never understand why I can't just buy a digital copy direct from Hyperion. I guess this project is on hold for me...
This also happens when using Update 2 files so its not a new issue, and is not restricted to using kyvos.
Yes, it is due to using newer files to build the Kickstart.zip when installing from the original FE4.1 iso. Other weird things can happen if some things are done out of order when installing (such as AmiUpdate not working), so Walkero has a full installation guide in the kyvos manual making it a pain-free and easy process.
Users will always have to install update 1, 2 and 3 as there is no 'combined' iso that has all the latest files in it.
Essentially, the USBCtrl message can be ignored and closed, and will not show when update 2 has been installed.
@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.
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
