Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Recommended Posts

The latest 0.4.6a version understands Joliet4 - I gave a link a few days ago (it was in a bug report Issue - last download). Although not properly released yet, I have been using it for days and found no issues.

Edited by steve6375

Share this post


Link to post
Share on other sites

Wow, so much information, so many solutions!!!

As to the provided mkisofs-link: The program is not running since the zip-file doesn't contain cygwin. I copied the cygwin-Dll-files from my currently used mkisofs but without success. They are not compatible with that version. Still not sure if my current mkisofs isn't newer. It was part of cdrtools-4 (the new link points to version 3.01a23).

Neither Nlite nor MS care about case at hotfix integration. Both expect uppercase at following step

Well, if you are sure about that, I will modify my HDD-files.

No, Windows can't read rock ridge. If possible avoid rock ridge at XP installation cd.

Very useful information. Thank you.

As well as these:

Iso9660 Level 3 proihibits lowercase, hence mkisofs uppercase the name. Compare the name at ISOBuster.
Textmode can't read joliet, cdfs.sys is not active that erarly.
-allow-lowercase allows lower case: it's preservers case from the hard disk:
uppercase names goes uppercase, lowercase names goes lowercase

and these:

if the -allow-lowercase switch is NOT used, then any non-conforming filename (in iso-level up to 3) will be uppercased to conform to ISO9660.(...) The downside is that the gfx-boot.gfx or GFX-BOOT.GFX may become GFX_BOOT.GFX.

Grub4dos maybe case sensitive still.
Does filenames within menu.lst has to match case at DVD?

In this new Grub-Beta-Release (0.4.5c 2014-01-17), I downloaded from a link posted here, it is not case sensitive in V4.8. I hit e and changed SETUPLDR.BIN to SETUPpldr.bin. XP-Setup is starting as usual, afterwards.

Any of the other things that you added to your DVD (and that you won't talk about :whistle:) may have one requisite or the other, some mkisofs parameter that "fixes" one thing may "create an issue" with something else, this is the dificult part when making "multi" CD/DVD's.

Who said I don't wanna talk about them?! They are just off-topic here: They are all integrated as hotfixes (created with addon-maker) or called from RunOnceEx.cmd, when case doesn't matter anymore. This is the multiboot-subforum. My trouble, with integrating / installing .NET1.1 and it's updates or with sygate always crashing after silent install, may be some topic in a different sub-forum. Only important thing here is: I don't need special characters in textsetup but later. Change of codepage did help. Thanks again.

Edit:

I just opened my old version 4.4 (ISO-3, Joliet, input-charset cp850, output-charset cp850, no additional tweaks) with isobuster. Isobuster shows me mixed case in both categories, ISO and Joliet. The graphical grub did work with this iso.

The used mkisofs-command 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

When ISO-3 forces all filenames to uppercase, how is this possible? Is isobuster showing something wrong? How it comes GFX-BOOT.GFX was not transformed to GFX_BOOT.GFX? However, the ISO-category in isobuster shows me broken Umlaute (should be no problem for me though - don't know why I discarded this built).

Edited by whocares02

Share this post


Link to post
Share on other sites

re. grub4dos not being case sensitive - it depends on the filesystem.

From observation:

CDFS filesystems seem to vary depending on how they were made.

Take a look at a recent case involving a WinPE ISO which wouldn't boot from grub4dos using 'chainloader /bootmgr' here.

However, an isolevel 4 proxmox-ve_3.2-1933730b-2.iso file, when map'ed by grub4dos shows files of both upper an lower case in the root of the ISO, but I can list a file by specifying either upper or lower case:

map /proxmox-ve_3.2-1933730b-2.iso (0xff)

map --hook

root (0xff)

ls /EULA

ls /eula

both work

Edited by steve6375

Share this post


Link to post
Share on other sites

mmm...they don't mention what filesystem was in use in that iso. Possible newest grub can even read joliet. And that guy didn't use newest grub...

Share this post


Link to post
Share on other sites

As to the provided mkisofs-link: The program is not running since the zip-file doesn't contain cygwin. I copied the cygwin-Dll-files from my currently used mkisofs but without success. They are not compatible with that version. Still not sure if my current mkisofs isn't newer. It was part of cdrtools-4 (the new link points to version 3.01a23).

Come on :):

http://www.student.tugraz.at/thomas.plank/index.html

get the needed Cygwin1.dll that is a separate download: http://www.student.tugraz.at/thomas.plank/cygwin1.dll_1.7.28_.zip and if needed the Zusätzliche DLLs http://www.student.tugraz.at/thomas.plank/dlls.zip

When ISO-3 forces all filenames to uppercase, how is this possible? Is isobuster showing something wrong? How it comes GFX-BOOT.GFX was not transformed to GFX_BOOT.GFX? However, the ISO-category in isobuster shows me broken Umlaute (should be no problem for me though - don't know why I discarded this built).

Probably it forces to uppercase in the ISO9660 "namespace", not in the Joliet one, I believe.

jaclaz

Share this post


Link to post
Share on other sites

Thank you, I didn't notice the cygwin-ddl-download. Don't believe cdrtools3.something was newer then v4 though.

I attached two isobuster-screenshots for you, showing the root-folder of my version 4.4-Iso.

Edit:

The version IS newer. Thank you then.

mkisofs 3.01a23 (i686-pc-cygwin) Copyright (C) 1993-1997 Eric Youngdale (C) 1997-2014 Joerg Schilling

Edit2:

@cdob: I was just about trying your script:

rem UpperCase XP files at hard diskrem Win32 Console ToolBox http://stevemiller.net/apps/ren F:\n-Lite-Temp\i386 I386filecase.exe /u F:\n-Lite-Temp\win*filecase.exe /u /s /d F:\n-Lite-Temp\i386

However, where do I get filecase.exe?

Edit3:

Allright, found it (as mentioned in line 2).

Edit4:

It's just an idea...but...is it possible ISO-3 includes UDF somehow? Because UDF supports mixed cases for filenames. When using imgburn and choosing iso-creation, the 3rd filesystem from top is ISO9660 + Joliet + UDF. Maybe Textsetup/grub4dos can read UDF...I'm still not into DVD-filesystem-theory....

post-390386-0-17544600-1396471249_thumb.

post-390386-0-22689300-1396471252_thumb.

Edited by whocares02

Share this post


Link to post
Share on other sites

I finally got a working Iso:

  • I changed all XP-filenames to uppercase, as suggested (thanks to cdob/Steve Miller).
  • I changed the line gfxmenu /GFX-BOOT.GFX in menu.lst to gfxmenu /GFXBOOT.GFX and renamed GFX-BOOT.GFX to GFXBOOT.GFX
  • I set LC_ALL to en_US.CP850
  • I set input- and output-charset to cp850 in mkisofs
  • I used Iso Level 3 with Joliet-Support

The resulting Iso has

  • Graphical Grub4Dos
  • All file- and foldernames uppercase in Grub4Dos' command-line (Iso9660)
  • Special characters converted to underscores in Grub4Dos' command-line (ISO9660)
  • Umlaut- and special-character-support in Windows-Explorer (Joliet)

Here my input at the command-line:

set LC_ALL=en_US.CP850mkisofs -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 E:\XP-SP2-Bugfix5.1.iso F:\n-Lite-Temp

Something missing? Yes, sure. Grub4Dos' menu-help can't display Umlaute. Windows File Protection doesn't accept the CD as original. However these are rather minor bugs I can live with.

Thanks for all the help.

Edited by whocares02

Share this post


Link to post
Share on other sites

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.

Since when did msfn start allowing discussion that includes hirens? Even the newest versions are still warez and here he says he's using a old version

Share this post


Link to post
Share on other sites

Something missing? Yes, sure. Grub4Dos' menu-help can't display Umlaute. Windows File Protection doesn't accept the CD as original. However these are rather minor bugs I can live with.

Grub4dos supports UTF-8 encoding alright, that allows to have all the special characters, you may need to load a special font with the font command, see:

http://reboot.pro/topic/19076-grub4dos-menu-font-type/

http://rmprepusb.blogspot.co.uk/2013/11/defining-fonts-in-grub4dos.html

http://www.rmprepusb.com/tutorials/grub4dos/fonts-and-graphics

Also, you may want to create a "German keyboard layout" for grub4dos. :unsure:, some hints and a basic worksheet are here:

http://reboot.pro/topic/8056-keyboard-layout/

http://reboot.pro/topic/8056-keyboard-layout/?p=68522

The link to the (partial) german layout is dead, but can be retrieved form the Wayback Machine:

https://web.archive.org/web/20090702065631/http://www.lrz-muenchen.de/~bernhard/grub.html

https://web.archive.org/web/20081206092135/http://www.lrz-muenchen.de/~bernhard/german.txt

jaclaz

Share this post


Link to post
Share on other sites

For NO apparent reason :whistle:

The latest 0.4.6a version understands Joliet4 - I gave a link a few days ago (it was in a bug report Issue - last download). Although not properly released yet, I have been using it for days and found no issues.


http://reboot.pro/topic/19683-boot-bitdefender-rescue-iso-from-usb-mystery/?p=183147

OK, found the problem. The version of grldr on the non-working was a very new March 2014 version (which otherwise seemed to work OK). When I updated it to an earlier one - it all works!

Must be a bug in that version.


jaclazDUCKEMOTICON_FINAL.gif

jaclaz

Share this post


Link to post
Share on other sites

1 - Kel is correct. One post did mention warez. Please do not discuss warez of any kind. If you haven't already doens so, pleae read the rules:

http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules

2 - There are two items of note (AFAIK) in the construction of a CD/DVD: File System and Character Set. Here gives a simple explanation of Character Set per File System, albeit rather confusing because of the last Joliette statement:

http://www.cdrinfo.com/forum/tm.asp?m=900

The topic is about Nero but still "kind of" applies. The "erroneous" statement actually refer to the Character Set applicable to the Joliette. The following is Wikipedia (mostly, but not always, dependable reference):

http://en.wikipedia.org/wiki/ISO_9660

TextMode -only- reads ISO-9660 (via the ElTorito Booting - via the BIOS Boot Selection). After TextMode the Joliette is read. UDF is -not- necessary -unless- you have -very- large files (AFAIK). Please note that -most- ISO-creating/burning softwares -usually- convert non-valid Characters depending on the FileSystems being created/used. I -personally- use ASCII for the Character Set. Please also note that NEWER MS OS DVD's use UDF -but- has a -different- BootImage than XP/2K3 and earlier. Win9x -generally- does NOT care about Joliette when Clean Installing, hence the reason I use ASCII, since it -prevents- conversion of (e.g.) "-" to "_". The Wikipedia link has further links and is -only- given as a reference point for your edification.

You're becoming -very- confused and -again- randomly wandering around with a blindfold on. Indeed, -many- of the MKISOFS parameters you're using (e.g. the System Architecture) are totally unnecessary.

Use the K.I.S.S. method instead of Overkill.

HTH

P.S. Also note the difference between DVD+R and DVD-R when using it for Real Hardware and the ability to Boot from it. I don't believe DVD-RW is generally supported. :unsure:

You can look that up further for yourself via Google: dvd+r vs dvd-r

Share this post


Link to post
Share on other sites

Actually I thought I used that special version. But with double-checking, I notice I did a downgrade again for some reason. Will try it again, thanks.

@Wipi: Please don't use the quote-button for spamming. I don't need the forum's permission to integrate software into my dvd. I've had this discussion about Hiren's on a different forum already. It is officially downloadable, gets recommended in forums like microsoft, tomshardware and others and is just the only full-featured repair-cd of on the web. There is just no commercial alternative. Please just fuck-off and complain at some company..or at hiren's if you prefere that.

Share this post


Link to post
Share on other sites

Yup, I love you too it's just we have a thing called rules here and try to follow laws so we can keep the google ads and not get cease and decist letter from ms

Share this post


Link to post
Share on other sites

Hmmm... You juste earned yourself a Report Button for not reading the rules and vulgarly chastising me. This is NOT "a different forum" but MSFN instead.

You're welcome. ;)

BTW, My name isn't Wipi - it's submix8c. :yes:

Share this post


Link to post
Share on other sites

I think he meant me (wpi)

I also don't need his permission to post in this thread.

Edited by Kelsenellenelvian

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.

×
×
  • Create New...