China DOS Union

Ask: Regarding the problem of using syslinux to boot grub4dos.

It is said that for USB drive booting, using syslinux has good compatibility. Therefore, I considered using syslinux to load gghost.img.
I tried it and found that loading non-standard images is extremely slow. Moreover, it is quite strict about the img. My gghost.img prompts that it cannot boot after being loaded.

So I thought of using syslinux to boot grub and then start the img.

I tried it. Using
label 1
KERNEL grub.exe

can boot grub, but it cannot find the menu.lst placed in the root directory of the USB drive, thus directly entering the command line. [The problem of not finding the menu was solved through menu internalization. May I ask, if not internalized, how to set it to find the menu file?]

If syslinux can directly boot grldr, it can solve the problem of not finding the root directory menu. So I flipped through the posts and saw that there is a post by bean "Booting grub4dos and ntldr in grub2-syslinux" which introduced syslinux to boot grub4dos. So I downloaded the file loadbin.bin, and according to the instructions inside, I wrote syslinux.cfg,
kernel loadbin.bin
append initrd=grldr

But after running, it prompts that linux is not found. I don't know why? I also don't know where I made a mistake.

Please let those who know give guidance.

There are many ways to boot from a USB drive, and I don't know which one has the best compatibility.

label 1
KERNEL grub.exe

Is menu.lst placed in the same directory as grub.exe?




The second method prompts that linux is not found. What version of syslinux are you using? Try to see what prompts the debug version will have, and also what the syslinux.cfg configuration is like

When booted via grub.exe, there seems to be no default "current device", so the menu.lst cannot be found. However, you can use

label 1
KERNEL grub.exe --config-file=(fd0)/menu.lst

or similar parameters to specify the menu file.

Originally posted by barton at 2008-1-3 15:51:
label 1
KERNEL grub.exe

Is the menu.lst in the same directory as grub.exe?




The second method prompts that linux is not found. What version of syslinux are you using? Try to see what prompts the debug version will have, and what the syslinux.cfg configuration is like

In the same directory, I have tried what is mentioned in the readme, but it doesn't work. It seems that it is indeed not pointing to the current device.

I considered specifying fd0, but will it become hd0? If not, it's okay. If it might become (hd0,0), how to solve it more universally?

The version of syslinux is 3.51. I downloaded it before and used it once, but it was too slow to load the img, so I didn't use it. Today someone wanted to boot gghost from a USB drive, and the DOS boot didn't work, so I thought of the more compatible sysliinux.

(DOS file) .\menu.lst, the MENU.LST in the current dir.

(DOS file) \menu.lst, the MENU.LST in the root dir of
the current drive.
(GRUB file) /menu.lst, the MENU.LST in the root dir of
the boot device.

Originally posted by barton at 2008-1-3 15:51:
Try to see what prompts the debug version will have, and what the syslinux.cfg configuration is like

The usage is written in bean's post.

kernel loadbin.bin
append initrd=grldr

The files were not found, and it doesn't help to change to the debug version of grldr.
Personally, I understand that this is because syslinux failed to boot grldr.
It should be that kernel loadbin.bin was not executed successfully.

Originally posted by Budian at 2008-1-3 16:06:
It's booted through grub.exe, and it seems there is no default "current device", so the menu.lst cannot be found. However, you can use

label 1
KERNEL grub.exe --config-file="(fd0)/menu.lst"

or similar parameters to specify the menu file.

See if what Budian said or the following one finds the menu

label 1
KERNEL grub.exe
APPEND --config-file="(fd0)/menu.lst"




The debug version I mentioned is for syslinux. O(∩_∩)o... It seems only isolinux has a debug version

[ Last edited by barton on 2008-1-4 at 03:00 PM ]

Originally posted by barton at 2008-1-3 20:51:
Check if the following is found in the menu
label 1
KERNEL grub.exe
APPEND --config-file=(fd0)/menu.lst
The debug version I mentioned is for syslinux, o(∩_∩)o... It seems only isolinux has a debug version

I'm sorry, I know very little about syslinux, just using it as a ready-made solution. Hehe.
Other than imitating, I can't do anything else.

If it starts as HD0, how to handle it properly?

I only use isolinux and pxelinux in syslinux, which is very similar to the usage of grub4dos.

But for the problem that the USB flash drive is recognized as fd or hd, you can use grub's find to locate and see if it works. Syslinux seems to have no way to solve this problem.

In syslinux, it is to determine whether it is the root directory of the current device according to whether there is a "/" symbol. No symbol means it is in the isolinux/pxelinux folder - relative path. I haven't used syslinux.exe-syslinux.com, so I don't know.

See if the following usage can work.

label 1

  KERNEL grub.exe 

  APPEND --config-file="find --set-root /gghost.txt;configfile /menu.lst;boot"

If it doesn't work, consider using the built-in menu.

:-)

[ Last edited by barton on 2008-1-4 at 03:21 PM ]