![]() ![]() I'm going to restart to see if its magically "fixed" or if fiddling around in the registry actually did it. Before, I clicked on the devices icon in bluetooth "devices" and added another serial port, I assume one can add as many as you wish, and this seems to work, despite originally displaying the same behavior as the other ports (unable to connect). The others I could open, but that didn't cause the bluetooth device to connect, which should happen. That's when I found this, based on wasyoungonce suggestion: Opening up the registry entries to edit - namely the COM port names - and closing them, I was able to open all the com ports, but only successfully send and receive data on the last one (that I added after pairing). This implies there is something dodgy about the ports labels, perhaps different terminal programs access the com port list from different parts of the registry. In device manager and most of the terminal programs it lists the com ports correctly as COM4 and COM5. The only oddity I found was a couple of terminal programs (I tried about 5) listed the two new com ports created for the bluetooth adapter simply as "COM" with no number. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |