Yahoo! Widget Engine
I want to deploy the Yahoo! Widget Engine using Active Directory to a fleet of Windows XP machines.
I've been able to download the install source from Yahoo! and have been able to extract the vendor msi from the setup.exe.
On my dev machine, I've also been able to install the msi silently with no problems.
The problem I have is with the behaviour of the application when it is first launched. The application displays a series of first run dialog boxes. Once the user clicks through these dialog boxes, about half a dozen widgets are placed on the desktop.
I would like to find a way of disabling this behaviour. I simply want the widget engine to install and open only the widgets that I specify.
I have tried using InCtrl5 to take a snapshot of the various registry keys and files that are created / modified during first run. I must be missing something though because when I add these modifications via a transform, I still get the same behaviour when I first run the application.
Has anyone else attempted this / had success?
Cheers,
I've been able to download the install source from Yahoo! and have been able to extract the vendor msi from the setup.exe.
On my dev machine, I've also been able to install the msi silently with no problems.
The problem I have is with the behaviour of the application when it is first launched. The application displays a series of first run dialog boxes. Once the user clicks through these dialog boxes, about half a dozen widgets are placed on the desktop.
I would like to find a way of disabling this behaviour. I simply want the widget engine to install and open only the widgets that I specify.
I have tried using InCtrl5 to take a snapshot of the various registry keys and files that are created / modified during first run. I must be missing something though because when I add these modifications via a transform, I still get the same behaviour when I first run the application.
Has anyone else attempted this / had success?
Cheers,
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
fosteky
17 years ago
All following advice assumes you have Macrovision AdminStudio or equivalent tools.
So assuming you've created a response transform, and these additional additional config nags come up after first launch of your installed MSI/MST, and considering you've done a manual looky-loo at the registry to see what's getting changed on first launch, it seems likely that there's some flag file determining first launch. I guess I'd try one of the following:
Include your first launch when creating your response transform
OR
Install your current MSI/MST, don't launch it, run Repackager 1st step snapshot, launch program - fill in whatever values on your first launch nag screens, close program, run Repackager 2nd step snap shot. Now go through your output and, specifically looking for what files were generated/changed.
So assuming you've created a response transform, and these additional additional config nags come up after first launch of your installed MSI/MST, and considering you've done a manual looky-loo at the registry to see what's getting changed on first launch, it seems likely that there's some flag file determining first launch. I guess I'd try one of the following:
Include your first launch when creating your response transform
OR
Install your current MSI/MST, don't launch it, run Repackager 1st step snapshot, launch program - fill in whatever values on your first launch nag screens, close program, run Repackager 2nd step snap shot. Now go through your output and, specifically looking for what files were generated/changed.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
