Ok, so I created the Pagemaker package using WinInstall, and like most of us, ran into the problem w/ it starting up, loading the modules, and then closing out. I added the reg keys like Craig said, and recompressed the package and it worked. I thought I owned the package. When I installed it on our Clean Test machine, the app opened and I DIDN'T get the request to register the product.

Cut to 3 days later. I need to wrap the package in Ghost, so I do, and run our ghost task to test the install is good. Whadda know... it installed fine, loaded fine, but that damn registration screen popped up. So I tried the MSI that I created, and the same thing happened. I got that pop up Registration choice box.

I've added keys in HKLM that mirror the keys in HKCUSoftware\Pagemaker\7.0\Registration thinking that might do the trick, but it didn't.

Anyone have any thoughts?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


have you tried running a tool such as installwatch or regmon to see what files or registry keys its modifying when you tell it not to register?
if so it may be one of those adobe things that just doesnt want to work, it may be stored in a hkcu key which can be tricky, see if you can find out what it is actually modifying
Answered 07/14/2005 by: ictu packager
Orange Belt

Please log in to comment
You can look if the value of the Key is being passed to some Poroperty Value....
if this is the case , u can edit the property value accordingly.
Answered 07/14/2005 by: Lillude
Senior Purple Belt

Please log in to comment