←  AutoPatcher for Microsoft Office XP / 2003 / 2007

AutoPatcher Forum

»

AutoPatcher Office 2003/2007 Hotfix Depot

Cristiano's Photo Cristiano 11 Nov 2011

there's no point in that, if the software is unable to read the detections. apup2 has several detections built-in, but the detections will be moved for an external file, to allow more detections. but this is an slow process and autopatcher.exe must be able to read that. right now, it's being developed apup2, to fix the several bugs that apup has and and an script maker, to make the live of releasers managers more easy. after that, maybe something else, but there's things that have more priorities than others

[]s
Quote

ViroMan's Photo ViroMan 12 Nov 2011

Basically what Cristiano said. The detections for the current offices are hard coded into the old code. I have updated the way apup2 will detect things but, I still have to create a way to read in detections. So it will read in another script that defines detections and then continue loading other scripts. I have set that issue aside for now since im still getting the download DLL finished. It has taken me a long time to get that right but, its nearing finish finally. Only some minor cosmetic things to fix before test release. I will work on getting external detections after I get reports from the testing and fix any bugs. Even after I get the detection moved out... autopatcher has its detections hard coded too. I will have to start the laborious process of converting that VB to c++ as well. So in conclusion its out of our hands to create a script for office at the moment... rather you can make one if you want.. but, autopatcher won't accept it yet.
Quote

_def_x_'s Photo _def_x_ 13 Nov 2011

ViroMan said:

So in conclusion its out of our hands to create a script for office at the moment... rather you can make one if you want.. but, autopatcher won't accept it yet.

This is a good idea, get a jump on the script - the bugs can be worked out later.

Here's a script template... add sections (edit) as needed.
Spoiler

Here's an apm template, edit as needed.
Spoiler

With the help of an existing release (script) used as reference, you can grab one from the Releases List , and the AP Docs , a good amount of progress could be made.
Quote

Black Ghost's Photo Black Ghost 13 Nov 2011

View Postdskushwaha, on 11 November 2011 - 02:09 PM, said:

Needed Office 2010 updates

I second that too.
Quote

dkdk_it's Photo dkdk_it 21 Nov 2011

New script for Office 2007 SP3.
This release "clean" the old SP2 release... so, if you want to keep old update, please don't mix SP2 and SP3 releases.

Tomorrow (I hope), new script "SP2 Addon Pack for Office 2007" (ENU).

Bye.
Quote

TechDud's Photo TechDud 17 Apr 2012

Updates for the ActiveX control MSCOMCTL.OCX (v6.01.9833) in Office 2003 SP3, Office 2007 SP2/SP3 & Office 2010 incl. 2k10 SP1
to resolve "Vulnerability in Windows Common Controls Could Allow Remote Code Execution (2664258)"
http://technet.micro...lletin/ms12-027
Quote

dkdk_it's Photo dkdk_it 19 Apr 2012

I'll update the script tonight... see you later.
Quote