Hello Kevin!

12 Jul 08 13:39, Kevin Klement wrote to All:

 KK> I'm running MS-DOS versions of Seal and Squish, the fidonet backbone
 KK> echo areas is now a small 200 areas, my squish.cfg needs a clean up of
 KK> dead echo areas.

 KK> Any quick way of doing this?

DROP will both clean up the SQUISH.CFG entries and delete the message data
files for the area.  I assume you are looking for an easy way to identify
which tags to drop, based on the criteria that they no longer are listed in
the .NA file?

If so, you can force SEAL to update the descriptions for the areas on the
;EchoSpec lines with:

SEAL DESCRIBE E  -FORCED

Without -FORCED, only missing descriptions are updated with current
ones...so the old lines will still have their old descriptions that were
added when the area was first created.  Adding -FORCED will change them to
blank, "(no description available)", or whatever SEAL.INI has
defined as DefaultDescription.

After that, a little FIND on the "no description" string and
search-n-replace magic is all it takes to make a .BAT with one SEAL DROP E
 line per area.  Scan the tags to make sure you don't
accidentally delete local or regional echoes that either don't appear in
the .NA or come from another uplink.

Setting GroupLines to "yes" may also be helpful if you normally
see each ;EchoSpec line immediately after its corresponding EchoArea line. 
It toggles them from being interleaved to listed as a block of EchoArea
lines and separate block of ;EchoSpec lines.  Don't forget to run SEAL
UPDATE to have it rewrite the SQUISH.CFG after toggling the setting in
SEALCFG or directly in SEAL.INI.

I recently had a downlink leave and then come back, and PAUSE / RESUME
would do pretty much what you're after more simply since it won't RESUME
areas that aren't found in the .NA with your uplink...but it doesn't like
your own address or the feed address as an argument.

.\\ike

--- GoldED/2 2.50+