Program believed to work in Wine, but not on my EeePC

drossall · Post by **drossall** » Sat Jan 03, 2009 2:08 pm

I'm trying to use Wine on an EeePC 701 in advanced mode. I think my Wine installation is basically OK, because I copied Windows Freecell (which was originally written as a test of the Win32s subsystem of course) across and it runs OK.

The program I actually want to run (Laridian PocketBible) has been reported as working by other Wine users. It doesn't for me. My guess is that the EeePC lacks some packages that support Wine. I tried installing all the required packages (as advised in Bugzilla) and filled my disc up - the EeePC is after all a small machine in all respects. How can I tell which are the packages required for my specific application?

The Laridian splash screen appears in Wine, but nothing else happens.

The errors I get are as follows:

fixme:system:SystemParametersInfoW Unimplemented action: 4114
(SPI_GETMENUFADE)
fixme:htmlhelp:HtmlHelpW HH case HH_INITIALIZE not handled.
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:advapi:LookupAccountNameW (null) L"eeepc-davidross" (nil) 0x33fc0c
(nil) 0x33fc10 0x33fc04 - stub
fixme:advapi:LookupAccountNameW (null) L"eeepc-davidross" 0xb697d0
0x33fc0c 0xb68c20 0x33fc10 0x33fc04 - stub
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=0033eba0 lp=0033eb90
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=0033ed6c lp=0033ed5c
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=0033ed74 lp=0033ed64

Thanks in advance.

austin987 · Post by **austin987** » Sat Jan 03, 2009 2:42 pm

On Sat, Jan 3, 2009 at 1:08 PM, drossall <[email protected]> wrote:

I'm trying to use Wine on an EeePC 701 in advanced mode. I think my Wine installation is basically OK, because I copied Windows Freecell (which was originally written as a test of the Win32s subsystem of course) across and it runs OK.

The program I actually want to run (Laridian PocketBible) has been reported as working by other Wine users. It doesn't for me. My guess is that the EeePC lacks some packages that support Wine. I tried installing all the required packages (as advised in Bugzilla) and filled my disc up - the EeePC is after all a small machine in all respects. How can I tell which are the packages required for my specific application?

The Laridian splash screen appears in Wine, but nothing else happens.

The errors I get are as follows:

fixme:system:SystemParametersInfoW Unimplemented action: 4114
(SPI_GETMENUFADE)
fixme:htmlhelp:HtmlHelpW HH case HH_INITIALIZE not handled.
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:advapi:LookupAccountNameW (null) L"eeepc-davidross" (nil) 0x33fc0c
(nil) 0x33fc10 0x33fc04 - stub
fixme:advapi:LookupAccountNameW (null) L"eeepc-davidross" 0xb697d0
0x33fc0c 0xb68c20 0x33fc10 0x33fc04 - stub
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=0033eba0 lp=0033eb90
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=0033ed6c lp=0033ed5c
err:toolbar:ToolbarWindowProc unknown msg 0466 wp=0033ed74 lp=0033ed64

Thanks in advance.

Most of the needed packages are only for compiling wine, not for running it.

Looking at the log, you might try native comctl32, but that's only a
guess. Is there a download available?

--
-Austin

drossall · Post by **drossall** » Sat Jan 03, 2009 6:13 pm

Thanks for the reply. comctl32 isn't listed in the Synaptic Package Manager. I'll have to do some digging to figure out whether any repository has a native package. Would any Debian one be likely to be OK or should it be native i.e. EeePC-specific? I'm still pretty much a newbie here.

BTW I should have mentioned that, when I installed all the packages as above, PocketBible produced an error that the working directory permissions did not allow writing. Actually the permissions were OK - I think it was the disc being full that prevented writing... This supports my idea that a missing package was the issue. comctl32 was not listed among the packages installed (and that I then removed to restore a working system).

Regards

drossall · Post by **drossall** » Sat Jan 03, 2009 6:15 pm

Sorry, just dawned on me, you mean the Windows comctl32 DLL - should have spotted it from the naming. Apart from taking it from a Windows install, which rather negates the point of Wine in avoiding licence issues, where would I find one?

austin987 · Post by **austin987** » Sat Jan 03, 2009 6:18 pm

On Sat, Jan 3, 2009 at 5:13 PM, drossall <[email protected]> wrote:

Thanks for the reply. comctl32 isn't listed in the Synaptic Package Manager. I'll have to do some digging to figure out whether any repository has a native package. Would any Debian one be likely to be OK or should it be native i.e. EeePC-specific? I'm still pretty much a newbie here.

comctl32 is a windows dll, it won't be in the repository. Use:

$ wget kegel.com/wine/winetricks
$ sh winetricks cc580

--
-Austin

drossall · Post by **drossall** » Sat Jan 03, 2009 7:12 pm

App requires comctl32.dll v5.81 or higher and that gave me 5.80...

drossall · Post by **drossall** » Sat Jan 03, 2009 7:21 pm

OK, so that was the problem because I have now substituted a later DLL and it ran. Program can't currently see the books it should be reading, but I'll look into that. Thanks.

Curiosity though - if the point of Wine is to avoid dependence on proprietary MS software, does this mean that:

I need a Wine component to do the job of this DLL, or:

The software I want to run depends on something (this DLL) not yet developed for Wine?

Regards

austin987 · Post by **austin987** » Sat Jan 03, 2009 7:39 pm

On Sat, Jan 3, 2009 at 6:21 PM, drossall <[email protected]> wrote:

OK, so that was the problem because I have now substituted a later DLL and it ran. Program can't currently see the books it should be reading, but I'll look into that. Thanks.

Curiosity though - if the point of Wine is to avoid dependence on proprietary MS software, does this mean that:

I need a Wine component to do the job of this DLL, or:
The software I want to run depends on something (this DLL) not yet developed for Wine?

The DLL is implemented in wine, but is not complete. File a bug at
http://bugs.winehq.org. Be sure to check for dupes first.

--
-Austin

Post by **DanKegel** » Sat Jan 03, 2009 8:42 pm

drossall wrote: App requires comctl32.dll v5.81 or higher and that gave me 5.80...

Please file a bug at http://bugs.winehq.org,
including the URL for the app
(http://www.laridian.com/pc/).

Please attach a log produced like this:

WINEDEBUG=+relay wine bible.exe > log.txt 2>&1

(substitute the real app name for bible.exe)
in a clean .wine directory, i.e. one without the native comctl32.

drossall · Post by **drossall** » Tue Jan 06, 2009 6:51 pm

Thanks. I now have a fully-working application. I have submitted this bug:
http://bugs.winehq.org/show_bug.cgi?id=16835

Recreating the bug was fun - I uninstalled Wine to get a clean install, and found I couldn't run the PocketBible installer under 1.1.11. Therefore I had to downgrade to Wine 0.9.25, install the Windows program, and upgrade Wine again

I'm grateful for the advice, and I even feel I have learnt a little of how Wine works

James McKenzie · Post by **James McKenzie** » Thu Jan 08, 2009 10:59 pm

drossall wrote:

Thanks. I now have a fully-working application. I have submitted this bug:
http://bugs.winehq.org/show_bug.cgi?id=16835 (http://bugs.winehq.org/show_bug.cgi?id=16835)

I linked in the bug report to the AppDB entry.

I will attempt to get this program and run it as well on Wine for MacOSX.

James McKenzie

drossall · Post by **drossall** » Sun Jan 25, 2009 5:29 pm

Dumb question but what is the meaning of the 2>&1 on the winedebug command line?

Thanks

austin987 · Post by **austin987** » Sun Jan 25, 2009 5:35 pm

On Sun, Jan 25, 2009 at 4:29 PM, drossall <[email protected]> wrote:

Dumb question but what is the meaning of the 2>&1 on the winedebug command line?

Thanks

It redirects all terminal output to wherever STDOUT is going. More specifically
2 = STDERR
1 = STDOUT

= redirect

& = and

so you're saying:

redirect STDERR (2) to the same place as STDOUT (1)

--
-Austin