wine users - Jan 2009 - Program believed to work in Wine, but not on my EeePC

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.

On Sat, Jan 3, 2009 at 1:08 PM, drossall <wineforum-user at winehq.org>
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

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

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?

:? 

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

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.

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

Thanks