Well, once you get everything sorted and get your disk made and working the way you described you wanted in the first post, it would be nice if you wrote up a "How To". This could serve two purposes, as a reminder for you if you need to do it again, and also to help others who might want to do something similar. I am also somewhat curious why you're using a DVD instead of USB where you might could use either this - http://www.msfn.org/...omusb-with-gui/, this - http://www.msfn.org/...winntsetup-v22/, this - http://www.msfn.org/...0-from-usb-hdd/, or any of the other options mentioned here - http://www.msfn.org/...ndows-from-usb/?
Cheers and Regards
I will certainly do my best to describe the steps I took in deviation from the standard guide if everything works as needed. As for why I wish to use a DVD to do this, it is because they are much cheaper and easier to mail than USB drives. Once I finish the disk I need to ship it to my brother who lives several states away so he can fix his install of XP, and I have neither the funds nor the inclination to purchase and ship a USB drive just for this. Besides, I have an abundance of CDs, DVDs, and DVD9s that I will probably never end up using otherwise. In the off chance I start to run short, I can easily test the ISO in a VM before burning to make sure it will boot properly.
The new image with all four setup environments boots and all four environments load with no issues. XP Pro is installing to the VM now. Will test Home and then 7 Ultimate and 7 Ultimate x64 (as those two should give a decent approximation of whether the 7 installs work) afterwards..
So XP installs without any issues, and even a slight bit faster than what it did for the original install to the VM. When attempting to install Windows 7, however, I get a most grievous error. It apparently wants a driver that is seemingly missing from the disc I created. That said, all of the files are present on the disk that were on the original Win7 disks. Those images will install to the VM, as will the original merged x86x64 image I created that has all the Windows 7 install.wim images merged into a single large file. It is only appearing on the newer disk.
The official Windows 7 w/ SP1 images do not give any errors at all when used to install to the VM, either from boot or from inside the existing OS (XP Pro at the time of attempt). They also load up to the OS Select options without issues when booted from on the physical machine, and they reach the same point when launched from inside my current install of Win7 x64. Have not tested beyond the point of asking for the partition to install to on the physical machine for obvious reasons.
The first Multi-boot disk I created, which merged the images from the two (32 and 64-bit) install.wim files, as well as including the 64-bit setup environment for making OS/startup repairs and XP Pro setup files also does not give any errors. I strongly suspect the error stems from the way I have the files set up, with the entire contents of Win7 x86 in one folder (minus BOOT and EFI files) and the contents of Win7 x64 in another. Likely the WinPE is searching for the driver and expecting to look in D:\Sources\, not D:\Win7_x86_SP1\Sources\. Though why it would look there I have no idea as I have not found any drivers in the sources folders, and the environment is running from X:\ and resembles a rudimentary Windows install complete with \Windows\System32\Drivers\ and \System32\DriverStore\, which DO contain driver files.
At this point I am lost as all suggestions I find via Google point back to the same two solutions, a bad ISO download or a BIOS issue, neither of which seem to apply here. Suggestions would be much welcomed.
Looks like I was on the right track with my suspicions before. When boot.wim is loaded, it is hard coded to look for install.wim in D:\Sources\, much the same way that the XP Setup is (was) hard coded to look for SETUPLDR.BIN in D:\I386\. The difference being that we can edit the XP files to place SETUPLDR where we want, with limitations, but changing the location of install.wim is just not possible afaik. This sucks...
Edited by Aroth, 11 May 2012 - 03:55 AM.