http://bugs.winehq.org/show_bug.cgi?id=3950
------- Additional Comments From penna@bb.com.br 2006-02-02 11:27 ------- One solution discussed at wine-devel list is to put "user.exe" (and of course start.exe and/or sound.dll) in "native,builtin" order. To solve the *.exe problems, you can follow the steps (the sound.dll solution is described later): a) launch winecfg (command line: winecfg) b) click at the "Application" tab c) click at the "Default Settings" d) click at the "Libraries" tab e) at the "New override for library" field, put the name of the executable (user.exe or start.exe) f) then click the "Add" button g) click the "Apply" button and then the "OK" button It worked for me. For the sound.dll problem you *must know* the name of the executable is trying to use it. Let's give it a fake name just to make an example: "foo.exe" needs sound.dll a) launch winecfg (command line: winecfg) b) click at the "Application" tab c) click at "Add application" button d) add the application that needs the sound.dll (in our case: foo.exe) e) still at the "Application" tab, click the executable you have just added (foo.exe) f) click at the "Libraries" tab g) at the "New override for library" field, put the name of the dll: sound.dll h) then click the "Add" button (obs.: that means sound.dll will be used in the order "native,builtin" *only* for the executable - foo.exe - you have just clicked right before in the "Application" tab). You can also change the order of DLL's by clicking on the "Edit" button. But in this case you will want "native, builtin" because of the sound.dll+executable problem. i) click the "Apply" button and then the "OK" button Hope this helps.