From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KcwHT-0006kY-Ce for mharc-grub-devel@gnu.org; Tue, 09 Sep 2008 02:00:51 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KcwHR-0006js-Df for grub-devel@gnu.org; Tue, 09 Sep 2008 02:00:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KcwHM-0006iv-ID for grub-devel@gnu.org; Tue, 09 Sep 2008 02:00:48 -0400 Received: from [199.232.76.173] (port=54929 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KcwHM-0006is-Cu for grub-devel@gnu.org; Tue, 09 Sep 2008 02:00:44 -0400 Received: from web31601.mail.mud.yahoo.com ([68.142.198.147]:27024) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1KcwHL-0007Qx-SW for grub-devel@gnu.org; Tue, 09 Sep 2008 02:00:44 -0400 Received: (qmail 19975 invoked by uid 60001); 9 Sep 2008 06:00:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=uugMYFoycPb+wf/4O5LcZf371Z6BUFN1jOUP4tBts1YPznyLjRNwmSe7rrhdJNHQTUJrzu09I50TA0lmYiM0b9rL3YCITj6STgeyQh6LuesRppuyjvJdclJoRLRP6FAlYVG4+0CASH7WID2McnOhl+tSkZYbbOMIM+++c3KNtos=; X-YMail-OSG: 6klXB2gVM1l6wLIVv3Iz2oTy9tl9JGhWAz4_CbKgGXtZGBVh5Q0LYpNiYxoUCg8X1Q-- Received: from [202.62.94.130] by web31601.mail.mud.yahoo.com via HTTP; Mon, 08 Sep 2008 23:00:42 PDT X-Mailer: YahooMailRC/1096.28 YahooMailWebService/0.7.218.2 Date: Mon, 8 Sep 2008 23:00:42 -0700 (PDT) From: Viswesh S To: The development of GRUB 2 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-946609160-1220940042=:18774" Message-ID: <298286.18774.qm@web31601.mail.mud.yahoo.com> X-detected-kernel: by monty-python.gnu.org: FreeBSD 6.x (1) Subject: Re: Windows,grub and grub2 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2008 06:00:49 -0000 --0-946609160-1220940042=:18774 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable =0A=0A=0A=0A----- Original Message ----=0AFrom: Bean = =0ATo: The development of GRUB 2 =0ASent: Thursday, 4 S= eptember, 2008 11:07:46 PM=0ASubject: Re: Windows,grub and grub2=0A=0AOn Tu= e, Sep 2, 2008 at 1:01 AM, Viswesh S wrote:=0A>= =0A>=0A> ----- Original Message ----=0A> From: Bean = =0A> To: The development of GRUB 2 =0A> Sent: Monday, 1= September, 2008 9:05:48 PM=0A> Subject: Re: Windows,grub and grub2=0A>=0A>= On Mon, Sep 1, 2008 at 11:27 PM, Viswesh S wrote= :=0A>>=0A>>=0A>=0A> Hi,=0A>=0A> Perhaps you can upload the boot sector file= ? I can dissemble it to=0A> see where the error is printed.=0A>=0A> --=0A>= Bean=0A> Hi,=0A>=0A>=0A> I was just trying out a way to disassemble it, as= objdump didnt give it to=0A> me.I think I am not giving the right option,I= suppose for binary.Let me know=0A> how to disassemble the binary.=0A>=0A>= =0A>=0A> I have attached the boot record.=0A=0A>Hi,=0A>=0A>I'm sorry for th= e delay, I'm a little busy in the last few days.=0A>=0A>I have disassemble = the boot sector, there are three places where the=0A>error could occur, ple= ase chain load the file in the attachment and=0A>write down the screen outp= ut:=0A>=0A>chainloader /ntfsnew=0A>boot=0A>=0A>-- =0A>Bean=0A=0A=0AHi,=0A= =0ABelow is the dump of screen output while chainloading the ntfsnew file.= =0A***************************************=0ADI=3DCFF0 SI=3D07EE BP=3D1FF0 = SP=3D1FE8 BX=3D0000 DX=3D0000 CX=3D0000 AX=3D0000=0ACS=3D0000 SS=3D0000 DS= =3D0000 ES=3D0000 FG=3D0246 IP=3D7C57=0A=0ADI=3D7FF0 SI=3D07EE BP=3D1FF0 SP= =3D7BF4 BX=3D55AA DX=3D0000 CX=3D0000 AX=3D0100 CX=3D07C0=0ADS=3D07C0 ES=3D= 0000 FG=3D0007 IP=3D0082=0A******************************************=0ACou= ld you please let me know the way to disassemble the binary file without an= y header.The way in which you decoded the boot record.=0A=0AAlso one more t= hing to let you know is that,=0A=0Awith the grub-1.96 ( without the chainlo= ader patch of disk->dev->read() ) , with windows2003 in partition 1 and lin= ux in partition 3, when we chainload, if we look at the partition table pas= sed to another bootloader ie location 0x7be - we can see that it is junk, b= ut the surprising point is that, in this case as I have mentioned in my fir= st mail, windows boots up from grub2.So it is that the partition table is n= ot required for the chainloader thing and just the boot record is sufficien= t=0A=0AViswesh=0A=0A=0A=0A Add more friends to your messenger and enjo= y! Go to http://in.messenger.yahoo.com/invite/ --0-946609160-1220940042=:18774 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

=0A

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

On Tue, Sep 2, 2008 at 1:01 AM, Viswesh S <<= A href=3D"mailto:viswesh_vichu@yahoo.com" ymailto=3D"mailto:viswesh_vichu@y= ahoo.com">viswesh_vichu@yahoo.com> wrote:
>
>
> --= --- Original Message ----
> From: Bean <bean123ch@gmail.com= >
> To: The development of GRUB 2 <grub-devel@gnu.org><= BR>> Sent: Monday, 1 September, 2008 9:05:48 PM
> Subject: Re: Win= dows,grub and grub2
>
> On Mon, Sep 1, 2008 at 11:27 PM, Viswes= h S <viswesh_vichu@yahoo.com> wrote:
>>
>>
= >
> Hi,
>
> Perhaps you can upload the boot sector fil= e ? I can dissemble it to
> see where the error is printed.
>> --
> Bean
> Hi,
>
>
> I was just tryin= g out a way to disassemble it, as objdump didnt give it to
> me.I thi= nk I am not giving the right option,I suppose for binary.Let me know
>= ; how to disassemble the binary.
>
>
>
> I have att= ached the boot record.

>Hi,
>
>I'm sorry for the dela= y, I'm a little busy in the last few days.
>
>I have disassembl= e the boot sector, there are three places where the
>error could occu= r, please chain load the file in the attachment and
>write down the s= creen output:
>
>chainloader /ntfsnew
>boot
>
>--
>Bean
=0A
 =0A
Hi,
=0A
 
=0A
Below is the dump of screen output while chainl= oading the ntfsnew file.
=0A
***************************************=0A
DI=3DCFF0 SI=3D07EE BP=3D1FF0 SP=3D1FE8 BX=3D0000 DX=3D0000 CX=3D0000 A= X=3D0000
=0A
CS=3D0000 SS=3D0000 DS=3D0000 ES=3D0000 FG=3D0246 IP=3D7C57=
=0A
 
=0A
DI=3D7FF0 SI=3D07EE BP=3D1FF0 SP=3D7BF4 BX=3D55AA DX= =3D0000 CX=3D0000 AX=3D0100 CX=3D07C0
=0A
DS=3D07C0 ES=3D0000 FG=3D0007 = IP=3D0082
=0A
******************************************
=0A
Could yo= u please let me know the way to disassemble the binary file without any hea= der.The way in which you decoded the boot record.
=0A
 
=0AAlso= one more thing to let you know is that,
=0A
 
=0A
with the gr= ub-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 0x= 7be - 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 an= d just the boot record is sufficient
=0A
 
=0A
Viswesh
=0A<= DIV style=3D"FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif">&n= bsp;

=0A=0A=0A=0A
Unli= mited freedom, unlimited storage. Get it now --0-946609160-1220940042=:18774--