Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mcdchg!ddsw1!karl From: karl@ddsw1.MCS.COM (Karl Denninger) Newsgroups: comp.unix.i386 Subject: Re: Rlogin problems with Foxbase+; screen is hosed Summary: Nope -- telnet, however >works<. This is a kludge; I need a fix! Message-ID: <1989Dec29.224442.417@ddsw1.MCS.COM> Date: 29 Dec 89 22:44:42 GMT References: <1989Dec28.194536.2499@ddsw1.MCS.COM> <1989Dec29.111054.7348@virtech.uucp> Reply-To: karl@mcs.MCS.COM (Karl Denninger) Organization: Macro Computer Solutions, Inc. - Mundelein, IL Lines: 37 In article <1989Dec29.111054.7348@virtech.uucp> cpcahil@virtech.uucp (Conor P. Cahill) writes: >In article <1989Dec28.194536.2499@ddsw1.MCS.COM>, karl@ddsw1.MCS.COM (Karl Denninger) writes: >> Has anyone tried to run SCO Foxbase+ from ISC 2.0.2 over a "rlogin" >> link? When we try, even in a loopback mode (ie: rlogin to yourself) >> the output on the screen is screwed up. Pieces of lines and entire >> lines are missing! Telnet does the same thing (if from the Unix >> host). > >The problem might be caused by foxbase turning off flow control in order to >emulate dbase III's input key. You might try to lower your baud rate >on the terminal comm line to see if your terminal can handle a full feed >at the lower speed. Nope. Even at 2400 baud it is completely hosed. However, we have been able to make it work using Telnet. This is also a kludge however, and we need rlogin fixed.... or source to Telnet (telnet apparently sets some very strange parameters on the user's end, and gets some intelligent boards very upset. In particular, it sets some combination that the Equinox Megaport doesn't like!) The docs for the Megaport say that it won't work with less than 10 bits/character (including stop, start & parity) at over 4800 baud. The telnet program appears to be setting something that violates those conditions on the local end -- which prevents it from working. (why, I don't know). Does anyone have a freely-usable telnet program in source form? That ought to do it. "Rlogin" doesn't -- I hacked up a rlogin with some help from a friendly person but that wasn't any better. Since NCSA Telnet works from a PC, I assume that if I do my own telnet for 386/Ix all should be ok. -- Karl Denninger (karl@ddsw1.MCS.COM, !ddsw1!karl) Public Access Data Line: [+1 708 566-8911], Voice: [+1 708 566-8910] Macro Computer Solutions, Inc. "Quality Solutions at a Fair Price"