Hello Bill,   
      
   On Sat 2011-Sep-10 09:07, Bill Gordon (1:3634/22) wrote to Richard Webb:   
      
   BG> Well, here's an outline of what I want it to do. Maybe that'll help:   
      
   Right, only trouble for me is, yes I could do a lot of if   
   exist stuff that you could plug in, and help you build the   
   appropriate labels to do what's needed if file exists, etc.   
   But, I don't know IRex from ADam's house cat, and I think if it's like most   
   other fIdonet stuff it generates errorlevels   
   or something similar to fire processes after receipt of   
   mail, etc.   
      
   BG> 1.   check the inbound directory (fido\in) to see if there is any    
   BG> mail/files   
      
   Okay, easy enough with the nodediff,  but it's going to be   
   just as long and convoluted to check for *.su*, *.mo*, etc.   
   to check for them as they're currently named by most.  If   
   Irex generates errorlevels after receipt of mail then you   
   can trap that in your batch as in:   
      
   if errorlevel 50 goto dothis   
   if errorlevel 40 goto dothat   
   if errorlevel 30 goto picknose   
   if errorlevel 20 goto burp   
      
   Remember to trap errorlevels in descending order.  Consult   
   your irex docs, they might have easier ways.  But, for your   
   nodediff ...   
   if exist fido\in\nodediff.* goto do_diff   
      
   Then create the label   
      
   :do_dif   
   :: insert the lines to invoke the process that handles your   
   nodediff.   
   :: at the end of do_diff remember to return   
   :: for further processing   
      
   :: remember to create lines for labels with one preceding   
   :: colon, two as shown here are comments   
   :: that don't take up memory   
   :: or whatever as  the next line would   
   rem this is also a comment.   
      
      
   Caveat here.  If allfix is gonna touch the nodediff archive, and you   
   especially want to send it to downlinks or points   
   don't let the line delete that archive from fido=in or   
   allfix is gonna complain where it has to move the nodediff   
   archive somewhere else and generate .tic files for any   
   downlinks.   
      
   As for the rest, it could get rather convoluted and   
   complicated imho when IRex might already give you some of   
   the solution you seek here.  I don't know, may have the Irex docs around here   
   somewhere, but don't have time over the   
   next few days to pore over them.   
      
   Glad to help with some basic tutorial hand holding on how to create some good   
   batch files to help you along.  Get from   
   your uplink using whatever method you use to freq the   
   maximus bbs docs, some good basics on batch files there, and lots of good   
   stuff archived in the bfds.  Connect with the   
   POsitronium repository, iirc 1:19/68 possibly also flying   
   under 1:393/68, I haven't checked lately for a complete bfds archive.   
      
      
   POsting some of your batch code snippets may also help us   
   help you out, but first consult your irex docs.   
      
   maybe an irex user will delurk   
   that can give you some pointers as well.   
      
   Regards,   
              Richard   
   ---   
    * Origin:  (1:116/901)