Hi Brad,

How to install Java runtime library and/or Qt libraries on WinXPe? What is the approach for installing apps on WinXpe?

I hope there is a way to decomponize it, but I did not see it yet...

 Appreciate the response,

Larry

Hi Brad,

Just to clarify, I am asking about SUN Java runtime libraries and Qt runtime libraries.

Thank you,

Larry

ldobkin:

Hi Brad,

How to install Java runtime library and/or Qt libraries on WinXPe? What is the approach for installing apps on WinXpe?

I hope there is a way to decomponize it, but I did not see it yet...

 Appreciate the response,

Larry

Hi Larry,

There are really two approaches to installing applications on XPe / WES2009. I'll call them Native Componentization and Installer Componentization (I just made that up).

Native Componentization:

• Componentizing an application by breaking the installer up into the individual files and registry data (registry data could be software information, service parameters,etc..).
• Requires a "clean" test system (preferrably XP Professional) where the application has never been installed.
• Use any number of snapshot or tracking tools (Sysinternals Filemon / Regmon for example) to monitor the application while it is being installed.
• Take the resulting output and add it as Files and Regisry Data in a new component.
• Alternatively, use Sean Liming's XPe Tools to "capture" the installer as its happening. The output is a SLD. http://www.sjjmicro.com/XPES_Tools_R2.html (probably the best $120.00 you'll spend during your XPe development time)

Installer Componentization:

• Create a new component that installs the applicaiton using its setup program during the FBA process.
• Involves creating a new component, adding the installation files as File resources and adding an FBA Generic Command that runs the applicable setup.exe.
• The FBA Generic Command should be launched in a late phase in FBA (post 8500, preferably 12000).
• Add a Component Dependency on the Windows Installer component (for MSI installs).

The first approach has value because it does not require the Windows Installer component. So, if your solution requires a level of security where end users cannot add applications, this method is a good choice. However, the development time required to monitor the setup can be long.

The second approach is fast, generally just a few minutes to create the component, but requires Windows Installer. Also, if the setup cannot be installed silently then someone will have to respond to the setup prompts during FBA. If the addition of Windows Installer is a show stopper, you could still use this method and just hack out the Windows Installer binaries post-FBA.

Hope that helps,
Brad