That's all done for mkisofs...
I won't be using mkisofs
to build my project. I tested the recommended mkisofs
commands from the various Grub4Dos guides to ensure that Grub4Dos was working. All went fine in terms of simply booting WinPE 2.1. The only point of note was that "chainloader /bootmgr" required the lowercase.
However, it seems that the use of mkisofs
requires further investigation.
Points I have noted using the recommended commands from the guide.
1. When mkisofs is executed in XP SP3 x86, the first line to appear in the cmd window is:
mkisofs: Warning: -rock has same effect as -rational-rock on this platform.
That is, -R equals -r "on my platform".
2. From the grub cmd-line, when using "chainloader /" [TAB], I noticed my custom "Program Files" folder in the root was displayed as "Program\ Files", which lead to the next point.
3. I was building a very basic PE - no shell, programs or extras. With a first attempt at Grub4Dos and the recommended mkisofs
commands, I was simply interested to see if it booted, and hadn't actually looked inside the PE. However, the strange "Program\ Files" entry in grub cmd-line's [TAB] looked like it neeeded further investigation.
From the booted PE, a quick "dir" of the Virtual CD Drive's root showed "PROGRAM_" where "Program Files" or "PROGRAM FILES" should have been. OK - there is probably a basic mkisofs
switch to correct that. The point is that, from the booted PE, everything in the CD is uppercase.
This is in contrast to IsoBuster on the Host HDD looking at the .iso. The right hand pane shows all files and folders in the original form - lowercase and mixed case - and the correct display of "Program Files" folder. However, in the left-hand pane, things are different - all uppercase, and "PROGRAM_"
The display from "dir" in the booted PE is also in contrast to the bootloader grub cmd-line [TAB] which reveals everything in its original form. That is, "grldr", "menu.lst", "bootmgr", "boot\" folder and contents, etc - all in lower case. And the custom folders in mixed case, but strange "Program\ Files".
This is significant for the Grub4Dos Menu entries because grub will only execute these file in the form shown by the grub cmd-line. "bootmgr" must be in lower case. The bit that had me confused was that it will still boot, even with all the boot files in lowercase. With oscdimg
's -d switch, everything is kept in its original case, but with all the boot files in lower case, it causes a "Windows failed to start ... [BCD error]. The reason must be the RockRidge extensions implemented by mkisofs
' -R or -r switch.
The misunderstanding with cdob
is that we were looking at different faces of the same thing.
for the well-proven (no doubt) mkisofs command. I'll try it out as soon as I can get winbuilder to create a suitable directory structure for testing. (I hate doing things manually! ...