 |
|
|
|
Topic: Windows friendly name
|
| By: Reinhard | Posted on: Jul 22 2011 at 10:39:21 AM | Hi, support team
I tried to use the Comm32 functions to tell which of the available COM ports is the right one to be opened.
But even if the Windows Device Manager displays a very specific string like "Dell Wireless 5530 HSPA Mobile Broadband Minicard (COM5)" the "Comm32.InstalledDrivers" function (and also the "Comm32.DeviceName"function) often returns just a generic string like "Communications Port (COM5)".
Is there a way to get the more descriptive "Windows Device Manager" name using Comm32?
Greetings from Germany!
Reinhard
| |
| By: Support | Posted on: Jul 22 2011 at 08:02:11 PM | Are you using Windows 7 ?
We've found that with Windpws 7 we often get that rather generic name even for simple USB adapters. On XP, for the exact same device, we get the proper friendly name.
So it looks as though MS have moved some of the data.
We do intend to revisit this problem especially for windows 7. Hopefully we can fix it soon. | |
| By: Reinhard | Posted on: Aug 3 2011 at 02:27:13 PM | Hi,
I tried on various windows systems. There is no difference between XP and "7", as far as I see. It seems to depend on the specific driver used.
The one driver we have certified by Microsoft is recognized with its Windows friendly name, the other one (not certified) is just shown as "Communication Port (COMn)". The .DeviceName function matches in all cases the .InstalledDriver result.
Is it possible that the certification makes such a difference? | |
| By: Support | Posted on: Aug 3 2011 at 05:24:52 PM | There's a proper place where such information should be stored in the OS and most device drivers do store it there and maybe MS certification confirms that the data is stored in its proper place.
But in an uncertified driver I suppose they could store it differently and we don't look hard enough in alternate locations.
Please send me an eMail - I'd like to send you an updated version of the ocx
support at comm32.com
| |
| By: Support | Posted on: Aug 12 2011 at 08:15:54 AM | Most recent version of the OCX improves the detection of windows friendly name of com ports
Version 3.2.0.120 | |
|
