WinCE 5.0 NDIS driver loading + signing

I've built an NDIS miniport driver for CE 5.0. It loads and runs on the
Platform Builder 5.0 x86 emulator. However I cannot get it to load on
the SDK ARM emulator. Neither will it load on a JasJar device. In fact
DriverEntry is never even called.

I've heard that drivers need to be signed before they can be loaded on
CE5. So for the ARM emulator I signed my driver with the priviledged
certs in the SDK. This made no difference.
I've also heard that if a driver is loaded dynamically after the boot
process then this gets around the problem of signed drivers, but this
hasn't worked for me either.

Can anyone shed any light on how to simply build drivers for ARM
platforms in order to test they run?

thanks,

Tim

Ajay
Mon Nov 21 23:46:32 CST 2005

I also faced the same problem. When I contacted MSFT Tech support, they said
dvelopment of NDIS driver is not supported by using WM50 SDK.If you want to
develop NDIS driver for a WM50 device then you would need to partner with
OEM.

Thanks,
-Ajay
------------------------------------------

"Tim" <timhoal@yahoo.co.uk> wrote in message
news:1132590935.044784.190550@g43g2000cwa.googlegroups.com...
> I've built an NDIS miniport driver for CE 5.0. It loads and runs on the
> Platform Builder 5.0 x86 emulator. However I cannot get it to load on
> the SDK ARM emulator. Neither will it load on a JasJar device. In fact
> DriverEntry is never even called.
>
> I've heard that drivers need to be signed before they can be loaded on
> CE5. So for the ARM emulator I signed my driver with the priviledged
> certs in the SDK. This made no difference.
> I've also heard that if a driver is loaded dynamically after the boot
> process then this gets around the problem of signed drivers, but this
> hasn't worked for me either.
>
> Can anyone shed any light on how to simply build drivers for ARM
> platforms in order to test they run?
>
> thanks,
>
> Tim
>

pavel_a
Tue Nov 22 21:42:02 CST 2005

"Tim" wrote:
> I've built an NDIS miniport driver for CE 5.0. It loads and runs on the
> Platform Builder 5.0 x86 emulator. However I cannot get it to load on
> the SDK ARM emulator. Neither will it load on a JasJar device. In fact
> DriverEntry is never even called.

Please let me get this straight.... are you trying to
run the x86 binary on ARM??

--PA


> I've heard that drivers need to be signed before they can be loaded on
> CE5. So for the ARM emulator I signed my driver with the priviledged
> certs in the SDK. This made no difference.
> I've also heard that if a driver is loaded dynamically after the boot
> process then this gets around the problem of signed drivers, but this
> hasn't worked for me either.
>
> Can anyone shed any light on how to simply build drivers for ARM
> platforms in order to test they run?
>
> thanks,
>
> Tim
>
>

Tim
Wed Nov 23 12:25:23 CST 2005

Pavel - The code was recompiled for the appropriate targets in both
cases.

Are other developers out there building NDIS drivers for CE5 that load
without problems on target devices?
Is it only possible to load drivers on a CE 5 device if each OEM is
targeted? How will this then affect distribution? Surely this means
developers can no longer build drivers for WM5 in general and will need
to supply binaries for iPaq or JasJar etc.

Ajay
Wed Nov 23 23:33:41 CST 2005

Please read posts with subject "Who Supports the OS for Mobile 5.0?" for
more information about this topic in the same newsgroup.

Thanks,
-Ajay


"Tim" <timhoal@yahoo.co.uk> wrote in message
news:1132770323.524089.304410@g43g2000cwa.googlegroups.com...
> Pavel - The code was recompiled for the appropriate targets in both
> cases.
>
> Are other developers out there building NDIS drivers for CE5 that load
> without problems on target devices?
> Is it only possible to load drivers on a CE 5 device if each OEM is
> targeted? How will this then affect distribution? Surely this means
> developers can no longer build drivers for WM5 in general and will need
> to supply binaries for iPaq or JasJar etc.
>