Status of TAPI

[Andreas Rosenberg]

Hi guys!

I'd like to run a TAPI based application in Wine (updated from CVS today).

I extracted the vendor specific TAPI driver and the registry keys
and included both into a Wine setup. 
Then I tried to do setup the TAPI driver using the 
telephon.cpl (taken from Win98):

wine rundll32.exe shell32.dll,Control_RunDLL telephon.cpl

first I had a problem with the Wine implementation of the TAPI32.DLL.

err:module:import_dll No implementation for TAPI32.dll.internalConfig imported from L"C:\windows\system\telephon.cpl", setting to 0xdeadbeef
...
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\TELEPHON.CPL' (0x75a70000)
Unhandled exception: page fault on read access to 0xdeadbeef in 32-bit code (0x404c5b7e).

who had dug in that DEAD BEEF? ;-)

Then I took the TAPI32.DLL from a Win98 installation. 
This gave me another error:

fixme:ole:RpcServerRegisterAuthInfoA ((null),10,(nil),(nil)): stub
fixme:seh:EXC_RtlRaiseException call to unimplemented function rpcrt4.dll.NdrClientCall
(last message repeated several times).

At last I took the rpcrt4.dll from a Windows98 installation and tried it again.

Then it took quite a time (~15 sec) until the Wine debugger came up.

wine rundll32.exe shell32.dll,Control_RunDLL telephon.cpl
wine: Unhandled exception (thread 0009), starting debugger...
WineDbg starting on pid 8
Can't find file for ELF 'wine-kthread' ((nil))
Loaded debug information from ELF 'wine-pthread' ((nil))
Breakpoint 1 at 0x4000dd60 (_end+0x3fefb8d0)
Loaded debug information from ELF '/usr/local/lib/libwine.so.1' (0x40028000)
No debug information in ELF '/lib/i686/libpthread.so.0' (0x40040000)
No debug information in ELF '/lib/i686/libc.so.6' (0x40091000)
No debug information in ELF '/lib/libdl.so.2' (0x401c4000)
No debug information in ELF '/lib/ld-linux.so.2' (0x40000000)
Loaded debug information from ELF '/usr/local/lib/wine/ntdll.dll.so' (0x401c8000)
Loaded debug information from ELF '/usr/local/lib/libwine_unicode.so.1' (0x40238000)
No debug information in ELF '/lib/i686/libm.so.6' (0x4032b000)
Loaded debug information from ELF '/usr/local/lib/wine/kernel32.dll.so' (0x40460000)
Loaded debug information from ELF '/usr/local/lib/wine/rundll32.exe.so' (0x405a2000)
Loaded debug information from ELF '/usr/local/lib/wine/user32.dll.so' (0x406c0000)
Loaded debug information from ELF '/usr/local/lib/wine/gdi32.dll.so' (0x407f8000)
Loaded debug information from ELF '/usr/local/lib/wine/advapi32.dll.so' (0x40878000)
No debug information in ELF '/usr/lib/libfreetype.so.6' (0x408b7000)
No debug information in ELF '/usr/lib/libfontconfig.so.1' (0x4090d000)
No debug information in ELF '/usr/lib/libexpat.so.0' (0x40935000)
Loaded debug information from ELF '/usr/local/lib/wine/x11drv.dll.so' (0x40955000)
No debug information in ELF '/usr/X11R6/lib/libSM.so.6' (0x4001c000)
No debug information in ELF '/usr/X11R6/lib/libICE.so.6' (0x409d3000)
No debug information in ELF '/usr/X11R6/lib/libXrandr.so.2' (0x405b6000)
No debug information in ELF '/usr/X11R6/lib/libXrender.so.1' (0x409ea000)
No debug information in ELF '/usr/X11R6/lib/libXext.so.6' (0x409f2000)
No debug information in ELF '/usr/X11R6/lib/libX11.so.6' (0x40a00000)
No debug information in ELF '/usr/lib/tls/libGL.so' (0x40afc000)
No debug information in ELF '/usr/lib/tls/libGLcore.so.1' (0x40b67000)
No debug information in ELF '/usr/X11R6/lib/libXcursor.so.1' (0x410e4000)
Unsupported debug information in ELF '/usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2' (0x40025000)
Unsupported debug information in ELF '/usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2' (0x41131000)
No debug information in ELF '/usr/lib/gconv/ISO8859-1.so' (0x408a9000)
Loaded debug information from ELF '/usr/local/lib/wine/imm32.dll.so' (0x41150000)
Loaded debug information from ELF '/usr/local/lib/wine/shell32.dll.so' (0x4116e000)
Loaded debug information from ELF '/usr/local/lib/wine/ole32.dll.so' (0x411f6000)
Loaded debug information from ELF '/usr/local/lib/wine/shlwapi.dll.so' (0x4126a000)
Loaded debug information from ELF '/usr/local/lib/wine/comctl32.dll.so' (0x412c1000)
No debug information in 32bit DLL 'C:\windows\system\rundll32.exe' (0x405b0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x401e0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' (0x40490000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' (0x40890000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x40810000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x406e0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40970000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\IMM32.DLL' (0x41160000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x7fb90000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x41210000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x41280000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x412d0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' (0x41190000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVCRT.DLL' (0x78000000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\TAPI32.DLL' (0x7f960000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\TELEPHON.CPL' (0x75a70000)
Unhandled exception: page fault on read access to 0xda62061d in 32-bit code (0x401f999a).
In 32-bit mode.
0x401f999a (RtlpWaitForCriticalSection+0x6a [critsection.c:204] in NTDLL.DLL): movl     0x1c(%eax),%eax
204             if ((!crit->DebugInfo) || (!crit->DebugInfo->Spare[1])) continue;

The wait time could be an indication that a timeout happened. 
Anybody has a clue what could be the problem?

Regards 
  Andy

[Mike McCormack]

Andreas Rosenberg wrote:
> Hi guys!
>
> I'd like to run a TAPI based application in Wine (updated from CVS today).

What does your TAPI based application do?  Does it need (or provide?) 
access to some kind of hardware?  If it's not a standard piece of 
hardware, you may need to find a Linux device driver that supports it...

The main reasons TAPI isn't implemented are:

1) that modems are kind of old technology, so the incentive to implement 
it is rapidly disappearing
2) most of the interface that TAPI provides (dialing modems, and 
starting ppp) needs to be implemented natively anyway.

Mike

[Henk Poley]

Mike McCormack wrote:
> Andreas Rosenberg wrote:
> > Hi guys!
> >
> > I'd like to run a TAPI based application in Wine (updated from CVS
> > today).
>
> What does your TAPI based application do?  Does it need (or provide?)
> access to some kind of hardware?  If it's not a standard piece of
> hardware, you may need to find a Linux device driver that supports it...
>
> The main reasons TAPI isn't implemented are:
> - that modems are kind of old technology, so the incentive to implement
>
> it is rapidly disappearing
> 2) most of the interface that TAPI provides (dialing modems, and
> starting ppp) needs to be implemented natively anyway.

This (dutch..) site provides some TAPI patches for Wine that are not in CVS:
http://home.wanadoo.nl/wijn/girotel/

I don't know how helpfull they are. Andreas, you could contact the author.
He is still maintaining the patches, but due to lack of input no longer
keeps his site up to date.

Henk Poley <><

[Rein Klazes]

On Wed, 07 Apr 2004 21:48:58 +0200, you wrote:
> > - that modems are kind of old technology, so the incentive to implement
> >
> > it is rapidly disappearing
> > 2) most of the interface that TAPI provides (dialing modems, and
> > starting ppp) needs to be implemented natively anyway.
>
> This (dutch..) site provides some TAPI patches for Wine that are not in CVS:
> http://home.wanadoo.nl/wijn/girotel/
>
> I don't know how helpfull they are. Andreas, you could contact the author.
> He is still maintaining the patches, but due to lack of input no longer
> keeps his site up to date.

Well I am the author of those patches and I'm afraid there is no chance
that they will help Andreas case. It is an extreme hackish
implementation of a data modem tailored to a single application. No
notion of drivers, certainly no support for external drivers and control
panel interface.

Rein.

[Henk Poley]

Rein Klazes wrote:
> On Wed, 07 Apr 2004 21:48:58 +0200, you wrote:
> > > - that modems are kind of old technology, so the incentive to
> > >
> > > implement it is rapidly disappearing
> > > 2) most of the interface that TAPI provides (dialing modems, and
> > > starting ppp) needs to be implemented natively anyway.
> >
> > This (dutch..) site provides some TAPI patches for Wine that are not in
> > CVS: http://home.wanadoo.nl/wijn/girotel/
> >
> > I don't know how helpfull they are. Andreas, you could contact the
> > author. He is still maintaining the patches, but due to lack of input no
> > longer keeps his site up to date.
>
> Well I am the author of those patches and I'm afraid there is no chance
> that they will help Andreas case. It is an extreme hackish
> implementation of a data modem tailored to a single application. No
> notion of drivers, certainly no support for external drivers and control
> panel interface.

Anyways, Mike McCormack just submitted some patch based on your TAPI
patches. Not that it's any thing structural, just 20 or so defines.

Henk Poley <><

[Andreas Rosenberg]

> Well I am the author of those patches and I'm afraid there is no chance
> that they will help Andreas case. It is an extreme hackish
> implementation of a data modem tailored to a single application. No
> notion of drivers, certainly no support for external drivers and control
> panel interface.

Thanks for your info. I talked with Mike McCormak and provided some
more details of our problem and he estimated that with a couple of
native dlls it could work - but the serial interface code could be
a problem.

Has anybody more information about this?

If I got a little more time, I will create an registry access log regarding
TAPI and try to move missing TAPI entries.  Perhaps this will help
to open the telephony control panel...

Andy