Text 167, 99 rader
Skriven 2004-10-16 03:02:00 av MICHEL SAMSON (1:10/345)
     Kommentar till en text av SEAN DENNIS
Ärende: Pure DOS TelNet ZMoDem
==============================
Hi Sean,

     About "Pure DOS TelNet ZMoDem" of October 14:

SD> ...ZModem is one of the worst protocols to use over telnet because
SD> its timing is designed for POTS, not Internet.  However, it was the
SD> most plentiful, so therefore, it proliferated even more.

     In the case of `ZMoDem' i call it positive re-inforcement.  This is
about the same as `Windows' vs `OS/2', Motorola's 68000 processor series
vs Intel's 8088/8086 family.  As i'd have argued before, if BBSers could
access `ZMoDem's options, euh...  `Kermit' would be harder to promote!!!

                                  %-)

SD> I don't know about "straight" DOS, but I'd imagine that there might
SD> be speed issues or protocol issues...

     I appologize for the lack of precise numbers but `ZMoDem' transfers
rarely reach over, say, 4K cps on selected remote systems while `Kermit'
doubles that figure and more (i've seen transfers around 12 Kcps);  take
note i use .ZIP file archives to rule out compression for all my testing
and the connection is thru a router feeding on a 128 Kbps ~DSL~ MoDem...

                                  ;-)

     If `ZMoDem' didn't have it's parameters hard-coded in `{Commo}', it
might have its rate improved but i do use the Escape function already...

SD> I only wish I knew more about protocols...  I am pretty proficient
SD> at Pascal, but I'm not as good as some of the people I know.

     There are many more ~FOSSIL~ source-code packages available but i'm
one of the very few guys who happen to see advantages in having `Kermit'
and `ZMoDem' side-by-side in a single ~TelNet~-compatible application...

     If `Conex's source-code were modified to make it interface directly
with the the packet-driver this shouldn't even involve any file transfer
protocol, nonetheless...  Instead of depending on ~BIOS INT-14~/~FOSSIL~
support in `TNPort', for example, i'd imagine a version of `Conex' where
my ~TelNet~ session can be redirected through the ~FOSSIL~ port in order
to gate the data stream toward an external file transfer protocol driver
(just like it's done with a BBS system)...  `Conex' with Novell ~ODI~ or
packet-driver interfacing would give `ZMoDem' a boost, `MS-Kermit' would
make a competitive addition provided that `Conex' behaves like `TNPort'.

     `Conex' has a dialing directory which allows easy connection to the
remote systems, the BBSers who `ZMoDem' alone can satisfy would probably
appreciate an extra Novell ~ODI~ or `Waterloo TCP' packet-driver option.

                                  ;^)

     Of course, it's more of a project than to simply add `Kermit' as an
external protocol driver - which is why i chose this very modest goal...

SD> Also-are you still wanting me to try to get Kermit running under
SD> my system again?  Just wasn't sure if you did or not.

     After the feed-back that i finally got from other source this year,
i'm even more convinced than before that my approach helps to avoid some
very concerning problems caused by using the .INI as suggested by Rob...

     I asked him to erase all references to me about helping to create a
previous version of `Kermit.INI', actually!  Should you feel comfortable
with the idea of switching to `MSK.INI, plug it in and i'll continue the
work...  :)  I still want to bring our cooperation to completion but i'm
at a point where Wayne Warthen's `Kermit for Windows' represents quite a
serious threat:  `Kermit.INI' disables transfer recovery, won't leave me
much time to start my protocol and its parameters make the session hang.
                                                                   ^^^^
     Can you please remind me which of `CKOKer16.EXE' or `MS-Kermit.EXE'
works with `Telegard/2' under `OS/2', instead of `CKOKer32.EXE'?  It was
tempting to replace `C-Kermit v5A(191)' of April 24, 1995 (`CKO191.ZIP')
with something, euh...  more recent!  The last time i checked this, your
`CKermit.INI' configuration-file forced `C-Kermit' to load `CKerMod.INI'
and the later was connecting to ~COM1~!!!  Which, i must confess, got me
quite a bit puzzled (since i didn't expect ~TelNet~ using `SIO'/`VMoDem'
to redirect data to ~COM1~).  A "Named Pipe" or else was mentioned but i
heard you had urgent matters to cope with so i waited for better news...

                                   :)

     As i wrote, i waited for years litterally...  A few more days/weeks
won't change my mind much as long as i see hope.  I wish you a nice day!

                                    Salutations,  ;^)

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


P.S.:  Can i still use `SpiffyTelnet' and, once i switched to BINARY, be
       able to D/L using Sailor's `ZMoDem' (which is very special here)?


... I BBS using LEGACY DOS+TCP/IP+TelNet+ZMoDem/Kermit+.QWK technologies
--- MultiMail/XT v0.45 - Let me try a TelNettable BBS with an OLMR door!
 * Origin: BBS Networks @ www.bbsnets.com 808-839-6036 (1:10/345)