Jazkal

Does v11 require dotnet framework? EDIT: What option did you use to build your WinPE2 wim?

Oops, should have said that I already tried renaming the file, and re-ran HFSLIP. It didn't work for me. So I switched back to XPize 4.6.

http://www.msfn.org/board/index.php?showtopic=100106 Wanted to see if there were plans to support the new XPize Darkside release? Thanks

Not to go off on a complete tangent, but . . . If you have multiple servers, I would assume they are on their own IP segment (if this assumption is wrong, then ignore everything else) Such as: 10.30.1.200 and maybe a 10.30.2.200 Why not just have a WinPE2 side IP detection script that will tell you what segment your on, and then you know what server it booted off of. If I'm not understanding what your trying to do, just ignore the the crazy old man.

It looks like HP finally figured out what was wrong with the 585 G2. http://h18004.www1.hp.com/products/servers...=reg_R1002_USEN The firmware fix (beta) listed, does work on my tests with WinPE v2.0

Any solution for this problem yet?

it is supported in the current production build. http://www.hfslip.org/changelog.html

No, I'm waiting for a fix from HP

I'm not sure, but I think you would get more help in the "Unattended Vista" forum.

Even though you haven't said it, I'm guessing you are trying to create an install DVD that will install your images?

it might help if clarify what it is your doing. What WinPE version are you using? What are you trying to do? What do you mean by "Master computer"?

You need to be more specific with what you want to do with it. You can burn any file onto a DVD (if it is smaller than the 4.4gig size of the DVD)

I would do a search inside *.inf files only. Once you find the INF file that references the SYS file, then remove the INF file and SYS file, then re-install your driver. EDIT: I did a search for "b57nd60x", and found these three files: drvindex.dat netb57vx.inf netb57vx.pnf I would leave drvindex.dat alone, but delete the other two, then reinstall your driver. Inside the INF file, I only found reference to: b57nd60x.sys Delete this file also

Anybody have a link to the x64 version of this file?

Once you have the wim mounted. Do a search of all the inf's for that sys file name, and remove the sys file and inf that references it. Then add you driver. Then you'll see what it does.

I know you can use devcon to give you a list of the actual INF's and SYS files loaded per device.

I launch all my HTA's via network share (mapped drives), that way I can update them without having to rebuild my WinPE Images. In WinPE2 I use the following to call my HTA files: cmd.exe /c Mshta.exe z:\PATH\FILENAME.hta

yes, when you build your WinPE image, use this cmd: peimg.exe" /inf:%DRIVERINF% %isosource%\Mount\Windows Before you finish up the WIM. It will over write the driver that is built in. If you mean load the x64 driver in WinPE x86, then no, you can not mix x64 and x86 drivers, they will not work.

That would be great, we are down to 2 final issues before we can roll out WinPE2 to our production systems. This issue is one, and the other is WinPE2 x64 not working right on the HP boxes.

As far as I know, no one else has been able to get it to work on WinPE2. There are dotnet2 plugins for WinPE v1.6, but not v2.

if you run a devcon scan (inside of WinPE), does the problem nic show up in the list? devcon.exe find pci* You may have to add devcon to your build.

Here is a possible thread that might help: http://www.msfn.org/board/index.php?showtopic=93468

i'm not sure why you are getting that error. If you can get it up into windows, run a devcon report: devcon find pci* This will tell us what devices it has, and then you can load the drivers into PE

If you compress the WinPE2 image durring creation, you can get that down around 120mb, without removing anything. EDIT: Here is a list of the commands I was talking about to compress the PE Image: copype.cmd x86 C:\winpe_2x86 imagex.exe /mountrw C:\winpe_2x86\winpe.wim 1 C:\winpe_2x86\mount xcopy "C:\winpe_2x86\mount\Windows\System32\Boot\*.*" C:\winpe_2x86\mount\Windows\System32\*.* /e /y peimg.exe /install=WinPE-HTA-Package C:\winpe_2x86\Mount\Windows peimg.exe /install=WinPE-WMI-Package C:\winpe_2x86\Mount\Windows peimg.exe /install=WinPE-Scripting-Package C:\winpe_2x86\Mount\Windows peimg.exe /install=WinPE-XML-Package C:\winpe_2x86\Mount\Windows peimg.exe /install=WinPE-MDAC-Package C:\winpe_2x86\Mount\Windows peimg.exe /inf:%DRIVERINF% C:\winpe_2x86\Mount\Windows peimg.exe /prep /f C:\winpe_2x86\Mount\Windows delete C:\winpe_2x86\ISO\sources\boot.wim imagex.exe /boot /compress maximum /capture C:\winpe_2x86\Mount C:\winpe_2x86\ISO\sources\boot.wim "WinPE2" imagex.exe /unmount C:\winpe_2x86\mount

Unless you have a Software Assurance agreement with Microsoft, your only option for WinPE is either VistaPE (WinPE 2.0) or BartsPE.