For now, an updated experimental Wdf plugin pack is available
here --> http://forum.driverpacks.net/viewtopic. … 302#p58302 

Any feedback is appreciated.

He would need to edit the .Ini within DP_LAN, as the WDF-based drivers are disabled for PE to allow the included plugins to (hopefully) work.

From:

[AX]
; BartPE Code
ms_count	= 0

...

[S]
; BartPE Code
ms_count	= 0

To:

[AX]
; BartPE Code
ms_count	= 3

...

[S]
; BartPE Code
ms_count	= 2

loading drivers for the Asix ax88772b or ax88179 USB nics in either bartpe or ubcd?

Do you boot from a CD/DVD or USB storage?

Yes, as indicated alredy WDF is the culpirt.
Windows Driver Frameworks (WDF) and NIC is a new beast.
No hardware to test this.

Assumption:
add WDF driver as a classic plugin.
load NIC card at PNP time, hence the NIC plugin is not required.

Create a file <PEBuilder>\plugins\WDF\wdf.inf

Extract files wdfldr.sys and wdf01000.sys. Copy both files to <PEBuilder>\plugins\WDF\files\

Add the DP_LAN package too.

Test this.

If this fails, then edit the driver inf files, remove the WDF coiinstaller lines.

        I hope i have credited cdob (and Damnation) appropriately.

    The plugins, in this form, are untested and marked as such.
  You will find each pack in their respective forum topics.

My apologies for any delay, the changelogs were the toughest nut to crack.

edit:  Ah, now i remember the relevance of 8.3 naming conventions.
          cdob advised that may be necessary should 8.3 filename generation be disabled.
            As for whether that is relevant in PE, IDK.

Note:  UBCD is linux-based, IIRC.

there will be much info on how to do this and the support team that is most familiar with it.

cdob may pop in here. He does that from time to time. but more likely over there.

PS in your original post you confused UBCD with UBCD4Win which are two seperate and unrelated projects .

PE drivers should not have XP skipped unless they are not to be installed ever for xp... (very rare)
all pe drivers should be skipped for 2k (not that it matters since there are no PE builds using 2K)
2k3 based on if it is supported by the driver. (most are)

Most of these sections will only have skip = 2K  (

always use mscount 0 to disable a driver

good thinking above, well done

; PE Builder v3 plug-in INF file
; created by cdob (for VIA USB 3.0), modified by TechDud for ASIX USB 2.0 LAN

; ASIX AX88772B/772C including Lenovo USB 2.0 Ethernet Adapter

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="driver: ASIX AX88772B USB2.0 to Fast Ethernet Adapter"
Enable=1

[SourceDisksFiles]
files\ax88772b.sys=4,,1
files\ax88772b.inf=20,,1
files\LenLan.inf=20,,1

;extracted with 7-zip from file - WdfCoInstaller01009.dll:
;Microsoft Kernel-Mode Driver Framework Install-v1.9-Win2k-WinXP-Win2k3.exe
files\WDFLDR.SYS=4
files\WDF01000.SYS=4

[SetValue]
;Controller
"txtsetup.sif","SourceDisksFiles","ax88772b.sys", "1,,,,,,4_,4,1,,,1,4"
"txtsetup.sif","BusExtenders.Load","ax88772b", "ax88772b.sys"
"txtsetup.sif","HardwareIdsDatabase","USB\VID_0B95&PID_772B&REV_0001", " ""ax88772b"""
"txtsetup.sif","HardwareIdsDatabase","USB\VID_0B95&PID_772B&REV_0002", " ""ax88772b"""
"txtsetup.sif","HardwareIdsDatabase","USB\VID_0B95&PID_7E2B&REV_0001", " ""ax88772b"""
"txtsetup.sif","HardwareIdsDatabase","USB\VID_17EF&PID_7203", " ""ax88772b"""
;
;Kernel Mode Driver Framework Runtime
"txtsetup.sif","SourceDisksFiles","wdfldr.sys", "1,,,,,,4_,4,1,,,1,4"
"txtsetup.sif","SourceDisksFiles","wdf01000.sys", "1,,,,,,4_,4,1,,,1,4"
"txtsetup.sif","BootBusExtenders.Load","wdf01000", "wdf01000.sys"
"txtsetup.sif","BootBusExtenders","wdf01000", " ""Kernel Mode Driver Framework Runtime"",files.none,wdf01000"

How can i package these?  It would be good to have them available for all 5 effected drivers.
  edit: found tutorials.  down to modifying the .Inf files

With the idea of using PE Plugins for those LAN drivers that use WdfCoInstaller01009.dll, it would seem that they should be disabled in the .Ini.

Is this correct?
    Is it also true that 8.3 file-naming conventions must be observed?

Please help to finish this.  I do credit by those that assist or pioneer solutions.

cdob already has a working plugin with wdfldr.sys included for VIA USB 3.0 PE support.  That should work for Fresco Logic controllers with some minor modifications.

How hard would it be to shoehorn in the file references you need for a custom plugin?
  Maybe something like this:

; PE Builder v3 plug-in INF file
; created by cdob (for VIA USB 3.0), modified by TechDud for ASIX USB 2.0/3.0 LAN

; ASIX AX88179/178A

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="driver: ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet Adapter"
Enable=1

[SourceDisksFiles]
files\ax88178a.sys=4,,1
files\ax88178a.inf=20,,1

;extracted with 7-zip from file - WdfCoInstaller01009.dll:
;Microsoft Kernel-Mode Driver Framework Install-v1.9-Win2k-WinXP-Win2k3.exe
files\WDFLDR.SYS=4
files\WDF01000.SYS=4

[SetValue]
;Controller
"txtsetup.sif","SourceDisksFiles","ax88178a.sys", "1,,,,,,4_,4,1,,,1,4"
"txtsetup.sif","BusExtenders.Load","ax88178a", "ax88178a.sys"
"txtsetup.sif","HardwareIdsDatabase","USB\VID_0B95&PID_1790", " ""ax88178a"""
"txtsetup.sif","HardwareIdsDatabase","USB\VID_0B95&PID_178A", " ""ax88178a"""
"txtsetup.sif","HardwareIdsDatabase","USB\VID_0DF6&PID_0072", " ""ax88178a"""
"txtsetup.sif","HardwareIdsDatabase","USB\VID_17EF&PID_304B", " ""ax88178a"""
"txtsetup.sif","HardwareIdsDatabase","USB\VID_0930&PID_0A13", " ""ax88178a"""
;
;Kernel Mode Driver Framework Runtime
"txtsetup.sif","SourceDisksFiles","wdfldr.sys", "1,,,,,,4_,4,1,,,1,4"
"txtsetup.sif","SourceDisksFiles","wdf01000.sys", "1,,,,,,4_,4,1,,,1,4"
"txtsetup.sif","BootBusExtenders.Load","wdf01000", "wdf01000.sys"
"txtsetup.sif","BootBusExtenders","wdf01000", " ""Kernel Mode Driver Framework Runtime"",files.none,wdf01000"

Upon review of my "LenLan.inf" file, it would appear that i have made some amateurish mistakes.
  First, i neglected to comment-out the .cat file.
    Second, I should have stuck with the string variable %AX88772B.DeviceDesc% instead of %LenLan.DeviceDesc%.
      Thirdly, I didn't modify the variables for all languages to read the following:

AX88772B.DiskName = "Lenovo USB 2.0 Ethernet Adapter Driver Diskette"
AX88772B.DeviceDesc = "Lenovo USB 2.0 Ethernet Adapter"

My apologies.

edit:  Additionally, it would seem that the entries in DP_Lan.ini may be incorrect as well.

[AX]
; BartPE Code
ms_count	= 2
ms_1_tag	= "ax88179"
ms_1_sysfile	= "ax88179_178a.sys"
ms_1_exc_skipIfOS	= "w2k,wxp,w2k3"

ms_2_tag	= "ax88772b"
ms_2_sysfile	= "ax88772b.sys"
ms_2_exc_skipIfOS	= "w2k,wxp,w2k3"

I would like to see this set up so that you have the greatest odds of success.

If anybody with more experience with network installs could weigh in, i would be most appreciative.
  The skipIfOS= variable has me puzzled.

edit:  if only "ms_1_sysfile2 = "wdfldr.sys"" could be added for both.

yes TD seems like we just did this didn't we

Additionally, i wonder if the new "LenLan.inf" works on it's corresponding hardware.
  I cannot test that.

Also, it may be true that ax88179_178a.sys and associated files need be renamed, and references to files in the .Inf altered to reflect the changes for textmode to function properly.
  (See DP_MassStorage_wnt5_x86-32_1308132\D\M\U3\Etron*.*)