Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!know!news.cs.indiana.edu!msi.umn.edu!cs.umn.edu!cybrspc!roy From: roy%cybrspc@cs.umn.edu (Roy M. Silvernail) Newsgroups: comp.sys.ibm.pc.hardware Subject: Re: null modem cable Message-ID: Date: 27 Jan 91 02:42:03 GMT References: <3439@nosc.NOSC.MIL> Organization: Villa CyberSpace, Minneapolis, MN Lines: 27 koziarz@halibut.nosc.mil (Walter A. Koziarz) writes: > In article <8Fy4V2w163w@cybrspc> roy%cybrspc@cs.umn.edu (Roy M. Silvernail) w > >Here's a design that emulates a LapLink cable. I've used it with great > > It's never a good move to try to 'fake-out' hardware handshaking!!!!! Don't > it!! Presented below is *the RIGHT way* to make a null modem cable -- [both designs deleted] OK, I have filed your design along with mine. However, I'd suggest (if you're going to be fanatic about it) building _both_ versions. In my case, I used the null-modem to talk with a non-PC machine, and the software on the other end didn't speak hardware handshaking. In this instance, your design would fail to function, while mine would pass the data. > This is the correct wat to make a FULL-HANDSHAKING null modem; throw away > ANYTHING that tells you to use the 'other', fake-out connection. If faking the handshake really is "never a good move", why did LapLink do it? -- Roy M. Silvernail -- roy%cybrspc@cs.umn.edu - OR- cybrspc!roy@cs.umn.edu Department of redundancy department, or "Take the long way home...": main(){system("perl -e '$x = 1/50; print \"Still just my \\$$x!\n\"'");} [new year, new .sig, same ol' cyberspace]