Re: Windows,grub and grub2

[Viswesh S <viswesh_vichu@yahoo.com>]

[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]





----- Original Message ----
From: Bean <bean123ch@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Sent: Thursday, 4 September, 2008 11:07:46 PM
Subject: Re: Windows,grub and grub2

On Tue, Sep 2, 2008 at 1:01 AM, Viswesh S <viswesh_vichu@yahoo.com> wrote:
>
>
> ----- Original Message ----
> From: Bean <bean123ch@gmail.com>
> To: The development of GRUB 2 <grub-devel@gnu.org>
> Sent: Monday, 1 September, 2008 9:05:48 PM
> Subject: Re: Windows,grub and grub2
>
> On Mon, Sep 1, 2008 at 11:27 PM, Viswesh S <viswesh_vichu@yahoo.com> wrote:
>>
>>
>
> Hi,
>
> Perhaps you can upload the boot sector file ? I can dissemble it to
> see where the error is printed.
>
> --
> Bean
> Hi,
>
>
> I was just trying out a way to disassemble it, as objdump didnt give it to
> me.I think I am not giving the right option,I suppose for binary.Let me know
> how to disassemble the binary.
>
>
>
> I have attached the boot record.

>Hi,
>
>I'm sorry for the delay, I'm a little busy in the last few days.
>
>I have disassemble the boot sector, there are three places where the
>error could occur, please chain load the file in the attachment and
>write down the screen output:
>
>chainloader /ntfsnew
>boot
>
>-- 
>Bean


Hi,

Below is the dump of screen output while chainloading the ntfsnew file.
***************************************
DI=CFF0 SI=07EE BP=1FF0 SP=1FE8 BX=0000 DX=0000 CX=0000 AX=0000
CS=0000 SS=0000 DS=0000 ES=0000 FG=0246 IP=7C57

DI=7FF0 SI=07EE BP=1FF0 SP=7BF4 BX=55AA DX=0000 CX=0000 AX=0100 CX=07C0
DS=07C0 ES=0000 FG=0007 IP=0082
******************************************
Could you please let me know the way to disassemble the binary file without any header.The way in which you decoded the boot record.

Also one more thing to let you know is that,

with the grub-1.96 ( without the chainloader patch of disk->dev->read() ) , with windows2003 in partition 1 and linux in partition 3, when we chainload, if we look at the partition table passed to another bootloader ie location 0x7be - we can see that it is junk, but the surprising point is that, in this case as I have mentioned in my first mail, windows boots up from grub2.So it is that the partition table is not required for the chainloader thing and just the boot record is sufficient

Viswesh



      Add more friends to your messenger and enjoy! Go to http://in.messenger.yahoo.com/invite/

[-- Attachment #2: Type: text/html, Size: 5038 bytes --]