Licensing Issue while packaging RoboHelpX5!!
Hi All,
Im trying to package RoboHelpX5 with InstallShield. It has a vendor MSI and an ISScript8.msi which needs to be install first.
There is a setup.exe which actually installs these MSIs in order.
The problem is that setup.exe askes for registration keys and creates some registry keys using some inbuilt algorithm or by calling some dll.
The MSI does not ask for registration keys and no registry keys are created.
Hardcoding of the registry keys also dont work.
Is there any way to get around this problem???
Im trying to package RoboHelpX5 with InstallShield. It has a vendor MSI and an ISScript8.msi which needs to be install first.
There is a setup.exe which actually installs these MSIs in order.
The problem is that setup.exe askes for registration keys and creates some registry keys using some inbuilt algorithm or by calling some dll.
The MSI does not ask for registration keys and no registry keys are created.
Hardcoding of the registry keys also dont work.
Is there any way to get around this problem???
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
VikingLoki
19 years ago
I'd be willing to bet the MSI makes the registry keys by calling some sort of Custom Action, probably a .DLL in the installation files, or imbedded in the MSI's Binary table.
I've had some success with other apps by scouring the MSI Code for exactly where that Registration DLL is called. You'll probably find that its not being called without the SETUP.EXE becuase some property is not being populated when you call the MSI directly. Either reverse-engineer the MSI Code to determine what the property value should be, or if the property is only in the condition and is not passed to the DLL, modify the condition so that it doesn't need the property value and launches the Custom Action when you want it.
This can be a challenge though, it's like looking for a needle in a haystack when you don't know what shape the needle is. It can be done though.
I've had some success with other apps by scouring the MSI Code for exactly where that Registration DLL is called. You'll probably find that its not being called without the SETUP.EXE becuase some property is not being populated when you call the MSI directly. Either reverse-engineer the MSI Code to determine what the property value should be, or if the property is only in the condition and is not passed to the DLL, modify the condition so that it doesn't need the property value and launches the Custom Action when you want it.
This can be a challenge though, it's like looking for a needle in a haystack when you don't know what shape the needle is. It can be done though.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
