Problem with XP com port

[Sushil Kumar Gehi]

Dear All,
we have Two applications with talks to two other application via the serial
port.
the application are configured to talk on com1 and com 2
in the earlier scenario the computers we used had 2 ports on board.
but off late we have computers with one port on the mother board.
hence we have to add a add on port card.
with this the ports that are recognized are 2 and 3.
since we have our application configured to talk on 1 and 2 we go to the
hardware settings and change the nos of the ports on the port card to 1 and
2 . and the port on the mother board as 3.
and when we run the application in this scenario we have been experiencing a
rather strange behaviour.
at times the application works fine.
but when we shut the application or the application crashes for some reason.
and we restart the application it is not able to sense the com port. and
hence the communication doesnt happen.

is this the problem with XP or the microsoft comm control. the application
is built on visual basic and uses microsoft comm control.






--


Regards,
Sushil

"What the caterpillar calls the end of the world, The master calls it the
butter fly"


Richard Bach

 

[Michael Cecil]

Dear All,
we have Two applications with talks to two other application via the serial
port.
the application are configured to talk on com1 and com 2
in the earlier scenario the computers we used had 2 ports on board.
but off late we have computers with one port on the mother board.
hence we have to add a add on port card.
with this the ports that are recognized are 2 and 3.
since we have our application configured to talk on 1 and 2 we go to the
hardware settings and change the nos of the ports on the port card to 1 and
2 . and the port on the mother board as 3.
and when we run the application in this scenario we have been experiencing a
rather strange behaviour.
at times the application works fine.
but when we shut the application or the application crashes for some reason.
and we restart the application it is not able to sense the com port. and
hence the communication doesnt happen.

is this the problem with XP or the microsoft comm control. the application
is built on visual basic and uses microsoft comm control.

That might be similar to a situation I came across last month. A company
is using an old program to sense gate openings via a sensor hooked to the
serial port. However, when you reboot the computer it doesn't work. It
requires going into the device manager, disabling, then re-enabling the
serial port to work. Just scanning for hardware changes (like you might
do to pick up an external modem that you've turned on after boot) doesn't
work. Various /fastdetect and the older NT4 /noserialmice boot.ini
switches don't help. There is even an command line program available from
MS to do device detection but it didn't help either. Never did figure out
a way to make XP gracefully work without doing the disable/reenable bit.