Windows 7 setup does not require Joliet or UDF. Plain ISO9660 is sufficient.
Sort order is importand!
Interesting, but you certainly did not use "plain" ISO9660, but rather ISO level 4
and while that might work for Windows 7 it breaks bootability of XP and ERD.
The fact why you couldn't have used the true ISO-standard is because the Win7
installation folder contains files like these:
This file has 74 characters in its name plus a file ending. This goes against any ISO-
standard there is (unless you use level 4). Also, there are tons of forums out there
were people complain about MS requiring UDF to make it bootable:http://forums.techar...ems/1098166.htm
Quote from that link:
windows vista bootable requires UDF file system & the above command creates the iso image with UDF file system.
Also, in the RC was a readme that said: "This disc contains a "UDF" file system and requires an operating system that supports the ISO-13346 "UDF" file system specification."http://www.sevenforu...udf-format.html
May be Microsoft used UDF because it is a standard contrary to ISO level 4. I assume you made this iso with
mkisofs. Did you try to include an XP-setup? Did it boot? Did you check the iso in Isobuster to verify that the iso-maker
in fact only used an ISO-filesystem?
I don't think that the sort order is my problem, because the Win7 setup starts at around 1.5GB which is way below
the 4GB limit. Since my install.wim is split, the very first install.swm is also within the 4GB range, so that's no problem.
Be aware: Cdimage sort by directory deep, Win32 ASMS files goes to end of media.
Thanks for the tip. I realized that when I tried to figure out why ERD wouldn't boot. Although the directory
was the first alphabetically, it was spread all over the disc. OSCimg does the same.
Do you have a link?
According to wikipedia all operating systems from Windows 2000 on need at least UDF 1.50
It was on german wikipedia. Unfortunately I don't have access to the site. For some reason it has been timing out
for the last couple of hours. But I have something better. The built-in help of the latest OSCDimg contains information
about the UDF-support by Windows:
I might have mixed up the version numbers, but on second thought that info doesn't mean much. The question is
which filesystems Windows supports during installation and booting and not after it has been installed, because then
you can support virtually all kinds of filesystems if you have the drivers. I doubt that the udf-driver is loaded during
install to ensure readability of UDF-based discs. The fact remains that mkisofs' UDF 1.02 doesn't work with Windows 7,
while CDimage's and OSCDimg's UDF 1.5 miraculously fix all errors.
The firadisk floppy image should work at ERD.
I checked out the post. I haven't worked with anything else than BCDW yet, except for some meddling with
CDshell that lead me nowhere, so the learning curve for me to get started with grub4dos or other loaders that
support firadisk or other RAM-loading mechanism would be pretty high. I'd like to see that only as a last resort
and would rather get into this method for my next project, unless there was a sure-fire easy-peasy way for dummies
to implement that in a couple of minutes
I would like to use your iso-settings if they also work with with XP/ERD, especially due to the massive overhead that
UDF creates. Could you please test your settings with an XP-install? In one of my attempts I tried to use compliant
ISO for XP and an extended Joliet format for Win 7 and that didn't work, so if ISO Level 4 is incompatible with XP's
setup then UDF should be the only choice left. For further tests I updated OSCDimg
to version 2.55 which finally supports not just UDF much better than mkisofs and also allows to load a sort-
file. I'm currently compiling an iso with it. Speed is painstakingly slow, but if it works then that's all that counts.
Edited by Mexxi, 12 January 2010 - 12:22 PM.