AutoPatcher XP x86 Hotfix Depot
Posted 15 February 2011 - 09:59 AM
you will get:
at this point, nothing is useful. you have to extract the content of Windows6.1-KB975560-x86.cab, that will have a dozen of .cat files. from those, you have to pick the right one. one problem: there's a few with an similar name, like:
the current version of the module for this one asks for Package_for_KB975560~31bf3856ad364e35~x86~~184.108.40.206.cat that isn't present... i can't be sure if the detection for this one works from here, but if it is, the .cat file without that _bf is renamed
so, to make the job more easy, try 7zip with the .msu files
Posted 15 February 2011 - 01:28 PM
The reason I ask is that the registry detection being used for IE has changed from the previous detection method and KB2482017 is being flagged as not installed for IE8 on my system even though it is installed.
I changed IE8-WindowsXP-KB2482017-x86-ENU.apm RegistryPath=
from HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB2482017-IE8\Filelist <----- does not work
to HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB2482017-IE8 <----- this works
Previous detection did not use Filelist for IE7 or IE8. Can this be changed so I can get back my official status on AP?
Edited by click-click, 15 February 2011 - 01:39 PM.
Posted 15 February 2011 - 10:47 PM
Just a side note but it's worth mentioning. The project is essentially dead, the forums are a ghost town, so you should get used to maintaining your release with what will be the perpetual Unofficial Warning Status nag screen - if you want to continue using AutoPatcher with future updates. In fact I'm not sure AutoPatcher will be as accurate once SP1 for Windows 7 is mainstream, and may be best used with XP, Vista, and Windows 7 without a service pack.
You seem to know quite a bit about how things are done, you can edit apm files, I figure you could have maintained a script had you wanted to so I would get used to having a so-called Unofficial release, one that you have created - now may be as good a time as any Edit the .apm files so they work for you, get rid of the .rti file as well. I never bother signing a release for my own use just to update a friends system, if I created the contents and I know they work signing is more effort simply to avoid looking at an interface I see for a moment anyway - and it doesn't affect AutoPatcher's ability to install an update. I do create a .md5 file for all the contents - this is a must.
I figure once Frank knows I can reach the ftp he will put a stop to it, it's only a matter of time before we're all gone for good. The forums are pretty depressing anyway, nobody logs in, if they do it is to complain, the wonderful pornographic spam hangin' around - gets old fast. I looked at a number of my last posts - few follow-up with even a kiss my butt, it makes you feel it's all a waste of time.
Posted 15 February 2011 - 11:08 PM
Posted 15 February 2011 - 11:31 PM
What I want to figure out is why the \Filelist is giving problems with only IE8 and not the rest of the updates, there were 9 or so total this month. Maybe it is something else causing problems. Again I will fix it as soon as I get the Extras Silverlight squared away - I would install it but I don't want it on my system.
Posted 16 February 2011 - 12:39 AM
at my job, i have an 100MB IC. so, everything is downloaded asap . but one tip: the modules us to be basically the same every month. so, the fastest way to do it is taking an previews one as template. take WindowsXP-KB2360937-x86-ENU.exe as an sample. forget the .exe part and replace it by .apm. opening it, just replace all the KB2360937 by the new kb number (like KB2443105). if you wish do the things even faster, forget about the FileMD5= part of the file detection and leave it as FileMD5=ANY. it works like this for seven and vista, so... if you wish do the modules for more languages, all that you have to do is replace ENU by PTB, ITA, etc and then change SystemLanguage by the target language. of course, it helps if you have free time (and as i'm working with government bidding since last year, there's days with a lot of work and days without nothing to do... the problem: it's vacations time, so i'm taking extra work load with contracts, etc...)
> have a look at the rti and md5 section - yes, no?
it's more easy to do, in fact. but as very often i did mistakes, it was more simple to fix one at a time
Posted 16 February 2011 - 02:57 AM
Posted 16 February 2011 - 03:56 AM
Cristiano, any ideas? I've made a note to remove them but why are they breaking things at click-click's end, for me they have worked on 3 systems now - and I'm puzzled. In fact, for the 4 or so months with Windows 2000 I used them and don't recall anyone saying a detection was failing because of \Filelist in the path and again, they always worked for me which is why I kept using them, it was listed as part of the Registry Verification string.
If anyone else is having this exact problem please say so.
Posted 16 February 2011 - 09:55 AM
i'm not sure. i guess that something may change when deploying the update or it is related to system variables. but i will take a look on it later. now, i have to fix 1 week work of my boss...
oh yes, i can't edit post #566 anymore. so, instead "just replace all the KB2360937 by the new kb number (like KB2443105)" read it like this: "just replace all the 2360937 by the new kb number (like 2443105)". without the kb, an simple replace will fix the more info link as well
Posted 16 February 2011 - 12:03 PM
I always keep a previous version of APUP as a backup and also, to see what has changed between each patch Tuesday. None of the reg detections in the previous APUP .apm files used /filelist and they all end with /KBxxxxxx. I assume the other /filelist detections worked because the .CAT files matched. I don't think any of the /filelist detections would work on my system if the CAT detections were removed.
Also, the /filelist entries on my system all end with a number from 0-10. I.e /filelist/0, /filelist/10
Thanks for taking the time .....
p.s. I just ran a test with KB2393802 by removing file detection and the reg detection fails here with /filelist, but okay without it.
Edited by click-click, 16 February 2011 - 12:58 PM.
Posted 16 February 2011 - 02:32 PM
The issue is not with \Filelist, I'll explain, but why didn't the last IE8 cumulative update fail, it wasn't renamed in the apm? I'm wondering if you have a hacked XP, 'tiny' or 'nLited' to death, this is making less sense as I look into it.
First, I will admit I'm not an expert here and I don't have the ability to see every single person's system, and I can only go by what I have access to - all 3 systems have a registry \FileList for 99% of every update isnstalled, there are maybe 5 out of more than 100 updates that don't need it, usually because the update was a registry edit and no files were updated. These categories may vary system by system but an update as important as the IE8 cumulative should have many entries under \FileList, I have 38 - that's \FileList\0 - \FileList\37.
>>>I just ran a test with KB2393802 by removing file detection and the reg detection fails here with /filelist,
It shouldn't fail with it as far as I can see, this update as well, replaced files, the locations, filenames, etc are listed under these subcategories. Now, if I put \FileList\10 and it didn't exist, this may fail but, \FileList simply means there is additional info regarding this update that lies beyond the path. On my system I have 18 subcategories beyond \FileList for this update that contains critical information... here's just two entries...
\FileList\0 - FileName (ntoskrnl.exe), Location (C:\Windows\system32)
\FileList\11 - FileName (ntdll.dll), Location (C:\Windows\system32\DllCache)
Like I said there are 16 more subcategories for me, you're saying you have zero registry info listed for this update beyond \KB2393802???
It probably is a good idea to simply leave off \FileList because it isn't needed but if an update overwrites or updates files, as well, there is the qfe reference, hidden uninstaller and so on, all this info is listed beyond \KBxxxxxx, and as far as I can tell is found beyond \FileList.
I'm still scratching my head as to why you say the IE8 cumulative update dropped the IE8 part, compatability with 8.3???
Btw, I do believe you I just don't know why your cat files are being renamed and you have no info beyond the \KBxxxxxx entry. In fact, I will get a screenshot of my regsitry entry for the IE8 cumulative update and you can see the subcategories drop way down the screen - can you get me one of yours as well so at least I can see what your seeing?
Good, I had time to edit - here's a screenshot of the updates we talked about and \Filelist in the registry - updates.jpg
Edited by gUiTaR_mIkE, 16 February 2011 - 03:20 PM.
Posted 16 February 2011 - 04:57 PM
I must add that the system I have was created with RyanVM Integrator using XP+SP3 +UpdatePack +Addons (IE8,WMP11, etc.). Every so often, I would find things not being detected by AP because I had hotfixes that had replaced the fixes AP detected. Cristiano was kind enough to add those hotfix detections for me so that AP was pretty much compatible with a system integrated with RVM. No hotfixes this time though, just business as usual.
Posted 16 February 2011 - 05:14 PM
The last IE8 cumulative update apm file did not use /filelist, so it did not matter if the file detection (renamed cat) failed because reg detection was successful finding the Type=Update entry. If you use /filelist, AP will not find any Type=Update entries in that subcategory on my system - only on the KBxxxxxx level.
If you are really sure filelist works for you, try removing the file detection section in one of you apm files and see if it still detects the fix only using /filelist reg detection.
Edited by click-click, 16 February 2011 - 05:36 PM.
Posted 16 February 2011 - 10:53 PM
Anyway, I'm geting a cold I think so I will deal with this later - you know whats going on. Btw, good catch
Posted 16 February 2011 - 11:59 PM
Edited by click-click, 17 February 2011 - 12:07 AM.
Posted 18 February 2011 - 06:22 AM
Please run APUP and update the release. Thanks for the feedback, much appreciated.
Posted 18 February 2011 - 10:33 PM
Edited by click-click, 18 February 2011 - 10:42 PM.
Posted 17 March 2011 - 08:51 PM
Remote Desktop Client 5 is old so the update was left out, if you want the update here is the bulletin information:
... MS11-017 /// WindowsXP-KB2483618-x86-ENU.exe
If you have Remote Desktop Client 6 or 7, please report any issues with the updates.
Media Center is not directly supported so an update was left out that targeted MCE2005 only, if you want the update here is the bulletin information:
... MS11-015 /// WindowsXPMediaCenter2005-KB2502898-ENU.exe
As always, please report any issues in the Windows XP SP3 (x86) Forum
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users