p.os.os2.misc:3013 comp.os.os2.beta:45   
   From: "Andy"    
      
   On Sat, 26 Mar 2011 13:56:56 UTC, Jonathan de Boyne Pollard    
    wrote:   
      
   > >>> The current FAT32 check often leads to a msg like: Please run u$    
   > >>> Scandisk to fix your partition :-/   
   > >>>   
   > >> Not knowing what error causes that, or even what the real message is    
   > >> (which what you write clearly is not), I cannot address specifics.   
   > >>   
   > > That really is very close to the message that you will get if you do a    
   > > chkdsk /f on a fat32 volume under OS/2 (at least if there is anything    
   > > non-trivial that chkdsk needs to do). It basically just says it sees    
   > > something it doesn't know how to handle and to run scandisk under    
   > > windows. When I then run a chkdsk under windows it doesn't generally    
   > > even seem to do much but then when reconnected to OS/2 and a chkdsk is    
   > > run it will run clean.   
   > >   
   >    
   > My goodness! Even the "u$" part?   
   >    
   > Pointing the user at Microsoft tools for everything is rather a cop-out.    
   > I can understand the desire for something better.   
   >    
   > Do you actually end up in this situation a lot? Because if this is a    
   > regular occurrence for you it might be interesting to see (a) what the    
   > error is that SCANDISK fixes, and (b) whether my volume checker can fix    
   > it. It might, after all, be an error that I haven't already thought of,    
   > or caused; and I can add it to the repair list. I mentioned earlier in    
   > this thread that I brought this up only for the sake of completeness,    
   > nothing more. But if there's a regular problem, that actually occurs in    
   > practice nowadays  that someone is genuinely experiencing xyrself as an    
   > on-going annoyance from month to month  then it's worth seeing whether    
   > CHKVOL will help.   
   >    
   Well, won't say the u$ part is actually part of it :-) but the overall   
   message is quite close.   
   It occurs if I forget to eject a USB drive before pulling it out, this   
   is most likely to occur if I have more than one drive connected and    
   remember to do the eject but eject the wrong drive by mistake.  Of    
   course a trap can cause the same condition if the USB drive is    
   connected.     
   Andy   
   --    
      
      
   --- Internet Rex 2.31   
    * Origin: TeraNews.com (1:261/20.999)