Mike
As I said before, it's a custom device. It only offers the serial port profile (again, as stated before, this works fine under WIDCOMM).
I will run the bluetooth discovery demo on the machines and let you know the results. In the mean-time, can you say what you mean by 'make sure that there is no parallel calls to toshiba stack'? My application manages two message loops, one which handles the device connection, and one which handles a continuous discovery process. During the connection to the device, the discovery process is terminated, and resumes afterwards (again this works fine on WIDCOMM). Could that be a source of problems?
At the end of the day, I need to try and create a reliable connection to these custom devices using various stacks, so any help you can give me in achieving that goal is much appreciated.
Also - do you have any documentation that can be read in order to find out these things like 'make sure there are no parallel calls to toshiba stack'? It's kind of natural to assume that WCL would handle these restrictions internally, seeing as it is a library. But it doesn't handle message loop creation etc, so is there defined somewhere a list of DOs and DONTs?
Thanks again for your help
Matt
