Path: utzoo!attcan!uunet!decwrl!wuarchive!mit-eddie!bloom-beacon!eru!hagbard!luth!d89-bfr
From: d89-bfr@sm.luth.se (Bjorn Fahller)
Newsgroups: comp.windows.ms
Subject: Re: WinComm look great but...
Message-ID: <1166@tau.sm.luth.se>
Date: 8 Oct 90 21:01:47 GMT
References: <7409@umd5.umd.edu> <1990Oct8.153539.22431@uokmax.ecn.uoknor.edu>
Organization: University of Lulea, Sweden
Lines: 29

butch@uokmax.ecn.uoknor.edu (H. G. Walker) writes:

>In article <7409@umd5.umd.edu>, dlevine@umd5.umd.edu ( First Aider) writes:
>|> However, I have found that the zmodem doesn't like talking to my
>|> zmodem program I had been previously using with WNQVT!  I had a

>I don't know what is the problem.  Is it possible that there have been some

At first I had no problems at all, but all of a sudden, WinComm complained.
The only differences I saw was that at first I had transfered an ASCII file
using compressed zmodem mode, and later I transfered a packed file with
standard zmodem protocol. When I tried transferring the packed file with
compressed mode, WinComm accepted at once.

>|> Another problem I have found is that I can't get vi (a unix full screen
>|> editor to work properly).  It would appear that the terminal's vt102
>|> emulation isn't complete and can't respond to the unix resize command.

I have noticed the same with Emacs. Some characters are repeated SEVERAL
times. Also the scroll down, feature on ANSI and vt102 seems to fail.

Another thing I'd like to see is a translate table, a'la procomm plus.
It's not a necessary thing, but it makes the whole thing look lots better.
I can stand seeing brackets and braces and backslash and so on instead of
our national letters, but I prefer not to.

Hope the problems will be fixed soon. It's shows promising power.
   _
/Bjorn.