The bitmap itself is not to be touched directly, use the ComDB APIs to
guarantee synchronized results.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michael Jones
Sent: Friday, September 02, 2005 6:10 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Multi-port serial adapter enumeration problem
(1) It is in the DDK src tree under setup\pnpports. Note the calls are
ComDB calls. After you make these calls see how it uses
…\CurrenControlSet\Control\COM Name Arbiter. This is a bitmap mask
where
each inuse port is a bit.
Sincerely;
Mike Jones
“Doron Holan” wrote in message
news:xxxxx@ntdev…
There is a stripped down version of msports.dll in the DDK that
demonstrates
the use of these APIs. You will need to modify the class installer code
to
be a device co installer and dealy with post installation processing,
but
the basic framework is there.
d
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Linus Fones Kwok
Huan
Sent: Thursday, September 01, 2005 2:34 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Multi-port serial adapter enumeration problem
Importance: High
Hi Doron,
Do you have a sample device coinstaller that uses the ComDBxx calls in
msports.dll or is there some documents on MSDN I can read?
Regards
Linus
xxxxx@lists.osr.com wrote: -----
To: “Windows System Software Devs Interest List”
From: “Doron Holan”
Sent by: xxxxx@lists.osr.com
Date: 09/02/2005 12:06AM
Subject: RE: [ntdev] Multi-port serial adapter enumeration problem
The ports class isntaller will give you a com port number per enumerated
device. You HAVE to use the number the ports class installer gives,
otherwise you can try to claim a number that is already used and then
both
devices will stomp on each other. You can write a device coinstaller
that
does post install processing that uses the com name DB (see ComDBXxx
calls
in msports.dll) to relese the number assigned to you and to try to claim
the
right number.
d
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Linus Fones Kwok
Huan
Sent: Thursday, September 01, 2005 8:49 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Multi-port serial adapter enumeration problem
Importance: High
Hi Doron,
The multi-port serial adapter I mentioned in my email is a USB->3serial
port
device.
It is the requirements of my customer to fix the 3 virtual COM ports as
COM4, COM8 and COM9. COM1 to 3 and 5 to 7 are real COM ports. What is
the
best way to fix the
virtual COM ports as COM4, COM8 and COM9. I tried fixing the virtual COM
ports by hard coding it within the VCOM driver. I am able to access
COM4,
COM8 and COM9 using Windows Hyperterminal, but they appear as COM4,
COM11
and COM12 in the device manager. I don’t know what is causing the
differences in the naming of the COM ports between Windows Hyperterminal
and
Device Manager.
Regards
Linus
xxxxx@lists.osr.com wrote: -----
To: “Windows System Software Devs Interest List”
From: “Doron Holan”
Sent by: xxxxx@lists.osr.com
Date: 09/01/2005 10:42PM
Subject: RE: [ntdev] Multi-port serial adapter enumeration problem
Hyperterminal only can open com 1-9 which is why you don’t see 11 and
12. have you ever disabled/enabled the MPS adapter? Do you have other
devices (like built in motherboard devices or USB->Serial devices) which
also have COM names?
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Linus Fones Kwok
Huan
Sent: Thursday, September 01, 2005 5:14 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Multi-port serial adapter enumeration problem
Hi Everyone,
I have a multi-port serial adapter that does not enumerate properly
under
the Windows Device Manager.
I see COMs 1, 2, 3, 4, 5, 6, 7, 11 and 12 under the Ports(COM & LPT)
section in the Device Manager Windows. COMs 8 and 9 are missing.
However, when I open up Windows Hyperterminal I see COMs
1,2,3,4,5,6,7,8,9.
There is no COM 11 and 12.
On different machines the COM ports are enumerated differently under the
Device Manager view, some numbers are missing here and there.
For Windows Hyperterminal, the same number of COM ports will appear, but
there won’t be any missing numbers in between.
Does anyone know what is the problem? Is there a way to synchronize the
names of COM ports that show up in the Device Manager with the names
that
appear in Windows Hyperterminal?
Regards
Linus
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256You are currently subscribed
to
ntdev as: unknown lmsubst tag argument: ‘’ To unsubscribe send a blank
email
to xxxxx@lists.osr.com
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com
— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 You are currently subscribed
to
ntdev as: unknown lmsubst tag argument: ‘’ To unsubscribe send a blank
email
to xxxxx@lists.osr.com
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com