Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

0

AutoPatcher Office 2003/2007 Hotfix Depot

Started by Antonis, Jul 06 2007 06:51 AM

«
Prev

You cannot reply to this topic
Go to first unread post

106 replies to this topic

#101 Cristiano

Super Helpful Guy

Veterans
3,851 posts

Gender:Male
Location:Brazil (Santa Maria - RS)

Posted 11 November 2011 - 11:03 PM

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

Back to top

#102 ViroMan

Just an awesome guy.

Project Manager
1,189 posts

Gender:Male
Location:California, USA, Earth, SOL, Milkyway
Interests:Programming and being a know it all pest.

Posted 12 November 2011 - 03:21 AM

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.

Back to top

#103 _def_x_

audi 5k

Veterans
1,466 posts

Gender:Male

Posted 13 November 2011 - 06:03 PM

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.

Back to top

#104 Black Ghost

AutoPatcher Expert

Members
224 posts

Posted 13 November 2011 - 07:47 PM

dskushwaha, on 11 November 2011 - 02:09 PM, said:

Needed Office 2010 updates

I second that too.

Back to top

#105 dkdk_it

Release Manager God

Release Managers
517 posts

Gender:Male
Location:Italy

Posted 21 November 2011 - 10:59 PM

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.

Back to top

#106 TechDud

Member

Members
11 posts

Gender:Male

Posted 17 April 2012 - 11:57 PM

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