My company has developed a Bluetooth product that uses the serial port profile via a virtual COM port. In Windows XP (as well as Vista), the 'Bluetooth Devices' dialog box shows, after pairing, the COM port assignments for both 'incoming' and 'outgoing' COM ports. Our product uses the 'incoming' COM port, since it autonomously initiates a commuincation. This works fine in XP and Vista. However, in testing with Windows 7, we have discovered that the Bluetooth pairing utility is now different from the one used in XP... we can get it to work, but the process reports back only one virtual COM port number, which we have discovered empirically is actually the outgoing port, not the incoming port. Normally, Windows XP assigns the outgoing port first, and then assigns the next ordinal port number to the incoming port... although we know, from experience, that this isn't always the case. For example, when pairing with Windows 7, we see that COM port 7 is assigned. In testing, we find that COM port 8 is actually the incoming port... but we can't depend on that... sometimes, the two port numbers are not sequential What I am looking for is a way to determine, programmatically, what incoming port was assigned as a result of the pairing process. I am assuming that somewhere, there is an API which would permit us to determine what ports are assigned to what devices, by name. For example, our device uses a name like 'DF2D-A34F'... how can I determine, from knowing the name, what incoming and outgoing ports are assigned to it? Is there an API which will list the ports? Can it be determined from a registry key? (I haven't found one, by searching, yet...) Any help on this would be appreciated.

Hi, If you have any trouble on developing device driver, please post your thread at Windows WDK and Driver Development Forum.