Hi All,

+ 24 Jun 16:44:27 SEAL Begin, Seal/386 v0.50 (mem=12307K)
# 24 Jun 16:44:27 SEAL Scanning bad msgs in F:\BAD\BAD_MSGS
: 24 Jun 16:44:27 SEAL Created echo area STARGATE from 1:140/1
! 24 Jun 16:44:27 SEAL ERROR: Run-time Error 216 at 0277:0434
+ 24 Jun 16:44:27 SEAL End. (length=0:00, mem=12306K)

+ 24 Jun 16:44:51 SEAL Begin, Seal/386 v0.50 (mem=12307K)
# 24 Jun 16:44:51 SEAL Scanning bad msgs in F:\BAD\BAD_MSGS
: 24 Jun 16:44:51 SEAL Created echo area STARGATE from 1:140/1
! 24 Jun 16:44:51 SEAL ERROR: Run-time Error 216 at 0277:0434
+ 24 Jun 16:44:51 SEAL End. (length=0:00, mem=12306K)


There is also newsgroups in my BAD_MSG area.

Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: Gypsy BBS -- Gypsy Designs CDN (403) 242-3221 (1:134/77)

Hello Kevin!

24 Jun 05 16:48, Kevin Klement wrote to All:

+ 24 Jun 16:44:51 SEAL Begin, Seal/386 v0.50 (mem=12307K)
# 24 Jun 16:44:51 SEAL Scanning bad msgs in F:\BAD\BAD_MSGS
: 24 Jun 16:44:51 SEAL Created echo area STARGATE from 1:140/1
! 24 Jun 16:44:51 SEAL ERROR: Run-time Error 216 at 0277:0434
+ 24 Jun 16:44:51 SEAL End. (length=0:00, mem=12306K)

There is also newsgroups in my BAD_MSG area.

Believe it or not, I think that runtime error is due to one of the syntax bugs in the distribution. I found this, but I seem to remember there might be more:

1. In SEAL.INI (SEALINI.DAT in distribution pack) in line

FileSpec=";FileSpec %20t %3a %3l %d

trailing quote is missing, making SEAL.INI corruption while using SEALCFG

2. In SETUP.INI in line

EchoSpec=String,":EchoSpec line","%t=tag %a=access %l=locks

":" should be replaced with ";"


You shouldn't need the runtime 200 fix, if you're able to use the EXEs at all.

You can also edit SEAL.INI with a text editor and run SEAL UPDATE afterwards to
update the binary version of the CFG, rather than using the SEALCFG program.

You might want to compare the lines in the [EchoFeeds] block to see what's different between the working line for Bob and other line for whatever address the gating software is originating from. Each of the elements of the line is documented in the comments above the block.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hi Mike,

Believe it or not, I think that runtime error is due to one

Wow... sounds great, really sorry Mike, I'm miss-understanding your directions, still getting the 216 error.

+ 27 Jun 12:35:38 SEAL Begin, Seal/386 v0.50 (mem=12307K)
# 27 Jun 12:35:38 SEAL Scanning bad msgs in F:\BAD\BAD_MSGS
: 27 Jun 12:35:38 SEAL Created echo area 24HOURSUPPORT from 1:134/77.10
! 27 Jun 12:35:38 SEAL ERROR: Run-time Error 216 at 0277:0434
+ 27 Jun 12:35:38 SEAL End. (length=0:00, mem=12306K)


Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: Gypsy BBS -- Gypsy Designs CDN (403) 242-3221 (1:134/77)

Hello Kevin!

27 Jun 05 16:55, Kevin Klement wrote to Mike Tripp:

Wow... sounds great, really sorry Mike, I'm miss-understanding your directions, still getting the 216 error.

Where did I lose you? Correcting the distribution errors or manually verifying
SEAL.INI?

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hi Mike,

Where did I lose you?

<gulp>

Correcting the distribution errors or
manually verifying SEAL.INI?

Both... :) Do I edit both or just one, specifically. Do I just edit
"seal.ini" and then run seal386 update?

Which files do I edit specifically?

Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: Gypsy BBS -- Gypsy Designs CDN (403) 242-3221 (1:134/77)

Hello Kevin!

28 Jun 05 16:37, Kevin Klement wrote to Mike Tripp:

Correcting the distribution errors or
manually verifying SEAL.INI?

Both... :) Do I edit both or just one, specifically.

Ideally, you would've known about the syntax bugs in the distribution files and
manually made both corrections before you started. Those strings are used as default templates for area creation, but you can customize them. I'm guessing you must've already done that for the ;Echospec line, or you'd probably be having trouble with all uplinks. The other is a ;Filespec line and you're not concerned with FileFeeds right now.

Do I just edit "seal.ini" and then run seal386 update?

Which files do I edit specifically?

SEAL.INI looks like any old ASCII-based text configuration file such as BINKLEY.CFG. SEALCFG.EXE is a nested menu configuration program like you find in FD or IREX. Most config programs accept the user input and then produce a cryptic binary file (which you little hope of fixing if corrupted) that the main program uses during execution. SEALCFG actually just updates the ASCII text to SEAL.INI and SEAL.EXE parses SEAL.INI on each execution run. So you have the option of using the config program w/pretty user interface and/or editing the ASCII directly with your text editor or batch logic.

If you make changes in SEALCFG, it automatically replicates any changes that are necessary out to the other CFG files that are impacted...namely, SQUISH.CFG
and TICK.CFG. If you make changes directly to the text in SEAL.INI, you have the extra step of running SEAL UPDATE to force the replication of those changes
out to the impacted files.

Troubleshooting the setup through the menued front-end can be difficult because
you are only accessing one attribute/field of one specific record on the screen
at a time. Discrepancies can be a lot easier to spot in the ASCII file itself where there is only one long line per nodelink/feed and all of the lines of the
same type are grouped together into consecutive lines and you can see all the working ones right alongside the one you're having trouble with. Even new link
setup can be simplified with some copy+modify: I want Joe to work just like Frank, except his address=xxx, his password=yyy, and I will flag his areas with
Z instead of A.

So fire that editor up and search your way to the string "ECHOFEED" and see what's different about your entry for the newsgroup feed address as compared to
the others that are working. It is probably something as simple a non-existent
path or a missing trailing slash, etc. Don't let the runtime error make you think that the code is hosed. Robert was more concerned about getting features
implemented and bugfixes in, and planned to spruce up the error-handling later after the feature-set stabilized...but became one of those famous "lost the source in a drive crash" and "dropped out of Fido soon after" stories instead.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hi Mike,

Don't let the
runtime error make you think that the code is hosed. Robert

This is GREAT Mike... You explained it really well. And I did
understand what ya said, so I'll try it again, it's sure half
the fun of this hobby.

Always did like Fidonet more than the Internet.

Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: Gypsy BBS -- Gypsy Designs CDN (403) 242-3221 (1:134/77)

Mulling over Kevin Klement to Mike Tripp 01 Jul 2005

Hi Kevin,

Don't let the
runtime error make you think that the code is hosed. Robert

This is GREAT Mike... You explained it really well. And I did
understand what ya said, so I'll try it again, it's sure half the
fun of this hobby.

By coincidence, I started getting runtime error 216 here a few days
ago, and only noticed it today. It proved to be caused by one or more
already processed netmails to Seal386, with the SCAN parameter.

Deleting the netmails fixed the problem.

Cheers, Steve..

---
* Origin: Xaragmata / Adelaide SA telnet://xaragmata.thebbs.org (3:800/432)

Hi Steve,

Wednesday July 06 2005, Steve Asher writes to Kevin Klement:

By coincidence, I started getting runtime error 216 here a
few days ago, and only noticed it today. It proved to be
caused by one or more already processed netmails to Seal386,
with the SCAN parameter.

Thanks, been busy so haven't had any time to try things, I'm
also going to try your suggestion too.

email | info@gypsy-designs.com
web | gypsy-designs.com
--- Squish/386 v1.11
* Origin: Gypsy BBS -- Gypsy Designs CDN (403) 242-3221 (1:134/77)