Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!uw-beaver!ubc-cs!cheddar.ucs.ubc.ca!ballard
From: ballard@cheddar.ucs.ubc.ca (Alan Ballard)
Newsgroups: comp.os.os2.apps
Subject: Re: Kermit Direct Connect under OS/2
Message-ID: <10033@ubc-cs.UUCP>
Date: 11 Oct 90 22:36:38 GMT
References: <6948@vax1.acs.udel.EDU> <58157@microsoft.UUCP>
Sender: news@cs.ubc.ca
Reply-To: ballard@cheddar.ucs.ubc.ca (Alan Ballard)
Organization: UBC Computing Centre, Vancouver, B.C., Canada
Lines: 22

In article <58157@microsoft.UUCP> w-ronra@microsoft.UUCP (Ron RADKO) writes:
>Hmm.  I just received my latest version of OS/2 for a Toshiba.  Gee there's 
>a little note with it.  It says:  do not attempt to run such programs as 
>lap link and cross talk from the dos compatibility box. 
>...  If anyone else has come up with some solutions,
>or knows what is causing the problem, I would love to hear about them.  
 
I'm not sure if I understand what problem you're having.  I use kermit
routinely from the Dos box, along with a couple of other terminal
programs.  The only catches I know of are 1) You must "setcom40 com1=on"
before you can use the com port and 2) for some combinations of hardware, 
dos software, and OS/2 syslevels you need to turn off hardware buffering
with a command "mode com1 xxxx,,,,buffer=off" (where xxxx is the baud
rate).  You must issue this from OS/2; do it from a startup.cmd file. 
And note it is buffer=, not buffers= as shown in the documentation. 
The problem requiring this buffer= option appeared with 1.2, it seems to
be fixed in current syslevels.
 
Alan Ballard                   | Internet: ballard@ucs.ubc.ca
University Computing Services  |   Bitnet: USERAB1@UBCMTSG
University of British Columbia |    Phone: 604-228-3074
Vancouver B.C. Canada V6R 1W5  |      Fax: 604-228-5116