PES2012 recently stopped working

mmdiego · Post by **mmdiego** » Wed Nov 30, 2011 7:31 am

I've recently updated wine version from 1.3.29 to 1.3.33 and I realised that PES2012 stopped working. It just opens a MessageBox with the text "The dynamic library rld.dll failed to initialize (E300)" and closes, without any error message on the terminal window.
I started downgrading the version of wine to check when the error started, and I can confirm that the problem started on version 1.3.31.
I'm running a Debian Sid and I've compiled wine from sources (as I've always done)
Can anybody confirm the bug? And how can I track the error?
Thanks, Diego

jjmckenzie · Post by **jjmckenzie** » Wed Nov 30, 2011 9:01 am

On Wed, Nov 30, 2011 at 5:31 AM, mmdiego <[email protected]> wrote:

I've recently updated wine version from 1.3.29 to 1.3.33 and I realised that PES2012 stopped working. It just opens
a MessageBox with the text "The dynamic library rld.dll failed to initialize (E300)" and closes, without any error
message on the terminal window.
I started downgrading the version of wine to check when the error started, and I can confirm that the problem
started on version 1.3.31.

Looks like a prime candidate for a Regression Test and Bug report.
Regression testing is described in the Wine Wiki in the Regression
Testing page (http://wiki.winehq.org/RegressionTesting).

Without information from the test, it is very difficult to resolve the problem.

Thank you.

James

vitamin · Post by **vitamin** » Thu Dec 01, 2011 12:03 am

mmdiego wrote:I've recently updated wine version from 1.3.29 to 1.3.33 and I realised that PES2012 stopped working.

See http://bugs.winehq.org/show_bug.cgi?id=29211 which is duplicate of http://bugs.winehq.org/show_bug.cgi?id=28994

mmdiego · Post by **mmdiego** » Thu Dec 01, 2011 7:48 am

Yes, excellent!
After doing the regression test, I found the patch that was causing the error. I submitted the bug and was instantly replied marking it as a duplicate of the bugs you mention above.
It can be solved applying this patch to version 1.3.32:
http://www.winehq.org/pipermail/wine-pa ... 08548.html

Although, I don't understand why it wasn't fixed in version 1.3.33... Is it because the patch needs to be verified? Will it be fixed in version 1.3.34? Perhaps some developer knows the answer...

Diego

jjmckenzie · Post by **jjmckenzie** » Thu Dec 01, 2011 9:29 am

On Thu, Dec 1, 2011 at 5:48 AM, mmdiego <[email protected]> wrote:

Yes, excellent!
After doing the regression test, I found the patch that was causing the error. I submitted the bug and was instantly replied marking it as a duplicate of the bugs you mention above.
It can be solved applying this patch to version 1.3.32:
http://www.winehq.org/pipermail/wine-pa ... 08548.html

Some patches are not approved because they cause problems with other
programs and some patches need more work because they do not match the
style of the existing code.

In the meantime, you can add this patch to the base Wine source code
and you can build Wine with it.

Hopefully, this patch can be corrected and it will be applied to Wine-1.3.34.

James

vitamin · Post by **vitamin** » Thu Dec 01, 2011 9:50 am

mmdiego wrote:Although, I don't understand why it wasn't fixed in version 1.3.33... Is it because the patch needs to be verified?

The patch needs lots of tests to cover as many cases as possible. Because changes to this area have to potential to break big number of different programs.

And it seems tests weren't covering enough ground for this fix to go in.

mmdiego · Post by **mmdiego** » Thu Dec 01, 2011 10:16 am

Thanks for your answers guys!
Diego