How to deal with the message: winedevice.exe has encountered

Yuri · Post by **Yuri** » Tue Apr 28, 2009 6:42 am

Since recent update I am getting this error:

Program Error
The program winedevice.exe has encountered a serious problem and needs
to close. We are sorry for the inconvenience.

I realize that I probably have some malfunctioning device driver.

How to fix this? How to remove the driver?

Yuri

vitamin · Post by **vitamin** » Tue Apr 28, 2009 8:52 am

Yuri wrote:How to fix this? How to remove the driver?

Unless you want to implement missing features you can't fix it.

To remove driver - just remove the driver file "*.sys" from windows/system32/drivers directory. A cleaner way would be to disable it in registry or remove it's complete section.

MindFlayer · Post by **MindFlayer** » Tue Apr 28, 2009 9:15 am

Also, remember to check the contents of windows/system32/drivers. I had the Starforce copy protection (sfdrv01.sys) in there, which caused a crash for me.

Montblanc · Post by **Montblanc** » Wed Apr 29, 2009 5:08 pm

I'd call this a regression, not a new feature.
I'm running many games with starforce protection, and when winedevice.exe has a problem, the game crashes to let this annoying message appear. I had to create wineprefixes to older versions of wine just to let my apps work as they should. Please, don't underestimate this post: I'm sure many people running various apps are having this issue.

austin987 · Post by **austin987** » Wed Apr 29, 2009 5:27 pm

On Wed, Apr 29, 2009 at 5:08 PM, Montblanc <[email protected]> wrote:

I'd call this a regression, not a new feature.

And for users that had random crashes with no explanation, they'd
think quite differently. You can't have your cake and eat it to.

I'm running many games with starforce protection, and when winedevice.exe has a problem, the game crashes to let this annoying message appear. I had to create wineprefixes to older versions of wine just to let my apps work as they should. Please, don't underestimate this post: I'm sure many people running various apps are having this issue.

You can use:
$ WINEDLLOVERRIDES="winedbg.exe=d" wine foo.exe to work around it.

That disables the debugger, but no error will appear.

--
-Austin

Montblanc · Post by **Montblanc** » Fri May 01, 2009 10:39 am

austin987 wrote:And for users that had random crashes with no explanation, they'd think quite differently. You can't have your cake and eat it to.

I don't get it: if an app crashes, I'm used to debug it from shell. Users can do as they did till 1.1.20. I think no one has asked for a buggy feature.

austin987 wrote:You can use:
$ WINEDLLOVERRIDES="winedbg.exe=d" wine foo.exe to work around it.

Thank you, I'll try it when I'll be forced to use wine >= 1.1.20.

austin987 · Post by **austin987** » Fri May 01, 2009 11:08 am

On Fri, May 1, 2009 at 10:39 AM, Montblanc <[email protected]> wrote:

austin987 wrote:
And for users that had random crashes with no explanation, they'd think quite differently. You can't have your cake and eat it to.
I don't get it: if an app crashes, I'm used to debug it from shell. Users can do as they did till 1.1.20. I think no one has asked for a buggy feature.

You may be, and that's good. But _a ton_ of users aren't using the
command line. And to be honest, we've put a lot of work into making
sure they don't have to.

It's not a buggy feature, it works fine. The bug is elsewhere, in
whatever's crashing

.

austin987 wrote:
You can use:
$ WINEDLLOVERRIDES="winedbg.exe=d" wine foo.exe to work around it.
Thank you, I'll try it when I'll be forced to use wine >= 1.1.20.

Apparently there's also a registry key, though I can't find it off
hand. Search the registry for 'showgui'.

--
-Austin

Post by **dimesio** » Fri May 01, 2009 11:50 am

austin987 wrote: You may be, and that's good. But _a ton_ of users aren't using the
command line. And to be honest, we've put a lot of work into making
sure they don't have to.

It's not a buggy feature, it works fine. The bug is elsewhere, in
whatever's crashing .

Sure, whatever's crashing is a bug, but for apps that used to continue despite the crash and are now failing to work solely because of the dialog box, I'd say that's a regression. And I question how much use this dialog box really is. It doesn't tell users anything they couldn't figure out from the fact that their app never started, and they are going to have to run the app from the command line anyway to debug it any further. Windows itself doesn't give users any such message, and Wine was already showing similar messages generated by the apps themselves just fine. JMHO.

austin987 · Post by **austin987** » Fri May 01, 2009 11:56 am

On Fri, May 1, 2009 at 11:50 AM, dimesio <[email protected]> wrote:

austin987 wrote:
You may be, and that's good. But _a ton_ of users aren't using the
command line. And to be honest, we've put a lot of work into making
sure they don't have to.

It's not a buggy feature, it works fine. The bug is elsewhere, in
whatever's crashing .

Sure, whatever's crashing is a bug, but for apps that used to continue despite the crash and are now failing to work solely because of the dialog box, I'd say that's a regression. And I question how much use this dialog box really is. It doesn't tell users anything they couldn't figure out from the fact that their app never started, and they are going to have to run the app from the command line anyway to debug it any further. Windows itself doesn't give users any such message, and Wine was already showing similar messages generated by the apps themselves just fine. JMHO.

Windows also had a complete ntoskrnl.exe implementation

Perhaps it will annoy people enough that they write patches to fix
those bugs <g>...

--
-Austin

mocham · Post by **mocham** » Sat May 02, 2009 2:34 am

I guess I'm late to the party. I'm getting this error on just about every program I run under Wine since I updated to 1.1.20. Even the Wine Configuration tool makes this error show up first. What is happening here?

I had 4 files in my ~/.wine/drive_c/windows/system32/drivers directory.

mountmgr.sys
MrtRate.sys
PxHelp20.sys
pxhelper.sys

If I move all of them out, the error popup stops showing up, but what are these files there for and what problems will I cause by moving them out? I use Wine with a number of CD/DVD applications, is this going to cause problems?

Post by **dimesio** » Sat May 02, 2009 8:14 am

mocham wrote:I guess I'm late to the party. I'm getting this error on just about every program I run under Wine since I updated to 1.1.20. Even the Wine Configuration tool makes this error show up first. What is happening here?

I had 4 files in my ~/.wine/drive_c/windows/system32/drivers directory.

mountmgr.sys
MrtRate.sys
PxHelp20.sys
pxhelper.sys

If I move all of them out, the error popup stops showing up, but what are these files there for and what problems will I cause by moving them out? I use Wine with a number of CD/DVD applications, is this going to cause problems?

Those are all device drivers, probably installed by the CD/DVD apps, none of which Wine can use anyway. In Windows they would load at boot, so Wine will try to load them whenever you start anything in Wine. They have been crashing in the background all along, you just didn't know about it until the useless and annoying GUI crash dialog was added in 1.1.20.

vitamin · Post by **vitamin** » Sat May 02, 2009 11:14 am

mocham wrote:I had 4 files in my ~/.wine/drive_c/windows/system32/drivers directory.
mountmgr.sys
MrtRate.sys
PxHelp20.sys
pxhelper.sys

Do not touch mountmgr.sys it's Wine's own "driver".

mocham wrote:If I move all of them out, the error popup stops showing up, but what are these files there for and what problems will I cause by moving them out? I use Wine with a number of CD/DVD applications, is this going to cause problems?

Doubt, they don't work as-is anyway.

mocham · Post by **mocham** » Sat May 02, 2009 11:56 pm

Thanks for the explanations. I guess I missed this in the release notes for 1.1.20. Anyway, I moved mountmgr.sys back in and kept the other ones out and everything is fine.

Post by **dimesio** » Tue May 05, 2009 8:36 am

austin987 wrote: Apparently there's also a registry key, though I can't find it off
hand. Search the registry for 'showgui'.
-Austin

The key is "ShowCrashDialog." I've added instructions to the FAQ on how to disable it.
http://wiki.winehq.org/FAQ#head-c857c43 ... 25483c91d6

monkeyslayer56 · Post by **monkeyslayer56** » Fri May 08, 2009 7:45 am

so is there anyway to fix it? because in my system32/drivers is teh wine driver and a punk buster driver and punkbuster works fine untill i get that error and then punkbuster (in cod4) starts complaining also removeing it from the system32/drivers just causes more punkbuster problems

any ideas?

vitamin · Post by **vitamin** » Fri May 08, 2009 10:10 am

monkeyslayer56 wrote:so is there anyway to fix it?

Disable this new GUI popup via registry. Set ShowCrashDialog to 1 ( http://wiki.winehq.org/UsefulRegistryKeys )

mocham · Post by **mocham** » Fri May 08, 2009 11:58 pm

Thanks for the registry fix. I was able to move my other driver files back in the dir and it works fine again.