Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/5/84; site chinet.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!chinet!randy From: randy@chinet.UUCP (Randy Suess) Newsgroups: net.micro.att Subject: Re: Continuing ports WARNINGS on 3b2 Message-ID: <155@chinet.UUCP> Date: Sat, 24-Aug-85 10:27:34 EDT Article-I.D.: chinet.155 Posted: Sat Aug 24 10:27:34 1985 Date-Received: Sun, 25-Aug-85 03:31:47 EDT References: <133@wlcrjs.UUCP> <759@pyuxqq.UUCP> Reply-To: randy@chinet.UUCP (Randy Suess) Organization: chinet, Public Access UN*X, Chicago Lines: 26 Keywords: error ports 3b2 ACU Summary: In article <759@pyuxqq.UUCP> pat@pyuxqq.UUCP (Pat M. Iurilli) writes: >The ports on the I/O boards seem to be unsuitable for running ACU's as >well. The problem does not really seem to be in the hardware. It seems to be an incompatibility between uugetty and the Hayes modem. I have added a couple of UDS 212A/d modems as bidirectional ports/ACU's and they are working fine. I stuck a datascope on the port and what seemed to happen was with a Hayes modem on the port, uugetty running, CD (pin 8) held hi, and a call coming in, uugetty sent a garbage character to the Hayes, which caused the Hayes to promptly hang up. This happens with a Hayes 1200B, a ARK 2400 and a USROBOTICS Courier, all Hayes compatible. The UDS modem eats the garbage and keeps on ticking. It is NOT Hayes compatible. I am going to be going with 2400 baud modems with my news feed, so I will have to get the Courier working. I am going to play around with the Dialers file and will let you know what I come up with. I have talked with a person at AT&T hot line, and he indicates that there is a software fix for the ports board hangin up with dtr off, but it is a cost upgrade. This is my personal system, so I guess I will have to pay bucks for AT&T's mistakes.. -- .. that's the biz, sweetheart... Randy Suess chinet - Public Access UN*X (312) 545 7535 (h) (312) 283 0559 (system) ..!ihnp4!chinet!randy