% in a registry value = no repack?

[prostetnic]

D:\apps\SECUDE\PSEMAN~1.EXE "%1"

that is the original entry made by the installer from company

[!psemanagement.exe]

this is what repackager converts it to.

why does the developer/repackager convert this? i would require that the first line be copied digit for digit, but it "intelligently" converts it into unusable rubbish??? why. I assume it is something to do with the "%1" and trying to resolve that as a variable. but can i stop this? i require kinda an urgent answer here please.

[praveenl]

The developer stores this in a formatted substring which will get resolve to full short path of the file during install, with the value 'psemanagement.exe' used as a key into your File table.

[prostetnic]

but it doesn't get resolved at runtime. it writes to the registry of the target machine as [!psemanagement.exe] it doesn't resolve to the full path. making it somewhat difficult to use the app. if i manually edit the fields containing this value i then get a 2343 runtime error from the msi.

[praveenl]

Can u send me the .inc,.isr/.nir? If its a bug I will get it to into our bug tracking system.
Thanks

[prostetnic]

I can send you the whole thing if u want 🙂 it is only a few meg. anyway ism /inc / and log are attatched.

[looeee]

you posted everything apart from the registry entries

\\isw6\isp-soft-all\work in progress\secude\input\Standard.nir

oops

looeee

[prostetnic]

....tell me why i don't like mhundays (sung in true rats style)

I have just finished reading through the adobe repacking post. is it related to this at all? % in filename = 2x%??

[looeee]

prostetnic
I think that I can see what has happened.

The reason why InstallShield has gone to such effort can probably be explained by Winzip.
The registry keys that are hurting you are due to the original installer that you repackaged making short-file-name file associations.
Winzip (and I think that it is unique for this) will complain if the associations are in long-file-name format, and use its own builtin selfrepair. your app probably will not.

Simple solution:
delete all the HKCR\SECLUDE.PSE.File entries and use the regular extension-ProgID tables instead.
Go to the components view and find the one called psemanagement.exe_COM. Once there, go to file types and you will see that most of the stuff you deleted in the last step are duplicated.
All you need to do is to add a new verb, "Open" and set its argument to -i %1


looeee

[prostetnic]

i'll have a look today and let you know.