To whom it may concern:

I did hope I would resolve this issue on my own, but I can't find the history of anybody solving it. Anyways, I receive this "famous" warning every time I build my XPe image for the target:

Warning  1115: This is an evaluation run-time image that is only valid for 90 to 180 days after it is first used. Estimated component sizes..

despite the fact the WinXPe product key was used and typed twice for tools and database. What is the magic for resolving this issue, please?

 Appreciate your response,

Larry

ldobkin:

To whom it may concern:

I did hope I would resolve this issue on my own, but I can't find the history of anybody solving it. Anyways, I receive this "famous" warning every time I build my XPe image for the target:

Warning  1115: This is an evaluation run-time image that is only valid for 90 to 180 days after it is first used. Estimated component sizes..

despite the fact the WinXPe product key was used and typed twice for tools and database. What is the magic for resolving this issue, please?

 Appreciate your response,

Larry

Hi Larry,

This may just be confusion between the PID for the tools and the PID for the runtime. The tools and database are installed using a 5x5 PID that is different from the Runtime PID that you enter in Target Desginer. The PID you used to install the tools cannot be used in Target Desginer. When you purchase licenses through your distributor you will receive the COA stickers and a card which contains the 5x5 PID that should be entered in Target Desginer. Have you purchased any runtime licenses yet?

Brad

Hi Brad,

Your response was right on the money! Thank you.

 Q1. Are there a way to add this runtime PID without removing WinXPe and re-installing it from the getgo?

Q2. Are there any association between wrong runtime license PID for the Target Designer and a missing system volume folder in the final XPe image?

 Appeciate your response,

Larry

Hi Larry,

ldobkin:

Q1. Are there a way to add this runtime PID without removing WinXPe and re-installing it from the getgo?

 Unfortunately not, once the timebomb is set in the XPe image, there is not a way to add the PID after the fact.

ldobkin:

Q2. Are there any association between wrong runtime license PID for the Target Designer and a missing system volume folder in the final XPe image?

I wouldn't think so. There is not problem with building the 120 evaluation images or with capturing / deploying them to other systems. (at least none that I'm aware of). Honestly, I haven't dug into your response in the other thread on the sysvol issue. I'll try to take a look at that this evening.

Brad

Hi Brad,

what is the safe way to uninstall XPe SP3 and SP2 besides normal add/remove programs? The information is very finicky especially for SP2.

 Thank you,

Larry

Hi Brad,

Sorry for bugging. The information for the removal of XPe SP2 must be obsolete since the following directory and the executable does not exist anywhere

$NtServicePackUninstall$\spuninst\spuninst.exe

I hope to see some light on these issues, please. Can SP2 be removed from the component database the same way as SP3 was before jumping into add/remove ..

Thank you,

Larry

Hi Larry,

I'm not totally clear on what you are trying to do. Are you attempting to uninstall the SP2 and / or SP3 updates from the Component Database in XP Embedded / WES2009?

Brad

Hi Brad,

I finally received the run-time license for the Target Designer. And now I am in the process of removing XPe SP3 and SP2.  I removed SP3 using the component database. I have not done anything for SP2 since the info is confusing and incorrect.

Thank you,

Larry

ldobkin:

Hi Brad,

I finally received the run-time license for the Target Designer. And now I am in the process of removing XPe SP3 and SP2.  I removed SP3 using the component database. I have not done anything for SP2 since the info is confusing and incorrect.

Thank you,

Larry

Hi Larry,

Got it, thanks for the clarification. So you are trying to remove the evaluation tools and database from your development machine so that you can install the licensed versions? I only have WES2009 installed here (which is a single remove in add/remove programs) but if I rememeber correctly you would uninstall the Windows XP Embedded database and Tools from Add/Remove and then reinstall with the licensed version. You do not have to remove the installation of SQL, the installer will locate the SQL instance and attach the licensed database. I do not remember explicitly running a service pack uninstaller like you are describing.

Brad

Hi Brad,

 Thank you for the prompt response.

Where did you download WES2009.slx file?

Thank you,

Larry

ldobkin:

Hi Brad,

 Thank you for the prompt response.

Where did you download WES2009.slx file?

Thank you,

Larry

Hi Larry,

I'm not quite sure what you mean. Maybe I should clarify the product names (they can be confusing). Windows Embedded Standard 2009 is not simply a configuration (SLX) of Windows XP Embedded, it is the successor product. When you install Windows Embedded Standard 2009 (database and tools) you are getting the latest version of the toolkit and a database / repository that contains the latest feature and security updates for the Windows Embedded product that is based on the XP codebase. You can open your previously built XP Embedded configurations (SLX) in the WES2009 toolkit.

Do you need a download link to the Windows Embedded Standard 2009  evaluation edition? Take a look here: http://www.microsoft.com/downloads/details.aspx?familyid=4715B660-9C24-4088-8448-96C8ABF2A940&displaylang=en

Edited to add: Windows Embedded Standard 2009 also reset the support life cycle, so you get 5 years mainstream and 5 years of extended support from the release date of WES2009.

Hope that helps.

Brad

Hi Brad,

Thank you for the prompt response.

I have no problem upgrading to WES2009 and I most likely have to do it anyway. Now, will my run-time license for XPe be good for WES2009?

It sounds like from your answer that I would need to updgrade my SLX file manually to WES2009 standard.

Appreciate the response.

 Thank you,

Larry