On 13/06/07, Alex Roman <[EMAIL PROTECTED]> wrote:
We might have to read the boot catalog manually, not with the 4Dh
function to achieve more compatibility. Tonight I'll try to do an
"Extended Read", function 42h, to get the boot catalog and parse it in
a structure and see if it "makes sense".
On Wed, Jun 13, 2007 at 07:55:38PM +0200, Jeroen Dekkers wrote:
> > > "FATAL: Int13 eltorito call with AX=4D00. Please report" (see screenshot)
> > >
> > > ... which I will (report, that is) :)
> > >
> > > But I thought I'd share the find first.. Looks like I'm going to have
> > > to use either a
On 13/06/07, Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
Alex Roman wrote:
El Torito part of the EDD3 spec might not be accessible if you have not
booted with such media that needs that support. At least this seems to
be case with VMWare which uses Phoenix BIOS. I once tested out those
CD-ROM a
On 13/06/07, Bean <[EMAIL PROTECTED]> wrote:
I think the bios service is not reliable, the best way to access cdrom is to
use ATAPI command directly.
That is the second stage of my project... the first stage is to make
this work using BIOS Int 13h which will be useful since it provides
compati
On Wed, Jun 13, 2007 at 08:33:02AM -0400, Alex Roman wrote:
> I've been messing around with int 13h calls and it seems that the QEMU
> BIOS supports EDD 3 extensions.
>
> However, it does not support ElTorito extensions... I called the 4D
> function (Return Boot Catalog) and the QEMU BIOS (I think
At Wed, 13 Jun 2007 16:28:42 +0200,
Robert Millan wrote:
>
> On Wed, Jun 13, 2007 at 08:33:02AM -0400, Alex Roman wrote:
> > I've been messing around with int 13h calls and it seems that the QEMU
> > BIOS supports EDD 3 extensions.
> >
> > However, it does not support ElTorito extensions... I cal
Alex Roman wrote:
> On 13/06/07, Alex Roman <[EMAIL PROTECTED]> wrote:
>> However, it does not support ElTorito extensions... I called the 4D
>> function (Return Boot Catalog) and the QEMU BIOS (I think) printed a
>> "nice" informative message:
>> "FATAL: Int13 eltorito call with AX=4D00. Please re
On Wed, Jun 13, 2007 at 08:33:02AM -0400, Alex Roman wrote:
> I've been messing around with int 13h calls and it seems that the QEMU
> BIOS supports EDD 3 extensions.
>
> However, it does not support ElTorito extensions... I called the 4D
> function (Return Boot Catalog) and the QEMU BIOS (I think
On 13/06/07, Alex Roman <[EMAIL PROTECTED]> wrote:
However, it does not support ElTorito extensions... I called the 4D
function (Return Boot Catalog) and the QEMU BIOS (I think) printed a
"nice" informative message:
"FATAL: Int13 eltorito call with AX=4D00. Please report" (see screenshot)
Furth
I've been messing around with int 13h calls and it seems that the QEMU
BIOS supports EDD 3 extensions.
However, it does not support ElTorito extensions... I called the 4D
function (Return Boot Catalog) and the QEMU BIOS (I think) printed a
"nice" informative message:
"FATAL: Int13 eltorito call w
10 matches
Mail list logo
