I'm working from a QA-side of this. You are correct in the behavior. In our case, I found this behavior isolated to the following conditions: 1. The shared folder exists on the physical server's local disk (that the network drive is mapped to). 2. The administrator has performed a (network or standalone) installation directly at the server. 3. The installation, regardless the installation type (standalone or network), was done to the mapped drive (i.e. the shared local folder). This issue has plagued our application for years and finding information on tech threads have been fruitless. Thank you for the link you provided, because it's given me the first solid lead on this issue in a while. Try installing the standalone version of your application to a network drive (following my above conditions) on a 2003 Server. I would like to know if you are yielding the same results. QUERIES: Is this a known issue? I believe so, but is sorely under-reported. Interestingly, I found an MS article of a hotfix that's suppose to fix a similar issue: http://support.microsoft.com/kb/909423. This was included in the 2003 SP2 rollout. Oddly, I don't think the behavior occurred until after I did the SP2 update. I'll have to retest this clean 2003 machine again to confirm. If yes, why other OSs with NTFS do not behave the Windows Server 2003 way? I'd like to know the answer to that myself. I'm not sure who to take this fight to... Microsoft, Installshield or both. Other installation packages I've tested don't exhibit this behavior under the same conditions BUT this is OS-specific, so it can go other way.
... View more