Jazkal

Try this winpe2 diskpart script: select disk 0 clean create partition primary size=20000 active assign letter C: format fs=ntfs label="SYSTEM" quick create partition primary assign letter D: format fs=ntfs label="DATA" quick exit

Are you using the format command from within diskpart? or are you using the standalon format? What is your command line for format?

I import the following reg file from my install script once WinPE2 is loaded: Windows Registry Editor Version 5.00 ;Settings for Windows XP, 2000 and 2003 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vds\Alignment] @="Alignment Settings in Bytes" "Between4_8GB"=dword:00000000 "Between8_32GB"=dword:00000000 "GreaterThan32GB"=dword:00000000 "LessThan4GB"=dword:00000000

Right before I kick off my install script on WinPE2, I use the method above: Modify your WinPE 2.0 image to have the following registry changes: HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\ALIGNMENT LessThan4GB REG_DWORD 0 Between4_8GB REG_DWORD 0 Between8_32GB REG_DWORD 0 GreaterThan32GB REG_DWORD 0 Once I've made those reg changes, then I use diskpart to create my partitions and format them, then I kick off the install.

Very nice, good job!

I know it will work, as I'm doing that now. Both WinPE v1.6 and v2.0 have x86 and x64 versions. So to kick off the Windows 2003 x64 setup, you'll need to boot the system on WinPE x64.

Very nice, thanks for sharing.

Vista did not require the latest Microsoft patches for DST. I would hope WinPE v2 (which is based on Vista) would also not require the DST patch. Have you tried manually setting the time on WinPE2, and retrying the map?

When I need to make changes to the HKCU hive, I use: reg load HKLM\PE-USR %isosource%\Mount\Windows\system32\config\systemprofile\ntuser.dat I would take a look at the hive while you have it loaded (before closing up your WIM), and see if you can see where it is in there.

Try the drivers here, these are newer than anything else I've seen out there. ftp://ftp.supermicro.com/driver/LAN/nVidi...55/Windows/RIS/ I had a new board that the older drivers wouldn't work on, but these did.

Describe the process you are going through to capture the image.

No, I have not tried the tools yet in WinPE2. I have a long list of Projects that I'm working on, and the HP tools aren't anywhere near the top of my long list. But if you have success, I would like to hear about it, because I will end up having to reproduce what you find. I hope HP at least has Beta drivers/software (that mostly work) by the time Longhorn launches, because we have to support it 100% on launch day.

I sent you a PM. I have WinPE v2.0 working on the following HP servers: DL380-G5 (32 and 64 bit) DL580-G5 (32 bit only, issues with 64 bit) DL385-G1 (32 and 64 bit) DL585-G1 (32 and 64 bit) DL385-G2 (only tested 32 bit so far, works) DL585-G2 (only tested 32 bit so far, doesn't work)

are you using Format directly or are you using the sub-command format from within diskpart? EDIT: I just tested on a box with a Win2k3 install, and the drives were formated via diskpart format command. I did see the same error, but it went away when I ran a "chkdsk c: /f" command. Will have to see if there is a fix for this, I hate to have to use a workaround.

I ended up having to open a ticket up with HP on the issue, I'll update here once I get a solution.

Yes, I can find that file. We are booting our WinPE images over PXE, using the BCD/WIM option, as I believe ISO booting over PXE is no longer an option. When I tried to load the drivers from within WinPE itself, I recieved this message for both INF's: DrvLoad: Successfully loaded bxvbd.inf After doing another devcon, nothing had changed. The NIC's aren't seen by WinPE, so the drivers aren't loaded, and NIC's don't work.

Try this workaround: http://www.msfn.org/board/index.php?showto...st&p=607059

First, I just want to say that I'm very impressed that HP would see this post and give an answer. Thanks chrislynch. After trying what you posted, however, it still doesn't detect the NIC's. You said the important one was cp006316, and inside that are two INF's: bxvbd.inf and bxnd.inf If you look in those INF's, you'll see that none of the device ID's are listed in the Devcon output from WinPE v2.0 (see above). I installed the INF's from all those packages that you listed, didn't want you to think I had only done this one package. I have verified that we are running the most current BIOS. Anything else you can think of? NOTE: your x86 link wasn't working, but I browsed through the FTP site, and used this one: ftp://ftp.compaq.com/pub/softlib2/softwar....65.lh.i386.exe

Thank you for the input. I should have given more details about the problem I'm having. I am using those drivers currently, and they are working on other systems that use those same broadcom nics. (ie. Dell 2950, and HP DL 385 G2). The problem I'm having is that WinPE v2 isn't even seeing the NICs at all. I think they are sitting behind another device that I don't have the drivers for, therefore everything behind that device isn't showing up. I have two devcon scans I'm posting below, one is from WinPE v1.6 (Windows 2005 SP1), and the other is from WinPE v2.0 (Vista PE). Both versions of WinPE have the same drivers installed. WinPE v1.6 devcon list PCI\VEN_0E11&DEV_B203&SUBSYS_3305103C&REV_03\4&21887AE&0&2048: Base System Device PCI\VEN_0E11&DEV_B204&SUBSYS_3305103C&REV_03\4&21887AE&0&2248: Base System Device PCI\VEN_1002&DEV_515E&SUBSYS_31FB103C&REV_02\4&21887AE&0&1848: Video Controller (VGA Compatible) PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&C0: PCI HOST Bridge PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&C8: PCI HOST Bridge PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&D0: PCI HOST Bridge PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&D8: PCI HOST Bridge PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&C1: PCI HOST Bridge PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&C9: PCI HOST Bridge PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&D1: PCI HOST Bridge PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&D9: PCI HOST Bridge PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&C2: PCI HOST Bridge PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&CA: PCI HOST Bridge PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&D2: PCI HOST Bridge PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&DA: PCI HOST Bridge PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&C3: PCI HOST Bridge PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&CB: PCI HOST Bridge PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&D3: PCI HOST Bridge PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&DB: PCI HOST Bridge PCI\VEN_1022&DEV_7458&SUBSYS_00000000&REV_12\3&33B859B7&0&80: PCI to PCI Bridge PCI\VEN_1022&DEV_7458&SUBSYS_00000000&REV_12\3&33B859B7&0&88: PCI to PCI Bridge PCI\VEN_1022&DEV_7459&SUBSYS_74591022&REV_12\3&33B859B7&0&81: System Interrupt Controller PCI\VEN_1022&DEV_7459&SUBSYS_74591022&REV_12\3&33B859B7&0&89: System Interrupt Controller PCI\VEN_103C&DEV_3230&SUBSYS_3234103C&REV_01\4&22FEBB0D&0&0060: RAID Controller PCI\VEN_103C&DEV_3300&SUBSYS_3305103C&REV_00\4&21887AE&0&2448: Universal Serial Bus (USB) Controller PCI\VEN_103C&DEV_3302&SUBSYS_3305103C&REV_00\4&21887AE&0&2648: PCI Device PCI\VEN_10DE&DEV_0051&SUBSYS_00000000&REV_B1\3&20FEA912&0&08: PCI to ISA Bridge PCI\VEN_10DE&DEV_0053&SUBSYS_31F8103C&REV_A3\3&20FEA912&0&30: IDE Controller PCI\VEN_10DE&DEV_005A&SUBSYS_31F8103C&REV_A2\3&20FEA912&0&10: Universal Serial Bus (USB) Controller PCI\VEN_10DE&DEV_005B&SUBSYS_31F8103C&REV_A4\3&20FEA912&0&11: Universal Serial Bus (USB) Controller PCI\VEN_10DE&DEV_005C&SUBSYS_00000000&REV_A2\3&20FEA912&0&48: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&60: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&68: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&70: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&58: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&60: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&68: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&70: PCI to PCI Bridge PCI\VEN_10DE&DEV_005E&SUBSYS_00000000&REV_A4\3&20FEA912&0&00: PCI Memory Controller PCI\VEN_10DE&DEV_005E&SUBSYS_00000000&REV_A4\3&33B859B7&0&00: PCI Memory Controller PCI\VEN_10DE&DEV_00D3&SUBSYS_CB8410DE&REV_B1\3&33B859B7&0&08: PCI Memory Controller PCI\VEN_14E4&DEV_164A&SUBSYS_1709103C&REV_02\4&9C889E9&0&0880: Broadcom BCM5706C NetXtreme II GigE PCI\VEN_14E4&DEV_164A&SUBSYS_1709103C&REV_02\4&9C889E9&0&1080: Broadcom BCM5706C NetXtreme II GigE #2 43 matching device(s) found. WinPE v2.0 devcon list PCI\VEN_0E11&DEV_B203&SUBSYS_3305103C&REV_03\4&21887AE&0&2048: Base System Device PCI\VEN_0E11&DEV_B204&SUBSYS_3305103C&REV_03\4&21887AE&0&2248: Base System Device PCI\VEN_1002&DEV_515E&SUBSYS_31FB103C&REV_02\4&21887AE&0&1848: Video Controller (VGA Compatible) PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&C0: PCI HOST Bridge PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&20FEA912&0&C8: PCI HOST Bridge PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&C1: PCI HOST Bridge PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&20FEA912&0&C9: PCI HOST Bridge PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&C2: PCI HOST Bridge PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&20FEA912&0&CA: PCI HOST Bridge PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&C3: PCI HOST Bridge PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&20FEA912&0&CB: PCI HOST Bridge PCI\VEN_103C&DEV_3230&SUBSYS_3234103C&REV_01\4&22FEBB0D&0&0060: RAID Controller PCI\VEN_103C&DEV_3300&SUBSYS_3305103C&REV_00\4&21887AE&0&2448: Universal Serial Bus (USB) Controller PCI\VEN_103C&DEV_3302&SUBSYS_3305103C&REV_00\4&21887AE&0&2648: IPMI Interface PCI\VEN_10DE&DEV_0051&SUBSYS_CB8410DE&REV_B1\3&20FEA912&0&08: PCI to ISA Bridge PCI\VEN_10DE&DEV_0053&SUBSYS_31F8103C&REV_A3\3&20FEA912&0&30: IDE Controller PCI\VEN_10DE&DEV_005A&SUBSYS_31F8103C&REV_A2\3&20FEA912&0&10: Universal Serial Bus (USB) Controller PCI\VEN_10DE&DEV_005B&SUBSYS_31F8103C&REV_A4\3&20FEA912&0&11: Universal Serial Bus (USB) Controller PCI\VEN_10DE&DEV_005C&SUBSYS_00000000&REV_A2\3&20FEA912&0&48: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&60: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&68: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&20FEA912&0&70: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&58: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&60: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&68: PCI to PCI Bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&33B859B7&0&70: PCI to PCI Bridge PCI\VEN_10DE&DEV_005E&SUBSYS_00000000&REV_A4\3&20FEA912&0&00: PCI Memory Controller PCI\VEN_10DE&DEV_005E&SUBSYS_00000000&REV_A4\3&33B859B7&0&00: PCI Memory Controller PCI\VEN_10DE&DEV_00D3&SUBSYS_CB8410DE&REV_B1\3&33B859B7&0&08: PCI Memory Controller 29 matching device(s) found. As you can see, there is a big difference in how many devices the two versions actually "see".

Anyone have a HP DL585-G2 working with WinPE v2.0? I can't seem to get the NIC's working.

In your syspreped image, have you included the vmware IDE or SCSI drivers in the mass storage section? if not, it will BSOD on you anytime you try and use that image on VMWare.

Why not just install windows to that directory name to begin with?

I'm not following what it is you are trying to do. Are you taking a Windows 2000 or XP install and trying to create a mini-windows install? Or are you trying to convert a WinPE install to run off a hard drive?

You may get better answers by asking in the Ryan forums. Personally, I use HFSLIP to do my hotfix slipstreaming, and don't have any issues with WinPE2 and winnt32 over the network. Sorry I couldn't help with the actual question though.

You need to follow this post: Thread Post with Answer You have to modify the registry when you build your WinPE2.0 image