32 replies to this topic

[sh1leshk4]

The SP3 blocks some file formats by default; more details here.

Of course, some of those formats are already obsolete, but should AP provide a separate add-on to change the registry to re-enable those formats?
Doesn't have to be all of the blocked formats, though; just what most people'd want.

[Pedro]

That would be a good addition. I still have some wks files around I might need to use some day...

[James]

I agree - kb938810 looks like the basis for some optional registry tweaks for Office 2003.

I certainly don't want these implemented by default. In fact, on those systems we have with Office 2003 installed, we have already tightened up file opening in Word from the default, by changing the FilesBeforeVersion value from the default (=101) to 217 - which now disallows anything before Office 2000.

Like Pedro, we also have some old .wks files we need to read.
--
James

Edited by James, 05 January 2008 - 11:57 AM.

[Pedro]

Some recent updates needed for Office 2003 since SP3

Security Update for Microsoft Office Publisher 2003 (KB946254)
Securty Update for Microsoft Office Word 2003 (KB943983)
Security Update for Microsoft Works Suite 2005 (KB943973)
Security Update for Office 2003 (K6945185)
Update for Office 2003 (KB907417)
Update for Outlook 2003 (KB943649)
Update for Outlook Junk Email Filter 2003 (KB944941)

(I have no idea why the Works Suite 2005 shows up, but Microsoft should know )

[Erik Ramey]

Yup.. working on this one <gotta get away from the gamming.. bad me bad me>

[Pedro]

Stop punishing yourself, Dobby

Thanks for the great work, Erik!

Edited by Pedro, 18 February 2008 - 02:33 PM.

[Pedro]

Thanks for the updates, Erik!

BTW, KB912440 has no Description other than English. Could you fix that, please?
Thanks!

[Erik Ramey]

@Pedro - MS only translates KB912440 to Chinese, Japanese, and Korean, which the only lanuages I know is English and bad English. If you could provide me with a translation, I would be happy to push it for ya?

[Pedro]

@Erik

Apparently I can just edit the apm file and add a Title_2070= and a Descripton_2070=
But when I do a apup, all the edited files are overwritten by the originals

For item KB912440 can you please add
Title_2070=Actualização para introdução complementar do Office 2003 (KB912440)
Description_2070=A actualização para Office Introdução complementar (KB912440) 2003 actualiza a estrutura que é utilizada para suportar serviços de texto avançados no Microsoft Office 2003.

After browsing the files one by one I found some of Portuguese Titles and Descriptions missing. But the one I was looking for is KB943649 which doesn't have a Title at all so it showed up on the list just as a check-box but I couldn't see a Title or Description...
Here it is:

Title_2070=Actualização para o Outlook 2003 (KB943649)
Description_2070=Esta actualização ajuda os utilizadores a configurar o Microsoft Office Outlook 2003 para que funcione correctamente com o Windows Live Mail.


Thank you again!

(I wish Antonis would fix the language bug...)

Edited by Pedro, 26 February 2008 - 12:10 AM.

[Erik Ramey]

Thanks for the translations Pedro. I updated both modules for Office 2k3.

Also a quick note: KB912440 was my fault. I left the translation blank which I should have omitted the "Title_2070=" from the module.

[Pedro]

Thank you for adding the March updates to 2k3.

However, Autopatcher doesn't recognize that the updates have been installed. If I tick 945185, 943983, 907417 and 946975 and install them, after a reboot, running AP still shows this updates as not installed (black). I suppose the same might apply to the other patches but I don't need them. Currently the only update showing in blue is SP3.

I hope you can fix this

Thanks again!

BTW any news on Renato? Did he abandon the project?

[Erik Ramey]

When was the last time you ran APUP to update Office '03. I made some detections updates to these modules the other day which it should have fixed it. Try updating them one more time and tell me if they are good.

About Renato, I haven't heard from him either.

[Pedro]

I ran apup today. So I guess it's not fixed... Sorry!

Could it be because of the date of the apm files? They are uncorrectly dated from 3rd of November and 3rd of December instead of 11 and 12th of March...

[Erik Ramey]

The date is a bug with APUP. 3/11 is being seen as 11/3 etc after the 13th, the bug goes away.

I'm behind a proxy and sometimes I don't see content updated until a couple days after I update. From your AP directory go "modules\office2003" and open KB943983_enu.apm in notepad.

This is what you are looking for:
RegistryPath=HKLM\SOFTWARE\Classes\Installer\Patches\3DC50BAEE72B76844A4DB2658F66C653\SourceList
KeyName=PackageName
KeyValue=

If KeyValue is blank, you are still seeing the old version *hate the proxy that I'm behind*

[Pedro]

KeyValue=WINWORD.msp

(I told you I updated today)

Ok. So if it's not a date thing then some verification is failing....

[Erik Ramey]

I was going on the assumption that you were behind a proxy via your ISP.

Don't understand why the detections aren't being detected. MSP files will always register themselves at HKLM\SOFTWARE\Classes\Installer\Patches. Additionally some files detections have been implemented as a backup. I can then only go under the assumption that these updates don't apply to your setup or there's an installation error when installing.

First thing we need to find out is if these updates were actually installed or not. Since the updates are installed silently, no errors are displayed. Go to your Add/Remove programs and make sure that "Show Updates" is checked. Look for the KB's under your Office installation. If you don't see them installed, go to modules\office2003\KBXXXXXX_enu.apm_files and try to install the update manually. If this produces an error, let me know. IF the KB's are in fact installed, we will then need to check the detections next. Also what Office suite are you running? Office 2003 Professional with Frontpage, Office Professional 2003, Office Basic, etc.

[Pedro]

Unfortunately my Windows install is too messed up to understand if this is a AP error or a registry error. Once I get things fixed I will let you know.

Edited by Pedro, 21 March 2008 - 10:30 AM.

[Pedro]

1) I can confirm that KB907417 shows in the installed updates in Control Panel but AP stills shows the update in black, i.e. as not installed.

2) I can also confirm that

Security Update for Microsoft Office 2003 (KB947355)
Security Update for Microsoft Excel 2003 (KB943985) v2
Security Update for the 2007 Microsoft Office System (KB947801)

are not showing in the AP update list. The KB943985 exe and apm were downloaded an the office2003 apm updated but it doesn't show up on the list...

Could it be because the apm reads ComponentVersion=>11.0.8172.0 when Excel reports 11.8211.8172?

3) Microsoft Office Compatibility Pack Service Pack 1 (SP1) KB940289 isn't listed but Microsoft Update shows as a needed update for the Compatibility Pack which I installed in my Office 2003 to be able to read Office 2007 files.

Thanks!

Edited by Pedro, 21 March 2008 - 11:34 AM.

[Erik Ramey]

@Pedro - I hate to say it but I do believe that there is something wrong with your installation. You're post is telling me a couple of things:

"Could it be because the apm reads ComponentVersion=>11.0.8172.0 when Excel reports 11.8211.8172?"

Check out http://www.microsoft.com/technet/security/...n/ms08-014.mspx
Security Update Deployment --> Excel 2003 and Excel Viewer --> File Information
Excel.exe Version: 11.0.8211.0 Date: 16-Mar-2008 Time: 07:16 Size: 10,352,128

This is the proper version of Excel.exe that is deployed with the update. As to why you are seeing differently, I'm not sure

"Microsoft Update shows as a needed update for the Compatibility Pack which I installed in my Office 2003 to be able to read Office 2007 files."

This is due to the Compatibility pack not registering it's GUID properly in your registry which is located at: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{********-0020-****-****-*000000FF1CE}

If you don't have this key, which you should, AP won't detected your office products. You can read more about Office product codes and GUID's here: http://support.micro....com/kb/928516/

As for the rest of the updates, if you want, we can go into detail on the detections for each update.

[Pedro]

Hi Erik

We were talking about different version numbers. You are talking about the version reported in the exe file. I was talking about the version reported by Excel in the About box.

I did a fresh install in another PC and the problem with KB907417 persists. It is installed but AP doesn't recognize it's installed.

Thanks! (Sorry about the version confusion)

Edited by Pedro, 30 March 2008 - 02:20 PM.