Path: utzoo!utgpu!watserv1!watmath!att!rutgers!cs.utexas.edu!usc!apple!netcom!mcmahan
From: mcmahan@netcom.UUCP (Dave Mc Mahan)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Summary: How do you get VT100 Inverse Video Char set to work?
Message-ID: <12182@netcom.UUCP>
Date: 15 Jul 90 20:54:54 GMT
References: <31705@cup.portal.com> <23847@uflorida.cis.ufl.EDU>
Distribution: na
Organization: Dave McMahan @ NetCom Services
Lines: 27


 In a previous article, jma@beach.cis.ufl.edu (John 'Vlad' Adams) writes:
>"Interesting comments..."  I've been using 1.0 for a few days now
>in conjunction with two VT100 connections and eight IBM ANSI
>connections.  I've yet to have a problem.  Jack even has the 16 color
>IBM ANSI finally working flawlessly in regards to PAL -hacked  Amigas.
>Zmodem works fine (unlike some bugs throughout the .99's).  I've not
>tried any of the other protocols since Xmodem is too slow and I
>don't have an HST to take advantage of the Ymodem-G protocol.  

I got my copy of 1.0 via the mail, and have tried to install it.  In the first
call to the first BBS I use to read usenet, I find that the VT100 mode does
not seem to properly handle inverse video.  It prints a line, but with a
character set that is black-on-black.  I dropped back to version .99n,
which I now use to write this message.  Is this black-on-black problem
a configuration error on my part, or is there something wrong with JR-Comm 1.0?
I'd really like to use it instead of an older version, but I need at least
some minimal functionality of the inverse video stuff for my mailer.  Any
suggestions out there?

Personally, I happen to think that JR-Comm is optimal for my needs, if I could
just get certain minor features to work correctly.  I'd love to standardize on
version 1.0 if I could get it to work.

>John  M.  Adams    --**--    Professional Student on the six-year plan!     ///

   -dave