Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!lll-winken!iggy.GW.Vitalink.COM!widener!dsinc!netnews.upenn.edu!msuinfo!USER2@cgevs3.cem.msu.edu
From: user2@cgevs3.cem.msu.edu (Stephen Medlin)
Newsgroups: comp.windows.ms
Subject: Re: Comm trouble: Win + DOV unit
Message-ID: <009479E3.C502A8C0@cgevs3.cem.msu.edu>
Date: 24 Apr 91 21:39:32 GMT
Sender: news@msuinfo.cl.msu.edu
Reply-To: user2@cgevs3.cem.msu.edu (Stephen Medlin)
Distribution: usa
Organization: MSU_Chemistry
Lines: 33

In article <1991Apr24.170157.28070@morrow.stanford.edu>, BA.CGB@forsythe.stanford.edu (Clif Baker) writes:
>Folks,
>
>This question is a bit on the broad based side...
>
>Is there an overall survey of communications packages for
>Windows 3.0?  Specifically one that rates their features,
>compatibility etc.
>
>Of course failing that...what sorts of recommendations from
>experienced users are there?
>
>Thanks!
>
>Clif

Clif,
	I can tell you about my experience with UniCom...Basically Did Not
Like IT!!!!!  Now, I have been presently using GT-PowerCom (non-Windows
program).  I've checked out a lot of Comm programs and I find that I can
learn the commands for any type of program, but what I couldn't abide with
was weak or missing features.  When I saw/bought Unicom, my colleages and I
were initially impressed with the layout of the program.  It was easy/fairly
intuitive to use.  But the features were missing.  The dialing directory was
weak, scripts were adequate, and the transfer rates/ screen updates were
slow.  I do like the Windows-type of features--DDE, cut/paste, running other
programs, etc.; but I think that Win Comm programs have a lot to catch up
to GT-PowerComm, Telix, etc.  I hope that they do. 
	I would be interested in hearing responses from other people on 
Win Comm programs.  I have heard that CrossTalk is supposed to be good.  Any
other comments out there?

Stephen