Author |
Topic: Identifying a particular COM port (Read 1829 times) |
|
movr0r0
New Member
member is offline
Posts: 7
|
 |
Re: Identifying a particular COM port
« Reply #3 on: Dec 28th, 2014, 10:40am » |
|
Hi Richard,
This Win32_SerialPort WMI class support with your code example above works well to enumerate "COMx" ports and getting their actual number 'x', using the "DeviceID" Property.
However, although everything is fine with Win7 (and I guess 8), when using this method on WinXP, enumeration stops at the first available port, without error.
On-line MSDN doc appears to relate only to Vista onwards, and obviously there is no more hint about description or changes of the XP version of this class.
Any idea on how to make it fully work on XP too?
Thanks,
R.
|
|
 Logged
|
|
|
|
rtr2
Guest
|
|
Re: Identifying a particular COM port
« Reply #4 on: Dec 28th, 2014, 12:06pm » |
|
on Dec 28th, 2014, 10:40am, movr0r0 wrote:| Any idea on how to make it fully work on XP too? |
|
I fear that if you can't make the WMI method work you will have to fall back to reading the Registry. Do you really need to support XP, given its age and status?
Richard.
|
|
Logged
|
|
|
|
movr0r0
New Member
member is offline
Posts: 7
|
|
Re: Identifying a particular COM port
« Reply #5 on: Dec 28th, 2014, 3:32pm » |
|
Many thanks for your quick reply, Richard!
Supporting XP would be nice; I still have a couple of old laptops -- with real serial ports  -- that prefer this aging version...
What's the best way to get Windows version from within bb4w?
R.
|
|
Logged
|
|
|
|
movr0r0
New Member
member is offline
Posts: 7
|
|
Re: Identifying a particular COM port
« Reply #7 on: Dec 28th, 2014, 5:45pm » |
|
Many thanks again for your great help, Richard.
R.
|
|
Logged
|
|
|
|
movr0r0
New Member
member is offline
Posts: 7
|
|
Re: Identifying a particular COM port
« Reply #8 on: Jan 20th, 2015, 09:59am » |
|
Hi!
It looks like Windows Win32_SerialPort WMI class miserably fails to detect and list most of virtual serial ports (e.g. over an Ethernet link, such as Tibbo), and more annoyingly USB-to-serial adapters, such as ATEN or Prolific.
Any idea about which method could be used to let Windows (and BBCBasic) nicely list what is reported in the "COM ports and LPT" section of the Device Manager?
Thanks,
R.
|
|
Logged
|
|
|
|
rtr2
Guest
|
|
Re: Identifying a particular COM port
« Reply #9 on: Jan 20th, 2015, 12:46pm » |
|
on Jan 20th, 2015, 09:59am, movr0r0 wrote:| It looks like Windows Win32_SerialPort WMI class miserably fails to detect and list most of virtual serial ports |
|
I don't think you should blame Windows, it's more likely that some 'virtual' serial ports fail to follow the rules when they install themselves. After all, you can pretty much guarantee that all serial ports on a modern PC are 'virtual' so it would be daft if WMI never worked.
Quote:| Any idea about which method could be used to let Windows (and BBCBasic) nicely list what is reported in the "COM ports and LPT" section of the Device Manager? |
|
I answered that before: "I fear that if you can't make the WMI method work you will have to fall back to reading the Registry". But you would be entirely justified in using WMI and simply saying that your software is incompatible with 'non-conforming' virtual port drivers.
Richard.
|
|
Logged
|
|
|
|
|
