>  > I actually figured out the problem!  I keep all of the *.NA files that
 >  > are set up in sbbsecho.ini in a directory to themselves.  The ones for
 >  > the "othernets" were still there but somehow the BACKBONE.NA file for
 >  > FIDO had gone missing. So, I guess when an NA file is missing, this is
 >  > what sbbsecho does.  I
 >  > replaced the missing file, and sbbsecho started generating the responses
 >  > for my other Zone 1 system.

 > That seems to me to be very unlikely to be the cause.


I was afraid of that, but areafix is working now that the NA file is back in
place.  I have received consistent responses from it, and the other sysop has
reported that they are now getting responses, too.

Filefix, OTOH, is still not responding.  I read the code and realized I needed
to run the jsexec install for it.  Did that.  Robots entry is now in the
sbbsecho.ini file (the only robots entry), and the event is active but it is
still not doing anything (aside from exiting with 0) when the event does run.
I have sent netmails both to FileFix and TickFix.  All are routed to my
account when they arrive.

Are there any changes required to the tickit.ini file?  Is the TO case
sensitive?  I am using my areafix password... is that right?

Thanks!
#

---
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP