maybe the kicklayout needs to be fixed..

hmm strange.. i updated to the latest updates via amiupdate, and installed the silicon motion driver and then made a new kickstart.zip but now it stopped booting here:

Loading uhci.usbhcd
Loading ohci.usbhcd
Loading ehci.usbhcd
Loading mounter.library
Starting exec

amiupdate always says that it fails to connect the first time i launch it, is this normal?

OK, i found out that it's the hyperion login, os updates downloading now..

"If you have chosen to install via BBoot/Kickstart, you should install Update1 and Update2 via AmiUpdate to bring your system up to date. Once you've done that, add the new siliconmotion502_chip to your Kickstart folder SYS:Kickstart/. You now have to take the entire Kickstart folder again from your installed system AmigaOs4.1 and create Kickstart.zip again and reassign BBoot Kickstart.Zip with updated modules from Update 1 and 2."

How do i list os updates in amiupdate?
I only got regular updates. It did prompt me for a login/pw though, which login is that?

@Maijestro

Ah, i just noticed. Memories coming back slowly.

@AmigaOldskooler

i settled for odyssey, seems to work for what i need it for.. mostly.

It's been around 10 years since i used amigaos4, but, uhm, i seem to remember it having a wbstartup drawer?
My install doesn't?

Ah.. for some reason the fullscreen gadget is greyed out in macos.. but the view/enter fullscreen menu item worked. cool.

Can i use a bigger resolution than 1280x720?
How do i get qemu to go fullscreen?

Who knows!? :D X-mas is coming up!
I don't promise anything though, mainly playing around.
I have a booting wb now anyway, is odyssey the browser of choice thest days?

OK, hehe nevermind. My system partition wasn't bootable.
I fixed that, now it boots. I first got a very low-res hardly readable screen but was able to select a proper one.

After a reboot it seems to have the wrong kickstart files and doesn't boot or something...

Can i share files between the mac and qemu somehow?

Installer is doing it's thing now, cool!

Ooooooooh.... bummer! I made some progress!
I had the os4 iso mounted, that's why it couldn't access it.
*Facepalm!*

The commandline used in the guide gives me this as well:

spot@BMS-MAC01 8.1.3_2 % qemu-system-ppc -machine pegasos2 -rtc base=localtime \
-serial stdio -vga none -device sm501 \
-drive media=disk,format=raw,file=amigahd.img \
-cdrom Peg2InstallCD.iso \
-kernel bboot -initrd Kickstart.zip
qemu-system-ppc: -cdrom Peg2InstallCD.iso: Failed to lock byte 100

This is the commandline i tried right now, i tried a few different ones from different guides.

spot@BMS-MAC01 8.1.3_2 % qemu-system-ppc -L pc-bios -M pegasos2 -bios pegasos2.rom -m 1024 -serial stdio \
-vga none -device sm501 \
-drive if=none,id=hd,file=Peg2InstallCD.iso,format=raw \
-device ide-hd,drive=hd,bus=ide.0 \
-drive if=none,id=cd,file=Pegasos2InstallCD-53.54_modified_with_drivers_for_sm501.iso,format=raw \
-device ide-cd,drive=cd,bus=ide.1 \
-device rtl8139,netdev=network00 -netdev user,id=network00
qemu-system-ppc: -drive if=none,id=hd,file=Peg2InstallCD.iso,format=raw: Failed to lock byte 100

Hello... i recently bought an amigaos4 pegasos II cd to try this..
But no matter what i do, i get this error when i try to start it:

qemu-system-ppc: -drive if=none,id=hd,file=Peg2InstallCD.iso,format=raw: Failed to lock byte 100

I am on an M1 mac if that matters.

Help!

And also the latest version of the Protracker clone ofcourse:
https://github.com/8bitbubsy/pt2-clone

Hot tips for porting, a Fast Tracker II clone:
https://github.com/8bitbubsy/ft2-clone