Nov 3, 2009 5:54 PM
What is the ETA for sw_lic_full_installer.msi 11.5.2.602/v10.4.2.27
-
Like (0)
I'm assuming that when the updated sw_lic_full_installer.msi is released, it will install 11.5.2.602 with the 10.4.2.27 compatibility components (based on the pattern seen with 11.5.0.600/10.4.0.25 and 11.5.1.601/10.4.1.26). Is there an ETA for its release? I hacked up a quick wget script to bang on fpdownload.macromedia.com so as to avoid having to repeatedly download the thing (this way it just grabs the headers notices the Content-Length and Last-Modified values and then sleeps for 60 seconds), but it would be nice to know how long I'm going to have to wait!
It's still showing "Last-Modified: Wed, 22 Jul 2009 12:01:55 GMT".
I would suggest you put the kettle on and be prepared to wait a long time. I've banged on about this multiple times and yet no-one in Adobe actually seems to care about the MSI. It's only the standard method used by big corporations so it's obviously low priority for them.
It's possible they're getting better. I don't recall much of a delay for the July 28, 2009 security update. It appears that I downloaded that file around 10:30 AM the day of the announcement (and the file itself is dated July 22nd, so it was ready to go 6 days ahead of time) . I'm hoping that this time it's just a minor oversight and someone forgot to publish the file. I suspect Sean Wilson may have an inside track of some sort (in http://forums.adobe.com/thread/514300?tstart=0 he mentioned on Oct 28th that "10.4.1.27 is on the verge of release."). Maybe he can shed some light (and get the issue resolved).
If I have an ETA by 2:30 PM EST (and that ETA is within the next 24 hours), I'll wait for the MSI. Otherwise I'll punt and use the EXE for now. Once the MSI releases, I'll package and deploy a job to remove the EXE and install the MSI (since I want the updated 10.4.* components out there). It only means several extra hours of work for me plus an extra reboot and 7 MB of bandwidth for all of my users (since Adobe now recommends a reboot between the uninstall of the previous version and the install of the new version), but that's life. I'd prefer the MSI (since it's easier to script the uninstall and has the 10.4.* components), but I'll use the EXE in the interim if the MSI isn't available and let the users enjoy yet another reboot!
Agreed, this is very frustrating. I get the bulletin telling me there's a new version available, grab the MSI and discover it's not the latest version. It would be nice if it was uploaded and ready to go alongside the other versions when it's announced.
Hey Toby, could you share that wget script you mentioned? That would be very useful to have.
Actually, I could probably write my own if I had a direct link to the file to download. The only link I can find is http://www.adobe.com/cfusion/entitlement/index.cfm?k=2C0FCE6A-D493-78E C-C008D9780095EA0E&loc=en_us# but wget doesn't understand it.
Thanks!
Aaron
I figured out the URL with a little sleuthing - found lots of references to the directory in question for the EXE files ![]()
I'm actually running it from my home Linux server (gets it outside of the corporate firewall so I don't have to worry about the proxy server).
It's a quick tcsh script:
while (1)
sleep 60
end
But you can loop that in any language you want - if you've got sleep.exe installed on a Windows box, use:
for /L %i in (1,1,1000) do @ sleep 60 & wget . . .
A new version is up there now at http://fpdownload.macromedia.com/get/shockwave/default/english/win95nt /latest/sw_lic_full_installer.msi
Last-Modified: Fri, 06 Nov 2009 10:52:22 GMT
MSI Property ProductVersion says "11.5.2.602".
Many thanks for the heads up.
Quick note - the new MSI re-installs upon first use. This resets any registry changes you make post-install to turn off auto-update. It appears that the best workaround is an MST file that adjusts those registry values (that way when the MSI does a re-install upon first use, it adjusts those registry values based upon the MST used during installation).
Also, the version on the compatibility components is as Sean Wilson predicted - 10.4.1.27.
That is to say, the last few releases have been:
11.5.0.600/10.4.0.25
11.5.1.601/10.4.1.26
11.5.2.602/10.4.1.27
Notice that this release doesn't follow the pattern perfectly.
And hey, check this out. The 11.5.1.601/10.4.1.26 installer creates
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Op tionalComponents\SwDir]
"Installed"="1"
Where as the 11.5.2.602/10.4.1.27 installer creates:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Op tionalComponets]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Op tionalComponets\SwDir]
"Installed"="1"
Glad I've got those OptionalComponets installed!
Maybe that's a new sort of netbook made from fishing gear - Comp-O-Nets!
Also, I'm not sure which is the correct key, but the previous version uses:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer \MimeTypes]
The new version uses:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer \Mime Types]
When I do a Google search for 'MozillaPlugins Suffixes "MimeTypes" Registry', I get 6,890 hits. When I do one for 'MozillaPlugins Suffixes "Mime Types" Registry', I get 2,730 hits.
Toby, thanks for the heads-up. What are you using to build the MST?
I used an ancient version of InstallShield. Should be able to do it with Orca, though (http://msdn.microsoft.com/en-us/library/aa370557(VS.85).aspx). I made changes in the Registry table to the following Keys:
(there may be a typo or two here - @#%$@#%@# InstallShield wouldn't let me copy out of Direct Editor):
SOFTWARE\Adobe\Shockwave 11\AutoUpdate
SOFTWARE\Adobe\Shockwave 11\collectstats
SOFTWARE\Adobe\Shockwave 11\uicontrol\CollectStatistics
SOFTWARE\Adobe\Shockwave 11\uicontrol\defaultautoupdate
SOFTWARE\Adobe\Shockwave 11\uicontrol\defaultcollectstats
SOFTWARE\Macromedia\Shockwave 10\CollectStatistics
SOFTWARE\Macromedia\Shockwave 10\collectstats
SOFTWARE\Macromedia\Shockwave 10\uicontrol\CollectStatistics
SOFTWARE\Macromedia\Shockwave 10\uicontrol\defaultautoupdate
SOFTWARE\Macromedia\Shockwave 10\uicontrol\defaultcollectstats
Names were all blank (i.e. "(Default)", AKA @ when in a .REG file, blank in the Registry MSI table). Value was set to 'n'.
Note that SOFTWARE\Macromedia\Shockwave 10\AutoUpdate already defaulted to 'n'.
I didn't want to break out Orca
Thanks for the response. I'll be looking for these keys when I get back to work tomorrow.
In addition to the msi changes Toby has suggested I've also edited another entry near the bottom of the Registry table. I was finding a DCOM error in the System Event Log every time Shcokwave launched because it was failing to execute the command:
[INSTALLDIR]SHOCKW~1\SWHELP~1.EXE"
This is because the string is terminated with a quote, but not started with one. I've edited the value to remove the trailing quote and added the change to my mst (using orca) and this has stopped the error. If you search for the line above. The key you're looking for in the table is
CLSID\{1F3CB77D-D339-49e0-B8E4-FECD6D6F8CB8}\LocalServer32
Shockwave did seem to function even when the error was occurring, but it was obviously failing to do something. Seems like rather sloppy work from Adobe.
Note that changing the value in the registry after install will fix the issue too, but only until another user uses Shockwave, at which point the rather annoying msiexec reconfiguration will put the quote back in.
Hi,
I have posted an MST file which fixes this and other issues to the following thread here:
http://forums.adobe.com/message/2697135#2697135
Please post any feedback to that thread!
Kind regards,
Chris Hill
Copyright © 2011 Adobe Systems Incorporated. All rights reserved.
Use of this website signifies your agreement to the Terms of Use and Online Privacy Policy (updated 07-14-2009).