/build/static/layout/Breadcrumb_cap_w.png

Adobe Premiere Pro 1.5 registration issue

OK, so I used ABCPY.INI to enter all of the information for the package. It worked like a charm but I am still getting the registration error asking Premiere Pro to be reinstalled. I moved the proper registry key from HKLM\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\IMINSTALL to the package but I am still getting the registration error. Does anyone know how to fix this issue?
Thanx.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: ictu packager 18 years ago
Orange Belt
0
so you copied the entire registy key from HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A14F7508-B784-40B8-B11A-E0E2EEB7229F} ??
if so it should be ok but with premiere pro 1.5 i had problems because i had to install a plugin for 2d3 steadymove - you have to include the same registry keys for that sort of thing too - located in the same area but under a different guid
Posted by: rodina00 18 years ago
Orange Belt
0
I'm using Wise pacakage Studio, so I copied that registry key and tested. it test fine but then I install the package aon another machine and I get the registration error. all of the other machines have admin priviledges, so it's not that... I used abcpy.ini to auto enter the info but I still get the same error.
Posted by: rodina00 18 years ago
Orange Belt
0
I also noticed that there is a reg key in the destination under Uninstall called [Product Code] and that the data in the key is only the Display icon. That data is in the A14 key, would that make a difference?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ