All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viswesh S <viswesh_vichu@yahoo.com>
To: grub-devel@gnu.org
Subject: Windows,grub and grub2
Date: Fri, 29 Aug 2008 13:29:38 -0700 (PDT)	[thread overview]
Message-ID: <577426.34688.qm@web31601.mail.mud.yahoo.com> (raw)

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

Hi,

I am back with my Windows boot up question using grub and grub2.Sorry for making the question a bit long.

Some experiments and results which I did.

Scenario: One hard disk,different partitions.

Case 1: 

Partition 1 -> Windows Server 2003
Partition 2 -> Swap
Partition 3 -> Linux

Boot loader : Grub2.

Windows boots up successfully from grub2 using chainloading (hd0,1) +1

Case 2:

Installed server 2008 in the free space in between Server 2003 and swap.

Partition 1 : Windows server 2003
Partition 2: Windows server 2008
Partition 3 :Swap
Partition 4:Linux

Grub2 doesnt boot up windows with the command chainloader (hd0,1) +1, with error 

A disk read error occurred 
Ctrl+Alt +del to restart.

But Grub legacy boots up with no issues , with the same command, prefixed with rootnoverify hd0

Case 3:

Partition 1 :Boot
Partition 2:Windows
Partition 3: Linux

Same behaviour : Grub2 doesnt boot Windows with chainloader command (hd0,2) +1

Same error as before.

Not surprisingly grub boots with the same command.

I had a look at the boot sector code of Windows, which gets copied, by dumping the partition using dd.

For me, it looked the same.

Also another hunch is that,as the error ( A disk read error occurred ),, happened in Windows boot sector, find the areas in boot sector code of Windows where it calls this error and goes into an infinite loop.

So in the different cases, I could see that it is something to do with the INT 13 call, with functions 41 and 42.

Can anyone let me know the differences here, with respect to grub2 and grub.

Also,on more thing is the way chainloader command is written in grub and grub2.I was finding it difficult to decode the assembly parts in both and find out the differences.

Can anyone pour some advice and directions on these.

Thanks in advance,

Viswesh


      Unlimited freedom, unlimited storage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/

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

             reply	other threads:[~2008-08-29 20:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 20:29 Viswesh S [this message]
2008-08-30  4:30 ` Windows,grub and grub2 Bean
2008-08-30  5:31   ` Bean
2008-08-30 15:03   ` Vesa Jääskeläinen
2008-08-30 15:21     ` Bean
  -- strict thread matches above, loose matches on Subject: below --
2008-09-01  9:08 Viswesh S
2008-09-01 10:16 ` Bean
2008-09-01 10:48 Viswesh S
2008-09-01 13:02 ` Bean
2008-09-01 13:37 Viswesh S
2008-09-01 13:51 ` Bean
2008-09-01 13:53 Viswesh S
2008-09-01 14:35 ` Bean
2008-09-01 15:27 Viswesh S
2008-09-01 15:35 ` Bean
2008-09-01 17:01 Viswesh S
2008-09-04 17:37 ` Bean
2008-09-09  6:00 Viswesh S
2008-09-22  3:40 ` Bean
2008-09-23  8:23 Viswesh S
2008-09-23 13:50 ` Bean
2008-09-29  5:18 Viswesh S
2008-09-29 10:50 ` Bean
2008-10-14 11:34 Viswesh S
2008-11-08 17:26 Viswesh S
2008-11-10 13:08 ` James Shewey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=577426.34688.qm@web31601.mail.mud.yahoo.com \
    --to=viswesh_vichu@yahoo.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.