> Hmm. That's odd. What about if you quit and restart your app? If I quit and restart the app without unplugging the serial device, it doesn't work either. Seems that something is still tying it up...well most of the time anyways, happens about 90% of the time. The other 10%, I have no clue what's going on.
Another odd thing I noticed is that if I set the port say, in the preferences (using a popupmenu to list all available ports, then set it); then run my routine to talk with it, it works the first time as mentioned. At this point in the debugger, the serial object will list the correct inputDriverName as expected. But... On subsequent runs, I usually get a StackOverflowException, and upon checking the InputDriverName in the debugger, it's set to a different driver. I'm triple-checked my code to make sure I'm not changing anything in there, and on my end, there are no changes to the port or anything else. Somehow it's changing around the port that it's connected to (which is what returns a ton of garbage from some other random driver that it connects to causing the overflow exception). Is there something that would cause the ports to rearrange themselves or their indexes automatically (nothing has been plugged/unplugged)? Thanks again for the help. Chad _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
