Hi Sean,

     About "Kermit on TeleGard" of October 19:

SD> ...internal variables...  ...happy to send you MCI.REF...

     I got it, thanks!  I just had time to get a glimpse, i've been busy
trying to compare `MS-Kermit' against `C-Kermit' and `VSPD XP4' required
some of my attention before i could refresh my memory with some testing.

                                  %-)

MS> Is there a BBS feature which can tell the user how fast his
MS> transfers have been over the week...  ...in cps...
SD> ...I could cause a script to run...  that would be interesting.

     Great!  I'd like to have `ZMoDem' vs `Kermit' comparisons possible.

MS> ...i'm most concerned because .QWK BBS doors must never UpDate
MS> message-pointers unless the user really received...
SD> Telegard does not update a user's pointers until AFTER the REP...

     Hummm...  It sounds quite effective - and natural enough may i add!

SD> TRANSFER.LOG is simply a log of the transfer...

     I get the idea, it will come somewhat later then.  In the meantime,
here's something to begin with which must be considered before `MCI.REF'
is even mentioned.  :)  1st of all, when i wanted to test `CKOKer16.EXE'
i found out that ftp://kermit.columbia.edu/kermit/archives/cko191.zip is
a 32-Bits release only:  `C-Kermit v5A(191)' doesn't include `CKOKer16',
only `CKOKer32' is provided and i can't test it in my `W32' environment.

     http://acornsw.com:9081/vs0169/vms94a/kermit/b/ckozip.boo was where
i found `C-Kermit v5A(189)' with both versions, a couple months ago.  To
unwrap it i had to use a piece of SoftWare called `ZipZap', as i recall.

     So, my testing has been done with `MS-Kermit v3.16' of October 2003
and `C-Kermit v5A(189)/16-Bits' of June 30, 1993.  Two major issues come
to mind:  the number of nodes to be supported and the top speed allowed.

     I'm afraid that `MS-Kermit v3.16' and `CKOKer16.EXE' both happen to
support only *FOUR* serial ports (COM1 to COM4), if ~FOSSIL~ ports could
be used `MS-Kermit' would support up to 99 nodes but not `CKOKer16' as i
found that it doesn't seem to support ~FOSSIL~ ports at all.  As for the
speed, `MS-Kermit' is OKay with 115K2 bps connections but not `CKOKer16'
which doesn't go beyond 57K6 bps...  From what i seen so far, the native
`OS/2' protocol driver would probably allow cps rates no higher than 3K5
cps, one bright side is that you get the "estimated time left" displayed
and the `Kermit' packet-size is exactly equal to what the setup defines;
i used `CKOKer16' to establish without a doubt that `HyperTerminal' only
supports `Kermit' packets of 94 bytes maximum - which is rather limited!

     That's all the news i have for now, stay tuned for more UpDates!...

                                    Salutations,  :^)

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


... Win32/WinSock+DSL+COMIP+DOSInt14+MSKermit+.QWK are LEGACY inclusive.
-!- MultiMail/MS-DOS v0.45 - Making TelNet OLMR BBSing more *UNIVERSAL*!

--- Mail-ennium/32 v2.0-beta-r1