<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div><pre><br><br>>You've handled *a* successful case, but what about the error case?<br><br>As i said already in the mail with the patch, it might be *a* case, but this is the case <br>that most apps will follow as far as i can see. Futhermore, when apps are really crashing <br>into the other cases, it can be added later on i.m.o. For now they will just fall back to the current <br>"implementation", returning "not implmented" then, so there will be no differnce with current behaviour.<br><br><br>+ {<br>+ lstrcpynW(volumepathname,filename,4);<br>+ return TRUE;<br>+ }<br><br><br>>Also, you're copying 4 bytes of filename into volumepathname. I don't<br>>think you understand what lstrcpyn does. Imagine this case:<br><br>volumepathname = "aaaaaaaa"<br>buflen =
8<br>filename = "C:\\file"<br><br>After the call to lstrcpyn:<br><br>volumepathname = "C:\\faaaa"<br><br><br><br>MSDN says volumepathname was a pointer to an "out" - string, so how would it become someting<br>like "aaaaaa", or am i overseeing something?<br></pre></div></div><br>Send instant messages to your online friends http://uk.messenger.yahoo.com </body></html>