Hey all.

I'm trying to get into understanding just how MakeNL actually works. For example, as NC, how would I get it to update just the network that I'd be managing on a regular basis?

I've taken examples from the provided hub.ctl from the documentation, and modified it, but it just gives me, in a test result, a CRC of 000, meaning there's no data there I'd guess.

)))[Psi-Jack -//- Decker]

... Power corrupts. Absolute power is kinda neat, though.
--- SBBSecho 2.27-Linux
* Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)

Eric Renfro wrote to All <=-

Hey all.

I'm trying to get into understanding just how MakeNL actually works.
For example, as NC, how would I get it to update just the network that
I'd be managing on a regular basis?

I've taken examples from the provided hub.ctl from the documentation,
and modified it, but it just gives me, in a test result, a CRC of 000, meaning there's no data there I'd guess.

Did you get my netmail??


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
=== MultiMail/Win32 v0.50
--- SBBSecho 2.27-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

05 Sep 15 12:25, you wrote to All:

I'm trying to get into understanding just how MakeNL actually works.
For example, as NC, how would I get it to update just the network that
I'd be managing on a regular basis?

ok...

I've taken examples from the provided hub.ctl from the documentation,
and modified it, but it just gives me, in a test result, a CRC of 000, meaning there's no data there I'd guess.

first off, what version of makenl? hopefully it is the latest ng version that is actively being developed and distributed...

second, that hub.ctl is not for a hub as we might think of a hub as for mail and files... it is for a HUB node in the nodelist which is mainly for HUB routed inbound netmail... the NC is a hub in this sense and there may be other hub divisions within a net... the NC can manage the whole segment or they may have the hubs manage their little sections and send them to the NC... if you are going to be managing a whole net, you should probably start with the net-s.ctl file as that is for a ""small"" net... the net-l.ctl is for a ""large"" net that would employ the previously mentioned HUBs to delegate management of smaller segments known as hubsegs which the NC would process with
the net-l.ctl file to build the netseg...

there's several ways that you can do this, too...

1. for many years i just used the net-s.ctl file and in the data section, i manually created and edited the entries for each node... then i would run a test run and see of there were any errors... if not, then i ran it again to send the netseg to my RC... it was pretty manual and only done when a change was necessary... this is probably the most common net level style of operation in this day in time...

2. i also toyed around with using nodesegs where each node would send in their single line entry and be responsible for it containing the proper data... then my net control file simply included them... during the normal daily run, makenl
tests and if a nodeseg was bad, makenl would send an error message back to the node and set that bad nodeseg aside... this style of operation is close to the large net and regional styles because it takes the input from downstream systems, tests it and sends back a notice that the segment is good or bad... as
i noted at the start of this section, i toyed with this but never put it into real production outside of the test environment...

3. i have also used a combination of 1 and 2 where i have a Data section with some entries and then a Files section to bring in others...

4. a more elaborate version of 3 is what i'm currently using, though... i took a page from ward's playbook... he adds the year and daynumber to his Z2C entry... i thought this was a good idea because you could then easily see when that seg was updated and sent upstream... so i scripted something together to do the same for my netseg... the script builds my ctl file from a static header
section, adds in the updated HOST line with the year/doy entry and finally brings in the static footer section... then makenl is run using that control file which then brings in the fairly static node entries file...


with all that said, here's a rough small net ctl for ficticious net789... there's the host entry, the host's non-admin entry and one other node...

==== Begin "net789.ctl" ====

logfile n789.log
loglevel 1
make network 789
outfile net789.seg
submit 1:456/20 INTL
netaddress 1:789/19
messages x:\ftn\netmail
private ok
allowunpub 1
alphaphone 0
baudrate 300,1200,2400,4800,9600,14400,16800,19200,28800,33600
copyright n789.cpy
prolog n789.pro
epilog n789.epi

Data Host,789,Somewhere_USA,yourcity_state_USA,your_name,1-800-555-0100,33600,XA,V34,CM,ITN,INA:your.domain.invalid,IBN,IVM,PING
,19,your_bbs,yourcity_state_USA,your_name,1-800-555-0100,33600,XA,V34,CM,ITN,INA:your.domain.invalid,IBN,IVM,PING
,27,some_bbs,somecity_state_USA,some_name,1-800-555-0101,33600,XA,V34,CM,INA:your.domain.invalid,IBN

==== End "net789.ctl" ====

this is basically taken from the bottom half of Figure 2 in the original makenl
documentation... we're managing all node entries in the bottom DATA section and
generating a net789.seg file to send upstream to the RC... the MSG format netmail directory is where makenl will place the file attach message with the seg file for sending... in a BSO environment this netmail area needs to be processed by a mail tosser to pack the netmail out to the RC's address with the
attached segment file... if you use an outbound filebox with binkd for your connection to your RC, you can throw away the file attach MSG file and just copy the net789.ctl file to the outbound filebox directory for binkd to send to
the RC... this is akin to the way interbbs door game files are moved...

the output of running makenl with the above control file looks like this...


x:\makenlng\test> ..\makenlp net789.ctl
MakeNL 3.4.1 (OS/2 32-bit) compiled with Watcom C on Oct 19 2013 10:57:21 MakeNL started
No directory for master files specified -- using X:\makenlng\test
No directory for output files specified -- using X:\makenlng\test
Cmdline: X:\makenlng\makenlp.exe "net789.ctl"
Using 'net789.ctl' in 'X:\makenlng\test'
Begin processing 'net789.seg' -- 15:55, Saturday, September 5, 2015
Sending 'X:\makenlng\test\net789.seg' to 456/20
CRC = 06075
MakeNL finished (rc=0)


since we did not specify the "-TEST" parameter, makenl went ahead and created the net789.seg file and attached it to a MSG netmail for sending to the specified 456/20 address of the RC... note that the parameters must start with a '-' (dash) and not a '/' (slash)... i suggest making it practice to always specify "-TEST" and "-PROCESS" when working with makenl... especially "-TEST" so that you can make sure there are no errors in the submission... once makenl has processed (vs tested) the file, it will keep up with it and will not send it again unless the seg file has actually been changed by an edit to the DATA section of the control file...

there are other features and capabilities of makenl that can be quite handy as one advances in its use but i would guess that maybe 90% of the folks using makenl do it all manually like this... it does at least give a check to ensure that the data is not broken ;)

if you want to delve in further, i'm available via netmail...

)\/(ark

... No, Vienna sausages are not made in Vienna!
---
* Origin: (1:3634/12.73)

Re: Re: MakeNL and how it works?
By: Bill McGarrity to Eric Renfro on Sat Sep 05 2015 01:20 pm

Eric Renfro wrote to All <=-

Hey all.

I'm trying to get into understanding just how MakeNL actually works.
For example, as NC, how would I get it to update just the network
that I'd be managing on a regular basis?

I've taken examples from the provided hub.ctl from the
documentation, and modified it, but it just gives me, in a test
result, a CRC of 000, meaning there's no data there I'd guess.

Did you get my netmail??

Hehe, yes, Bill, I did. I'm looking at it, still not honestly understanding what it's looking for in order to do what it needs to do. Like, what /should/ be in the master directory (defaulting to the current working directory if not set specifically), and everything.

I put together a little modified version of it in preparation to work with net135, I just don't know if it's right or what it's doing, or going to be doing. heh heh

)))[Psi-Jack -//- Decker]

... File not found. Should I fake it? (Y/N)
--- SBBSecho 2.27-Linux
* Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)

Re: MakeNL and how it works?
By: mark lewis to Eric Renfro on Sat Sep 05 2015 02:33 pm

05 Sep 15 12:25, you wrote to All:

I'm trying to get into understanding just how MakeNL actually works.
For example, as NC, how would I get it to update just the network
that I'd be managing on a regular basis?

first off, what version of makenl? hopefully it is the latest ng version that is actively being developed and distributed...

MakeNL 3.4.5 custom compiled from an RPM .spec I made to build it and package it for CentOS 7.1. :)
Got that from makenl.sourceforge.net. Correct, right? ;)

1. for many years i just used the net-s.ctl file and in the data section, i manually created and edited the entries for each node... then i would run a test run and see of there were any errors... if not, then i ran it again to send the netseg to my RC... it was pretty manual and only done when a change was necessary... this is probably the most common net level style of operation in this day in time...

with all that said, here's a rough small net ctl for ficticious net789... there's the host entry, the host's non-admin entry and one other node...

==== Begin "net789.ctl" ====

logfile n789.log
loglevel 1
make network 789
outfile net789.seg
submit 1:456/20 INTL
netaddress 1:789/19
messages x:\ftn\netmail
private ok
allowunpub 1
alphaphone 0
baudrate 300,1200,2400,4800,9600,14400,16800,19200,28800,33600
copyright n789.cpy
prolog n789.pro
epilog n789.epi

Data Host,789,Somewhere_USA,yourcity_state_USA,your_name,1-800-555-0100,33600,X A,V34,CM,ITN,INA:your.domain.invalid,IBN,IVM,PING ,19,your_bbs,yourcity_state_USA,your_name,1-800-555-0100,33600,XA,V34,CM,I TN,INA:your.domain.invalid,IBN,IVM,PING ,27,some_bbs,somecity_state_USA,some_name,1-800-555-0101,33600,XA,V34,CM,I NA:your.domain.invalid,IBN

==== End "net789.ctl" ====

This is very similar to what I had, with a few lack in some options, like logging options specifically. :)

this is basically taken from the bottom half of Figure 2 in the original makenl documentation... we're managing all node entries in the bottom DATA section and generating a net789.seg file to send upstream to the RC... the MSG format netmail directory is where makenl will place the file attach message with the seg file for sending... in a BSO environment this netmail area needs to be processed by a mail tosser to pack the netmail out to the RC's address with the attached segment file... if you use an outbound filebox with binkd for your connection to your RC, you can throw away the file attach MSG file and just copy the net789.ctl file to the outbound filebox directory for binkd to send to the RC... this is akin to the way interbbs door game files are moved...

Hmmm... When you talk about the outbox, do you mean, the net789.seg could be directly tossed into the outbox, not the net789.ctl, or do you mean the literal net789.ctl itself? hehe

So long as I'm using BinkD to send these things, I want to use MakeNL to do what it needs to do, and skip the whole netmail part and toss it into an outbox just as you say, that is afterall the cleanest way, instead of having SBBSEcho pack it up and send it.

the output of running makenl with the above control file looks like this...

x:\makenlng\test> ..\makenlp net789.ctl
MakeNL 3.4.1 (OS/2 32-bit) compiled with Watcom C on Oct 19 2013 10:57:21 MakeNL started
No directory for master files specified -- using X:\makenlng\test
No directory for output files specified -- using X:\makenlng\test
Cmdline: X:\makenlng\makenlp.exe "net789.ctl"
Using 'net789.ctl' in 'X:\makenlng\test'
Begin processing 'net789.seg' -- 15:55, Saturday, September 5, 2015 Sending 'X:\makenlng\test\net789.seg' to 456/20
CRC = 06075
MakeNL finished (rc=0)

since we did not specify the "-TEST" parameter, makenl went ahead and created the net789.seg file and attached it to a MSG netmail for sending to the specified 456/20 address of the RC... note that the parameters must start with a '-' (dash) and not a '/' (slash)... i suggest making it practice to always specify "-TEST" and "-PROCESS" when working with makenl... especially "-TEST" so that you can make sure there are no errors in the submission... once makenl has processed (vs tested) the file, it will keep up with it and will not send it again unless the seg file has actually been changed by an edit to the DATA section of the control file...

there are other features and capabilities of makenl that can be quite handy as one advances in its use but i would guess that maybe 90% of the folks using makenl do it all manually like this... it does at least give a check to ensure that the data is not broken ;)

if you want to delve in further, i'm available via netmail...

This is awesome, perfect, and what I was looking for. At least a better basic understanding. The documentation that comes with it... Isn't very useful, but explaination of how it's working, like you have provided, was more helpful.

With the few questions I have left to ask, as such above, and I should be ready to go.

)))[Psi-Jack -//- Decker]

... The worst thing about censorship is ██████████.
--- SBBSecho 2.27-Linux
* Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)

Eric Renfro wrote to Bill McGarrity <=-

Re: Re: MakeNL and how it works?
By: Bill McGarrity to Eric Renfro on Sat Sep 05 2015 01:20 pm

Eric Renfro wrote to All <=-

Did you get my netmail??

Hehe, yes, Bill, I did. I'm looking at it, still not honestly understanding what it's looking for in order to do what it needs to do. Like, what /should/ be in the master directory (defaulting to the
current working directory if not set specifically), and everything.

The first time you run makenl with the -p switch (-process), it will create files that are put in the master.

I put together a little modified version of it in preparation to work
with net135, I just don't know if it's right or what it's doing, or
going to be doing. heh heh

Here is the one you'll use for SportNet.... just make the the obvious changes for the net, run makenl in the -TEST mode to make sure there are no error. (You're going to need to change the path to your netmail folder.)

===Start net110.ctl===

make net 110 ; note explicit name of file simplifies processing


outfile net110 ;master file and output file have SAME name


submit 24:10/0 ;where you send updates, CRASH and/or HOLD optional

netaddress 24:110/0 ; your network address here

messages c:\????? ; path name to mail server's network mail area

PRIvate ok
ALLOwunpub 1

MINphone 1



; No other options are needed. Master directory and output directory will
; default to the current directory.
;
;
Data

Host,110,SE_Net_Coordinator_WV_VA_KY_TN_AR_MS_LA_AL_GA_NC_SC_FL,Gainesville_FL,Eric_Renfro,-Unpublished-,9600,CM,INA:binkp.deckersheaven.com,IBN
,1,SE_Net__Echomail_Coordinator_WV_VA_KY_TN_AR_MS_LA_AL_GA_NC_SC_FL_PR,Gainesville_FL,Eric_Renfro,-Unpublished-,9600,CM,INA:binkp.deckersheaven.com,IBN
,2,Decker's_Heaven,Gainesville_FL,Eric_Renfro,-Unpublished-,9600,CM,INA:bbs.deckersheaven.com,IBN

===End net110.ctl===

You'll not need a master folder as the output will be stored in the folder where makenl is run from. You'll edit this control file as you add nodes. Remember to follow the order in which the entries are entered. If they're wrong, it will give you an error. Always run the -TEST mode first!!


As mark stated previously, makenl will attach the segment and will be sent to your RC.

You have my number, call me if you need help.


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
=== MultiMail/Win32 v0.50
--- SBBSecho 2.27-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

05 Sep 15 18:39, you wrote to Bill McGarrity:

Did you get my netmail??

Hehe, yes, Bill, I did. I'm looking at it, still not honestly understanding what it's looking for in order to do what it needs to
do. Like, what /should/ be in the master directory (defaulting to the current working directory if not set specifically), and everything.

if you follow the simple net-s.ctl as depicted in my example, there's only one file, the ctl file, needed in the master directory... makenl will create the netseg in there from the entries in the DATA section of the control file...

I put together a little modified version of it in preparation to work
with net135, I just don't know if it's right or what it's doing, or
going to be doing. heh heh

it takes a little time to figure it all out... i have an entire setup for a private othernet running with regions and nets with ZINs and RINs... it is all scripted and copies the netsegs and regsegs to the zone's updates directory before processing... i have to study it a little bit each time i go back to look it over and make any changes...

)\/(ark

... A guy never felt compelled to stop a friend from getting laid.
---
* Origin: (1:3634/12.73)

Re: Re: MakeNL and how it works?
By: Bill McGarrity to Eric Renfro on Sat Sep 05 2015 07:37 pm

Eric Renfro wrote to Bill McGarrity <=-

Re: Re: MakeNL and how it works?
By: Bill McGarrity to Eric Renfro on Sat Sep 05 2015 01:20 pm

Eric Renfro wrote to All <=-

Did you get my netmail??

Hehe, yes, Bill, I did. I'm looking at it, still not honestly
understanding what it's looking for in order to do what it needs to
do. Like, what /should/ be in the master directory (defaulting to
the current working directory if not set specifically), and
everything.

The first time you run makenl with the -p switch (-process), it will create files that are put in the master.

I put together a little modified version of it in preparation to
work with net135, I just don't know if it's right or what it's
doing, or going to be doing. heh heh

Here is the one you'll use for SportNet.... just make the the obvious changes for the net, run makenl in the -TEST mode to make sure there are no error. (You're going to need to change the path to your netmail folder.)

Heh, after Mark Lewis's explaination, I think I finally got it all. I do like to use the master directory as it'll keep things tidy, and I can use a simple dummy messages directory that'll be wiped out every run, because I'll use binkd's fileboxes instead of netmail, much more clean. Unfortunately makenl itself goes ape when you don't give it a messages area.. Perhaps I can bug the developers to fix that for BSO handling. :)

)))[Psi-Jack -//- Decker]

... I am not an Economist. I am an honest man!
--- SBBSecho 2.27-Linux
* Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)

Eric Renfro wrote to Bill McGarrity <=-

Heh, after Mark Lewis's explaination, I think I finally got it all. I
do like to use the master directory as it'll keep things tidy, and I
can use a simple dummy messages directory that'll be wiped out every
run, because I'll use binkd's fileboxes instead of netmail, much more clean. Unfortunately makenl itself goes ape when you don't give it a messages area.. Perhaps I can bug the developers to fix that for BSO handling. :)

Why? Just let it to the attach and then sbbsecho will convert it when you run fidoout. You're making things way to complicated for yourself. :)


--

Bill

Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live


... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
=== MultiMail/Win32 v0.50
--- SBBSecho 2.27-Win32
* Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)

Re: Re: MakeNL and how it works?
By: Bill McGarrity to Eric Renfro on Sun Sep 06 2015 10:29 am

Eric Renfro wrote to Bill McGarrity <=-

Heh, after Mark Lewis's explaination, I think I finally got it all.
I do like to use the master directory as it'll keep things tidy, and
I can use a simple dummy messages directory that'll be wiped out
every run, because I'll use binkd's fileboxes instead of netmail,
much more clean. Unfortunately makenl itself goes ape when you don't
give it a messages area.. Perhaps I can bug the developers to fix
that for BSO handling. :)

Why? Just let it to the attach and then sbbsecho will convert it when you run fidoout. You're making things way to complicated for yourself. :)

heh.. I guess I still don't entirely trust sbbsecho yet, especially for file-related stuff. :)

FREQ's fail, because it's using arcmail methods that obviously won't work over binkd, for example.

)))[Psi-Jack -//- Decker]

... Da trouble wit computers is, dey got no sense of humor.
--- SBBSecho 2.27-Linux
* Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)

05 Sep 15 19:04, you wrote to me:

first off, what version of makenl? hopefully it is the latest ng
version that is actively being developed and distributed...

MakeNL 3.4.5 custom compiled from an RPM .spec I made to build it and package it for CentOS 7.1. :) Got that from makenl.sourceforge.net. Correct, right? ;)

yep!

[trim]

==== End "net789.ctl" ====

This is very similar to what I had, with a few lack in some options,
like logging options specifically. :)

i don't remember if they were available in the original or not... redirection was generally used back then if logging was desired...

this is basically taken from the bottom half of Figure 2 in the
original makenl documentation... we're managing all node entries in
the bottom DATA section and generating a net789.seg file to send
upstream to the RC... the MSG format netmail directory is where makenl
will place the file attach message with the seg file for sending... in
a BSO environment this netmail area needs to be processed by a mail
tosser to pack the netmail out to the RC's address with the attached
segment file... if you use an outbound filebox with binkd for your
connection to your RC, you can throw away the file attach MSG file and
just copy the net789.ctl file to the outbound filebox directory for
binkd to send to the RC... this is akin to the way interbbs door game
files are moved...

Hmmm... When you talk about the outbox, do you mean, the net789.seg could be directly tossed into the outbox, not the net789.ctl, or do you mean the literal net789.ctl itself? hehe

if by outbox you mean filebox, then yes, you could place the SEG file in there directly from makenl but it is better to copy it to the filebox so that makenl can maintain its own copy... makenl does create and maintain a sequence.dat file which is queued to the control file's DATA section or to any files brought
in via a FILES section... so the SEG file might not be needed by makenl... i've
not tested that, though...

So long as I'm using BinkD to send these things, I want to use MakeNL
to do what it needs to do, and skip the whole netmail part and toss it into an outbox just as you say, that is afterall the cleanest way,
instead of having SBBSEcho pack it up and send it.

in your script, just copy the SEG file to the filebox and you should be good to
go...

NOTE: you might want to contact your RC and decide on a name for your netseg file... this is a security thing... there have been instances in the past where
some neferious person dropped off a false netseg with the same name as a net's netseg file... the software on the RC's system processed it and replaced the network section with that of the false netseg... you and your upstream *C just need to use the same name for your netseg in your scripts so that it will be processed properly and imposters won't be able to cause problems...

[trim]

if you want to delve in further, i'm available via netmail...

This is awesome, perfect, and what I was looking for. At least a better basic understanding. The documentation that comes with it... Isn't very useful, but explaination of how it's working, like you have provided, was more helpful.

good deal :)

With the few questions I have left to ask, as such above, and I should
be ready to go.

alright! we're here if needed :)

)\/(ark

... Anything worth taking seriously is worth making fun of.
---
* Origin: (1:3634/12.73)

06 Sep 15 11:25, you wrote to Bill McGarrity:

Why? Just let it to the attach and then sbbsecho will convert it when
you run fidoout. You're making things way to complicated for
yourself. :)

heh.. I guess I still don't entirely trust sbbsecho yet, especially
for file-related stuff. :)

in the past, there wasn't any real call for such... most folks using sbbs and the like just didn't do those things... some might have wanted to but there was
no real call for it over all the users...

FREQ's fail, because it's using arcmail methods that obviously won't
work over binkd, for example.

that's a pretty easy addition to make... and these days, a few voices asking are heard more than may have been in the past... especially with the packages' user count getting smaller...

)\/(ark

... Life is a do-it-yourself project.
---
* Origin: (1:3634/12.73)

Re: MakeNL and how it works?
By: mark lewis to Eric Renfro on Sun Sep 06 2015 01:46 pm

06 Sep 15 11:25, you wrote to Bill McGarrity:

Why? Just let it to the attach and then sbbsecho will convert it
when you run fidoout. You're making things way to complicated for
yourself. :)

heh.. I guess I still don't entirely trust sbbsecho yet, especially
for file-related stuff. :)

in the past, there wasn't any real call for such... most folks using sbbs and the like just didn't do those things... some might have wanted to but there was no real call for it over all the users...

FREQ's fail, because it's using arcmail methods that obviously won't
work over binkd, for example.

that's a pretty easy addition to make... and these days, a few voices asking are heard more than may have been in the past... especially with the packages' user count getting smaller...

True enough. I just know Rob Swindle doesn't exactly like working on things for SBBSEcho. hehe. It was kinda left on his plate to maintain, but he does, and I'm honestly glad he does.

Back and fourth, I reported an issue where netmail was set to not be kill when sent, because BSO style it doesn't matter, but I wanted to keep some kind of history of what Netmail I was sending so I could look back on it. Problem was, sbbsecho would continually re-send the same netmail because it wasn't looking for the "Sent" flag in it. After some deliberating, testing, and compiling, and even some of my own code I slopped together to fix a little tiny bug based on his own code changes that caused an even more severe issue out of it, we solved the problem.

I'm hoping we can do something similar for the FREQ for BSO. It's not much, but it /can/ be useful from time to time just the same. I already submitted the issue to the forums on DOVE-net about it, and just waiting. It's Labor Day Weekend so a lot of people are out and about, enjoying their time off. hehe. Including Rob, as I just noticed on Facebook earlier. hehe

)))[Psi-Jack -//- Decker]

... Interchangable devices won`t.
--- SBBSecho 2.27-Linux
* Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)

Hello, Eric.

Sunday September 06 2015 at 16:35, you wrote to mark lewis:

True enough. I just know Rob Swindle doesn't exactly like working on things for SBBSEcho. hehe. It was kinda left on his plate to maintain,
but he does, and I'm honestly glad he does.

That's because Rob Swindell (proper spelling) did not write the FTN-related code in Synchronet; he hired someone else to do it. He has told me he doesn't know very much about that code. So if you're wanting to get things done, you might want to talk to someone who knows more about FTN and its arcane ways. :)

Later,
Sean

--- GoldED/2 3.0.1
* Origin: Outpost BBS * Johnson City, TN * bbs.outpostbbs.net (1:18/200)

Re: MakeNL and how it works?
By: Sean Dennis to Eric Renfro on Mon Sep 07 2015 05:56 pm

Hello, Eric.

Sunday September 06 2015 at 16:35, you wrote to mark lewis:

True enough. I just know Rob Swindle doesn't exactly like working on things for SBBSEcho. hehe. It was kinda left on his plate to maintain, but he does, and I'm honestly glad he does.

That's because Rob Swindell (proper spelling) did not write the FTN-related code in Synchronet; he hired someone else to do it. He has told me he doesn't know very much about that code. So if you're wanting to get things done, you might want to talk to someone who knows more about FTN and its arcane ways. :)

The FTN-related code in Synchronet proper, I did write. I also wrote SBBSFIDO which was the pre-cursor to SBBSecho. What I did not initially write was SBBSecho (Allen Christiansen, a.k.a. King Drafus, did while employed by Digital Dynamics). So yeah, that's kind of right. But since around '97, I've been pretty much the only one maintaining and enhancing SBBSecho and I think I know more now about FTN and its arcane ways than Allen ever did (no disrespect to him).

-Rob

digital man

Synchronet "Real Fact" #36:
Synchronet's Windows Control Panel is built with Borland C++ Builder.
Norco, CA WX: 77.8°F, 45.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs

Re: MakeNL and how it works?
By: Sean Dennis to Eric Renfro on Mon Sep 07 2015 05:56 pm

Hello, Eric.

Sunday September 06 2015 at 16:35, you wrote to mark lewis:

True enough. I just know Rob Swindle doesn't exactly like working on
things for SBBSEcho. hehe. It was kinda left on his plate to
maintain, but he does, and I'm honestly glad he does.

That's because Rob Swindell (proper spelling) did not write the FTN-related code in Synchronet; he hired someone else to do it. He has told me he doesn't know very much about that code. So if you're wanting to get things done, you might want to talk to someone who knows more about FTN and its arcane ways. :)

Actually... I told him about the .REQ file used for SRIF, and he's already added the functionality in, minus password support, but he's added in the ability to use the subject-line FR: filename filename, and for BSO configured mode for sbbsecho, it'll drop a .REQ file down, and append to it if it already exists and hasn't been handled already.

I'm quite impressed that he went and researched it so quickly and found enough details to understand it, actually, and implemented it. I'm left only to test it out, which I will be attempting to do very soon. :)

)))[Psi-Jack -//- Decker]

... A liberal is a man too broadminded to take his own side in a quarrel.
--- SBBSecho 2.27-Linux
* Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)