Re: Adapter failed to initialize query

Thanks Maxim....but I have another problem. I am porting from Windows to
WinCE where I use NDISRegisterAdapter to bind to NDIS.

This is obsolete in DDK but works in WinCE. The problem is that once I
choose 802.3 as a medium I am restricted to send only ethernet packet size
worth of data which would prove expensive as the IP packets I revceive can
be much larger in size.

In wince newsgroup I found the following discussion that looks like my
problem

http://groups.google.co.in/group/microsoft.public.windowsce.embedded/browse_thread/thread/227fab67a0222e18/6ee9c3c6e17a845b?lnk=st&q=mac+layer+driver+in+wince&rnum=5&hl=en#6ee9c3c6e17a845b


but unfortunately it doesn't provide a complete solution.

Can you please guide me on what I can do to avoid faking as an ethernet
driver so that I can send up my IP packets without fragmenting them and
making ethernet frames out of them.

Your help is most appreciated.

Regds.
Nitin
"Maxim S. Shatskih" <maxim@xxxxxxxxxxxxxxxx> wrote in message
news:uiJYOpQpGHA.4192@xxxxxxxxxxxxxxxxxxxxxxx
Use 803.3 media type, this will allow TCP/IP to bind to you and you
will
have the Ethernet frame format in your driver. Fake the MAC addressed
someway
in them, as also in "query MAC address" OID.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@xxxxxxxxxxxxxxxx
http://www.storagecraft.com

"tsindia" <tsindia@xxxxxxxxxxxxxxxxx> wrote in message
news:usbzYjOpGHA.2360@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

I have a usb function driver( its not RNDIS) which I am binding to NDIS
as
I need to pass IP packets to teh protocol layer. DiverEntry and
MiniportInitialize go through okay.

I choose the medium as NdisMediumDix as USB is not a defined as a medium.

I set my virtual NIC attributes as

NdisMSetAttributesEx(
MiniportAdapterHandle,
(NDIS_HANDLE) Adapter,
0,
NDIS_ATTRIBUTE_NO_HALT_ON_SUSPEND,
NdisInterfaceInternal);

I get Queries from NDIS to which I respond. The last query I get is for

OID_PNP_CAPABILITIES

which I succeed and then I get the error message

LanRegister: Adapter failed to initialize. Status = 0xc0010019

I have no idea why my adapter is failing to initialize.

Can anyone help me.

Thanks.
Nitin





.

Relevant Pages

  • RE: Help!! Out of the Pot and into the Driver Fire
    ... We are for now doing all this on pre-Vista OS. ... However, if you are just desperate to do things at NDIS level, you can write ... NDIS IM filter is not always easy to write - the same driver may work well ... the effect of lag and dropped packets and I got tagged as the lucky developer ...
    (microsoft.public.development.device.drivers)
  • Re: Capturing network packets on Vista
    ... And NDIS 6.0 silently drops packets before filter. ... Or may be packets are dropped in stack. ... surely packet sends to the miniport in D2 are noise. ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS Vs Protocol Who will drop the packets?
    ... I'll also add a summary of the "Ndis miniport syncronisation question" chat, ... > explicitly been asked to allow certain types of packets, ... The mechanism by which NICs achieve this is hardware ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS IM: queueing question
    ... NDIS actually reflects what NDIS really does... ... NDIS does not drop any packets because it does not allocate them. ... to help protocols and miniports communicate with each other. ... drivers to be separate. ...
    (microsoft.public.development.device.drivers)
  • Re: NDIS Version question.
    ... WinCE 4.2, the IP stack was NDIS 4 and did not support them. ...
    (microsoft.public.development.device.drivers)