http://bugs.winehq.org/show_bug.cgi?id=4436
------- Additional Comments From J.A.Gow@furrybubble.co.uk 2006-01-02 04:27 ------- Re regression testing: I have tried this. there is another issue that effectively prevents identification of the exact patch that introduced this bug.
I could not get CVS much before 2005-05-03 to build on my system (I tried several prior versions spaced in time and I do not still have my old 32-bit system to try the build on). 2005-05-03 builds, but the app segfaults. Versions from 2005-05-03 until very recently (including CXO 5.0) result in the app segfault. However this segfault problem has now been fixed in recent CVS, so I am not going to spend time chasing it.
However, the OLE32/Storage problem I am describing in the bug report was introduced some time within the period where Wine would cause the app to segfault, so it is impossible to run the app on these versions of Wine, and determine exactly which CVS update introduced the OLE32/Storage problem.
Re: adding a test case: The problem here is that although I understand the failure _mechanism_, it looks like a sensible failure, i.e. a call that _should_ fail. This points to a subtle bug elsewhere in the storage API that is causing the app to misbehave. Not being a Windows apps programmer I have insufficient knowledge of the way in which the storage API _should_ operate to be able to spot the problem. That is why I offered to work with someone with better knowledge of the Windows API in order to get this resolved quickly.