29 replies to this topic

[Cristiano]

i may check those modules, but the older modules are also they already was. also you should be aware of, i always report every single change into the scripts into the very begin of the log, like this one:
# 2009-05-05: +KB923561; +KB952004; +KB956572; +KB959426; +KB960803; +KB961373; +KB963027_IE7; +KB963027; +KB909520; +KB968220_ie8; +IE8; -KB951698; -KB956841; -KB960714; -KB961260; ~kb890830

except for KB909520, that was added this month despite be on WU since last month and be an update for xp since sp1, the other ones was in the script long ago. just to let you know how the process works, i've downloaded the old .7z file that james did. you also can download that obsolete file from here. that file is untouched at our servers. you can compare the md5 for the files, if you wish. it will be the exact same one. so, it can be an issue from your side, an issue that was in there since some time ago and it may also be an new version for this one released with the very same name (and ms does that from times to times. and yes, sometimes, they change the detection)

anyway, you can check the detection for this one by yourself, downloading this file and extracting it by running this command:
Windows-KB909520-v1.000-x86-ENU.exe /x

then, select one folder to the extracted files. can be anyplace, since you can reach it easily. then, look for the basecsp.cat, that is the .cat file for this one. then, take the md5 for that file: bbbc61614fe770768647ec026fe1181c . now, open KB909520_xp_x86_enu.apm file with notepad. you will find 2 possible detections for this one. the first one is an registry detection (that i believe that you can find by following the patch in regedit)

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP1\KB909520
KeyName=Type
KeyValue=Update

ok, registry detections aren't fully reliable, but you also have the .cat detection, that is this one:

[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=basecsp.cat
FileVersion=ANY
FileMD5=bbbc61614fe770768647ec026fe1181c

if you find any detection that doesn't match, please let me know it, because this one was released by request by ms by several years. if there's more detections for other possible versions of this one, we need to know to think about another kind of detection

[offtopic]
> detection problems or........
about this part, i'm inclined to think that you are, again, trying to shoot someone by any reason, like you did in your last BAN. if you wish another one, in a more permanent way, please let me know it that i may give you an special hammer that we have for trolls:


i'm just showing you this because your last BAN was just to let you think about your behavior. for the next one, you will be unable even to download anything from here. so please, no sarcasm or false accusations in here again.

i hope that this last subject was clear enough[/offtopic]

edit: and, by the way, i've checked the KB952069 v2. the module has the following detections:

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows Media Player\KB952069_WM9
KeyName=DisplayVersion
KeyValue=1

RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows Media Player\KB952069_WM9
KeyName=DisplayVersion
KeyValue=2

[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=kb952069.cat
FileVersion=ANY
FileMD5=2bd8570d4fef8a2a62678f91c02ed527

if i'm not mistaken, james had to remove the other .cat detection for this one. we have the following issue: for the registry detections, one or another works. for the md5 detections, it has to be this one and this another one, making impossible to you have 2 different md5 for the very same file. but this kb has 2 versions, that are the same except by the .cat file. so, you can't have the v1 detection for the .cat file, because the ones that download the new one will see it also non-installed. by the other hand, those that have the v1 for this kb will see it also non-installed, because the module will look for the md5 for the v2 file, that aren't the same. so please, check your system. you probably will see that you have v1 installed instead v2

[]s

[Pedro]

Cristiano, thank you for the updates, even though you don't use the English version!

I think that maxsisac wasn't being rude. I believe there is a communication problem because our native language is not English

Peace!

Obrigado! Um abraço!

[Cristiano]

pedro, please read again the last sentence. see, i didn't born speaking english. in fact, the best english lessons that i had in my life was from some k7s that london bbc once sell (and it was about 20 years ago) and, after that, just movies, magazines, songs, etc. i do not speak an good english, i know, but in any language, the last sentence says the exact same thing. but that is and dead subject. just please, no more sarcasm, implicit false accusations, this kind of thing. i don't know about of yours age, but i'm 33 years old and if there's an thing that i really don't like is those things. this is an forum, not an arena.

[]s

[Mihai]

Guys, I have a big respect for sharing us your great piece of work. Even if I was waiting sometimes for new releases (sometimes I double checked daily) I never asked or stressed you for them as you should be forced to do it quickly. We never had to pay for your work so we cannot have any pretensions, only many thanks for what are you doing.
I am sad watching you fight instead of being friendly and cooperative, as you used to be. Please, leave behind the anger and nervousness and try to ignore almost all rude comments.

Cristiano, you are great! Your post about Everybody, Somebody, Anybody, and Nobody it's really impressive, I liked it a lot.

My English is not as I would like it to be, but I assure you guys about my best wishes!

Thank you's to all of you.

[Cristiano]

Mihai, that text is not mine. it's just an old story that once someone told me and it applies with the situation that we are facing in here. in fact, it's an great text. i just don't know who wrote that first.

[]s

[Cristiano]

KB909520 was replaced today, by KB969497, released at May 07. so please, update your script

> ModuleFolder, can autopatcher really install patches without that
yes. there's 2 options for autopatcher.exe run. one is implicit and another one is explicit. it's implicit if the module name has the same name than the folder name has plus _files. it is explicit if the folder for the module has any other name. then, inside the module, an command telling to the module look for the target folder in another place. sometimes, when you are doing the script, you may left an wrong letter. in that case, enu isn't the same than ENU. for this one, this is the module name:
KB968220_ie8_xp_x86_enu.apm

and this is the folder name:
KB968220_ie8_xp_x86_enu.apm_files

matching booth:
KB968220_ie8_xp_x86_enu.apm
KB968220_ie8_xp_x86_enu.apm_files

it seems the exact thing than should be. so, please, the next time that this happen, please look into windows folder, by an file named autopatcher.log. every single issue related to that is showed in there, with the answer. anyway, i've found 3 wrong removals. it's fixed now. just please run apup again in order to fix the issue

[]s