From: Viswesh S <viswesh_vichu@yahoo.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Windows,grub and grub2
Date: Mon, 1 Sep 2008 02:08:25 -0700 (PDT) [thread overview]
Message-ID: <599868.39737.qm@web31606.mail.mud.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
----- Original Message ----
From: Bean <bean123ch@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Sent: Saturday, 30 August, 2008 11:01:18 AM
Subject: Re: Windows,grub and grub2
> Hi,
>
> I thinks it's caused by partition entry pointer %esi which isn't
> correct in grub2, please see if this patch fixes the problem.
>
> --
> Bean
>
Hi,
BTW, you should use the following command:
set root=(hd0,1)
chainloader +1
It's not the same as chainloader (hd0,1)+1, as chainloader command
would use the value of root to decide the boot partition index.
--
Bean
Hi,
There was no need for the initial partition to me made active, as it was already active.So trying that didnt help out anyway.
Initially I was not calling set root=(hd0,1).
But even after I use it, the results were the same.
The location 7c00 was good, so the boot record is getting copied correctly.
I am repeating my earlier doubt, are we sure that,the assembly part of both grub-legacy and grub2 doesnt have any changes with respect to grub2, especially in th
I still feel, there might be a problem with that, as I feel we are jumping into boot record of windows and then going to an infinite after dumping the error :A disk read error occurred'
Viswesh
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
Download prohibited? No problem. CHAT from any browser, without download. Go to http://in.webmessenger.yahoo.com/
[-- Attachment #2: Type: text/html, Size: 3532 bytes --]
next reply other threads:[~2008-09-01 9:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 9:08 Viswesh S [this message]
2008-09-01 10:16 ` Windows,grub and grub2 Bean
-- strict thread matches above, loose matches on Subject: below --
2008-11-08 17:26 Viswesh S
2008-11-10 13:08 ` James Shewey
2008-10-14 11:34 Viswesh S
2008-09-29 5:18 Viswesh S
2008-09-29 10:50 ` Bean
2008-09-23 8:23 Viswesh S
2008-09-23 13:50 ` Bean
2008-09-09 6:00 Viswesh S
2008-09-22 3:40 ` Bean
2008-09-01 17:01 Viswesh S
2008-09-04 17:37 ` Bean
2008-09-01 15:27 Viswesh S
2008-09-01 15:35 ` Bean
2008-09-01 13:53 Viswesh S
2008-09-01 14:35 ` Bean
2008-09-01 13:37 Viswesh S
2008-09-01 13:51 ` Bean
2008-09-01 10:48 Viswesh S
2008-09-01 13:02 ` Bean
2008-08-29 20:29 Viswesh S
2008-08-30 4:30 ` Bean
2008-08-30 5:31 ` Bean
2008-08-30 15:03 ` Vesa Jääskeläinen
2008-08-30 15:21 ` Bean
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=599868.39737.qm@web31606.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.