Re: Intel PRO 100 VE Component broken?
- From: "Sean Liming \(MVP\)" <sean_liming@xxxxxxxxxxxx>
- Date: Fri, 28 Sep 2007 09:29:20 -0700
With several versions of the Intel driver I had to include the extra DLL and DIN file. I believe these are needed for Windows to communicate with the driver.
--
Regards,
Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
"Michael" <michael@xxxxxxxxxxxxx> wrote in message news:E1D729CF-D03A-47EA-8B69-B0723A9B43FC@xxxxxxxxxxxxxxxx
I use an XP embedded target board with an Intel PRO 100 VE network adapter.
In TargetDesigner I include the corresponding PRO 100 VE component, but when
I boot the target no network is working. Also snetcfg.exe doesn't show any
adapter.
I recognised that the files C:/WINDOWS/system32/drivers/e100b325.sys and
C:/WINDOWS/inf/net557.inf actually are installed, but still the PnP doesn't
recognize the adapter.
On the other hand, when I install a normal XP on the same target board then
networking is no problem. In that case I use the original Intel driver for
the PRO 100. However, in that case the driver properties also show
dependencies to other files like e100b325.din, e100bmsg.dll and others from
the C:/WINDOWS/system32 directory.
When I copy those files manually to my XP embedded image then networking is
no problem.
My question now is, is the PRO 100 VE Component broken or do I need
additional components (where maybe the dependency check is broken)?
My TargetDesigner is version 2.00.0807.0 with SP2 installed. The PRO/100 VE
Adapter Component shows up as version 5.1.2600 rev 620.
Any help greatly appreciated.
Cheers, Michael
.
- Prev by Date: Re: Importing inf File into Componet Designer
- Next by Date: Re: Dependency Check very slow.
- Previous by thread: Re: Importing inf File into Componet Designer
- Next by thread: Re: Possible to make a bootable CF card ROM w/o secondary disk/partiti
- Index(es):
Relevant Pages
|
|
