NDIS? winsock?..plspls help..., anyone familiar with these?
i gotta get my bluetooth connected to the network layer before 19th feb...oh gosh...really dunno whether i would be able to finsh this or not.. found some info tht mentioned writing a bluetooth driver does not need any miniport or MDIS driver, instead, the msdn is giving me advice on winsock programming..i'm not familiar with these commands... only manage to find these...
btw, my bluetooth can acutlally talk with another bluetooth, i.e. both bluetooth can communicates with each other, but, windows is unaware of the activity going on. thus, the windows cant detect the bluetooth attach tothe system but both bluetooth are able to have basic messagin in command windows, when i executed a programme in visual studio..thus, i gotta connect this prog to the network layer, which i believe, i would need a NDIS (network intermediate programme) to do tht job but reading thry the winsock i doubt thts the right way.. pls help..
note tht i've got SDP n device discovered all done..
any help would be great..
[quote]
Bluetooth on Windows provides core services similar to those exposed by Transmission Control Protocol (the TCP part of TCP/IP). Like many networking protocols and services, Bluetooth connectivity and data transfer are programmed through Windows Sockets function calls, using common sockets programming techniques and specific Bluetooth extensions. However, since significant differences exist between a wired, fixed network and a wireless ad-hoc network, Bluetooth provides extensions such as service/device discovery and notification that enable applications to operate properly in the wireless environment. These extensions also pave the way for simple porting to similar technologies, such as IrDA, or future wireless transports.
There are two primary Bluetooth programming approaches for Windows: programming with the Windows Sockets interface, and managing devices directly with non-sockets Bluetooth interfaces.
Bluetooth provides programming definitions in the Ws2bth.h and BluetoothAPIs.h files. The Ws2bth.h file must be included after Winsock2.h to use Bluetooth sockets.
As with all Windows Sockets application programming, the WSAStartup function must be called to initiate Windows Sockets functionality and enable Bluetooth.
All standard synchronous and overlapped mechanisms to read and write data currently supported with other address families operate properly with the AF_BTH address family.
|
Linear Mode
