Subj : SBBS/W32 Kermit SABOTAGE To : Michel Samson From : Rob Swindell Date : Tue Oct 19 2004 03:44 am Re: SBBS/W32 Kermit SABOTAGE By: Michel Samson to Rob Swindell on Tue Oct 19 2004 05:07 am > About "Pure DOS TelNet ZMoDem" of October 16: > > RS> Have you setup gkermit... ...synchro.net/docs/kermit.txt > MS> ...i wonder if you will agree to remove all mentions relative to me > MS> on `SynchroNet's ~WEB~ site... ...it makes more sense to just point > MS> at the UpDate: http://public.sogetel.net/bicephale/MSK.INI > RS> Sure, no problem. Unfortunatley, this .INI file is not a "drop-in" > RS> replacement for the kermit.ini I've provided for Synchronet sysops. > > It appears you got much more than just a Drop-In Replacement issue: > > __________________________________________________[ `Kermit.TXT v1.5' ]_ > RS> These instructions are specifically not authorized, approved, > RS} condoned, or verified by Michel Samson, the self-appointed Kermit > RS} expert and evangelist. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > This single sentence is flawed, just like the rest. The person who > could request action regarding Winston Smith is Winston Smith himself so > i have to wonder: did he ask not to be associated with this SABOTAGE as > well?! The sentence you quoted has nothing to do with Winston Smith. Why are you bringing any innocent bystander into this? > Regarding your "Evangelist" token, some readers might ask who's who > in the long run! You're favourite game is "break the toys of others" so > my quote below, from `Kermit.UPD', "GENERAL SETUP" (26.2), euh... would > sound quite appropriate at this time: "Kermit commands appearing in the > BBS's MSKERMIT.INI file might be..." - yes, read MIGHT as in OPTIONAL or > SUGGESTED - Indeed. If I thought they weren't optional, I would've included all the options listed in the file. You don't need to teach me how to read a document. > why keep refering to it, euh... almost "religiously" then?! I only refer to it once, in my kermit.ini file. I have no idea what you're talking about. If anyone "keeps referring" to thing "religiously", it's you, you weirdo. > MS> ...incompatible with Wayne Warthen's `Kermit for Windows'... > RS> ...this point is moot. ...no "transfer recovery" is possible. > > What's "moot" is your decision not to take into account suggestions > such as the following which comes from `Kermit.UPD' (same 26.2 section): > > The BBS software should invoke MS-DOS Kermit with "command- > line arguments", i.e. commands to be executed, given on the > same line... If you need to issue more commands than will fit > on the command line, simply collect them into a file, and then > --> invoke Kermit with a TAKE command... Communication parameters > --> should be given on the Kermit command line for each session, Why should I bother with the "TAKE" command? The "-f kermit.ini" option works just fine. Why don't *you* remove the redundant "Set Port FOSSIL 1" from your command-lines and put it in your MSK.INI file instead? Then your command-lines would fit in the space alloted without requiring Mickey Mouse stunts like renaming `Kermit.EXE' as `MSK.EXE' > `Kermit' as installed on `SBBS/W32' is real SABOTAGE; `Kermit.UPD' > shows macro examples in this very same passage (26.2) and yet i've never > seen any macro in your own .INI setup versions, which is coherent with a > lack of experience - and objectivity - to say the least! :( OH MY GAWD, I DON'T HAVE ANY MACROS!?!? For shame. I must go create some immediately, or Michel will think I don't know what I'm doing!!! > Your over- > simplified setup makes it COMPLICATED to create any `Kermit.INI' Drop-In > Replacement which would render `Kermit' as "straightforward" as `ZMoDem' > otherwise - and it makes the *1* `Win-16/32' FreeWare client USELESS!... > ^^^^^^^^ I'll have to download this client and test for my self someday. In the mean-time, HyperTerminal (FreeWare), and Kermit-95 works just fine. > That's only a sample of what you chose to ignore, i have a few more > features waiting. Oh, by the way... I meant D/L Recovery for *BBSers*! > > Self-centered SysOps would wait long enough for the fog to clear up > and remind themselves that no users will be left to argue, eventually... blah blah blah > In the meantime, even if BBSers living in remote locations can hope > for High-Speed INet access, someday, i have to warn against `Kermit.INI' > since it imposes your own preference ("Send" vs "ReSend") If RESEND can be used in place of SEND, always, that's great. It's unclear from the kermit docs if this is the case. In your suggested configuration, you have 2 different command-lines for SEND and RESEND (yuck). File recovery should be the default mode (if the file exists) and the BBS should not require 2 different command-lines for the user to be able to resume an aborted download. > and `WWKfW-16/ > 32' is made to hang the session! This situation lasted for over a year, > who did this SABOTAGE serve, exactly?... Yes, our whole lives are moot, > but BBSers must be FREE to evaluate `Kermit' for their own, nonetheless. Well if you want to point out the exact items in the KERMIT.TXT that prevent this from happening, please do so. Otherwise, leave me alone. > MS> Character Translation which makes it possible to use ~ASCII~ UpLoad > MS> for pre-writen text from a foreign environment isn't available. > RS> Perhaps we have different definitions of "ASCII Upload", but my > RS> definition is just raw ASCII, terminated by a Ctrl-Z char usually. > > I'd call it ~ASCII~ UpLoad on *ONE* side only, obviously. I have no idea what you mean. Which side only? Both sides have to agree on the protocol used (or *no* protocol, in the case of "ASCII upload"). > I repeat > the request that you remove my name from your ~WEB~ site including here: Your request has been noted. > In addition, my late revision built from what you rejected is here: > > --> http://public.sogetel.net/bicephale/MSK.INI > > Should you ever come to care to open the door to long-term projects I don't care to open the door to any projects (long-term or otherwise), if you are involved in them, but thanks for the offer! digital man Snapple "Real Fact" #180: The first VCR was made in 1956 and was the size of a piano. .