Windows 7 Download periodically updates pricing and information of Wise Telnet & Serial Terminal free download from the publisher, but some information may be out-of-date. Using cracks, warez serial numbers, registration codes or keygens for Wise Telnet & Serial Terminal license key is illegal.

Hi, I have a serial communications application I develop which is not currently detecting COM ports that are created as part of the 'Standard Serial over Bluetooth Link'. The opeating system I am using is Windows 7 Professional 32-bit. The device pairs and the COM port (in this case COM9) shows up in device manager but does not enumerate. My application checks to see if the port exists with GetDefaultComConfigA, tested for each serial port within a user-provided range. This returns 0 for COM9, with ERROR_INVALID_PARAMETER (which is the same all other ports that do not appear to exist on the machine). Of additional note, my application also enumerates available driver ports via EnumPorts. The list of ports returned by this function explicitly skips COM9, showing both COM7 and COM10 (both of which do not actually exist, but this is standard for EnumPorts).

Additionally, a CreateFile on the COM port directly fails. This seems like it might be a security issue, but GetDefafultComConfig has no recomended replacement and takes no security information. Can anyone lend some insight? If the user's operation fails ask the user to choose another one. The port mapping is device-dependent. There is no API or SDK from Microsoft to tell which COM port is simulated by a device driver.

You need to get the device's SDK from the driver developer, if there is one. The following is signature, not part of post Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.