26

Re: [SLVD] Bug HP NC373i & NC373T drivers

Hi, is there any update on this issue? Let me know if I can help.
Thank you.

Edoardo

Edoardo

Re: [SLVD] Bug HP NC373i & NC373T drivers

Try this please...

LAN 10.02 RC3

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

28

Re: [SLVD] Bug HP NC373i & NC373T drivers

Hi Jeff,
unfortunately I have always the "Unable to install network adapters" error. I used W2k3 Ent Sp2 (no R2) as source.

Edoardo

Last edited by ef (2010-02-09 20:32:08)

Edoardo

Re: [SLVD] Bug HP NC373i & NC373T drivers

I've compared the drivers from the link you provided with the ones in D\L\B3 and they're bit-for-bit identical EXCEPT that the .inf and .cat files are different.  Because I can't rename the .cat files to a unique name without breaking the digital signing, I'm adding the HP drivers to a separate folder: D\L\HP1.  This should solve your problem.
This will be incorporated in DriverPack LAN 1002r4. 
@ef, if you can test for us successfully, this will make it into the final build. smile

30

Re: [SLVD] Bug HP NC373i & NC373T drivers

Thank you very much: waiting for 1002r4 to be downloadable to test it!

Edoardo

Edoardo

Re: [SLVD] Bug HP NC373i & NC373T drivers

Try this please:
DP_LAN_wnt5_x86-32_1002r4
Download: http://driverpacks.sytes.net/driverpack … _1002r4.7z
MD5: b54be6099efb532eac7b088c2f702e4b
Size: 8 MB

32

Re: [SLVD] Bug HP NC373i & NC373T drivers

It didn't fix the issue. Moreover I had the following popup from PE network configurator:
"Cannot make a visible window modal".
In the UBCD4WIN event viewer, apart from the previously mentioned 2 errors (source nvgts5 and nvgts6, both event IDs 4, no description), I had a new error, source Application popup, event id 877, description:
"Error [DATABASE NOT LOADED] during processing of drivers database".

Last edited by ef (2010-02-09 23:48:06)

Edoardo

33

Re: [SLVD] Bug HP NC373i & NC373T drivers

I don't know if this can help, but the bxvbd.inf added in the plugin\DriverPacks.net\LAN\wnt5 folder is still the D\L\B3 one, not the D\L\HP1 one.
And, apart from having previously tested the HP driver in place of the Broadcom one without success, does it depend from the 2 set of files having the same names, although contained in different folders?
Sorry for my newbie questions...

Edoardo

Re: [SLVD] Bug HP NC373i & NC373T drivers

Re duplicate names in separate folders...

I wrote this code last year for bartpe...

Jeff wrote:

By useing the existing mass storage tags i was able to reduce the code required to implement bartpe for the remaining packs. however we will now need to be aware of the new ini entries when we update packs.

basicaly i am useing the section/folder name, the tag name, the sysfile name, and the skipIfOS

[A1]
ms_count                 = 1
ms_1_tag                 = "1asacpi"
ms_1_sysfile             = "asacpi.sys"
ms_1_exc_skipIfOS     = "wxp,w2k3"

the above code marks the entire A1 folder to be skipped for windows XP and windows 2k3 
(which means excluded for bartpe since it only supports xp and 2k3)

same as with mass storage - a tag name may not be repeated in an individual INI
the sysfile name can be anything but it makes sense to use a filename in the folder.
the above example is the minimum and only entries supported right now.

to recap all the above entrys must exist
and the "skip" applies to all files in the folder.

when two drivers have the same name the last one processed by BASE wins...
by assinging a unique name for the "tag" value this issue is resolved wink
REMEMBER the tag name must be unique not only to ALL of the packs used for BartPE but also to existing windows files too wink.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [SLVD] Bug HP NC373i & NC373T drivers

As known HP NC373i & NC373T uses Broadcom hardware.

Broadcom offers two different drivers: regular windows and RIS/WinPE drivers.
http://www.broadcom.com/support/etherne … remeii.php

HP relaese RIS/WinPE drivers too:
http://h20000.www2.hp.com/bizsupport/Te … taskId=135

The RIS/WinPE drivers are  for: "BartPE - UBCD4Win - WinPE"
The RIS/WinPE drivers should work at regular windows too, but this is not supported.

Re: [SLVD] Bug HP NC373i & NC373T drivers

If that is the case then those drivers should be added to the pack.
The existing windows drivers in the pack should be marked in the pack INI (with all the above tags) as skip wxp,w2k3 when the RIS drivers are added.

It is important to note that a normal slipstream is NOT affected by these tags! they are only used / relevant for BartPE.

It is also important to note that the RIS drivers are not signed so they should not conflict with their windows counterparts for a normal sliptream for disc installs...

As always thanks for your valuable input cdob!!!! right on target as usual!!!

I belive if this is implemented then we have fixed your issue ef...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [SLVD] Bug HP NC373i & NC373T drivers

OK, so looking at the pack .ini, there are no BartPE skip-sections at all.  Do I need to add them?  For all the drivers or just a select few?
The \HP1\ folder will remain, but I added the WinPE HP drivers to to HP1 as well.

Re: [SLVD] Bug HP NC373i & NC373T drivers

if a driver has the same name as another then tag it (similar to mass wink)... yes a select few

well if you put them both in hp1 then the skip command will skip the entire folder... not the result we need wink
the ris drivers will need their own folder wink

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [SLVD] Bug HP NC373i & NC373T drivers

If I go through and add the tags for all folders, then this will take a while! sad
There's 135 folders.

PS both of the RIS drivers could go in one folder wink

Re: [SLVD] Bug HP NC373i & NC373T drivers

you don't need to do them all!
How many LAN issues have been reported with BartPE? I would deal with them as / when they are reported wink.
there is probably only a handful that need tagged (just a select few)

PS both of the RIS drivers could go in a folder named PE smile perhaps with the johua drivers (where did those land???)


to be clear I would only do this one driver / folder for now...

PS We used to have the Joshua plugin included in the LAN pack which replaces all the nvidia drivers for PE...
I think it got deleted and the related INI entries sad

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [SLVD] Bug HP NC373i & NC373T drivers

OverFlow wrote:

to be clear I would only do this one driver / folder for now...

PS We used to have the Joshua plugin included in the LAN pack which replaces all the nvidia drivers for PE...
I think it got deleted and the related INI entries sad

Well, I didn't delete any drivers or entries.  I only updated existing drivers.

OK, I moved the RIS drivers to the \RIS\ folder (how original eh?) smile
I'm also adding the BartPE exception code to \HP1\ and a few others.  The \RIS\ section won't have a BartPE exception because as I read it, that section must be used...right?

What's a Joshua driver?
I've got all the intermediate builds of DriverPack LAN all the way back to 8121.  Just tell me what folder it's in and I'll find it.

I'm finalizing this pack now.  I hope to have it finished by Monday.
Speak now or forever hold your peace! wink

Re: [SLVD] Bug HP NC373i & NC373T drivers

http://www.drowaelder.de/winpe/PEIndex.htm
NForceAll-RIS-V2

Basically Joshua built the best driverset for nvidia NICs using Nvidia supplied RIS drivers.
UBCD4Win included them in previous versions, before DriverPacks.
IDK of we included V1 or V2 of his drivers in the past.
IDK if we still include them, If not we should, for the same reasons as above. wink

Yes you are correct no entries means it is included.
We only need to create entries to eliminate conflicts.
Create an entry to exclude a known "problem" driver.
IE DON'T create an entry for the RIS folder... but DO create an entry for the driver it replaces big_smile!

Does that help?

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

43

Re: [SLVD] Bug HP NC373i & NC373T drivers

Hi,
any news for my issue? I didn't test latest DP_LAN.
Thank you for your support.

Edoardo

Re: [SLVD] Bug HP NC373i & NC373T drivers

http://forum.driverpacks.net/viewtopic. … 054#p37054

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

45

Re: [SLVD] Bug HP NC373i & NC373T drivers

I just tested DP_LAN 10.03.12, but I have the same issue...

Edoardo

Re: [SLVD] Bug HP NC373i & NC373T drivers

@Erik see post 35 by cdob wink

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [SLVD] Bug HP NC373i & NC373T drivers

Related: http://forum.driverpacks.net/viewtopic.php?id=4427

dpdt38  wrote:

Hello.

I'm new on this forum and i need some help.

I'm trying to work with BartPE and DriverPacks.

I have no problems with DriverPacks integration.

I have an network card HP NC7760 Gigabit Server Adapter Device ID:PCI\VEN_14E4&DEV_16A6&SUBSYS_00BB0E11&REV_02\3&267A616A&0&20, on Windows 2003 server, with "q57xp32.sys".

With BartPe, this card is shown (in "Device manager clone") as "BCM 5703 Gigabit Ethernet" and need "b57xp32.sys" when i try to update driver manually.

My problem seems to be like as http://forum.driverpacks.net/viewtopic.php?id=1452

I have tried, without success RIS driver.

Can someone help me ?

Thanks for your help.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: [SLVD] Bug HP NC373i & NC373T drivers

OverFlow wrote:

@Erik see post 35 by cdob wink

I've already got those.
Arrgh!  I feel like I'm playing "Whack-A-Mole"! wink

I'm continuing my research into this problem but another user reported (here) that editing the .inf and "changing class=net to class=Net allowed the project to finally add the driver."  Seems the \HP1\ drivers are using "class=net".  Could that be the problem?
I'll be going through DriverPack LAN again looking for duplicate HWIDs between the broadcom/HP drivers (again).  Maybe I missed something.
There are a few duplicates in \B3, \HP1, and \RIS. 
Still looking...

Re: [SLVD] Bug HP NC373i & NC373T drivers

Just to compare:

$ md5sum broadcom/b06nd.inf
dbb0c6a58942e002d3baad2f7775f0c7 *broadcom/b06nd.inf

$ md5sum sp43878/b06nd.inf
dbb0c6a58942e002d3baad2f7775f0c7 *sp43878/b06nd.inf

$ md5sum broadcom/b06nd51x.sys
06811297d1ca596c664c3ec898fea512 *broadcom/b06nd51x.sys

$ md5sum sp43878/b06nd51x.sys
06811297d1ca596c664c3ec898fea512 *sp43878/b06nd51x.sys

Broadcom b06nd51x.sys 5.0.0.0 and HP OEM driver are equal.
HP distribute a original Broadcom RIS driver.


'mr_smartepants' wrote:

changing class=net

This refers to PEBuilder using drivers directory only.
PEBuilder parse *.inf : class=net is searched case sensitive.

However this is not used at a plugin.
Ignore this part as for DriverPacks BartPE plugin.
class=net is fine.

Re: [SLVD] Bug HP NC373i & NC373T drivers

Yes, the .inf and .sys are bit-for-bit identical.
Odd that the broadcom .inf files (in \B3, \HP1, and \RIS) are the only ones that have class=net, the other 100+ infs all use the standard class=Net. 
And they are the folders that are causing our problems here.
Sounds like a bug in PEbuilder.
I'm still looking, but I don't know if I'll find anything.