Ahh, but were you USING DOS [API services] for perfoming the Serial I/O or
were you bypassing it and going to a lower [BIOS or Hardware] level......
That is the crux.....
DOS did NOT work well (IIRC and others seem to agree) for serial I/O
DOS was NOT a protected OS and allowed direct access to lower layers..
Therefore you could write good serial IO on a machine that was RUNNING dos,
but you could NOT write high performace routines USING dos.....
>> -----Original Message-----
>> From: cctalk-bounces(a)classiccmp.org
>> [mailto:cctalk-bounces@classiccmp.org] On Behalf Of Vintage
>> Computer Festival
>> Sent: Tuesday, August 03, 2004 2:04 AM
>> To: General Discussion: On-Topic and Off-Topic Posts
>> Subject: Re: Electronics Barn closing
>>
>> On Mon, 2 Aug 2004, ben franchuk wrote:
>>
>> > Joseph S. Barrera III wrote:
>> >
>> > > Don't be silly. Of course DOS has interrupt handling. See e.g.
>> > > <http://webster.cs.ucr.edu/AoA/DOS/ch17/CH17-4.html>
>> >
>> >
>> > Well I guess you have never used a SERIAL PORT under DOS!
>> > Can we say 300 BAUD!
>> > Grumpy PROGRAMER!
>>
>> I designed a state-machine based application that handled 3
>> serial ports (mutli-port serial card sharing on interrupt)
>> simultaneously downloading data files at up to 19.2Kbps per channel.
>>
>> I also designed a system that used 2 standard COM ports
>> simultaneously:
>> one for remote access and one for transferring data.
>> Worked fine at up to 19.2Kbps (the fastest cheap modems of
>> the day, e.g. USR Sportsters).
>>
>> Under MS-DOS 6.22.
>>
>> So I have no idea what you're talking about really :/
>>
>> --
>>
>> Sellam Ismail
>> Vintage Computer Festival
>> ------------------------------------------------------------
>> ------------------
>> International Man of Intrigue and Danger
>>
http://www.vintage.org
>>
>> [ Old computing resources for business || Buy/Sell/Trade
>> Vintage Computers ]
>> [ and academia at
www.VintageTech.com || at
>>
http://marketplace.vintage.org ]
>>