Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!uokmax!uokmax.ecn.uoknor.edu!butch
From: butch@uokmax.ecn.uoknor.edu (H. G. Walker)
Newsgroups: comp.windows.ms
Subject: Re: Attention! Wincomm demo available
Message-ID: <1990Oct9.210050.29419@uokmax.ecn.uoknor.edu>
Date: 9 Oct 90 21:00:50 GMT
References: <15910@shlump.nac.dec.com>
Sender: news@uokmax.ecn.uoknor.edu (Nets)
Reply-To: butch@geo785.gcn.uoknor.edu
Organization: University of Oklahoma, Norman,OK 73019
Lines: 17

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