Jazkal

Thanks. But I am aware of that, as it is described in the step by step walk through I listed above. Been there, tried that, didn't work.

Did you verify this was a problem? Just want to make sure it wasn't just me that had that problem.

Microsoft SUCKS! I just upgraded to the WAIK for Windows 7 RC. Went through the list of instructions in the help file. (Walkthrough: Create a Custom Windows PE Image) Got all the way to "Step 2: Mount the Base Windows PE Image" This command: Dism /Mount-Wim /WimFile:C:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mount Doesn't work any more, because the removed the "/Mount-Wim" switch, with out telling us what the replacement is. I have work to do, so I'm removing this crap. I'll look at it more later.

Here are my commands and results. And here is the final Directory contants: I would try uninstalling WAIKv3 Rebooting Deleting the WAIK folder, and reinstalling waikv3

Run this command at a command prompt, and post the output. dir /s /b C:\PE\winpe_x86

1) You have to have WAIKv3 installed. 2) If you follow through the steps listed; 'call copype.cmd x86 C:\PE\winpe_x86' ; will create the file where it should be.

oops

You can resize the WinPEv2.0+ ramdisk partition (X:) at build time. Why would this not work for you?

Thanks. Now I can have my app send me emails and text messages to my phone. Very nice.

Thats why I stopped using BartsPE years ago. I needed to have that official path of support from Microsoft. I can say that I have our systems working great on WinPE2.1 x86. I can install all versions of Windows Server (2000, 2003, 2008, x86 and x64).

I would try installing x64 from the original install.wim, to verify that this isn't the problem.

what command line did you use for the win2k8 x64 install?

You use the x86 version of the Win2k8 'setup.exe' and run with lots of command line options, including pointing to the 'install.wim' you want. (web, std, x86, x64). Monday I'll post an actual command line.

I'm lucky in that I only have to support the Server versions of the OS. We have Win2k3 x86 and x64, and Win2k8 x86 and x64 both installing from Winpe2.1 x86. See this article: http://support.microsoft.com/kb/925279/ For Win2k3 we use the winnt32.exe for a network install, but most of those are captured to a WIM for a syspreped deployment. And Win2k8 we also do network based installs, as well as syspreped WIM deployments also. I would try out those switches in that article and see if they also work for XP. You may get lucky. If not, I'll see if I can find any of my old notes on multi-boot winpe2.1 and pxelinux.

Yes, it can be done. We had dual booting using our pxelinux system. pxelinux itself points to a BCD file, which is configured to give you a menu of different options for booting. Our pointed to a x86 and an x64 WinpE boot WIM. I don't remember how we got it to work though, as we did away with the need to dual boot. We now handle all our installs (both 32 and 64 bit) through a 32bit WinPE image.

look for a command line tool called "setres.exe"

I'm really interested in the error you mentioned.

You would use that durring your WinPE build process. If you don't have a build process yet, and are just using the basic base winpe image, look in the docs and do a search for 'peimg'. That will take you to the sections you need that explain how to build a custom version of WinPE.

If I may ask, what system are you using that can't use v2.x?

After it boots up, and is sitting idle for a couple of mins (meaning it is done doing whatever). Run: wpeinit.exe See if that helps. I've seen some systems that won't load the nic drivers or network stack with out a time wait.

Give us the output of the scan if you can.

I've found that when you know the NIC driver is in the WinPE image, but it still doesn't see it, then there is a driver you need for something on the PCI bus that sits between the NIC and everything else. Try doing a scan: Then look through your driver INF files and see what other device drivers may need to be installed. EDIT: I forgot, you may need to include devcon in your WinPE image.

WinPE v1.0 - v1.6 : You have to have a EA agreement with MS to have legal access to WinPE. WinPE v2.0 - v2.1 : Anyone can download and use WinPE via the WAIK.

You want to disable IPv6 in the WinPE image?