I have an application where I am using an auxiliary PCI
dual serial port card. When first plug card in and start
W2K (service pack 4), the card is recognized and all works
fine. When I power down, then re-start, one of the com
ports does not work.
If I run WINMSD, the com port is reported to be busy,
although there are no other applications running that
would use the port. Device manager shows that the port is
functioning and there are no conflicts. Looking at the
task manager, there seems to be nothing out of the
ordinary that may assume control of the port.
Is there some utility or API call that would tell me
exactly what it is that has "control" of the COM port?
Thanks for the help.

Check out Process Explorer from www.sysinternals.com. It allows you to
search on which processes have which handles open.

--
John Phillips
MVP - Windows SDK



"Phil" <(E-Mail Removed)> wrote in message
news:513201c4912a$ca01b520$(E-Mail Removed)...
> I have an application where I am using an auxiliary PCI
> dual serial port card. When first plug card in and start
> W2K (service pack 4), the card is recognized and all works
> fine. When I power down, then re-start, one of the com
> ports does not work.
> If I run WINMSD, the com port is reported to be busy,
> although there are no other applications running that
> would use the port. Device manager shows that the port is
> functioning and there are no conflicts. Looking at the
> task manager, there seems to be nothing out of the
> ordinary that may assume control of the port.
> Is there some utility or API call that would tell me
> exactly what it is that has "control" of the COM port?
> Thanks for the help.