Article View: comp.os.msdos.programmer
Article #4723DOS Comm Driver?
From: Jack Cloninger
Date: Mon, 18 Feb 1991 22:17
Date: Mon, 18 Feb 1991 22:17
10 lines
917 bytes
917 bytes
We are looking for a communications driver to replace the standard BIOS driver. The intention is to improve the speed on a particular machine that has a poor built-in driver. Thanks for any info. Jack -- Jack Cloninger, TeqSoft, 112 US Highway 1, Tequesta, FL 33469 B-) jmc%teqsoft@domain.com OR ...uunet!comtst!teqsoft!jmc Phone: 407-747-7163 Fax: 407-747-0354 Disclaimer: I speak for myself, not my company, and offer opinion, not fact.
Technical Details
Message-ID:
<42@teqsoft.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!comtst!teqsoft!jmcShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!comtst!teqsoft!jmc From: jmc@teqsoft.UUCP (Jack Cloninger) Newsgroups: comp.os.msdos.programmer,comp.os.msdos.misc Subject: DOS Comm Driver? Keywords: dos, msdos, communications Message-ID: <42@teqsoft.UUCP> Date: 18 Feb 91 22:17:56 GMT Followup-To: poster Organization: TeqSoft, 112 N Highway 1, Tequesta, FL 33469 (407-747-7163): Document Processing Lines: 10