Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Allow Lowercase on Multiboot-DVD

- - - - - iso9660 joliet boot filename lowercase uppercase multiboot

  • This topic is locked This topic is locked
64 replies to this topic

#1
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 88 posts
  • OS:XP Home
  • Country: Country Flag

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.

 




How to remove advertisement from MSFN

#2
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,190 posts
  • OS:none specified
  • Country: Country Flag

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, 31 March 2014 - 07:22 AM.

Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image


#3
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

@whocares02

 

To allow lowercase use option mkisofs -relaxed-filenames
-iso-level 4 uncludes -relaxed-filenames http://www.msfn.org/...-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.c.../downloads/list

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



#4
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,029 posts
  • OS:none specified
  • Country: Country Flag

See:

http://reboot.pro/to...d-with-mkisofs/

 

AND given links.

 

Or have a look here:

http://reboot.pro/to...g-and-grub4dos/

particularly my post:

http://reboot.pro/to...ub4dos/?p=84348

 

Additionally, check the actual mkisofs in use, see:

http://reboot.pro/to...drive/?p=183011

 

jaclaz



#5
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 88 posts
  • OS:XP Home
  • Country: Country Flag

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.



#6
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,029 posts
  • OS:none specified
  • Country: Country Flag

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

http://reboot.pro/to...ub4dos/?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/to...ting-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.c...-17.7z&can=2&q=

OR

the latest "featured" version: http://code.google.c...-03.7z&can=2&q=

 

Which brings you back to the given links.

 

jaclaz

 



#7
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 88 posts
  • OS:XP Home
  • Country: Country Flag

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.



#8
steve6375

steve6375

    Junior

  • Member
  • Pip
  • 57 posts
  • OS:Windows 7 x64
  • Country: Country Flag

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, 31 March 2014 - 12:17 PM.

Visit www.rmprepusb.com for RMPrepUSB, the new Easy2Boot multiboot USB solution and 100+ tutorials on booting from USB drives.


#9
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,029 posts
  • OS:none specified
  • Country: Country Flag

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/...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.

 

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



#10
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 88 posts
  • OS:XP Home
  • Country: Country Flag

 

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, 31 March 2014 - 01:51 PM.


#11
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

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.

#12
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 88 posts
  • OS:XP Home
  • Country: Country Flag

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 22
Stack trace:
Frame     Function  Args
002289C8  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 22
Stack trace:
Frame     Function  Args
002289C8  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-D
E_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-Bugfix
4.iso nLiteTMP
Warning: 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-pathnames
Writing:   Initial Padblock                        Start Block 0
Done with: Initial Padblock                        Block(s)    16
Writing:   Primary Volume Descriptor               Start Block 16
Done with: Primary Volume Descriptor               Block(s)    1
Writing:   Eltorito Volume Descriptor              Start Block 17
mkisofs: 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-se
g 0x1000 -allow-multidot -hide grldr -hide boot.catalog -posix-L -o n:\XP-SP2-Bu
gfix4.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, 31 March 2014 - 07:39 PM.


#13
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

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.

#14
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,029 posts
  • OS:none specified
  • Country: Country Flag

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/...-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:

 

 

Additionally, check the actual mkisofs in use, see:

http://reboot.pro/to...drive/?p=183011

 

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/...-2#entry1072315

of trying first with a smaller, simpler one.

 

jaclaz

 

 



#15
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

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.

#16
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,190 posts
  • OS:none specified
  • Country: Country Flag

Hmmm...

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

And I said

IMGBURN will create a DVD Image and/or burn a Built DVD from folders.

<snip>

Get IMGBURN and look it over.

and that was my preference as opposed to MKISOFS, since it has a GUI and functions very well (IMHO) similar to NERO, which DOES have "Ignore Read Errors" under "Copy Options", which "apparently" you are MOUNTING an ISO image (we don't know that). Please note that nLite uses its OWN parameters INTERNALLY to pass to it (MKISOFS), which is a COMMAND LINE tool. This is where you are erring, among the fact that you missed the remainder of the thread CLARIFYING what would need to be done, regardless of the tool to be used.

 

Also note that "?" wherever I had used it means :unsure: (UNSURE). I do tend to do that occasionally rather than use an emoticon.

 

Randomly attempting to create a CD/DVD/ISO outside of SPECIFIC instructions by ANY member (INCLUDING corrections by other members) and expecting it to work will continue to result in failures. You are not being clear which will ALSO result in "bad advice". The USUAL method is to clearly state WHAT you want to do thusly (to borrow jaclaz' now-famous link) -

http://homepage.ntlw...ard-litany.html

Otherwise, the best that can be done is give EXAMPLES and continue going in circles.

 

Thank you, and HTH. ;)


Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image


#17
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 88 posts
  • OS:XP Home
  • Country: Country Flag

 

Yes, requirements are changed: grldr finds a ISO9660 filename /MENU.LST and /menu.lst.
A uppercase or a lowercase file is found.

 

That's a goo thing! Propably the reason my CD is booting now, finally. 
 

 

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

 

 

No, I DID CREATE THEM! Of course!  And I don't need to explain why! The fact I did creat them lets you now that there WAS need for them because I decided so. The only important information here for you is: mkisofs provides a switch to follow hardlinks in windows. Hence there is not even a problem anymore - just something to learn.

 

The almost 4GB size is the result of many applications I added to my build. They are all running fine. There is nothing complex about it.

 

My problem is now to choose a proper filesystem. Joliet4  seems to work for installation. However, after setup finishes special characters are displayed wrong on the dvd. Very annoying because of german Umlaute (Ä, Ö and Ü). I can't acces my additional folders now.

 

Mkisofs is from the official homepage. Not my fault it's not newest version. Only strange thing: It still crashes when I run it from drive f:\. Residing on drive C:\ everything works well. Maybe it's really some bug: Drive f:\ is a JBOD-Raid on my PC. 

 

@cdob:

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?

 

 

My decision creating a multiboot-dvd was last minute, when I discovered my nlite-iso is running pretty well. I just added an old version of hiren's boot-CD (small in size, fast linux onboard) to provide a partition-manager and repair-kit. It is working already. Actually I need no help with it.

My problem is the final installed XP has problems with some characters. With RockRidge XP's textsetup has trouble reading files.

Should I just try Iso-Level3 then?

I know some file-names HAVE to be uppercase. Therefore I look for a way to allow both, upper- and lowercase, compatible with textsetup. I took care already keeping iso below 4GB.

 

When setting up a computer someone always needs a partition-manager. Making my dvd multi-bootable would save swapping disks.

 

 

 



#18
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,029 posts
  • OS:none specified
  • Country: Country Flag

No, I DID CREATE THEM! Of course!  And I don't need to explain why! The fact I did creat them lets you now that there WAS need for them because I decided so.

Well, you don't *need* to, but it would have been nice of you to provide this information :yes:.
 

The only important information here for you is: mkisofs provides a switch to follow hardlinks in windows. Hence there is not even a problem anymore - just something to learn.

Let me assure you how that information is not at all important to me, basically because I already knew about it, most probably long before you learned about the existence of nlite or mkisofs (but thanks for providing it :)). For the record, the version of mkisofs I use has even a  "-duplicates-once" switch!  :w00t:
 

The almost 4GB size is the result of many applications I added to my build. They are all running fine. There is nothing complex about it.

Good. :)
 

My problem is now to choose a proper filesystem. Joliet4  seems to work for installation. However, after setup finishes special characters are displayed wrong on the dvd. Very annoying because of german Umlaute (Ä, Ö and Ü). I can't acces my additional folders now.

Then the thingy is maybe not actually "running fine" or maybe it is "running fine BUT with wrong characters displayed" :unsure:.
 

Mkisofs is from the official homepage. Not my fault it's not newest version. Only strange thing: It still crashes when I run it from drive f:\. Residing on drive C:\ everything works well. Maybe it's really some bug: Drive f:\ is a JBOD-Raid on my PC.

The basic question remains,why would you ask for suggestions/guidance and later do something different?
By the same tokens you should use only the grub4dos version that you can find on the sourceforge or gna.org page.

jaclaz



#19
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 88 posts
  • OS:XP Home
  • Country: Country Flag

Grub4Dos doesn't get updated since years. The provided link is pointing to some chinese website. I guess somebody did just continue working on it. This is called a fork.

I downloaded the newest Mkisofs from the official Sourceforge-Site, here. I'm sure somebody here knows even some newer fork. But actually this one is working. So the question actually is not

why would you ask for suggestions/guidance and later do something different?

 

 

The question is rahter: "Why should I change something that is already working?"

 

 

Then the thingy is maybe not actually "running fine" or maybe it is "running fine BUT with wrong characters displayed"

Mkisofs has an option to define input- and output-character-set.

 

I now tried ISO-Level 3 with Codepage 850. The Iso installed properly. However, Umlaute are still displayed wrong on DVD in explorer. At least I can access these folders now (was not possible with Joliet-4 and unset codepage). Seems I have to fiddle around a bit to get the right combination.

 

 

My mkisofs-command I used was:

mkisofs -v -iso-level 3 -l -D -d -J -joliet-long input-charset cp850 -output-charset cp850 -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.4.iso F:\n-Lite-Temp

I got some warnings with this, but mkisofs didn't stop creating the ISO:

Warning: creating filesystem that does not conform to ISO-9660.
Warning: creating filesystem with (nonstandard) Joliet extensions
         but without (standard) Rock Ridge extensions.
         It is highly recommended to add Rock Ridge
mkisofs: Iconv based locales may change file name length.

Iso was bootable. Textsetup and everything else had no reading-problems.
 

Let me assure you how that information is not at all important to me, basically because I already knew about it, most probably long before you learned about the existence of nlite or mkisofs (but thanks for providing it :)). For the record, the version of mkisofs I use has even a  "-duplicates-once" switch!  :w00t:

 

 

LOL, ROFL :lol:  I so much don't give a s***!

 

Hardlinks are transparent to windows-programs. I use them extensively. Not even XP distinguishes between usual folders and hardlinked ones. Mkisofs seems to be an exception. I guess it's because it's a linux-tool. Nice to see they didn't forget windows-hardlinks!



#20
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,029 posts
  • OS:none specified
  • Country: Country Flag

Grub4Dos doesn't get updated since years. The provided link is pointing to some chinese website. I guess somebody did just continue working on it. This is called a fork.

Not in this case.
JFYI (already provided link):
http://reboot.pro/topic/14-grub4dos/
http://reboot.pro/to...b4dos/?p=133739

The question is rahter: "Why should I change something that is already working?"

Possibly to get something that is working better? :unsure:

jaclaz
 
 
 

 
jaclaz

#21
steve6375

steve6375

    Junior

  • Member
  • Pip
  • 57 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Grub4Dos doesn't get updated since years. 

grub4dos is being actively developed and improved by chenall and others - see here.

 

version 0.4.6a includes Joliet3 (soon also Joliet4) support and has it's own USB driver (like Plop but it is rd/wr and built into grub4dos).


Visit www.rmprepusb.com for RMPrepUSB, the new Easy2Boot multiboot USB solution and 100+ tutorials on booting from USB drives.


#22
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

My problem is now to choose a proper filesystem. Joliet4  seems to work for installation. However, after setup finishes special characters are displayed wrong on the dvd. Very annoying because of german Umlaute (Ä, Ö and Ü). I can't acces my additional folders now.

Strange, seems to ignore Joliet fileystem.
Compare file systems at ISOBuster. The free version supports ISO9660, Joliet and RockRidge.

Cygwin/Iconv can handle Umlaute at ISO9660:1999, -iso-level 4 nowadays.
Haven't done this in years. Seems to be some fun.
Back then I used a environment variable:
set LC_ALL=en_US.CP850
Simple example added: "mkisofs -iso-level 4 -o o.iso ."
Umlaute are listed correctly, given CP850 is set at windows. That's the default codepage at a german installation.
 

Mkisofs is from the official homepage.

Which files do you use?

http://cdrecord.berl...e/cdrecord.html
ftp://ftp.berlios.de/pub/cdrecord/alpha/win32/
ftp://ftp.berlios.de/pub/cdrecord/alpha/
Jörg offers source code only nowadays, last win32 binaries are from 2001.

http://www.student.t...k/index_en.html
Thomas offers binaries since then.
 

Actually I need no help with it.

That's good, because support won't be within forum rules.
 

Should I just try Iso-Level3 then?

I've to correct: -allow-lowercase allows lowercase.
-iso-level 3 -N -D -d -relaxed-filenames -allow-lowercase -allow-multidot -joliet-long
 

I know some file-names HAVE to be uppercase. Therefore I look for a way to allow both, upper- and lowercase, compatible with textsetup.

Post #12 refers FileCase.exe http://www.911cd.net...indpost&p=26119
Uppercase XP files in root, all folder and files within I386
 

I took care already keeping iso below 4GB.

Core boot files has to be below 4 GB LBA, the ISO file can be bigger.

Edited by cdob, 01 April 2014 - 01:46 PM.


#23
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 88 posts
  • OS:XP Home
  • Country: Country Flag

Thank, cdob. I'll try your new suggestions.

 

@Jaclas and Steve:

 

Please look at your posted links yourself. The project changed to a chinese host in 2009. I didn't know that and I think it's very interesting. However, the original gnu grub4dos died before. The project wasn't maintained for years! Good thing somebody saved the project.

 

 

Which files do you use?

The ones I linked in my post.
 



#24
cdob

cdob

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 962 posts

I'll try your new suggestions.

Summerize this to:
uppercase required files yourself
set LC_ALL=en_US.CP850
mkisofs -iso-level 4
do not use Joliet

#25
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 88 posts
  • OS:XP Home
  • Country: Country Flag

I typed this now:

set LC_ALL=en_US.CP850

mkisofs -v -iso-level 4 -l -N -D -d -volid "XP-SP2 -DE_Silent" -A GRLDR/MKISOFS -sysid "Win32" -b grldr -no-emul-boot -boot-load-seg 0x1000 -relaxed-filenames -allow-lowercase -allow-multidot -hide grldr -hide boot.catalog -posix-L -o n:\XP-SP2-Bugfix4.5.iso F:\n-Lite-Temp

Iso-Level 4, no Joliet

 

For some reason it didn't accept input-charset cp850 anymore. Output-charset cp850 didn't work either because "input and ouptut charset are different". Hope it will work nevertheless. At least mkisofs did accept the line "set LC_ALL=en_US.CP850". It said something about "switching to cp850".

 

Are you sure ISO 1999 is a good choice? Somewhere within all the posted links someone stated, ISO1999 was worst-case with compatibility. I don't know the differences between version 3 and version 4.







Also tagged with one or more of these keywords: iso9660, joliet, boot, filename, lowercase, uppercase, multiboot

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN