• Pure DOS TelNet Kermit

    From Michel Samson@1:106/2000 to Mark Lewis on Wed Oct 27 23:00:00 2004
    Hi Mark,

    This is an addendum to "Pure DOS TelNet ZMoDem" of October 16:

    ...i (finally) saw that you had uploaded a private package to me, a
    long while back, of kermit stuffs... i've not had time to try to do anything with it and have never been asked about kermit... ...you
    still wanting to do/try something with it on my OS/2 system, too??
    I didn't change my mind about what it's worth... ...though, i
    confess i forgot what's in the archive...

    I paid a visit to your BBS yesterday, there's no .QWK door and much
    less a `Kermit' option... I wasn't able to locate the archive i sent to
    you and i found no `Kermit' option in the file section neither. There's
    a long way to go before we can resume course and reverse twenty years of negative re-inforcement; once you got `Kermit' installed and well set i
    would advise that you use patience (try twenty more years) but the users
    must see it work first and we're not there yet, as far as i'm concerned!

    Salutations,

    Michel Samson
    a/s Bicephale


    ... Sometimes, the cost of new features is too high, really! Is it not?
    ___ MultiMail/MS-DOS v0.45 - Numbers make BBSing UNIVERSAL, not sugar...
    --- Maximus/2 3.01
    * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)
  • From mark lewis@1:3634/12 to Michel Samson on Wed Nov 3 09:09:16 2004
    This is an addendum to "Pure DOS TelNet ZMoDem" of
    October 16:

    ...i (finally) saw that you had uploaded a private package to me, a
    long while back, of kermit stuffs... i've not had time to try to do
    anything with it and have never been asked about kermit... ...you
    still wanting to do/try something with it on my OS/2 system, too??
    I didn't change my mind about what it's worth... ...though, i
    confess i forgot what's in the archive...

    I paid a visit to your BBS yesterday, there's no .QWK
    door

    right... all offline mail doors were removed until my software settles down enough for an offline door to work with it... some things have changed in the data structures that make things not compatible...

    and much less a `Kermit' option...

    never did have a kermit option... what you sent is/was to be the first ever on the system...

    I wasn't able to locate the archive i sent to you

    because you marked it as "sysop's eyes only" ;)

    and i found no `Kermit' option in the file section neither.

    same protcol selection in the entire system...

    There's a long way to go before we can resume course and
    reverse twenty years of negative re-inforcement; once you
    got `Kermit' installed and well set i would advise that you
    use patience (try twenty more years) but the users must see
    it work first and we're not there yet, as far as i'm
    concerned!

    i believe i understand... i was just not wanting you to be jaded about sending some info this way and then nothing ever being done with it...

    my biggest problem is to decide if i should go with native OS/2 flavor of whatever or go with a DOS flavor... DOS stuff generally just drops right in... OS/2 stuff has a few tricks that are needed at times...

    it can be rather rough running a salt'n'pepper system ;)

    )\/(ark
    * Origin: (1:3634/12)
  • From Michel Samson@1:106/2000 to Mark Lewis on Thu Nov 4 11:35:00 2004
    Hi Mark,

    About "Pure DOS TelNet Kermit" of November 3:

    ...i (finally) saw that you had uploaded a private package to me...
    ...you still wanting to do/try something with it... ...?...
    I didn't change my mind... ...though... ...i forgot what's in...
    ...you marked it as "sysop's eyes only"...

    It would help if you could remind me the file-name of this archive.

    I was just not wanting you to be jaded about sending some info this
    way and then nothing ever being done with it...

    You must be the 3rd `OS/2' SysOp with who i discussed `Kermit' this
    year, so far; consider that you're likely to get the better part of the
    deal since i identified/collected some of the needed information already
    and it wouldn't be a 1st time, anyway (i've been "jaded" before)... %-)

    My biggest problem is to decide if i should go with native OS/2
    flavor of whatever or go with a DOS flavor...

    That's my problem as well: i don't run a BBS and much less `OS/2'.

    Here's what i learned. `C-Kermit 5A(190)' of November 16, 1994 was
    the last release WITH A 16-BITS `OS/2' VERSION INCLUDED. I can't do any
    test with it in a `W32' DOS box but it seems the "ReSend" feature (which
    would support Transfer Recovery), the passing of File Attributes and the
    ~REXX~ interface were finally supported there. The LAST RELEASE was `C-
    Kermit 5A(191)' of April 24, 1995; you get NO 16-BITS VERSION IN IT and
    don't expect too much out of a 32-Bits build because of a bug, i'm told.
    In short, forget about a cure for bugs introduced in `C-Kermit 5A(190)'!

    As far as i'm concerned i bet on `MS-Kermit' - a much better choice
    in terms of maturity: October 12, 2003 for v3.16 and September 17, 1997
    for v3.15 - and it's also the 2nd most stable DOS program i ever used...

    If you go for the later then i recommend that you take a peek here:

    http://fidonet.sensationcontent.com/echomail/searchlight/f742a4263556c006.html

    This late setup includes all of the ~URL~s you'd need, in any case.

    ;-)

    The one archive which i didn't include yet can be found right here:

    ftp://kermit.columbia.edu/kermit/archives/cko190.zip (790 Kb)

    The 16-Bits `C-Kermit 5A(189)' executable CAN be tested under `W32' environments, which is important because the command-line differs a lot;
    the features enumerated above are absent from this older version but i'm
    hoping that's sufficient for me to figure out a few things from it. ;^)

    Perhaps you'd be well advised to read the related thread started in `FdN_TeleGard' by Sean Dennis, any details which i may have forgot could
    have been discussed out there: Sean is also an `OS/2' SysOp, after all.

    Salutations, :)

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


    ... `MS-DOS v7.10a'+`RTSPkt v3.18'+`RLFossil v1.23'+`MS-Kermit v3.16'...
    ___ MultiMail/MS-DOS v0.45 - Trying to 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)
  • From mark lewis@1:3634/12 to Michel Samson on Thu Nov 4 15:00:00 2004
    Hi Mark,

    About "Pure DOS TelNet Kermit" of November 3:

    ...i (finally) saw that you had uploaded a private package to me...
    ...you still wanting to do/try something with it... ...?...
    I didn't change my mind... ...though... ...i forgot what's in...
    ...you marked it as "sysop's eyes only"...

    It would help if you could remind me the file-name of
    this archive.

    KERMIT!.ZIP - with a description about gathered from carsomething in canada...

    I was just not wanting you to be jaded about sending some info this
    way and then nothing ever being done with it...

    You must be the 3rd `OS/2' SysOp with who i discussed
    `Kermit' this year, so far;

    this year? try in the last 2 years ;)

    consider that you're likely
    to get the better part of the deal since i
    identified/collected some of the needed information already
    and it wouldn't be a 1st time, anyway (i've been "jaded"
    before)... %-)

    well, the archive data is 6 june 2002 and your first logon to my system was the
    month before ;)

    the archive contains three .bat files and two ini files... the .bat files appear to be executing the mskermit stuff...

    My biggest problem is to decide if i should go with native OS/2
    flavor of whatever or go with a DOS flavor...

    That's my problem as well: i don't run a BBS and much
    less `OS/2'.

    i can understand... i can also understand how the BBS side settings can be different than the user's side settings...

    Here's what i learned. `C-Kermit 5A(190)' of November
    16, 1994 was the last release WITH A 16-BITS `OS/2' VERSION
    INCLUDED. I can't do any test with it in a `W32' DOS box
    but it seems the "ReSend" feature (which would support
    Transfer Recovery), the passing of File Attributes and the
    ~REXX~ interface were finally supported there. The LAST
    RELEASE was `C-Kermit 5A(191)' of April 24, 1995; you get
    NO 16-BITS VERSION IN IT and don't expect too much out of a
    32-Bits build because of a bug, i'm told. In short, forget
    about a cure for bugs introduced in `C-Kermit 5A(190)'!

    depending on the bugs, they may not even come into play on some setups...

    As far as i'm concerned i bet on `MS-Kermit' - a much
    better choice in terms of maturity: October 12, 2003 for
    v3.16 and September 17, 1997 for v3.15 - and it's also the
    2nd most stable DOS program i ever used...

    ok...

    that would also limit me to implementing the DOS version... i might have to see
    if i can locate an OS/2 version like others are using... maybe i'll see about getting hold of juge and getting hold of what he has...

    If you go for the later then i recommend that you take a
    peek here:

    http://fidonet.sensationconten t.com/echomail/searchlight/f742a4263556c006.html

    This late setup includes all of the ~URL~s you'd need, in
    any case.

    ;-)

    The one archive which i didn't include yet can be found
    right here:

    ftp://kermit.columbia.edu/kermit/archives/cko190.zip (790
    Kb)

    The 16-Bits `C-Kermit 5A(189)' executable CAN be tested
    under `W32' environments, which is important because the
    command-line differs a lot; the features enumerated above are
    absent from this older version but i'm hoping that's sufficient
    for me to figure out a few things from it. ;^)

    the command line is generally where i set most things to run from... i have a few protocols that have seperate ini files referenced on their command lines, though... hslink and hydracom being two that i can think of right offhand...

    Perhaps you'd be well advised to read the related thread
    started in `FdN_TeleGard' by Sean Dennis, any details which i
    may have forgot could have been discussed out there: Sean is
    also an `OS/2' SysOp, after all.

    yes, i'm aware... i don't carry the telegard echo, though... might be able to locate some info in the archives at fidosensation...

    )\/(ark
    * Origin: (1:3634/12)
  • From MICHEL SAMSON@1:10/345 to MARK LEWIS on Fri Nov 5 08:06:00 2004
    Hi Mark,

    About "Pure DOS TelNet Kermit" of November 4:

    ...i (finally) saw that you had uploaded a private package to me...
    ...you still wanting to do/try something with it... ...?...
    I didn't change my mind... ...though... ...i forgot what's in...
    ...you marked it as "sysop's eyes only"...
    It would help if you could remind me the file-name of this archive.
    KERMIT!.ZIP - with a description about gathered from carsomething...

    Right, i see what's in it now. It's from work i done with Stephane Garceau, which has evolved after i tried to adapt it for `SynchroNet'...

    I was just not wanting you to be jaded about sending some info this
    way and then nothing ever being done with it...
    You must be the 3rd `OS/2' SysOp with who i discussed `Kermit' this
    year, so far; consider that you're likely to get the better part of
    the deal since i identified/collected some of the needed information already and it wouldn't be a 1st time, anyway...
    This year? Try in the last 2... Well, the archive date is 6 june
    2002 and your first logon to my system was the month before...

    Sorry... I'm afraid i mistaken you for another SysOp (Marc Lewis)!

    My biggest problem is to decide if i should go with native OS/2...
    That's my problem as well: i don't run a BBS and much less `OS/2'.
    The archive contains three .bat files and... I can also understand
    how the BBS side settings can be different than the user's side...

    It's even more complicated than that. If you take `MSK.INI', which
    i mentioned here abundantly, euh... you'll notice that it seemed useful
    to separate the settings for DownLoad and UpLoad in order to simplify my
    task when doing adjustments. I'm still unable to explain it to this day
    but assymetry works and that's why the few separate macros can help - at
    least during the initial setup phase! `Kermit!.ZIP' is an old sample...

    Here's what i learned. `C-Kermit 5A(190)' of November 16, 1994 was
    the last release WITH A 16-BITS `OS/2' VERSION INCLUDED. ...forget
    about a cure for bugs introduced in `C-Kermit 5A(190)'!
    Depending on the bugs, they may not even come into play...

    Yes, this is my hope too so i'd favour that both drivers are tried.

    As far as i'm concerned i bet on `MS-Kermit'...
    That would also limit me to implementing the DOS version...

    Sorry, i'm unsure what you got in mind but i'm ready to discuss it.

    ;-)

    I might have to see if i can locate an OS/2 version like others are using... Maybe i'll see about getting hold of juge...

    It's a part of what i learned. I've been refered to `PM2You41.ZIP:

    http://home.swipnet.se/ridax/pm2you41.zip (1M4)

    There's NO `Kermit' code in `PM2You v4.1', `OS2FTP.EXE' DEPENDS on:

    ftp://kermit.columbia.edu/kermit/archives/cko190.zip
    `C-Kermit 5A(190)', 790 Kb, November 16, 1994

    ftp://kermit.columbia.edu/kermit/archives/cko191.zip
    `C-Kermit 5A(191)', 620 Kb, April 24, 1995

    For all i know, `Install.CMD' renames `CKOKer16.EXE'/`CKOKer32.EXE'
    as `CKermit.EXE' (whichever suits your `OS/2' version)... Configuration
    is done using `C-Kermit.INI' (or perhaps `CKermit.INI', i don't recall),
    but a secondary .INI file (i think it's `CKerMod.INI') is where you must
    search for `Kermit' features as packet-size, etc. I wonder if `C-Kermit
    v8' wouldn't be a better choice for an `OS/2' installation, in any case.

    The 16-Bits `C-Kermit 5A(189)' executable CAN be tested under `W32' environments, which is important because the command-line differs...
    The command line is generally where i set most things to run from...

    `Kermit's command-line, i meant. `MS-Kermit' and `C-Kermit' differ significantly and only their .INI's content is *PARTLY* interchangeable.

    I have a few protocols that have seperate ini files referenced on
    their command lines, though... hslink and hydracom being two...

    At this stage it's time to discuss the internal `Maximus' variables
    which will be used on the external protocol driver command-lines. There
    may be a good reason to make `PM2You v4.1' launch `C-Kermit' but i can't imagine why it isn't preferable to run `C-Kermit' directly instead. I'm
    afraid only Bob Juge can explain it to you, that's where SysOp expertise
    is most wanted! It may be doing what .BAT files could do a couple years
    ago on systems running another OS (?), i'm dependent on your input here.

    ...you'd be well advised to read the related thread started in `FdN_ TeleGard' by Sean Dennis, any details which i may have forgot could
    have been discussed out there: Sean is also an `OS/2' SysOp...
    I don't carry the telegard echo... Might be able to locate some
    info in the archives at fidosensation...

    My last posts failed to propagate to sensationcontent lately, i was
    unable to connect to this ~WEB~ site yesterday but i'll be patient. ;-)

    Salutations,

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


    ... `MS-DOS v7.10a' + `RTSPkt v3.18' + `RLFossil v1.23' + `{Commo} v7.7'
    --- MultiMail/MS-DOS v0.45 - If only TelNet OLMR BBSing were *UNIVERSAL*
    * Origin: BBS Networks @ www.bbsnets.com 808-839-6036 (1:10/345)