X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Recieved: from localhost (localhost [127.0.0.1])
From: John Wright <john AT wacontrols DOT com>
Organization: WAC
Date: Tue, 22 Feb 2011 11:01:16 -0600
User-Agent: KMail/1.13.5 (Linux/2.6.32-28-generic; KDE/4.4.5; i686; ; )
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Serial I/O Programming with DJGPP - (need good examples to start with)
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201102221101.16553.john@wacontrols.com>
Reply-To: john AT wacontrols DOT com

I'm looking for some complete code examples using PCOM, DZCOM or SVASYNC 
routines. Which ever anyone might have or recommend. I have several books that 
I have been studying, and they all have good examples, but everything is based 
on MSC 6.0 or Turbo C++. 

Anyway, I have this book by Mark Goodwin which maybe someone is familiar with, 
"Serial Communications In C and C++". He shows you how to build a toolkit from 
start to finish in this book. It comes with all the source code and pre 
compiled binaries produced from his source. I think Goodwin's source is the 
foundation I am looking for, but I need to port it to DJGPP so I can expand on 
it from there. I am not foreign to C programming, but I would certainly 
consider myself to be a competent beginner. So one question is..., how hard or 
easy will it be for me to port Goodwin's examples to DJGPP? 
I'm not familiar with Turbo C or gcc compiler directives, so I really have 
nothing to compare with. If I can get the toolkit examples compiled, I think 
that will give me jump start into my project. I have always wanted to learn 
how to talk to the UART, so I figure at the end of this 
journey I will have learned a lot about DJGPP and what takes to compile 
foreign sources.

Any examples or recommendations would be appreciated. In the meantime, I will 
just go for it and see what happens. I have no problem cleaning things up in a 
step-wise fashion. I'm just wondering how bad it will be? The application 
front end that I would like to create will need direct, dial-up, and serial 
over IP connections. The PLC that I am developing for has three RS-232 ports 
and a IP/serial bridge on board.  The old 16 bit Windows application has no 
built-in IP support, so I use a serial wedge (e.g. HW-VSP) to communicate over 
the Internet.

Sorry so long, but I hope a little background helps explain my goals. I'll be 
glad to provide more if needed.

-jw