EL230 Errors found in MOD submission, see messages:

EL219 Error Unknown keyword found: TOT
EL231 Ruletext rejected due to other reported errors
EL213 UPD to non existing area - Rejected.


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

EL230 Errors found in MOD submission, see messages:

EL231 Ruletext rejected due to other reported errors
EL213 UPD to non existing area - Rejected.


--- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
* Origin: The Elist Maintainer (2:250/1)

Hello Marc!

Wednesday May 13 2020 21:30, I wrote to you:

EL230 Errors found in MOD submission, see messages:

EL219 Error Unknown keyword found: TOT
EL231 Ruletext rejected due to other reported errors
EL213 UPD to non existing area - Rejected.

You have sent a few submissions with a keyword of TOT

What is it as I have no references for it any where.

Oh, you were trying to Update a non existing area so it is a MOD-ADD

Done it any way :)

Methinks it might be a good idea to accept a UPD to create a echo that does not
exist.

What does every think?

Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Hello Vincent.

<On 13May2020 23:39 Vincent Coen (2:250/1) wrote a message to Marc Lewis regarding REC-RADIO-AMAT-DX EL230 Errors found in MOD submission, see messages:

EL219 Error Unknown keyword found: TOT
EL231 Ruletext rejected due to other reported errors
EL213 UPD to non existing area - Rejected.

You have sent a few submissions with a keyword of TOT

What is it as I have no references for it any where.

That was left over from the old system.

Oh, you were trying to Update a non existing area so it is a
MOD-ADD

Done it any way :)

Strange. It must have expired. It's still an active echo.

Methinks it might be a good idea to accept a UPD to create a echo
that does not exist.

Might be a good thing. Especially for cases like this where the echo is still active and distributed.

BTW, I will re-submit a corrected .ECO file.

Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Re: REC-RADIO-AMAT-DX EL230 Errors found in MOD submission, see messages:
By: Vincent Coen to Marc Lewis on Wed May 13 2020 23:39:12

You have sent a few submissions with a keyword of TOT

some time back, when you first wrote about TOT, i posted what it was for... that was several weeks ago...

TOT : the number of nodes carrying the area

i got this information from the original echomod archive(s) that dana bell did...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello mark!

Wednesday May 13 2020 20:55, you wrote to me:

Re: REC-RADIO-AMAT-DX EL230 Errors found in MOD submission, see
messages: By: Vincent Coen to Marc Lewis on Wed May 13 2020 23:39:12

You have sent a few submissions with a keyword of TOT

some time back, when you first wrote about TOT, i posted what it was
for... that was several weeks ago...

Must have missed that.

TOT : the number of nodes carrying the area

i got this information from the original echomod archive(s) that dana
bell did...

OK, found that but it is not in Ben's program but might have been in the previous one.

I can see why, as no one could possible know how many systems are connected to a echo as no uplink provides that data other than in a manual way and even then
it will be very limited as most BBS system do not report on it at all.

Please remove all references to that keyword (as it is dead) from all submission files.

It will save you getting error reports!

Vincent

--- Mageia Linux v7.1 X64/Mbse v1.0.7.13/GoldED+/LNX 1.1.5-b20180707
* Origin: The Elist Maintainer (2:250/1)

Re: REC-RADIO-AMAT-DX EL230 Errors found in MOD submission, see messages:
By: Vincent Coen to mark lewis on Thu May 14 2020 16:56:17

You have sent a few submissions with a keyword of TOT

some time back, when you first wrote about TOT, i posted what it was
for... that was several weeks ago...

Must have missed that.

probably when you had the other address set for this area which caused you problems with messages in here...

TOT : the number of nodes carrying the area

i got this information from the original echomod archive(s) that dana
bell did...

OK, found that but it is not in Ben's program but might have been in the

previous one.

i did state "that dana bell did" above... dana is the original echomod author ;)

I can see why, as no one could possible know how many systems are connected to a echo as no uplink provides that data other than in
a manual way and even then it will be very limited as most BBS
system do not report on it at all.

you're forgetting about the seenby lines ;) most moderators would have access to them in the messages and can easily gather and count them... i've done similar with my PATHS program clone which maps out an echo's layout on the network :)

Please remove all references to that keyword (as it is dead) from all submission files.

i've already done that for mine...

It will save you getting error reports!

true but i should note that i'm not the moderator the original message was posted to :)


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)