>BS> A new version of AllFix is now available.  Please visit   
    >BS> www.allfix.com for it   
    >   
    > this is GREAT news! however, i think i'll wait a bit until the fileshare   
    > bug is handled... IIRC, i run the universal version... i have to run it   
    > as a separate task during my midnight maint when the mailer nodes are   
    > down because there is tha above mentioned MSG file sharing bug... when   
    > my FD is running and rescanning the mailer's netmail area, there are   
    > times when FD and AF were trying to access the same MSG file at the same   
    > time... in those cases, AF lost and generally hung on me requiring a   
    > hard reboot of the Warp3Connect system...   
    >   
    > dunno if this bug has ever been reported but if not, it is now :P ;)   
      
    BS>       I also use the UNI version here, two separate processes in   
    BS> fact, although under Warp 4 FP13, and have never seen this happen   
    BS> here.  I run IM and AllFix as separate processes, in separate   
    BS> windows, only communicating via the semaphore flags.   
      
   ummm... i was running it as a background task while the mailers were all still   
   active... mail would come in and a semaphore created then when the semaphore   
   was seen, it would kick off the mail and file tossing... this was specific to   
   the maint of the netmail area but i forget if it was when looking for filefix   
   messages or what...   
      
    BS>       You couldn't simply close the AllFix window, and then restart   
    BS> it?    
      
   no, the window would not close at all and the entire system would hang... in   
   some cases, the mouse would move but nothing would respond... in other cases,   
   the mouse would not move at all... some cases had the keyboard dead, too...   
   those required a power off... if i was lucky and happened to be right here at   
   the console, i might be able to catch it and CAD instead of power off... at   
   least CAD generally closed all the open files (logs mainly) and allowed for a   
   reboot... the loss of data in the logs was probably the worst aspect :?   
      
   i'll have to dig out my process batch and cmd files... i know that i broke the   
   processing into separate tasks that ran serially while the whole tossing ran   
   parallel to the mailers in the background... i finally had to adjust to   
   processing mail like this and move allfix processing to midnight maint...   
   IIRC, it was that one of the FD nodes would rescan and netmail area while   
   allfix was in there and when they both grabbed the same netmail file, this   
   would happen... FD would move on but the allfix task was jammed...   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)