Results 11 to 14 of 14
I think your rootnoverify line should read:
Code:
rootnoverify (hd1,0)
not what you currently have:
Code:
rootnoverify (hd1)
And also you can add 'makeactive' under the chainloader line.. everyone else ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 07-04-2004 #11Linux Engineer
- Join Date
- Jul 2003
- Location
- Uppsala, Sweden
- Posts
- 1,278
I think your rootnoverify line should read:
not what you currently have:Code:rootnoverify (hd1,0)
And also you can add 'makeactive' under the chainloader line.. everyone else seems to have that when booting windows.Code:rootnoverify (hd1)
The filesystem in use by windows makes no difference whatsoever to the grub boot sequence.Proud to be a GNU/Gentoo Linux user!
- 07-04-2004 #12Linux Newbie
- Join Date
- Apr 2004
- Posts
- 173
I tried changing the 'rootnoverify' and I added the 'makeactive' command, but neither fix the error:
I was searching through the possible commands and I saw there was a 'parttype' What exactly does that do, and could it be a possible fix?Code:root (hd1,0) Filesystem type unknown, partition type 0x7
- 07-04-2004 #13Linux Guru
- Join Date
- Oct 2001
- Location
- Täby, Sweden
- Posts
- 7,578
The original rootnoverify command was obviously wrong. Anyhow, from what I know, Windows refuses to boot if it's not installed on the first hard drive. Fortunately, there's a workaround for that with GRUB. Try these commands instead:
Code:title Windows rootnoverify (hd1,0) map (hd0) (hd1) map (hd1) (hd0) chainloader +1
- 07-05-2004 #14Linux Newbie
- Join Date
- Apr 2004
- Posts
- 173
Excellent! That fixed it. I was tired of swapping jumpers on the drive to switch between OS's. Thank you, and everyone else, who helped me with this. This has got to be one of the most helpful Linux forums I've yet to find, and I'll keep coming back. Thanks again to everyone!


Reply With Quote
