I recently revisited WinGRUB form other versions of GRUB for NTFS and have the following points and suggestion to make for minor improvements to make about WinGRUB which I now use exclusively instead.
[I do realise that WinGRUB is intended for experienced users but the following behaviour appear strange and would be extremely confusing for even experienced users like myself. BUT the following ISSUE is probably the major reason for people NOT USING WINGRUB or trying it out and then moving on to another tool…]
ISSUE 1:
The use of C:\GRUB after having already installed Linux typically results in the NTFS GRLDR loader finding and using the Linux “menu.lst” from “/boot/grub” the first found Linux Root File System rather than the “C:\GRUB\MENU.LST” intended.
POSSIBLE RESOLUTIONS:
(A) Have WinGRUB install instead to “%SystemDrive%\BOOT\GRUB” or better yet (since this will work _ONLY_ if Windows _IS_ the first partition found):
(B) _ALTER_INSTEAD_ the default GRUB Preset Menu so that the default “/grub/menu.lst” is FIRST rather than last in the search list:
default 0
timeout 0
fallback 1
title load /menu.lst
find --set-root /menu.lst
configfile /menu.lst
title load /boot/grub/menu.lst
find --set-root /boot/grub/menu.lst
configfile /boot/grub/menu.lst
title load /grub/menu.lst
fallback 2
find --set-root /grub/menu.lst
configfile /grub/menu.lst
SUGGESTION 2:
Rather than the following “default.lst”:
timeout 10
title Windows at (hd0,0)
root (hd0,0)
chainloader +1
Change the default to the following or add a “windows+linux.lst” as follows as this is much more useful and near universal Windows+Linux dual-boot menu:
timeout 10
title Linux at (hd0,1)
root (hd0,1)
kernel /vmlinuz root=/dev/hda2 ro # quiet splash
initrd /initrd.img
title [GRUB at (hd0,1)]
rootnoverify (hd0,1)
chainloader +1
title [Windows at (hd0,0)]
root (hd0,0)
chainloader +1
The file as whole will suit 90% of Windows + Linux installs.
The first menu item will boot 90% of Linux’s (can probably drop the “quiet” and “splash” – this comes form Ubuntu but the rest is almost stock standard).
The second menu item permits chain loading another linux menu installed at (hd0.1) {i.e. the one that shouldn’t be loaded by default in ISSUE 1 unless you intend to do so by simply deleting C:\BOOT\GRUB or C:\BOOT\GRUB\MENU.LST.
And the bracket indicate that a menu follows: either GRUB or Windows…
I am happy to make these changes myself if you add me to your project as a developer.
Regards and thankyou for your great tool,
Matthew Sheeran
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I recently revisited WinGRUB form other versions of GRUB for NTFS and have the following points and suggestion to make for minor improvements to make about WinGRUB which I now use exclusively instead.
[I do realise that WinGRUB is intended for experienced users but the following behaviour appear strange and would be extremely confusing for even experienced users like myself. BUT the following ISSUE is probably the major reason for people NOT USING WINGRUB or trying it out and then moving on to another tool…]
ISSUE 1:
The use of C:\GRUB after having already installed Linux typically results in the NTFS GRLDR loader finding and using the Linux “menu.lst” from “/boot/grub” the first found Linux Root File System rather than the “C:\GRUB\MENU.LST” intended.
POSSIBLE RESOLUTIONS:
(A) Have WinGRUB install instead to “%SystemDrive%\BOOT\GRUB” or better yet (since this will work _ONLY_ if Windows _IS_ the first partition found):
(B) _ALTER_INSTEAD_ the default GRUB Preset Menu so that the default “/grub/menu.lst” is FIRST rather than last in the search list:
default 0
timeout 0
fallback 1
title load /menu.lst
find --set-root /menu.lst
configfile /menu.lst
title load /boot/grub/menu.lst
find --set-root /boot/grub/menu.lst
configfile /boot/grub/menu.lst
title load /grub/menu.lst
fallback 2
find --set-root /grub/menu.lst
configfile /grub/menu.lst
SUGGESTION 2:
Rather than the following “default.lst”:
timeout 10
title Windows at (hd0,0)
root (hd0,0)
chainloader +1
Change the default to the following or add a “windows+linux.lst” as follows as this is much more useful and near universal Windows+Linux dual-boot menu:
timeout 10
title Linux at (hd0,1)
root (hd0,1)
kernel /vmlinuz root=/dev/hda2 ro # quiet splash
initrd /initrd.img
title [GRUB at (hd0,1)]
rootnoverify (hd0,1)
chainloader +1
title [Windows at (hd0,0)]
root (hd0,0)
chainloader +1
The file as whole will suit 90% of Windows + Linux installs.
The first menu item will boot 90% of Linux’s (can probably drop the “quiet” and “splash” – this comes form Ubuntu but the rest is almost stock standard).
The second menu item permits chain loading another linux menu installed at (hd0.1) {i.e. the one that shouldn’t be loaded by default in ISSUE 1 unless you intend to do so by simply deleting C:\BOOT\GRUB or C:\BOOT\GRUB\MENU.LST.
And the bracket indicate that a menu follows: either GRUB or Windows…
I am happy to make these changes myself if you add me to your project as a developer.
Regards and thankyou for your great tool,
Matthew Sheeran
oops i got the wrong section in the default grub menu search list but you know what i mean (swap first and third searches say...
regards,
Matthew