Re: [PATCH] Create floppy emulation boot CD with grub-mkimage

[Christian Franke <Christian.Franke@t-online.de>]

Bean wrote:
> On Feb 10, 2008 12:53 AM, Christian Franke <...> wrote:
>   
>> ...
>> Results:
>>
>> PC: grub_boot_drive=0x9f, but INT13 Extensions reported for 0x9f
>>
>> VMware: grub_boot_drive=0x9f
>>
>> VirtualPC: grub_boot_drive=0xef
>>
>> VirtualBox: grub_boot_drive=0xe0
>>
>> GRUB_MOD_INIT(biosdisk) detects INT13 Extensions for 0x9f on the real
>> PC, therefore "(cd0)" does not appear in "ls" output.
>> Nevertheless, access to (cd0) and everthing else works as expected due
>> to the default setting of
>> biosdisk.c::cd_start = 0x9f.
>>
>> ...
>>     
>
> I don't know which drive to start scanning for cdrom. 0x9F means at
> most 31 hard drives, i think it's fine for the most time.
>
>   

Agree.

Sorry, my info was wrong, it should read:

PC: Reports INT13 Extensions *not* available for drive 0x9f.

All VMs: INT13 Extensions available for grub_boot_drive.


CD device scanning fails if BIOS reports no INT13 Extensions for the 
boot CD drive. I will post a patch in a new thread.
Please apply your init.c "(cd0" patch also, as it is necessary if 
grub_boot_drive is not equal to ..._CDROM_START.

Christian