Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!olivea!oliveb!amdahl!rtech!ingres!seg
From: seg@ingres.com (scott e garfinkle)
Newsgroups: comp.os.os2.apps
Subject: OS2 Comm programs (was Re: Kermit Direct Connect under OS/2)
Summary: Get TE2
Message-ID: <1990Oct16.161402.1393@ingres.Ingres.COM>
Date: 16 Oct 90 16:14:02 GMT
References: <6948@vax1.acs.udel.EDU> <58157@microsoft.UUCP>
Reply-To: seg@beaver.Ingres.COM (scott e garfinkle)
Organization: Ingres Corp.
Lines: 21

In article <58157@microsoft.UUCP> w-ronra@microsoft.UUCP (Ron RADKO) writes:
>... the only two solutions that I have found are to either boot DOS if you want
>to use any standard protocols, or to use the OS/2 terminal program if you
>want to transfer just ASCII.  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 currently looking into writing a terminal program for OS/2 that will
>allow standard protocol transfer.  But, it'll be awhile before it's 
>completed.

I have been using the TE2 communications program for OS2 for the last few
days.  The current version is 1.10B.  It comes with x/y/zmodem built in, and
has kermit available as an "external protocol".  TE2 is shareware from "Oberon
Software".  Their BBS is at (507) 388-1154, and by voice at (507) 388-2848.
I have been very pleased with the program.  It does a lot of things right.

By the way, I had been using procomm+ in the DOS box successfully (even at
14.4kbaud) prior to getting TE2.

	-scott garfinkle
	Ingres Corp.
Standard Disclaimer