Subj : Kermit on TeleGard
To   : Sean Dennis
From : Michel Samson
Date : Tue Oct 19 2004 05:07 am

Hi Sean,           [Replying to a post which didn't distribute fully...]

     About "Pure DOS TelNet ZMoDem" of October 16:

SD> CKOKer32.EXE has a problem (read: bug) in it somewhere...

     Then i agree, it's better to avoid trouble by using `CKOKer16.EXE'!

MS> ...i didn't expect ~TelNet~ using `SIO'/`VMoDem' to redirect data to
MS> ~COM1~...  A "Named Pipe" or else was mentioned...
SD> Under OS/2, using SIO/VMODEM, everything uses comports...  It's all
SD> as if you're using a dialup BBS (which is why Telegard/2 works so
SD> well with it).  You don't use any sockets, named pipes, et al.

     Oh, then wouldn't it be simpler just to use `MS-Kermit.EXE' instead
of `CKOKer16.EXE' in that case?  Hummm...  I need to load `CKOKer16.EXE'
in a `W32' DOS box and see what happens - this should work, as i recall,
but if it doesn't then i must find the means to figure a few things out!

                                  %-)

SD> I am actually having a harder time getting the configuration of
SD> TG/2's protocol setup rather than getting Kermit to work.  For that,
SD> we should probably move this over to TG_SUPPORT. 

     Then i'll meet you in the `TeleGard Support' area and hope for less
noise than what i've been able to observe everywhere else this month!...

                                    Salutations,  8^)

                                    Michel Samson
                                    a/s Bicephale
                                    http://public.sogetel.net/bicephale/


.... And only 8088+DOS+TCP/IP+TelNet+Kermit+.QWK technologies were used?!
___ MultiMail/MS-DOS v0.45 - It could make TelNet OLMR BBSing UNIVERSAL.
--- Maximus/2 3.01
 * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)

.