Path: utzoo!attcan!uunet!fernwood!decwrl!wuarchive!udel!sbcs!sbstaff2!altman
From: altman@sbstaff2.cs.sunysb.edu (Jeff Altman)
Newsgroups: comp.windows.ms
Subject: Re: Attention! Wincomm demo available
Message-ID: <1990Oct10.073756.24507@sbcs.sunysb.edu>
Date: 10 Oct 90 07:37:56 GMT
References: <15910@shlump.nac.dec.com> <1990Oct9.210050.29419@uokmax.ecn.uoknor.edu>
Sender: usenet@sbcs.sunysb.edu (Usenet poster)
Organization: State University of New York at Stony Brook
Lines: 50

In article <1990Oct9.210050.29419@uokmax.ecn.uoknor.edu> butch@geo785.gcn.uoknor.edu writes:
>In article <15910@shlump.nac.dec.com>, simon@hpspwr.enet.dec.com (Curiosier and curiosier...) writes:
>|> 
>|> While we are at this, there are a couple of other things that the 
>|> company could improve on:  Support of an LK250 keyboard (by Digital 
>|> Equipment which I use) and 19200 baud.  As far as I am concerned, these 
>|> two features would really make the package great.
>
>Well, then, we should be in business.  Wincomm does support 19200 baud and
>higher.  As far as the LK250 keyboard, if you can get the control codes for it,
>you can use the keyboard remapper to create it.  It is one of the more powerful
>features of Wincomm.  Simply select the key, enter the code to be sent, and so
>forth.  Save the configuration in a file then associate that keyboard mapping
>with the session files you want to use it with.  You ought to be able to get
>as close to LK250 as is possible on a PC keyboard.  E-mail me if you have
>further questions. 
>
>	Butch

Not necessarily true.
Since WinComm does not allow for mapping of <f1>, <f10> or the <NumLock>
keys.
Programs like MS-Kermit allow you to map those keys and therefore 
you are able to have a LK250 mapping.

WinComm is still too restrictive in this respect.

As far as the <f10> key goes, it is used to bring you to the Menu
when using the keyboard.  I much prefer programs which bring you to
the menu by using the Alt key by itself.

NumLock isn't used for anything so it should be allowed to be mapped.

And <F1> is used for Help.  This is a standard function.
However, this function should be able to be mapped to any key
or no key by use of a >>HELP<< identifier in the Mapper Utility.

BTW, how do you access the cut and paste capabilities?

Also, the help files themselves are almost useless.  It is clear
that Wincomm's help files were written so as to be useless without
the manuals.  If I had to give this program to my secretaries
and have them be able to get answers to questions via the Help
I would be receiving quite a few calls.  Not that the Help files
provided with Crosstalk for Windows is any better.

I am as critical as I am only because I want to finally see one 
Comm Package that can meet all of my needs.

- Jeff (jaltman@ccmail.sunysb.edu)