I think i might have an answer to why my nic is not being foudn when pe

boots.



it appears that my lan.inf file i manually copied is not being copied to the

iso.image when being created.



i confirmed this while looking at the buildcd.log and found it had no

mention there either.



I'm confused.



Cheers.

Andrew

The "BuildCD" process uses DRVINST.EXE (a Windows PE utiliy) to inject the

drivers in the "ExtraNics" directory into the PE image.  It decides what

files need to be copied by reading the driver installation INF files in the

"ExtraNics" directory.  It will not search subdirectories, nor will it copy

files not referenced by the INF.



Typically, the LAN.INF (which isn't a driver installation INF) is used by

the old DOS drivers and isn't needed.



From the BuildCD.log, can you see any messages from DRVINST.EXE reporting

drivers added to PE?  What does your "ExtraNics" directory look like?



-Michael Niehaus

Systems Design Engineer

mniehaus@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.





"SameOld" <andrew_paiti@hotmail.com> wrote in message

news:1135034539.24387@huey.topnz.ac.nz...

>I think i might have an answer to why my nic is not being foudn when pe

>boots.

>

> it appears that my lan.inf file i manually copied is not being copied to

> the iso.image when being created.

>

> i confirmed this while looking at the buildcd.log and found it had no

> mention there either.

>

> I'm confused.

>

> Cheers.

> Andrew

>

Be aware that drvinst.exe in the BDD scripts check for error codes so be

sure to read the buildcd.log Michael mentioned. If you use the newest

broadcom inf supplied with the dell SX620 (i believe), drvinst.exe does not

add the necessary files to winpe because it generates an error because of

the b57w2k.sys file specified in the b57wxp.inf.



Comment out the b57w2k.sys in the sourcedisknames and copy files section

will do



r





"Michael Niehaus [MS]" <mniehaus@online.microsoft.com> wrote in message

news:e$LUj$fBGHA.2476@TK2MSFTNGP10.phx.gbl...

> The "BuildCD" process uses DRVINST.EXE (a Windows PE utiliy) to inject the

> drivers in the "ExtraNics" directory into the PE image.  It decides what

> files need to be copied by reading the driver installation INF files in

> the "ExtraNics" directory.  It will not search subdirectories, nor will it

> copy files not referenced by the INF.

>

> Typically, the LAN.INF (which isn't a driver installation INF) is used by

> the old DOS drivers and isn't needed.

>

> From the BuildCD.log, can you see any messages from DRVINST.EXE reporting

> drivers added to PE?  What does your "ExtraNics" directory look like?

>

> -Michael Niehaus

> Systems Design Engineer

> mniehaus@microsoft.com

> This posting is provided "AS IS" with no warranties, and confers no

> rights.

>

>

> "SameOld" <andrew_paiti@hotmail.com> wrote in message

> news:1135034539.24387@huey.topnz.ac.nz... 

>

>

That is precisely my problem, buildcd.log is reporting that DRVINST is an

invalid internal or external command, script or batch utility (not the exact

wording)

I had a look for it and I cannot find this file.



Additionally earlier in the buildcd.log i see a mention not bldini not being

found, would you knwo exactly what this is?



Appreciate your reponse!

Thanks,

Andrew





"Michael Niehaus [MS]" <mniehaus@online.microsoft.com> wrote in message

news:e$LUj$fBGHA.2476@TK2MSFTNGP10.phx.gbl...

> The "BuildCD" process uses DRVINST.EXE (a Windows PE utiliy) to inject the

> drivers in the "ExtraNics" directory into the PE image.  It decides what

> files need to be copied by reading the driver installation INF files in

> the "ExtraNics" directory.  It will not search subdirectories, nor will it

> copy files not referenced by the INF.

>

> Typically, the LAN.INF (which isn't a driver installation INF) is used by

> the old DOS drivers and isn't needed.

>

> From the BuildCD.log, can you see any messages from DRVINST.EXE reporting

> drivers added to PE?  What does your "ExtraNics" directory look like?

>

> -Michael Niehaus

> Systems Design Engineer

> mniehaus@microsoft.com

> This posting is provided "AS IS" with no warranties, and confers no

> rights.

>

>

> "SameOld" <andrew_paiti@hotmail.com> wrote in message

> news:1135034539.24387@huey.topnz.ac.nz... 

>

>

It sounds like you don't have a valid copy of Windows PE 2004 or Windows PE

2005.  You need to copy the entire Windows PE CD to the specified

directories (e.g. \source\WindowsPE2004).  Windows PE 1.2 is not supported.



-Michael Niehaus

Systems Design Engineer

mniehaus@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.



"SameOld" <andrew_paiti@hotmail.com> wrote in message

news:1135220068.186@huey.topnz.ac.nz...

> That is precisely my problem, buildcd.log is reporting that DRVINST is an

> invalid internal or external command, script or batch utility (not the

> exact wording)

> I had a look for it and I cannot find this file.

>

> Additionally earlier in the buildcd.log i see a mention not bldini not

> being found, would you knwo exactly what this is?

>

> Appreciate your reponse!

> Thanks,

> Andrew

>

>

> "Michael Niehaus [MS]" <mniehaus@online.microsoft.com> wrote in message

> news:e$LUj$fBGHA.2476@TK2MSFTNGP10.phx.gbl... 

>

>