> I wonder if OpenOffice will work
it will. the first time that i've did that i only had openoffice (in my case, broffice, because someone has openoffice as tm in here). so, let's try it:
- first, it's far more easy do it if you don't do that straight from modules folder. it will work anyway, but then you will not have an template good enough. then, just open an cmd window. as an test, i've tested an comparison between xp ptb and enu. so, first go to critical folder, then run something like dir /b /a-d *.apm >list.txt if you wish get an list from the subfolders too, then add /s into the command. the /a-d will make you loose the folders, making your comparison far more clean
- after that command, you will have at critical (or the folder that you are scanning) an file named list.txt. you will have something like this:
do you wanna clean it even more? open that file into notepad and replace all -x86-PTB.apm or anything else that you don't wanna by nothing. this will remove the undesired data, leaving just the kb number, like this:
now, select everything and paste it into openoffice calc. now, repeat the same process into the same folder into the target, but paste the results in another column (eg: B ). if you wish, sort the columns by name (it will help a lot).
now, compare the columns. the kb numbers that was suppose to exist must match. let's suppose that at A2 you have KB2079403 and at B2 you have KB2079404. the columns don't match, right? but take a look, between booth, you have KB890830 and KB2115168. what was supposed to be between them? now, you know that there's an kb missing. so, now select everything else in that column and move it to the line where the kb numbers match side by side again. the empty spaces are now the missing ones and you already know the ones that have become obsolete
also, an tip: the registry detection is common to all languages and the only one change will be at the file detection. if you wish, you can extract the content of the kb and fill FileMD5, but if you think that check for the presence of the file is enough, then FileMD5=ANY is good enough. the problem: sometimes, the .cat file changes between the versions of the same kb. if you don't have the md5, you will detect the new version and the old version as the same
> apup.exe v1301 to run locally and be visible
no. it only worked in remote mode, hosted into an site, with an command similar to this one: apup.exe /log /listfile:http://www.autopatcher.com
i will ask antony if there's an hidden command that i'm not aware of
Edited by Cristiano, 15 September 2010 - 08:31 PM.