Hi Matt,

About "Topic steering" of November 28 in two parts:

Tell me more about your 'commo' program, you say it will do
a ppp dial up connection and telnet?

I've been made aware of the two posts you addressed to me elsewhere
but it happens that those who took over the echo got me banned because i disagreed with Off-Topic discussions going on forever - hence the "Topic steering" title... %-b, I'll post replies here, if you don't mind! :>

-=*=-

1st of all, the thread to which you refer should have made it clear
that `{Commo}' ISN'T FROM ME so i gather you didn't go thru it but i was
just expressing my gratefulness after i read that the author passed out.

Now, relatively to your topic, it will be somewhat more appropriate
to refer to my `LSPPPDlr' "GlueWare". :) So, what is `LSPPPDlr'? What
does it accomplish?... Well, i've proved that ~TelNet~ BBSing should be ACCESSIBLE TO PRACTICALLY EVERYONE, despite the limitations of their PC;
i used my 8088 PC to BBS via ~PPP~ for a year (during 2000), actually...

I've been experimenting with several in my attempts to do telnetting
into bbs'ing, but haven't found any that will let me download files
from bbs, other than kermit for DOS, which is painfully slow.

Have you ever been curious about combining `RLFossil' to `{Commo}'s `ZMoDem' or `MS-Kermit's same-name file transfer protocol? This is what allowed me to transfer my .QWK/.REP (.ZIP) binary files under "pure DOS"
setups for years... I also tried to share my findings whenever possible
but i believe nobody else expressed that much interrest since my project started!... It would be a pleasure to discuss it further, to be honest.

%-)

If you can point me to a download of commo... I'd like to try this
commo terminal program of yours...

My ~WEB~ site remains active for such occasions and i made the site bilingual to help people forget about my French-Canadian origins, simply
follow the "English Version" link!!! I thought some hands-on experience
could save us time and energy so i finally published `2K3UpDat.ZIP', for
your own convenience. Search for my "GlueWare" link from the main page,
then use the "2K3UpDat" link on my 2003 Up-Date page or type this ~URL~: http://public.sogetel.net/bicephale/2K3UpDat.ZIP (140 Kb, 2004-Dec-3)...

I mentioned my UpDate page as well because the links over there are
going to ease the replication of my setup and today's archive is to make
my late additions (like the configuration "Wizard") available too. This GlueWare can help DOS BBSers in managing with packet-drivers but there's
been so little feedback i waited for an intervention like yours to get a
new archive On-Line - which explains why that's no clean version... ;-)

Compared to the previous edition, the [F10] key is now redefined so
that the macro short-cuts menu has a more intuitive location but changes
like this one may not reflect in the documentation yet. The router item
(which i added after i practically stopped using ~PPP~ DialUp this year)
is another undocumented feature example and it isn't the definitive form
anyway (i'd like to select an ~NIC~ from the dialing directory, like the
rest) but i still have hope that it will be sufficient to get you going;
the `LSPPPDlr' UpDate gives you access to the setup i have, in any case.

The `LSPPPDlr' GlueWare concept observes author rights, which means `{Commo}' ISN'T part of the archive even if it's the main engine. There
are only batch-files and macros in `LSPPPDlr' but i tried to ease things
up a bit (at the begining it was a Stand-Alone BBS/INet diskette and the
setup was even more complicated)... `{Commo}'s versatile macro-language
makes customization simple, this is what allowed me to configure a ~PPP~ packet-driver, set `WatTCP' DOS environment variables and launch `EPPPD'
or `LSPPP' in a breeze. `{Commo}' seems to be rejuvenated, as a result.

Both local DialUp or ~TelNet~ BBS access are now allowed and i also wrote/read ~E-Mail~s/~News~ with it (i still do ~E-Mail~s on occasions).

-=*=-

Oh, euh... I appreciate the feedback but use my true name, PLEASE!

%-)

Salutations,

Michel Samson <- Not "Michael"...
a/s Bicephale ^
http://public.sogetel.net/bicephale/


... Used: LEGACY DOS Packet-Driver + RLFossil + {Commo}/`ZMoDem' + .QWK
___ MultiMail/MS-DOS v0.45 - Lets try TelNettable BBSes with OLMR doors!
--- Maximus/2 3.01
* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)

Hi Matt, [2nd try: this post didn't fully propagate]

About "Topic steering" of November 28 in two parts:

Tell me more about your 'commo' program, you say it will do
a ppp dial up connection and telnet?

I've been made aware of the two posts you addressed to me elsewhere
but it happens that those who took over the echo got me banned because i disagreed with Off-Topic discussions going on forever - hence the "Topic steering" title... %-b, I'll post replies here, if you don't mind! :>

-=*=-

1st of all, the thread to which you refer should have made it clear
that `{Commo}' ISN'T FROM ME so i gather you didn't go thru it but i was
just expressing my gratefulness after i read that the author passed out.

Now, relatively to your topic, it will be somewhat more appropriate
to refer to my `LSPPPDlr' "GlueWare". :) So, what is `LSPPPDlr'? What
does it accomplish?... Well, i've proved that ~TelNet~ BBSing should be ACCESSIBLE TO PRACTICALLY EVERYONE, despite the limitations of their PC;
i used my 8088 PC to BBS via ~PPP~ for a year (during 2000), actually...

I've been experimenting with several in my attempts to do telnetting
into bbs'ing, but haven't found any that will let me download files
from bbs, other than kermit for DOS, which is painfully slow.

Have you ever been curious about combining `RLFossil' to `{Commo}'s `ZMoDem' or `MS-Kermit's same-name file transfer protocol? This is what allowed me to transfer my .QWK/.REP (.ZIP) binary files under "pure DOS"
setups for years... I also tried to share my findings whenever possible
but i believe nobody else expressed that much interrest since my project started!... It would be a pleasure to discuss it further, to be honest.

%-)

If you can point me to a download of commo... I'd like to try this
commo terminal program of yours...

My ~WEB~ site remains active for such occasions and i made the site bilingual to help people forget about my French-Canadian origins, simply
follow the "English Version" link!!! I thought some hands-on experience
could save us time and energy so i finally published `2K3UpDat.ZIP', for
your own convenience. Search for my "GlueWare" link from the main page,
then use the "2K3UpDat" link on my 2003 Up-Date page or type this ~URL~: http://public.sogetel.net/bicephale/2K3UpDat.ZIP (140 Kb, 2004-Dec-3)...

I mentioned my UpDate page as well because the links over there are
going to ease the replication of my setup and today's archive is to make
my late additions (like the configuration "Wizard") available too. This GlueWare can help DOS BBSers in managing with packet-drivers but there's
been so little feedback i waited for an intervention like yours to get a
new archive On-Line - which explains why that's no clean version... ;-)

Compared to the previous edition, the [F10] key is now redefined so
that the macro short-cuts menu has a more intuitive location but changes
like this one may not reflect in the documentation yet. The router item
(which i added after i practically stopped using ~PPP~ DialUp this year)
is another undocumented feature example and it isn't the definitive form
anyway (i'd like to select an ~NIC~ from the dialing directory, like the
rest) but i still have hope that it will be sufficient to get you going;
the `LSPPPDlr' UpDate gives you access to the setup i have, in any case.

The `LSPPPDlr' GlueWare concept observes author rights, which means `{Commo}' ISN'T part of the archive even if it's the main engine. There
are only batch-files and macros in `LSPPPDlr' but i tried to ease things
up a bit (at the begining it was a Stand-Alone BBS/INet diskette and the
setup was even more complicated)... `{Commo}'s versatile macro-language
makes customization simple, this is what allowed me to configure a ~PPP~ packet-driver, set `WatTCP' DOS environment variables and launch `EPPPD'
or `LSPPP' in a breeze. `{Commo}' seems to be rejuvenated, as a result.

Both local DialUp or ~TelNet~ BBS access are now allowed and i also wrote/read ~E-Mail~s/~News~ with it (i still do ~E-Mail~s on occasions).

-=*=-

Oh, euh... I appreciate the feedback but use my true name, PLEASE!

%-)

Salutations,

Michel Samson <- Not "Michael"...
a/s Bicephale ^
http://public.sogetel.net/bicephale/


... Used: LEGACY DOS Packet-Driver + RLFossil + {Commo}/`ZMoDem' + .QWK
--- MultiMail/MS-DOS v0.45 - Lets try TelNettable BBSes with OLMR doors!
* Origin: BBS Networks @ www.bbsnets.com 808-839-6036 (1:10/345)

Hello Michel,

A thousand pardons for not getting your name right, also, I've never done a whole lot of posting on fidonet or echomail as many have over the years, so if I miss things that should have been obvious or unknowlingly breach some sort of
'echo etiquette' that I am unaware of, I ask a little tolerance and leeway from
those more experienced than I, it seems that frequently in the past I'll post a
comment and the next thing I know I've got people jumping all over me for saying the wrong thing in the wrong post at the wrong time or something or another, some of it even seems a bit snippy and mean spirited at times, and I don't see how that benefits anybody, after all, if there is something that I, or someone else doesn't know, should we be afraid to ask a question?

At any rate, YES, trying to figure out a way to dial up my ISP using a DOS ppp connection and telnetting into a BBS and being able to go to the files area and
download using zmodem is something I've been intrigued about for a long time. I
really have to struggle sometimes to get DOS ppp connections up and running, but I can generally follow the logic of what has to be done and make it work.

I've made a note of your website, and as soon as I finish this posting I'll take a look at what you've got. I'm actually using BANANACOM right now, dialed into the last remaining BBS here in the Houston area.

regards,
Matt
--- Maximus/2 3.01
* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)

Hi Matt,

About "LSPPPDlr 2003" of December 5:

Tell me more about your 'commo' program...

...`{Commo}' ISN'T FROM ME...

...I ask a little tolerance and leeway...

Granted. I've been the moving target of others so often these late
years i regularily feel the need for this myself! %-) Most of the guys
who address me usually sound like they've been "prepared" so i can't but welcome you... 8-) Anyway, i believe the thread can be read from here:

http://fidonet.sensationcontent.com/echomail/dos_internet
http://www.fidonet.m.nu/echomail/area/DOS_INTERNET/LIST=1

...the next thing I know I've got people jumping all over me for
saying the wrong thing in the wrong post at the wrong time...

That feels familiar enough for me who has been posting on `FidoNet'
for some time, which is why i refrained from warning you against using a `BBBS', `WildCat!' or similar pre-1985 3rd-party `Kermit' implementation
when i read you about "Kermit for DOS" being "painfully slow": having a
chance to correspond with DOS LEGACY BBSers like myself is so unique the warning could wait my next post i thought! It's refreshing reading you.

8,-b

...if there is something that I, or someone else doesn't know,
should we be afraid to ask a question?

If my reply makes you uncomfortable there's something wrong, either
you never heard of me or what you know is somewhat biased... `LSPPPDlr' wouldn't still be On-Line today if i didn't really want to save you from
the frustration; ask me questions and i'll answer as honestly as i can.

...trying to figure out a way to dial up my ISP using a DOS ppp
connection and telnetting into a BBS and being able to go to the
files area and download using zmodem is something I've been
intrigued about for a long time. I really have to struggle...

An image is worth a thousand words. You'll find that your transfer
rates depend on the ~ISP~, the HardWare/SoftWare and the BBS being used;
i've been lucky with all my ~ISP~s since none of them disabled a packet-
driver by doing validation via ~MS-CHAP~ exclusively (it isn't supported
by `EPPPD'/`LSPPP'), for example... as for the file transfer protocols,
their availability and suitability will depend on your HardWare/SoftWare
in combination with the remote host implementations. `{Commo}'/`ZMoDem'
seems OKay on my P-200 Mhz MMX but it doesn't "degrade" as gracefully as `Kermit' on more modest systems (unless `BBBS-Kermit'/`WC-Kermit' is the
only alternative to it)... I have 8088 PCs and later, let me know about
your setup and i'll try to tell you what .ZIP cps rate you can dream of.

;^)

...I'll take a look at what you've got. I'm actually using
BANANACOM right now, dialed into the last remaining BBS here...

I don't recall re-evaluating `BananaCom' in this century, i do know
i didn't retain it as a candidate when i searched for terminal emulators
with the features required for an external ~PPP~ packet-driver dialer in
any case - which was long before i switched to "Plan-B" (~TelNet~ only).

Luckily, *IF* `BananaCom' supports ~FOSSIL~ interfacing, you should
be able to use your favourite SoftWare without much help from `{Commo}'s `LSPPPDlr' macro: simply generate some `SetPPP.BAT' + `LogIn.BAT' setup
thru `{Commo}'s Wizard then switch to `COMTool'. I must testify that my
8088s made an unforgiving test-bench and that `{Commo}' sure passed this
test, though... Who would start from the ground up anyway? I wouldn't!

I mention ~FOSSIL~ because i don't expect to hear about `BananaCom' supporting ~TelNet~ internally. Is v4 still the last realease there is?

Salutations, ;-)

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


... DOS+TCP/IP+TelNet+ZMoDem/Kermit+.QWK technologies on 8088s or higher
-!- MultiMail/MS-DOS v0.45 - It could make TelNet OLMR BBSing UNIVERSAL!
--- Mail-ennium/32 v2.0-beta-r1
* Origin: Mail-ennium/32 v2 Beta Coming Soon! (1:379/1200.0)

Hi Michel,

To clarify, your responses don't make me uncomfortable at all, far from
it, I was just generally referring to some situations in the past not
related to you...

I checked out your site, and I sort of am 'getting it'. I grabbed IVT
for DOS and sure enough it won't work with a standard packet driver
loaded at 0x60, it seems to require PC/TCP and that's apparently not an
option unless I fork out some dough....

So, I did some digging on my own, and I have come to the conclusion...
and set me straight if I'm wrong, but GENERALLY I would want to do
something along these lines - have lsppp establish a tcp/ip connection
to my ISP, then have RLfossil (which I downloaded and read the docs)
emulate a modem comport so that a terminal program, such as COMMO, or
maybe telemate?? can make the connection, have I got the right concept?
Then I went and downloaded most of the files on your 'glueware' page and
have them still zipped up in a temporary directory, I'm not sure exactly
where to go from here, as I'm not sure exactly where to unzip
everything, but I'll keep studying it.

Anyway, I'll get back to you and I am really excited about the
possiblity of using a DOS machine to telnet into a bbs and actually transferring files with zmodem....

cheers,

Matt

Hi Matt,

About "LSPPPDlr 2003" of December 5:

Tell me more about your 'commo' program...

...`{Commo}' ISN'T FROM ME...

...I ask a little tolerance and leeway...

Granted. I've been the moving target of others so often these late years i regularily feel the need for this myself! %-) Most of the guys
who address me usually sound like they've been "prepared" so i can't but welcome you... 8-) Anyway, i believe the thread can be read from here:

http://fidonet.sensationcontent.com/echomail/dos_internet
http://www.fidonet.m.nu/echomail/area/DOS_INTERNET/LIST=1

...the next thing I know I've got people jumping all over me for
saying the wrong thing in the wrong post at the wrong time...

That feels familiar enough for me who has been posting on `FidoNet'
for some time, which is why i refrained from warning you against using a `BBBS', `WildCat!' or similar pre-1985 3rd-party `Kermit' implementation when i read you about "Kermit for DOS" being "painfully slow": having a chance to correspond with DOS LEGACY BBSers like myself is so unique the warning could wait my next post i thought! It's refreshing reading you.

8,-b

...if there is something that I, or someone else doesn't know,
should we be afraid to ask a question?

If my reply makes you uncomfortable there's something wrong, either
you never heard of me or what you know is somewhat biased... `LSPPPDlr' wouldn't still be On-Line today if i didn't really want to save you from
the frustration; ask me questions and i'll answer as honestly as i can.

...trying to figure out a way to dial up my ISP using a DOS ppp connection and telnetting into a BBS and being able to go to the
files area and download using zmodem is something I've been
intrigued about for a long time. I really have to struggle...

An image is worth a thousand words. You'll find that your transfer rates depend on the ~ISP~, the HardWare/SoftWare and the BBS being used; i've been lucky with all my ~ISP~s since none of them disabled a packet- driver by doing validation via ~MS-CHAP~ exclusively (it isn't supported
by `EPPPD'/`LSPPP'), for example... as for the file transfer protocols, their availability and suitability will depend on your HardWare/SoftWare
in combination with the remote host implementations. `{Commo}'/`ZMoDem' seems OKay on my P-200 Mhz MMX but it doesn't "degrade" as gracefully as `Kermit' on more modest systems (unless `BBBS-Kermit'/`WC-Kermit' is the only alternative to it)... I have 8088 PCs and later, let me know about your setup and i'll try to tell you what .ZIP cps rate you can dream of.

;^)

...I'll take a look at what you've got. I'm actually using
BANANACOM right now, dialed into the last remaining BBS here...

I don't recall re-evaluating `BananaCom' in this century, i do know
i didn't retain it as a candidate when i searched for terminal emulators with the features required for an external ~PPP~ packet-driver dialer in
any case - which was long before i switched to "Plan-B" (~TelNet~ only).

Luckily, *IF* `BananaCom' supports ~FOSSIL~ interfacing, you should
be able to use your favourite SoftWare without much help from `{Commo}'s `LSPPPDlr' macro: simply generate some `SetPPP.BAT' + `LogIn.BAT' setup thru `{Commo}'s Wizard then switch to `COMTool'. I must testify that my 8088s made an unforgiving test-bench and that `{Commo}' sure passed this test, though... Who would start from the ground up anyway? I wouldn't!

I mention ~FOSSIL~ because i don't expect to hear about `BananaCom' supporting ~TelNet~ internally. Is v4 still the last realease there is?

Salutations, ;-)

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

... DOS+TCP/IP+TelNet+ZMoDem/Kermit+.QWK technologies on 8088s or higher
-!- MultiMail/MS-DOS v0.45 - It could make TelNet OLMR BBSing UNIVERSAL!

--- Mail-ennium/32 v2.0-beta-r1
* Origin: Mail-ennium/32 v2 Beta Coming Soon! (1:379/1200.0)

--- Platinum Xpress/Win/WINServer v3.0pr5a
* Origin: FidoTel & QWK on the Web! www.fidotel.com (1:275/311)

Michel,

can you repaste those links here so the next time I come back I can grab
them? I'm actually on my slackware linux box at the CLI prompt and
telnetting into the fidotel bbs to read/reply to my messages right now,
and I'm kind of a linux newbie still.... I think I manage to 'capture'
the URL by holding down the shift key and left mouse button, but I'm not
sure how / where I can paste it to grab it later... maybe an editor like
PICO ??? Argh, these learning curves are something else for me ;/

best
Matt

Hi Matt,

About "LSPPPDlr 2003" of December 5:

Tell me more about your 'commo' program...

...`{Commo}' ISN'T FROM ME...

...I ask a little tolerance and leeway...

Granted. I've been the moving target of others so often these late years i regularily feel the need for this myself! %-) Most of the guys
who address me usually sound like they've been "prepared" so i can't but welcome you... 8-) Anyway, i believe the thread can be read from here:

http://fidonet.sensationcontent.com/echomail/dos_internet
http://www.fidonet.m.nu/echomail/area/DOS_INTERNET/LIST=1

...the next thing I know I've got people jumping all over me for
saying the wrong thing in the wrong post at the wrong time...

That feels familiar enough for me who has been posting on `FidoNet'
for some time, which is why i refrained from warning you against using a `BBBS', `WildCat!' or similar pre-1985 3rd-party `Kermit' implementation when i read you about "Kermit for DOS" being "painfully slow": having a chance to correspond with DOS LEGACY BBSers like myself is so unique the warning could wait my next post i thought! It's refreshing reading you.

8,-b

...if there is something that I, or someone else doesn't know,
should we be afraid to ask a question?

If my reply makes you uncomfortable there's something wrong, either
you never heard of me or what you know is somewhat biased... `LSPPPDlr' wouldn't still be On-Line today if i didn't really want to save you from
the frustration; ask me questions and i'll answer as honestly as i can.

...trying to figure out a way to dial up my ISP using a DOS ppp connection and telnetting into a BBS and being able to go to the
files area and download using zmodem is something I've been
intrigued about for a long time. I really have to struggle...

An image is worth a thousand words. You'll find that your transfer rates depend on the ~ISP~, the HardWare/SoftWare and the BBS being used; i've been lucky with all my ~ISP~s since none of them disabled a packet- driver by doing validation via ~MS-CHAP~ exclusively (it isn't supported
by `EPPPD'/`LSPPP'), for example... as for the file transfer protocols, their availability and suitability will depend on your HardWare/SoftWare
in combination with the remote host implementations. `{Commo}'/`ZMoDem' seems OKay on my P-200 Mhz MMX but it doesn't "degrade" as gracefully as `Kermit' on more modest systems (unless `BBBS-Kermit'/`WC-Kermit' is the only alternative to it)... I have 8088 PCs and later, let me know about your setup and i'll try to tell you what .ZIP cps rate you can dream of.

;^)

...I'll take a look at what you've got. I'm actually using
BANANACOM right now, dialed into the last remaining BBS here...

I don't recall re-evaluating `BananaCom' in this century, i do know
i didn't retain it as a candidate when i searched for terminal emulators with the features required for an external ~PPP~ packet-driver dialer in
any case - which was long before i switched to "Plan-B" (~TelNet~ only).

Luckily, *IF* `BananaCom' supports ~FOSSIL~ interfacing, you should
be able to use your favourite SoftWare without much help from `{Commo}'s `LSPPPDlr' macro: simply generate some `SetPPP.BAT' + `LogIn.BAT' setup thru `{Commo}'s Wizard then switch to `COMTool'. I must testify that my 8088s made an unforgiving test-bench and that `{Commo}' sure passed this test, though... Who would start from the ground up anyway? I wouldn't!

I mention ~FOSSIL~ because i don't expect to hear about `BananaCom' supporting ~TelNet~ internally. Is v4 still the last realease there is?

Salutations, ;-)

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

... DOS+TCP/IP+TelNet+ZMoDem/Kermit+.QWK technologies on 8088s or higher
-!- MultiMail/MS-DOS v0.45 - It could make TelNet OLMR BBSing UNIVERSAL!

--- Mail-ennium/32 v2.0-beta-r1
* Origin: Mail-ennium/32 v2 Beta Coming Soon! (1:379/1200.0)

--- Platinum Xpress/Win/WINServer v3.0pr5a
* Origin: FidoTel & QWK on the Web! www.fidotel.com (1:275/311)

Hi Matt, [posted in `FdN_BlueWave' by mistake]

About "LSPPPDlr 2003" in two parts of December 6:

I checked out your site, and I sort of am 'getting it'.

The site's main purpose is to keep references and archives handy in
my name. Less effort was put on the surrounding words, i'm afraid! ;-)

I grabbed IVT for DOS... ...it seems to require PC/TCP...

^^^^^^
It takes me back to times when no `Waterloo TCP'-compatible packet-
driver (`EtherPPP' for one) was as reliable and as standard as `PC/TCP': `EPPPD'/`LSPPP' FreeWare releases attracted no attention yet. ;-) When
Ruurd Beerstra (author of `IVT') went to the `DOS-INet' echo, some years
later, it already felt lonely mentioning `PC/TCP' so it's no surprize to
find that `IVT' still happens to be of marginal use today. It's too bad
i also felt lonely when i asked for `WatTCP' compatibility, though! %-(

I'd have been glad if Mr. Beerstra had decided that Caldera's `Web- Spyder' ~ODI~ `NetWare' ShareWare stack was a valid compromise for `IVT'
(there are "shims") but no significant feedback justified it neither; i
can thank "spotlight lovers" for all this but what i regret most is that
the `IVT' receipie may never be fully explained, much less transposed...

...connection... ...RLfossil... ...modem comport...

That's what my `LSPPPDlr' GlueWare does (and much more since you'll
have the choice to call a local DialUp BBS, to connect to an ~ISP~ or to ~TelNet~ to a remote system once the packet-driver is loaded), using the
very same dialing directory interface all the time - not to mention that multiple BBS/~ISP~/account entries are allowed, and you only need to run `Commo.BAT' once if, for some reason, `{Commo}' doesn't suit your needs!

...so that a terminal program, such as COMMO, or maybe telemate...

I'd like to comment that `TeleMate' is a nice terminal emulator but
it dumped me to the DOS command-line pronto on occasions so, i concluded `{Commo}' or `MS-Kermit' are more reliable in comparison. The quest for
more versatility is appealing? Feel free to evaluate any other material
if you must but i've tried quite a few of them already... ;-> You only
need to find your MoDem, load the `Wizard' macro and create `LogIn.BAT'/ `SetPPP.BAT' files which will help you to use your favourite SoftWare as
an external dialer for the DOS packet-driver (instead of `COMTool.COM'),
if it's what you have in mind... From `{Commo}'s terminal screen, press [Alt]+[G] if `Commo.SET' hasn't opened already and edit the `por', `bps'
and `com' lines if you wish; the Serial-Port menu will appear after you pressed the [Escape] key (just note that changes take effect immediately
in that menu while `Commo.SET' modifications done from `{Commo}' require
a restart to be taken into account), simply press [1]-[8], then [M] and/
or [I] as required. When the MoDem finally responds, access the `LSPPP' Configuration Wizard by pressing [F10] (from `{Commo}'s terminal screen)
and by choosing the corresponding item in the short-cut menu. A dialing directory entry will be created once you are done with the questionaire.

Passed your 1st successful ~PPP~ connection, you're free to inspect
the configuration files and DOS environment variables to reproduce these manually: a set of files (`LogIn.BAT'/`SetPPP.BAT') should now show up,
after you used the `{Commo}' entry to connect with your ~ISP~, i mean...

`LogIn.BAT' looks for `SetPPP.BAT', executes it and runs `COMTool';
that's where to begin if you must use `BananaCom', `TeleMate' or else as
the external dialer. Now, relatively to `RLFossil', type "RLF ?" and it
will display the syntax which allows you to select `{Commo}', `Conex' or `MS-Kermit' (once you loaded `LSPPP', of course)... `ZMoDem' support is available both in `{Commo}' and `Conex' but `MS-Kermit' makes sense if a
remote server is suitable - which isn't true of implementations as with
the `BBBS' or `WildCat!' BBSes. `MS-Kermit' is a good terminal emulator
but only the same-name transfer protocol works and since `RLFossil' does
not seem to fully comply with the ~FOSSIL~ standard it means no external protocotol drivers (`CE-XYZ', for example) can work, most unfortunately.

...I went and downloaded most of the files on your 'glueware' page
and have them still zipped... ...I'm not sure exactly where to go
from here, as I'm not sure exactly where to unzip everything...

I hesitate to override the directives i published. `PKUnZip' using
the "-d" flag from the root to recreate the directories, `C:\PPP\' being
the main one, typically - `{Commo}' also needs `C:\Recv\' and `C:\Send\'
for transfers; features not directly related to `LSPPPDlr' are found in `C:\Arachne\', `C:\DOS-W32\' and `C:\EtherNet\'. Don't forget the flag!

...I am really excited about the possiblity of using a DOS machine
to telnet into a bbs and actually transferring files with zmodem...

A December 1998 record from SensationContent shows a `Kermit' setup already allowed to transfer files via ~TelNet~ at least six years ago, i
regret that most `Kermit' pre-conceptions persist to this day. `ZMoDem'
which seemed to be possible a while later may be at hand now that you're
going to reproduce the ~TelNet~/`ZMoDem' setup i've adopted myself. ;-)

Can you repaste those links here...

Hummm... The `FidoNet' archives or my `LSPPPDlr' page? Try these:

http://fidonet.sensationcontent.com/echomail/dos_internet
http://www.fidonet.m.nu/echomail/area/DOS_INTERNET/LIST=1

;-)

Salutations,

Michel Samson
a/s Bicephale
http://public.sogetel.net/bicephale/eng/2k3updat.htm


... As *LEGACY* as it might sound `MS-Kermit' flew to the Space Station!
--- MultiMail/MS-DOS v0.45 - Only numbers can make BBSing *UNIVERSAL*...
* Origin: FidoTel & QWK on the Web! www.fidotel.com (1:275/311)

Hi Michel,

Just one more question about PC/TCP in the hopes of getting it to try
the IVT for DOS program. I did some googling and can't find ANY type of downloads for TP/TCP other than 'updates' which require registration
keys, I understand that netmanage.com now supposedly 'handles' it and I
went to the netmanage website and the only mention of it is in the
'Legacy' section, and even there there is no obvious support or sales.
So, does that mean they just retain the 'rights' to it and there is no
way it will ever be available, either as public domain or for sale? is
it just 'hopeless' to try to aquire PC/TCP ????

CHEERS
Matt

--- MultiMail/MS-DOS v0.45 - Only numbers can make BBSing *UNIVERSAL*...

--- Platinum Xpress/Win/WINServer v3.0pr5a
* Origin: FidoTel & QWK on the Web! www.fidotel.com (1:275/311)

Hi Mark,

About "LSPPPDlr 2003" (part 4/4) of December 8:

...could I not just fire it up, cd to c:\rlfossil and run the
RLfossil program and cause it to emulate a comport, my modem is on
com2, mouse is on com 1, so what comport/irq would I use?

Another, other than COM1 or COM2 as they are both in use... perhaps
COM3 with IRQ5... ...don't exit RLFossil since it is the com/modem emulator... if you exit it, the emulation isn't in place anymore...

...no ~IRQ~... `RLFossil' talks to the Packet-Driver and the later
has EXCLUSIVE use of your real MoDem. The packet-Driver itself is
no piece of HardWare... ...an image is worth a thousand words...

But what COM port would one tell {COMMO} or telix or procomm to use
to talk to RLFOSSIL?

`Procomm v2.4.3' doesn't have such a capability, `{Commo} v7.7' and
`Telix v3.51' do support ~INT-14~/~FOSSIL~ Serial-Ports. Since an image
is worth a thousand words, euh... i'll simply use command-line samples:

RLFossil.EXE 2 1 "Commo.EXE /:INT-14 /{*1,,3,V,}"
C:\PPP\RLFossil.EXE 2 1 "Telix.EXE INT14"

There are three parameters found on these `RLFossil' command-lines:
the 0-based Serial-Port number (0=COM1, 1=COM2, 2=COM3 and 3=COM4), next
we define the number of sessions possible (four ~TelNet~ connections are supported simultaneously, in separate/virtual DOS sessions); the 3rd is
where we find the Application's Command-Line (DEFINED BETWEEN BRACKETS).

There's only one HardWare Serial-Port present on my PC but i used a
US Robotics ~ISA~ MoDem (model 0584, product #005687-03) not so long ago
and i consider COM2 to be reserved even if i had to remove my card after
the MoDem lost its ~Flash~ FirmWare... I can start numbering `RLFossil' Serial-Ports from COM3 and up but i only need to emulate one in my case.

;-)

Take note that no genuine `{Commo}' release used the `INT-14' macro
but both packages allow the selection of a ~FOSSIL~ Serial-Port from the Command-Line: in `{Commo}'s case, "*1" in "{*1,,3,V,}" means ~BIOS INT- 14~/~FOSSIL~ Serial-Port at 38K4 bps. I must confess that the matter of
local connection speed (~DTE~, isn't it?) sure sounds somewhat "elusive"
since i get rate peaks around 4K cps (both on `{Commo}' and `Telix') but there's no significant drop when i set `Telix' for a 9K6 bps connection;
if i use `MS-kermit' with `RLFossil' instead then my connect speed shows
as "unknown"... In any case, the Serial-Port `{Commo}' or `Telix' would
use is defined right on `RLFossil's Command-Line!... It's just a matter
of making both pieces of SoftWare agree (and to pick a Serial-Port which
is free, preferably)! ;-) Now, might a HardWare and a ~Fossil~ Serial-
Port coexist by using the same COM number and yet work correctly? There
is such a possibility in a `W32' DOS box when `COM/IP' happens to be the Virtual ~TelNet~ MoDem "Shim", i believe, but my setup is OK as it is...

8-)

Salutations,

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


N.B.: Please, drop me a note when you're ready to try `MS-Kermit' as an
`OS/2' external file-transfer protocol-driver on a `Maximus' BBS!


... In 1981, with some effort, might we have got InterNet access on XTs?
--- MultiMail/MS-DOS v0.45 - Help TelNet OLMR BBSing to become UNIVERSAL
* Origin: BBS Networks @ www.bbsnets.com 808-839-6036 (1:10/345)

[trim]

...no ~IRQ~... `RLFossil' talks to the Packet-Driver and the later
has EXCLUSIVE use of your real MoDem. The packet-Driver itself is
no piece of HardWare... ...an image is worth a thousand words...

But what COM port would one tell {COMMO} or telix or procomm to use
to talk to RLFOSSIL?

`Procomm v2.4.3' doesn't have such a capability, `{Commo}
v7.7' and `Telix v3.51' do support ~INT-14~/~FOSSIL~ Serial-Ports.

interesting... very interesting... i wasn't aware that {COMMO} or Telix has INT14 capabilities... especially Telix and i've been using it since it first appears in the wild...

Since an image is worth a thousand words, euh... i'll simply use command-line samples:

RLFossil.EXE 2 1 "Commo.EXE /:INT-14 /{*1,,3,V,}"
C:\PPP\RLFossil.EXE 2 1 "Telix.EXE INT14"

thanks!! what versions of {COMMO}, Telix and RLFossil are those, please?

[trim]

Take note that no genuine `{Commo}' release used the
`INT-14' macro but both packages allow the selection of a
~FOSSIL~ Serial-Port from the Command-Line: in `{Commo}'s
case, "*1" in "{*1,,3,V,}" means ~BIOS INT-14~/~FOSSIL~
Serial-Port at 38K4 bps. I must confess that the matter
of local connection speed (~DTE~, isn't it?)

hardware to hardware (IE: modem to computer or printer to computer) are DTE as in Data Terminal Equipment... DCE is modem to modem as in Data Communication Equipment...

sure sounds somewhat "elusive" since i get rate peaks around
4K cps (both on `{Commo}' and `Telix') but there's no
significant drop when i set `Telix' for a 9K6 bps connection;

there shouldn't be, either, since the equipment is not hampered by hardware (aka uart) speed limitations/settings...

if i use `MS-kermit' with `RLFossil' instead then my connect
speed shows as "unknown"...

that would seem to indicate that ms-kermit either doesn't have a matching connect speed or doesn't recognise what it may be being told is the connection speed...

In any case, the Serial-Port `{Commo}' or `Telix' would use
is defined right on `RLFossil's Command-Line!...

ok... my bbs does that with telix all the time anyway... when a user logs off, my system fires up telix (only one copy installed on the machine) one which ever com port belongs to that node and runs a script to fetch the session's stats from the modem (ie: fallbacks, retrains, up/downlink speeds, db's at specific frequencies) for later analysis (aka beating the telco with) if needed...

It's just a matter of making both pieces of SoftWare agree
(and to pick a Serial-Port which is free, preferably)! ;-)
Now, might a HardWare and a ~Fossil~ Serial-Port coexist by
using the same COM number and yet work correctly?

yes... FOSSIL ports start at 0 (zero) and the physical address of port0 can be defined differently then the "standard" port addresses... for that matter, if one is handy with debug or other capable software, one can redefine the BIOS table of serial and parallel port addresses that reside at 0040:0000 ;)

ie:

debug

-d 0040:0000
0040:0000 F8 03 00 00 00 00 00 00-78 03 00 00 02 00 80 9F
0040:0010 27 C2 00 7C 02 28 00 20-00 00 22 00 22 00 30 0B
0040:0020 0D 1C 62 30 75 16 67 22-0D 1C 64 20 20 39 30 0B
0040:0030 30 0B 34 05 30 0B 3A 27-30 0B 30 0B 30 0B 00 80
0040:0040 00 00 FF 01 F7 01 00 E0-C8 03 50 00 40 20 00 00
0040:0050 00 11 00 00 00 00 00 00-00 00 00 00 00 00 00 00
0040:0060 07 06 00 D4 03 29 30 7F-03 00 C0 FF CD 1C 0D 00
0040:0070 00 00 00 00 00 01 00 00-14 14 14 28 01 01 01 01
-

you'll note the first line shows F8 03 (small endian format) which is the (general) address of COM1... if i alter that to something else, then programs that look to the BIOS table will go for the new address... each port address is
a 'word' (two bytes) in size... there is only space allocated in the BIOS table
for four words which matches to the four com ports... in the above, the 5th word, 78 03, is the address of the first parallel port ;)

There is such a possibility in a `W32' DOS box when `COM/IP'
happens to be the Virtual ~TelNet~ MoDem "Shim", i believe,
but my setup is OK as it is...

;)

N.B.: Please, drop me a note when you're ready to try
`MS-Kermit' as an `OS/2' external file-transfer protocol-driver
on a `Maximus' BBS!

i'll do that 'cept it'll be on a RemoteAccess BBS since i don't run Maximus "out front" ;)

)\/(ark
* Origin: (1:3634/12)

Hi Mark,

About "LSPPPDlr 2003" of December 11:

...`{Commo} v7.7' and `Telix v3.51' do support ~INT-14~/~FOSSIL~...

Interesting... Very interesting...

`{Commo}' is handy for sure. Its full range of interfaces tells us
how much quality was put in it, i couldn't think of anything else for my external ~PPP~ dialer once i discovered it and the fact that it works as
the ~TelNet~ client too (instead of having to use two separate pieces of SoftWare) only confirms that it wasn't counter-productive to investigate
a while before i became more involved with external dialers, eventually.

8^)

...an image is worth a thousand words... ...command-line samples: RLFossil.EXE 2 1 "Commo.EXE /:INT-14 /{*1,,3,V,}"

What versions of {COMMO}, Telix and RLFossil are those, please?

As i mentioned above, `{Commo}' is version v7.7 (the last one there
was before its source-code and author both disapeared). As for `Telix',
i'm refering to version 3.51 but you tell me if it's the last release...

;^)

I must confess that the matter of local connection speed (~DTE~,
isn't it?) sure sounds somewhat "elusive" since i get rate peaks
around 4K cps (both on `{Commo}' and `Telix') but there's no
significant drop when i set `Telix' for a 9K6 bps connection... if
i use `MS-kermit' with `RLFossil' instead then my connect speed
shows as "unknown"... In any case, the Serial-Port `{Commo}' or
`Telix' would use is defined right on `RLFossil's Command-Line!...

...the equipment is not hampered by hardware (aka uart) speed... ...ms-kermit either doesn't have a matching connect speed or doesn't recognise what it may be being told is the connection speed...

I have found that the behavior of ~BIOS INT-14~/~FOSSIL~ compatible terminal emulators varied significantly when i investigated them but the "unknown" result returned by `MS-Kermit' was said to make perfect sense, according to its maintainers at the Columbia university. From memory, i believe their reasoning was it's the ~FOSSIL~ driver's responsability to
manage it, usually (it sounds about true of `X00', `ADF' and the suite).

My bbs does that with telix all the time... When a user logs off,
my system fires up telix... ...and runs a script to fetch the
session's stats from the modem...

BBSes depend on a fully compliant level 5 ~FOSSIL~ driver which can support application swapping even when the Serial-Ports are still "Hot",
i wish `RLFossil' were compliant enough to support the use of a `ZMoDem' protocol driver run from `MS-Kermit's terminal interface, or vice-versa!

8,-(

Right now, i can "share" connections (alternately) using `LSPPPDlr'
with `MS-Kermit' run as a protocol-driver - when used via `COM/IP' - but
not with `RLFossil' (the later reboots my PC instead)!... I wonder what feedback i'd get from a person like Sylvain Lauzon (he was knowledgeable
enough about `RLFossil' to get me a 8088 built which didn't exist on the
Net), euh... i have to wonder if he wouldn't happen to know where to go
for the source-code or, maybe, even a quick fix. `TelNet Port' suffered
from the same problem when i checked, i may be stuck with this for ever!

%-o

...if one is handy with debug or other capable software, one can
redefine the BIOS table of serial and parallel port addresses...

Back in days when i played with `Z-80' code, a concept like double-
Byte numbers with their most significant Byte last made sense but that's
all history now, i depend on the talent of others for my modest hobby...

;-)

...drop me a note when you're ready to try `MS-Kermit' as an `OS/2' external file-transfer protocol-driver on a `Maximus' BBS!

...on a RemoteAccess BBS since i don't run Maximus "out front"...

Good! 8-) Anyway, i must meditate on the meaning of the riddle...

Salutations, ;-)

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


... Windows made your old AT look better, now it's the other way around!
--- MultiMail/MS-DOS v0.45 - Help TelNet OLMR BBSing to become UNIVERSAL
* Origin: BBS Networks @ www.bbsnets.com 808-839-6036 (1:10/345)

Hi Matt,

About "LSPPPDlr 2003" of December 11:

I pasted/copied all your instructions into a single txt file which I
will probably print out on fanfold paper and drag into the next
room, I have a pentium 90 with just DOS on it and it would be a good machine to dedicate to the lsppp/rlfossil/commo venture.

With my `LSPPPDlr.BAT' file of December 8 you only had to highlight
some archive file-names and ensure their presence when you execute it...

%-)

I already have kermit and it runs okay...

Evaluate it without its internal ~TelNet~ support, using `RLFossil' intead... ...you'll see the point when you compare your cps rates!

I think we've had a discussion in the past about msdos kermit.

Then you'll probably remember that i mentioned the archaic pre-1985 3rd-party implementations being responsible for `Kermit's bad reputation
over the years... Quite honestly, i don't believe that you'll ever make `MS-Kermit' compensate for `BBBS' and `WildCat!' `Kermit' flavours which
many ~TelNettable~ BBSes still keep offering today - most unfortunately!

`MS-Kermit' working with a 128 Kbps InterNet access (thru a router,
on a P-200 Mhz MMX) will be as fast as ~HTTP~ or `ZMoDem' transfers, for
all purposes; the problem is to get a remote system which supports this
and i can't tell what kind of cps rates a better HardWare would allow (i
think i observed beyond 25 Kcps in local ~TelNet~ testing, as i recall).

I'd say `Kermit' is worth a thought in terms of speed; in terms of
of reliability and UNIVERSALITY there's just no doubt in my mind at all.

What will happen if I try your setup and I happen to have other DOS internet stuff (bobcat/arachne/lynx/etc/etc) on the same machine?

I have `Arachne' and `Lynx' working with `LSPPPDlr' routinely. For
all i know, different packages depend on different `WatTCP.CFG' files so
i wouldn't worry too much: in case of trouble reset the DOS environment variables or simply reboot when required. In my opinion, you won't have
to invest three years of your spare-time in this hobby before conclusive results show up (my case)!... When i have fear because of new SoftWare,
i load `XMSDSK' and conduct my evaluations in ~RAMDisk~; the best work-
bench i've had was when i accessed the ~RAMDisk~ remotely: all my files
were untouched after the client PC finished rebooting (which does help).

...I'll keep you posted.

It's a pleasure to hear of you as long as you can think the same...

Salutations, ;^)

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


... DOS+TCP/IP+TelNet+Kermit+.QWK technologies will run on XTs or better
--- MultiMail/MS-DOS v0.45 - Help TelNet OLMR BBSing to become UNIVERSAL
* Origin: BBS Networks @ www.bbsnets.com 808-839-6036 (1:10/345)

...an image is worth a thousand words... ...command-line samples:
RLFossil.EXE 2 1 "Commo.EXE /:INT-14 /{*1,,3,V,}"

What versions of {COMMO}, Telix and RLFossil are those, please?

As i mentioned above, `{Commo}' is version v7.7 (the last
one there was before its source-code and author both disapeared).

ahh, i had missed that... my thoughts have been to gather everything together for others... i have {COMMO} v7.7 but i note that it has a 30 day trial period and that there is a COMMO.ID file for registered users... how bad does it get if it is not registered? have mr. bruckner's people released a free key and/or are they continuing on with {COMMO}'s development?

As for `Telix', i'm refering to version 3.51 but you tell me if
it's the last release...

hummm... i have a floppy here of Telix 3.22 from deltacomm... i know i've seen 3.51... i just wonder where? i wasn't aware of any version of telix supporting INT14/FOSSIL stuffs until you mentioned it... a quick search for "14" thru the v3.22 docs i have turns this up...

=====
Problem:

We have our modems on a network and we need a network version of Telix in order
to access them. Does Telix have network support built in?


Solution:

Networking a comm program, or using a modem across the network as a resource requires two things.

1) The network must be NETBIOS compliant.

2) The comm program must use the BIOS (Int-14) for comm routines. Telix normally bypasses the slower BIOS and writes directly to the comm port for speed considerations, making it incompatible with networks.

However, we have developed a version of Telix which uses the Int-14 calls, and it is now available as a separate product. please call our sales staff for more
information about Telix for Networks.
=====

it would appear that they incorporated this functionality in a later version that came after 3.22... now i've gotta hunt that one down and try to get the serial registration number into it...

I must confess that the matter of local connection speed (~DTE~,
isn't it?) sure sounds somewhat "elusive" since i get rate peaks
around 4K cps (both on `{Commo}' and `Telix') but there's no
significant drop when i set `Telix' for a 9K6 bps connection... if
i use `MS-kermit' with `RLFossil' instead then my connect speed
shows as "unknown"... In any case, the Serial-Port `{Commo}' or
`Telix' would use is defined right on `RLFossil's Command-Line!...

...the equipment is not hampered by hardware (aka uart) speed...
...ms-kermit either doesn't have a matching connect speed or doesn't
recognise what it may be being told is the connection speed...

I have found that the behavior of ~BIOS INT-14~/~FOSSIL~
compatible terminal emulators varied significantly when i
investigated them but the "unknown" result returned by
`MS-Kermit' was said to make perfect sense, according to its
maintainers at the Columbia university. From memory, i
believe their reasoning was it's the ~FOSSIL~ driver's
responsability to manage it, usually (it sounds about true of
`X00', `ADF' and the suite).

yes and it is all too easy to tell the FOSSIL using software what speed the FOSSIL is running at so that transfer calculations may be performed... my RemoteAccess BBS knows the FOSSIL driver is locked at a set speed (115200) but it still uses a/the connection speed for calculations... when a dialup connection is made, it takes the info from the CONNECT line... in telnet mode, my shim says all connections are at 56k... it just seems to me that kermit would also be able to do this... but then again, from what i've read from you and others, i can easily see why it doesn't from the butt-type attitudes of kermit's developer(s)...

My bbs does that with telix all the time... When a user logs off,
my system fires up telix... ...and runs a script to fetch the
session's stats from the modem...

BBSes depend on a fully compliant level 5 ~FOSSIL~ driver
which can support application swapping even when the
Serial-Ports are still "Hot", i wish `RLFossil' were compliant
enough to support the use of a `ZMoDem' protocol driver run
from `MS-Kermit's terminal interface, or vice-versa!

unless i've something crossed up, DSZ (and FDSZ, i believe) can be used to dial
out and have a rudimentary terminal... FDSZ, BTW, is FOSSIL DSZ ;)

Right now, i can "share" connections (alternately) using
`LSPPPDlr' with `MS-Kermit' run as a protocol-driver - when
used via `COM/IP' - but not with `RLFossil' (the later reboots
my PC instead)!...

if you have and are using COM/IP, that indicates WIN9x (at least) is installed so why even mess with the legacy ways? even moreso since WIN9x alters a lot of rules for its own purposes... i'm assuming that your statement above is saying that you have the reboot problem with RLFOSSIL when using it in WIN9x?

I wonder what feedback i'd get from a person like Sylvain Lauzon
(he was knowledgeable enough about `RLFossil' to get me a 8088
built which didn't exist on the Net), euh... i have to wonder if
he wouldn't happen to know where to go for the source-code or,
maybe, even a quick fix.

i dunno but i do know that there are some out there who can reverse engineer things back to source code... maybe not the original, as the author wrote it, source code but source enough that it can be fixed and recompiled...

`TelNet Port' suffered from the same problem when i checked, i
may be stuck with this for ever!

what problem? the reboot problem when trying to share it between LSPPPDlr and MS-Kermit? also, when yo usay "share" you don't mean at the same time from different windows/tasks, do you?

...if one is handy with debug or other capable software, one can
redefine the BIOS table of serial and parallel port addresses...

Back in days when i played with `Z-80' code, a concept like
double-Byte numbers with their most significant Byte last made
sense but that's all history now, i depend on the talent of
others for my modest hobby...

i hear that... but the table did make some sense in how the BIOS stuff plays its part in the definition and location of the standard serial ports and helps to explain where comm programs get the info for the basic ports when they don't
have any real port setup capability, right?

...drop me a note when you're ready to try `MS-Kermit' as an `OS/2'
external file-transfer protocol-driver on a `Maximus' BBS!

...on a RemoteAccess BBS since i don't run Maximus "out front"...

Good! 8-) Anyway, i must meditate on the meaning of the
riddle...

"out front" meaning that i have max here but on another machine... sadly, though, its not compiling properly for me and i'm kinda like you in that i have
to rely on others to fix the problem... what i have here is the linux port on one of my linux boxes and i'm not a C coder at all ;)

)\/(ark
* Origin: (1:3634/12)

Hi Mark,

Addendum about "LSPPPDlr 2003" of December 13 and 15:

...30 day trial period... ...COMMO.ID file... How bad does it get
if it is not registered? Have mr. Brucker's people released a free
key and/or are they continuing on with {COMMO}'s development?

...no such lock in v7.7! ...my understanding was that the author
got a thought for the blind... ...right in time for ChristMass...
...i tried to read the YahooGroups mail-list yesterday... I might
try later and give you at least a name but it will have to wait...

I finally found how i was supposed to get the posts, here they are:


_______________________________________________[ 2003-Sep-20, 18h18 ]_
| Subject: "Fred Brucker" | |----------------------------------------------------------------------|
| I am Fred's nephew and am looking for anyone who knew him personally |
| or was a business associate of his. Fred has suddenly passed away |
| and my family and I are trying to get his affairs together and could |
| use any help. |
| |
| Please email me at this address. |
| Thank You |
| Larry Gilman, DVM |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


_______________________________________________[ 2003-Sep-20, 18h20 ]_
| Subject: "Fred Brucker" | |----------------------------------------------------------------------|
| I am looking for anyone who knew Fred personally or was a business |
| associate of his, he has suddenly passed away and my family and I |
| are trying to get his affairs together. |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


_______________________________________________[ 2003-Sep-22, 10h45 ]_
| Subject: "Re: [COMMO-list] Fred Brucker" | |----------------------------------------------------------------------|
| Thanks |
| [Non-text portions of this message have been removed] |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


________________________________________________[ 2003-Sep-25, 9h42 ]_
| Subject: "Re: [COMMO-list] Fred Brucker" | |----------------------------------------------------------------------|
| Thanks |
| [Non-text portions of this message have been removed] |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


_______________________________________________[ 2003-Oct-20, 18h04 ]_
| Subject: "Re: [COMMO-list] Fred Brucker" | |----------------------------------------------------------------------|
| Thanks |
| [Non-text portions of this message have been removed] |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The YahooGroups interface is less than convivial, especially if one considers that DOS people are trying to post in there, euh... Mr. Larry Gilman, the nephew, probably isn't into LEGACY hobbies so the posts must
have been done in a ~GUI~ environment but i can see why he had to retry, nonetheless. Apparently, he didn't manage to get a part of his "Thanks" message published or perhaps he just replied the same thing everytime he
wrote back and this part slipped away, unnoticed... I wonder what "Non-
Text Portions" i missed exactly! 8^o Well, over a year passed since we
got the bad news and this situation hasn't evolved. Anyway, it might be innacurate to state that no relative of mister Brucker "cared" about his
work (well, there _was_ mention of his business and affairs, after all).

Maybe the status changes after a delay, relatively to the status of SoftWare surviving its author? No `{Commo}' or `{C}TE' specific comment
was made on the official site so feel free to draw your own conclusions.

Salutations, :^)

Michel Samson
a/s Bicephale

http://public.sogetel.net/bicephale/


... Exploring DOS+TCP/IP+TelNet+ZMoDem/Kermit+.QWK since mid-1996 or so.
--- MultiMail/MS-DOS v0.45 - We could make TelNet OLMR BBSing UNIVERSAL!
* Origin: BBS Networks @ www.bbsnets.com 808-839-6036 (1:10/345)

Hi Mark,

About "LSPPPDlr 2003" in two parts of December 18:

But maybe HardWare performance has more inlfuence than i suspected!

On my internal 10mb LAN, i'm getting 9kcps...

Yet it tells me how much potential there is on a 100 Mbps one!

I'm this || close to getting the needed items to upgrade the major
parts of my LAN to 100mb... The NICs will have to come secondary...

Considering that On-Board ~EtherNet~ support becomes widespread and
hence that ~NIC~s are likely to disapear before routers do (~WiFi~ being
the last frenzy), euh... i'd shop around looking for the trickier parts
1st: the ~NIC~ must support at least one of `OS/2 LAN Server v2.3/4.0',
`OS/2 MicroSoft LAN manager' (~NDIS~ v2.0) or `OS/2 NetWare' (~ODI~). I
got a number of archives for D-Link's `DFE-538TX' or its clones based on
the `RTL8139' chip (like Encore's cheap `ENL832-TX') which tell me these
cards should be OKay (at 100 Mbps, i realize we're most probably talking
~PCI~ here). After all, if you have no use for a Dial BackUp Router, it
won't take much effort to find an affordable model for you these days so
my advice is to manage with what could be removed from inventories next.

:)

Of course, there's still some time left ahead: it's only relative.

Can you tell i'm testing something?

Hummm... Let me guess... ;-) Blue ~CAT-5~ cables look great in a ChristMass tree?... ;-D But if it were ~USB~ you'd have lightning too!

8-D ))

...`LSPPPDlr'... ...the BBS community could have done it!

...supposed sysops are really little more than advanced lemmings...

Am i detecting some dark poetry in the way you see things?...
Even i find myself on the "dark side" more often than not...

Anyone can be tempted by the Dark Side, Luke! But remember, that's
only a hobby, anyway; the trick is to not allow negative emotions to be
used for games like "break the toys of others" and you should be safe...

8-)

Which reminds me... I'll have to UpDate `LSPPPDlr' very soon! ;-)

Salutations, WBHW (With my Best Holiday Wishes),

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


... Windows made your old AT look better, now it's the other way around!
--- MultiMail/MS-DOS v0.45 - We could make TelNet OLMR BBSing UNIVERSAL.
* Origin: BBS Networks @ www.bbsnets.com 808-839-6036 (1:10/345)