The only time I had real problems with the mscomm control was when I was
porting an app toa japanese version of windows 98 where the double byte
character system ruled (not even unicode - yech!) and it wasn't a
problem with mscomm, just with the string handling routines I was using
(lesson - don't treat binary data as strings - may be convenient, but
will byte you later ;-)).

But I've heard others have headaches with it.  My boss at a previous job
disliked it so much he used a third party tool.

I'll take a peek around sometime for the old code - should be
entertaining to read if nothing else.  Probably not more than a dozen
lines or so.

-Adam

Tim McDonough wrote:

>On Fri, 26 Jul 2002 16:47:57 -0400, M. Adam Davis wrote:
>
>
>>The MSCOMM control does allow individual control of the discrete
>>serial port signals (CTS, RTS, DTR, etc - only outgoing, of course).
>>
>>I know it works - when I needed to listen in on communications
>>between a computer and another device I used two serial ports on a
>>seperate system running a VB program.  It detected and shuttled not
>>only byte information but also the status pins toggling - the device
>>I was using didn't run without proper use of these signals.  You
>>need to tell the control that the communication should have no flow
>>control (as opposed to hardware or xon/xoff) so it doesn't
>>automatically toggle them for you.
>>
>>I probably still have the program and source around here somewhere.
>>Never did get it on my website.
>>
>>
>
>If you run across it I wouldn't mind taking a look. I didn't have any
>luck with MSCOMM when I was starting the project.
>
>Tim
>
>--
>http://www.piclist.com hint: PICList Posts must start with ONE topic:
>[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
>
>
>
>
>
>
>

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads