Re: driver Intel 82541ER - Help

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hello Paolo,

I tried another DLL-File (Driver) which is not from Intel. I can say that
there was something wrong in the DLL from Intel. Because Intel don't support
those Driver or make the code free you got no chance to get the mistake
within the sourcecode...

Sorry,

Greetings Mario

"Paolo" wrote:

On 24 Apr, 11:48, Mario Z <Mario Z...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Hi,

I've downloaded the “Intel® 82541ER Gigabit Ethernet Controller”-driver for
Windows
CE5, available from the Intel website. My doubt is how to install it. I have
imported the CEC through Platform Builder, and it appears in the catalog
under Third Party -> Device Drivers  Intel(r) Gigabit Ethernet Drivers.

I included the registry entries and the bib file like Intel explains it in
the “ReadMe”-file. Furthermore I bind the e1000ce5.dll and e1000ce5.rel Files
into the image.

I use a Kontron ETX-PM witch has already one network chip on it. I use this
one for debugging. Windows CE starts but the e1000ce5.dll don’t get loaded.
In the Debug output I get following output:

NDIS:ndisAddPCMCIADevice INdisOpenDeviceKey failed
NDIS:: CE_AddBusFriendlyName() [successfully created]
[HKLM\Comm\BusFriendlyNames\PCI_1_3_0\E1000CE51]>>> Loading module e1000ce5.dll at address 0x01B70000-0x01B96000

Loaded
'F:\WINCE500\PBWORKSPACES\ELB50PM\RELDIR\JCEPC_X86_DEBUG\E1000CE5.DLL', no
matching symbolic information found.
==>NdisInitializeWrapper
<==NdisInitializeWrapper
OEMIoControl: Unsupported Code 0x1012000 - device 0x0101 func 2048
==>NdisMRegisterMiniport: NdisWrapperHandle 00055DE0
==>ndisRegisterMiniportDriver: NdisWrapperHandle 00055DE0
<==ndisRegisterMiniportDriver: MiniBlock 0005E860
NdisMRegisterMiniport: MiniBlock 0005E860
<==NdisMRegisterMiniport: MiniBlock 0005E860, Status 0

ndisMInitializeAdapter: Miniport 00391200,
==>ndisQueueMiniportOnDriver: Miniport 00391200, MiniBlock 0005E860
ndisQueueMiniportOnDriver: Miniport 00391200, MiniBlock 0005E860, rc 1
==>NdisMSetAttributesEx: Miniport 00391200
Deleting an uninitialized critical section, ignored!
Deleting an uninitialized critical section, ignored!
Deleting an uninitialized critical section, ignored!
Deleting an uninitialized critical section, ignored!
==>NdisMDeregisterAdapterShutdownHandler: Miniport 00391200
<==NdisMDeregisterAdapterShutdownHandler: Miniport 00391200
***NDIS*** (b, 2078)
INIT FAILURE: Dequeueing the miniport from the driver block.
==>ndisDeQueueMiniportOnDriver, Miniport 00391200, MiniBlock 0005E860
<==ndisDeQueueMiniportOnDriver: Miniport 00391200, MiniBlock 0005E860
***NDIS*** (b, 2105)
INIT FAILURE: Dereferencing the miniport block.
ndisDereferenceMiniport:Miniport 00391200, Ref = 0
==>ndisMUnload: DriverObject 00055D30
ndisMUnload: MiniBlock 0005E860
<==ndisMUnload: DriverObject 00055D30, MiniBlock 0005E860
<<< Unloading module e1000ce5.dll at address 0x01B70000-0x01B96000
Unloaded symbols for
'F:\WINCE500\PBWORKSPACES\ELB50PM\RELDIR\JCEPC_X86_DEBUG\E1000CE5.DLL'
DEVICE!LaunchDevice: Init() failed for device 0x00055840
DEVICE!I_ActivateDeviceEx: couldn't activate: prefix NDS, index 1, dll
NDIS.dll, context 0x602da1c

So I need help!?!

Regards,

Mario

Hi,
I have a very similar problem with the chipset 82559 driver.. The
error it's the same in the same position of boot.. Unfortunately I
have not found a solution.. And the Intel has answered to my help
request saying that they don't support the driver !! Mah.. Can you
report the .reg configuration? I'm curious to see it..

Thank You

Paolo


.



Relevant Pages

  • Re: driver Intel 82541ER - Help
    ... available from the Intel website. ... ndisQueueMiniportOnDriver: Miniport 00391200, MiniBlock 0005E860, rc 1 ... Deleting an uninitialized critical section, ... Dequeueing the miniport from the driver block. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: FreeBSD 7.0 problems
    ... Ergo I can't fault the hardware in any way. ... The wifi driver complains of timeout errors. ... vendor = 'Intel Corporation' ... ABI class: ...
    (freebsd-questions)
  • ASUS P5B-MX [946GZ/GMA 3000] does not work with Intel driver
    ... I cannot make Intel 3000GMA in ASUS P5B-MX to work with intel driver. ... intel: Failed to allocate framebuffer. ... Loading extension XFree86-DRI ...
    (freebsd-stable)
  • ASUS P5B-MX [946GZ/GMA 3000] does not work with Intel driver
    ... I cannot make Intel 3000GMA in ASUS P5B-MX to work with intel driver. ... intel: Failed to allocate framebuffer. ... Loading extension XFree86-DRI ...
    (freebsd-current)
  • Re: RAID Setup and DP35DP?
    ... The Intel RAID/ACHI driver diskette in a NEC USB Floppy Drive was seen/read OK after an F6 during a WinXP clean-install just now. ... this device which worked a minute earlier in the install process is now dead to the install process. ... I can repeat this problem constantly, and have tried various other changes such as specifying AHCI instead of RAID in the BIOS. ...
    (comp.sys.intel)