> as I know there is no Windows stack that provides full access to the HCI
> layer as BlueZ do. Actually it must be possible in some kind of way, but
> in most cases you have to pay for their development kit.
The COM1 stack used to allow direct HCI access (H4 interface) if opening as
a serial port the special file declared in
HKLM\SYSTEM\CurrentControlSet\Enum\USB\Vid_xxxx&Pid_xxxx\something_goes_here
\Device Parameters\SymbolicName
(replace Vid_xxxx&Pid_xxxx with the ones from your device)
You can download their drivers from their website et make it work with your
dongle by editing the .inf file to add YOUR dongle vid&pid.
Just kill their btstack and write your own...
It's surely not usable for commercial products but it works for
testing/development purposes ... I used it to create some demos but am now
working with widcomm SDK which gives acces to all levels of the stack
beginning from l2cap (or HCI vendor commands)
Hope it helps.
I did reply to the list because there are often questions about
bluetooth/windows here ...
BR,
--
Xavier Garreau <[email protected]>
Prim'Time Technology
http://www.prim-time.fr/