Re: IOCTL_NDIS_QUERY_GLOBAL_STATS on CE/PPC 2003

From: Maxim S. Shatskih (maxim_at_storagecraft.com)
Date: 02/26/04

  • Next message: Paul G. Tobey [eMVP]: "Re: IOCTL_NDIS_QUERY_GLOBAL_STATS on CE/PPC 2003" 
    Date: Fri, 27 Feb 2004 01:15:47 +0300

        Well... you're right in the point that NDISUIO also has the "query OID"
    IOCTL, but IOCTL_NDIS_QUERY_GLOBAL_STATS has no connections to NDISUIO.

        In fact, NDISUIO (at least on Windows, maybe the CE picture is another) is
    just the protocol driver who converts the IOCTLs to things like NdisRequest,
    WriteFile to NdisSend and so on.

        IOCTL_NDIS_QUERY_GLOBAL_STATS talks to NDIS itself, not to some protocol
    driver. If it has some lame support in CE - then I will use NDISUIO. 

    -- 
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com
"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument_no_spam.com> wrote in message
news:OYOYAPL$DHA.3828@TK2MSFTNGP10.phx.gbl...
> I'd guess that you send that through the NDISUIO driver, which you can look
> up in the help.  Generally, you open it, then call DeviceIoControl() to send
> messages to it.
>
> Paul T.
>
> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
> news:uYN2TAL$DHA.4072@tk2msftngp13.phx.gbl...
> >     I need to send an OID query to my miniport.
> >
> >     In Windows, I would use IOCTL_NDIS_QUERY_GLOBAL_STATS to do this.
> >
> >     This IOCTL is also noted in PB and PPC 2003 SDK headers, with no MSDN
> > Library (CD version at least) documentation and no sample code.
> >
> >     Can I call this IOCTL on CE?
> >
> >     If yes - how must I open and prepare the file handle for it to denote
> the
> > particular adapter, and not just "NDS0:"?
> >
> > -- 
> > Maxim Shatskih, Windows DDK MVP
> > StorageCraft Corporation
> > maxim@storagecraft.com
> > http://www.storagecraft.com
> >
> >
>
>
  • Next message: Paul G. Tobey [eMVP]: "Re: IOCTL_NDIS_QUERY_GLOBAL_STATS on CE/PPC 2003"

    Relevant Pages

    • Re: sharing memory with user and kernel
      ... Pend an IOCTL in the driver, then, when event occurs, fill it with data and ... Maxim Shatskih, Windows DDK MVP ...
      (microsoft.public.development.device.drivers)
    • Re: Kernel mode to user mode
      ... where they make sense in the context of using IoCtls for data passing also. ... An app passes an IoCtl to a driver initiating a series of tests that will ...
      (microsoft.public.development.device.drivers)
    • [RFC] dev_acpi: device driver for userspace access to ACPI
      ... The basic concept of operation is that the ioctl operates on the ACPI ... The sample, proof-of-concept app, is called acpitree. ... You can find the driver and sample app here: ...
      (Linux-Kernel)
    • Re: Accessing Ndis miniport from user mode application
      ... sticking to WMI, you confine yourself to strictly defined model - there are ... driver can indicate. ... to you - as I told you already, you should go for IOCTL model. ... Accessing custom OIDS through WMI. ...
      (microsoft.public.development.device.drivers)
    • Re: Why is remote system information calling ioctl for my driver?
      ... Changing the key name doesn't keep the System Information ... don't think the ioctl probing was causing the System Information util to fail ... How does it decide that my driver is a serial port ... the SerialPortIndex registry key to decide if the driver should be probed ...
      (microsoft.public.windowsce.platbuilder)