cdob

Add Rock Ridge file extension instead: mkisofs -r

driverpack.net support both: textmode and regular pnp drivers.

Some files contain a checksum. http://msdn.microsoft.com/en-us/library/ms809762.aspx ModifyPE can set a new checksum to altered files. http://unattended.msfn.org/unattended.xp/view/web/16/ Try apply a new checksum to setupdd.sys.

Another idea: don't you use NTFS USB stick or USB hard disk? NTFS support hardlinks. This saves space. 'finddupe -hardlink' replace duplicates with hardlinks. http://www.sentex.net/~mwandel/finddupe/

A default plugin was used: (UBCD4Win)\plugin\Multiboot-003\ubcd And default UBCD4Win ISO build solution was used, that's mkisofs. Try mkisofs. Or try cdimage. Your previous example does work too. UBCD4Win does boot from \XPPE folder.

@rageaddict http://en.wikipedia.org/wiki/ISO_9660 http://en.wikipedia.org/wiki/Joliet_(file_system) http://en.wikipedia.org/wiki/Rock_Ridge_file_system Use appropiate settings at your ISO image creation application.

@rageaddict Add file system Joliet or Rock Ridge.

UBCD4Win boot fine from a 2.6GB ISO image at VMware, \XPPE foldr, profiles.exe at LBA 1306171. Default UBCD4Winbuilder used, a big dummy file added. That's no files are injected via isoimage, a new ISO image is created.

There are BIOS routines used that early. Basic files are read. Kernel file is loaded to RAM and processed. Knoppix seek knoppix file at real hardware.There is no image at real hardware. This fails. Knoppix is a example: BCDW ISO file support BIOS calls, but no hardware calls. BCDW ISO file works as designed.

Well, UBCD4Win does boot fine form \XPPE here. Which DVD media do you use? Try high quality media at a reliable writer. Remember, there is no OS error correction at PE booting. A file maybe readable at windows, but unreadable at PE. How do you prepare ISO image? What's ISO file size? What's profiles.exe LBA (Logical Block Address)? IsoBuster list LBA.

@carfan A CD drive can be accessed direct by hardware and by BIOS routines. BCDW support BIOS support. Booting ISO works as long as a livecd project use BIOS only. Booting fails, if hardware is acessed. Or windows setup program use hardware acess and find files at hardware. Files from CD are read next, not from ISO file. Currently there is no ISO file boot with direct hardware support.

Add a file \WIN51IP.SP3 to CD. Upper case is importand.

As Martin H wrote already: KB314479 refers to RIS installations. This does not match CD installation.Generally at CD boot: $OEM$ goes beside I386. This maybe at root of the CD. At multi boot solutions, this maybe a subdirectory. http://flyakite.msfn.org/ In addition there is another exeption: Textmode drivers at winnt.sif [MassStorageDrivers] http://www.msfn.org/board/TEXTMODE-MassSto...hod-t19792.html Textmode drivers goes twice to CD: $OEM$\TEXTMODE\ I386\$OEM$\ Be aware I386\$OEM$\ are read early at boot. ISO9660 file system is used. Char $ is a invalid char at ISO9660 Level 1, violade ISO9660 names. ISO9660 name has to be $OEM$, not _OEM_

Do you have a old non working DVD still? Did you fill data greater 4GB to DVD?There is a sector address limitation. Early boot files has to be below 4GB sector address. 4GB sector address limitation occurs twice: textmode: setupldr. bin read files from DVD. Once cdfs.sys is loaded and active, hole DVD is readable. first reboot: at end of textmode hivesys.inf disables cdfs.sys. Driver is not loaded at first reboot. Next asms files are read. This fails, if asms files are at end of DVD media. At PNP drivers are loaded, cdfs.sys is activatet again. Hole DVD is available. Cdimage sort directory deep levels at end of image. Asms is a deep directory. Cdimage I386 sort directory I386 only, no sub directories. If you add own files, use a deeper directory. Mkisofs dosn't sort by directory level. File sort from operating system is used. If you add own files, use a directory name at end of alphabet, e.g. \Z_add. Or use mkisofs -sort. 4GB sector address is a limitation inside setupldr.bin and ntldr. At some BIOS there occur a limitation at 2GB sector address.

Configure the BCD (Boot Configuration Database) to boot from X:. Yes, ntldr istself can't chainload another OS. However ntldr can chainload another partition boot sector(s), extracted to a file, e.g. C:\WINNT\SYSTEM32\BOOTPE.BIN This partition boot code may load another OS. No, bootsect.exe dosn't change the MBR of the hard disk.Bootsect does change the boot sectors of a partition. That way a file name bootmgr or file name ntldr is launched.

Do you use one hard disk or two hard disks? Partition was formated at XP. Partition boot code search a file ntldr. Two choices: copy file \bootmgr to \ntldr or use vista bootsect.exe to write a vista boot code: bootsect.exe /nt60 X: /force