Ipaq 5500;cannot open internal wifi adapter with ndisuio

Discussion in 'Windows Vista Drivers' started by Denis Lassoto, Oct 13, 2003.

  1. Hi,

    I am trying to develop an application that requires me to send and receive
    packets on an ipaq 5500 (windows ce 4.2) via the internal wifi interface. I
    am using ndisuio protocol driver for the packet sending receiving stuff.

    I can create a file handle, but I find I am totally unable to open the
    adatper. my code however is fairly simple and looks like this:

    // Create file handle for the driver
    Handle= CreateFile (NDISUIO_DEVICE_NAME,

    // open the specified adapter
    status=DeviceIoControl (Handle,
    wcslen(TEXT("VNETUSBA1")) * sizeof(TCHAR),
    NULL, 0, &dwReturnedBytes, NULL);

    the CreateFile is sucessful by the DeviceIoControl fails systematically.

    Has anybody been ever successful in opening this interface that way?

    Denis Lassoto
    Denis Lassoto, Oct 13, 2003
    1. Advertisements

  2. Fails with what error?

    Are you developing your own network protocol to use instead of TCP/IP or
    something (I'm trying to understand why you'd want to send raw packets via

    Paul T.
    Paul G. Tobey [eMVP], Oct 13, 2003
    1. Advertisements

  3. I want to catch 802.1X packets . They carry the ethernet protocol 0x888E
    Error in 1F : a device attached to the system is not functionning.

    Denis Lassoto, Oct 13, 2003
  4. And you're sure about the adapter name you're passing to the
    DeviceIoControl() call? Is it the same name as returned from
    GetAdaptersInfo() (I think you can call that function)?

    Paul T.
    Paul G. Tobey [eMVP], Oct 13, 2003
  5. Actually in order to get the adapter names, i use DeviceIoControl with the
    In the case of the ipaq 5500, the internal wifi, the device name is
    returned as VNETUSBA1
    and the description as vnetusba1.
    If I attach an other pcmcia wifi adapter to the ipaq using a jacket, I can
    successfully opn this adapter and to read and write operations on it. But it
    does not work with the internal one.

    Denis Lassoto, Oct 13, 2003
  6. Unless the internal adapter's driver failed a request sent as a result of
    the DeviceIoControl, I don't know how to explain the error. Unfortunately,
    I don't know enough about what might cause that error to be returned to
    hazard a decent guess as to what to try next. MS?

    Paul T.

    Paul G. Tobey [eMVP], Oct 13, 2003
  7. Hi,

    You don't have to open the adapter as it is in other Windows systems
    (XP, NT, 9X...)

    If you look closer to the documentation about the NDIS queries, you will
    see that you need to provide the adapter's name in the structure passed
    to the function (NDISUIO_QUERY_OID / pAdapterName). That's why you don't
    need to open it before.

    It works very well for me and I have the same iPAQ!

    Marc-Aurèle Brothier, Oct 20, 2003
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.