中国DOS联盟

I repeatedly experimented. Using the find command always prompts that the file is not found and cannot locate the file, while without using find, setting the root to the default or adding something like (hd0,0) as the root can instead read the file.

For example:
I created a file, my.txt, on the USB flash drive.
title Micro Windows XPE (by LaoMaotao)
find --set-root /my.txt
chainloader /ldrxpe
It shows that the my.txt file is not found and cannot boot.
While the following:
title Micro Windows XPE (by LaoMaotao)
chainloader /ldrxpe
or
title Micro Windows XPE (by LaoMaotao)
chainloader (fd0)/ldrxpe
can both boot.

If this is the case, is it better to use the default root? Because it seems that it can automatically locate. While using find always fails to find, and specifying fd0 limits that the USB flash drive cannot be of HDD type.

Please confirm whether the flag file (my.txt) exists

How can the file I created myself not exist? And I've done similar experiments more than once. Because almost every time I see others using find, I always feel不服 (unconvinced), so I tried again, and after repeating this many times, I've never successfully used the find command. According to the writing, there must be no problem. The file was also created in the root directory as required, and there's no reason for it. So I'm confused.

Yes, I think there is also a problem with the use, but I still don't know where the problem is. Please give me some advice.

-_-!!.
It is estimated that it was made with UltraISO and then the box for default support of lowercase letters in properties was not checked, and then......

Originally posted by yjd at 2009-3-14 15:27:
-_-!!.
It is estimated that it is made with ultraiso and the default support for lowercase letters in the properties is not checked and then......

No, I'm not making an ISO. Mine is a USB drive boot

Sweat, still...

The LZ should report the version of GRUB4DOS? How did you boot? What operations did you do? Anyway, the more detailed the better.
It's best to attach screenshots,
And then execute some other commands to see if this file exists. For example, ls /my.txt

These are the basic skills to solve the problem. If you don't do this, wanting to solve the problem, others can only guess the specific reason. The chance of guessing correctly is not big. It's a waste of others' time,

So for a problem like yours, generally not many people will pay attention, you can see it yourself.
From the posting time 3.12, to the previous reply 3.18, there is no solution yet, which has already shown the problem.

Take a look at other people's posts, which provide sufficient information. Under normal circumstances, it can be solved within a day.

Originally posted by chenall at 2009-4-1 13:17:
Sweat, still here...

The owner should report the version of GRUB4DOS? How did you start it? What operations did you do? Anyway, the more detailed the better.
It is best to match with screenshots,
And then perform some other commands to see this...

Yes, it has been unable to solve the problem. It is estimated that others have not encountered such a problem, so.......

First, let's talk about how to make the boot. Originally, Flashboot was used to make DOS boot to enter GRUB, now grubinst is used to make the boot, and then bootlace was also tried with DD to make MBR.
It should have nothing to do with the version. The versions I tried are all like this. The computer starts in USBZIP method. The USB is formatted as ZIP. Under the grub4dos command line, ls can display files and all files, but the find command only lists all hard disk partitions, but there is no USB device. This may be the reason why FIND cannot be used. I tested the CD (ISO) and floppy disk (IMG) in the virtual machine. FIND and LS are displayed normally, but the real machine find only has the hard disk, and the USB flash drive does not come out. Does FIND not support USBZIP?
I think it is very difficult for me to be very detailed, because it is a real machine use, and there is no way to take screenshots from the virtual machine (the virtual machine can find FD0).

In fact, find is only used in specific situations. For example, when you don't know which partition your file is on, you need to use it.

If your boot menu and your file are on the same disk, you don't need the find command at all. Using it will反而 get unexpected results. For example, if you boot from a CD and use find, if the file happens to be on the hard disk, then the file on the hard disk will be used, and the file on the CD will be useless.

Just use the relative path directly.

So, don't use this command casually without understanding. Also, don't follow the crowd. Others may have their own purposes for using find.

I try to use one less command if possible. As long as the boot is normal, that's fine.

Yes.
I also discovered such a problem, so I have started using relative paths. However, in some cases, it is still necessary to describe the device. For example, when DOS starts to execute grub.exe, if the device is not specified, it will preferentially read the files on the hard disk, so only fd0 can be specified. Of course, this is an experimental test, because according to the test, I can avoid the method of starting with DOS, thus avoiding the use of absolute paths, and making the file search order meet the expectations.