Windows CE 5.0 compilation crashes after installing rollup 2007 QFE

Hi Microsoft Engineer,

I updated my windows ce enviroment (platform builder) with the rollup
2007 package and after when I try to buid a new image I have a problem
with kerberos module, same problem that

http://groups.google.fr/group/microsoft.public.windowsce.platbuilder/browse_=
thread/thread/d3d5cbd536df3626/5462f1f52148e08c?lnk=3Dgst&q=3DDsGetDcNameW#5=
462f1f52148e08c

=2E..in the attached link (post of this forum) the user Michel Verhagen
(eMVP) told that the only way to correct this problem is reinstall the
platform buider, because in the rollup 2007 package there=B4s million
strange errors and after install rollup 2007 package the developer can
=B4t do a clean build and sysgen the windows ce enviroment, never more.

Is there another way to solve this problem ?

Regards
Mauricio de Sousa Coelho
Windows CE R&D Team
www.connec.com.br

Michel
Mon May 19 16:21:24 PDT 2008

Ok, that confused even me...

The reason why your environment is a mess is because you did a "build
and sysgen". That has nothing to do with any QFE package.

AFAIK there is no way to restore your tree after that because the "build
and sysgen" action simply overwrites a lot of binaries, and as you know
deleted files can be brought back, overwritten files can not.

A very good tip for your next installation is to *copy* the entire
C:\WINCE500 tree to C:\WINCE500NoQFE directly after installing CE 5.0
(or WINCE600 in case of CE 6.0); so before installing *any* QFE's! That
way you can always go back to the original CE tree without having to
reinstall (a simple copy or rename is enough then).

Please see http://www.guruce.com/content/whattobuildwhen for a more
detailed explanation on why you should never do a "build and sysgen"
(and also how to get rid of that command in PB).

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Mauricio Sousa (Connec Brasil) wrote:
> Hi Microsoft Engineer,
>
> I updated my windows ce enviroment (platform builder) with the rollup
> 2007 package and after when I try to buid a new image I have a problem
> with kerberos module, same problem that
>
> http://groups.google.fr/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/d3d5cbd536df3626/5462f1f52148e08c?lnk=gst&q=DsGetDcNameW#5462f1f52148e08c
>
> ...in the attached link (post of this forum) the user Michel Verhagen
> (eMVP) told that the only way to correct this problem is reinstall the
> platform buider, because in the rollup 2007 package there´s million
> strange errors and after install rollup 2007 package the developer can
> ´t do a clean build and sysgen the windows ce enviroment, never more.
>
> Is there another way to solve this problem ?
>
> Regards
> Mauricio de Sousa Coelho
> Windows CE R&D Team
> www.connec.com.br

Mauricio
Wed May 21 08:07:04 PDT 2008

Hi everybody,

God helped me.

Like I told, I had a problem exactly same the YDLU (error in kerberos
module after install the 2007 rollup QFE), after many tests, I found
the problem.

After apply the 2007 rollup QFE the build system of Kerberos module in
makefile is faulting the netapi32 library

kerberos::cryptdll winsock msasn1
@set TARGETLIBS=3D$(OWNLIB) $(SG_OUTPUT_OAKLIB)\msasn1.lib $
(SG_OUTPUT_OAKLIB)\cryptdll.lib $(SG_OUTPUT_SDKLIB)\winsock.lib

=2E..and so, NetApiBufferFree and DsGetDcNameW functions there aren=B4t to
generate the kerberos module, because netapi32 library provides these
functions.

To solve this problem change the kerberos build system im makefile,

kerberos::cryptdll winsock msasn1 NETAPI32
@set TARGETLIBS=3D$(OWNLIB) $(SG_OUTPUT_OAKLIB)\msasn1.lib $
(SG_OUTPUT_OAKLIB)\cryptdll.lib $(SG_OUTPUT_SDKLIB)\winsock.lib $
(SG_OUTPUT_SDKLIB)\NETAPI32.lib

After that, I did the a "Clean Before Build" and "Build and Sysgen"
and IT WORKS FINE.

I hope be helpfull at everybody
Mauricio de Sousa Coelho
Windows CE R&D Team
www.connec.com.br

Michel
Wed May 21 13:18:30 PDT 2008

Great that it works for you. I do expect another post from you really
soon with another strange error now that you did a build and sysgen again.

Seems like you don't want to make use of our experience and take our
free advice. Of course, we can't compete with the experience of God...

NEVER EVER DO A BUILD & SYSGEN: http://guruce.com/content/whattobuildwhen

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Mauricio Sousa (Connec Brasil) wrote:
> Hi everybody,
>
> God helped me.
>
> Like I told, I had a problem exactly same the YDLU (error in kerberos
> module after install the 2007 rollup QFE), after many tests, I found
> the problem.
>
> After apply the 2007 rollup QFE the build system of Kerberos module in
> makefile is faulting the netapi32 library
>
> kerberos::cryptdll winsock msasn1
> @set TARGETLIBS=$(OWNLIB) $(SG_OUTPUT_OAKLIB)\msasn1.lib $
> (SG_OUTPUT_OAKLIB)\cryptdll.lib $(SG_OUTPUT_SDKLIB)\winsock.lib
>
> ...and so, NetApiBufferFree and DsGetDcNameW functions there aren´t to
> generate the kerberos module, because netapi32 library provides these
> functions.
>
> To solve this problem change the kerberos build system im makefile,
>
> kerberos::cryptdll winsock msasn1 NETAPI32
> @set TARGETLIBS=$(OWNLIB) $(SG_OUTPUT_OAKLIB)\msasn1.lib $
> (SG_OUTPUT_OAKLIB)\cryptdll.lib $(SG_OUTPUT_SDKLIB)\winsock.lib $
> (SG_OUTPUT_SDKLIB)\NETAPI32.lib
>
> After that, I did the a "Clean Before Build" and "Build and Sysgen"
> and IT WORKS FINE.
>
> I hope be helpfull at everybody
> Mauricio de Sousa Coelho
> Windows CE R&D Team
> www.connec.com.br
>

Dean
Thu May 22 11:13:31 PDT 2008

Here is a much better solution...

http://blogs.msdn.com/cenet/archive/2008/05/16/kerberos-cannot-resolve-netapi32-dll-in-ce5-0-after-qfe-updates.aspx

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Mauricio Sousa (Connec Brasil)" <mauricio.scoelho1@gmail.com> wrote in
message
news:4afcf95e-9eaa-4caf-bace-3541be523603@z72g2000hsb.googlegroups.com...
Hi everybody,

God helped me.

Like I told, I had a problem exactly same the YDLU (error in kerberos
module after install the 2007 rollup QFE), after many tests, I found
the problem.

After apply the 2007 rollup QFE the build system of Kerberos module in
makefile is faulting the netapi32 library

kerberos::cryptdll winsock msasn1
@set TARGETLIBS=$(OWNLIB) $(SG_OUTPUT_OAKLIB)\msasn1.lib $
(SG_OUTPUT_OAKLIB)\cryptdll.lib $(SG_OUTPUT_SDKLIB)\winsock.lib

...and so, NetApiBufferFree and DsGetDcNameW functions there aren´t to
generate the kerberos module, because netapi32 library provides these
functions.

To solve this problem change the kerberos build system im makefile,

kerberos::cryptdll winsock msasn1 NETAPI32
@set TARGETLIBS=$(OWNLIB) $(SG_OUTPUT_OAKLIB)\msasn1.lib $
(SG_OUTPUT_OAKLIB)\cryptdll.lib $(SG_OUTPUT_SDKLIB)\winsock.lib $
(SG_OUTPUT_SDKLIB)\NETAPI32.lib

After that, I did the a "Clean Before Build" and "Build and Sysgen"
and IT WORKS FINE.

I hope be helpfull at everybody
Mauricio de Sousa Coelho
Windows CE R&D Team
www.connec.com.br

Mauricio
Tue May 27 09:03:47 PDT 2008

Perfect Dean, I read the solution posted in the link and I think much
better too.

Mauricio de Sousa Coelho
Windows CE R&D Team
www.connec.com.br