[Deacon]

This isn't easy, but I've been trying to get it to work for 5 months, so I'll take it.

I'm using Bartpe 3.13 and UBCD 2.4. I'm not using the new nic or mass storage plugins via the driver directory, still using the old ones (which work fine for me) as plugins.

Here's the steps. (I'm not sure all of these are necessary, but this is what worked, will be trying to pare it down over time.) Also, putting this up here now, so that others who need it can use it and also help refine it.

You need a batch file that's on your boot CD and on your menu if you want easy access.

It just needs this in it.

regsvr32 %windir%\system32\netcfgx.dll

call it regnet.cmd

You need the hwpnp plugin and the infcachebuild utility installed.

add these four lines to the XML file in the hwpnpn plugin directory (adds two items to your menu (the ID strings should add the net bus enumerator and the ethernet contoller for most nforce3 compatible motherboards.)

<MITEM TYPE="ITEM" DISABLED="@Not(@FileExists(@GetProgramDrive()\Programs\HWPnP\HWPnP.exe))"
CMD="RUN" FUNC="@GetProgramDrive()\Programs\HWPnP\HWPnP.exe -all /d /p /u /log /s =PCI\VEN_10DE&DEV_00DF&SUBSYS_100C1695&REV_A2\3&13C0B0C5&0&28">Install NForce3 part1(HWPnP)</MITEM>
<MITEM TYPE="ITEM" DISABLED="@Not(@FileExists(@GetProgramDrive()\Programs\HWPnP\HWPnP.exe))"
CMD="RUN" FUNC="@GetProgramDrive()\Programs\HWPnP\HWPnP.exe -all /d /p /u /log /s ={1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV00DF\4&2DB8AF09&1&01">Install NForce3 part2(HWPnP)</MITEM>

Make sure you've added the nforce3 plugin from the new .2 beta driver set to the drivers/net directory.

Create a subdirectory somewhere that you can copy some files from and load the nforce3 net drivers to that directory (could pull from the plugin dir.) My files are in this location

E:\1-pebuilder-313-24\nforce3-Ethernet\

which is referenced in the script below, so edit below script to reflect your location.

Build your Bart disk the following way.

Create a batch file called pebuilder.cmd

Put these lines in it (sbustituting in your own directory paths.)

cls
@echo off
pebuilder.exe -exit -overwrite

if exist E:\1-pebuilder-313-24\BartPE\i386\inf\*.pnf ( echo y.|del E:\1-pebuilder-313-24\BartPE\i386\inf\*.pnf )
if exist E:\1-pebuilder-313-24\BartPE\i386\inf\InfCache.1 del E:\1-pebuilder-313-24\BartPE\i386\inf\InfCache.1
copy E:\1-pebuilder-313-24\nforce3-Ethernet\*.inf E:\1-pebuilder-313-24\BartPE\i386\inf
copy E:\1-pebuilder-313-24\nforce3-Ethernet\*.dll E:\1-pebuilder-313-24\BartPE\i386\system32
copy E:\1-pebuilder-313-24\nforce3-Ethernet\*.exe E:\1-pebuilder-313-24\BartPE\i386\system32
copy E:\1-pebuilder-313-24\nforce3-Ethernet\*.sys E:\1-pebuilder-313-24\BartPE\i386\system32\drivers
start /wait E:\1-pebuilder-313-24\BuildScripts\InfCacheBuild.exe E:\1-pebuilder-313-24\BartPE

mkisofs.exe -v -force-uppercase -duplicates-once -iso-level 4 -volid "BartPE" -A PEBUILDER/MKISOFS -sysid "Win32" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o E:\1-iso-s\bpe313ubcd24markwnf.iso E:\1-pebuilder-313-24\BartPE


:end

When you execute that file, it brings up the pebuilder, hit build and when done hit exit and script will continue.

Burn your ISO (the ISO created by this mkisofs line seems a slow booter to me, but haven't had time to work on that yet, pulled it from another forums tips.)

Boot with new CD.

When booting is done do not load network support.

Run regnet.cmd
Run Install NForce3 part1 from System tools menu
Run Install NForce3 part2 from System tools menu
run Load Network and Fileshare support from system, network menu.

Tada you should now be able to access the network over your onboard nic.

Odds and ends.

Penetconfig does not work and neither does Load Network support (GUI) don't know why, just getting started with this.

BGinfo does show the Nvidia Network bus enumerator and the Nforce Network Controller after you run the two HWPNP scripts.

Thanks to many different people whose tips and utils and help have gone into getting this working.

Good luck.

I also did amend my above process to incorporate the following enhancements and it works well.

Call it 'Nforce.cmd' (or whatever you want) That you can reference from the HWPnP menu like this:

CODE

<MITEM TYPE="ITEM" DISABLED="@Not(@FileExists(@GetProgramDrive()\Programs\HWPnP\Nforce.cmd))"
CMD="RUN" FUNC="@GetProgramDrive()\Programs\HWPnP\Nforce.cmd">Install NForce3 (HWPnP)</MITEM>


That can make several of these steps 1 step i.e.:

CODE

:: NForces.cmd
@echo off

echo Registering netcfgx.dll...

regsvr32 %windir%\system32\netcfgx.dll

echo Executing HWPnP Step 1

HWPnP.exe -all /d /p /u /log /s =PCI\VEN_10DE&DEV_00DF

echo Executing HWPnP Step 2

HWPnP.exe -all /d /p /u /log /s ={1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV00DF\

pause


Beyond that I have a question; Why is the /d and the /u required in HWPnP?
Also, do you mind reporting your finding back to the original threads concerning this issue? There are still at least 1 open thread on this issue.

Finally I would like to note that if you computer does not have a Hardware ID:
PCI\VEN_10DE&DEV_00DF you might want to try looking for PCI\VEN_10DE&DEV_008C.

I'll follow this post with contents of my various files in the next post.

Thanks

[Deacon]

Okay, here's the contents of my various files.

In plugins directory in net directory in nforce3 directory I have this inf file

; nic_nforce3.inf
; PE Builder v3 plug-in INF file for nVidia nForce3 Ethernet

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="fsl nVidia nForce3 Ethernet"
Enable=0

[SourceDisksFiles]
;to system32\drivers
netbus\nvnetbus.sys=4,,1
netbus\nvnrm.sys=4,,1
netbus\nvsnpu.sys=4,,1
files\nvefdxp.sys=4,,1
files\NVENETFD.sys=4,,1

;to system32
netbus\nvnetbus.sys=2,,1
netbus\nvnrm.sys=2,,1
netbus\nvsnpu.sys=2,,1
files\nvefdxp.sys=2,,1
netbus\bdco1.dll=2,,1
netbus\nvconrm.dll=2,,1
files\fdco1.dll=2,,1
files\NVENETFD.sys=2,,1

;to windows\inf
netbus\nvnetbus.inf=20,,1
files\nvenetfd.inf=20,,1

;to inf\internet
;netbus\nvnetbus.inf=a,,1
;files\nvenetfd.inf=a,,1

[Software.AddReg]

0x1, "Microsoft\Windows NT\CurrentVersion\NetworkCards\10","Description","Nvidia Ethernet Network Controller"
0x1, "Microsoft\Windows NT\CurrentVersion\NetworkCards\10","ServiceName","{c4f6eed3-1c5e-4f43-a768-83ecba42fcc1}"

This directory also has the files and the netbus directories with the files in the locations indicated by the inf entries.

The files directory also has nforce3.cmd in it

Which has this contents

@echo off
echo ===============================
echo Installing nforce3 (HWPnP)
echo ===============================

regsvr32 /s %windir%\system32\netcfgx.dll
"x:\Programs\hwpnp\hwpnp.exe" -all +PCI\VEN_10DE /log /s
"x:\Programs\hwpnp\hwpnp.exe" -all +{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV00DF\ /log /s
rem first nforce4 attempt
"x:\Programs\hwpnp\hwpnp.exe" -all +{1A3E09BE-1E45-494B-9174-D7385B45BBF5}\NVNET_DEV0057\ /log /s
goto exit

:exit
pause


And in the netbus dir the file nvnetbus.inf has the following edit in it

;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
; Commented out by fsl... either not need or causing problems
;HKR, Uninstall, Script,0,"nvnrm.nvu"
;HKR, Uninstall, Name,0,"NVIDIA Ethernet Driver Components"
;HKR, Uninstall, INFSrcDir, 0, %1%
;HKR, Uninstall, Uninstaller,0,"nvunrm.exe"

;[BDCoInfo]
;OriginalInfSourcePath = %1%
;~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


My hwpnp.xml file has the entry added to it

CMD="RUN" FUNC="@GetProgramDrive()\Programs\HWPnP\nforce3.cmd">Install nforce3 Adapter</MITEM>
<MITEM TYPE="ITEM"

And there's a copy of the nforce3.cmd file in the

hwpnp files dir.

And as I said above I use a batch file to launch pebuilder

Here's the contents of that.

cls
@echo off
echo have you copied correct nforce folder to nforce-ethernet folder
pause
pebuilder.exe -exit -overwrite


rem echo INFCACHE.1

if exist E:\1-pebuilder-313-24\BartPE\i386\inf\*.pnf ( echo y.|del E:\1-pebuilder-313-24\BartPE\i386\inf\*.pnf )
if exist E:\1-pebuilder-313-24\BartPE\i386\inf\InfCache.1 del E:\1-pebuilder-313-24\BartPE\i386\inf\InfCache.1
rem start /wait UpdateInfs.exe E:\1-pebuilder-313-24\BartPE\i386\inf\*.inf
copy E:\1-pebuilder-313-24\nforce-Ethernet\*.inf E:\1-pebuilder-313-24\BartPE\i386\inf
copy E:\1-pebuilder-313-24\nforce-Ethernet\*.dll E:\1-pebuilder-313-24\BartPE\i386\system32
copy E:\1-pebuilder-313-24\nforce-Ethernet\*.exe E:\1-pebuilder-313-24\BartPE\i386\system32
copy E:\1-pebuilder-313-24\nforce-Ethernet\*.sys E:\1-pebuilder-313-24\BartPE\i386\system32\drivers
start /wait E:\1-pebuilder-313-24\BuildScripts\InfCacheBuild.exe E:\1-pebuilder-313-24\BartPE


echo building ISO...

makeiso.cmd


:end

and makeiso.cmd has this in it

mkisofs.exe -v -force-uppercase -duplicates-once -iso-level 4 -volid "BartPE" -A PEBUILDER/MKISOFS -sysid "Win32" -b bootsect.bin -no-emul-boot -boot-load-size 4 -hide bootsect.bin -hide boot.catalog -o E:\1-iso-s\bpe313ubcd24markwnf.iso E:\1-pebuilder-313-24\BartPE


This later I don't believe ever got tweaked and I have no idea if it's even mildly optimal I just know it seems to work okay.

That's it, easy huh <g>.

Thanks

[Deacon]

So, with the above you can build a working nforce3 nic plugin.

I put the current nvidia all in one ethernet drivers in the directory quoted in my final build script (E:\1-pebuilder-313-24\nforce3-Ethernet\.)

Unfortunately Nvidia hasn't released a new all in one driver pack that properly supports both nforce3 and nforce4 so in order to build for nforce4, you have to use the nforce4 driver pack and put those files in that same location (E:\1-pebuilder-313-24\nforce3-Ethernet\.)

So, you can build a disk that supports one or the other but not both because both drivers use files with the same names, but with different chipset support.

Thanks

[SteelTrepid]

I thank you for taking the time to post this in our forum, very informative and helpful. We are here to help. I appreciate it when users that have knowledge of something that I do not know are willing to take the time to help everyone else.

I notice someone pinned this. I think it should be moved to a different category or forum. I was thinking of "CD Creation Questions" or "FAQ", just some where else more appropriate. I didn't move it because I wanted more feedback from you guys on where it should be located. Once we figure that out I will delete these "off topic" posts about where to move it to. I also realized when trying to find a place for it, that there are several topics that are pinned but seem to be in inappropriate categories or forums. I'll have to look at that more. If anyone has the time please PM any suggestions on where something should be moved.

[Deacon]

I geuss I can't edit my posts? or I'm blind, not seeing an edit button.

Anyway, I left out an important piece of info in the above description.

Nvidia driver ships with two files

nvefdxp.sys and
nvefd2k.sys

One of those files gets copied and renamed to nvenetfd.sys for installation.

So, yes my plugin such as it is, installs both the unrenamed and the renamed file. I actually don't think this is necessary, but haven't really been able to figure this out totally, other then that I know what's listed does work.

Thanks to neutr0n for bringing this to my attention.

[LittlBUGer]

I've also noticed the renaming of the file issue as pebuilder will spit back at me if I don't (when I originally created the drivers). So I had to copy the file and rename it and then it worked fine (well... at least it didn't spit an error back at me...).

[Deacon]

Here's another possible source for a more finished and supposedly functional nforce3 plugin

http://www.911cd.net...showtopic=12153

I tried a version of this and didn't work for me, but didn't put in much time tweaking.

Thanks

[LittlBUGer]

I think there's got to be a way to trick pebuilder in adding the Net Bus as some sort of SCSI Adapter along with the drivers themselves and somehow get it to work. How to do this, I don't know... maybe create some sort of crazy txtsetup.oem file? Anyway, hopefully someone will figure something out. I tried getting that plugin you mentioned that someone posted today, but link was dead. :-\

[SteelTrepid]

I would love to try and get it working! But I do not have the cash to purchase a new board and processor. I also have little time so I probably wouldn't get to it very quickly. Kind of like the wireless network, had the hardware for months but still haven't found time to test.

[LittlBUGer]

Well, since I'm all done with school now, I should be able to have a little more time for testing and since my mobo is nForce3, I can see what I can come up with, if the plugin(s) work.

[Pihahiroth]

LittlBUGer, on May 10 2005, 04:17 PM, said:

I think there's got to be a way to trick pebuilder in adding the Net Bus as some sort of SCSI Adapter along with the drivers themselves and somehow get it to work. How to do this, I don't know... maybe create some sort of crazy txtsetup.oem file? Anyway, hopefully someone will figure something out. I tried getting that plugin you mentioned that someone posted today, but link was dead. :-\

Once of the big problems is with the renaming of either nvefdxp.sys and nvefd2k.sys to nvenetfd.sys. It may be possible to alter this behavior with a rewrite of the inf since nvefd2k.sys is not applicable.

Has this already been done since '05? I noticed that v1.8 of the drivers has nforce3 and nforce4. Do these drivers actually work?

[dirkgently42]

1.8 drivers are included with v3.0 of the project.
You might try LB's 1.9 drivers from link: http://downloads.littlbuger.info/ under "Ultimate Boot CD 4 Windows"
(link also available by clicking on LB's sig)

[SteelTrepid]

Yeah, but really....that doesn't address the issues with those STUPID nVidia drivers!!