Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!im4u!ut-sally!utah-cs!utah-gr!uplherc!sp7040!jose!pedro!garon From: garon@pedro.UUCP (Garon C. Yoakum) Newsgroups: comp.dcom.modems,comp.unix.questions Subject: Re: Telebit Trailblazer on Microport Message-ID: <127@pedro.UUCP> Date: Wed, 11-Nov-87 02:01:43 EST Article-I.D.: pedro.127 Posted: Wed Nov 11 02:01:43 1987 Date-Received: Sun, 15-Nov-87 20:52:00 EST References: <177@wa3wbu.UUCP> <122@pedro.UUCP> Organization: An As Yet Unnamed Public System Lines: 35 Summary: Telebit TrailBlazer expoeriences with MicroPort V/AT Xref: mnetor comp.dcom.modems:1192 comp.unix.questions:4915 In article <177@wa3wbu.UUCP>, john@wa3wbu.UUCP (John Gayman) writes: > > Is anyone currently using one of the new Telebit Trailblazer modems > successfully with Microport Sys V/AT UNIX ? Curious if this operating > will handle them. > Recently, I have read many articles asking about the Telebit TrailBlazer modem on MicroPort V/AT systems similar to the one above. Following, is a summary of my experience with using the TrailBlazer on MicroPort systems. 1 - Make sure you have modem firmware release 3.0 Without it, a couple of bothersome problems occur. First, if you want high-speed operation, then low speed modems time out before the TrailBlazer gets to their speed. Second, UUCP, XMODEM and other block type transfers have serious time-out problems because the TrailBlazer waits for a full buffer before sending data. 2 - MicroPort V/AT doesn't handle 19.2 connections to the modem very successfully. However, 9600 baud works fine. 3 - MicroPort V.3/386 does handle 19.2 wonderfully. 4 - The TrailBlazer seems succeptable to line noise at 2400 & 1200. Those are the worst things I have experienced with TrailBlazers. Currently, I'm running modem Firmware R3.0 on MicroPort's V.3/386 and have not experienced any problems. The TrailBlazer answers at 2400/1200/300 and then high-speed. Thereby allowing low-speed and high-speed modems to login in without timing out. In addition, it is set up to work with block orientated protocols so it doesn't time out after each block. I welcome other point's of view, and can be reached through USENET or directly at: pedro -> (801) 277-0272 - Garon