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
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)
On Tue, Jun 12, 2007 at 04:16:59PM +0200, adrian15 wrote:
Can you ellaborate? From the code you pasted, I just see that when
interactive is set to 0, this has the same effect as pager being set to
the 0 string.
That's what I mean. I think that interactive for grub2 means being in
the
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 report (see
On Wed, Jun 13, 2007 at 01:37:15AM +0800, Bean wrote:
On Tue, Jun 12, 2007 at 03:54:12PM +0200, Robert Millan wrote:
Is there any reason why grub_prefix is in boot.img rather than core.img ?
This brings problems when the following conditions are met:
- core.img is loaded directly
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 called the
Bean [EMAIL PROTECTED] writes:
[...]
Another thing I notice, the blocklist command generate messy result when
compared to GRUB Legacy, is it supposed to be so ?
What do you mean? Can you give an example?
BTW, is it possible for me to join the GRUB2 development term ? I really
want to help
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, 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
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
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 different emulator
hi,
i gone thru this link : http://grub.enbug.org/MemoryManagement
i am not able to get the following images.
http://www.inma.ucl.ac.be/~guffens/images/grub2/mem_after_init.jpg
http://www.inma.ucl.ac.be/~guffens/images/grub2/allocation_ring.jpg
These ideas are mostly from grub4dos, I think they can be useful in GRUB2.
1. cat
In addition to the current function, cat can also generate hexadecimal dump,
and it can optionally choose the range of bytes to display. For example:
cat [--hex] [--skip=S] [--length=L] FILE
Sometimes it's
13 matches
Mail list logo
