home *** CD-ROM | disk | FTP | other *** search
-
- Sample batchfiles for Multinode use of Frontdoor v 1.0
- ======================================================
-
- Written by Peter Janssens.
- Last updated on Nov 3, 1990.
-
- If you have questions relating to these samples then feel free to
- contact me through the echomail conference FDECHO or via netmail.
- Fidonet 2:512/1 or 2:512/117
- SIGnet 27:331/1
-
- =========================================================================
-
- Disclaimer:
- These batchfiles eat diskspace on your system.
- They do the same thing on mine. I can't guarantee that they do anything
- else. They are my own batchfiles, but then simplified for documentation
- purposes only.
-
- -------------------------------------------------------------------------
-
- Directory structure:
-
- C:\Fd Frontdoor Node 1 system directory
- C:\Fd\Fd2 Frontdoor Node 2 system directory
- C:\Ra RemoteAccess system directory
- C:\Msgs RemoteAccess messagebase and userfile
- C:\Ra\Line1 RemoteAccess Node 1 home directory
- C:\Ra\Line2 RemoteAccess Node 2 home directory
-
- -------------------------------------------------------------------------
-
- Special programs used on my system:
-
- CdCheck Gives errorlevel depending on whether there is a carrier
- DvCommand DesqView utility
-
- I have included DVCO and CD-Check in the distribution archive.
- They are both shareware.
-
- -------------------------------------------------------------------------
-
- Frontdoor multinode feature used:
-
- FDEXIT.xxx A file with this name, residing in the system directory
- of Frontdoor will make the mailer exit with errorlevel xxx
-
- -------------------------------------------------------------------------
-
- How does this work:
-
- When a user on the BBS enters mail then RA will exit with a special error-
- level. Apart from this, ECHOMAIL.BBS will exist in the C:\MSGS directory
- if he entered Echomail or NETMAIL.BBS if he entered Netmail.
-
- FrontDoor on both lines is setup to exit with an Errorlevel 100 after
- receipt of (echo-) mail. The only thing the batchfile for Node 2 does is
- trigger an exit for Node 1 with the same Errorlevel 100.
-
- If Node 1 starts mail processing it first detects whether there is a
- carrier on Node 2. If there is no carrier then Node 2 is put to sleep
- via Errorlevel 160 and the mail is processed.
-
- If there is a carrier then this can be either a mailsession or a BBS caller.
- If it's a mailsession, then FD2 must be active and thus a signal can be
- set using Fdexit.xxx to let Node 2 return a signal when it is available
- again. If it's a BBS caller then the same signal will be given to Node 1
- as soon as the caller leaves the BBS (and RA exits to the batchfile).
-
- As soon as Node 1 is available again, either immediately or after a BBS
- caller or a mailsession, it will simply restart the process because Node 2
- regenerated the Errorlevel 100.
-
- This batchfile processes the mail all day on my system (except in ZMH) and
- works even fast enough during the busy hours.
-
- To help people who have RAQMX installed I have not deleted the XRS mail
- processing from the example. If you don't run RAQMX then you should
- consider to start using it. (Saves you the trouble of deleting the lines
- from these batchfiles :-).
-
- -------------------------------------------------------------------------
-
-