Integrating WinXP Setup CD to UBCD vs RockRidge
Posted: Mon Jul 11, 2005 12:37 am
Hi,
UBCD is great and very usefull. It is better than the other "bootCD" because it can integrate them!
Since I ve discover the customizing possibilities, I would like to integrate also the Windows XP Setup CD.
I've add the following in my custom.scn file:
print " [F4] Setup Windows XP SP2 Professional "
if ($lastKey == key[f4]); then isolinux /boot/images/w2ksect.bin
The given mkisofs command "mkisofs -N -J -r -o \ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 ubcd"
freeze the computer when I press F4 (Isolinux is launched, but the winNT sector can not launch NTLR)
Then, I tested many parameters to mkisofs (see below)
Actually, it appears that WinXP CD (suppose it applied to all WinNT) is incompatible with the rockRidge extension. The WinXP setup start only when I removed the "-r" option.
Besides, I saw a pb with the RockRidge (that is, with the "-r" option activated) extension under linux:
Due to long filename limitation, a "rr_moved" dir is created on the root of the CD with "-r", causing some deep directories not be readable under linux.
This pb can be resolved by adding "-l -D" (up to 31 char in filename and deep directory: Why is mkisofs limited to 6 dir when Windows tools (nero, ...) goes to 8 ?)
But the long dir and filename cannot be read under old OS like MSDOS.
The question is: 1/ where are the RockRidge extension realy needed? Will I have problem by desactivating them?
I ve tested the iso with only joliet, and all small linux distribution of the UBCD can read it. It is indeed better than RR because it avoid the previous "rr_moved" problem.
Finally, the best command I found is
"mkisofs -N -J -joliet-long -D -V "UltimateBootCD" -log-file mkisofs.log -o ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 ubcd"
2/ I've just seen UBCD4Win, but is is NOT the same stuff.
"UBCD4Win is a Windows® "pre-install" environment, basically Windows® booted from CD" whereas I just want to copy the WinXP Installation CD.
Other solution / mkisofs option are welcome to enhance my CD!
I suggest to update the customize page on the website with this information (RockRidge extension with NT CD).
--------- other parameters tested -------------------------------
Before I've read the tutorial "Integrating a Windows Boot Disk into Ultimate Boot CD"
I've tried with "memdisk", "bcdw boot" and "discemu". And also with "chain" that I saw in 911CD.
Now, I think isolinux is the good command.
Then, I tested many parameters to mkisofs (version 2.01a17)
I had to remove the "-r" option in order that WinXP installation can start. "-R" make the same as "-r".
Then I wanted to remove the the warnings about the the too long filename and dirname (more than 6 sucessive dir).
the "-iso-level 4" (ISO-9660:1999 version2) option in mkisofs resolve these problems, but is not compatible with the loader.bin (the CD does not boot anymore)
For the too deep directories, the "-D" option accept them. And the "-l" option solve the too long filename (up to 31 char)
Then, I understood these function only affect the cd when no joliet extension can be loaded (means is is ignored under Windows that read the joliet layer)
So it works with the following command:
"mkisofs -N -J -joliet-long -l -D -V "UltimateBootCD" -o \ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 ubcd"
It seems to works well, despite I already know that the long filename would not work under dos.
I was also made wrong about the long name with WinImage6: the software read the Joliet layer only if I had RockRidge (without RR, it read as DOS would) !
UBCD is great and very usefull. It is better than the other "bootCD" because it can integrate them!
Since I ve discover the customizing possibilities, I would like to integrate also the Windows XP Setup CD.
I've add the following in my custom.scn file:
print " [F4] Setup Windows XP SP2 Professional "
if ($lastKey == key[f4]); then isolinux /boot/images/w2ksect.bin
The given mkisofs command "mkisofs -N -J -r -o \ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 ubcd"
freeze the computer when I press F4 (Isolinux is launched, but the winNT sector can not launch NTLR)
Then, I tested many parameters to mkisofs (see below)
Actually, it appears that WinXP CD (suppose it applied to all WinNT) is incompatible with the rockRidge extension. The WinXP setup start only when I removed the "-r" option.
Besides, I saw a pb with the RockRidge (that is, with the "-r" option activated) extension under linux:
Due to long filename limitation, a "rr_moved" dir is created on the root of the CD with "-r", causing some deep directories not be readable under linux.
This pb can be resolved by adding "-l -D" (up to 31 char in filename and deep directory: Why is mkisofs limited to 6 dir when Windows tools (nero, ...) goes to 8 ?)
But the long dir and filename cannot be read under old OS like MSDOS.
The question is: 1/ where are the RockRidge extension realy needed? Will I have problem by desactivating them?
I ve tested the iso with only joliet, and all small linux distribution of the UBCD can read it. It is indeed better than RR because it avoid the previous "rr_moved" problem.
Finally, the best command I found is
"mkisofs -N -J -joliet-long -D -V "UltimateBootCD" -log-file mkisofs.log -o ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 ubcd"
2/ I've just seen UBCD4Win, but is is NOT the same stuff.
"UBCD4Win is a Windows® "pre-install" environment, basically Windows® booted from CD" whereas I just want to copy the WinXP Installation CD.
Other solution / mkisofs option are welcome to enhance my CD!
I suggest to update the customize page on the website with this information (RockRidge extension with NT CD).
--------- other parameters tested -------------------------------
Before I've read the tutorial "Integrating a Windows Boot Disk into Ultimate Boot CD"
I've tried with "memdisk", "bcdw boot" and "discemu". And also with "chain" that I saw in 911CD.
Now, I think isolinux is the good command.
Then, I tested many parameters to mkisofs (version 2.01a17)
I had to remove the "-r" option in order that WinXP installation can start. "-R" make the same as "-r".
Then I wanted to remove the the warnings about the the too long filename and dirname (more than 6 sucessive dir).
the "-iso-level 4" (ISO-9660:1999 version2) option in mkisofs resolve these problems, but is not compatible with the loader.bin (the CD does not boot anymore)
For the too deep directories, the "-D" option accept them. And the "-l" option solve the too long filename (up to 31 char)
Then, I understood these function only affect the cd when no joliet extension can be loaded (means is is ignored under Windows that read the joliet layer)
So it works with the following command:
"mkisofs -N -J -joliet-long -l -D -V "UltimateBootCD" -o \ubcd.iso -b boot/loader.bin -no-emul-boot -boot-load-size 4 ubcd"
It seems to works well, despite I already know that the long filename would not work under dos.
I was also made wrong about the long name with WinImage6: the software read the Joliet layer only if I had RockRidge (without RR, it read as DOS would) !