These are only test scripts. They are to get an idea of what we are going to do. In the end there will be a gui and you will be able to choose your path etc.Us2002 wrote:How about KB913571, KB917148, KB921587?
IMHO that was full support english office system 2003.
q: why u use drive "c:" in scripts, not "%systemdrive%"?
[Slipstreamer] Office 2003 Post-SP2 Updates
Test scripts indeed, but 100% working. I choose for C: instead of %SystemDrive%, because I wanted to make sure the installation instructions are clear to everyone. %SystemDrive% is not C: on every PC.
About those updates, KB913571 and KB917148 are optional updates, they don't appear on MU/OU, so I didn't include them. When the GUI is finished, you will be able to have additional hotfixes slipstreamed as well.
KB921587 was replaced by KB925254, which is in the pack.
About those updates, KB913571 and KB917148 are optional updates, they don't appear on MU/OU, so I didn't include them. When the GUI is finished, you will be able to have additional hotfixes slipstreamed as well.
KB921587 was replaced by KB925254, which is in the pack.
2ViVa
1. 921587 ur right
2. 917148 is critical for OneNote (WSUS2)
3. 905645 was replaced by 913571 and was replaced by 924886 is critical for spelling-checker for Office (WSUS2)
905645 http://www.microsoft.com/technet/securi ... 6-009.mspx
913571 http://support.microsoft.com/kb/913571/en-us
924886 http://support.microsoft.com/kb/924886
1. 921587 ur right
2. 917148 is critical for OneNote (WSUS2)
3. 905645 was replaced by 913571 and was replaced by 924886 is critical for spelling-checker for Office (WSUS2)
905645 http://www.microsoft.com/technet/securi ... 6-009.mspx
913571 http://support.microsoft.com/kb/913571/en-us
924886 http://support.microsoft.com/kb/924886
I've just done this whole process manually and it took around an hour so this is a great project that I for one will really appreciate when it is finished.
(Must make it clear that it took an hour doing it manually by slipstreaming each patch one by one - not by using this new tool that is under development).
(Must make it clear that it took an hour doing it manually by slipstreaming each patch one by one - not by using this new tool that is under development).
Mandarin, this tool is under development in a way that it will have a GUI instead of the CMD windows yes, but not in the sense of that it's not working or anything, it works 100%.
Secondly, the only limitation is that you need an administrative install of Office 2003 (which you can create yourself from a non-admin install via "setup.exe /a"), but in the end, both administrative and non-administrative will be supported.
Secondly, the only limitation is that you need an administrative install of Office 2003 (which you can create yourself from a non-admin install via "setup.exe /a"), but in the end, both administrative and non-administrative will be supported.
Last edited by ViVa on Sat Dec 23, 2006 3:38 am, edited 1 time in total.
OneNote 2003 isn't part of Office 2003, it's a separate application, see http://www.microsoft.com/office/edition ... mpare.mspx as well, so it's obvious I don't include updates for OneNote in this package.
What you mention as http://www.microsoft.com/technet/securi ... 6-009.mspx , is included by Ryan's Update Pack under KB901190, see http://www.ryanvm.net/msfn/updatepack.html
KB924886 is no critical update for Office 2003, it's one for Office 2003 Proofing Tools, but that will be a seperate pack, see http://viva.ryanvm.net/office_2003_proo ... dates.html .
Take a look at http://viva.ryanvm.net/office_2003_post ... dates.html , those 13 are currently the only critical hotfixes for Office 2003 at the moment of writing.
What you mention as http://www.microsoft.com/technet/securi ... 6-009.mspx , is included by Ryan's Update Pack under KB901190, see http://www.ryanvm.net/msfn/updatepack.html
KB924886 is no critical update for Office 2003, it's one for Office 2003 Proofing Tools, but that will be a seperate pack, see http://viva.ryanvm.net/office_2003_proo ... dates.html .
Take a look at http://viva.ryanvm.net/office_2003_post ... dates.html , those 13 are currently the only critical hotfixes for Office 2003 at the moment of writing.
2Viva
"OneNote 2003 isn't part of Office 2003"... is a part of Office System 2003 (like Visio, FrontPage, Project and will be nice see pack for office system + mui, not for office only)
i will do test fresh install XP+RyanPacks+DriverPacks+OfficeSystem2003sp2+MUI+VivaPack once more at this week and will see WSUS reports.
"OneNote 2003 isn't part of Office 2003"... is a part of Office System 2003 (like Visio, FrontPage, Project and will be nice see pack for office system + mui, not for office only)
i will do test fresh install XP+RyanPacks+DriverPacks+OfficeSystem2003sp2+MUI+VivaPack once more at this week and will see WSUS reports.
2ViVa
I did aply ur updates to my administrative Office+sp2+muisp2 and install automatic DVD fresh system: XPsp2, MUI+ups, RyanVM2.1.5a, RyanVMaddon, BoooggyMP11 + very many ohter addons, all driverpacks, many swithless installers... full Office 2003 system + MUI was included.
Report Date: 12/26/2006 5:32pm
Current Service Pack Level: Service Pack 2
Hotfixes Identified:
KB841625_RUS: Current on system.
KB873339: Current on system.
KB883667: Current on system.
KB884575: Current on system.
KB885626: Current on system.
KB885836: Current on system.
KB886677: Current on system.
KB887472: Current on system.
KB888111: Current on system.
KB889016: Current on system.
KB889320: Current on system.
KB889673: Current on system.
KB890831: Current on system.
KB890859: Current on system.
KB892489: Current on system.
KB893008: Current on system.
KB893756: Current on system.
KB893803: Current on system.
KB894395: Current on system.
KB895961: Current on system.
KB896256: Current on system.
KB896344: Current on system.
KB896358: Current on system.
KB896423: Current on system.
KB896428: Current on system.
KB896626: Current on system.
KB897338: Current on system.
KB897663: Current on system.
KB898461: Current on system.
KB898543: Current on system.
KB898900: Current on system.
KB899271: Current on system.
KB899409: Current on system.
KB899591: Current on system.
KB900485: Current on system.
KB901017: Current on system.
KB901190: Current on system.
KB901214: Current on system.
KB902149: Current on system.
KB902845: Current on system.
KB902853: Current on system.
KB903234: Current on system.
KB903250: Current on system.
KB904412: Current on system.
KB904942: Current on system.
KB905414: Current on system.
KB905749: Current on system.
KB906216: Current on system.
KB906569: Current on system.
KB907265: Current on system.
KB907865: Current on system.
KB908519: Current on system.
KB908531: Current on system.
KB908536: Current on system.
KB909441: Current on system.
KB909520: Current on system.
KB909608: Current on system.
KB909667: Current on system.
KB910437: Current on system.
KB910678: Current on system.
KB911280: Current on system.
KB911562: Current on system.
KB911927: Current on system.
KB911990: Current on system.
KB912024: Current on system.
KB912461: Current on system.
KB913296: Current on system.
KB913580: Current on system.
KB914388: Current on system.
KB914440: Current on system.
KB914463: Current on system.
KB914841: Current on system.
KB914906: Current on system.
KB915865: Current on system.
KB916189: Current on system.
KB916595: Current on system.
KB916846: Current on system.
KB917140: Current on system.
KB917275: Current on system.
KB917730: Current on system.
KB917953: Current on system.
KB918005: Current on system.
KB918033: Current on system.
KB918334: Current on system.
KB918439: Current on system.
KB919007: Current on system.
KB919071: Current on system.
KB920183: Current on system.
KB920213: Current on system.
KB920342: Current on system.
KB920670: Current on system.
KB920683: Current on system.
KB920685: Current on system.
KB920872: Current on system.
KB921401: Current on system.
KB921411: Current on system.
KB922120: Current on system.
KB922582: Current on system.
KB922599: Current on system.
KB922616: Current on system.
KB922668: Current on system.
KB922819: Current on system.
KB922859: Current on system.
KB923154: Current on system.
KB923191: Current on system.
KB923232: Current on system.
KB923414: Current on system.
KB923694: Current on system.
KB923980: Current on system.
KB924191: Current on system.
KB924270: Current on system.
KB924441: Current on system.
KB924867: Current on system.
KB924941: Current on system.
KB925454: Current on system.
KB925486: Current on system.
KB925876: Current on system.
KB926255: Current on system.
KB926646: Current on system.
KB928388: Current on system.
KB929120: Current on system.
!!!BUT!!! i saw, all OfficePro components was not installed, because i replace original PRO11.MSI by ur patched. Then i replace it by original PRO11.MSI and run butch file manualy. Then i saw my WSUS reports where needed and reqested updates for system was:
(KB894542) Publisher 2003
(KB907417) Office 2003
(KB913807) Outlook 2003
(KB914455) Office 2003
(KB917148) OneNote 2003
(KB919029) Office 2003
(KB920103) InfoPath 2003
(KB923088) Excel 2003
(KB923091) PowerPoint 2003
(KB923094) Word 2003
(KB923097) Office 2003
(KB923272) Office 2003
(KB924424) Office 2003
(KB924886) Office 2003 MUI
(KB925254) Outlook 2003
I install it manualy by WSUS
I did aply ur updates to my administrative Office+sp2+muisp2 and install automatic DVD fresh system: XPsp2, MUI+ups, RyanVM2.1.5a, RyanVMaddon, BoooggyMP11 + very many ohter addons, all driverpacks, many swithless installers... full Office 2003 system + MUI was included.
Report Date: 12/26/2006 5:32pm
Current Service Pack Level: Service Pack 2
Hotfixes Identified:
KB841625_RUS: Current on system.
KB873339: Current on system.
KB883667: Current on system.
KB884575: Current on system.
KB885626: Current on system.
KB885836: Current on system.
KB886677: Current on system.
KB887472: Current on system.
KB888111: Current on system.
KB889016: Current on system.
KB889320: Current on system.
KB889673: Current on system.
KB890831: Current on system.
KB890859: Current on system.
KB892489: Current on system.
KB893008: Current on system.
KB893756: Current on system.
KB893803: Current on system.
KB894395: Current on system.
KB895961: Current on system.
KB896256: Current on system.
KB896344: Current on system.
KB896358: Current on system.
KB896423: Current on system.
KB896428: Current on system.
KB896626: Current on system.
KB897338: Current on system.
KB897663: Current on system.
KB898461: Current on system.
KB898543: Current on system.
KB898900: Current on system.
KB899271: Current on system.
KB899409: Current on system.
KB899591: Current on system.
KB900485: Current on system.
KB901017: Current on system.
KB901190: Current on system.
KB901214: Current on system.
KB902149: Current on system.
KB902845: Current on system.
KB902853: Current on system.
KB903234: Current on system.
KB903250: Current on system.
KB904412: Current on system.
KB904942: Current on system.
KB905414: Current on system.
KB905749: Current on system.
KB906216: Current on system.
KB906569: Current on system.
KB907265: Current on system.
KB907865: Current on system.
KB908519: Current on system.
KB908531: Current on system.
KB908536: Current on system.
KB909441: Current on system.
KB909520: Current on system.
KB909608: Current on system.
KB909667: Current on system.
KB910437: Current on system.
KB910678: Current on system.
KB911280: Current on system.
KB911562: Current on system.
KB911927: Current on system.
KB911990: Current on system.
KB912024: Current on system.
KB912461: Current on system.
KB913296: Current on system.
KB913580: Current on system.
KB914388: Current on system.
KB914440: Current on system.
KB914463: Current on system.
KB914841: Current on system.
KB914906: Current on system.
KB915865: Current on system.
KB916189: Current on system.
KB916595: Current on system.
KB916846: Current on system.
KB917140: Current on system.
KB917275: Current on system.
KB917730: Current on system.
KB917953: Current on system.
KB918005: Current on system.
KB918033: Current on system.
KB918334: Current on system.
KB918439: Current on system.
KB919007: Current on system.
KB919071: Current on system.
KB920183: Current on system.
KB920213: Current on system.
KB920342: Current on system.
KB920670: Current on system.
KB920683: Current on system.
KB920685: Current on system.
KB920872: Current on system.
KB921401: Current on system.
KB921411: Current on system.
KB922120: Current on system.
KB922582: Current on system.
KB922599: Current on system.
KB922616: Current on system.
KB922668: Current on system.
KB922819: Current on system.
KB922859: Current on system.
KB923154: Current on system.
KB923191: Current on system.
KB923232: Current on system.
KB923414: Current on system.
KB923694: Current on system.
KB923980: Current on system.
KB924191: Current on system.
KB924270: Current on system.
KB924441: Current on system.
KB924867: Current on system.
KB924941: Current on system.
KB925454: Current on system.
KB925486: Current on system.
KB925876: Current on system.
KB926255: Current on system.
KB926646: Current on system.
KB928388: Current on system.
KB929120: Current on system.
!!!BUT!!! i saw, all OfficePro components was not installed, because i replace original PRO11.MSI by ur patched. Then i replace it by original PRO11.MSI and run butch file manualy. Then i saw my WSUS reports where needed and reqested updates for system was:
(KB894542) Publisher 2003
(KB907417) Office 2003
(KB913807) Outlook 2003
(KB914455) Office 2003
(KB917148) OneNote 2003
(KB919029) Office 2003
(KB920103) InfoPath 2003
(KB923088) Excel 2003
(KB923091) PowerPoint 2003
(KB923094) Word 2003
(KB923097) Office 2003
(KB923272) Office 2003
(KB924424) Office 2003
(KB924886) Office 2003 MUI
(KB925254) Outlook 2003

I've followed these instructions exactly to try to get an Office11 + SP2 + Hotfixes admin install, but when everything is done integrating the post-SP2 hotfixes (all 13 appear to patch without problems), I run the setup script as instructed and I'm getting the following error:
Windows Installer
-----------
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
-----------
Plus VIVA.CMD appears to insert the registry settings even if the main setup fails. Hope this doesn't mess up anything when I install it w/o the hotfixes...
I even re-did everything TWICE just for sanity purposes.
*sigh* guess I'll just stick with Office11 + SP2 admin install...it seems to execute just fine...would have been nice for this to work...
Windows Installer
-----------
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
-----------
Plus VIVA.CMD appears to insert the registry settings even if the main setup fails. Hope this doesn't mess up anything when I install it w/o the hotfixes...
I even re-did everything TWICE just for sanity purposes.
*sigh* guess I'll just stick with Office11 + SP2 admin install...it seems to execute just fine...would have been nice for this to work...
I get the exact same problem as dougm.ViVa wrote:I'm sorry to see it doesn't work for you, it works perfectly fine here and for other people. Are you sure you have a clean source?
PS: The registry entries won't do any harm.
This is a perfectly clean source - a O2K3 admin install point w/ SP2 integrated.
Integrating post sp2 O2K3 patches is something I gave up on because MU would still stupidly complain the patches were still required to download. This looked promising but I get the aforementioned error. Could it have something to do with the PRO11.msi being replaced? (I'm not sure why this even needs to be done?)
Hi, this is something I dedicated my sunday to this week, and after quite a bit of messing around, I finally got it working ok. None of it was the fault of Viva's pack though (well done mate, excellent work btw) it was a few things I did wrong but figured out over time.
dougm: check this microsoft knowledge base, sounds like its a problem with your windows installation and the Windows Installer.
http://support.microsoft.com/kb/236597
also check this in regards to the same thing happening when installing daemon tools.
http://www.daemon-tools.cc/dtcc/archive ... t1241.html
Fragbert: Never ever trust MU over Office Update. The support for detecting Updates in MU is totaly screwed, every time I logon on it says different things about what need to be installed to patch my office 2003. I don;t listen to it, its always wrong, just look at Office Update and trust that. Microsoft's fault, not ours.
dougm: check this microsoft knowledge base, sounds like its a problem with your windows installation and the Windows Installer.
http://support.microsoft.com/kb/236597
also check this in regards to the same thing happening when installing daemon tools.
http://www.daemon-tools.cc/dtcc/archive ... t1241.html
Fragbert: Never ever trust MU over Office Update. The support for detecting Updates in MU is totaly screwed, every time I logon on it says different things about what need to be installed to patch my office 2003. I don;t listen to it, its always wrong, just look at Office Update and trust that. Microsoft's fault, not ours.
Bardo Thodol dotnet
www.bardothodol.net
www.bardothodol.net
Right but everybody is complaining that there needs to be a method to convince MU as the goal for many is a clean slate on MU. The add reg hack that Viva uses here so far is the only solution.pupil wrote: Fragbert: Never ever trust MU over Office Update. The support for detecting Updates in MU is totaly screwed, every time I logon on it says different things about what need to be installed to patch my office 2003. I don;t listen to it, its always wrong, just look at Office Update and trust that. Microsoft's fault, not ours.
Also I think the issues that I and dougm are having may stem from an integrated license key in our install points. I still have no idea why the pro11.msi needs to be messed with in the first place. I edited the slipstreaming cmd so that just the msp's are integrated and run a sucessful install (with a transforms MST too)
I followed your directions to a T, this is on a brand new WinXP SP2 install slipstreamed with RyanVM Update Pack, nothing else installed on the computer other than the drivers.ViVa wrote:I'm sorry to see it doesn't work for you, it works perfectly fine here and for other people. Are you sure you have a clean source?
PS: The registry entries won't do any harm.
If it makes any difference, my version of Office runs setup via SETUPPRO.EXE, there was no such SETUP.EXE file on the installation disc. Maybe I'm running the corporate edition or something.
I do not use setuppro.exe, just regular setup.exe, and my copy is the corporate edition (I think all have to be to create an admin install point in order to integrate SP2?). Same problem as you.dougm wrote:I followed your directions to a T, this is on a brand new WinXP SP2 install slipstreamed with RyanVM Update Pack, nothing else installed on the computer other than the drivers.ViVa wrote:I'm sorry to see it doesn't work for you, it works perfectly fine here and for other people. Are you sure you have a clean source?
PS: The registry entries won't do any harm.
If it makes any difference, my version of Office runs setup via SETUPPRO.EXE, there was no such SETUP.EXE file on the installation disc. Maybe I'm running the corporate edition or something.
I think you mean Enterprise here instead of Corporate.
@dougm, that explains your problem I guess, I never heard of SETUPPRO.EXE, my copy has SETUP.EXE as well.
For clearance: the reg entries are so that MU won't complain. PRO11.MSI is replaced because of an error in the InfoPath hotfix (which will appear if you don't have .NET installed during setup, that's why I'm replacing it, so there won't be no error even if there is no .NET installed).
Also, sorry for the delay, I'm very busy at my school project atm.
Microsoft released 3 updates today for Office 2003 btw, I will update asap:
@dougm, that explains your problem I guess, I never heard of SETUPPRO.EXE, my copy has SETUP.EXE as well.
For clearance: the reg entries are so that MU won't complain. PRO11.MSI is replaced because of an error in the InfoPath hotfix (which will appear if you don't have .NET installed during setup, that's why I'm replacing it, so there won't be no error even if there is no .NET installed).
Also, sorry for the delay, I'm very busy at my school project atm.
Microsoft released 3 updates today for Office 2003 btw, I will update asap:
Security Update for Excel 2003 (KB925257)
Download size: 4.9 MB
A security vulnerability exists in Microsoft Office Excel 2003 that could allow remote code execution. This update resolves that vulnerability.
Security Update for Outlook 2003 (KB924085)
Download size: 8 MB
This update resolves a security vulnerability in Microsoft Office Outlook 2003 that could enable a remote user to execute code on a computer that is running Outlook 2003.
Update for Outlook 2003 Junk Email Filter (KB925534)
Download size: 3.2 MB
This update provides the Junk E-mail Filter in Microsoft Office Outlook 2003 with a more current definition of which e-mail messages should be considered junk e-mail. This update was released in January 2007.
-
- Posts: 67
- Joined: Thu Nov 17, 2005 3:28 am
- Location: Bulgaria
Probably he is talking about VOL version of Office which require no activation. Also Setuppro.exe is the main installation file of Office 2003 Pro with Frontpage 2003ViVa wrote:I think you mean Enterprise here instead of Corporate.
@dougm, that explains your problem I guess, I never heard of SETUPPRO.EXE, my copy has SETUP.EXE as well.
That's what it is, the Enterprise edition of O2K3 with Publisher and FrontPage. Has anyone successfully gotten this slipstream pack to work with the Enterprise edition?colornokia wrote:Probably he is talking about VOL version of Office which require no activation. Also Setuppro.exe is the main installation file of Office 2003 Pro with Frontpage 2003ViVa wrote:I think you mean Enterprise here instead of Corporate.
@dougm, that explains your problem I guess, I never heard of SETUPPRO.EXE, my copy has SETUP.EXE as well.
dougm, what you simply do is make sure your PRO11.MSI doesn't get overwritten in the end (you can edit Office 2003 Post-SP2 Updates.cmd and make sure these 3 lines are removed:
echo Patching PRO11.MSI...
bspatch.exe C:\OFFICE11\PRO11.MSI C:\OFFICE11\PRO11.MSI PRO11.diff
echo Patching complete.
), and you will be just fine I guess. If you are using InfoPath, please make sure you have .NET Framework installed before setup.
echo Patching PRO11.MSI...
bspatch.exe C:\OFFICE11\PRO11.MSI C:\OFFICE11\PRO11.MSI PRO11.diff
echo Patching complete.
), and you will be just fine I guess. If you are using InfoPath, please make sure you have .NET Framework installed before setup.
This package is for Office 2003 SP2 English Version only, as you can read in the first post of this topic.Microsoft Security Bulletin MS07-001
Vulnerability in Microsoft Office 2003 Brazilian Portuguese Grammar Checker Could Allow Remote Code Execution (921585)
Affected Software:
- Microsoft Office 2003 Service Pack 2 (Brazilian Portuguese Version)
hmm... may be, i have tryed to download ups from MU and in C:\WINDOWS\SoftwareDistribution\Download\... was OUTLFLTR.CAB, EXCEL.CAB, OUTLOOK.CAB and directory for IE7 up.
!!!BUT OUTLOOK.CAB (6 649 856 bytes) contains less files than Outlookff.msp (9 357 824 bytes) and cannot replace it completly (IMHO)
im wrong? where im mistake, can i hear ur comment plz
!!!BUT OUTLOOK.CAB (6 649 856 bytes) contains less files than Outlookff.msp (9 357 824 bytes) and cannot replace it completly (IMHO)
im wrong? where im mistake, can i hear ur comment plz
This is AWESOME stuff, ViVa!!
Aside from Windows, Office is probably the second most-installed app.
Personally, I don't use it all that much. But for my customers, it's a must-have.
This takes all the pain out of it.
Question:
(Forgive me if this is obvious, but...) So, this is like an Office version of Xable's Zero Update Pack, right? Does this include the Office Service Packs, or just pure hotfixes/security updates?
Hope you and Sigi can put an 'Office Integrator' app together. That'd save you time, and of course, would be easier to use.
Til the meantime, thx!!
Aside from Windows, Office is probably the second most-installed app.
Personally, I don't use it all that much. But for my customers, it's a must-have.
This takes all the pain out of it.

Question:
(Forgive me if this is obvious, but...) So, this is like an Office version of Xable's Zero Update Pack, right? Does this include the Office Service Packs, or just pure hotfixes/security updates?
Hope you and Sigi can put an 'Office Integrator' app together. That'd save you time, and of course, would be easier to use.
Til the meantime, thx!!
"may be"? You didn't even take the trouble to download the patch and try it out?? Download link: http://www.microsoft.com/downloads/deta ... layLang=en , unpack and see for yourself. According to MU/OU this update is a full replace btw. You can't judge on file sizes, please investigate a little more before you start shouting these things.Us2002 wrote:hmm... may be, i have tryed to download ups from MU and in C:\WINDOWS\SoftwareDistribution\Download\... was OUTLFLTR.CAB, EXCEL.CAB, OUTLOOK.CAB and directory for IE7 up.
!!!BUT OUTLOOK.CAB (6 649 856 bytes) contains less files than Outlookff.msp (9 357 824 bytes) and cannot replace it completly (IMHO)
im wrong? where im mistake, can i hear ur comment plz
This is indeed "something like" Xable's Zero Update Pack or in other words just a Zero Update Pack for Office 2003 SP2. It doesn't include service packs, same as Ryan's or Xable's pack doesn't include service packs. This pack contains all the post-SP2 updates for Office 2003, which appear on MU/OU.RaGhul wrote:This is AWESOME stuff, ViVa!!
Aside from Windows, Office is probably the second most-installed app.
Personally, I don't use it all that much. But for my customers, it's a must-have.
This takes all the pain out of it.
Question:
(Forgive me if this is obvious, but...) So, this is like an Office version of Xable's Zero Update Pack, right? Does this include the Office Service Packs, or just pure hotfixes/security updates?
Hope you and Sigi can put an 'Office Integrator' app together. That'd save you time, and of course, would be easier to use.
Til the meantime, thx!!
Sigi and me are working on the app, in the meanwhile this perfectly works.

Yes that is planned. As well as a way to choose what hotfixes you integrate. You will be able to download official or non-official hotfixes and have them integrated.RaGhul wrote:So, in other words, you need to integrate the SP first.
Do you plan to include an option to integrate the SP's through the app you and Sigi are working on?
That would be real nice.


2ViVa
i cannot right now dowload patch from MS, i dowloaded it from MU on intalled system, compare filesizes, read KB articles and ask u, mistake i or not
.
may be i have dowloaded "delta" update for fullfile from MU...
http://support.microsoft.com/kb/913807 (8.6MB)
Outlookff.msp (9 357 824 bytes):
Addrpars.dll 11.0.6550.0 88,264 17-ìàð-2005 19:32
Dlgsetp.dll 11.0.8009.0 77,000 16-ÿíâ-2006 23:09
Envelope.dll 11.0.8004.0 132,808 06-äåê-2005 21:44
Exchcsp.dll 11.0.6424.0 247,808 01-ìàð-2005 19:27
Exsec32.dll 11.0.8000.0 346,824 22-îêò-2005 21:15
Impmail.dll 11.0.6550.0 122,056 17-ìàð-2005 19:32
Oladd.fae 11.0.6550.0 158,912 17-ìàð-2005 19:41
Olappt.fae 11.0.6550.0 152,264 17-ìàð-2005 19:41
Oljrnl.fae 11.0.6550.0 117,960 17-ìàð-2005 19:41
Olmail.fae 11.0.6550.0 113,352 17-ìàð-2005 19:41
Olnote.fae 11.0.6550.0 104,648 17-ìàð-2005 19:41
Oltask.fae 11.0.6550.0 147,144 17-ìàð-2005 19:41
Outllib.dll 11.0.8010.0 7,613,128 20-ÿíâ-2006 21:37
Outlmime.dll 11.0.6555.0 92,360 25-àïð-2005 18:29
Outlook.exe 11.0.8010.0 196,296 20-ÿíâ-2006 21:35
Outlph.dll 11.0.6550.0 141,000 17-ìàð-2005 19:32
Outlrpc.dll 11.0.6552.0 64,200 31-ìàð-2005 18:21
Outlvbs.dll 11.0.6550.0 44,744 17-ìàð-2005 19:32
Recall.d ll 11.0.8001.0 39,112 01-íîÿ-2005 20:57
Rm.dll 11.0.6550.0 74,944 17-ìàð-2005 19:32
Sc2.sam 11.0.6550.0 111,808 17-ìàð-2005 19:41
Schplus.sam 11.0.6550.0 143,048 17-ìàð-2005 19:41
Transmgr.dll 11.0.8000.0 100,552 22-îêò-2005 21:56
http://www.microsoft.com/rus/technet/se ... 7-003.mspx (8.1MB)
Outlook.msp (6 649 856 bytes):
Dlgsetp.dll 11.0.8009.0 17-ÿíâ-2006 01:09 77 000
Envelope.dll 11.0.8004.0 06-äåê-2005 23:44 132 808
Exsec32.dll 11.0.8027.0 23-ìàÿ-2006 00:39 346 896
Mimedir.dll 11.0.8115.0 03-íîÿ-2006 01:50 177 424
Oladd.fae 11.0.8029.0 02-èþí-2006 23:10 158 992
Olappt.fae 11.0.8109.0 23-ñåí-2006 07:15 152 848
Oljrnl.fae 11.0.8109.0 23-ñåí-2006 07:15 118 032
Olmail.fae 11.0.8109.0 23-ñåí-2006 07:15 113 424
Olnote.fae 11.0.8109.0 23-ñåí-2006 07:15 104 720
Oltask.fae 11.0.8029.0 02-èþí-2006 23:10 147 216
Outllib.dll 11.0.8118.0 24-íîÿ-2006 04:54 7 619 856
Outlmime.dll 11.0.8104.0 17-àâã-2006 23:04 93 456
Outlook.exe 11.0.8118.0 24-íîÿ-2006 04:56 196368
Recall.dll 11.0.8001.0 01-íîÿ-2005 22:57 39 112
Transmgr.dll 11.0.8000.0 22-îêò-2005 23:56 100 552
so, where im wrong?
i cannot right now dowload patch from MS, i dowloaded it from MU on intalled system, compare filesizes, read KB articles and ask u, mistake i or not

may be i have dowloaded "delta" update for fullfile from MU...
http://support.microsoft.com/kb/913807 (8.6MB)
Outlookff.msp (9 357 824 bytes):
Addrpars.dll 11.0.6550.0 88,264 17-ìàð-2005 19:32
Dlgsetp.dll 11.0.8009.0 77,000 16-ÿíâ-2006 23:09
Envelope.dll 11.0.8004.0 132,808 06-äåê-2005 21:44
Exchcsp.dll 11.0.6424.0 247,808 01-ìàð-2005 19:27
Exsec32.dll 11.0.8000.0 346,824 22-îêò-2005 21:15
Impmail.dll 11.0.6550.0 122,056 17-ìàð-2005 19:32
Oladd.fae 11.0.6550.0 158,912 17-ìàð-2005 19:41
Olappt.fae 11.0.6550.0 152,264 17-ìàð-2005 19:41
Oljrnl.fae 11.0.6550.0 117,960 17-ìàð-2005 19:41
Olmail.fae 11.0.6550.0 113,352 17-ìàð-2005 19:41
Olnote.fae 11.0.6550.0 104,648 17-ìàð-2005 19:41
Oltask.fae 11.0.6550.0 147,144 17-ìàð-2005 19:41
Outllib.dll 11.0.8010.0 7,613,128 20-ÿíâ-2006 21:37
Outlmime.dll 11.0.6555.0 92,360 25-àïð-2005 18:29
Outlook.exe 11.0.8010.0 196,296 20-ÿíâ-2006 21:35
Outlph.dll 11.0.6550.0 141,000 17-ìàð-2005 19:32
Outlrpc.dll 11.0.6552.0 64,200 31-ìàð-2005 18:21
Outlvbs.dll 11.0.6550.0 44,744 17-ìàð-2005 19:32
Recall.d ll 11.0.8001.0 39,112 01-íîÿ-2005 20:57
Rm.dll 11.0.6550.0 74,944 17-ìàð-2005 19:32
Sc2.sam 11.0.6550.0 111,808 17-ìàð-2005 19:41
Schplus.sam 11.0.6550.0 143,048 17-ìàð-2005 19:41
Transmgr.dll 11.0.8000.0 100,552 22-îêò-2005 21:56
http://www.microsoft.com/rus/technet/se ... 7-003.mspx (8.1MB)
Outlook.msp (6 649 856 bytes):
Dlgsetp.dll 11.0.8009.0 17-ÿíâ-2006 01:09 77 000
Envelope.dll 11.0.8004.0 06-äåê-2005 23:44 132 808
Exsec32.dll 11.0.8027.0 23-ìàÿ-2006 00:39 346 896
Mimedir.dll 11.0.8115.0 03-íîÿ-2006 01:50 177 424
Oladd.fae 11.0.8029.0 02-èþí-2006 23:10 158 992
Olappt.fae 11.0.8109.0 23-ñåí-2006 07:15 152 848
Oljrnl.fae 11.0.8109.0 23-ñåí-2006 07:15 118 032
Olmail.fae 11.0.8109.0 23-ñåí-2006 07:15 113 424
Olnote.fae 11.0.8109.0 23-ñåí-2006 07:15 104 720
Oltask.fae 11.0.8029.0 02-èþí-2006 23:10 147 216
Outllib.dll 11.0.8118.0 24-íîÿ-2006 04:54 7 619 856
Outlmime.dll 11.0.8104.0 17-àâã-2006 23:04 93 456
Outlook.exe 11.0.8118.0 24-íîÿ-2006 04:56 196368
Recall.dll 11.0.8001.0 01-íîÿ-2005 22:57 39 112
Transmgr.dll 11.0.8000.0 22-îêò-2005 23:56 100 552
so, where im wrong?
Us2002, like I said before, according to MU/OU it is a full replace. Also, don't trust the filenames on the KB pages, they are usually outdated. I did a fresh install of Office 2003 SP2 without any updates integrated, and KB924085 now pops up instead of KB913807 (since the January 2007 updates). Please contact Microsoft for further questions regarding this, I cannot be more clear to you then I already am right now.
- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
The patching is a workaround for people who want to use InfoPath and don't have .NET installed, you can remove it if you either don't use InfoPath or have .NET installed. This will change in the future, right now me and Sigi are busy with other stuff. 

Last edited by ViVa on Tue Jan 16, 2007 1:08 pm, edited 1 time in total.
- ricktendo64
- Posts: 3214
- Joined: Mon May 22, 2006 12:27 am
- Location: Honduras
2ViVa
\\Btw, you are the first one reporting this, I will look into it. What's the precise error?\\
FIRST??? Read my posts please, same error.
\\!!!BUT!!! i saw, all OfficePro components was not installed, because i replace original PRO11.MSI by ur patched. Then i replace it by original PRO11.MSI and run butch file manualy.\\
\\Btw, you are the first one reporting this, I will look into it. What's the precise error?\\
FIRST??? Read my posts please, same error.
\\!!!BUT!!! i saw, all OfficePro components was not installed, because i replace original PRO11.MSI by ur patched. Then i replace it by original PRO11.MSI and run butch file manualy.\\