One popular way to remotely access a PC is through
Windows remote desktop. It works like PC anywhere. I have noticed that using Remote desktop to connect to computer running XP and an async pro fax program can
randomly corupt async pro. What happens is you start getting some wierd read error exceptions. Closing your async pro application does no good. Try/Catch blocks do not capture the error. Running the windows terminal emulation program will allow you to access serial ports so it proves there is a problem with async pro. You have to reboot the computer to clear up the condition. Note that Remote desktop does let you map serial ports. However, I never enable that check box. Something else is that I am not sure how to reproduce the problem all the time.
Has anyone else notices this?
I suspect there is some code in windows that does something when there is a remote desktop connection. Async pro lib code is not looking for this and something causes resources and/or threads to get stuck forvever requiring a reboot.
Kinda a bummer because the video quality of remote desktop is so much better than pcanywhere.