title: Locking is not possible in the directory C:\eclipse\configuration\org.eclipse.osgi
body: <p>I used to have Eclipse 3.5.2 working from my Limited User Account (i.e. not Administrator).</p>
  
  <p>But when I upgraded to 3.6.2, Eclipse refuses to run in the Limited User Account (it only runs under administrator).</p>
  
  <p>It issues the following error:</p>
  
  <blockquote>
    <p>Locking is not possible in the directory
    C:\eclipse\configuration\org.eclipse.osgi. A common reason is that the
    file system or Runtime Environment does not support file locking for
    that location. Please choose a different location, or disable file
    locking passing "-Dosgi.locking=none" as a VM argument.
    C:\eclipse\configuration\org.eclipse.osgi.manager.fileTableLock
    (Access is denied)</p>
  </blockquote>
  
  <p>Well, I checked the owner of that folder (Windows XP) and it is the Administrator, so of course access would be denied.</p>
  
  <p>But... why didn't this happen in Eclipse 3.5.2?</p>
  
  <p>I could probably workaround this by assigning ownership of the entire <code>C:\eclipse\configuration\org.eclipse.osgi</code> but without understanding why, I don't know whether I would need to do that for additional folders.</p>
  
  <p>Another workaround is to do just as the error message suggests: Disable file locking passing <code>-Dosgi.locking=none</code> as a VM argument. But I don't what the tradeoff would be (locking is there for a reason, right? What is it?)</p>
  
  <p>If I understand what the purpose of that locking is, I can wisely choose one of the 2 workarounds outlined above.</p>