Subj : FastLst 2.02
To   : Andy Roberts
From : Bob Jones
Date : Mon Jul 23 2001 02:52 pm

AR>> Flst202P.Zip  09-25-99  120,048

BJ> Hmmm.... Mine shows FLST202P.ZIP 10-15-99  120639 .  I wonder if
BJ> one of ours got re-packed with a system advertisement....  I think
BJ> mine came in on one of the filebone areas.

AR> The IFDC requires a Zip comment.  After awhile I strip all Zip files of
AR> comments and re-Touch the dates to the latest contained file.  Besides
AR> some of those old files gave credit to USR, which is no longer part of the
AR> system and IMO makes a great modem but doesn't deserve credit for what is
AR> history as far as the IFDC is concerned.

Thanks.  I understand what you're doing.  I probably have the same archive
then.

AR> Sorry I strayed off your subject, but your original msg did leave an
AR> alternative open.

No problem.  I was asking for alternatives....

...
AR> I never call out to anywhere without knowing exactly where I'm calling.
AR> The years of huge phone bills are long gone for me.  Considering the
AR> rather small quantity of Telnet nodes available, it would probably take me
AR> less time to manually setup all those in the current nodelist, than it
AR> does for me to reply to this msg.

I'll admit that by default, all netmail going through here is routed.  I would
only rarely make a long distance call, and for those I have to manually reset
the nodelist tables to permit it.  But with the internet connectivity, if I
could automate a few things, I could send more stuff direct via TCP/IP
links.....

AR> IMO it wouldn't take much to write a REXX CMD to read a raw nodelist
AR> (looking for "000-") and output a short list of Telnet nodes then append
AR> that to QNode.cfg

It takes more than translating "000-" phone numbers.  If all you want is the
list of telnet nodes, pick up the INODELST file bone.  The list is supposed to
be posted weekly, but I haven't seen an update for about two to four weeks.

AR> ---
AR> Perl560.Zip                     03-22-00       5,298,642
AR>     PERL v5.60 language interpreter.
AR> ---

Going to have to dig that out.....  I have other reasons to learn more perl
code.  For my current work, REXX isn't of interest, but I know it is doable.

AR> If it were me I'd just manually rearrange those dozen or so lines and edit
AR> qnode.cfg manually.  Otherwise I'd use REXX to automate the job.

As of the last INODELST file I receive, it is 240 telnet'able FTSC handshaking
nodes within fidonet (at least those that admit to such capability in the
nodelist).  I get the needed BinkD configuration information straight out of
the I-BINKD (or INODELST) filebone.  I was looking for how to handle the telnet
(and VMODEM) connections....  I think I like your dial / cost translation table
edits....  Hmmmmm....  That could be automated via an generated file included
in the QNode processing.....  Hmmmmm.....

BJ> Hmmmm....

BJ> Thanks for the thought.....

AR> Welcome to the confusion too. <g>

AR>      Thanks and Good Luck,        Andy Roberts
AR>                                   [email protected]

And thank you for feeding me with another round of ideas for handling the
situation.....  Now I need time.....

Bob Jones, 1:343/41
telnet://tophat.darktech.org


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)