schanck@daisy.cis.ohio-state.edu (Christopher Schanck) (01/11/89)
In article <5399@watdcsu.waterloo.edu> hazela@watdcsu.waterloo.edu (Jose Reynaldo Setti) writes: >Telix 3.11 - This is the most incredible piece of shareware I have ever had a >chance to use and as a telecom package it leaves Procomm+ in its dust. I, too have found Telix to be awesome. However, I found a bug which, albeit minor, realy irritates me. When using the VT102 emulation, if the host sends the underline code, Telix responds by using (I believe) the BIOS underline function, which on my CGA turns the foreground text to blue. This is irritating since my favorite color combo is cyan on blue. Since I spend most of my time on a UNIX system, and important things like man and rn use underlining, I either have to choose different colors or not use it. Currently, I am using a homebrew program, and awaiting a fix. I left a message about it on Exis, Inc.'s BBS, and I'l*l be looking for a new version. Other than that, it is awesome! Chris -=- "My brain is NOT a deadlock-free environment!!!!" --- Christopher Schanck, mammal at large. schanck@flounder.cis.ohio-state.edu
hundt@paul.rutgers.edu (Thomas M. Hundt) (01/11/89)
>if the host sends the underline code ... turns the foreground text to >blue >most of my time on a UNIX system Doesn't telix support some other form of highlighting? You could hack up your own termcap, then you could tell it to use whatever color you want! Perhaps run telix in ansi terminal mode, and use red or something for the "ul=" mode. The reason for the blue foreground is that the underline code in the attribute byte maps to blue color on CGA, I believe. -- RRRRRR Thomas M. Hundt (aka hundt@occlusal.rutgers.edu) RR RR Gradual Student --- Electrical & Computer Engineering RR RR Rutgers University 201/932-5843(Lab) RRRRR 272 Hamilton St. #96 201/247-6723(H) RR RR New Brunswick, NJ 08901 RRR RRR Famous last words: "The virus ate it."
jsin@island.SEAS.UCLA.EDU (01/12/89)
In article <Jan.10.17.31.09.1989.15865@paul.rutgers.edu> hundt@paul.rutgers.edu (Thomas M. Hundt) writes: >>if the host sends the underline code ... turns the foreground text to >>blue > >>most of my time on a UNIX system > >Doesn't telix support some other form of highlighting? You could hack >up your own termcap, then you could tell it to use whatever color you >want! Perhaps run telix in ansi terminal mode, and use red or >something for the "ul=" mode. > This would be most welcome. As it stands now, it makes the program almost unusable, since In order to see the highlighted character, I have to squint real hard and turn up the brightness on my monitor. 'course, this makes all other characters fuzzy. Another gripe: Why does it always start up in N71, when I set it up as S71? I suppose maybe I should read the docs, but it seems counter-intuitive. Too bad. Back to Procomm. John (Jonghoon) Sin (Above opinions are my own and etc, etc, etc...) UCLA SEASnet Facilities InterNet: jsin@seas.ucla.edu 2567 Boelter Hall UUCP: ...!(uunet,ucbvax,rutgers)!seas.ucla.edu!jsin Los Angeles, CA. 90024 Voice: (213) 206-6864 */Real Men Don't Use Icons/*
schanck@harmonica.cis.ohio-state.edu (Christopher Schanck) (01/12/89)
In article <Jan.10.17.31.09.1989.15865@paul.rutgers.edu> hundt@paul.rutgers.edu (Thomas M. Hundt) writes: >Doesn't telix support some other form of highlighting? You could hack >up your own termcap, then you could tell it to use whatever color you >want! Perhaps run telix in ansi terminal mode, and use red or >something for the "ul=" mode. > >The reason for the blue foreground is that the underline code in the >attribute byte maps to blue color on CGA, I believe. That is the reason for it, and yes I could hack up my own termcap (this has been suggested by several people), but I don't want to have to. It really bugs me that such an otherwise fine package is marred by such a little problem. Telix supports adapters so well, with snow testing and such, why can't it handle this case without special handling. For now, I'll stick with what I am using. In another vein, I have used Telix a few times for 8n1 transfers, on different systems, with ZMODEM, XMODEM, and KERMIT, and have had no trouble (version 3.11...) Chris -=- "My brain is NOT a deadlock-free environment!!!!" --- Christopher Schanck, mammal at large. schanck@flounder.cis.ohio-state.edu
tbetz@dasys1.UUCP (Tom Betz) (01/14/89)
Quoth jsin@island.SEAS.UCLA.EDU (John Sin) in <19463@shemp.CS.UCLA.EDU>: |>[Somebody writes:] |>>if the host sends the underline code ... [Telix] turns the foreground text to |>>blue I had this problem with the vt102 emulation on my mono system using a CGA card. I conferred with Colin, he explained this was standard for a color VT102 monitor. In other words, according to him, the problem is that his emulation is >too< good. I found, when I switched from CGA emulation to Herc emulation, the vt102 emulation underlined correctly. If you have a mono monitor, and your card is capable of software switching to Herc mode, I suggest you add that software switch to your .BAT file that calls Telix. If you're using a color monitor, then you might try the Alt-W configuration option, which permits remapping incoming characters to other characters, and see if you can fix it that way. |Another gripe: Why does it always start up in N71, when I set it up as |S71? I suppose maybe I should read the docs, but it seems counter-intuitive. It always helps to RTFM. I don't know whether this is or is not possible, but why should it matter, when each entry in the dialing directory can be set up to switch to S71, or whatever you like? At any rate, as Colin is not here to anwer your questions, I'll pass them along to him, and see what he has to say. In my discussions with him, he has said he would change the underline color (or make it user-configurable) in a future release. |Too bad. Back to Procomm. Too bad. -- "Big Bob says he's getting tired of you saying he |"Do you think God lets doesn't really exist." - Fat Little Nerdy Kid - | you plea bargain?" Tom Betz - ZCNY - Yonkers, NY - 914-375-1514 |"I'd worry more about ...cmcl2!dasys1!tbetz OR ...uunet!dasys1!tbetz | your mom." - C & H
wales@valeria.cs.ucla.edu (Rich Wales) (01/16/89)
In article <8269@dasys1.UUCP> tbetz@dasys1.UUCP (Tom Betz) writes: > Another gripe: Why does it always start up in N71, when I set > it up as S71? I don't know whether this is or is not possible, but why should it matter, when each entry in the dialing directory can be set up to switch to S71, or whatever you like? One reason it matters is that the default terminal mode is what Telix uses when it sends out the modem initialization string. A mode of "N71" is likely to fail pretty badly. There is indeed a bug in Telix 3.11 which causes a default parity set- ting of SPACE to be forgotten and replaced by NONE. (EVEN or ODD works, however.) A workaround for this problem would be to use a default terminal mode of "N81" instead of "S71". -- Rich Wales // UCLA Computer Science Department // +1 (213) 825-5683 3531 Boelter Hall // Los Angeles, California 90024-1596 // USA wales@CS.UCLA.EDU ...!(uunet,ucbvax,rutgers)!cs.ucla.edu!wales "Now, if you do see me again today, I want you to report it to me immediately."