g3neration

It looks that way but I have no idea as to how to get it "uncorrupt". Even doing just a basic copype x86 winpe and then trying to mount the newly created wim file in WinPe still gives me no luck. Although I just remembered that I dont have access to a Vista box as of yet and my technician PC is running XP. Not sure if that has anything to do with it. [Edit] Just checked and there seems to have been a hotfix for XP x86 version. I'm on XP x64. Doesnt seem to be any issues there. Wimfltr and fltmgr service are both started and running.

Thanks for the info, but unless I'm missing something, its still not working for me. I did follow the pdf and its pretty much the same steps I did. Imagex is still not working for me. The error message that I get is that there is an error opening the file and that the data is invalid. I can mount it fine on the technician PC but on a WinPE, so far no luck. As for Imagex support on WinPE itself, I got the unsupported info from: http://forums.microsoft.com/TechNet/ShowPo...8&SiteID=17 There were also a few more sites that posted that it wasnt just a simple copy and pasting of tools\x86 or tools\servicing, although I can't seem to find them now. Would be really interested in what the steps were to get imagex to work.

Hi, I apologize if the solution has been posted already, but doing a search hasn't really posted any results that have worked as of yet. I am aware that MS does not support imagex in WinPE but I seem to get the impression that many have already found a way to make it work. My desired result is to get a wim file mounted in WinPE 2.0. So far the steps I have taken are: 1) copy tools\x86\* to winpe\mount\windows\system32 2) install HTA, MDAC, Scripting, WMI packages Then PXE booting into WinPE: 1) rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 X:\windows\wimfltr.inf 2) net start wimfltr 3) double check fltmgr service is running All these seem to be fine and it states that the wimfltr service is started. Trying to mount a wim file though gives me an error that states that the data is invalid. Am I missing a file? Or does a registry edit need to be done? Thanks for any info.

Yep. Nothing seems to be working. At first I thought it might be a TFTPD32 issue as the DHCP server for it was giving me problems. Therefore I also installed WinAgents TFTP server but still the same issue.

My current problem is as follows: I've setup a test environment in VMware Workstation 6. This consists of two VM's, a Vista x64 box and the PXE client. On the Vista box, I've installed WAIK (WinPE2.0), MagikDHCP, and TFTPD32 with the TFTPD32 acting purely as a TFTP server. I have the DHCP server point to pxelinux.0 in c:\tftpboot. The relevant winpe files are in c:\tftpboot\boot, with bootmgr.exe in the root folder ( c:\tftpboot ). My pxelinux.cfg/default file is pretty simple and it is as follows: LABEL linux kernel kernel/vmlinuz append vga=normal initrd=initrd/initrd.gz -- Label win kernel boot/pxeboot.0 PROMPT 1 TIMEOUT 0 My problem is that after pxeboot.0 is loaded, it requests from the TFTP server bootmgr.exe but the TFTP server does not respond back. I've run a packet trace with wireshark to verify this. At first I thought it may be one of the options regarding TFTPD32, ie. PXE compatibility, Translate Unix file names, etc. But after playing around with all the combinations, its still unsuccesful. The packet trace shows that its asking for: 533 520.398712 192.168.80.254 0.0.0.0 TFTP Read Request, File: bootmgr.exe, Transfer type: octet, blksize=1456 I cant seem to narrow down this problem. Pxeboot.0 is transferred fine as shown from the packet capture. 429 517.599844 192.168.80.254 192.168.80.100 TFTP Read Request, File: boot/pxeboot.0, Transfer type: octet, tsize=0, blksize=1408 430 517.985751 192.168.80.100 192.168.80.254 TFTP Option Acknowledgement, tsize=25068 Any help would be great.