Hello all, I hope someone can help me.
I am attempting to package Adobe Page Maker 7.0.1.
When it is installed and first run you get a popup to register it.
I have entered the information and sent it to a printer both in normal installation and during the dependency scan phase.
I have modified one of sections by putting in a Feature Lockdown
bRegistrationProduct
So far nothing has worked the MSI loads but the app fails to run.
I also get errors when un-installing it.
I found a fix for that on this forum, modifying the permissions ro the RSRC folder was suggested but I haven't tried that yet.

Anyone have any ideas where I can start looking for a fix?
I am using Installshield X Professional Adminstudio Edition SP1 on a stripped down
XP box.

ej
0 Comments   [ + ] Show Comments

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.

Answers

0
What is the error you see when you try to initialize PageMaker from your .msi install?

One that you might see is something like "PageMaker is damaged and must be re-installed". If that is the case, then you are missing PageMaker keys from HKLM\Software\Microsoft\CurrentVersion\Uninstall as is mentioned in the AppDeploy KB article about this package. Is it possible that ISAS is excluding these? I know the issnapshot.ini from version 5 excluded everything in that reg branch by default.

The permissions information about the RSRC folder in the KB article was provided by me, but modifying those perms is not a requirement for the package to work. It is just there for those who work and deploy workstations in a locked down environment.

As far as the errors on uninstall go, Windows Installer verbose logging is the place to start examining errors and reasons.

Craig --<>.
Answered 04/14/2005 by: craig16229
Third Degree Brown Belt

Please log in to comment
0
I am not seeing any errors. The only thing that happens is the applications begins, an as soon as the windows start to open, the screen clears.
The shortcuts work, Table30, Dictionary Editor, the readme file and such open and allow me access. I may get a screen that pops up for registration in the web browser window but that's all that happens.

I installed the product on an XP SP2 image and it worked even though I did not register it. I got the registration pop up window but ignored it.
Page maker works without a problem.
The problem occurs after I package it and, as I said, only on that particular poriton of the app "pm70.exe" I have read the readme but that didn't point out anything.

Most annoying, I though it might have been a permissions error but that doesn't seem to be the case.
I did read the posting on the RSRC folder. I also remove the "uninstall Adobe Page Makre" shortcut from the menu, That is a local requirement so users can't remove apps at will. I usually do this right after the application is installed or in the .irp file witht he Exclude function.

ej
Answered 04/14/2005 by: erjones
Senior Yellow Belt

Please log in to comment
0
Removing the shortcut to uninstall PageMaker will definitely not cause a problem. If I remember, it is just a shortcut that points to isuninst.dll or something like that. I typically exclude that .dll as well as the shortcut to it when generating .msi's from apps that were originally authored in InstallShield wizard format.

The uninstall reg keys I mentioned above, though, must be present. Can you verify for us that the PageMaker HKLM\Software\Microsoft\Uninstall keys exists in your package? This drove me crazy the first time I ran into an app that put product key info here instead of in HKLM\Software\[vendor name]\[product name]\registration. The app would install perfectly, ask me for the key and all info, package up easily, install from .msi beautifully - and then refuse to run. I had the HKLM\Software\Microsoft\uninstall as part of my base exclusion list, and didn't catch on to what was happening until I read a post here at AppDeploy.

If those keys do exist in your package, then I fear I will sound like I am just giving the same stock reply to different questions here at AppDeploy - are you familiar with RegMon and FileMon? My guess is that your problem is not one of permissions, but these two tools will still give you a very detailed picture of exactly what is happeing as you initialize the program.

I find these tools absolutely indespensable not only for repackaging, but also for troubleshooting in a wide variety of circumstances. I can't think of any other way to start when there is a problem like this, and there are no error messages from which to work.

Craig --<>.
Answered 04/14/2005 by: craig16229
Third Degree Brown Belt

Please log in to comment
0
Capture the rego part and you will fine it inserts a key into HKCU.....you need to deploy that key with your msi.
Answered 04/15/2005 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
I did see the post on the uninstall issue but didn't think it had anything to do with my problem of getting the app to run. I thought that was related only to the uninstall problem I had with wia*.log files. Now the way you put it in this posting explains it to me better.
I do believe that path in the key registry is not there. I shall look on Monday when I go in.
I'm in Japan so it is Saturday now.

ej
Answered 04/15/2005 by: erjones
Senior Yellow Belt

Please log in to comment
0
Ok I just got a look in the registry section in Installshield.
I went down the path
HKLM\Software\Microsoft and thre is no uninstall folder there. My intent is to make one and see what happens.
The HKLM\Software\vendor name\product name\registration key is there and has the product key installed.
I created an uninstall key, set the type to serial and entered the registration key as data.
what a surprise, it didn't work.
I will read over the posts to see if I missed anything and there is new post that mentions catpuring the "rego part".
I'm not familiar with this could you give me some information. I may know it just not the way it's referenced here.

ej
Answered 04/17/2005 by: erjones
Senior Yellow Belt

Please log in to comment
0
If you want to do a clean test:

- install PageMaker from the native InstallShield setup
- run PageMaker; note the behavior
- navigate to the PageMaker keys at HKLM\Software\Microsoft\uninstall and delete them
- run PageMaker; note the behavior


Craig --<>.
Answered 04/17/2005 by: craig16229
Third Degree Brown Belt

Please log in to comment
0
For the original install of PageMaker from the CD's there is no HKLM\~\uninstall folder.
I searched around but couldn't find one.

ej
Answered 04/17/2005 by: erjones
Senior Yellow Belt

Please log in to comment
0
BTW - when you look for the PageMaker key under HKLM\Software\Microsoft\CurrentVersion\Uninstall, they key will not say "PageMaker". The key will have an alpha-numeric identifier. You will have to click on them one at a time, then look to the right to see which one is PageMaker relevant.

If you are repackaging or testing on a clean machine, that key should be fairly close to the top of the HKLM\Software\Microsoft\CurrentVersion\Uninstall branch.


Craig --<>.
Answered 04/17/2005 by: craig16229
Third Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity