Subj : SBBS/W32 Kermit SABOTAGE
To : MIKE POWELL
From : MICHEL SAMSON
Date : Tue Nov 16 2004 08:48 am
Hi Mike,
About "SBBS/W32 Kermit SABOTAGE" of November 15:
MS> ...you and your guru remain consistently silent relatively to the
MS> VERY WEAK INTERFACE between `SynchroNet' and `MS-Kermit'...
SH> ...breaking "kermit" because the interface is somehow "weak". [?]
MS} Wrong, he's been warned of the consequences of rejecting my .INI on
MS} 1st sight and hence his decision made him responsible for disabling
MS} some of the `Kermit' features - SysOps & BBSers *DID* complain...
MS> I also informed him that hanged sessions fail to be detected (the
MS> "CARRIER" signal may be stuck), that message-pointer UpDating may be
MS> wrong and/or that users are at risk to be kept out of an `SBBS'
MS> system for a day. This matter of a weak external protocol-driver
MS> interface only makes things worst as he won't even try to address it
MS> but `Kermit' was made crippled because of "fluff" he has rejected...
MP> If goofing up the setup could result in these things, they sound
MP> like good reasons not to risk setting up Kermit at all.
That's why i refer to Rob Swindell's `Kermit.INI' as SABOTAGE! The
`MS-Kermit.EXE' external file-transfer protocol-driver isn't involved, a
"NO CARRIER" condition would make it react (*IF* only one occured) and i
also tried to manage with Error Trapping relative to it but Rob rejected
my contribution... It's his task to ensure that his SoftWare remains in
control, `SBBS' is responsible for supporting the ~FOSSIL~ interface and
it runs the drivers, not the opposite, after all! I'd most probably get
the same results reproduced using ANY OTHER EXTERNAL PROTOCOL-DRIVER, do
you see the larger picture now? This `SBBS' issue is out of my hands...
Salutations,
Michel Samson
a/s Bicephale
... Rob's SBBS/Kermit: spend spare-time just to find out why it stalls!
--- MultiMail/MS-DOS v0.45 - Trying to make TelNet OLMR BBSing UNIVERSAL
* Origin: BBS Networks @ www.bbsnets.com 808-839-6036 (1:10/345)
