btw, out of topic,Penetwork plugin also have lan-driver add option, which may workaround what you mention herehttp://theoven.org/index.php?topic=294still it is a workaround of failure of lan-driver integration,and as all workarounds it has some drawback since penetwork first needs to find driver and install, and than start network ;)dism experts may write more info there when they have some free time...
Start Editor" --> "CMDs after startup" or "CMDs after ip change".options ;) adding your batch name...
Maybe an additional option around IncludeinSys32a checkbox saying "PeNetwork_After.cmd" (default selected true)PeNetwork_After_CheckBox=PeNetwork_After.cmd,1,3,320,781,127,18,Trueso if end-user add PeNetwork_After.cmd to Win7PE_SE\Workbench\Common\PENetwork_Include\he would automatically get the magic (hopefully via Penetwork-"CMDs after startup", some ini entry...)this way, a usual problem of "start after network" mostly solved
CMDStart.CMD1=CmdsAfterstartup.cmdCMDStart.Start1=NormalCMDStart.Wait1=Yes
hehe, sorry we do not have funds to buy time If we have, I may be first time a bit selfish to buy myself
here you go