AutoPatcher Forum

Office adddon pack and Addon pack for office 2007 are not working.They seem to get installed but after restart it again gets back to original state i.e. not getting installed.Hope you guyz understand my problem

So you're saying the detections are broken. I'm sure one of thee team will take a look soon.

domenico probably will. but right now, he is adapting/checking the scripts for seven compatibility. he will be warned, and will fix this, don't worry

[]s

 Dibakar, on 11 February 2010 - 11:36 PM, said:

Hello Dibakar,
can you send/post me a list of broken updates Or an AutoPatcher screenshoot?!?

Thanks.

New updates for Office 2003

Security Update for Microsoft Office 2003 (KB982311)
Security Update for Microsoft Office Excel 2003 (K8982133)
Security Update For Microsoft Office InfoPath 2003 (KB980923)
Security Update for Microsoft Office PowerPoint 2003 (KB982157)
Security Update For Microsoft Office Publisher 2003 (KB982122)
Security Update For Microsoft Office Word 2003 (KB982134)
Security Update for the 2007 Microsoft Office System (KB982312)
Security Update for the 2007 Microsoft Office System (KB982331)
Update For Microsoft Office Outlook 2003 Junk Email Filter (KB983503)

(I apologize for insisting on Office 2003 but the damn Ribbon just doesn't work for me...)
Edited by Pedro, 17 June 2010 - 05:08 PM.

 Pedro, on 17 June 2010 - 04:13 PM, said:

I'm not a big fan of that Ribbon either Pedro. If you're stuck using Office 2007, I've found UbitMenu very handy to bring that old Office 2003 menu back to Office 2007/2010. Best of all, it's free for private use.
Edited by dfdff3000, 21 June 2010 - 09:41 PM.

Currently the updater reads "AutoPatcher Office 2007 SP2", shouldn't it read "AutoPatcher for Office 2007 SP2"???, since its not the addon pack???

Be aware that some of those maintaining and updating suff around here do not speak English as their primary language and many listings/items you see reflect translation attempts that may seem a bit odd.

true. but there's one fact: doesn't matter if there's translation problems, if the job is done. antonis, is greek and was one of the founders. he also runs linux and did an project to update windows. blaze? he is american, as Frank, Joe and Erik. Domenico? italian. James? it's from UK. Antony? russian me? Brazil. fact: the ones that are updating the scripts right now may have translation issues, but we are doing an job for free. if someone points the issues, then an fix can be done, just that

[]s

your right and i failed to take that into consideration

there is over a month since Pedro posted about new updates for Office 2003.
since I am a big fan of Office 2003 too, for not being too overbloated, I am asking myself if those updates were incorporated...

do you wanna an honest answer? i don't know. this script was updated by Michael Bonwick last time and i don't see him in a long time. i don't have office 2003. i do have now an localized version of office 2007 and when ms honor his word, then office 2010 too. but so far, no luck. without have the main thing, is possible update an script, but the detections become an nightmare. honestly, i will not do that. if someone wishes help the community and do the proper changes in the script, i can put that online, but just that

thanks for your understanding

[]s

oookkeeeyyy

so Michael wasn't online since February 2010 or so.


what if he has not time anymore for this project ? or worse ! like he got married

so anyway... do I have to presume that nobody else can't push forward this project ?

Quote

That's always the $100 question, in many cases the volunteer vanishes without a given reason and all you can do is say thank you for helping out.

AutoPatcher has always been a volunteer effort and unless someone steps up to the plate this particular script will be put on hold - or canned altogether.

Office is probably the toughest script to get right, AutoPatcher for Office scripts needs a volunteer with the software and a good deal of know-how, so the answer is likely the script will remain dorment.

My only criticism is I wish (and believe it is fair) that when a volunteer steps forward they are clear about their time. This is an example, the word gets out about a revived script, people get their hopes up, and then the AutoPatcher team have to try and explain what's going on. You can search the forum and you will find many offers of help, a regular forum member takes the time to explain how to do something, and the new member that offered the help simply disappears - you get used to this after a few times, and come to expect it.

well, what to say, if you can forward me to some new guide you were making then maybe i can read it and decide if i will be able to do it, i will do office since that the area lacking, i came looking for office there no 2007 sp2 eng and nothing of 2010.

Quote

There is an Office 2007 SP2 release - see APUP selections windows. AutoPatcher needs to be updated to detect Office 2010 I believe before a release can be done.

Also, Here! is the only documentation available, its getting outdated but still may help, use an existing release for guidance as well, look at the Office script and open the .apm files in notepad to get an idea of how things work.

I'd like to see Office 2000 support returned to Autopatcher. WSUS Offline just removed support for it from their latest release. Since nothing new has been released by MS for O2K in ages, the script wouldn't need updating beyond making sure it downloads everything available for that version.

> Since nothing new has been released by MS for O2K in ages
half true. ms just isn't stating that the updates works for 2k anymore. do you wanna an sample? .net 2 sp2. but there's more...

[]s

office 2007 has reached sp3 level yesterday. more infos about can be reached here

[]s

Needed Office 2010 updates