http://bugs.winehq.org/show_bug.cgi?id=2957
thibault <fthibault(a)perinfo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fthibault(a)perinfo.com
--- Comment #7 from thibault <fthibault(a)perinfo.com> 2007-12-20 04:14:12 ---
Any Workaround ?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=10462
Summary: Vokabeltraier 3 ratail storage/space test of
installation crashes
Product: Wine
Version: 0.9.49.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thomas(a)haeber.de
In the installation dialoge of the ratail version of Vokabeltrainer 3 is the
option to calculate the space for installation. If you start this test wine
crashes.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7828
James Hawkins <truiken(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #10 from James Hawkins <truiken(a)gmail.com> 2007-12-20 00:48:18 ---
Closing.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7828
James Hawkins <truiken(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
--- Comment #9 from James Hawkins <truiken(a)gmail.com> 2007-12-20 00:47:54 ---
This bug and bug 8945 are duplicates, but I'm marking this as the duplicate
because the other bug has more information.
*** This bug has been marked as a duplicate of bug 8945 ***
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8051
--- Comment #29 from Stefan Dösinger <stefandoesinger(a)gmx.at> 2007-12-19 18:53:15 ---
I guess you're free to re-use the old surface or recreate it, but watch out for
the size. If the resolution changed you'll have to change the depth stencil
surface size as well. Either by recreating it, or by changing the surface like
it happens with the render targets.
Actually, I think it is better to just adjust the members in the surface,
otherwise you'll have to take care for re-creating the d3d8 and d3d9 surface as
well, not just the wined3d one.
You could extend the test to see what happens if you have any other surface in
D3DPOOL_DEFAULT. I think some MSDN page says that the application must release
all surfaces in D3DPOOL_DEFAULT(and depth stencil and render targets are in
that pool).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8051
--- Comment #27 from Stefan Dösinger <stefandoesinger(a)gmx.at> 2007-12-19 17:57:47 ---
Tests are always good :-)
I am not sure what you mean with "release any reference to the stencil buffer".
I think I can give a better comment when I see the test.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8051
--- Comment #26 from Peter Beutner <p.beutner(a)gmx.net> 2007-12-19 17:31:45 ---
(In reply to comment #22)
> > 2) next problem is that GetDepthStencilSurface() fails with D3DERR_NOTFOUND.
> > What happens is:
> > CreateDevice() called with AutoDepthStencil=true
> > SetDepthStencil(NULL)
> > Reset() called with AutoDepthStencil=true
> > GetDepthStencilSurface() is expected to return something.
> > Not sure what the proper fix is here. Just reassign the stencilBufferTarget to
> > existing auto_depth_stencil_buffer as done in the patch or create a new one ?
> Writing a test for this might reveal more information.
kinda stuck there. As it turns out you need to release any reference to the
stencil buffer before calling Reset(I can send a test for this if wanted), so I
see no way to check if the stencil buffer after the reset is still the old one
or a newly created one.
My guess would be it doesn't really matter if you do one or the other. Just
re-using the existing one is probably cheaper.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.