Porting a driver from WinCE 4.2 to 5.0 (CodePalette)

Hi everyone,

I successfully developped a driver on WinCE 4.2 (I used CodePalette to
generate the template). Now i'm willing to have it work on WinCE 5.0. I
figured I could just compile it under Platform Builder 5 and see what
appends, but ... nothing appends. My DllEntry is not even called.
Is there major changes I should apply ? Have anyone already made a
WinCE 5.0 driver using CodePalette ? I can't even have the template
working.

Thanks anyone who could help me.

Edouard Dessioux

Anthony
Wed Feb 08 07:25:49 CST 2006

Check your .reg, .bib and SOURCES files. Make sure your SOURCES file does
not have any SKIPBUILD, make sure the registry settings are correctly set
for loading your driver at boot (check the drivers\builtin key), see if your
dll is in the a bib file (that's not mandatory) and make sure the dirs file
of the upper level dircteory includes the directory that contains your
driver.
Note that the cec files have changed a lot between 4.2 and5.0.

HTH

--
--
--
----------------------------------------------------------------
Anthony Pellerin
ADENEO (ADESET)
Windows Embedded Consultant
<apellerin AT adeneo DOT adetelgroup DOT com>
http://www.adeneo.adetelgroup.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------
"Edouard Dessioux" <edessioux@no-spam-everbee.com> a écrit dans le message
de news: dscbas$304n$1@biggoron.nerim.net...
> Hi everyone,
>
> I successfully developped a driver on WinCE 4.2 (I used CodePalette to
> generate the template). Now i'm willing to have it work on WinCE 5.0. I
> figured I could just compile it under Platform Builder 5 and see what
> appends, but ... nothing appends. My DllEntry is not even called.
> Is there major changes I should apply ? Have anyone already made a
> WinCE 5.0 driver using CodePalette ? I can't even have the template
> working.
>
> Thanks anyone who could help me.
>
> Edouard Dessioux

Edouard
Wed Feb 08 07:59:29 CST 2006

Anthony Pellerin a écrit :
> Check your .reg, .bib and SOURCES files. Make sure your SOURCES file does
> not have any SKIPBUILD, make sure the registry settings are correctly set
> for loading your driver at boot (check the drivers\builtin key), see if your
> dll is in the a bib file (that's not mandatory) and make sure the dirs file
> of the upper level dircteory includes the directory that contains your
> driver.
> Note that the cec files have changed a lot between 4.2 and5.0.
>
> HTH
>

I check my SOURCES file, it does not contain any SKIPBUILD in it.
I also check the registry and I have the following :
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\CipherManager]
"Prefix"="CMG"
"Dll"="myDriver.dll"
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"
Index=1
Order=5
The bib file contains the line :
CipherManager.dll $(_FLATRELEASEDIR)\myDriver.dll NK SH
I cannot find any dirs files at the upper level directory, maybe it is
part of the problem.

But I see something weird in the log of my emulator :
4294773566 PID:23f97af2 TID:23fa089a 0x83fca800: DEVICE!CreateDevice:
illegal entry point combination in driver DLL 'myDriver.dll'

And then, everything goes wrong. I modify my sources file to include
DLLEntry=DllEntry (I should have it copied from CodePalette), and now
my driver is loaded.

Anyway, thanks for your help,

Edouard Dessioux.