Newsgroups: comp.windows.ms
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!maverick.ksu.ksu.edu!unmvax!uokmax!uokmax.UUCP!butch
From: butch@alliant.backbone.uoknor.edu (Butch Walker)
Subject: Attention! - Windows Comm. Program
Message-ID: <1990Aug28.082531@alliant.backbone.uoknor.edu>
Sender: news@uokmax.uucp (Nets)
Reply-To: butch@alliant.backbone.uoknor.edu (Butch Walker)
Organization: University of Oklahoma, Norman, OK
References: <1990Aug25.160852.25287@amd.com> <1990Aug27.234514.6869@chinet.chi.il.us>
Date: Tue Aug 28 13:25:31 1990 GMT

In article <1990Aug27.234514.6869@chinet.chi.il.us>,
patrickd@chinet.chi.il.us (Patrick Deupree) writes:
|> >
|> >My local store was out of CrossTalk for Windows... I will be
getting
|> >it soon. Anyone have experience with it under Win3. Does it use the
|> >16550? I know no auto-learn in CT. How easy is the scripting
language?
|> >How good is the vt100 emulation?
|> 
|> I don't remember the previous message, so I may be covering a
terminal program
|> that has already been covered.  I'm using DynaComm (as a matter of
fact, I'm 
|> using it right now) on both a Unix machine and on CompuServe.  I like
it a
|> lot.  The Scripting language isn't too bad (I didn't have the manual
for
|> the script language, so I used another script and modified it for my
|> purposes).  For CompuServe it's great because it supports the
Compuserve
|> B protocol.

Anybody thinking of buying a commercial package would be well advised to
wait for a few weeks and get by with what you are currently using.  I am
currently beta-testing a Windows communication package, Wincomm, which
is about ready for release and, at least for my needs, blows away all
the other packages I've used.  It has an extremely powerful macro
language which allows creation of menu bars, full feature dialog boxes,
bitmaps or metafiles with hotspots, DDE support and Sendkeys function
for non-DDE programs, macro recorder, background transmission of data
and a lot more. It supports Kermit, X/Y/ZModem, YModem-g, and Compuserve
B+ transfer protocols.  Terminal emulations include: Compuserve Vidtex
w/RLE graphics support, VT52, VT102, and Color ANSI.  
	In addition, Wincomm has a PC to PC operating mode which would be
suitable for LapLink type operations or as a simple host.  The slave
program runs TSR and occupies 18K of memory.  It also provides simple
security.  There is also a Phone mode which acts as a phone directory
and dials the number for you.
	Included with the package is a Dialog Editor which allows you to design
the dialog boxes graphically and which then generates the macro code. 
There is also a keyboard remapper, a hot spot editor, and a facility for
creating your own context-sensitive help for macros.
	I really think that this package will do some things that haven't been
done before.  There will be a demo version of the package available soon
on Compuserve and possibly some archive sites.  If there are any feature
you would like to know about or would like some sort of flier, e-mail to
me and I'll see if I can get something arranged. 

--Butch