Adobe Flash Mod Addons for XPx64 Update Pack

[5eraph]

Adobe Flash Mod Addons for the Windows XP x64 Update Pack

Purpose:

• These addons change the default installation behavior for the 64-bit ActiveX version of Adobe Flash Player included with the Windows XP x64 post-SP2 update pack.

Details:

• Addons require update pack v2012-06_1 or later.
• All addons tested with pack v2012-06_1, installed in VirtualBox, to ensure proper functionality.
• Integrate with RyanVM Integrator 1.6 or nLite 1.4.9.1. *See Notes section below.

Credits:

• ricktendo64

Downloads:

• Enable Auto-Update
  GUI: "Install updates automatically when available"
  Note: This is the default setting in the update pack.
• Link: FlashAddon_SetEnable_x64.7z
  Size: 480 B
  MD5: df767c17d280c46bf039dd7206f45fb1
  
  Notify Auto-Update
  GUI: "Notify me when updates are available"
• Link: FlashAddon_SetNotify_x64.7z
  Size: 478 B
  MD5: 9ceff1dfd223aa3827f2b1ea87d324c0
  
  Disable Auto-Update
  GUI: "Never check for updates"
• Link: FlashAddon_SetDisable_x64.7z
  Size: 484 B
  MD5: cee834620f4f5565bc43318c40356d49
  
  Remove Auto-Update
  Note: Removes the scheduled task, EXE and service responsible for the updater.
• Link: FlashAddon_DeleteAuto_x64.7z
  Size: 470 B
  MD5: 3ed84dac357b414a5711f931532dc0de

Notes:

• All of these addons modify the 5erUpPck.inf file in the update pack to achieve the intended result. The Auto-Update addons are meant to counteract each other, should you change your mind after integration.
  
  It should be common practice to use nLite only once on any given source to prevent inconsistencies caused by multiple nLite sessions—in other words: do all addons, drivers, unattended settings, removals and tweaks in a single nLite session. In this case the RyanVM Integrator can be used to apply a different Auto-Update addon to an nLited source as desired without adverse effects.

Changelog:

• [2012/06/13 04:55 UTC] - v2012-06_1 - Updated to work with new OCX registration technique. The No64Bit addon is no longer supported because Adobe merged the 32-bit and 64-bit installers.
  
  [2012/04/17 21:45 UTC] - v2012-04_2 - Initial release.

[Passion]

in other words: do all addons, drivers, unattended settings, removals and tweaks in a single nLite session. In this case the RyanVM Integrator can be used to apply a different Auto-Update addon to an nLited source as desired without adverse effects.

Hmm.. this gives the impression RVMI should be used on an already nLited image, while my experience is I get the best results by starting with RVMI and then using nLite.
(If I'm correct, this is what you told me to do, long ago, when I ran into some issues/erratic behavior with the resulting image and adding Windows Mediaplayer+updates.)

[5eraph]

It depends on what you're using RVMi to do. RVMi can be used before and after nLite, as many times as necessary, because it is simpler. nLite can make too many complicated changes to the source for me to be confident that it can track them all over multiple sessions, and I'm not alone in thinking this.