Async32 works fine if you're happy to work directly with the data.
Max
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Grant Black
Sent: Monday, 8 March 1999 16:41
To: Multiple recipients of list delphi
Subject: RE: [DUG]: Serial Comms / Ope
Just my penny worth. I have always used freeware Comdrv32 (old url was
http://www.mdlive.com/d3k/
)
Works well, is easy to impliment. If u cant get it, give me a yell and I'll
email it to you.
Could never understand why Borland refused to include com driver routines in
any of their codes from C
SmartMove (NZ) Ltd
Phone: +64 9 361-0219 extn 719
Fax : +64 9 361-0211
Email: [EMAIL PROTECTED]
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 08, 1999 3:46 PM
> To: '[EMAIL PROTECTED]'
> Subject:
Your best solution is to chuck all the old stuff, and invest in Asynch Pro. You will
waste an enormous amount of effort getting your own comms going, and Asynch covers
everything you could ever want, and even more, it does it 100% reliably.
Save yourself a bunch of $ and buy into AsynchPro.
Th
-
From: Grant Black [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 08, 1999 2:56 PM
To: Multiple recipients of list delphi
Subject: [DUG]: Serial Comms / OpenComm functions
I am looking at porting a Delphi 1 app to Delphi 4. I have it all
ported except for a serial component that is embedded fairly
I am looking at porting a Delphi 1 app to Delphi 4. I have it all
ported except for a serial component that is embedded fairly extensively
in the app.
The component is TMSComm by Jeff Atwood which is a fairly simple wrapper
around the MSComm control. I have not been successful in tracking down
