Strange registry error
I'm experiencing a VERY strange problem with WPS 5.51 (no worries, have tried 4.21/5.1 and Installshield X Editor aswell, same problem with the MSI).
I have a <default> registry value that has a filepath as a value ([#FILENAME]) under HKCR. So far so good since this is what I want.
The only problem is that the registrykey gets another files filepath (that doesn't exist in the installation) and even though I change the value of the key to a static value it still gets the same value as before. (???)
Does anyone have an idea of where/what I should look for in the tables?
I have tried searching for the incorrect value the registrykey gets with both WPS/IS and with ORCA but it finds NOTHING. The registry tableentry shows me nothing of value and none of the values/variables it has either.
Anyway, happy new year if no-one can help me!
// martin
I have a <default> registry value that has a filepath as a value ([#FILENAME]) under HKCR. So far so good since this is what I want.
The only problem is that the registrykey gets another files filepath (that doesn't exist in the installation) and even though I change the value of the key to a static value it still gets the same value as before. (???)
Does anyone have an idea of where/what I should look for in the tables?
I have tried searching for the incorrect value the registrykey gets with both WPS/IS and with ORCA but it finds NOTHING. The registry tableentry shows me nothing of value and none of the values/variables it has either.
Anyway, happy new year if no-one can help me!
// martin
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
VikingLoki
19 years ago
Yes, that IS odd. Well, the one thing all your attempts have in common is that particular MSI file. It may be corrupted, I've seen that happen on rare occasion. I'd build another test MSI which installs only that registry entry that you are having trouble with. If that works, then nothing outside of the MSI is forcing that value. The culprit is within your MSI install file. Since WPS, InstallShield and Orca can't find and/or edit out the problem, I'd chalk it up to minor corruption within the MSI. Delete it & rebuild it.
Posted by:
mgroover
19 years ago
I have narrowed this down even further to being something that actually DID have something to do with Wise, will leave an issue to their support personnel.
I tried repackaging with both WPS AND Installshield again and the Installshield package worked fine, very odd!
Will update you more later on.. ;)
I tried repackaging with both WPS AND Installshield again and the Installshield package worked fine, very odd!
Will update you more later on.. ;)
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.