Licensing problem with WinXPe Runtime Image

[Dion Kriel]

We are experiencing licensing related expiry issues with
the runtime image we built with the licensed XPE toolkit.

Any help is much appreciated.
Dion

Using the licensed Toolkit I built a runtime image that I
considered to be licensed. However, some indicators exist
that this new run-time image is NOT licensed.
So here's my story...

Indicators that my new image is NOT licensed:

[1] WinXPe post-FBA : My Computer-> Help-> About Windows
The About Windows dialog shows...
Version 5.1 (Build 2600.xpsp2.030422-1633)License Agreement to: OEM OEM<<
Clicking on the >>End-User License Agreement<< link opens
EULA.TXT in Notepad.
EULA.TXT states that: >>This is a time-sensitive Windows
XP Embedded Runtime.<<

[2] The release notes file (RELEASE NOTES.HTM) on CD-1 of
the Windows Embedded Studio toolkit states:
QUOTE
Evaluation Period
For this release of Windows XP Embedded, run-time images
have a 90-day to 180-day expiration period, depending on
the type of image created. This evaluation period starts
when the embedded device is first booted. Under certain
conditions, at the end of 90 days, Windows XP Embedded
will notify you that Windows must be activated. The run-
time activation framework is not included with Windows XP
Embedded; therefore, activation is not possible. Once the
activation grace period has expired, you will be notified
that the evaluation period has expired and Windows XP
Embedded will exit with a license violation stop code, for
example, the run-time image will display a blue screen.
ENDQUOTE

Indicators that my new image is indeed licensed:

[1] Target Designer -> Run-time Image Licensing entry
When selecting the image.slx SETTINGS, a field called Run-
time Image Licensing becomes available.
In this field I entered a 25 digit PID obtained from one
of the 10 licenses we received from supplier.
//Note: the evalkit did not have a field to enter Run-time
Image Licensing

[2] Target Designer -> Build Image results
After building the runtime image, the results
indicated "no errors or warnings".
//Note: the evalkit generated a warning that >>This is an
evaluation run-time image that is only valid for 90 to 180
days after it is first used.<<.

[3] WinXPe post-FBA -> Desktop Appearance
The bottom right corner of the Desktop displays no Windows
XP Embedded text.
//Note: The evalkit image has shown >>Windows XP Embedded.
Evaluation Copy. Build 2600.xpsp1.020828-1920<<

 

[Edson dela Torre]

Hi Dion,

You have to purchase valid runtime PID's so that your build will not expire.

 

[Guest]

No, thats not my problem.

As I stated in my posting, we entered valid 25-digit PIDs
in Target Designer, using a full version of XPE Embedded
Studio. All indicators (as mentioned in my posting) are
that the runtime is licensed. Except for the EULA.TXT
message.

My question remains: Under conditions described, why does
EULA.TXT indicate a time-sensitive runtime?

Am I supposed to replace the default EULA.TXT with a
custom one? Or is the default EULA.TXT a Microsoft oops?

Dion