VMWare Tools Installation
-
jayteeo
- How helpful is this to you?
- Average Rating 0
- 3944 views
- 03/05/2009
Hey again guys.. The VMWare tools installation is an MSI that uses files from the sourcedir (that contains the MSI file itself). I'm trying to understand if there is a good reason why the files being used wouldn't have been included inside the MSI's binary table instead?
0 Comments
[ - ] Hide Comments
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
Answer this question
or Comment on this question for clarity
Answers
VMTools have always been a real pain to install.Really? I must have installed various versions of it at least 40 times on different hosts/VMs, each time without incident.
I'm trying to understand if there is a good reason why the files being used wouldn't have been included inside the MSI's binary table instead?You mean embedded CABs, not the Binary table. It's always a toss-up for a packager: embedded or external CAB(s) or external, uncompressed files. Sometimes, it's the client's call. At my current client, we tend to restrict MSIs with embedded CABs to 50Mb. Anything bigger and we go external.
Please log in to comment
Hey VBScabb,
When you tell WPS to copy files to a location, does that not write a binary stream to the install database? Or does it actually create a CAB file and then write to the database? The VMWare install has several uncompressed files that it uses.
As for your client's rule to limit embedded CABs to 50 MB, is that for performance reasons?
When you tell WPS to copy files to a location, does that not write a binary stream to the install database? Or does it actually create a CAB file and then write to the database? The VMWare install has several uncompressed files that it uses.
As for your client's rule to limit embedded CABs to 50 MB, is that for performance reasons?
Please log in to comment
I'm not that familiar with the process flow but yes, the embedded CAB is a binary stream but it's not stored in the 'Binary' table.
As for the 50Mb limit, I have no idea why it exists but, guessing, I'd say yes, the client wants to avoid enormous MSIs being copied into the local cache before installation, particularly for remote sites which aren't on fast links.
As for the 50Mb limit, I have no idea why it exists but, guessing, I'd say yes, the client wants to avoid enormous MSIs being copied into the local cache before installation, particularly for remote sites which aren't on fast links.
Please log in to comment
ORIGINAL: VBScab
I'm not that familiar with the process flow but yes, the embedded CAB is a binary stream but it's not stored in the 'Binary' table.
As for the 50Mb limit, I have no idea why it exists but, guessing, I'd say yes, the client wants to avoid enormous MSIs being copied into the local cache before installation, particularly for remote sites which aren't on fast links.
Ahh.. I thought that it got written to the binary table. Wonder where the embedded CAB actually goes.
Please log in to comment
Comments
Please log in to comment