在 Windows Embedded CE 6.0 上启动时自动加载 NDIS 驱动程序
我有一个制造商提供的 Wi-Fi 驱动程序。该驱动程序支持即插即用。插入或移除适配器后，Windows CE 已成功识别它。但在启动时，如果适配器处于“插入状态”，CE OS 不会加载它，因此我必须将其移除然后插入。
我想在启动时自动加载驱动程序。是否可以？
之前，我写过一个简单的流接口驱动程序。我编辑了project.reg，在 HKLM\Devices\BuiltIn 下创建一个子项，以便设备管理器可以在启动时自动加载。并且加载成功。但 Wi-Fi 驱动程序是非流驱动程序。设备管理器可以用同样的方式自动加载Wi-Fi驱动吗？
“HKLM\Drivers\BuiltIn 下的所有驱动程序”都是流接口驱动程序吗？从启动时自动加载的角度来看，流接口驱动程序和 NDIS Wi-Fi 驱动程序之间有什么区别？如果您能稍微解释一下，我将非常高兴。
I have a Wi-Fi driver from a manufacturer. That driver has Plug and Play support. After the adapter has been inserted or removed, Windows CE has recognized it successfully. But at boot time, if the adapter is "inserted state", CE OS does not load it so I must remove then insert it.
I want to load the driver automatically during boot time. Is it possible?
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?
Are "all of drivers under HKLM\Drivers\BuiltIn" stream interface drivers? What differences are there between stream interface drivers and NDIS Wi-Fi drivers from the point of loading automatically during boot-time? I will very happy if you can explain it a little.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
是的，这绝对是可能的。这是即插即用设备的主要目的。 WinCE 设备自动加载适合即插即用设备的驱动程序。不需要手动执行此操作。如果是这样，则不需要即插即用功能。
由于您的情况没有发生这种情况，您可以尝试以下操作。
实际上，块设备也可以自动加载，类似于流接口驱动程序。 HKEY_LOCAL_MACHINE\Drivers\BuiltIn 注册表项还可以识别内置块设备。
您可以参考此 msdn 链接，了解有关加载块设备的更多信息。
Yes, it is definitely possible. That was the main purpose of plug and play devices. The WinCE device automatically loads a driver appropriate to the Plug 'n' Play device. There would not be any need for doing it manually. If so, then there is no need for a Plug 'n' Play functionality.
As this is not happening in your case, you could try the following
Actually, the block devices can also be loaded automatically, as similar to stream interface drivers. The HKEY_LOCAL_MACHINE\Drivers\BuiltIn registry key recognizes built-in block devices also.
You can refer this msdn link for further information regarding loading the block devices.