wine users - Jul 2008 - How to fix "CAPI 2.0 not installed"?

Hallo,

I recently installed wine 1.1.2 on my SlackWare 12.1 Linux
system, because I have to run a hardware debugging program
which only runs under Windows.
When I run the application, i get the message "CAPI 2.0 not
installed".
In the same directory as the application there's a file
called capi2032.dll, and I suspect that has something to
do with it.
If so, how do I tell wine that is should use it?
I've never used Windows and am absolutely new to wine,
so please tell me in a easy to understand way :)

Groeten,

           Hans.

jdh punt beekhuizen bij duinheks punt nl

--- GoldED+/LNX 1.1.5/080603
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)

lists.wine-users wrote:
> 
> 
> When I run the application, i get the message "CAPI 2.0 not
> installed".
> In the same directory as the application there's a file
> called capi2032.dll, and I suspect that has something to
> do with it.
> If so, how do I tell wine that is should use it?
> I've never used Windows and am absolutely new to wine,
> so please tell me in a easy to understand way :)
> 
> 

Overrides are set in winecfg, on the Libraries tab.

Hello,

On Friday July 25 2008, dimesio wrote to wine-users at winehq.org:

 >> When I run the application, i get the message "CAPI 2.0 not
 >> installed".
 >> In the same directory as the application there's a file
 >> called capi2032.dll, and I suspect that has something to
 >> do with it.
 >> If so, how do I tell wine that is should use it?
 >> I've never used Windows and am absolutely new to wine,
 >> so please tell me in a easy to understand way :)

 di> Overrides are set in winecfg, on the Libraries tab.

I'm afraid this was not simple enough for me :(
In winecfg I added capi2032.dll under libraries, but still
I get the message. I tried both without path and with full
path.
What am I doing wrong?

Regards,

           Hans.

jdh dot beekhuizen at duinheks dot nl
--- GoldED+/LNX 1.1.5/080603
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)

You don't need the path in winecfg. Try copying the dll to to Wine's
windows/system32 directory. If that doesn't work, post console output.

Hallo.

Op zaterdag 26 juli 2008 schreef dimesio aan wine-users at winehq.org:

 di> You don't need the path in winecfg. Try copying the dll to to
 di> Wine's windows/system32 directory.

What's that in Linux language?

 di> If that doesn't work, post console output.

The console output is not very interesting:
jbeekhui at duinheks:~/test$ wine dtrace32.exe -s -m -d2 -d3 -c2 -c3 -nt3 -c4
-c5
CAPI 2.0 not installed

That's all!

Groeten,

           Hans.

jdh punt beekhuizen bij duinheks punt nl

--- GoldED+/LNX 1.1.5/080726
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)

Hallo

Op zaterdag 26 juli 2008 schreef mikolajz aan wine-users at winehq.org:

 mi> Wine provides its own capi2032,

I noticed that later: there exists a /usr/lib/wine/capi2032.dll.so

 mi> however it gets built only when a Linux libcapi20 is installed
 mi> and the header linux/capi.h is present. At the end of ./configure
 mi> (the first step when building Wine from sources) you will get a
 mi> messages "libcapi20 not found,ISDN won't be supported" if
these
 mi> tests fail. You could check if you have capi support properly set
 mi> up.

Just to make certain I double checked this, and .configure really
is not complaining about a missing libcapi after the help I got
earlier from members of this list. The only missing librarie is
libgphoto2, but I couldn't care less about that.

 mi> As it was said, you could also try to use this capi2032.dll.
 mi> Copy it to Wine system32 folder and set "capi2032.dll" to
 mi> "native" in winecfg Library tab. However, as I understand,
this
 mi> is a hardware access library, so this may not work.

Whatever the reason, it still doesn't work :(
I guess I'll see what I van do with the live Windows CD I've got.
Although that involves setting up the network on that, and I really
am a Windows nitwit...

Groeten,

           Hans.

jdh punt beekhuizen bij duinheks punt nl

--- GoldED+/LNX 1.1.5/080726
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)

That message "CAPI 2.0 not installed" is printed from the app itsself
right? It would be interesting to see what the calls are just before  that
message appears.
You could run the app like

WINEDEBUG=+relay,+seh,+tid wine appname.exe &>/tmp/log.txt

and then put the file /tmp/log.txt (bzipped2) up somewhere. then we'd could
have a look what happens just before the error message appears`

Hello,

On Sunday July 27 2008, qwertymn wrote to wine-users at winehq.org:

 qw> That message "CAPI 2.0 not installed" is printed from the app
 qw> itsself right?

I suppose so :)

 qw>  It would be interesting to see what the calls are
 qw> just before  that message appears.

I'm willing to do anything that may help :) I need to run this
application for the support department of the factory of my
ADSL modem and they assume everybody is running Windows :(

 qw>  You could run the app like
 qw> WINEDEBUG=+relay,+seh,+tid wine appname.exe &>/tmp/log.txt
 qw> and then put the file /tmp/log.txt (bzipped2) up somewhere.

Done. It is [or should be :)] available as
http://www.duinheks.nl/files/testing/wine-dtrace_beekhuizen.log.bz2
or
ftp://ftp.duinheks.nl/pub/testing/wine-dtrace_beekhuizen.log.bz2

 qw> then we'd could have a look what happens just before the error
 qw> message appears`

I'm really curious to hear what will be the result of this.
Even if I'm doing something extremely stupid :) This is the
first time I use wine and have always tried to avoid Windows.

Regards,

           Hans.

jdh dot beekhuizen at duinheks dot nl
--- GoldED+/LNX 1.1.5/080726
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)

Though i'm not familiar with capi at all, your log looks pretty easy to
understand:

0009:Ret  PE DLL (proc=0x7ef5b280,module=0x7ef50000
L"capi2032.dll",reason=PROCESS_ATTACH,res=(nil)) retval=1
0009:Ret  KERNEL32.LoadLibraryA() retval=7ef50000 ret=0040be3d
0009:Call KERNEL32.GetProcAddress(7ef50000,0041cc10 "CAPI_REGISTER")
ret=0040be6b
and more and more of these

0009:Call KERNEL32.GetProcAddress(7ef50000,0041ccc8 "CAPI_INSTALLED")
ret=0040bf37
0009:Ret  KERNEL32.GetProcAddress() retval=7ef5a8ac ret=0040bf37


0009:Call capi2032.CAPI_INSTALLED() ret=0040d2c9
0009:Ret  capi2032.CAPI_INSTALLED() retval=00001009 ret=0040d2c9

0009:Call KERNEL32.FreeLibrary(7ef50000) ret=0040bf6f
0009:Call PE DLL (proc=0x7ef5b280,module=0x7ef50000
L"capi2032.dll",reason=PROCESS_DETACH,res=(nil))
0009:Ret  PE DLL (proc=0x7ef5b280,module=0x7ef50000
L"capi2032.dll",reason=PROCESS_DETACH,res=(nil)) retval=1
0009:Ret  KERNEL32.FreeLibrary() retval=00000001 ret=0040bf6f

CAPI 2.0 not installed


So apparently it's not happy with the value CAPI_INSTALLED returned here:
retval=00001009

I had a quick look at the source, and if you hadn't installed capi, it would
return 0x1109, you have 0x1009,  so it is installed apparently.

I did some google, but i couldn't find really anything what the return value
should be for capi2.0, there was one site that mentioned 0 , but i find that
strange. I hacked together a quick program that returns the value from
CAPI_INSTALLED, and on my computer i too get 0x1009. Maybe someone knows what
the app is expecting here?

(if you're familiar with hacking wine's source you could try hack the
file capiwxxx.c to return another value and see if that changes anything)

Hello,

On Sunday July 27 2008, qwertymn wrote to wine-users at winehq.org:

 qw> hmm, also on another site
 qw> (http://64.233.183.104/search?q=cache:hMAG0EXBscsJ:www.gsd.inesc

I already replied to this message, but I never saw my
message appear in the list. So I'll include the text
here, my apologies if you saw it before.

=== import ==
 qw> hmm, also on another site
 qw> (http://64.233.183.104/search?q=cache:hMAG0EXBscsJ:www.gsd.inesc
 qw> -id.pt/~jnos/ec-rdbl/download/capi20-2.pdf+capi_installed+return
 qw> +value&hl=nl&ct=clnk&cd=3&gl=nl)
 qw> it says that CAPI_INSTALLED() should return 0x0000 if capi20 is
 qw> installed. Maybe it's a bug in wine then.  Maybe you could try
 qw> if the patch below (a hack) makes the app happy.

Well... Not entirely happy... It's not complaining about an
uninstalled capi anymore:
jbeekhui at duinheks:~/test$ cd ~/test ; wine dtrace32.exe -s -m -d2 -d3 -c2 -c3
-nt3 -c4 -c5
-------------------------------------------------------------------------------
DTRACE32.EXE 2.08 (C) AVM Berlin                         27 Jul 2008 - 
16:28:06
CAPI Version: 0.102        Manufacturer version: 24.83
Manufacturer:    Serial Number:
Number of installed controllers: 26112
Traced Controller: c2  c3(nt)  c4  c5
-------------------------------------------------------------------------------
TEECK:   T  = Typ ('K'opf, 'H'ex, 'D'ekodierung,
'L'eerzeile)
         EE = Ebene (D1, D2, D3, B2, B3, X2 = X31)
         C  = Controller
         K  = Kanal
DTRACE.EXE does only work with AVM ISDN-controllers !!

But the remark that it only works with AVM ISDN_ontrollers is a
bit spurious. In the first place, I don't have an ISDN-controller.
The thing I'm trying to run the dtrace on is an ADSL-modem. And
it *is* made by AVM. Also the dtrace application is made by AVM.
I got it from them directly, so there are no funny things there.
Maybe I should try to force wine to use the AVM supplied
capi2032.dll, if it did not do that already. But is is getting
too warm now for that kind of hard thinking, I'll leave it for
another day :)
So far thanks for your help. It shows that the problem lies
mainly with wine and that I'm not a complete moron :)

PS: 26112 installed controlers also doesn't seem quite right.
=== tropmi ==
I've tried some more things:
Removed both capi2032.dll: complaints about "unable to
load DLL" - quite fair, I think.
Used only the AVM patched version: "CAPI 2.0 not installed".
Used only wine version: output as above.

My conclusion: something is wrong with those DLLs, probably
they are returning he wrong value. I don't speak any C, so
there's nothing I can do about that myself.

In the meantime I acquired a Live Windows CD. It was rather
a pain near the back, but I managed to make a couple of
dtrace runs. Now I hope that AVM support can do something
with them...

Regards,

           Hans.

jdh dot beekhuizen at duinheks dot nl
--- GoldED+/LNX 1.1.5/080726
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)

As i said, i don't now really anything about capi, but it looks to me like
wine's capixxxx.dll is pretty much outdated, and the bug you see after you
worked around the "libcapi2.0 is not installed" is probably yet
another wine-bug.
 If you ever feel like it and have spare time you could file a bug in wine's
bugzilla for this app. However, as isdn-stuff is  not really used that much
(anymore) by applications, i guess fixing the bugs in wine's capixxxx.dll
won't get high prioritty from the wine developers. For now i guess you have
to stick to your windows live cd, good luck anyway!

Hello,

On Thursday July 31 2008, qwertymn wrote to wine-users at winehq.org:

 qw> As i said, i don't now really anything about capi, but it looks
 qw> to me like wine's capixxxx.dll is pretty much outdated, and the
 qw> bug you see after you worked around the "libcapi2.0 is not
 qw> installed" is probably yet another wine-bug.

That's also a possibility.

 qw> If you ever feel like it and have spare time you could file a bug
 qw> in wine's bugzilla for this app. However, as isdn-stuff is  not
 qw> really used that much (anymore) by applications, i guess fixing
 qw> the bugs in wine's capixxxx.dll won't get high prioritty from
the
 qw> wine developers.

As you say, ISDN is a bit outdated. And the chance that somebody
needs to run that debugging tool under Wine is very small. I don't
think I'll bother to file a bug. That probably also means they'll
come back to me with more questions and requests to do tests. I
can find better uses of my time :)

 qw> For now i guess you have to stick to your windows live cd, good
 qw> luck anyway!

Well, my nerves are still a bit upset because I actually used
Windows :) But the live CD served its purpose, so I'll keep
it for a while.
As I only in staled Wine to be able to run this program, I'll
uninstall it now. Ans also unsubscribe from this list.
Thanks to all who helped me think about this problem. Even
though it produces no real solution.

Regards,

           Hans.

jdh dot beekhuizen at duinheks dot nl
--- GoldED+/LNX 1.1.5/080731
 * Origin: The Wizard is using MBSE/Linux (2:280/1018)