Adobe Premier Elements - Missing Details
Hi Everyone,
I've spent the last few days trying to create a package for Adobe Premier Elements 1 and I'm at the point of giving up. I first started off by using Wininstall LE 2003 to create the package. This installs fine, but when trying to run it, the message "registration information is invalid. Please reinstall" pops up.
I noticed that the capture process didn't capture some vital looking registry entries and so I manually added these in. They were the ones as mentioned here. This didn't make a bit of difference.
So I set about on the mission of identifying the snippet of registry data the capture process had missed out. The only way I could get it working was to merge an entire fragment from the 'currentversion' part of the registry (taken from a clean installation) with that of a machine containing a faulty MSI installation. So I've managed to narrow the missing part down to this section at least!
What troubles me is, the guide (mentioned above) rates the package as very easy! What am I doing wrong?! I've not dabbled with MSTs yet, is this what I should be doing? I thought as long as I embed the data into the MSI though, there would be no point. I've even taken the MSI off the Elements CD and added in the entries using 'ORCA'.
Can anyone out there help me!?
Thanks in advance
Nick
I've spent the last few days trying to create a package for Adobe Premier Elements 1 and I'm at the point of giving up. I first started off by using Wininstall LE 2003 to create the package. This installs fine, but when trying to run it, the message "registration information is invalid. Please reinstall" pops up.
I noticed that the capture process didn't capture some vital looking registry entries and so I manually added these in. They were the ones as mentioned here. This didn't make a bit of difference.
So I set about on the mission of identifying the snippet of registry data the capture process had missed out. The only way I could get it working was to merge an entire fragment from the 'currentversion' part of the registry (taken from a clean installation) with that of a machine containing a faulty MSI installation. So I've managed to narrow the missing part down to this section at least!
What troubles me is, the guide (mentioned above) rates the package as very easy! What am I doing wrong?! I've not dabbled with MSTs yet, is this what I should be doing? I thought as long as I embed the data into the MSI though, there would be no point. I've even taken the MSI off the Elements CD and added in the entries using 'ORCA'.
Can anyone out there help me!?
Thanks in advance
Nick
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
jonasm
18 years ago
Hi!
Are you repackaging the application? As far as I see, this application comes as an MSI so you can create a MST instead.
/Jonas
Are you repackaging the application? As far as I see, this application comes as an MSI so you can create a MST instead.
/Jonas
Posted by:
John McDermott
18 years ago
Maybe a dumb question, but are you packaging version 1.x or 2.x?
Because the procedures are different for version 2.
Because the procedures are different for version 2.
Posted by:
nick3young
18 years ago
Thanks for the replies guys.
I'm attempting to package 1.X.
Jonasm, does creating and applying an MST have a different effect to simply directly editing the table entries in the MSI?
Thanks
I'm attempting to package 1.X.
Jonasm, does creating and applying an MST have a different effect to simply directly editing the table entries in the MSI?
Thanks
Posted by:
jonasm
18 years ago
Well.. The result is supposed to be the same, but it's recommended to create a MST if you already has a vendor-MSI.
/Jonas
/Jonas
Posted by:
nick3young
18 years ago
In the Premier Elements 1.x guide, IanE says:
Properties I set are:
AgreeToLicense (yes)
COMPANYNAME
SERIALNUMBER
USERNAME
From this list, the only entry in the properties table in the vendor msi is 'AgreeToLicense'. Does this mean I have to create the other 3 as rows in the properties table?
What complicated this is that the 3 missing rows do actually exist, but as values in the registry table. Do I just change these values as opposed to creating them as new rows in the properties table?
Finally, with regards to importing the registry file into the mst, is there any difference with doing this to simply changing the registry entries in the mst?
Properties I set are:
AgreeToLicense (yes)
COMPANYNAME
SERIALNUMBER
USERNAME
From this list, the only entry in the properties table in the vendor msi is 'AgreeToLicense'. Does this mean I have to create the other 3 as rows in the properties table?
What complicated this is that the 3 missing rows do actually exist, but as values in the registry table. Do I just change these values as opposed to creating them as new rows in the properties table?
Finally, with regards to importing the registry file into the mst, is there any difference with doing this to simply changing the registry entries in the mst?
Posted by:
Blue_Demon
18 years ago
Leave the vendor MSI as is, then create an MST.
Also, does the application use an ini file to contain the registration details? I had a similar problem with PhotoShop. Once I used the ini file instead of an MST it worked fine.
Then I created an MST with reg key changes etc, all worked fine.
Also, does the application use an ini file to contain the registration details? I had a similar problem with PhotoShop. Once I used the ini file instead of an MST it worked fine.
Then I created an MST with reg key changes etc, all worked fine.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.