home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!news.service.uci.edu!ttinews!soldev!moss
- From: moss@soldev.TTI.COM (Les Moss)
- Subject: Re: Serial Communications and Windows ?
- Message-ID: <1992Nov24.015112.8098@ttinews.tti.com>
- Sender: usenet@ttinews.tti.com (Usenet Admin)
- Nntp-Posting-Host: soldev.tti.com
- Reply-To: moss@soldev.TTI.COM (Les Moss)
- Organization: Citicorp/TTI
- References: <20NOV92.17743545.0023@VM.MPG.MCGILL.CA>
- Date: Tue, 24 Nov 1992 01:51:12 GMT
- Lines: 9
-
- You don't need the interrupt srvicing and buffering stuff from
- your DOS program. The Windows Comm API takes care of all this.
- Just process the data using ReadComm when it is available (based
- on a WM_TIMER, or the new 3.1 notification message.)
-
- Les Moss moss@tti.com
- Citicorp TTI
- 3100 Ocean Park Blvd. (310) 450-9111, ext. 2982
- Santa Monica, CA 90405
-