esotechnica

I'm curious as to how the kernel manages to load the initrd image once execution is handed off to the kernel after rEFInd loads it. My understanding is that rEFInd loads the kernel into memory, and executes it just like any other EFI application, passing it the kernel command line parameters (including 'initrd=xxx' parameters). But how does the kernel then load the initrd image? My understanding is that the kernel has no filesystem drivers (isn't this the whole point of initial ramdisks?), and in...

I found the culprit, all of the ATAx config lines had enabled=0.

I can't get bochs to boot from my hard disk image. The image is just a 512 byte boot sector. Attached are the image, my bochsrc, and bochsout.txt. I've also attached screenshots showing how I have run bochs, and a hex dump of the boot sector. I've tried many different things but have no idea what I'm doing wrong. Can anyone help?

Same behaviour occurs in qemu. This makes me suspect it is a bug in PC-DOS 1.1

Fantastic, it works! Thanks for your help. It's interesting that if you do format b: /s it works, but if you do format b:, followed by sys b:, it won't work. It still says 'No room for system on destination disk'

@vruppert I've used what I think is the SeaBIOS modules ($BXSHARE/bios.bin-1.13.0 and $BXSHARE/vgabios-cirrus.bin-1.13.0). But now it doesn't do anything at all. Every time I press c to continue execution, it just keeps returning to the BIOS entry point (F000:FFF0).

OK thanks for your effort. I will try using this BIOS.

Thank you for changing it. However I still can't see where to edit the title. I can edit the contents of the post with the edit button. There doesn't seem to be an icon near the title bar, there's just the 'Follow This' and 'Unsubscribe from this topic' icons.