http://bugs.winehq.org/show_bug.cgi?id=15887
--- Comment #10 from Forester pbronline-wine@yahoo.co.uk 2009-01-19 00:31:34 --- (In reply to comment #9)
Hello,
just experienced the same issue while testing Microsoft Visual Studio Express Versions with some Frameworks and SDKs installed prior into WINEPREFIX.
Ah, sweet read-only issue again.
Although msi's cabinet_copy_file() ensures that newly created (extracted cabinet) files have sane attributes set, it fails to handle the case when the file to be replaced is already present with read-only attributes - which leads to failure when trying to re-create.
Adjusting the file attributes of existing files to force the successful re-creation fixes the problem.
If I understand your diagnosis correctly, I should find files under $WINEPREFIX that are read-only and if I change the permissions of these files to read/write then I should be able to install my application.
There are no read-only files under $WINEPREFIX either before or after the attempted installation and there are none created in C:\windows\temp during the installation either.
However it does seem to be a problem overwriting existing files. Installer logs have the failed installation ending with the copy of C:\windows\system32\mfc42.dll and log of from successful installation following this with C:\windows\system32\msvcirt.dll. Both of these files are extracted from vcredist.dll as part of winetricks wsh56.
Although I can't be sure, this does not look like a difference between upper and lower case filenames either. What other possibilities are there ?