From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Ki3BY-0002AC-Nl for mharc-grub-devel@gnu.org; Tue, 23 Sep 2008 04:23:52 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ki3BW-00026Y-Gc for grub-devel@gnu.org; Tue, 23 Sep 2008 04:23:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ki3BT-00021r-Uv for grub-devel@gnu.org; Tue, 23 Sep 2008 04:23:49 -0400 Received: from [199.232.76.173] (port=49462 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ki3BT-00021e-Rg for grub-devel@gnu.org; Tue, 23 Sep 2008 04:23:47 -0400 Received: from web31608.mail.mud.yahoo.com ([68.142.198.154]:48064) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Ki3BT-0006Ye-CX for grub-devel@gnu.org; Tue, 23 Sep 2008 04:23:47 -0400 Received: (qmail 75203 invoked by uid 60001); 23 Sep 2008 08:23:43 -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:Content-Transfer-Encoding:Message-ID; b=gpaervmXLBwWnVUNYV+mnu/iJhrNJ/1pMpn9U3NwEUKejMXlQmhi7/9aTrM8HSF8u24LNgrj/+Dc5LnYwyJY4Yb/BdBaLnvMxb5ckuol4YksPLMCYVZ7jw+/q7rAhppEPfj6k1ggnproIrZHHKJ+2OI5XDPG5qYq//Xxlna7pnQ=; X-YMail-OSG: PAus9ewVM1nmn98M7Vky1eWQafzSGVCgSfyAI9SCaKZ17tBm8p9t_OEmB4yLOmAWK2r_CcIhWMIg3ZwgUGfz.ga4xNACET0EHdTy.BenTgj.N.iXJdD7OsRsKyD1UnMCCSupEEV89jflQYpl8nB0cWYuyNygEj2JK7AIwXt7iDsWo1PfMw-- Received: from [202.62.94.130] by web31608.mail.mud.yahoo.com via HTTP; Tue, 23 Sep 2008 01:23:43 PDT X-Mailer: YahooMailRC/1096.28 YahooMailWebService/0.7.218.2 Date: Tue, 23 Sep 2008 01:23:43 -0700 (PDT) From: Viswesh S To: The development of GRUB 2 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <669465.74261.qm@web31608.mail.mud.yahoo.com> X-detected-operating-system: 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, 23 Sep 2008 08:23:50 -0000 =0A=0A=0A=0A----- Original Message ----=0A> From: Bean =0A> To: The development of GRUB 2 =0A> Sent: Monday, = 22 September, 2008 9:10:26 AM=0A> Subject: Re: Windows,grub and grub2=0A> = =0A> On Tue, Sep 9, 2008 at 2:00 PM, Viswesh S wrote:=0A> > Below is the du= mp of screen output while chainloading the ntfsnew file.=0A> > ************= ***************************=0A> > DI=3DCFF0 SI=3D07EE BP=3D1FF0 SP=3D1FE8 B= X=3D0000 DX=3D0000 CX=3D0000 AX=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 E= S=3D0000 FG=3D0007 IP=3D0082=0A> > ****************************************= **=0A> > Could you please let me know the way to disassemble the binary fil= e without=0A> > any header.The way in which you decoded the boot record.=0A= > >=0A> > Also one more thing to let you know is that,=0A> >=0A> > with the= grub-1.96 ( without the chainloader patch of disk->dev->read() ) ,=0A> > w= ith windows2003 in partition 1 and linux in partition 3, when we chainload,= =0A> > if we look at the partition table passed to another bootloader ie lo= cation=0A> > 0x7be - we can see that it is junk, but the surprising point i= s that, in=0A> > this case as I have mentioned in my first mail, windows bo= ots up from=0A> > grub2.So it is that the partition table is not required f= or the chainloader=0A> > thing and just the boot record is sufficient=0A> = =0A> Hi,=0A> =0A> Oh, sorry for another long delay. I disassemble the file = with ida,=0A> which is an amazing tool. I don't know if there is open sourc= e=0A> alternative, please let me know if you find one.=0A> =0A> The output = from ida is in masm format, I modify it a bit so that it=0A> can be compile= d using nasm. Please note that nasm doesn't generate the=0A> same binary fi= le as original one, but you can get an idea what it=0A> does.=0A> =0A> From= the output, the program fails at the second int 13 call, int=0A> 13/ah =3D= 48h. Although I notice that DL=3D0, which is not supposed to=0A> happen. P= erhaps you can add a grub_printf in grub_chainloader_boot to=0A> show the v= alue of boot drive:=0A> =0A> static grub_err_t=0A> grub_chainloader_boot (v= oid)=0A> {=0A> =A0 grub_printf ("boot_drive=3D%d\n", boot_drive);=0A> =A0 g= rub_chainloader_real_boot (boot_drive, boot_part_addr);=0A> =0A> =A0 /* Nev= er reach here.=A0 */=0A> =A0 return GRUB_ERR_NONE;=0A> }=0A> =0A> -- =0A> B= ean=0A> =0A> =0A=0AHi,=0A=0AThe value of boot drive is 0x80.=0A=0AThis was = the same value in disk->drive also.=0A=0AViswesh=0A=0A=0A Be the first= one to try the new Messenger 9 Beta! Go to http://in.messenger.yahoo.com/w= in/