Hi Sean,

     About "Kermit on TeleGard" of October 22 and 23 and
"More Telegard
reference stuff" of October 23 (which i received via ~E-Mail~):

MS> What i need to know...  ...1) how long the command-line can be...  
MS> 2) can the internal variables...  ...be read as DOS environment
MS> variables;  3) how much memory `MS-Kermit' and `C-Kermit' are using.
SD> Your answers:  1) I'm not sure on that...  2) Yes, they are passed
SD> directly to a batch file...  ...%1 %2  3) That's not an issue...
MS> ...newer...  ...`C-Kermit 5A(190)'...  ...won't execute in a `W32'
MS> DOS windows...  ...the command-line is very different from that of
MS> `MS-Kermit', i only see good reasons to pick `MS-Kermit' instead...
SD> ...going to email you the .PDF file format...  ...developer's kit.
SD> ...I am on dialup and it seems my ISP has blocked port 23...  I do
SD> have QModem Pro for Windows installed on this machine, so I can
SD> actually test out a Kermit install on the OS/2 machine.

     `MS-Kermit' could be the obvious choice for a Protocol Driver and a
suitable Terminal Emulator as well since `SIO'/`VMoDem' is installed and
`OS/2' can run 16-Bits DOS applications.  The "ReSend" Transfer Recovery
feature was added only in the final 16-Bits `OS/2' version of `C-Kermit'
so i'm worried:  there were no successive releases in the later case, if
any "ReSend" bug remained uncovered in `C-Kermit 5A(190)' that means you
will be stuck with it.  I'd have prefered `MS-Kermit' but `C-Kermit' can
support transfers over 24 Kcps and this is faster than my 128 Kbps ~DSL~
feed will allow - hence there's no bottleneck at `Kermit's level, as far
as i'm concerned...  I've been able to install `QModem Pro' only under a
`Win 98 SE' environment (which i don't use too often anymore) and it was
so unstable it aborted on 1st try (i believe that's a "Beta"), `QMoDem's
`Kermit' maximum packet-size is 1024 bytes, anyway!  For `Windows' users
who prefer ~GUI~ stuff (and who aren't going to have `COM/IP' in$talled,
in any case), euh...  `Zap-O-Comm' seems to be a suitable alternative (i
obtained satisfying `Kermit' transfer rates with it, i can't comment yet
about it's reliability though).  `MS-Kermit' is known to be "rock-solid"
and would have been significantly easier on me but we'll try `C-Kermit'.

SD> Here's the actual .PDF (protocol definition file) documentation for
SD> Telegard...  Hope this can help you.  I'll grab the file you
SD> mentioned recently (the 16-bit OS/2 version of Kermit) and try...

     `Text_PDF.DOC' did help:  it tells us that the command-lines can be
sixty characters long;  i can't say if it includes everything, though...

     Something else which i'm wondering about is the curly brackets:  it
would make it self-documentary if the .PDF could include comments in it!

     The "ENVIRONMENT" field is very interresting, i can define at least
one DOS environment variable which `MS-Kermit' can read (i don't know if
`C-Kermit' can do the same at the moment)...  UpLoad and DownLoad Result
Codes are another feature i like (one more i'm not sure about just yet),
what are we supposed to do with "DLCODE1", relatively to the
"Single" vs
"Batch" modes (not to mention the "SUCCESS" field which
got me puzzled)?

     "Word Position" is another thing which needs clarification, must we
start counting from zero or is is the 1st column numbered 1?  "ULCODE2",
"ULCODE3"...  "DLCODE2", "DLCODE3", etc., are
additional unknowns:  must
we define as much of them as there are FileNames in the batch-list file?

______________________________________[ `Kermit.PDF' - TESTING SAMPLE ]_
PROTOCOL    Kermit Terminal (Debug Command-Line)
BATCH       Y
UPLOAD      CKOKer16 -l ~CP -b ~CA
DOWNLOAD    CKOKer16 -l ~CP -b ~CA
ENVIRONMENT 
ULCODE1     0
DLCODE1     0
SUCCESS     Y
TEMPLOG     CKOKer16.TMP
FILELIST    {at}
LOG_FILE    1
LOG_RESULT  40
ULCODE2     0
ULCODE3     0
DLCODE2     0
DLCODE3     0
BIDIREC     N
NOTE        `Kermit' Terminal option, Debug Command-Line mode
NOTE        -------------------------------------------------
NOTE        Start your `Kermit' protocol with these settings:
NOTE
NOTE        Set Window 3
NOTE        Set Streaming On
NOTE        Set Block-Check 3
NOTE        Set File-Type Binary
NOTE        Set Terminal ByteSize 8
NOTE        Set Attributes Date Off
NOTE        Set File InComplete Keep
NOTE        Set File Collision UpDate
NOTE        Set Control UnPreFixed All
NOTE        Set Control PreFixed 0 1 17 19 129
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     I hope i didn't leave too much to your discretion.  ;-)  As you may
have noticed, i dropped using `MSK.INI'...  there can be many changes to
make before i can try to integrate them in it, i'm afraid.  As for being
a DialUp ~TelNet~ BBS with a picky ~ISP~, don't worry:  when we're ready
for testing lets use ~IM~ (which makes it easy to agree on a rendez-vous
and then proceed from there);  port 23 isn't mandatory and i can get the
~IP~ in a chat session, after all.  In the meantime, have a nice day!...

                                    Salutations,  :)

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


... I BBS using LEGACY DOS+TCP/IP+TelNet+ZMoDem/Kermit+.QWK technologies
-!- MultiMail/MS-DOS v0.45 - Trying to make TelNet OLMR BBSing UNIVERSAL

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