none
How to load a Wi-Fi driver automatically during boot time? RRS feed

  • Question

  • Hi all,

    I have a Wi-Fi driver from a manufacturer (not included source code). That driver has Plug and Play support. I want to load the driver automatically during boot time.

    Before, I've written a simple stream interface driver. I have edited project.reg to create a sub-key under HKLM\Devices\BuiltIn so that Device Manager can load automatically during boot time. And it was successfully loaded. But Wi-Fi driver is a non-stream driver. Can Device Manager load Wi-Fi driver automatically with the same way? What should I change/add to do this? I have seen that NDIS driver can have XXX_Init function in NDIS Upper-Edge functions at http://msdn.microsoft.com/en-us/library/ee481066.aspx.

    What differences are there between stream interface drivers and NDIS Wi-Fi drivers from the point of loading automatically during boot-time? Can you give me links for further information?

    Thanks in advance for your helps and clarifications.

    Best regards,

    Tuesday, November 2, 2010 1:47 PM

All replies

  • Check out the following page for the registry settings for your NDIS driver.
    Tuesday, November 2, 2010 2:59 PM
  • you have to check the following components added in your OSDesign

    Wireless LAN (802.11) STA - Automatic Configuration and 802.1x  - SYSGEN_ETH_80211

    Network User Interface - SYSGEN_CONNMC

    See the bellow given registry settings for Miniport driver.

    http://msdn.microsoft.com/en-us/library/ms893567.aspx

    you have to configure these registry settings for your driver

     


    Vinoth.R http://vinoth-vinothblog.blogspot.com http://www.e-consystems.com
    Tuesday, November 2, 2010 3:30 PM
  • Hi, Thanks a lot for your help. I've read the link but msdn sources of NDIS interface drivers are not clear sufficiently for me (newbie for Windows Embedded CE 6.0). Can I say that Device manager implements the loading drivers during boot-time as the following: If there is a registry sub-key for a driver in the HKLM\Drivers\BuiltIn, Device Manager initalizes the loading process according to having the user or kernel mode driver (Reflector service is used for user mode drivers like a proxy). But in my scenario, NDIS Wi-Fi driver does not have a sub-key there. During boot time, Device Manager also scans the key HKLM\Comm for NDIS drivers in order to succeed the loading communications drivers. Is it true? Thanks in advance for your clarifications,
    Tuesday, November 2, 2010 3:46 PM
  • Which is the interface for the adapter? You're talking about PnP so I imagine it's CF or PCMCIA. Take a look at http://msdn.microsoft.com/en-us/library/ee482460.aspx  also.
    As a reference, look at the registry entries for  PCMCIA NE2000 network adapter and PCMCIA AR6K Wifi in %_WINCEROOT%\PUBLIC\COMMON\OAK\FILES\common.reg

    --
    Luca Calligaris (MVP-Windows Embedded)
    lucaDOTcalligarisATeurotechDOTcom
    www.eurotech.com
     
     
    "yaseminyilmaz" <=?utf-8?B?eWFzZW1pbnlpbG1heg==?=> ha scritto nel messaggio news:43186c21-6207-4dd3-a52f-060a7d153dee...
    Hi, Thanks a lot for your help. I've read the link but msdn sources of NDIS interface drivers are not clear sufficiently for me (newbie for Windows Embedded CE 6.0). Can I say that Device manager implements the loading drivers during boot-time as the following: If there is a registry sub-key for a driver in the HKLM\Drivers\BuiltIn, Device Manager initalizes the loading process according to having the user or kernel mode driver (Reflector service is used for user mode drivers like a proxy). But in my scenario, NDIS Wi-Fi driver does not have a sub-key there. During boot time, Device Manager also scans the key HKLM\Comm for NDIS drivers in order to succeed the loading communications drivers. Is it true? Thanks in advance for your clarifications,

    Luca Calligaris (MVP-Windows Embedded) lucaDOTcalligarisATeurotechDOTcom www.eurotech.com
    Wednesday, November 3, 2010 10:56 AM