/build/static/layout/Breadcrumb_cap_w.png

Compress Admin install point

I have an admin install point for a vendor app (PGP Desktop) I would like to recompress it into a single msi. I tried using the vbs script WiMakCab.vbs using the following command:

cscript wimakcab.vbs C:\pgp\pgpdesktop.msi Cabs.w1 /L /C /U /E

I get the following error: Makecab.exe failed, possibly could not find source files, or invalid DDF format. I have done this process with Adobe Acrobat reader and it worked great. Anyone run into this before and have an idea?

0 Comments   [ + ] Show comments

Answers (15)

Posted by: Inabus 12 years ago
Second Degree Green Belt
0
Revert the MSI back to an ISM or Wise equivalent and then recompile as 1 MSI.

P
Posted by: joedown 12 years ago
Third Degree Brown Belt
0
I didn't know that was possible with a vendor supplied MSI?


ORIGINAL: Inabus

Revert the MSI back to an ISM or Wise equivalent and then recompile as 1 MSI.

P

Posted by: anonymous_9363 12 years ago
Red Belt
0
If you're using Wise or IS, why not simply set the media option to internal CABs? Or take the original MSI from which you created the AIP and merge your MST with it using Orca/InstEdit? Apart from the fact that the vendor is likely to term the result as 'unsupported', of course?
Posted by: joedown 12 years ago
Third Degree Brown Belt
0
I have IS but it is the Zenworks edition which is extremely limited. I was hoping to recompress this install point so I would have a single file to distribute instead of multiple files. It just seems odd that this worked great for an Adobe product of all products but fails with a Wise built vendor install.


ORIGINAL: VBScab

If you're using Wise or IS, why not simply set the media option to internal CABs? Or take the original MSI from which you created the AIP and merge your MST with it using Orca/InstEdit? Apart from the fact that the vendor is likely to term the result as 'unsupported', of course?
Posted by: nheim 12 years ago
10th Degree Black Belt
0
Hi joe,
we use this script regularly, but there are a few things to keep an eye on.
Check the following things:
- is admin install in Summary Info checked?
- do the file attributes contain the compressed bit (decimal 8094)?
- invoke the command at the root of the AIP!
- Switch on Installer logging, so you can check the CostFinalize action and see whats wrong with the directory tree.

Regards, Nick
Posted by: joedown 12 years ago
Third Degree Brown Belt
0
Thanks Nick for the info, I learned of this feature from a post you made awhile back. I tried it with Adobe reader and it worked so slick I thought I would utilize this more often.

The admin install has the Summary Info checked.
The file attributes in the file table have either 0 or 1024. Do I need to make a change here?
I have been running the command from the root of the install point.
Here is the CostFinalize action from the log. I don't see any problems there. Unless it is this line here :

MSI (c) (A8:E0) [08:29:45:062]: Note: 1: 2262 2: RemoveFile 3: -2147287038 but I don't know what that means.


Action start 8:29:45: CostFinalize.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
MSI (c) (A8:E0) [08:29:45:062]: Note: 1: 2205 2: 3: Patch
MSI (c) (A8:E0) [08:29:45:062]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'C:\'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding ProfilesFolder property. Its value is 'C:\WINDOWS\'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding PGP property. Its value is 'C:\Documents and Settings\All Users\Start Menu\Programs\PGP\'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding drivers property. Its value is 'C:\WINDOWS\system32\drivers\'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding PGPCOMMON property. Its value is 'C:\Program Files\Common Files\PGP Corporation\'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding Strings property. Its value is 'C:\Program Files\Common Files\PGP Corporation\Strings\'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding INSTALLDIR property. Its value is 'C:\Program Files\PGP Corporation\'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding PGP_Echo property. Its value is 'C:\Program Files\PGP Corporation\PGP Desktop\'.
MSI (c) (A8:E0) [08:29:45:062]: PROPERTY CHANGE: Adding Documentation1 property. Its value is 'C:\Program Files\PGP Corporation\PGP Desktop\Documentation\'.
MSI (c) (A8:E0) [08:29:45:062]: Target path resolution complete. Dumping Directory table...
MSI (c) (A8:E0) [08:29:45:062]: Note: target paths subject to change (via custom actions or browsing)
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: TARGETDIR , Object: C:\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: WindowsFolder , Object: C:\WINDOWS\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: ProfilesFolder , Object: C:\WINDOWS\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: RecentFolder , Object: C:\Documents and Settings\wsadmin\Recent\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: NetHoodFolder , Object: C:\Documents and Settings\wsadmin\NetHood\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: StartMenuFolder , Object: C:\Documents and Settings\All Users\Start Menu\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: ProgramMenuFolder , Object: C:\Documents and Settings\All Users\Start Menu\Programs\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: StartupFolder , Object: C:\Documents and Settings\All Users\Start Menu\Programs\Startup\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: PGP , Object: C:\Documents and Settings\All Users\Start Menu\Programs\PGP\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: SystemFolder , Object: C:\WINDOWS\system32\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: drivers , Object: C:\WINDOWS\system32\drivers\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: ProgramFilesFolder , Object: C:\Program Files\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: CommonFilesFolder , Object: C:\Program Files\Common Files\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: PGPCOMMON , Object: C:\Program Files\Common Files\PGP Corporation\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: Strings , Object: C:\Program Files\Common Files\PGP Corporation\Strings\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: INSTALLDIR , Object: C:\Program Files\PGP Corporation\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: PGP_Echo , Object: C:\Program Files\PGP Corporation\PGP Desktop\
MSI (c) (A8:E0) [08:29:45:062]: Dir (target): Key: Documentation1 , Object: C:\Program Files\PGP Corporation\PGP Desktop\Documentation\
MSI (c) (A8:E0) [08:29:45:062]: Note: 1: 2262 2: RemoveFile 3: -2147287038
Action ended 8:29:45: CostFinalize. Return value 1.


ORIGINAL: nheim

Hi joe,
we use this script regularly, but there are a few things to keep an eye on.
Check the following things:
- is admin install in Summary Info checked?
- do the file attributes contain the compressed bit (decimal 8094)?
- invoke the command at the root of the AIP!
- Switch on Installer logging, so you can check the CostFinalize action and see whats wrong with the directory tree.

Regards, Nick

Posted by: anonymous_9363 12 years ago
Red Belt
0
MSI (c) (A8:E0) [08:29:45:062]: Note: 1: 2262 2: RemoveFile 3: -2147287038 but I don't know what that means.I wish MS would decide one way or the other how it presents error numbers! This is a quasi-decimal representation of the error 80030002. (Use Calc in 'Scientific' view to subtract 2147287038 from zero, then click the 'Hex' radio button. You get FFFFFFFF80030002. You always throw away the 8 leading Fs.

So, back to 80030002... The most significant digit for our purposes is the last one, 2. DOS error 2 is "File not found." Thus, to answer your question, the action would have removed a file but it wasn't there.
Posted by: AngelD 12 years ago
Red Belt
0
Sounds more like the RemoveFile table does not exist in the MSI
Posted by: joedown 12 years ago
Third Degree Brown Belt
0
RemoveFile table is present but it is empty.

ORIGINAL: AngelD

Sounds more like the RemoveFile table does not exist in the MSI
Posted by: jmcfadyen 12 years ago
5th Degree Black Belt
0
the sequence of the RemoveFile Action is prior to CostFinalize that seems a little odd.

try moving it after InstallInitialize
Posted by: AngelD 12 years ago
Red Belt
0
You got good eyes John :)
Posted by: joedown 12 years ago
Third Degree Brown Belt
0
No, I checked the InstallExecuteSequence and the RemoveFile action is after CostInitialize and InstallInitalize actions.


ORIGINAL: jmcfadyen

the sequence of the RemoveFile Action is prior to CostFinalize that seems a little odd.

try moving it after InstallInitialize

Posted by: nheim 12 years ago
10th Degree Black Belt
0
Hi Joe,
i think we are on the wrong track here.
WiMakCab does only a directory resolution and nothing else.
Therefore, that looks, as if the directory resolution fails.
So the question is:
What did you change?
I mean, there is a reason, you did the admin install, isn't it?

Next step: Do a validation and look at the errors.

BTW: The MSI was made with Wise Package Studio. Only this app stores the CAB in a binary table.

Regards, Nick
Posted by: joedown 12 years ago
Third Degree Brown Belt
0
Got it figured out. There was an error in a line of the WiMakCab.vbs file. Set Compress was set to 7 instead of ON I think it was supposed to be set CompressionLevel=7. It's working great now.


ORIGINAL: nheim

Hi Joe,
i think we are on the wrong track here.
WiMakCab does only a directory resolution and nothing else.
Therefore, that looks, as if the directory resolution fails.
So the question is:
What did you change?
I mean, there is a reason, you did the admin install, isn't it?

Next step: Do a validation and look at the errors.

BTW: The MSI was made with Wise Package Studio. Only this app stores the CAB in a binary table.

Regards, Nick

Posted by: anonymous_9363 12 years ago
Red Belt
0
That must be an old SDK you have. I checked back through the last 2 releases which I have and both have it set to "ON". Still, good job on tracking it down!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ