Why does MSComm hang PC on Open?
Further info.
The reason my port is open is that I have address contention between the
modem and the network card. When I start my PC both cards get opened. I
know I can resolve this issue with a fix on the address, but what happens
when (not if) the user hits this and the system hangs?
Does VB have a peek and poke function that can see the "actual" serial port?
Thanks for any suggestions.
Quote:
> I first check the MSComm1.PortOpen for false and then issue the true to
> open/connect to the modem. My system hangs at this point.
> Root cause for this is that my PC connects the modem when I start my PC.
VB
> doesn't recognize the correct status. The system hangs trying to open an
> open modem.
> I remove the error by opening a HyperTerminal session and disconnect the
> modem. I then restart my application and it works correctly. While this
> works for testing, I need a solution that my user can live with.
> Any suggestions?
