Three Versions of Shockwave 11
I'm tasked to install Shockwave 11 on our corp's workstations. I went to Adobe's page and was presented with three different installs. An MSI, slim EXE, and full EXE. Though Adobe doesn't show any differences besides the names of these installers, each has a considerably different size footprint:
MSI = 156MB to 208MB
slim EXE = 5.2MB
full EXE = 182MB to 234MB
Another issue I've noticed is that when pushing the MSI (using Altiris), the install does not appear in Add/Remove Programs. The installation does appear when pushing either EXE.
The Adobe Flash Player MSI does not show the size of the install in Add/Remove programs and, when installing the EXE, it does not show up at all.
I'm waiting to hear back from Adobe regarding these issues but I thought I'd try here as well.
MSI = 156MB to 208MB
slim EXE = 5.2MB
full EXE = 182MB to 234MB
Another issue I've noticed is that when pushing the MSI (using Altiris), the install does not appear in Add/Remove Programs. The installation does appear when pushing either EXE.
The Adobe Flash Player MSI does not show the size of the install in Add/Remove programs and, when installing the EXE, it does not show up at all.
I'm waiting to hear back from Adobe regarding these issues but I thought I'd try here as well.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
I'm not familiar with the SW flavours nor have I looked at the web site but, at a guess, I'd say that the slim EXE performs a web-driven install (where the files aren't copied locally) and the full EXE simply extracts the MSI and runs MSIExec against it.
As to the appearance or not in ARP, this is normally controlled by the presence or absence of the ARPSYSTEMCOMPONENT property. Note that I say 'presence or absence': you might reasonably expect a '1' to indicate that the package is a system component (for ARP purposes) and that a '0' would indicate that it is not. That is not the case, however. You could set the property's value to 'FooBar' and the package wouldn't appear in ARP. So, if you want it to appear in ARP, use the MSI along with a transform in which the ARPSYSTEMCOMPONENT property is removed.
As to the appearance or not in ARP, this is normally controlled by the presence or absence of the ARPSYSTEMCOMPONENT property. Note that I say 'presence or absence': you might reasonably expect a '1' to indicate that the package is a system component (for ARP purposes) and that a '0' would indicate that it is not. That is not the case, however. You could set the property's value to 'FooBar' and the package wouldn't appear in ARP. So, if you want it to appear in ARP, use the MSI along with a transform in which the ARPSYSTEMCOMPONENT property is removed.
Posted by:
nheim
15 years ago
Hi Marek,
see: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_19523
for an explanation of the full/slim versions of shockwave player.
Be aware, that version 11 is the first version of the MSI package, which installs the Mozilla plugin too, if needed.
The size of the hole installation is about 15MB.
Regards, Nick
see: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_19523
for an explanation of the full/slim versions of shockwave player.
Be aware, that version 11 is the first version of the MSI package, which installs the Mozilla plugin too, if needed.
The size of the hole installation is about 15MB.
Regards, Nick
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
