Xref: utzoo comp.sys.att:12327 comp.unix.questions:31777 comp.unix.sysv386:8538 comp.dcom.modems:10082 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!mips!bridge2!jarthur!uunet!lll-winken!abhg!wrangler!ssbn!bill From: bill@ssbn.WLK.COM (Bill Kennedy) Newsgroups: comp.sys.att,comp.unix.questions,comp.unix.sysv386,comp.dcom.modems Subject: Re: Internal Modem and AT&T SV/386 R3.x Message-ID: <2072@ssbn.WLK.COM> Date: 29 May 91 23:57:17 GMT References: <1991May25.004941.26239@mccc.edu> <1991May26.105023.17157@uhura.neoucom.EDU> Reply-To: bill@ssbn.WLK.COM (Bill Kennedy) Followup-To: comp.sys.att Organization: W.L. Kennedy Jr. and Associates, Pipe Creek, TX Lines: 21 :gemini@geminix.in-berlin.de (Uwe Doering) writes: :wtm@uhura.neoucom.EDU (Bill Mayhew) writes: : :>limitation of the asy driver. I'm not an expert at writing :>drivers. I agree that the FAS 2.06 driver that Peter recommends is :>a good idea. I've installed it on my system. I also rigged my : :I think a better idea would be to use FAS 2.08. :-) This is the :latest FAS release. I has lots of speed improvements compared to :FAS 2.06. : : Uwe Sorry to repeat the whole post, but my question doesn't make sense without it. Does FAS 2.08 work on AT&T 3.x? When I tried an earlier version it had a different tty structure and wouldn't bind. I gave up on it and went back to Interactive but maybe I just made some bone headed mistake or 2.08 will work. I was using 2.06 and Vr3.2.2 if memory serves. -- Bill Kennedy internet bill@ssbn.WLK.COM or ssbn!bill@attmail.COM uucp {att,cs.utexas.edu,pyramid!daver}!ssbn.wlk.com!bill