<div dir="ltr"><div>Your design is wrong IMO. You don't handle reparse points at all; you only rely on the nature of a drive, which isn't sufficient in most cases. See mounting volumes for example where you can mount a whole volume anywhere in an NTFS partition.</div>
<div> </div>
<div>The correct fix would be to:</div>
<div>- ensure your code handles those cases correctly (which it doesn't)</div>
<div>- ensure that wine returns the correct relevant information for remote mounted FS (which I'm pretty sure sure it's not done today)</div>
<div><br>A+</div>
<div class="gmail_quote">2008/9/30 Mark Wagner <span dir="ltr"><<a href="mailto:carnildo@gmail.com">carnildo@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="Wj3C7c"><br>On Mon, Sep 29, 2008 at 14:55, Juan Lang <<a href="mailto:juan.lang@gmail.com">juan.lang@gmail.com</a>> wrote:<br>>> Did you read the second paragraph of my original email? I'm not<br>
>> working around a bug in Wine, unless it's a bug that a user can map<br>>> "/" to "C:" and call it a "fixed disk".<br>><br>> Yes, I read it. And scanning "/" shouldn't be a problem, unless<br>
> you've also mapped network drives there. That seems to be the root of<br>> the problem.<br><br></div></div>Yes, that's the root of the problem. I can't prevent the end-user<br>from mounting network drives -- in fact, in the expected installation<br>
environment, the average user will have several very large network<br>drives mounted.<br><br>Under Windows, installation takes about five minutes, and the<br>full-disk search provides a nicer user experience if they're upgrading<br>
from an ancient copy of the software. Under Wine, I need to either<br>skip the full-disk search, or warn the user that it may take several<br>hours.<br><br>--<br><font color="#888888">Mark<br><br><br><br><br></font></blockquote>
</div><br><br clear="all"><br>-- <br>-- <br>Eric Pouech<br></div>