Re: [TSP] Creating WinCE TSP service

Tech-Archive recommends: Fix windows errors by optimizing your registry

Jonathan,

maybe you should download the WinCE 4.x SDK? The sample
is part of the CE 4.2 documentation, so I think it should at least
be consistent with the 4.2 SDK.

If all fails you might better start a support incident with MS on
this issue.

Best regards,

Matthias Moetje
-------------------------------------
TERASENS GmbH
Augustenstraße 24
80333 Munich, GERMANY
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot com
www: www.terasens.com
-------------------------------------

"Jonathan Lowden" <jonathanl@xxxxxxxxxxx> wrote in message
news:OulhR7aaGHA.1200@xxxxxxxxxxxxxxxxxxxxxxx
Just a little bit of an update.

The "tapicomn.h" file doesn't exist still on my PC but it seems that the
MSDN text compared to the header files differ. The TSPI_lineGetProcTable
is
not declared as:

LONG TSPIAPI TSPI_lineGetProcTable(LPTSPI_PROCS *lplpTSPIProcs)

It is declared as:

LONG TSPIAPI TSPI_lineGetProcTable(void *lplpTSPIProcs)

I wish there was some consistency in the MSDN library.

It seems also that the TSPI_PROCS structure is just pointers to function
names, so I should be able to implement it by copying the different
function
details and creating a struct for each. I'll post how I get on here.

Regards,
Jonathan

"Jonathan Lowden" <jonathanl@xxxxxxxxxxx> wrote in message
news:OEJzdfZaGHA.508@xxxxxxxxxxxxxxxxxxxxxxx
Hello Matthias,

Thanks for your response.

Yes I had seen that and I thought that was the case. The problem I have
run into is that with WinCE 5.0 SDK the header file (tapicomn.h) used to
define the TSPI_PROCS structure is missing. I have searched for the
header file through my entire computer and have come up with nothing.
Doing searches on google only makes reference to the header file in one
location, the MSDN website, which doesn't even contain the header file.
I
might be able to get around it if I knew the actual structure of the
TSPI_PROCS and typedef it myself but that still doesn't help the fact
that
the header file is missing. It makes it very difficult to build a TSP on
CE when some of the required header files are missing. Couldn't they
have
just included the structure in the standard TAPI.h??? Apparently not.

Could you do a search on your PC for the header file too? I just want
to
make sure I haven't missed something in my install.

I tried to use the code sample that is supplied in the MSDN library (the
one you talk about below) but it also is missing other header files.
The
entire sample is incomplete. I found one of the header files via a
google
search but the others were nowhere to be found. I sent a message to the
MSDN board and the only response I got was "Dear Jonathan, Thank you for
your feedback. The relevant content owner has been notified and will
follow up as needed. Best regards, - Microsoft Mobile and Embedded
Devices
User Assistance Team" and that was three weeks ago with no response from
the "relevant content owner".

Anyway thanks again for your response.

Regards,
Jonathan Lowden

"Matthias Moetje [MVP]" <moetje@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uCrq36YaGHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
Jonathan,

I've read you post but I have no idea about the differences on
Windows CE. Did you read everything on MSDN about it?

I just found the following from a transcript:

Q: Can you talk about TAPI and TSP porting - will TSPs need to be
recompiled
to work on CE?
A: (from David Kanz (offline)): TAPI TSPs on CE are different enough
from
the desktop TAPI TSPs that there is some code work involved to port a
TSP
from the desktop to CE. The biggest differences are the order of
messages
and functions calls, and CE's TAPI uses a function pointer array
instead
of
exported dll functions. On CE, a TAPI TSP dll only needs to export 1
function, TSPI_lineGetProcTable.

The article at the following address explains that further:


http://msdn.microsoft.com/library/en-us/wcetapi/html/cmconTelephonyServiceProviderInterface.asp

Just below there is a TSP sample for Windows CE, did you see that?

Best regards,

Matthias Moetje
-------------------------------------
TERASENS GmbH
Augustenstraße 24
80333 Munich, GERMANY
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot com
www: www.terasens.com
-------------------------------------

"Jonathan Lowden" <jonathanl@xxxxxxxxxxx> wrote in message
news:u1EGBFYaGHA.1348@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I was just wondering if anyone has had a chance to read my post?

Regards,
Jonathan Lowden

"Jonathan Lowden" <jonathanl@xxxxxxxxxxx> wrote in message
news:u2bMOdEaGHA.4116@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

I've been playing around with code for the better part of 3 weeks
now
trying to create a TSP DLL for the Windows CE 5 environment. My
code
all
built fine and so I excepted that it was just a matter of copying
across
the DLL and running the lineAddProvider function from within an EXE.
It
was returning invalid numbers (not 0) and so I thought I missed
something.
I then looked up the code samples available on the Microsoft MSDN
website
and it makes reference to "tapicomn.h" and to
"TSPI_lineGetProcTable".
Looking around the internet it is referenced in only one place the
MSDN
website. Does anyone know about this? Do I have to use it or can I
export
my functions like I normally would?

Thanks in advance.

Regards,
Jonathan Lowden











.

Relevant Pages

  • Re: [TSP] Creating WinCE TSP service
    ... I wish there was some consistency in the MSDN library. ... header file through my entire computer and have come up with nothing. ... A: ): TAPI TSPs on CE are different enough from ... a TAPI TSP dll only needs to export 1 ...
    (microsoft.public.win32.programmer.tapi)
  • Re: [TSP] Creating WinCE TSP service
    ... I have searched for the header file ... I tried to use the code sample that is supplied in the MSDN library (the one ... A: ): TAPI TSPs on CE are different enough from ... a TAPI TSP dll only needs to export 1 ...
    (microsoft.public.win32.programmer.tapi)
  • Re: PPC im Cradle ( ja / nein)
    ... In der MSDN steht das u.a. diese beiden typen nicht unterstützt werden! ... The following constants are defined in the header file, ... Nur bekomme ich immer ein false zurück! ...
    (microsoft.public.de.german.windowsce.entwickler)
  • Re: Does anybody have a listing of the MS constants such as WM_KEYDOWN and WM_SYSKEYDOWN
    ... They are referred to all over MSDN but I can't locate the actual listing of the constants and their values. ... The name of the header file containing the define is listed in the documentation. ... ApiViewer ...
    (microsoft.public.dotnet.languages.vb)
  • Re: EVC3, EVC4 or VStudio 2005?
    ... VS2005 C++ compiler complains about these lines, ... Looking at the WM5 SDK, in the same header file "vector", this file is ... Therefore, I copied the WM5 version into the PocketPC2003 SDK, and voila, ...
    (microsoft.public.pocketpc.developer)