Hi all
I created a .cab file i put entry of that cab file in media table using installshield . At the time of installtion i got the pop-up


The file required can not be installed because the cabinate file is not digitally signed . This may indicate that the cabinate file is corrupted .


I created a cabinate file with cabpacker 1.4 tool
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
This may indicate that the cabinate file is corrupted .Nonsense.

Clearly, you're trying to package using Orca or InstEdit but you are not yet at the level of knowledge to make that a realistic option.

Before you do anything else, read & digest Phil Wilson's book The Definitive Guide to Windows Installer. It's available as a downloadable PDF. Then have you employer purchase a proper MSI authoring tool. Today, that means InstallShield: Wise is dead.
Answered 10/13/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab



Clearly, you're trying to package using Orca or InstEdit



Not so sure about that Ian, the OP does mention that he put an entry in the Media table using Installshield ... and if thats the case theres no need to use 3rd party CAB packing tools as the 'Releases' section in the InstallShield Editor should take care of that (assuming that the base MSI is converted to an ISM project file first). Also, a full validation taking specific note of any ICE81 warnings/errors would probably assist.

Agree wholeheartedly with your comment to the OP to read The Definitive Guide to Windows Installer as I sense a level of inexperience here.

Spartacus
Answered 10/13/2011 by: spartacus
Black Belt

Please log in to comment
0
Oops! Missed that! LOL. I guess I was harking back to another post from the same user which also suggested that he was editing tables directly.
Answered 10/13/2011 by: VBScab
Red Belt

Please log in to comment
0
please provide me vbscript file to install/uninstall msi with mst because i want to use that in CA.... . I am new in packaging

Thank you for suggesting the The Definitive Guide to Windows Installer
Answered 10/13/2011 by: rahulkumar
Senior Yellow Belt

Please log in to comment
0
You should not nest MSIs i.e. run one MSI by executing a Custom Action in another MSI.

Besides, there must be 100,000 script examples showing how to execute a program.
Answered 10/13/2011 by: VBScab
Red Belt

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