[p4ntb0y]

Hi,

I have a DL360 G5 HP server this uses the NC375I Multi nic function card.

I have added the driver to my winpe 2 image by using the PEIMG /INF=LOCATION etc

When I boot into winpe and type ipconfig /all i do not get any address info.

I have a DHCP scope running giving out ips etc.

I have tried...

netcfg -winpe

I have also tried to set a static ip address.

Is there there something I am missing?

has anyone used winpe 2 on HP kit yet?

[Sonic]

Have you tried ipconfig /release & ipconfig /renew ?

[p4ntb0y]

Yep tried that but no go..

i have tested this on my desktops which work fine (HP range)

Any Ideas?

[Jazkal]

can you give us a devcon output?

devcon find pci*

mainly intrested in the NIC device id's

On this page: HP DL360 Driver Page : Which nic are you talking about?

EDIT: I ask about the drivers, because I don't see that the NC375I is supported on any of those.

This post has been edited by Jazkal: 22 January 2007 - 12:33 PM

[p4ntb0y]

Hi the Driver is the HP NC-Series Multifunction Driver for Windows Server 2003.

I have extracted the drivers and there is an i386 folder with 2 sys files and 3 dll files.

The normal sys, inf and cat files

I will check with devcon when I am in work next and see what driver is actually loaded on my Windows 2003 Server.

I suspect that I require some these dll's to go somewhere on the winpe disc.

can you manually add drivers to winpe 2? instead of using peimg /inf?

Can I copy all of the inf files to \winpe\inf and all the sys files to \winpe\drivers and the cats to \winpe\catroot and then drop the dll's into system32, I will do some tests as always......

thanks guys

[Jazkal]

From that drivers list of supported nic cards:

Quote

* NC370F

* NC370i

* NC370T

* NC371i

* NC373F

* NC373i

* NC373m

* NC373T

* NC374m

* NC380T

your card isn't listed. Check the devcon device id's in the driver INF, and see if they are there.

[p4ntb0y]

The Network card is a NC373i

[p4ntb0y]

Ok I have tested the network using winpe 2005 with the hp drivers and this works ok.

I made another winpe 2 disc with the drivers for winpe 2005 and again no go.

I noticed that there are a some dll winsock2 files within an i386 dir I suspect that these need to be placed somewhere within the winpe 2 disc (I am thinking system32)

Somehow the network loading part has changed somehow within winpe 2 as they are the same drivers but handled another way, I dont really understand it at the moment.

I burn another disc off and try and place the dll,s files within system32.

I wonder if HP are doing aa support pack for winpe 2 like they did for winpe 2005?

[p4ntb0y]

Ahhhh

this is driving me crazy! I just tried the same disk on a D510 compaq evo and I get the same thing!

[p4ntb0y]

I did read somewhere that it could be the ndis drivers not knowing alot about this I can not be sure..

Has anyone got any broadcom 2 ndis drivers working in winpe 2 or vista?

[Jazkal]

I checked the device id's in the Hp driver pack, and these drivers I'm including should work. They were meant for RIS, but they work in WinPE also.

let me know how they work out.

Attached File(s)

•  ris.zip (80.4K)
  Number of downloads: 33

[p4ntb0y]

Yeah did some more tests the bus emulator is not supported so I downloaded the The NetXterme II monolithic drivers which are just for the network drivers and not the bells and whistles.

link here Drivers

this works great!

Many thanks Jazkal you were on the right track!

[leen2]

I have found a similar issue with the HP Multifunction NIC included in a number of HPs servers, specifically the DL585 server. Unfortunately the WinPE drivers included in the latest Smart Start Scritping toolkit do not work either. I had assumed that this was some sort of conflict between drivers included with WinPE 2 from WAIK and the HP provided drivers but I will try the drivers you have found to see if they work.

For this particular server, a DL585 G1 server I was trying to build with a x64 OS version, I had to use WinPE 1.5 with the drivers extracted from Proliant Support Pack 7.60. Newer drivers from different Proliant Support Packs did not work. It seems that HP no longer actually test their drivers that they put out in the Smart Start Scritping toolkit.

[FredBeagle]

I used the drivers from HP SmartStart Scripting Toolkit 1.8 and so far no issues.

http://h18013.www1.hp.com/products/servers...loadtkpage.html