| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | MS-Kermit on BBSes |
Hi Ben, [re-posting my July 30 message]
About "MS-Kermit on BBSes" of July 29:
MS> ...automated File Transfer only. I am testing C-Kermit 8.0.209...
MS> ...`C-Kermit' is very well featured, and bloated as a result...
MS> ...tiny FreeWare... http://kermit.wwarthen.com
BR> Bloated is relative at 233MHz & up... ...lite is fine but the lite
BR> commands subset would need to work identical... Should work nice
BR> for Wins 3.1... ...since it's a 16-bit app.
It (lets call it `WWWK'), euh... can hardly support the comparison
given the miniature size. `WWWK' would only suit the needs of some user
who wants to transfer .QWK/.REP message-packets, for example; he should
also be able to enjoy his ~VT-102~ sessions on remote `Lynx' browsers or
"Shell" environments but simplicity comes at a price. Though, it's FREE
and there are versions for all the `Windows' flavours one can use. This
won't be your next `Kermit' protocol driver since i haven't seen `WWWK's
source-code on the ~WEB~ site, as i recall, but `K95's co$t is no longer
an excuse to tell BBSers that no one is going to use `Kermit' because of
_that_! Preconceptions are tough to undo but i guess it's possible, one
step at a time. `WWWK' is the argument that was lost along the path: i
can now tell SysOps/BSSers that co$t isn't reason enough to ignore it...
I don't know why but if you only need transfers `G-Kermit' could be
a better choice. This isn't my own saying but that of a `DOVE-Net' guy.
MS> `ZMoDem' code from an outside source was added to `K95'...
BR> I have ZModem myself, licensed directly from Omen Tech...
If you have both source-codes and you know how to use it then you'd
be able to combine them in a single application but you won't be allowed
to publish your executable because of the Columbia author rights, no?...
8^o
BR> I used Lynx for quite some time until I discovered the Links
BR> browser, which handles Tables & Frames quite nicely in Text mode,
BR> so I have both now . I do still use Lynx for Text browsing...
My case as well... I liked `Links' when i was trying `BasicLinux';
as for `Lynx', i often use remote installs via ~TelNet~ for the speed...
BR> My Editor (The Hessling Editor, THE, a super IBM XEdit clone) also
BR> works under every platform I have here...
Finding a text editor which fits my needs was a long quest, none of
the ShareWare i could try was well featured and sturdy at the same time;
it also had to be quite easy on the processing resources since i've been
a true LEGACY user not so long ago - an application had to be "perfect"!
I quit searching when i found `The SemWare Editor Junior v4.0' as i
no longer feared crashes (a 8088 4.77 Mhz boots slowly, you know!), etc.
:)
I understand the attachment to an environment only too well, it was
the reason why i felt so disapointed after each new `Windows' release!!!
BR> ...my BBS software only allowed Text mode transfers...
BR> What about a .QWK door...
BR> ...at 300 Baud (1200 if you were a rich kid) it made little
BR> difference, IMHO.
I still got a "dumb" 300 bps MoDem somewhere but what about now?...
BR> ...Upload a Text file directly to an online Message Edit session (as
BR> WC!4 allows) ASCII works well. Saves typing Online time.
Yes, there were instances when i posted that way (because of a lack
of `Kermit' support)... It worked well for single documents but i tried
to avoid it for one hundred lines multi-part posts: the headers were my
worst nightmare, it was too easy to mess up! `Kermit' was my liberator,
it allowed me to write for a couple days and post the .REP in seconds...
:)
As you may know, `ZMoDem' is no success story over ~TelNet~ in DOS!
%-b,
BR> My Download Protocol options here include... ...Kermit... I can
BR> even provide a custom/new Protocol option with an external client if
BR> that's what it takes... ...I pride myself in File management/access
BR> capabilities and definitely see the need to support as many...
Let me give you the same advice as for every other `WC' SysOp: the
internal 3rd-party `Kermit' protocol implementation is hurting `Kermit's
reputation a big deal so, please, remove that thing! `WC' appears to be
everywhere and everywhere it's the same problem - `WC Kermit' is useless
and when someone dares try it they automatically conclude `Kermit' isn't
worth a thought and they walk away from it for ever! Give them a chance
to experience the post-1985 `Kermit' protocol as it should be, the .INIs
i've published are for that purpose, specifically. Fight preconceptions
by not being a part of it - no insult intended - or better, by using the
`MS-Kermit v3.15+' protocol drivers; i'll beg of you if i must! P-) I
would visit Positronium if it was a local call, sorry; but anyway, it's
not necessary to take my word for it, ask around! Begin with Winston...
Salutations, ;^)
Michel Samson
a/s Bicephale
... And then there were none, a footnote in the history of the InterNet.
--- MultiMail/XT v0.42 - Who wants to make TelNet OLMR BBSing UNIVERSAL?
* Origin: BBS Networks {at} www.bbsnets.com 808-839-6036 (1:10/345)SEEN-BY: 633/267 270 @PATH: 10/345 106/1 2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.