From: sjack@dontemail.me   
      
   Ha,ha. Fooled myself looking at file id (FDIID) for zero value to   
   indicate cleanup took place. When file i/o failed because file foo   
   didn't exist, FDIID never got set so was always zero. (there were   
   other means of verifying that cleanup code got accessed, e.g. the   
   "FVIEWS abandon' being printed.   
   But to see FDIID being reset I needed to at least get the file opened   
   and then have it fail. So just open a corrupt file. No! Whatever I   
   put into a file, nulls and control characters, does not make the i/o   
   fail! To have failure has to be done on my end in processing the   
   data. So patched UABORT into a low level part that was acting   
   on the data. Mission achomplished.   
      
   --   
   me   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)