![]() ![]() Microsoft and the Window logo are trademarks of Microsoft Corporation in the U.S. Alexa and all related logos are trademarks of, Inc. App Store is a service mark of Apple Inc. Mac, iPhone, iPad, Apple and the Apple logo are trademarks of Apple Inc., registered in the U.S. Android, Google Chrome, Google Play and the Google Play logo are trademarks of Google, LLC. Firefox is a trademark of Mozilla Foundation. or its affiliates in the United States and other countries. ![]() NortonLifeLock, the NortonLifeLock Logo, the Checkmark Logo, Norton, LifeLock, and the LockMan Logo are trademarks or registered trademarks of NortonLifeLock Inc. LifeLock identity theft protection is not available in all countries. If the WAN miniport driver supports connections through TAPI, the driver should also include Ndistapi.h.The Norton and LifeLock Brands are part of NortonLifeLock Inc. C_DEFINES=-DNDIS_TAPI_CURRENT_VERSION=0x00030000įor WAN miniport drivers, the include paths should include Ndiswan.h as well as Ndis.h. If you are writing a CoNDIS WAN miniport driver that is an integrated miniport call manager (MCM) and that supports the CoNDIS address family type CO_ADDRESS_FAMILY_TAPI_PROXY, you must add the following line to your sources file before building to identify the TAPI version that your driver supports. If you are writing an NDIS WAN miniport driver that supports connections through TAPI, you must add the following line to your Sources file before building to identify the TAPI version that your driver supports. This topics provides some information about defining build parameters for NDIS and CoNDIS WAN miniport drivers.Īdd the following line to your Sources file before building to identify your driver as a miniport driver. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |