http://bugs.winehq.org/show_bug.cgi?id=16956
Gustavo Conte gustavo@ventania.blog.br changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gustavo@ventania.blog.br
--- Comment #31 from Gustavo Conte gustavo@ventania.blog.br 2010-08-27 12:08:53 --- (In reply to comment #27)
Created an attachment (id=27423)
--> (http://bugs.winehq.org/attachment.cgi?id=27423) [details]
patches
The patches let the installer crash at a later time, although invoking the installer again afterwards replies that the product is already installer (and the files seem to be there).
From the voicewarmup log it looks windows msi moves the rows with conflicting diskids temporarily:
http://www.eggheadcafe.com/forumarchives/windowsmsi/Nov2005/post24581380.asp
Would this help? Seems like same problem, so well, it can also affect Windows developers (note this is from 2005) so a good way is to understand the best practice from Microsoft, how the demon itself solves this issue.
I'm not even close of a good dev and very far from Windows developer, but I know how to google and want to help with this issue. It affects wine too much to let it go. So here's my idea: if it can also affect a windows dev, whats the best practice AS windows dev? How Microsoft solves the problem?
ALSO, these people might know something: http://wix.sourceforge.net/ -> looks like They are specialized is MSI, we should check their code because the solution might be there!
cya