whocares02

Allow Lowercase on Multiboot-DVD

65 posts in this topic

Hi there,

just try to use grub4dos and mkisofs to make my nlite-compiled XP-CD multiboot-ready. Problem: The Grub4Dos of the boot-record is looking for /menu.lst (written in lowercase!) but all files on the DVD appear in uppercase. Maybe this is because of some ISO9660-standard. Anybody knows what do I have to change to allow lowercase-filenames? Right now, the DVD is ISO9660+Joliet3. I'm sure grub4dos and/or mkisofs need some specific dvd-format at early state of boot-process. Propably grub4dos' search for menu.lst is hardcoded in the boot-record and not editable.

0

Share this post


Link to post
Share on other sites

So far, you've been helped with other subjects requiring more information, so...

What version of Grub4DOS and how did you set up the DVD? "It doesn't work because" is not enough.

Please give a link to what you used as far as software and the "how-to" you used to better assist.

Edited by submix8c
0

Share this post


Link to post
Share on other sites

@whocares02

To allow lowercase use option mkisofs -relaxed-filenames
-iso-level 4 uncludes -relaxed-filenames http://www.msfn.org/board/topic/171350-textsetup-wont-accept-nlite-dvd/page-2#entry1072315

Be aware: some bootloader expect uppercase at ISO9660: setupldr.bin and bootmgr.

Uppercase textmode boot files at hard disk first.

Or use a ISO9660 MENU.LST and RockRidge menu.lst.

You may edit the embedded menu.lst too.

Use a current grub4dos:

grub4dos-0.4.5c-2014-01-17.7z http://code.google.com/p/grub4dos-chenall/downloads/list

Uppercase requirements may have been changes, don't remember details anymore.

0

Share this post


Link to post
Share on other sites

Wow, thank you. That was QUICK!

I'll try the relaxed-option for mkisofs first.

As to my attempt (@submix8c): The Iso was created with newest nlite and the builtin mkisofs (as described in my other threat). Afterwards I used newest mkisofs to create a grub boot-iso. I opened that new iso with ultraiso, extracted the boot-record and replaced the one in my selfmade nlite-iso with grub's boot-iso's record (also using ultraiso). Unfortunately I don't know my grub4dos-version.

grub4dos --version

doesn't seem to work. The newest entry in the changelog file is dated: 2009-06-20(r68). According to this tutorial, I tried both methods to create a grub-iso to copy the boot-record from. For my last attempt I used:

mkisofs -R -b grldr -no-emul-boot -boot-load-seg 0x1000 -o grub-iso_v2.iso iso_root

to build that iso.

0

Share this post


Link to post
Share on other sites

Well, if you take some time actually READing the provided info, you will see how you fell in the usual misunderstanding:

http://reboot.pro/topic/9696-oscdimg-and-grub4dos/?p=84356

This:

mkisofs -R -b grldr -no-emul-boot -boot-load-seg 0x1000 -o grub-iso_v2.iso iso_root

is a commonly used/referenced set of command line switches to make a grub4dos/grldr booting .iso, but it won't in any way work for a PE or Windows XP install, and not necessarily it is a good "source" to extract and copy the boot files on another .iso (made with a completely different set of command parameters).

As it was already suggested to you, you should NEVER edit .iso's, but rather create them in one single pass.

Again, this does not mean that it won't work, only that you are looking for troubles as it is probable that it won't work.

This is particularly true when using grldr as "boot sector" (or isolinux for that matters) as they are bigger than 4*512 bytes sectors=1*2048 bytes sector (the size of a common no-emulation CD/DVD bootsector), compare with this :

http://reboot.pro/topic/12406-editing-iso-files/

and please review the specific information provided about "-boot-load-seg 0x1000" vs. "-boot-load-size 4"

Get a decently recent version of grub4dos, like the one cdob suggested you, the version you have is seemingly "the changelog file is dated: 2009-06-20(r68)" an ancient, preliminary (and rejnown to be buggy) 0.4.4 version (the only 0.4.4 version that you could use is the one dated 16/10/2009), see:

http://reboot.pro/topic/14-grub4dos/

but nowadays you should use ONLY:

the latest version cdob suggested: http://code.google.com/p/grub4dos-chenall/downloads/detail?name=grub4dos-0.4.5c-2014-01-17.7z&can=2&q=

OR

the latest "featured" version: http://code.google.com/p/grub4dos-chenall/downloads/detail?name=grub4dos-0.4.5c-2013-03-03.7z&can=2&q=

Which brings you back to the given links.

jaclaz

0

Share this post


Link to post
Share on other sites

Thank you! One of the links you provided points to a grub from 2014!!! How did you find that?! For years I'm already looking for a newer version! I'm sorry my chinese is not good enough - I can't read the website's homepage. What is the difference between the two versions? I just downloaded the newer one.

Regarding to your critics about editing existing isos: There just seems to be no other way. Mkisofs always outputs an iso-file - not a boot-record-file (which was .bin, .bif, .ima or something similar) to be used with imgburn, nero or something alike. It's pretty obvious that a bootable iso without content needs further editing.

Also, I can't influence nlite's behavior compiling it's iso. The only options are: switching the engine (from standard to mkisofs) and pointing to a boot-record-file (to override the standard-option). That's it. I also tried feeding nlite with the extracted grub-boot-record (extracted with Ultraiso of course). Problem is the same: Forced uppercase for all files.

I guess you want me to compile the iso myself without nlite - just with pointing mkisofs to a folder now. That's a good idea. Thank you very much. I will soon begin to study all the links you posted for me.

0

Share this post


Link to post
Share on other sites

The very latest bugfix version of grub4dos 0.4.6a undertstands Joliet3/4 - try the experimental version at the end of the issue list here.

No doubt it will be rolled out into a proper release soon.

P.S. To find the site at any time just Google 'chenall grub4dos'.

Edited by steve6375
0

Share this post


Link to post
Share on other sites

Well, reboot.pro (was bootland) has been the UNofficial grub4dos support site since what? 2006 ;), and it is mostly written in English.

You still seem to me like missing a vital :yes: piece of info.

A CD is a .iso and a .iso is a CD.

As well,

a DVD is a .iso and a .iso is a DVD.

A .iso is a byte-by-byte/sector-by-sector image of a CD or DVD, you just "copy" (in jargon "burn") it as-is to the CD or DVD media.

You want normally to make a .iso (with mkisofs or oscdimg, or other tool) and then burn the .iso image, that's the whole point.

On the other thread:

http://www.msfn.org/board/topic/171350-textsetup-wont-accept-nlite-dvd/

you failed to follow the link, given here:

http://www.msfn.org/board/topic/171350-textsetup-wont-accept-nlite-dvd/?p=1072211

to this thread on 911CD:

http://www.911cd.net/forums//index.php?showtopic=24562

where (specifically here: http://www.911cd.net/forums//index.php?s=&showtopic=24562&view=findpost&p=169834 ) it is explained what to do, i.e. burning the .iso image with IMGBURN following this:

http://forum.imgburn.com/index.php?showtopic=61

guide.

I know that sometimes my suggestions/links lead to other places where other links are given where other links are given, etc..... :blushing: but this way, if one has the patience to follow through them, gets more info.

Of course there are n tools capable of burning a .iso image, the important thing is to understand the concept above (a CD is a .iso and a .iso is a CD), and IMGBURN has proved over the years to be very reliable (besides being freeware and fairly small).

And of course every one has his/her own ways, Steve6375, as an example, lives in the future and suggests always latest, experimental versions ;), whilst I - living in the past :w00t: - tend to always suggest known, tested, reliable versions :whistle:.

jaclaz

0

Share this post


Link to post
Share on other sites

On the other thread:

http://www.msfn.org/...cept-nlite-dvd/

you failed to follow the link, given here:

http://www.msfn.org/...-dvd/?p=1072211

to this thread on 911CD:

http://www.911cd.net...showtopic=24562

where (specifically here: http://www.911cd.net...ndpost&p=169834 ) it is explained what to do, i.e. burning the .iso image with IMGBURN following this:

http://forum.imgburn...hp?showtopic=61

guide.

Jaclaz, I red these pages and followed the imgburn-tutorial! I wrote it in my other threat! How about you try some reading as well? Imgburn needs a boot-file for Boot-CD-creation, like any other burning or iso-software does. And like all other iso/burning-programs out there imgburn also supports reading of boot-records from CD. However there is no CD to read a grub-boot-record from! When you want a grub-boot-record you have to extract it from a selfmade iso-image, created with mkisofs and grub, described here.

I will read all the new links and post my results as soon as I have time for it. See you soon.

Edited by whocares02
0

Share this post


Link to post
Share on other sites

Imgburn needs a boot-file for Boot-CD-creation, like any other burning or iso-software does.

The suggestion was to create a ISO image first, not to edit it and burn it with ImgBurn,

And like all other iso/burning-programs out there imgburn also supports reading of boot-records from CD.

The boot record may be grldr, actually first four virtual sectors prefered.

However there is no CD to read a grub-boot-record from! When you want a grub-boot-record you have to extract it from a selfmade iso-image, created with mkisofs and grub, described here.

Read again: -b grldr reference the grub-boot-record: grldr itself is the boot record.
0

Share this post


Link to post
Share on other sites

I tried allowing the RockRidge extension as mentioned in a link in a threat which was one of your links.

.\mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -R -volid "XP-SP2-DE_Silent" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-seg 0x1000 -allow-multidot -hide grldr -hide boot.catalog -o .\XP-SP2-Bugfix4.iso n-Lite-Temp

I used the latest mkisofs, newest grub2014 and the newest bugfixed grubldr, linked here as well. Output is:

      2 [main] mkisofs 4012 F:\mkisofs.exe: *** fatal error - add_item ("Ò¢£?","/", ...) failed, errno 22Stack trace:Frame     Function  Args002289C8  610274AB  (002289C8, 00000000, 00000000, 00000000)00228CB8  610274AB  (61177840, 00008000, 00000000, 61178977)00229CE8  61004ADB  (611B05C4, 0022BD0C, 00000016, 0003000A)0022CD18  6107D93A  (60FC000C, 612007F0, 0022CD98, 61071220)60FC0000  610BDE7D  (00000000, 00000000, 00000000, 00000000)End of stack trace

So I went back to my old threat and copied the line for creating an iso with mkisofs. I changed it to my needs. The iso shall become just a Joliet4-Image to support upper- and lowercase (as cbod already stated, his link is pointing to the line I used). So NO RockRidge this time:

mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -volid "XP-SP2-DE_Silent" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-seg 0x1000 -hide boot.catalog -hide bootsect.bin -allow-multidot -o n:\XP-SP2-Bugfix4.iso n-Lite-Temp

Output:

      2 [main] mkisofs 1304 F:\mkisofs.exe: *** fatal error - add_item ("Ò¢£?","/", ...) failed, errno 22Stack trace:Frame     Function  Args002289C8  610274AB  (002289C8, 00000000, 00000000, 00000000)00228CB8  610274AB  (61177840, 00008000, 00000000, 61178977)00229CE8  61004ADB  (611B05C4, 0022BD0C, 00000016, 0003000A)0022CD18  6107D93A  (60FC000C, 612007F0, 0022CD98, 61071220)60FC0000  610BDE7D  (00000000, 00000000, 00000000, 00000000)End of stack trace

@Cdob:

The suggestion was to create a ISO image first, not to edit it and burn it with ImgBurn,

No, the suggestion was burning an Iso with imgburn and setting up filesystem and boot-option manually.

Edit:

Strange thing: When running mkisofs running from C:\grub4dos, it is not crashing but complaining:

C:\grub4dos>mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -R -volid "XP-SP2-DE_Silent" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-seg0x1000 -hide boot.catalog -hide bootsect.bin -allow-multidot -o n:\XP-SP2-Bugfix4.iso nLiteTMPWarning: Creating ISO-9660:1999 (version 2) filesystem.Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.Setting input-charset to 'UTF-8' from locale.3.00 (i686-pc-cygwin)cygwin warning:  MS-DOS style path detected: n:\XP-SP2-Bugfix4.iso  Preferred POSIX equivalent is: /cygdrive/n/XP-SP2-Bugfix4.iso  CYGWIN environment variable option "nodosfilewarning" turns off this warning.  Consult the user's guide for more details about POSIX paths:    http://cygwin.com/cygwin-ug-net/using.html#using-pathnamesWriting:   Initial Padblock                        Start Block 0Done with: Initial Padblock                        Block(s)    16Writing:   Primary Volume Descriptor               Start Block 16Done with: Primary Volume Descriptor               Block(s)    1Writing:   Eltorito Volume Descriptor              Start Block 17mkisofs: Uh oh, I cant find the boot image 'grldr' inside the target tree.

grldr is inside the target folder! And it is lowercase. I changed it manually since nlite just made it uppercase (same thing with menu.lst)!

Edit2:

OK, got it. It seems mkisofs is not using hardlinks. Luckily the linux-switch

-posix-L

to follow symlinks also works in windows. The full command I used is:

C:\grub4dos>.\mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -R -volid "XP-SP2-DE_Silent" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-seg 0x1000 -allow-multidot -hide grldr -hide boot.catalog -posix-L -o n:\XP-SP2-Bugfix4.2.iso F:\n-Lite-Temp

The resulting image is "exactly" below 4GB (3.3993,93 MB). Now I hope for the best and will try the new image in virtualbox. I forgot to mention that I created the image directly after nlite finished integrating everything. I didn't press the next-button (which would bring up the iso-creation-page) to stop nlite making all files in root-folder uppercase.

Edited by whocares02
0

Share this post


Link to post
Share on other sites

I used the latest mkisofs

3.00 (i686-pc-cygwin)

That's a outdated version, name used version string always. Use a current one.

It seems mkisofs is not using hardlinks.

I'm using hardlinks at mkisofs cygwin.

The resulting image is "exactly" below 4GB (3.3993,93 MB). Now I hope for the best and will try the new image in virtualbox. I forgot to mention that I created the image directly after nlite finished integrating everything. I didn't press the next-button (which would bring up the iso-creation-page) to stop nlite making all files in root-folder uppercase.

Remember setupldr.bin searches uppercase names: I386 not i386.
0

Share this post


Link to post
Share on other sites

Now I see, you were following submix8c's suggestion, which I pointed out as not being (IMHO) valid for this scope, here:

http://www.msfn.org/board/topic/171350-textsetup-wont-accept-nlite-dvd/?p=1072315

as said everyone has his own ways :), still, the simpler approach is to create a .iso and then burn the image EXACTLY along the IMGBURN tutorial I also linked to.

I also gave you a link to this thread:

which talks about recent (and suggested) mkisofs.exe versions. (just for the record, I personally use always the Mingw versions)

There should be no need whatsoever for symlinks or hardlinks in any Windows XP install CD/DVD :unsure:

Did nlite create them? :w00t: (or did you add them, and if yes, why?)

The almost 4 Gb seem to me like a very, very large (and possibly complex) build, just in case I will re-point you to my suggestion:

http://www.msfn.org/board/topic/171350-textsetup-wont-accept-nlite-dvd/page-2#entry1072315

of trying first with a smaller, simpler one.

jaclaz

0

Share this post


Link to post
Share on other sites

grub4dos-0.4.5c-2014-01-17.7z

Uppercase requirements may have been changes, don't remember details anymore.

Yes, requirements are changed: grldr finds a ISO9660 filename /MENU.LST and /menu.lst.

A uppercase or a lowercase file is found.

@whocares02

Step back one step. Rephrase the question.

You like to create a Multiboot-DVD.

So far I understand grub4dos as bootloader and adding Windows XP.

Which multi boot parts do you like to include too?

There is no general filesystem/filecase advise for a Multiboot-DVD.

E.g. a WinPE1 uses different filenames as a XP installation CD.

There are different solutions based on different included parts.

Clarify your needs.

0

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.