Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mintaka!yale!think.com!sdd.hp.com!elroy.jpl.nasa.gov!jarthur!uunet!munnari.oz.au!csource!david
From: david@csource.oz.au (david nugent)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: null modem cable
Message-ID: <881@csource.oz.au>
Date: 30 Jan 91 04:36:43 GMT
References: <3439@nosc.NOSC.MIL>, <s1Vew1w163w@cybrspc> <EbdHzzm00W458_qgUK@andrew.cmu.edu>
Organization: Unique Computing Pty Ltd, Melb, Aust.
Lines: 15

jc58+@andrew.cmu.edu (Johnny J. Chin) writes:

> Excerpts From Captions of netnews.comp.sys.ibm.pc.hardware:
> 27-Jan-91  Re: null modem cable Roy M. Silvernail@cs.umn (1242)   
> >If faking the handshake really is "never a good move", why did LapLink
> >do it?

> Laplink does it in order to avoid hardware control problems when you have
> serial ports on different speed computers talk to each other.  A 386 talking
> to an 8088 will definitely have different handshaking signal timings.  That
> is why data is checked via software with Laplink.


Err, what has this to do with hardware timings?  Hardware signals are
controlled by software and are not intrinsic to the hardware itself.