After reading a lot about slipstreaming SP1 to Office 2003 still I couln'd find a nice solution. So after many different approaches and reading a lot about MSI here comes another guide on slipstreaming

The Goal: build a fully functional Office 2003 SP1, using cache on setup, asking for serial, being only a bit larger than the original without SP1 & allowing for administrative install

What do you need:
- ORCA
- MSI 3.1 installed
- WSH 5.6 installed
- md5sum.exe (http://unxutils.sourceforge.net/)
- makecab.exe (Microsoft Cabinet SDK)
- sort2cabs.js (Download (5,5kB))
- Office 2003 CD(s)
- appropriate administrative updates
- some hard disk space and some time

What I did to create a working Office 2003 SP1:

1. Copy the office 2003 to the hard disk (referred from now on as X:\office2003). Remove all hidden and write-only attributes from files. Store all updates on hard disk (*.MSP, directory referred to is called x:\SP1). Make backups of X:\office2003\FILES\SETUP\*.INI

2. Apply Updates (slipstream) using the following Syntax:



if this is not working, try first making an administrative install and then copy the original msi-files over the altered and the apply the patches. This may be no longer necessary since MSI 3.x

After the Updates delete any cab files in X:\office2003

3. Create a subdirectory X:\office2003\sort and extract sort2cabs.zip here. Create subdirectories for every msi you installed before (-> X:\office2003\sort\pro11, X:\office2003\sort\owc10, X:\office2003\sort\owc11, ...). The following has to be done with every msi file:
- open with ORCA
- export tables CabinetDetail, Component, Directory, File, Media to the created corresponding directory

4. Copy XML files located at X:\office2003\FILES\SETUP to X:\office2003\sort. Now edit X:\office2003\sort\tabledirs.lst and X:\office2003\sort\xmlfiles.lst to match your need. tabledirs.lst lists all directories containing the exported tables from the msi packages (existence is checked in sort2cabs.js) and xmlfiles.lst lists all xml to edit (correct md5sums).

5. Open a command line (cmd) and change path to X:\office2003\sort. Start sort2cabs using folling syntax:
for successful completion md5sum.exe and makecab.exe should be placed in a directory listed in the path variable! ok, time for a cup of coffee

6. When the script stops you have to replace some tables in your msi packages. Use ORCA for this task:
- open zzz.msi with ORCA (replace zzz with msi package names)
- import tables called *.new.idt from X:\office2003\sort\zzz, replace the old ones, do not merge
- save (this is important, too)
now the script may continue (this stop is necessary for calculating the md5sums for the xml files)

7. That's nearly all, now copy the xml files from X:\office2003\sort to X:\office2003\FILES\SETUP, restore the backed up ini files in X:\office2003\FILES\SETUP and delete all files that were not originally on the office cd (ok, i wrote a bat file for copying all files to another location, which files are necessary you'll see on your cd ). Burn your new Office 2003 on a CD labeled 'OFFICE11'



It may be necessary to edit the msi package of MS Project when building an AIO CD. The table "Media" contains a column "VolumeLabel" which should be "OFFICE11". Make this change after step 1.

I know this is not as easy as just pressing a button, but sort2cabs.js is rather generic and may work with other msi packages. If not, try to alter the script

Here a short summary what the script does:
- read dirlist.lst and test for all necessary files in listed subdirs
- read all *.idt and combine information in arrays
- sort by media (cab files) and sequence numbers from msi packages
- renumber all files/set new sequence numbers to eliminate duplicate numbers (otherwise you cannot use compression)
- compress using makecab and ddf files to control process, sorting of files in cabs must be the same as sorting by sequence numbers in msi packages
- calculate md5 sums for cabs and other files listed in xml files located in X:\office2003\FILES\SETUP

This may help understanding the script. I added some comments, too.

Because I tested the whole process only with SP1 (maybe all later patches can be integrated) and not in detail please report problems here.

What is ORCA?

IT Also works withui mui updated with sp1

Thank You very match , No Any Problems .

Thanks, gonna give a try on this. Looks very interesting to me.

------------------------------------------------------------------------
Edit:


When applying the Sp/Update patches to original files, there is also an additional file called ocw10.msi. This file is not present in admin image.

So if I apply the Sp/Updates to extracted admin image, what about the ocw10.si file?

If I perform an admin image first, then copy over the original unaltered .msi's wouldnt the folder structure be different in the target source?

Although I have yet to try this, I would like to ask if this switch might work while doing the first admin image?
msiexec.exe /a pro11.msi MSINODISABLEMEDIA=1

------------------------------------
Edit:2
Along with this can we also enable Office Online Update??

ok. Followed your guide to the letter and created cab-compressed image of All products of Office 2003 slipstreamed with sp1 and recent hotfixes after sp1.

The main reason for this guide is to fit everything on one cd. So I would like to mention that after integrating sp1 in to core office11, visio11, frontpage11, onenote11, project11, (also webcomponents 11 & 10) the final ISO comes to 991MB, optimised comes to 791MB.

I still have to install test this baby.

One more note: Some of the cabinets in different products having the same name do not have the same content, therefore "the beef stew method" of creating AIO (supposedly vol.msdn cd method) is out of the question here.

Did another try with using the old makecab and not the one on my system from Server 2003 Sp1. And the final cabs were bigger than my pervious attempt BUT the whole thing optimised with cdimage
fit on one 701MB CD!! Thanks once again.

Also I used the same method for giving it a try with Proofing Toolkit and recived the following errors..
This list is from a long list which I edited...

--------------------
Copyright © Microsoft Corp 1993-1997. All rights reserved.

Parsing directives (YS561417.CAB.ddf: 100 lines)
YS561417.CAB.ddf(136): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\2052\SAPICPL.HLP
YS561417.CAB.ddf(137): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\2052\SPEECH.CHM
YS561417.CAB.ddf(138): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\1033\SPEECH.CHM
YS561417.CAB.ddf(139): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\1033\SAPICPL.HLP
YS561417.CAB.ddf(140): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\1041\SPEECH.CHM
YS561417.CAB.ddf(141): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\1041\SAPICPL.HLP
Parsing directives (YS561417.CAB.ddf: 150 lines)
ERROR: MakeCAB aborted: 6 errors encountered


Microsoft ® Cabinet Maker - Version (32) 1.00.0601 (03/18/97)
Copyright © Microsoft Corp 1993-1997. All rights reserved.

Parsing directives (PR2052BA.CAB.ddf: 1 lines)
PR2052BA.CAB.ddf(6): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\HELP\WINWB86.CHM
PR2052BA.CAB.ddf(7): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\HELP\WINWB86.CNT
PR2052BA.CAB.ddf(8): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\HELP\WINWB86.HLP
PR2052BA.CAB.ddf(13): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\HELP\WINWB98.CHM
PR2052BA.CAB.ddf(14): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\HELP\WINWB98.CNT
PR2052BA.CAB.ddf(15): ERROR: Could not find file: ..\FILES\WINDOWS\HELP:WUBI86\HELP\WINWB98.HLP
ERROR: MakeCAB aborted: 6 errors encountered

creating PR308250.CAB:


creating YJ561403.CAB:

Microsoft ® Cabinet Maker - Version (32) 1.00.0601 (03/18/97)
Copyright © Microsoft Corp 1993-1997. All rights reserved.

Parsing directives (YJ561403.CAB.ddf: 1 lines)
YJ561403.CAB.ddf(1): ERROR: Could not find file: ..\FILES\PFILES\COMMON\MSSHARED\WORDBRKR:.\MSIR3JP.
DLL
YJ561403.CAB.ddf(2): ERROR: Could not find file: ..\FILES\PFILES\COMMON\MSSHARED\WORDBRKR:.\MSIR3JP.
LEX
ERROR: MakeCAB aborted: 2 errors encountered

creating ZR561427.CAB:

creating ZZ561401.CAB:

Microsoft ® Cabinet Maker - Version (32) 1.00.0601 (03/18/97)
Copyright © Microsoft Corp 1993-1997. All rights reserved.

42 bytes in 1 files
Total files: 1
Bytes before: 42
Bytes after: 62
After/Before: 147.62% compression
Time: 0.02 seconds ( 0 hr 0 min 0.02 sec)
Throughput: 2.56 Kb/second
calculating md5 for ZF561421.CAB (98581164):
-> DC73E68BFFDB6D41F57132271A238AC6
calculating md5 for MT561437.CAB (1387940):
-> DE6C1746C76F631C52D4E306359CFDE6
calculating md5 for ZY561417.CAB (483122):
-> 54E3A7B28150EE86E13B0FE106CE1AC2
calculating md5 for YO561424.CAB (29828672):
-> 7538E933850294278FB7CEB75CE96167
calculating md5 for PR103687.CAB (4183243):
-> 8F43C3BEE595D922F95469AF9FED7071
calculating md5 for PR1041CS.CAB (2212966):
-> 59846016760B90AD200024E15EACADD6
calculating md5 for MI561416.CAB (119437636):
-> 858A6B65830816A1F3DC84BB6B4A4B98

Error: [object Error]

H:\OFFICE11_PTK\sort>

--------------------------------

hmm, isnt anyone interested in this anymore.

I slipstreamed, service pack 2 for office 2003 and the rest of the office programs using the method above. ( Overwrote the native makecab.exe with the old version in cabinet sdk )

The final size for ..
Office, Frontpage, Visio, OneNote, ProjectClient -- 2003 integrated with Service Pack 2 after using cdimage.exe to optimze the source,
was only 679MB.

Great now I have all the office 2003 sp2 collection on 1 cd with some room to spare for adobe reader 7 too.

I'm interested... but I can't seem to get it to work...

How do you go about clearning out all the files that aren't on the original CD?

Also... do you just take the files that are on each CD and simply copy them over into your working directory, overwriting any existing files?

@Historic - Would you mind clarifying some of the orignal instructions?

Also, do you get the option to save the cache at the end of the install? If I can find a method that does that I would be very very very happy.

sorry for not answering, gonna take a look at all later. please be patient cause i'm short of time at the moment. i also found a way to ommit ORCA (just using MSI routines in jscript for reading/writing tables) more later.

HE'S BACK!!!!

w00t!!! *waits patiently... or impatiently...*

Hmm...

I managed to follow the guide again, using only Disc1 for the time being. Everything went smoothly, and I managed to delete all the files that weren't originally on the non-SP disc. In the end, the slipstreamed re-cabbed install comes out at just over 400MB... just like before.

But I'm still missing the option to cache the install files....

Thank you marek722!
I make a 5IN1 AIO CD with slipstreamed SP2, and replaced some code as below for MAX compress ratio:

Thanks for the excellent guide.

Worked great for me installing SP2 on my student/teacher edition...or whatever it is (says 30 day trial on the disk, no it's not pirated).

My original disk was 391 mb. after slipstream it's 388 mb. ---burned with nero

Updating the guide would probably help some people out. It took me a couple tries to get everything right.

@zxian

My install is getting cached to the HD, not sure if this is just because of the version I'm using. I just used the original guide, didn't make any other tweaks.

Strange... No matter what I try to do (slipstream using administrative install point or just following the guide), I can't get the option to cache the install files. I think I'll give this one more shot tonight...

I just wanted to add I made my firt attempt to install this on my pc, rather than VM, yesterday and the software didn't install. This iwas most likely caused from having services and/or programs removed which office needs to run. (I forgot to write down the error )

Also, I am not able to make an admin install point with this version, and I think I will have to manually install my key, not sure if it is going to work in the mst file.

I'm going to test again tonight, I have a bunch of other stuff to fix on top of this problem.

-----EDIT

Just tried a new install. Office began loading, and rolled back without any messages. Going to try again when I get a chance.

Please specify on what topic do need further instructions. Glad to be of help.

I followed the original guide to the letter for both, sp1 integration and sp2 integration.
But with the diffrence that I replaced the original setup.exe from ALL office setup's (off,frontpage,visio,project..etc.) with the enhanced setup.exe available in office toolbox at microsoft office resources admin page.
Made a custom boot menu, from "Autoplay Media Studio v4" by indigorose.
Left the original setup.ini files as is.

In autoplay setup launcher, added the command-line parameters passed to setup.exe with sn=xxxxxx and enforcecache=true, user=username organization=orgname

Plus I integrated, Office sounds, and Remove hidden data into the original office setup. So that it is installed along with the main office package. And created the XML cache files for office sounds and RHD so that all the extra files too are also cached along with the main office.
Then corrected all the messed up md5 values in setup.ini and created 2 more ini files and respective folders for the proper installation,cache,and integration of rhd & sounds packages.

Setting the cabinet compression to max will make the full 5 cd's unable to be optimised on one cd, as each cabinet with the same content will have slightly different compressed cab's and cdimage will find the cab file content not equal, so size will shoot above 730mb.

I wrote this batch to delete unwanted files.
Just copy and paste in a "finish_slipstream.bat" file the following code and replace <path to original CD|folder> and <path to slipstreamed CD|folder> to suit your needs. Run the batch from a folder OUTSIDE the slipstreamed CD|folder and burn the slipstreamed version.

Example:
original Office CD in drive E, slipstreamed folder in d:\office
replace <path to original CD|folder> with e:\ <= ENDING SLASH NEEDED FOR ROOTS (DRIVES)
replace <path to slipstreamed CD|folder> with d:\office <= NO ENDING SLASH (FOLDERS)
run the batch from outside d:\office


@echo off

echo Removing useless Folders and Files

rem SUBST creates a temp. virtual HD for folders and files listing
rem This is needed to have the same path prefix on folders and files
rem when comparing the differences between the two versions

rem Creates folders and files lists of the original version
SUBST w: "<path to original CD|folder>"
DIR /A /AD /ON /B /S w:\ >CD_dirs.txt
DIR /A /A-D /ON /B /S w:\ >CD_files.txt
SUBST w: /D

rem Creates folders list of the slipstreamed version
SUBST w: "<path to slipstreamed CD|folder>"
DIR /A /AD /ON /B /S w:\ >CDSP2_dirs.txt
rem Finds and deletes folders not existing in the original version
FOR /f "tokens=*" %%i IN (CDSP2_dirs.txt) DO (
FIND /I "%%i" CD_dirs.txt >nul
If ErrorLevel 1 IF EXIST "%%i" RD /S /Q "%%i"
)
rem Creates remaining files list of the slipstreamed version
DIR /A /A-D /ON /B /S w:\ >CDSP2_files.txt
rem Finds and deletes remaining files not existing in the original version
FOR /f "tokens=*" %%i IN (CDSP2_files.txt) DO (
FIND /I "%%i" CD_files.txt >nul
If ErrorLevel 1 DEL /Q "%%i"
)
SUBST w: /D

rem Removes temp. files used
DEL CD*.txt

echo Finished!
pause


NOTE 1: if you have the W: drive letter already in use, change it in the batch code with someone free
NOTE 2: if you have any CD*.txt file in your folder running the batch they will be deleted, so rename them or back up somewhere before running the batch.
NOTE 3: the batch deletes EVERITHING inside the <path to slipstreamed CD|folder> not found in the <path to original CD|folder> (as needed), so if u have some folders inside DO A BACKUP COPY before running the batch.

Could we start with step 1?

It says 1. Copy the office 2003 to the hard disk (referred from now on as X:\office2003). Does that mean that you simply overwrite any duplicate entries from one CD to the next, so that you have one folder that contains all the files from the 5 CDs? Or do you do each CD one at a time, and then use the standard AIO methods? It's kinda unclear from the original guide.

That much I can understand... just making the final product a little fancier.

This sounds like customization outside of the guide. I might have a look at this once I get the basics working.


If you don't set the cabinet compression to max (i.e. leave the , will the 5CDs optimize? You said that you got everything into 701MB and then 679MB at first (with the second using Project Client).


@tCP - Thanks! That makes things a little easier for cleaning up.

Right guys.... thank you....

marek722... This is a great piece of code you're handing us here... ... It took me while to get it through, iunno, not really reading the tutorial... lol... but i finaly managed to get my first updated Office 2003 MUI SP1 language pack running perfectly... using this method...

tCP... Dude i'll never thank ya enough for your little batch...lol... I can tell ya there's a lot to delete on a full MUI 6CD set...

well i'll get working on the other 49 languages left... lol... Txs again...

Do the standard 1 cd at each time.
Follow the exact procedure as described, separately for each cd.
That is you'd have to repeat the full procedure 5 times for 5 office cd's.

Regarding cabinet compression, let me specify waht I experienced,
All integration was done initially on Windows Server 2003 Enterprise edition which has makecab.exe already present in system32 folder.
So after following the guide, I had 5 folders for 5 cd's which I ran through cdimage.exe with optimization enabled and the final size was above 730mb
Now I deleted everything and followed the guide again, but this time replaced the makecab.exe in system32 fodler with the one found in cabinet sdk kit. That is replaced new makecab with old one.
This time around the final size of 5 folders was more than last time BUT after running it through cdimage.exe the optimized size was 701mb.
This size was for Sp1.

To save myself trouble, followed the same guide once again for Sp2, with the old makecab.exe and the final optimized size from cdimage comes to 679mb. (With the old makecab.exe from cabinet sdk)

Hope this makes things clear.

@Historic - Thanks for clearing that up... the original guide made it seem like you could do everything at once...

Hmm.... Ok. I've got CD1 done and re-cabbed. I've got a total size of 399MB. Is this the same as what others have? I've attached a listing of my directory structure just to make sure that what I've got is what I'm supposed to have.

I'm still not able to get the cache to work. I've replaced the regular setup.exe with the enhanced setup to allow for the ENFORCECACHE=TRUE option, but when I copy all the files over into my VM and try to install, I still get no cached installer anywhere on my harddrive (i.e. the msocache folder doesn't exist and the option to save the cache is gone).

ok, forgot to set email-notification on this topic ...

here now answers to your questions:

post #5, Historic:

1) ocw10.msi

This one is not included in an admin install. Don't know why and how although I tried many option when making an admin install. The result is not making an admin install but applying the patches with MSI 3.1 to the copied files on your harddisk. A useful side-effect of this is the still working lokal caching (-> msocache). I hoped the updates would still work as well this way - there is still no solution now.

2) "If I perform an admin image first, then copy over the original unaltered .msi's wouldnt the folder structure be different in the target source?"

No, the folder structure is generated from the .msi's and so it should work (did I test this case? Sorry, can't remember)

3) "Although I have yet to try this, I would like to ask if this switch might work while doing the first admin image? msiexec.exe /a pro11.msi MSINODISABLEMEDIA=1"

This switch is necessary if you want to create a install CD/DVD as far as I understand it.

4) "Along with this can we also enable Office Online Update??"

Actually no. But this is a feature I will look for, don't know now where to alter the install.

post #6, Historic:

1) "One more note: Some of the cabinets in different products having the same name do not have the same content, therefore 'the beef stew method' of creating AIO (supposedly vol.msdn cd method) is out of the question here."

All code was especially written to allow 'the beef stew method'. Later more on this one.

post #7, Historic:

Just a hint about size: my experiments endeed in a 540MB 5in1sp1-iso (no hotfixes included).

post #9, Zxian:

1) "How do you go about clearning out all the files that aren't on the original CD?"

This is something for a batch-job saw a solution later in the thread.

2) "Also... do you just take the files that are on each CD and simply copy them over into your working directory, overwriting any existing files?"

the working directory is a temporary directory where you copy all CDs overwriting existing files except the setup.ini and .xml files under /FILES/SETUP. If you rename setup.exe to setupxxx.exe and setup.ini to setupxxx.ini (for each product own name) the setups will continue to work. Seems I forgot to mention this because I started with a AIO version.

post #18, FaceMouth:

"Also, I am not able to make an admin install point with this version, and I think I will have to manually install my key, not sure if it is going to work in the mst file."

Strange, tested it and worked fine with 5in1sp1 (no other hotfixes). Looked like the original. Seems that more testing is needed and a new version including a framework for the main routines to make all easier ...

post #20, tCP:

Thanks for this contribution - didn't test it, maybe i'll include it in a new version later

post #24, Zxian:

"the original guide made it seem like you could do everything at once..."

That's the idea behind all. More explanations in next post.

post #25, Zxian:

you need enough free space for caching and it is not working with a admin install as starting point. Didn't try the enhanced setup.exe so can't help with this. In setup.ini the following should be included:



ok, next post with technical details ... this one is long enough

here we are again with few details about sort2cabs.js and the cabs on the original cds and how I understood the whole thing:

the cabs

On the original cds there are lot of duplicate cabs with same content. This way the products are easy to combine in different packages with more or less cds. Very important are the order of the cabbed files corresponding to the order in the different .msi files. That's the point sort2cabs.js is mostly dealing with.

'the beef stew method' for building an AIO cd only works because it is intended to work. As long as Microsoft is caring about this, sort2cabs.js will work (only very little error checking is included, sorry).

sort2cabs.js

When applying the patches .msi files get altered. New files are added and checksums corrected and badly some other things change (more investigation needed). Really ugly the whole thing gets because of new files which get already used sequence numbers thus destroying the possibility to compress files. This is what sort2cabs.js is supposed to repair

Shortly: sort2cabs collects all information about the files and there install order (sequence numbers). Because not all .msi use all files from the cabs, sort2cabs builds large arrays in memory and sorts the files using the order from all .msi. Some files appear in more than one .msi - those give hints how to sort. After that new sequence numbers are generated and written to the tables (you have to reimport with ORCA). This ordering is also used when generating the new cabs. Sounds easy, ins't it

other thoughts

I really don't know if the idea of just copying files to harddisk and then patching is intended. Somehow it works and gives better results than making an admin install. After I 'accidentally' found this way I belief it's the right one slipstreaming service packs to the install cd(s). Still some things get altered in the .msi files that prevent online updates and I hope to find them.

Optimizing the cd to find duplicate files is not really necessary when running sort2cabs.js on all parts together only once. In the result only setup.exe will be found as a duplicate file (if you rename it when copying files to harddisk). As stated before 5in1 with SP1 is only about 540MB.

One aspect is still unclear: in .xml you'll find a product id and source id. I belief those should change on a slipstreamed version to distinguish original from service pack versions - any one who knows more?

Ok, gonna track the topic now and give more answers ... and I'm planning to add more routines for easier slipstreaming ... if only the day had more than 24 hours

What I meant was that after all the 5 cd's are done re-cabbing and deleting extra files, the final size of all 5 folders is way above 700mb (Dont actually remember the exact size). So to burn all the 5 folders on 1 cd, the source folder containing all 5 folders is scanned for and optimized by cdimage.exe

Now I dont know if you made any change to sort2cab.js regarding the compression max-lzma or default ms-zip but for me the size is exactly 699mb for sp1 (And I put in autorun files etc.. and its 702mb and sizeon cd-disk is 703mb)

I cant figure out what I did wrong to not the size of 540mb like you did.
Any way this question is not important now as I already have an sp2 cd with final size of 679mb (incl. 2-3mb of autorun etc.)

Regarding the setup.xml, if you look at ocw10.xml, ocw11.xml and pro11.xml, get more idea that product id is the msi gui-id.
e.g. if pro11.msi has the product id of xyz when viewed through orca, the pro11.xml should have the product id of xyz.
similarly for owc10 and owc11.
Source id, is the same as product id, maybe a "close xml parsing" statement?
DownloadCode in .xml is the folder name inside msocache where the files will be cached. For my enhancements purposes, including rhd & sounds, kept the download-code the same as pro11 productid, so that files get cached in the same folder as office cache.

As For Proofing Tools vs sp2 edit with orca Directory table:
directory:
CWUBI86HelpMidFolder.3630F825_EED5_11D3_91FE_00AA0059F9F6
change defaultdir to:
.:WUBI86
directory:
WordBreakerFolder.31D1FCD7_F3CA_4A73_B34D_CA95CAEAB62E
change defaultdir to:
WORDBRKR

@marek722

When you plane updated your guide for Office 2003 SP2?

BTW Good work
dziubek

when next version is ready

Havn't slipstreamed SP2 till now but it should work the same way as SP1.

This is just bizarre...I've done exactly everything as per the guide (several times) and I still don't get even an option to cache the installer files. The check box in the last window of the installation page doesn't exist, just as if I had performed an administrative install (which I haven't).

I've used tCP's batch file to perform the post-cabbing clean up. When all is said and done, the final directory for CD1 is 399MB and the install works as normal (installs without errors) except for that annoying little non-existant check box.

Zxian do you have enough HDD space on virtual pc ?
I ran my tests on virtual pc initially and there was no cache folder
and no option to enable/delete cache as well. As I had setup minimum
required space to run test on virtual pc.

I installed on "real" system and everything went ok
with msocahce folder created with properly cached files/cabinets.
(Using enhanced setup.exe with enforcecahe=true command passed)

Here are my final sizes for all to reference using sp2.
There is no need for a separate guide for sp2, just follow the initial guide and
it works sp2 as well.

frontpage=189 MB (198,405,064 bytes) 94 files,14 folders
office11=400 MB (420,474,476 bytes) 151 files,19 folders
(this has additional remove hidden data tool, office sounds, outlook personal folder backup
extras included for each extra theres 1 extra folder and 3 files, + the original msi's
which comes to 13 extra files and 3 extra folders)
onenote=67.8 MB (71,124,549 bytes) 53 files,12 folders
project=119 MB (125,037,522 bytes) 107 files,18 folders
visio=219 MB (230,668,792 bytes) 126 files,14 folders.

Yup... the VM has plenty of free space on the hard drive (3.5GB should be enough.. right? )

I'll give it a shot on a real computer tonight though. We'll see if that works. *crosses fingers*

I just realized you left this post or I would have replied earlier.

My version is not the full package 5 disk. It's just a single trial disk I bought through school. The 5 disk set is the only one you are able to make an admin install point with (I know there is another thread relating to how to change the install options).

Anyway, I haven't really been playing with this much lately. I think I might work on my unattend disk more this week. School has been busy, but next week looks like a light work load.

I do have the 5 disk set, I really don't need all these programs though, and the academic version was more of a challenge. There are other things I want to work on also, so I am just going to add some of the programs from 5 disk set and move on to other stuff.

I know this was a long winded babbling poet, I got up at 5 after sleeping only 3 hours. Insomnia sucks lol

thanks again for a great guide

I think this guide would be a great sticky as well !!

Great guide, thought I was gonna manage SP2 on my first go, but no.

Shortly (about a minute) after running sort2cabs.js it errors


the file is there, any suggestions? I'm running a fresh install of winXP sp2 if that makes any difference

Thanks in advance,

Suicidal_Orange

Hi all,

First, thanks a lot to marek722 for is wonderful process and also TCP for is "delete batch"

I have followed carefully the instructions to build both "SP2 slipstreamed CDs" and "SP2 slipstreamed AIO CD" of my French Office 2003. Everything went fine during the process (no error from msiexec or from the .js script) and after the "delete batch" I get some SP2 CDs or an AIO CD which looks quite OK.

However when I try to install the five programs I get the following:

Office: NOK (Quickly, before asking for any serial number, I get a popup with "Error 2715. An internal error has occured (IPMAIN11.AW_1036)". Then the installation process is cancelled.

Project/Visio: NOK (Idem, with "Error 2715. An internal error has occured (F346 msdapml.dll.E8D71C4B_62C9_4D1B_A02F_C916CAE50331)". Then the installation process is cancelled.

Frontpage/Onenote: OK (Installation is OK, and programs seems to run OK).

Looks very strange, isn't it?

I have repeated marek722 process twice, being very carefully not to forget anything, but I get always this results, whatever on single or AIO built CDs.

Any idea why I get those weird errors on 3 out of 5 office 2003 components...? Could it be something linked to the fact I am doing it with a French Office 2003 + French SP2? Anything which could be language specific?

Thanks in advance,

Stellar7.

ON CAHCED INSTALL and Administrative Install Points
---------------------------------------------------

Microsoft has 2 differnt strategies for patching Office 2003.

1) Optomized for high-availability LAN

2) Optomized for low-availability LAN, slow-links, mobile, etc.


Option 1 and Option 2 are mutually exclusive. You must use one or the other.
http://www.microsoft.com/technet/itsolutio...ade_5.mspx#EEAA

Option 2 assumes you don't have a lot of bandwidth available and/or that you may be without LAN connectivity from time to time. It compensates for this with LIS (Local Install Sources). LIS keeps a copy of the media on your Local system. The patching stratergy here is based on the same assumption, no connectivity. This istall method favors patches and hotfixes. These are small and install individually. This is the right choice for mobile users or users with slow links.

Option 1 assumes you have a reasonably fast network available all the time. In this situation the network sources are updated en mass. The large scale changes can be easily pushed to the client without as much worry over validation and traffic interruption. THAT is why you can make an administrative install point and install SP1 or SP2 to it.


Once again, Option 1 and Option 2 are mutually exclusive. Therefore if you create an Administrative install point and slipstream it, you have chosen Option 1 and cannot benefit from LIS (Cached install)

On another note: Only Volume License copies of Office can be used for an Administrative install point. You can't buy it in the store and do these procedures.

Now what's my motivation in all this? I'm hoping somebody out there will prove me wrong and show me how to slipstream an SP2 install then repackage it to a compressed CD image that is capable of utilizing the LSI model. Like the rest of you, I want the best of both worlds.

Nice guide. I'm sure i would give it a try to replace my chained instal i have now.
But i still have some questions:
is it also possible to integrate mui Packs in the installation sources?
Or must i keep these installed with chained install?
And how should I slipstream updates for the MUI packs?

On the moment i have problems with the installation log. If i use the runonceEx command

Hello world

... just realized, that the thread-tracker is purged when no activity is seen - not good!

So here are some good news: finally I found a solution to use the update web pages from microsoft after slipstreaming (better say I managed to convice Office Update to accept my slipstreamed OFF2003SP1 and not to identify it as a administrative version). Looks like approaching the aim and going to build a slipstreamed Office 2003 that will act like the original release version. What's still broken are version numbers in the slipstreamed .msi - actually working on this.

Next steps will be: extend the scripts for easier use, include new changes, test a bit, rewrite the guide and give the code to you for more tests. Stay tuned and patient - this project consumes a lot more time than I can afford.

@paulvanleemput:
Can't test MUI version, but maybe it will work when the integration of other patches after the service packs will work. But this will be interesting after service pack slipstreaming is functional.

@polysulfide:
This project may proof that you are wrong. For instance LIS is already working after slipstreaming SP1. Don't know if I will succeed but I'm trying

@Stellar7:
hmm, looks like missing files. Maybe the new scripts will fix this, otherwise more investigations are nessessary.

@suicidal_orange:
still not tested SP2 cause all seems useless to me, if windows update/office update won't work.

@FaceMouth:
slipstreaming should not change admin install routines in the .msi, in other words if it worked before it should work after too. But I did not read the whole install routines.

next news should include success on updating a slipstreamed SP1 via windows update

I must be doing something wrong... will anyone lend me a hand? I'm using SP2, but I figured as other people have had success there must be some way of getting it to work.

I've tried both methods; 1 CD at a time and all 5 in one directory and both have had quirks.

1 CD at a time results in successful completion of sort2cabs.js and when I go to install the program it usually works. But under some configurations (such as installing Frontpage before Office) I'll get an error saying a CAB file was not found, and when I point it to that file it refuses to have it. Also, on a successful installation ticking the box to delete installation files does nothing (i.e. it doesn't remove the cabs in MSOCache).

5 in 1 is strange because at the end when it tries to calculate the MD5 sums of the cabinets it fails to find one and stops with an object error.

I might try SP1 to see if it makes a difference, but I think I'll wait for this project to ferment a bit futher first

EDIT: With a bit more toying around I've finally managed to make the beef stew method work. The same error occured as last time (just after cab creation is completed) but I decided to comment out the cab compression bit and run the script again, where it continued on as if the error didn't exist.

Cache options don't appear much like Zxian was describing, but I used the enhanced setup thingy with enforcecache=true and that allowed me to cache them.

Anyway thanks for the script marek722

I've just finished working with this slipsteaming method.
The results were great: I did it with SP2, it worked great. I did it also for MUI with SP2 and also wotked great.
The size of Office has shrinked by 2 MB; the size of MUI has become bigger by 7 MB.
I used the method 1 CD at a time.
NB: the file "finish_slipstream.bat" worked fine with Office but failed with MUI (it deleted all the contents), so I did it manually.
Great tool Marek722. Waiting for new updates from you.

Great News:
I created AIO CD (Office Pro, Frontpage, Visio, Project and MUI Arabic). Note that Office Pro contains (Access, Frontpage, Excel, Word, Powerpoint, InfoPath, Onenote, Outlook, Publisher) with SP2 for all of them.
The CD size 640MB and down to 596MB if using CDIMAGE (-o) option to optimize duplicate files
- 1st I compared the contents of the Office 2003 Pro CD with both the contents of Visio 2003 and Project 2003 and MUI Arabic CD. I found many common files including cabs on all these CDs.
- I moved the contents of them to their corresponding common folder with a unique change: renaming the "setup.exe" and its corresponding ".ini" file in \Files\Setup folder. For Example setupvis.exe and setupvis.ini for Visio instead of setup.exe and setup.ini (just not to conflict each setup of them)
- I downloaded the latest "setup.exe" from microsoft website and replaced each "setup???.exe" file by the new downloaded file.
- I had to leave one copy of the original "setup.exe" as it's used during this guide
- I've got an oringinal AIO CD without any SP or hotfix for it with a total size of 649 MB.
- I followed the guide of Marek722 to end up with the above result.

- I made the same test after including my "*.mst" files and end up also with a positive result.

- I checked for the updates on the microsoft website for all the installed applications: I just found these 2 hotfixes not installed:
* Update for Outlook 2003 Junk Email Filter (KB907492)
* Update for Office 2003 (KB907417)
and this is obviously true as these 2 hotfixes were not included in the SP2 release.

I'm planning to integrate them using the same method.


I can assure you that this guide works properly with SP2 instead of SP1.

Great work Marek722

Hmmm... whenever I try to do this I get an error after a while that says:



Any ideas what may cause this?

I am using a SP1 disk to begin with... and I slipstreamed the SP2 files to it.

Could this error be because I am starting with SP1 instead of a disk that has no SP?

This looks very interesting... but I am having no luck so far.

Edit: Well... It looks like that error is normal. I went ahead and finished the tutorial and everything seems to be working fine!
Thanks a lot!! This is awsome! It is a pretty confusing tutorial... but it does work. One thing missing from the tutorial is to make sure you copy the setup.exe file to the SORT directory.

I tried this with the danish version of office 2003 with SP2.
It works well, until I have to run the sort2cabs.js file, and it tells me to update the MSI files with the new tables. The problem is, that there is no new files to import, the sort directory contains no subfolders.

Any ideas?

btw. looking forward to an updated guide that doesn't require ORCA.

marek722 thanks a lot!! That's work!

Can you be a little more specific on which directory to place the makecab.exe and md5sum.exe? Should they be placed in the SORT folder?



I did not find any tables called *.new.idt, only the original table names were found.



I cannot restore all of the backed up ini files to X:\office2003\FILES\SETUP because I have 1 file from each of the 5 office discs, and these are all called setup.ini. They have the same name.

Help appreciated.

Hi hohner, this process can be a bit confusing at first and usually takes a few tries.

Put them in the path variable, as suggested. If you're not sure what's in your path variable, you can just put the files in the Windows folder (i.e. C:\WINDOWS or C:\WINNT) as that's always in the path.


There was probably an error somewhere, try it again after moving the two executables above. The cabbing and MD5Summing should take a small while before it prompts you.


Somewhere in the thread was the answer to that. For each setup.ini, rename it to setupxxx.ini, where 'xxx' is an abbreviation of the application. So, for example, Frontpage could be called 'setupfpg.ini'. For each ini file, you will need to make a copy of setup.exe and rename that accordingly. So for our 'setupfpg.ini' file, we'll have a 'setupfpg.exe' installer in the main directory.

For the Main Office 'suite', keep the original names 'setup.ini' and 'setup.exe'.

I have many, many question that I hope someone can help me answer. I keep trying and rereading everything but can't seem to understand it all. So here goes, sorry for the long post.


I am only testing this on the Visio CD first and am assuming that if I can do it with one CD the others should be able to be done in the same way. I am using WinXP. I am attempting this with SP2, using the correct full file updates for each program. In the end I want to make the AIO CD with a program in each file instead of the beef stew method.


I am correct that to remove the read only and hidden attributes from the files you do this after the admin install buy right clicking on the directory and unchecking those to boxes?

#1 in the instructions say to copy cd contents to the HD, I thought the only way to be able to slipstream was by doing and admin install, is this correct? If I just copy the CD contents to the HD the SP cant' update because the files are still in the cabs, correct?

#4 in the instructions say to get the XML files from the HD but when i do and admin install there is only the setup.ini in that folder and no XML files. I have to copy the XML file from that directory on the CD and put it in the sort folder. Is this ok, or am i supposed to have the XML files where the instructions say to get them from?

#4 in the instructions say to edit the tabledirs.lst and xmlfiles.lst to meet my needs. Does this mean to edit it so that the tabledir.lst says e.g. C:\Visio\sort\vispro? Or does it just mean to have the name already like it has them but keep the ones for what you are doing and comment(#) out the others?

the first few times i ran the script it did not make the cabs. After looking at the script and comparing it to the file names that ORCA exported the tables as I noticed they were different(e.g. Componen.idt, Director.idt, CabinetD.idt, the File.idt and Media.idt were correct). Did i do something wrong, miss something or does ORCA actually export the table names incorrectly?

does the msi need to be anywhere specific? i just left it where the admin install put it.

in post #45 Siginet says that the setup.exe needs to be in the sort folder, is the correct? it wasn't in the original instructions and others seemed to have got it to work without supposedly knowing about this, so does it actually need to be placed here?



so when i get things to sort of work it makes all the cabs and then i think it starts to calculate the md5's and i get this error.


----------------------------------------------------
...

creating J5614D01.CAB:

Microsoft ® Cabinet Maker - Version 5.1.2600.0
Copyright © Microsoft Corporation. All rights reserved..

43,576 bytes in 1 files
Total files: 1
Bytes before: 43,576
Bytes after: 15,490
After/Before: 35.55% compression
Time: 0.09 seconds ( 0 hr 0 min 0.09 sec)
Throughput: 472.83 Kb/second
calculating md5 for O1561403.CAB (12936423):
md5sum: O1561403.CAB: No such file or directory

Error: [object Error]

C:\Visio\sort>
------------------------------------------



Where are the cabs supposed to be put when they are made?

For me they are, in in this case, in C:\Visio. If i move them to the sort folder and run the script again it again puts the cabs in C:\Visio but it gets past this part seeming only because I have moved the cabs to the sort folder.
Should I have to move the cabs?


It makes the new CabinetDetail.idt. I then edit the VISPRO.MSI in ORCA and hit enter to continue the script and get this error.

-----------------------------------------------
xml files found: VISPRO.XML
modifying VISPRO.XML
md5sum: AER_1033.ADM: No such file or directory

Error: [object Error]

C:\Visio\sort>
--------------------------------------


Two things here:

1. I compare the supposedly modified VISPRO.XML with the original and they are both the same. What needs to happen for the XML file to actually be modified?

2. I look and this file (AER_1033.ADM) is in C:\Visio\FILES\WINDOWS\INF. So i dont know where the script is looking for this file and where any files it will look for after this should be place. Where should ALL the files be so the the script knows where they are at?



At this point in time I am stuck and don't know what to do. Any help with these issues is greatly appreciated. Thank You Very Much in advance. I have more question but this will do for now.

Hello AgentZero


In theory this should work. When I tried it this way, I had problems (see post #42), so I can only help you to that extent. Do note that once you have managed to re-compress all the cabinet files for each Office CD, you'll need to use a tool that optimises the CD so that duplicate files are not stored more than once. I used UltraISO for this, but there are others around.


Yes. Also make sure it un-sets the attribute to all subdirectories and files too when it asks.


You are right, but I think you missed something. The idea of this procedure is to:

• Turn the install CD(s) into admin install image(s) (it takes the files out of the cabs), and slipstreaming the service pack into it. [Steps 1+2]
• Create a directory structure to hold the updated files and original installation tables. [Steps 3+4]
• Recompress the updated files into cabinets by using the original cabinet names stored in one of the tables. [Step 5]
• Update the MD5Sums of the files so that the installation procedure is successful by importing them with Ocra. [Step 6]
• Remove all unnecessary files and restore original XML files. [Step 7]

The file it asks for is identical to the one on the CD. But that file should be there; are you sure you did the admin install as it asked?


It's asking for the directory you made in the sort folder for (in this case), Visio. So in the file you should delete all the others and put in 'vispro', if that was the name of the folder you made.


Oh, I remember this. I had the same problem. It's Ocra, it doesn't export all of the Long File Name - so what you have to do (by hand, unfortunately) is rename them to what they want.

Componen.idt = Component.idt
Director.idt = Directory.idt
CabinetD.idt = CabinetDetail.idt

That should fix it.


It should be fine where it is, just remember to give whatever commands need it the right path.


I managed to do the (beef stew) procedure without doing such a thing, so unless it is explained further I don't see how it would do anything.


In C:\Visio. All cabs from the CD should now have been deleted so that the new ones can be put there. This might have failed due to previous errors, though. Try it again after fixing the table name problem above.


I don't think so, no.


It's supposed to update the MD5Sums contained within it. They're going to change due to the new cabinet files.


It should only be looking at cabinet files.


I hope what I have said helps you in some way. Again, when I tried the individual AIO method it failed to install properly for me, and the original method was designed for 'beef stew', but perhaps you'll have better luck.

(Sorry about the quotes not showing up properly, not sure what's up with them)