X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: David Bolen Newsgroups: comp.os.msdos.djgpp Subject: Re: serial port interaction Date: 30 Dec 2004 14:16:24 -0500 Organization: Fitlinxx, Inc. - Stamford, CT Lines: 36 Sender: db3l AT CTWD0222 Message-ID: References: <01c4ee2d$Blat.v2.2.2$e31bb780 AT zahav DOT net DOT il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net VRPexEqOiQt07ecMFSt+Owv+iyYNBDVWjn8+MFapyNrtpPxEpQ User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Eli Zaretskii" writes: > > From: David Bolen > > Date: 29 Dec 2004 14:46:25 -0500 > > > > We use pmcom for our serial handling and find it works very nicely. > > Unless you use something like this, the odds are very good that you'll > > lose serial data since BIOS won't buffer any information but must be > > polled to ensure you receive all data. While it doesn't directly > > integrate into the filesystem layer in DJGPP, by and large > > COMPortOpen, COMWriteBuffer and COMReadBuffer are pretty easy > > replacements for open(), write() and read(). > > One could integrate pmcom into the filesystem layer by using the DJGPP > Filesystem Extensions feature (it is described in the library > reference manual). Then you could simply use `open', `read', and > `write'. Right - I wasn't saying it couldn't be done, just pointing out that the current pmcom library didn't make use of that facility (as opposed to, for example, wattcp32). > > You may be getting compilation errors due to some older preprocessor > > string concatenation stuff that was in the source (at least in the 1.0 > > version we use). In our case it was fixable by editing com.c and > > replacing instances of "##x" with just "x" (not including quotation > > marks) > > Perhaps a fixed version of pmcom could be uploaded to the DJGPP FTP > site. If I recall back when we did this we found some references to a 1.1 beta that was available by request, so figured this would be handled subsequently. Not sure where that stands currently. -- David