MichaelPetch wrote:
When I wrote that bootloader code it was specifically for Floppy Disk media. I'm wondering if the way you built the ISO, burned it and then set your BIOS to boot has done something. Possibly you need to change the bootloader code to use int 13h/ah=42h. An enhancement to the code I wrote would be to check if the drive you are reading supports extended disk BIOS functions and use them. If it doesn't it falls back to int 13/ah=2h.
Right now, the process of building the ISO, burning it, and what your BIOS is set to is likely factoring into this. At this point I highly doubt it is a buggy BIOS for this kind of thing. It seems you are using Windows to burn your image? I'd try using
Chryscome's DD for Windows to place disk.img onto the USB drive directly and then set the BIOS to boot using Floppy Disk Drive emulation. I wrote a Stackoverflow Article (the second part) that includes instructions on using it:
https://stackoverflow.com/a/36052385/3857942 .
In Windows with a console window in Administrator priveleges you could issue a command like:
dd if=disk.img od=<driveletterofUSB>: bs=512
Where
driveletterofUSB is the drive letter followed by a colon.Note it doesn't use
of= it uses
od= which is special to this version of DD for Windows. Once DD'ed you need to safely eject the USB device (right mouse click the USB device icon on the task bar at the bottom) to ensure all the data is properly flushed to the USB device.
I get this error from dd (Windows)
Code:
rawwrite dd for windows version 0.6beta3.
Written by John Newbigin <
[email protected]>
This program is covered by terms of the GPL Version 2.
Device d: is a link to \\?\Device\HarddiskVolume31
\\?\Device\HarddiskVolume31 is a partition on \Device\Harddisk1
0 Error writing file: 5 Acceso denegado
0
1+0 records in
0+0 records out
Using this flags:
Code:
dd if=disk.img od=d: bs=512
Tried using D: and D:\, with no luck...
Ugh, what a bad luck I have!
(I'm in Administrator mode)