Cheers
Release Maintainer
#1 Guest_Visibleman_*
Posted 15 January 2009 - 07:47 PM
Cheers
#2
Posted 15 January 2009 - 09:06 PM
[]s
#3
Posted 21 January 2009 - 12:49 PM
A Release Maintainer needs to understand the Windows update process, including:
-Checking the Microsoft Security Bulletins
-Where to find updates at the Microsoft Download Center
-How to install standalone updates, without using Windows Update
-Writing the APUP script and associated APM files (which are all human-readable text files)
--
#4
Posted 22 January 2009 - 01:03 AM
James, on Jan 21 2009, 06:49 AM, said:
A Release Maintainer needs to understand the Windows update process, including:
-Checking the Microsoft Security Bulletins
-Where to find updates at the Microsoft Download Center
-How to install standalone updates, without using Windows Update
-Writing the APUP script and associated APM files (which are all human-readable text files)
I have already tried discussing this issue with you and only Christiano and now Antonis have responded.
I am in the position of time to work on the x64 bit platform for the AutoPatcher program and I wish to learn enough about the operation to keep the x64 bit Autopatcher up to date and to add the Tweaks and Add-ons in to the layout for approval.
I am currently studying the documentation and comments/statements from others to understand the layout.
One question; I know that the .apm and .apf files are writen using apps like "Notepad", and the .script files can also, but,
what about the .rti files and are they part of the module updates?? And is that part of the update work??
Thanks
Larry
#5
Posted 22 January 2009 - 01:37 AM
that is the easy part. we run a tool for that. basically, it's just fill the blanks with some infos. at your pms, there's an image of that screen. the main idea about this tool is to be used only after some time. i was able to sign my own release just last year and i'm with autopatcher since long ago
> And is that part of the update work?
the rti files are needed only to check release integrity and be sure that nothing is missing or corrupt. also this tool stores the md5 for each file, if a single file is changed, it will say "unofficial", but that will not prevent you from running nothing
[]s
#6
Posted 22 January 2009 - 11:56 AM
Cristiano, on Jan 21 2009, 07:37 PM, said:
that is the easy part. we run a tool for that. basically, it's just fill the blanks with some infos. at your pms, there's an image of that screen. the main idea about this tool is to be used only after some time. i was able to sign my own release just last year and i'm with autopatcher since long ago
> And is that part of the update work?
the rti files are needed only to check release integrity and be sure that nothing is missing or corrupt. also this tool stores the md5 for each file, if a single file is changed, it will say "unofficial", but that will not prevent you from running nothing
[]s
Thanks Christiano
I am going to be studying the system and get the XPP x64 version ready for you're inspection.
Edited by LarryLaser, 22 January 2009 - 11:57 AM.
#8
Posted 24 January 2009 - 12:52 PM
LarryLaser, on Jan 22 2009, 01:03 AM, said:
I have already tried discussing this issue with you and only Christiano and now Antonis have responded.
Apologies for not responding immediately to your PM, but I was off ill when it arrived and I cannot commit the rest of the AutoPatcher development team without first consulting them.
In the meantime, your offer of help is welcomed.
--
#9
Posted 25 January 2009 - 05:44 AM
#10
Posted 25 January 2009 - 11:32 AM
[]s
#11
Posted 19 March 2009 - 09:52 PM
Edit: Just noticed the pinned message. Silly me.
Edited by René Kabis, 19 March 2009 - 09:56 PM.
2 user(s) are reading this topic
0 members, 2 guests, 0 anonymous users












