Software Deployment

You must make sure all user settings is repaired by the self-healing

not to hijack his thread, but I was also working with this app and do not understand how to make the user setting self heal upon first execution.

Either you add the missing component keypaths or to make it easier add a Active Setup that installes the user part (msiexec /fu <Product Code>)

I have made this to work but added my own components containing the user resources and customaction to handle the PostInstallLauncher (Pil.exe) and HotSyncManager (HOTSYNC.EXE). All this was done in a transform so the original msi was intact. To use the original msi it is required to preinstall the installshield script engine.

AngeID wrote:
Either you add the missing component keypaths or to make it easier add a Active Setup that installes the user part (msiexec /fu <Product Code>)

I have made this to work but added my own components containing the user resources and customaction to handle the PostInstallLauncher (Pil.exe) and HotSyncManager (HOTSYNC.EXE). All this was done in a transform so the original msi was intact. To use the original msi it is required to preinstall the installshield script engine.

Can you please explain a little more what y did with the native msi file(remember im a newbie) A step by step would be nice:-D

1. I have given <everyone> full access to files c:\%programfolder%\palmone
2. I have preinstalled the installshield engine

So what do i have to do with the native msi file?????Step by step please

Bankeralle

Sorry can't give you a step by step because I did this at a customer so don't have it.

Remember that this is a difficult application to work for multi users so for a beginner this could be very difficult.
But basically what I did was to capture the execution of the application. The start will create a lot of missing registry info for U.S. Robotics so I did add those to the MST. Upon a repair I made sure that the pil.exe was launched. don't remember if there were any parameters to it. During the repair I also killed the hotsync.exe and started it after the pil.exe execution.

Hope that will get you started.

Cheers!

[:@] Thx for the effort AngeID i really appriciated it

But i think you need to specify a bit more for me
As you described i have taken a capture of the application. I installed the isscript before the capture. Then i i took a capture when installing the native palm.msi file
But here it stops


1. What you mean by the "the start will create a lot of missing registry info"
2. Upon a repiar i made sure the pil.exe was launched(what is this) More explanaing needs
I have read that i need to create an repair but how do i do it

As I said this is a difficult application so if you have a friend that could help you would make it easier for ya.

1. What you mean by the "the start will create a lot of missing registry info"
What I meant with capture the start is not capture of the installation but after installation and during the execution of the application (shortcut).

2. Upon a repiar i made sure the pil.exe was launched(what is this) More explanaing needs
Take your time to ready about condition and the CustomAction "Execute Program From Installed Files"
Also you need to understand how the self-healing is triggered by entry points/"key path"

You must make sure all user settings is repaired by the self-healing and also open up the permissions on %ProgramFiles%\palmOne so regular users can write to this directory