DS2KX0JqNl0qpXR88whloYtQi0wZ!ONfCCB/HDzQpMVT1Sa16Fdvcs4c4cSMUSMi   
   yI8UWakH5XEaenJz0wguwzLOUnfo3DQb02DSJjw2!ky95IEE=   
   properly   
   p.os.os2.misc:3036 comp.os.os2.beta:59   
   From: "Mark Dodel"    
      
   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.   
      
   I have seen this (or something real close to it) FAT32 CHKDSK error in   
   the past.  Currently I have no windows installed anywhere, but since I   
   stopped playing with Linux I haven't done much with my FAT32 volume    
   either.  I'd be willing to test it if you make it available.   
      
   Mark   
      
      
   --    
   From the eComStation  2.0 GA desktop of Mark Dodel   
      
   Warpstock 2010 - http://www.warpstock.org   
   Warpstock Europe 2010 - http://www.warpstock.eu    
      
   --- Internet Rex 2.31   
    * Origin: VOICE - http://www.os2voice.org (1:261/20.999)