AutoPatcher Forum

yep, but there's another issue: the FileVersion detection is partially broken and, for certain files, it doesn't work. this one of the issues that are in our to do list for autopatcher.exe

[]s

I just tried my suggestion using detection on file version and it did not work on this one. Oh well, I guess I'll just copy the CAT file over there. It was not added by the integration because LegitCheckControl.dll is digitally signed and therefore not necessary.
Edited by click-click, 15 November 2009 - 12:55 PM.

 Cristiano, on 15 November 2009 - 11:33 AM, said:

Hi, did you get a chance to take a second look?

sorry. i'm working against the clock. to be honest, i didn't looked any of those fixes. but i'm saving one copy of the enu files into an portable device. i will look at those issues in a few days. sorry, but today is sunday and i'm still working. just now, another client call, thanks to the storms that we are having in here. every day, at least one. and the computers are falling like rain...

[]s

sorry my late, but i'm really working against the clock. for those that are in doubt about the extra rain in here, please take a look for the place that had more rain in the entire globe last month. NASA did the comparison and was in here... by the way: it's raining again...

> KB952069
this one has 2 versions and has detections for booth versions. not updated

> KB958655_xp_x86.apm -> components
updated

> KB968816_xp_x86_enu.apm -> wmp critical
updated

> KB971961_IE8_xp_x86_enu.apm -> msie critical
updated


> KB954155_xp_x86_enu.apm -> wmp critical.
updated

> KB968816_xp_x86_enu.apm - wmp critical.
updated

> KB969878_xp_x86_enu.apm - wmp critical.
updated

[]s

Thanks for the update Cristiano. Everything is looking good. As far as KB952069 goes,
I do not have any reg entries named HKLM\SOFTWARE\Microsoft\Updates\Windows Media Player\KB952069_WM9
on my SP3. I only have HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB952069. I'm not sure why the detection keys you have are not present.

Thanks

> I'm not sure why the detection keys you have are not present
weird. the update creates those keys. KB952069 is present in your system as an integrated update or applied as an regular update? if is integrated, then this may be an issue from the integration process. i will check this update again, but i didn't found that key that you pointed in a first look

[]s

 Cristiano, on 07 December 2009 - 11:34 AM, said:

I think it is an integration problem. I will ask over at the RyanVM forum. I checked the
MS08-076 and the reference table for XP shows your key under Registry Key Verification.

Another detection for an RVM SP3 integrated system

KB943729 replaced by KB974266 (non-public hotfix)
http://support.microsoft.com/kb/974266

Modification tested as follows:

KB943729_x86.apm (Components) added OR detection
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB974266
KeyName=Type
KeyValue=Update

Thanks ....
Edited by click-click, 12 December 2009 - 07:34 PM.

I also cannot get KB909520 to be detected because basecsp.cat was renamed to KB909520.CAT in
the RVM Update Pack. I'm not sure why this was done. For detection to work I did the following:

KB909520_xp_x86_enu.apm (NonCritical) added OR detection
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB909520
KeyName=Type
KeyValue=Update

The rest looks very good and I can say that AP is pretty much compatible with RVM

Thanks ...

ok. those changes will be done later today

[]s

> basecsp.cat was renamed to KB909520.CAT in the RVM Update Pack
strange. KB909520.CAT doesn't exist inside KB909520, only basecsp.cat. even more, KB909520 can't be found at HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4 only at SP1. i believe that they did this by mistake

about RVM, the idea is nice. i'm unsure so far why they didn't received the same nasty letter from ms that we once received or if they received, they are just ignoring it. due that, we lost a lot of users, a lot of good people that was helping us keep the releases up-to-date, etc. due that letter, we had to rebuild everything in a way that is too painful to keep and an problem to the users that see every single update than we do as an problem. but ok, they are an service pretty similar than our own.

those modules was booth updated, despite i think that they did an mistake with KB909520 (unless they are talking about an non-public version about this update)

[]s

Well it looks like Microsoft managed another Timezone hotfix for the new year and not detected.

KB976098 replaced by KB977748 (non-public hotfix)
http://support.microsoft.com/kb/977748

Modification tested as follows:
KB976098_xp_sp3_x86_enu.apm (Critical) added OR detection
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB977748
KeyName=Type
KeyValue=Update

Thanks ....

ok. that will be fixed tomorrow

[]s

done. compatibility added

[]s

Sorry to bother.... Microsoft has come out with another hotix for Timezone and one for RPC/HTTP Authentication.

KB976098 replaced by KB977748 (non-public hotfix) replaced by KB978125 (non-public hotix)
http://support.micro...p/dst_hottopics

Modification tested as follows:
KB976098_xp_sp3_x86_enu.apm (Critical) changed previous OR detection
from
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB977748
to
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB978125



KB970238 replaced by KB974841 (non-public hotfix)
http://support.microsoft.com/kb/974841 (RPC/HTTP Authentication)

Modification tested as follows:
KB970238_xp_x86_enu.apm (Critical) added OR detection
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB974841-v2
KeyName=Type
KeyValue=Update

Ciao
Edited by click-click, 26 January 2010 - 04:35 PM.

isn't a problem. in fact, an report that makes the scripts better are good for all. for sure, not everybody runs non-public updates, but those that run surely likes the job that you are doing

enu script updated

[]s

AP error after the last update:

UNOFFICIAL: File 'Z:\Autopatcher\modules\Critical\KB970238_xp_x86_enu.apm' (mentioned by RTI 'C:\#AutoPatcher_Temp#\xp_sp3_enu.rti') size mismatch!

Ciao
Edited by click-click, 26 January 2010 - 11:46 PM.

weird. the file names are as should be. i'm at my girlfriend home right now, so i will download the whole package to see what is wrong and fix it

thanks

[]s

my friend, i may require your help to track this issue. i've just finished an clean download from the xp enu script, plus ap engine. no issue at all, not even an wrong check for sizes. i've also checked the md5 file and all files match. it may be related to an obsolete file forgot in some place, i don't know. but from here, i don't see nothing wrong. even if i run autopatcher, the script still looks as official, for booth xp enu and autopatcher engine

[]s