Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

slipstream Office 2003 SP1 & rebuild CD

* * * * * 6 votes

  • Please log in to reply
106 replies to this topic

#1
marek722

marek722

    Newbie

  • Member
  • 12 posts
  • Joined 12-March 05
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 :lol:

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:

msiexec /a X:\office2003\PRO11.MSI /p X:\SP1\MAINSP1ff.msp MSINODISABLEMEDIA=1 SHORTFILENAMES=TRUE PIDKEY="xxxxxxxxxxxxxxxxxxxxxxxxx"
msiexec /a X:\office2003\OWC11.MSI /p X:\SP1\OWC11SP1ff.msp MSINODISABLEMEDIA=1 SHORTFILENAMES=TRUE PIDKEY="xxxxxxxxxxxxxxxxxxxxxxxxx"
msiexec /a X:\office2003\OWC10.MSI /p X:\SP1\OWC102003SP1ff.msp MSINODISABLEMEDIA=1 SHORTFILENAMES=TRUE PIDKEY="xxxxxxxxxxxxxxxxxxxxxxxxx"
msiexec /a X:\office2003\FP11.MSI /p X:\SP1\MAINSP1ff.msp MSINODISABLEMEDIA=1 SHORTFILENAMES=TRUE PIDKEY="yyyyyyyyyyyyyyyyyyyyyyyyy"
... (and so on for all your components)

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:
cscript sort2cabs.js
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 :thumbup

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 :P ). 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 :huh:

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.


How to remove advertisement from MSFN

#2
eSouL

eSouL
  • Member
  • 1 posts
  • Joined 03-February 05
What is ORCA?

#3
samra

samra
  • Member
  • 1 posts
  • Joined 17-June 05
Thank You very match , No Any Problems .

#4
Historic

Historic

    Newbie

  • Member
  • 25 posts
  • Joined 13-September 04
Thanks, gonna give a try on this. Looks very interesting to me.

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

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


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??

Edited by Historic, 25 August 2005 - 01:51 AM.


#5
Historic

Historic

    Newbie

  • Member
  • 25 posts
  • Joined 13-September 04
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.

#6
Historic

Historic

    Newbie

  • Member
  • 25 posts
  • Joined 13-September 04
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>

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

#7
Historic

Historic

    Newbie

  • Member
  • 25 posts
  • Joined 13-September 04
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.

#8
Zxian

Zxian

    Scroll up - see the Google bar?

  • Super Moderator
  • 5,066 posts
  • Joined 30-September 04
  • OS:none specified
  • Country: Country Flag
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?

#9
Zxian

Zxian

    Scroll up - see the Google bar?

  • Super Moderator
  • 5,066 posts
  • Joined 30-September 04
  • OS:none specified
  • Country: Country Flag
@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.

#10
marek722

marek722

    Newbie

  • Member
  • 12 posts
  • Joined 12-March 05
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.

#11
Zxian

Zxian

    Scroll up - see the Google bar?

  • Super Moderator
  • 5,066 posts
  • Joined 30-September 04
  • OS:none specified
  • Country: Country Flag
HE'S BACK!!!!

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

#12
Zxian

Zxian

    Scroll up - see the Google bar?

  • Super Moderator
  • 5,066 posts
  • Joined 30-September 04
  • OS:none specified
  • Country: Country Flag
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.... :(

#13
benase

benase
  • Member
  • 2 posts
  • Joined 03-September 04
Thank you marek722!
I make a 5IN1 AIO CD with slipstreamed SP2, and replaced some code as below for MAX compress ratio:

oExec = wsh.Exec("cabarc -m lzx:21 n ..\\" + i + " @" + i + ".ddf");

// oExec = wsh.Exec("makecab /D CabinetNameTemplate=..\\" + i + " /F settings.ddf /F " + i + ".ddf");


Edited by benase, 07 October 2005 - 06:04 AM.


#14
FaceMouth

FaceMouth

    What the hell is this thing?

  • Member
  • Pip
  • 71 posts
  • Joined 10-September 05
  • OS:Windows 7 x64
  • Country: Country Flag
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.

:thumbup
Bleach gets you young, so I've been told. Cause no one who drinks it lives to get old.

#15
Zxian

Zxian

    Scroll up - see the Google bar?

  • Super Moderator
  • 5,066 posts
  • Joined 30-September 04
  • OS:none specified
  • Country: Country Flag
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... :realmad:

#16
FaceMouth

FaceMouth

    What the hell is this thing?

  • Member
  • Pip
  • 71 posts
  • Joined 10-September 05
  • OS:Windows 7 x64
  • Country: Country Flag
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 :realmad: )

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.

Edited by FaceMouth, 13 October 2005 - 12:58 AM.

Bleach gets you young, so I've been told. Cause no one who drinks it lives to get old.

#17
Historic

Historic

    Newbie

  • Member
  • 25 posts
  • Joined 13-September 04

@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.


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.

Attached Files



#18
tCP

tCP
  • Member
  • 1 posts
  • Joined 14-October 05
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.

Edited by tCP, 14 October 2005 - 03:44 PM.


#19
Zxian

Zxian

    Scroll up - see the Google bar?

  • Super Moderator
  • 5,066 posts
  • Joined 30-September 04
  • OS:none specified
  • Country: Country Flag

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

Could we start with step 1? :lol:

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.

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

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

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.

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

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.

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. :thumbup

#20
XXsplit

XXsplit

    Newbie

  • Member
  • 18 posts
  • Joined 24-March 05
Right guys.... thank you....

marek722... This is a great piece of code you're handing us here... :thumbup ... 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...

#21
Historic

Historic

    Newbie

  • Member
  • 25 posts
  • Joined 13-September 04
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.

#22
Zxian

Zxian

    Scroll up - see the Google bar?

  • Super Moderator
  • 5,066 posts
  • Joined 30-September 04
  • OS:none specified
  • Country: Country Flag
@Historic - Thanks for clearing that up... the original guide made it seem like you could do everything at once...

#23
Zxian

Zxian

    Scroll up - see the Google bar?

  • Super Moderator
  • 5,066 posts
  • Joined 30-September 04
  • OS:none specified
  • Country: Country Flag
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).

Attached Files



#24
marek722

marek722

    Newbie

  • Member
  • 12 posts
  • Joined 12-March 05
ok, forgot to set email-notification on this topic ... :whistle:

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:

[Cache]
; The cache section provides settings for caching the install source locally 
;	   Value		   Default		 Description
;	   CDCACHE			2			 Option to specify cache level 
;									   [auto, 0, 1, 2]
;	   LOCALCACHEDRIVE <predefined>	Option to specify a drive to cache 
;									   the install source to
;	   DELETABLECACHE  1				Option to display UI to remove the 
;									   cache at the end of setup [0,1]
;	   PURGE		   0			   Option to always remove cache at end of 
;									   setup [0,1]
CDCACHE=auto
;LOCALCACHEDRIVE=C:\ 
DELETABLECACHE=1
PURGE=0

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

#25
marek722

marek722

    Newbie

  • Member
  • 12 posts
  • Joined 12-March 05
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 :yes:

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 :P

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 :lol:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users