Service Pack 2

[Debbie Giuliano]

Hello,

I have updated my database to service pack to for XPe. I do see in target
designer a component for Windows XP Service pack 2 OOB and Resource dll.
However, my completed image when I right-click on my computer and properties
still tells me service pack 1. Am I missing an important component and/or
should I see in my computer and properties on the general tab xp with sp2?

Thanks,

Debbie Giuliano

 

[Matt Kellner \(MS\)]

Hi Debbie. Are you building a new configuration? Or is this an existing
SP1 configuration that you wish to upgrade to SP2?

--
Matt Kellner ([email protected])
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers no rights.
===============================

 

[Debbie Giuliano]

Hello Matt,

I am building from an existing configuration. Is that the problem? Is
there something special that I need to do?

Thanks,

Debbie Giuliano

 

[KM]

Debbie,

Have you tried upgrading the configuration? (menu Configuration --> Upgrade Configuration)

--
Regards,
KM, BSquare Corp.

PS. Each configuration has an extended properly cmiServicePackLevel that your can change manually to match the required SP.
However, the configuration system components may need to be upgraded as well.

 

[Debbie Giuliano]

Dear KM,

I have my SLX file already set to upgrade configuration automatically. Is
there something else I need to do? I have many images and cannot afford to
rebuild from scratch that would be a total waste of time.

Any ideas?

Thanks,

Deb

 

[KM]

Debbie,

I re-read the thread from the beginning and now I see your problem.
First, verify that you are building the image with SP2 binaries. Just got to your image build directory and compare the date/time
stamp (or the size) of some system binaries (like winlogon.exe, etc.) to the ones from XPE Repository. E.g., for the winlogon.exe it
should be the same as for the "\Windows Embedded Data\Repositories\{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}\winlogon.exe" file.

Then, please check the following reg.key at run time [HKLM\SYSTEM\CurrentControlSet\Control\Windows],"CSDVersion". It is likely set
to "100" (hex) on your build so you see the "Service Pack 1" reported. It should be set to "200" (hex) to report "Service Pack 2".
To fix the issue within your configuration in TD, please add "Client / Server Runtime (Console)" component (or if it is already
there, upgrade it - it must be the latest revision from SP2).

 

[Debbie Giuliano]

Dear KM,

I checked what you suggested and the binaries match, I check winlog on and a
few and as a matter of fact when I view the component in target designer it
even says SP2 on the binaries that in the repository
{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}. In any case I did change in the
component Client/Server Runtime to hex 200 and after compiling and running
through FBA it still says SP1 not SP2. Any ideas? I have the slx file
automatically ugrading when opening that is a selection in the slx file
itself.

Thanks,

Debbie

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net

Debbie,

I re-read the thread from the beginning and now I see your problem.
First, verify that you are building the image with SP2 binaries. Just got
to your image build directory and compare the date/time
stamp (or the size) of some system binaries (like winlogon.exe, etc.) to
the ones from XPE Repository. E.g., for the winlogon.exe it
should be the same as for the "\Windows Embedded
Data\Repositories\{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}\winlogon.exe"
file.

Then, please check the following reg.key at run time
[HKLM\SYSTEM\CurrentControlSet\Control\Windows],"CSDVersion". It is likely
set
to "100" (hex) on your build so you see the "Service Pack 1" reported. It
should be set to "200" (hex) to report "Service Pack 2".
To fix the issue within your configuration in TD, please add "Client /
Server Runtime (Console)" component (or if it is already
there, upgrade it - it must be the latest revision from SP2).

--
Regards,
KM, BSquare Corp.

Dear KM,

I have my SLX file already set to upgrade configuration automatically.
Is
there something else I need to do? I have many images and cannot afford
to
rebuild from scratch that would be a total waste of time.

Any ideas?

Thanks,

Deb

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net

 

[KM]

Debbie,

Dear KM,

I checked what you suggested and the binaries match, I check winlog on and a
few and as a matter of fact when I view the component in target designer it
even says SP2 on the binaries that in the repository
{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}. In any case I did change in the
component Client/Server Runtime to hex 200 and after compiling and running
through FBA it still says SP1 not SP2.

What is the value of the key [HKLM\SYSTEM\CurrentControlSet\Control\Windows],"CSDVersion" at run time after you changed it in the
Client/Server Runtime component?
If it is still 100, it seems to me you've got the CSDVersion 100 value coming from some (custom!) component in your configuration or
the Configuration Extra Registy section. Can this be the case?

KM

Any ideas? I have the slx file
automatically ugrading when opening that is a selection in the slx file
itself.

Thanks,

Debbie

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net

Debbie,

I re-read the thread from the beginning and now I see your problem.
First, verify that you are building the image with SP2 binaries. Just got
to your image build directory and compare the date/time
stamp (or the size) of some system binaries (like winlogon.exe, etc.) to
the ones from XPE Repository. E.g., for the winlogon.exe it
should be the same as for the "\Windows Embedded
Data\Repositories\{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}\winlogon.exe"
file.

Then, please check the following reg.key at run time
[HKLM\SYSTEM\CurrentControlSet\Control\Windows],"CSDVersion". It is likely
set
to "100" (hex) on your build so you see the "Service Pack 1" reported. It
should be set to "200" (hex) to report "Service Pack 2".
To fix the issue within your configuration in TD, please add "Client /
Server Runtime (Console)" component (or if it is already
there, upgrade it - it must be the latest revision from SP2).

--
Regards,
KM, BSquare Corp.

Dear KM,

I have my SLX file already set to upgrade configuration automatically.
Is
there something else I need to do? I have many images and cannot afford
to
rebuild from scratch that would be a total waste of time.

Any ideas?

Thanks,

Deb

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net


Debbie,

Have you tried upgrading the configuration? (menu Configuration -->
Upgrade Configuration)

--
Regards,
KM, BSquare Corp.

PS. Each configuration has an extended properly cmiServicePackLevel
that
your can change manually to match the required SP.
However, the configuration system components may need to be upgraded as
well.


Hello Matt,

I am building from an existing configuration. Is that the problem?
Is
there something special that I need to do?

Thanks,

Debbie Giuliano

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net


Hi Debbie. Are you building a new configuration? Or is this an
existing
SP1 configuration that you wish to upgrade to SP2?

--
Matt Kellner ([email protected])
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers no
rights.
===============================

Hello,

I have updated my database to service pack to for XPe. I do see in
target designer a component for Windows XP Service pack 2 OOB and
Resource dll. However, my completed image when I right-click on my
computer and properties still tells me service pack 1. Am I
missing
an
important component and/or should I see in my computer and
properties
on
the general tab xp with sp2?

Thanks,

Debbie Giuliano

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net

 

[Debbie Giuliano]

Dear KM,

I will check.

Thanks,

Debbie Giuliano

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net

Debbie,

Dear KM,

I checked what you suggested and the binaries match, I check winlog on
and a
few and as a matter of fact when I view the component in target designer
it
even says SP2 on the binaries that in the repository
{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}. In any case I did change in the
component Client/Server Runtime to hex 200 and after compiling and
running
through FBA it still says SP1 not SP2.

What is the value of the key
[HKLM\SYSTEM\CurrentControlSet\Control\Windows],"CSDVersion" at run time
after you changed it in the
Client/Server Runtime component?
If it is still 100, it seems to me you've got the CSDVersion 100 value
coming from some (custom!) component in your configuration or
the Configuration Extra Registy section. Can this be the case?

KM

Any ideas? I have the slx file
automatically ugrading when opening that is a selection in the slx file
itself.

Thanks,

Debbie

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net

Debbie,

I re-read the thread from the beginning and now I see your problem.
First, verify that you are building the image with SP2 binaries. Just
got
to your image build directory and compare the date/time
stamp (or the size) of some system binaries (like winlogon.exe, etc.)
to
the ones from XPE Repository. E.g., for the winlogon.exe it
should be the same as for the "\Windows Embedded
Data\Repositories\{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}\winlogon.exe"
file.

Then, please check the following reg.key at run time
[HKLM\SYSTEM\CurrentControlSet\Control\Windows],"CSDVersion". It is
likely
set
to "100" (hex) on your build so you see the "Service Pack 1" reported.
It
should be set to "200" (hex) to report "Service Pack 2".
To fix the issue within your configuration in TD, please add "Client /
Server Runtime (Console)" component (or if it is already
there, upgrade it - it must be the latest revision from SP2).

--
Regards,
KM, BSquare Corp.


Dear KM,

I have my SLX file already set to upgrade configuration automatically.
Is
there something else I need to do? I have many images and cannot
afford
to
rebuild from scratch that would be a total waste of time.

Any ideas?

Thanks,

Deb

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net


Debbie,

Have you tried upgrading the configuration? (menu Configuration -->
Upgrade Configuration)

--
Regards,
KM, BSquare Corp.

PS. Each configuration has an extended properly cmiServicePackLevel
that
your can change manually to match the required SP.
However, the configuration system components may need to be upgraded
as
well.


Hello Matt,

I am building from an existing configuration. Is that the problem?
Is
there something special that I need to do?

Thanks,

Debbie Giuliano

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net


Hi Debbie. Are you building a new configuration? Or is this an
existing
SP1 configuration that you wish to upgrade to SP2?

--
Matt Kellner ([email protected])
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers
no
rights.
===============================

Hello,

I have updated my database to service pack to for XPe. I do see
in
target designer a component for Windows XP Service pack 2 OOB
and
Resource dll. However, my completed image when I right-click on
my
computer and properties still tells me service pack 1. Am I
missing
an
important component and/or should I see in my computer and
properties
on
the general tab xp with sp2?

Thanks,

Debbie Giuliano

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net

 

[Debbie Giuliano]

Dear KM,

Great Call. I am loading extra registry data to have the quick launch show
after FBA automatically and one does have the CSD version. I was
overwriting it. Duh! Anyway, I am build a new image now and let you know
the outcome.

Thanks for all your help,

Debbie Giuliano

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net

Dear KM,

I will check.

Thanks,

Debbie Giuliano

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net

Debbie,

Dear KM,

I checked what you suggested and the binaries match, I check winlog on
and a
few and as a matter of fact when I view the component in target designer
it
even says SP2 on the binaries that in the repository
{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}. In any case I did change in the
component Client/Server Runtime to hex 200 and after compiling and
running
through FBA it still says SP1 not SP2.

What is the value of the key
[HKLM\SYSTEM\CurrentControlSet\Control\Windows],"CSDVersion" at run time
after you changed it in the
Client/Server Runtime component?
If it is still 100, it seems to me you've got the CSDVersion 100 value
coming from some (custom!) component in your configuration or
the Configuration Extra Registy section. Can this be the case?

KM

Any ideas? I have the slx file
automatically ugrading when opening that is a selection in the slx file
itself.

Thanks,

Debbie

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net


Debbie,

I re-read the thread from the beginning and now I see your problem.
First, verify that you are building the image with SP2 binaries. Just
got
to your image build directory and compare the date/time
stamp (or the size) of some system binaries (like winlogon.exe, etc.)
to
the ones from XPE Repository. E.g., for the winlogon.exe it
should be the same as for the "\Windows Embedded
Data\Repositories\{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}\winlogon.exe"
file.

Then, please check the following reg.key at run time
[HKLM\SYSTEM\CurrentControlSet\Control\Windows],"CSDVersion". It is
likely
set
to "100" (hex) on your build so you see the "Service Pack 1" reported.
It
should be set to "200" (hex) to report "Service Pack 2".
To fix the issue within your configuration in TD, please add "Client /
Server Runtime (Console)" component (or if it is already
there, upgrade it - it must be the latest revision from SP2).

--
Regards,
KM, BSquare Corp.


Dear KM,

I have my SLX file already set to upgrade configuration
automatically.
Is
there something else I need to do? I have many images and cannot
afford
to
rebuild from scratch that would be a total waste of time.

Any ideas?

Thanks,

Deb

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net


Debbie,

Have you tried upgrading the configuration? (menu Configuration -->
Upgrade Configuration)

--
Regards,
KM, BSquare Corp.

PS. Each configuration has an extended properly cmiServicePackLevel
that
your can change manually to match the required SP.
However, the configuration system components may need to be
upgraded as
well.


Hello Matt,

I am building from an existing configuration. Is that the
problem?
Is
there something special that I need to do?

Thanks,

Debbie Giuliano

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."

http://www.ihatespam.net


Hi Debbie. Are you building a new configuration? Or is this an
existing
SP1 configuration that you wish to upgrade to SP2?

--
Matt Kellner ([email protected])
STE, Windows Embedded Group

This posting is provided "AS IS" with no warranties, and confers
no
rights.
===============================

Hello,

I have updated my database to service pack to for XPe. I do
see in
target designer a component for Windows XP Service pack 2 OOB
and
Resource dll. However, my completed image when I right-click on
my
computer and properties still tells me service pack 1. Am I
missing
an
important component and/or should I see in my computer and
properties
on
the general tab xp with sp2?

Thanks,

Debbie Giuliano

--


---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam
buster."

http://www.ihatespam.net