Subj : MO Sys
To   : Gord Hannah
From : Bob Jones
Date : Wed Oct 24 2001 01:51 am

 GH> I just did this one up, seeing that I ma not that good at .cmd and
 GH> .bat files look for errors and see if it may be a big 
 GH> wreck.  Timed can be called separately.

 GH> mailonly.cmd:
 ...
 GH> I renamed bt23 to Binkley, I may also need to do some 
 GH> more errorlevel work if memory serves as bink needs 
 GH> them to answer the call and will go to a text file 
 GH> stating  that this is a Mail Only system and an 
 GH> alternate way of contacting me.

Note:  Under OS/2 one typically uses BBS SPAWN option in Binkley instead of the 
method that exits with an error level, at least if using the OS/2 native 
version of software.  If your flaged as mail only on all events in Binkley.evt 
file, the one liner in the Binkley.CFG is sent and I believe you don't have to 
worry about this issue.  But, it is probably better to have the BBS SPAWN 
option setup right just to be safe.

 GH> :TOSS
 GH> h:
 GH> cd\mail\inbound
 GH> if exist *.tic goto tick
 GH> if exist nodediff.* goto nodelist

BJ> Note:  If you get your nodelist with tic's, the if exist nodediff.*
BJ> isn't going to get executed, because you will first jump and process
BJ> the tic's.... 

 GH> I can change this around sound good to me.

Think it through before you change it.  Do you need the TIC files to be 
processed before you play with the nodelist compilation?  If so, the order you 
are doing things in is correct, it's just that you have a test that under 
normal situations won't be exercised.  On the other hand, if your NC or RC 
dumps you a nodediff without a .TIC file associated with it, your line will 
handle that situation.  In my case, I need the .TIC file processed first (which 
validates my source of the nodediff) and actually moves the nodediff to where 
the nodelist processing obtains the file.  My comment was made to have you 
think it through, not to necessarily make the change.  Sometimes, a line like 
that is explicitly added by the author to catch special situations.  Some times 
it is because the author hasn't thought through the processing.  Think through 
the processing order and then decide if you want to keep the line where it is, 
delete the line or move the line.

BJ> "ECHO ON" and "PAUSE" statements as needed to see what's happening
BJ> and help in debugging. 

 GH> Good advice.

Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01
 * Origin: Top Hat 2 BBS (1:343/41)

.