Please see the attachment for more information (rename from ZIP to MHT)
Thanks,
pcgeek
Posted 17 April 2008 - 10:41 PM
Posted 17 April 2008 - 11:02 PM
Posted 17 April 2008 - 11:29 PM
Posted 17 April 2008 - 11:54 PM
Posted 18 April 2008 - 12:09 AM
Posted 18 April 2008 - 08:42 AM
Posted 18 April 2008 - 04:36 PM
Posted 18 April 2008 - 04:38 PM
Posted 18 April 2008 - 05:00 PM
Posted 18 April 2008 - 05:31 PM
Posted 18 April 2008 - 05:34 PM
Posted 19 April 2008 - 01:09 AM
Posted 21 April 2008 - 05:39 PM
My install.wim container is indeed set to "1" and the boot.wim container is set to "2" ... these are the default settings I believe, as I didn't even know they existed before!It looks to me like you need to make sure that the VistaPE 'Preconfig' setting has 'install.wim container' at value '1'.
If that doesn't fix it, there might be a conflict of version numbers. Vista Folder Names often have the version number in them, and VistaPE has them hardcoded (last time I looked...), which is one reason why v.11 is for pre-VistaSP1, and v.12 beta for VistaSP1/Server2008... I think?
To see if the .wim files are mounting properly, there is a 'debug' script folder in Winbuilder Interface. Select the mount script and click the lttle green arrow to run that script only. Then have a look in BootWimSrc/ and InstallWimSrc/. Don't forget to run the unmount script afterwards!
Posted 21 April 2008 - 08:31 PM
Posted 22 April 2008 - 12:28 AM
Ok, well I think I figured out the first part. The boot.wim index was 2 by default, and should have been 1, since that has the Windows PE source files, not the Vista setup files.
Now I'm running into an issue where the system blue screens on startup, during the Vista-like splash screen. I'm stripping out some components, such as Windows Explorer, some additional drivers, dotNET, and so on.
Any ideas on beginning to troubleshoot this issue?
Posted 22 April 2008 - 01:30 AM
I was trying to use a Windows Vista DVD although I do have the WAIK v1.1 installed on the same machine I'm developing the VistaPE image on. After switching the boot.wim to index #1, I seemed to "get farther" in the VistaPE build process than I did when it was set to 2. And yes, I did analyze the boot.wim file, and noticed that index #2 is "Longhorn Setup." I believe that index #2 of boot.wim is missing many of the files that boot.wim has, because the huge number of missing files approached zero after I changed from #2 to #1.You are on the right track. I'd strip out everything that is not required to start, then work my way up.
Regarding those boot.wim images... AFAIK #1 is the source files and #2 is/was setup.exe - as you mentioned - plus the source files. #2 is flagged as the 'boot' image so that when you insert the DVD and the #2 image loads into RAM, the setup screen begins. I'm not sure why #1 is even there.
I could never figure out why NightMan had #2 as the default, but it worked OK. Because, VistaPE is taking the source files only, #1 and #2 seemed interchangeable to me, but I never tried. Maybe things are a bit different now with downloadable versions.
However, with the WAIK's winpe.wim, there is only one image. If VistaPE is using that as source, the 'boot image container' does need to be set at #1.
Regards
Posted 22 April 2008 - 02:11 AM
I was trying to use a Windows Vista DVD although I do have the WAIK v1.1 installed on the same machine I'm developing the VistaPE image on. After switching the boot.wim to index #1, I seemed to "get farther" in the VistaPE build process than I did when it was set to 2. And yes, I did analyze the boot.wim file, and noticed that index #2 is "Longhorn Setup." I believe that index #2 of boot.wim is missing many of the files that boot.wim has, because the huge number of missing files approached zero after I changed from #2 to #1.
By the way, I'm not sure if it matters at this point, but I'm testing on both a Lenovo T60 and VMware Server 1.0.4. Both of them exhibited the same blue screen behavior directly after the splash screen.
Thanks for your continued help.
0 members, 0 guests, 0 anonymous users