search

kxylxp / grub4dos-chenall

Automatically exported from code.google.com/p/grub4dos-chenall
0 stars 0 forks source link

preset menu.lst failed #20

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. ./configure --enable-preset-menu=preset_menu.lst
2. make
3. copy the new grldr to boot disk

What is the expected output? What do you see instead?
I wish grldr could access my /grub/menu.lst automatically, but failed.

What version of the product are you using? On what operating system?
svn r149. And archlinux.

Please provide any additional information below.
I use preset_menu.lst whic.h already prepared in src directory

Original issue reported on code.google.com by dlin...@gmail.com on 28 Mar 2011 at 7:15

GoogleCodeExporter commented 8 years ago 
For newish versions, the preset menu has precedence over the on-disk menu.lst 
file. If you want the menu.lst on disk to work well, you should use a 
configfile command in your preset menu.

If you wish /grub/menu.lst automatically function well, you should add a line 
of "configfile /grub/menu.lst" to your preset menu, or let it follow an 
additional line of "find --set-root /grub/menu.lst".

Another possible reason why it failed to find /grub/menu.lst is that the 
/grub/menu.lst is on a USB storage device, and grub4dos failed to access data 
on it(because of CHS messed up by your BIOS). You may try to use "cat --hex 
(...)+1"(where "..." should be filled in for your USB drive) and see if the 
first sector of your USB drive can be accessed. If yes, you may "cat --hex 
(...)1+1", and "cat --hex (...)2+1",... ... "cat --hex (...)N+1", and find the 
maximum N.

If the device is present and some sectors can be accessed, then you should 
consider to use fbinst to build your bootable USB. Fbinst works fine with 
grub4dos, and can deal with the CHS mess-up issue.

If your are experiencing a hard drive problem, then possibility is that the 
menu.lst is physically outside the capability of your BIOS. Many BIOSes have a 
limit of 137G.

Emmm, it is also possible that you have a compiler problem. Try using the 
released build and see if the problem still there.

Original comment by tinyb...@gmail.com on 29 Mar 2011 at 1:07

GoogleCodeExporter commented 8 years ago

Original comment by chenall.cn on 27 May 2011 at 10:32