Suggest changes made to Shockwave and Silverlight

[Whatacrock]

As many of you that may use a x64 Operating System will notice in autopatcher AddOns(extras) release that there are multiple entries for the same items, mainly speaking of Shockwave Player and Silverlight at this stage.

Shockwave Player is an easy edit to perform and will be expedited in the near future..

Silverlight on the other hand a little trickier, as users may be only using a 32 bit compatible browser, and if edited in similar fashion to Shockwave, would not have the option to install the 32bit installer. Only the x64 update being displayed.

Would like to hear you comments and criticisms on the matter before proceeding ahead with the changes.

[DesertJerry]

My preference would be to consolidate the Adobe and Oracle items in one place (previously mentioned years ago - not approved);

Main > Windows Addons
New sub: Adobe
Under Adobe: Adobe AIR, Adobe Flash, Adobe Reader

New sub: Oracle
Under Oracle: Java Runtime

New sub: Microsoft Security
Under Microsoft Security: EMET and Security Essentials

Delete Stand Alone

Silverlight - no preference

[Whatacrock]

I do recall the request for your preference changes to AddOns etc.
Have taken the time and after some consideration, created a mockup of your outlay and after viewing the results am happy to say that this would be a viable proposition. If this meets the approval of other members, it could be implemented as a standard outlay. There were would however considerable editing of not only the apm modules but also the scripts, this would take time, as well some testing..
Comments please....

Here are a couple of screen shots of the mockup

[TheAPGuy]

nitpicking but... one says "Silverlight" and the other says "SilverLight".

[Whatacrock]

That was me when I originally created the apm module and never got round to changing it.... just laziness on my part

[DesertJerry]

Great - I like the changes proposed.

Also, I made this suggestion over at Coomon programs and various OS's.

Suggest renaming APMs in accordance with Adobe's present naming system:

Title=Adobe Flash Player *** for Internet Explorer - ActiveX
Title=Adobe Flash Player *** for Firefox and Netscape Plug-In compatible applications - NPAPI
Title=Adobe Flash Player *** for Opera and Chromium based applications - PPAPI

See here: http://labs.adobe.com/

[Whatacrock]

That is fine and good to have an apm module for the different web browsers, it does create more work keeping each maintained and as I have repeated once before they are just "PLUG-INS". Am currently looking making changes to Flash Player modules similar to what I proposed for shockwave and silverlight but so far am left with the same issue as per Shockwave and silverlight. Any advice would be appreciated in this matter..

UPDATE To research this further, I took the liberty to install Google Chrome in a vm. Investigation shows me that Adobe Flash Player is internally updated when necessary and with this information I do NOT see the need for any additional apm modules to be created. One thing further, if you use the Flash Player Plugin in Google Chrome,it utilizes windows:\System32\Macromed\Flash\NPSWF32_xx_x_x_xxx.dll ..

[Whatacrock]

Refer to http://autopatcher.net/forum/viewtopic. ... 2881#p2881 fopr current changes made.

[DesertJerry]

Update to EMET.APM - minor error.

reads:

[DetectionFile]
FilePath=progfiles:\EMET 5.0
FileName=EMET_GUI.exe
FileVersion=5.1.5426.28434

should read:

[DetectionFile]
FilePath=progfiles:\EMET 5.1 <--
FileName=EMET_GUI.exe
FileVersion=5.1.5426.28434

[Whatacrock]

Thanks DesertJerry --- taken care of and uploaded.