Activity for esotechnica
-
esotechnica posted a comment on discussion General Discussion
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.
-
I'm sorry does anyone know how to change the title?
-
I am hoping someone may shed some light on some odd behaviour I am seeing. I am running a PC-DOS 1.1 image (boots from drive A:) and have another disk in drive B: The A: image is a 160K image of PC-DOS 1.1, with B: being a 320K zeroed-out image, made with dd if=/dev/zero, of=320k.img bs=1024 count=320. Booting the system from A: works fine. I then attempt to format B: and get the following strange output: As you can see none of the output makes sense for a 320k disk. Running a dir on B: I get 96...
-
All good, it was a SF server issue...
-
Remove excessive forward slashes from file paths
-
Removed excessive forward slashes from InstallDir path. This causes rEFInd to fail in locating the ESP if it hasn't already been mounted. This is because refind-install searches mtab for the string //boot/efi, which it will never find. If the ESP is already mounted, this error does not occur. This bug may have gone unnoticed because running refind-install a second time after the first attempt will run correctly (since the ESP is already mounted).
-
I want to create a fork of this project, but it just gets stuck on "Repo Status: cloning..." with the spinner that has been going for over an hour now. I'm new to this and am not sure what I am doing, but I'm just following the steps in the video for forking that is on the doco page. Any ideas?
-
I've identified the problem. I have an EXT4 partition mounted in Windows using Paragon ExtFS. Win32DiskImager works after unmounting this drive. Not sure if this is documented (does this come under ramdisks? I'm not sure?)
-
Application crashes at startup
1