Path: utzoo!attcan!uunet!decwrl!sdd.hp.com!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!unmvax!uokmax!uokmax.ecn.uoknor.edu!butch From: butch@uokmax.ecn.uoknor.edu (H. G. Walker) Newsgroups: comp.windows.ms Subject: Re: WinComm look great but... Message-ID: <1990Oct8.153539.22431@uokmax.ecn.uoknor.edu> Date: 8 Oct 90 15:35:39 GMT References: <7409@umd5.umd.edu> Sender: news@uokmax.ecn.uoknor.edu (Nets) Reply-To: butch@geo785.gcn.uoknor.edu Organization: University of Oklahoma, Norman,OK 73019 Lines: 46 In article <7409@umd5.umd.edu>, dlevine@umd5.umd.edu ( First Aider) writes: |> Well, I decided with a review like this got, it had to be awesome. |> WinComm really is an incredible advancement over WINQVT. |> It's really very complete as far as features. |> |> 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 |> similar problem when trying out much older versions of UNICOM I don't know what is the problem. Is it possible that there have been some changes in the zmodem protocol and Wincomm is using an older version. I have in the past had problems using zmodem from one host while the same program works on another host. I think zmodem is kinda quirky about that. If you can send any more info to me, I'll let Synappsys know and see if they can work it out. |> 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. If you would, use the capture feature to record the problem and then call Synappsys. They will probably want to get a copy of the problem so it can be investigated and fixed. I have used vi several times in Wincomm without difficulty, so they will be interested in seeing that. |> The only other problem I've had thus far with this great terminal is |> with it's keyboard remapping program. I want to change my backspace |> to <> and that's ok. But when I save it, god knows where it |> goes because when I want to use it, it doesn't appear where I put it! The keyboard mapper saves tha mapping to a file which can they be associated with whatever session files are appropriate. You need to select the keyboard remap in the session editor. I believe it is in the terminal part of the session editor where you select which keymap to use. I hope this solves your problem. |> |> And by the way, how much is this thing? It's really great...and where |> do you send the moeny while you're it it. ;) The price is $149 retail, though they do have a educational discount which is explained in the wincomm.txt file. If you want to send money, the address is: Synappsys 401 West Main Suite 300 Norman, OK 73069