You are not logged in. Please login or register.
There appears to be a problem with LAN 10.03. Just tried it with BartPE (XPE) and the network controller* was not detected on boot, only after using Kare's Drive Import PE. Reverted back to LAN 8.12.1 and all went fine (automatic detection on boot). Interestingly enough, the drivers are the same version in both packages.
*motherboard ASUS M2NPV-VM (North Bridge: nVIDIA GeForce 6150 (C51PV), South Bridge: nVIDIA nForce 430 (MCP51))
Post the HWIDs for the offending system please?
Also, post the relevant portion of %systemroot%\setupapi.log so we can find out which .inf is causing the problem.
From Kare's DriverImportPE:
nVidia nForce networking controller
07/11/2007
67.5.3
PCI\VEN_10DEDEV_0269
From HWIDS:
PCI\VEN_10DE&DEV_0269&SUBSYS_816A1043&REV_A3\3&2411E6FE&0&A0: NVIDIA Network Bus Enumerator
Last edited by ceroni (2010-03-03 13:24:01)
Well, that HWID has a duplicate in DriverPack LAN. Both \NV\ (07/11/2007, 67.5.3) and \NV8\ (10/12/2007, 67.6.7) have that HWID.
In fact, looking at the nvidia website, your board should be using the following versions:
# Ethernet Driver (v67.89) WHQL
# Network Management Tools (v67.96) "Sedona"
Maybe that's the problem? Maybe I need to add some BartPE exceptions to the pack .ini.
Can you delete the \NV\ folder from the pack, rebuild your BartPE plugin and try again?
Good teamwork guys!
Can you delete the \NV\ folder from the pack, rebuild your BartPE plugin and try again?
Most certainly. I'll do it tomorrow and report back. Thanks.
Nope. Didn't work 
There was no automatic detection on boot.
Kare's DriverImport PE didn't work either. It reported finding an appropriate driver, but after importing it I could not start network support.
I have a test pack for you to try please...
http://driverpacks.sytes.net/driverpack … _1003r1.7z
Changelog
restore HWID to N7
add BartPE exception to skip N8 in pack INI
No automatic detection on boot. Sorry.
Kare's DriverImport PE detected and installed the proper driver.
strange... that should have been the identical load out as the 8.12.1 setup...
Can you try deleteing the N8 folder altogether and tell me if that works?
Perhaps my INI exception failed and N8 is still in conflict
Can you try deleteing the N8 folder altogether and tell me if that works?
N8 deleted: No automatic detection on boot again. Kare's DriverImportPE detected and installed the (proper?) driver but I was unable to start network support.
Unrelated: integrated Sound_A+B into my DVD. Didn't work. It seems my audio driver* is missing. Could get sound to work though using DriverImportPE to get the drivers from my HD installed Windows XP.
Many thanks again for all the efforts.
*
HDAUDIO\FUNC_01&VEN_11D4&DEV_1986&SUBSYS_104381B3&REV_1005\4&3333247E&0&0001
Name: SoundMAX Integrated Digital HD Audio
Hardware ID's:
HDAUDIO\FUNC_01&VEN_11D4&DEV_1986&SUBSYS_104381B3&REV_1005
HDAUDIO\FUNC_01&VEN_11D4&DEV_1986&SUBSYS_104381B3
Compatible ID's:
HDAUDIO\FUNC_01&VEN_11D4&DEV_1986&REV_1005
HDAUDIO\FUNC_01&VEN_11D4&DEV_1986
HDAUDIO\FUNC_01&VEN_11D4
HDAUDIO\FUNC_01Yeah sound is not yet ready to go...
The UBCD4win team needs to work on the HWPnP plugin before sound will work reliably 
that is why the sound packs are somewhat disabled .
the NIC really has me stumped...
In theory if you removed N8 then what i gave you should be close to, or identical to, LAN 8.12.1...
Hmmm... back to the drawing board. 
I am working on BASE ATM if one of the PacksTeam doesn't get to it i will take another look at it after i get the DriverPacks BASE bugs fixed 
!
PS drop by the driverImportPE thread here and give some props. that way others may know it works, and the author can get some props! http://forum.driverpacks.net/viewtopic.php?id=3217
SamLab had made some edits to the NV*\ .inf files to fix some HWID overlap bugs. I haven't compared DriverPack LAN 8121 with 1003 yet in that regard but I'll bet there are changes.
I have the nvidia 15.26 nforce drivers for your board with me. I'll try to have another look. Maybe SamLab's changes broke something?
NVIDIA Network drivers use child drivers.
Example: nvnetbus.sys load nvnrm.sys
The name nvnrm.sys is encoded in nvnetbus.sys.
NVIDIA Network Resource Manager nvnrm.sys
NV\nvnrm.sys 1.00.02.06753 857kb
NV1\nvnrm.sys 1.00.00.0442 56kb
NV2\nvnrm.sys 1.00.02.06565 901kb
NV3\nvnrm.sys 1.00.00.0482 256kb
NV4\nvnrm.sys 1.00.02.0652 1134kb
NV5\nvnrm.sys 1.00.02.06024 1079kb
NV6\nvnrm.sys 1.00.02.06764 868kb
NV7\nvnrm.sys 1.00.02.06789 934kb
NV8\nvnrm.sys 1.00.02.06767 920kb
NV9\nvnrm.sys 7.01.01.07108 280kb
Strange, file size goes from 56kb to 1134kb.
Does one nvnrm.sys support some NVIDIA hardware only?
A BartPE CD is read only by default.
There can be one file version only at CD.
LAN 10.03 plugin adds file nvnrm.sys 7.01.01.07108.
I understand, the plugin adds one file nvnrm.sys only. One out of ten at above example.
Does this create a version conflict?
There are much less conflicts at NVIDIA RIS drivers.
http://www.drowaelder.de/
http://www.drowaelder.de/winpe/ubcd4win … RIS-V2.Cab
NVIDIA didn't release new RIS driver the last years.
The UBCD4win team needs to work on the HWPnP plugin before sound will work reliably
Sound with and without HD Audio can be added. This is a manual task so far.
Add a sound plugin and a sound driver plugin relating to your hardware.
that is why the sound packs are somewhat disabled .
A plugin integration cause a lot of version conflicts: same file name.
I've no idea to resolve the conflicts.
Import drivers to a running PE is a approach.
This require a writable SystemRoot.
A filter driver can do this at CD. E.g. fbwf from XP Embedded, that's a non distributable file.
Unfortunately DriverImportPE is a commercial application in the meantime.
@ceroni
Try add NV8 only, delete all other NV NIC drivers.
Think I've found something:
Can you try deleteing the N8 folder altogether and tell me if that works?
N8: NETGEAR FA311/312 PCI Card.
NV8: the one we want!!!
My previous attempts were done after deleting N8 and not NV8.
Despite the acts of sabotage (:lol::lol::lol:) I'll delete NV8 and try again.
If that fails, I'll also try cdob's suggestion of keeping only NV8.
Last edited by ceroni (2010-03-07 01:13:22)
NV8 deleted: No automatic detection on boot again. Kare's DriverImportPE detected and installed a driver from DP_LAN_wnt5_x86-32_1003r1.7z but I was unable to start network support.
Before trying cdob's suggestion I would like to ask a few things:
- there is a flag (?) in DriverPack_LAN_wnt5_x86-32.ini (ms_1_exc_skipIfOS="wxp,w2k3") that prevents NV8 being slipstreamed into BartPE's plugin, isn't it?
- if I leave just the NV8 folder it would not get slipstreamed, right?
- do I also need to remove ms_1_exc_skipIfOS="wxp,w2k3" before attempting to slipstream the NV8 folder alone?
Overflow is concentrating on finishing the code for DriverPacks BASE. I will look into this problem further but now that cdob is here hopefully we'll find a solution soon.
I have very little experience using BartPE. I built my first UBCD4win disc last week!
NV8 deleted:
Before trying cdob's suggestion I would like to ask a few things:
- there is a flag (?) in DriverPack_LAN_wnt5_x86-32.ini (ms_1_exc_skipIfOS="wxp,w2k3") that prevents NV8 being slipstreamed into BartPE's plugin, isn't it?
- if I leave just the NV8 folder it would not get slipstreamed, right?
- do I also need to remove ms_1_exc_skipIfOS="wxp,w2k3" before attempting to slipstream the NV8 folder alone?
YES!
Right!
YES! That Whole [NV8] section removed ...
I think the best thing to do is to add the RIS driver cdob pointed to by adding it to the <UBCD4Win>\drivers\ folder and not use DriverPack LAN at all (disable or delete the DriverPack LAN plugin... does that work?
I already said that RIS drivers were a better way to go ...
if that works we delete all the NV folders from BartPE by using the mass INI file adding the skipIfOS="wxp,w2k3" exception. (or we could call it a flag... which should have the same effect as removing all the NV folders from the pack ) and add the RIS driver to the pack (NV9 ?)
Sorry about my sabatoge / N8-NV8 typo!
add the RIS driver cdob pointed to by adding it to the <UBCD4Win>\drivers\ folder and not use DriverPack LAN at all (disable or delete the DriverPack LAN plugin... does that work?
The RIS drivers are a plugin too. They go to <UBCD4Win>\plugin\.
E.g. <UBCD4Win>\plugin\DriverPacks.net\LAN\Nvidia_RIS\
Nvidia did release strange RIS drivers.
The newer release should support old hardware. However driver did load but ping failed.
The plugin includes old and new drivers, plugin adjust *.inf.
Last RIS driver is some years old.
A idea, not tested, no hardware: include RIS driver plugin and the newest non RIS driver (NV9 currently).
I'm rebuilding all the NV* folders in DriverPack LAN from scratch. There were so many altered .inf files it was difficult to find the original ones.
This will take me most of today to do (my only day off!).
I'm also updating some of the folders with newer drivers, and pruning duplicate folders/drivers.
Jaak had done an amazing amount of homework regarding the nvidia LAN drivers here: http://forum.driverpacks.net/viewtopic.php?id=2752
It's worth a read (I've read it 3 times just this morning!)
I've got a pot full of coffee and no distractions for the next two hours...
Hopefully I'll have a working DriverPack LAN nightly for you guys to test by the end of the day.
Please test the below nightly test dp.
DP_LAN_wnt5_x86-32_100311
http://driverpacks.sytes.net/driverpack … _100311.7z
MD5: 37703ac4f5349328f9b1e60539decf2c
Size: 8 MB
v100311
Deleted older conflicting drivers, updated many drivers, added older signed compatible driver (NV2).
New layout for Nvidia LAN drivers.
-NV\ NVIDIA nForce Networking Controller RIS Drivers, DriverVer = 07/11/2007, 67.5.3 & 02/03/2005, 4.7.1
-NV1\ NVIDIA nForce Networking Drivers, DriverVer = 04/06/2005, 4.8.2
-NV2\ NVIDIA nForce Networking Drivers, DriverVer = 05/15/2006, 60.1.5
-NV3\ NVIDIA nForce Networking Drivers, DriverVer = 03/06/2007, 65.6.5
-NV4\ NVIDIA nForce Networking Drivers, DriverVer = 09/20/2007, 67.6.4
-NV5\ NVIDIA nForce Networking Drivers, DriverVer = 08/01/2008, 67.8.9
-NV6\ NVIDIA nForce Networking Drivers, DriverVer = 07/01/2009, 71.0.8
-NV7\ NVIDIA nForce Networking Drivers, DriverVer = 07/01/2009, 73.1.0
Restored signed driver .inf where possible. \NV4 is still not signed (unknown source).
Added BartPE code to .ini. All NV* folders are skipped for wxp, w2k3 sources. NV\ RIS drivers are preferred at the moment for BartPE (requires testing).Added BartPE code to .ini. All NV* folders are skipped for wxp, w2k3 sources. NV\ RIS drivers are preferred at the moment for BartPE (requires testing).
Based on previous user reports:
can you edit nvnb5032.inf and disable Nforce 1 and Nforce 2 hardware?
Driver does load, but ping fails.
[Nvidia]
; DisplayName Section DeviceID
;%NVENETFD.DeviceDesc% = NVENETFD1.NDI, PCI\VEN_10DE&DEV_01C3
;%NVENETFD.DeviceDesc% = NVENETFD1.NDI, PCI\VEN_10DE&DEV_0066
;%NVENETFD.DeviceDesc% = NVENETFD3.NDI, PCI\VEN_10DE&DEV_0086
;%NVENETFD.DeviceDesc% = NVENETFD3.NDI, PCI\VEN_10DE&DEV_008CThis HardwareIDs are handled by nvrisxp.inf.
In addition e.g. nv5\nvetbus.inf contains PCI\VEN_10DE&DEV_0AB0.
The RIS driver dosn't support this HardwareID.
However both RIS nvnb5032.inf and nv5\nvetbus.inf use a child driver nvnrm.sys.
Of course the same file name, but different versions.
No idea to resolve the conflict so far. Further user testings are required.
Made your recommended changes to DriverPack LAN 100312. Original .inf backed up to NV\Originals.7z
Uploading now.
Please test the below nightly test dp.
DP_LAN_wnt5_x86-32_100312
http://driverpacks.sytes.net/driverpack … _100312.7z
MD5: d0d90720e429c61c22a10a6a16861a47
Size: 8 MB
v100312
Changed
-NV\ nvnb5032.inf
Commented out 4 HWIDs and added 1.
[Nvidia]
; DisplayName Section DeviceID
;%NVENETFD.DeviceDesc% = NVENETFD1.NDI, PCI\VEN_10DE&DEV_01C3
;%NVENETFD.DeviceDesc% = NVENETFD1.NDI, PCI\VEN_10DE&DEV_0066
;%NVENETFD.DeviceDesc% = NVENETFD3.NDI, PCI\VEN_10DE&DEV_0086
;%NVENETFD.DeviceDesc% = NVENETFD3.NDI, PCI\VEN_10DE&DEV_008C
;Added by DriverPacks
%NVENETFD.DeviceDesc% = NVENETFD3.NDI, PCI\VEN_10DE&DEV_0AB0
v100311
Deleted older conflicting drivers, updated many drivers, added older signed compatible driver (NV2).
New layout for Nvidia LAN drivers.
-NV\ NVIDIA nForce Networking Controller RIS Drivers, DriverVer = 07/11/2007, 67.5.3 & 02/03/2005, 4.7.1
-NV1\ NVIDIA nForce Networking Drivers, DriverVer = 04/06/2005, 4.8.2
-NV2\ NVIDIA nForce Networking Drivers, DriverVer = 05/15/2006, 60.1.5
-NV3\ NVIDIA nForce Networking Drivers, DriverVer = 03/06/2007, 65.6.5
-NV4\ NVIDIA nForce Networking Drivers, DriverVer = 09/20/2007, 67.6.4
-NV5\ NVIDIA nForce Networking Drivers, DriverVer = 08/01/2008, 67.8.9
-NV6\ NVIDIA nForce Networking Drivers, DriverVer = 07/01/2009, 71.0.8
-NV7\ NVIDIA nForce Networking Drivers, DriverVer = 07/01/2009, 73.1.0
Restored signed driver .inf where possible. \NV4 is still not signed (unknown source).
Added BartPE code to .ini. All NV* folders are skipped for wxp, w2k3 sources. NV\ RIS drivers are preferred at the moment for BartPE (requires testing).Thanks. I'll try it as soon as I can.
In the meantime, I've integrated WLAN 10.03 into my BartPE DVD and tested on 3 different laptops and a desktop (I'll post the details later). Works perfect
Yesssssssssssssssssssssssssssssssssssssss
DP_LAN_wnt5_x86-32_100312.7z worked just fine.
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.022 seconds, 10 queries executed ]