No replies to this topic

[BlackholeForever]

The "Critical" flag in the [Behavior] section of .APM files appears to drive default (Ctrl-R) selection in AutoPatcher.

I've noticed a side effect between this flag and the "Depends" flag amongst related patches. If the following occurs:

PATCH1.APM
------------
[Behavior]
UniqueID=PATCH1

PATCH2.APM
------------
[Behavior]
UniqueID=PATCH2
Critical=True
Depends=PATCH1

Then, I cannot unselect PATCH1 for installation, regardless if PATCH2 is unselected. Under these conditions, PATCH1 becomes "hard-coded" for install (note: Critical flag for PATCH1.APM can be True or False).

Is this the expected result? I'm just curious...


p.s. - This occurs on a fresh install of Windows 2000 SP4 with the following:

• MDAC_2_8_SP1_ENU (aka Microsoft Data Access Components 2.8 SP1)
  
• MSXML_2_6_ENU (aka Microsoft XML Parser (MSXML) 2.6 (KB823490))

Neither can be unselected for install.