Prev: CVTRES : fatal error CVT1109: target machine "THUMB" requires "/WI
Next: DirectShow issue with Windows Mobile 5
From: knopper on 24 Jan 2006 11:41
after i copy the dll file to \windows folder and changed the registry like on
WM 5.0 pocket Emulator, i can't connect to the pocket (MDA Pro) through
ActiveSync. I delte the dll file and restore the registry, but i can still
not connect to the device. May be i had do somthing wrong. Did you have the
same problem before ?
I use power management API to disable wlan.

regard,
Knopper

"MSenne" wrote:

> My problem #3 is that when I disable the WiFi it crashes my driver.
>
> Have you loaded it onto a device with a WiFi adapter? When you do
> please let me know if you have the same problem that I do when
> disabling the WiFi (via the wireless manager or whatever software on
> your device controls that).
> -MSenne
>
>
From: MSenne on 25 Jan 2006 09:25
I have had problems where I couldn't sync with my PC, but a hard reset
always took care of that. When syncing the Passthru driver will try to
bind to the RNDISFN "adapter," which might be your problem. I added
RNDISFN to the list of adapters to skip in ProtocolBindAdapter (in the
WinCE500 PT source) and don't have USB syncing problems anymore.
Also, regarding power management, did you implement the bug fix in
ProtocolPNPHandler?
For case NetEventSetPower, replace the code there with
status = NDIS_STATUS_NOT_SUPPORTED;
This works around a known and longstanding issue with PPC power
management. This part at least is covered in several newsgroup posts
elsewhere.
-MSenne

From: knopper on 26 Jan 2006 08:37
I can once load the passthru driver example on the WM 5.0 pocket emulator
and on pocket device. But now it seems that the driver doesn't load any
more. I don't change code so much.

Maybe i can use the same SDK certificate only one time on the same device ?

regards
knopper

"MSenne" wrote:

> I have had problems where I couldn't sync with my PC, but a hard reset
> always took care of that. When syncing the Passthru driver will try to
> bind to the RNDISFN "adapter," which might be your problem. I added
> RNDISFN to the list of adapters to skip in ProtocolBindAdapter (in the
> WinCE500 PT source) and don't have USB syncing problems anymore.
> Also, regarding power management, did you implement the bug fix in
> ProtocolPNPHandler?
> For case NetEventSetPower, replace the code there with
> status = NDIS_STATUS_NOT_SUPPORTED;
> This works around a known and longstanding issue with PPC power
> management. This part at least is covered in several newsgroup posts
> elsewhere.
> -MSenne
>
>
From: MSenne on 26 Jan 2006 15:22
Hard resetting a device will remove the test certs and you'll have to
install the SDKCerts.CAB again.
Yours should run every time - the same test certs can be installed and
used on any number of devices.

From: gp on 30 Jan 2006 15:52
anybody got success with pass thru driver?

pl let me know.

"MSenne" wrote:

> Hard resetting a device will remove the test certs and you'll have to
> install the SDKCerts.CAB again.
> Yours should run every time - the same test certs can be installed and
> used on any number of devices.
>
>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6
Prev: CVTRES : fatal error CVT1109: target machine "THUMB" requires "/WI
Next: DirectShow issue with Windows Mobile 5