No MsoCache with slipstreamed SP3

[jetjackson]

Greetings all, newbie here at the Board.
I have read many of the posts in the threads here, and not been able to find one that addresses my problem, if there is, please excuse.
I have been trying to Slipstream Office 2003 with SP3. The slipstreaming has worked (thank you) and I was able to chain link the 2007 File Format converters (thanks again). The problem I have, is that whatever I have or have not done, the Slipstream process has not cached the install files as in "MSOCache", which a normal install will do, so when I need to add a feature the Office Installer asks for the original install disc.
Has anyone got any clues as to what I may have done incorrectly, or what I can do so that the Slipstreamed install, does cache the installer files.

Cheers,
Jet.

[mr_smartepants]

The MSOCACHE folder is a hidden folder. Make sure you have "show hidden files/folders" checked.

[jetjackson]

The MSOCACHE folder is a hidden folder. Make sure you have "show hidden files/folders" checked.


Thanks for that,,,,I did check and I do have all files and folders "unhidden"


If you read my post, I say that because the Slipstreamed install hasn't cached the files in the MSOCache, I am asked for the original disc when some extras are needed to install. :)


This is what I would like to know,,,,,how to ensure that the files are cached.


Cheers,
Jet.

[mr_smartepants]

I misunderstood. Sorry.

[Siginet]

You need to replace your setup.exe files with the enhanced setup.exe from microsoft:
http://download.microsoft.com/download/C/4/A/C4A1310D-4C72-40AC-B317-55347270504C/EntSetup.exe

Plus you need to add this to your setup.ini files in the "Files\Setup" directories.

[Cache]
ENFORCECACHE=Y
DELETABLECACHE=1

If you do this it will allways be cached no matter what.

[jetjackson]

You need to replace your setup.exe files with the enhanced setup.exe from microsoft:


Plus you need to add this to your setup.ini files in the "Files\Setup" directories.

[Cache]
ENFORCECACHE=Y
DELETABLECACHE=1

If you do this it will allways be cached no matter what.


Thanks friend, for this info. :)

I will re-compile my Office/SP3 disc with this extra stuff and report back here with my results. :)


Cheers,
Jet.

[jetjackson]

Well, I have tried recompiling with the added .ini file entry and also the enhanced M$ setup file, and I still have troubles with no "MSOCache". I have tried various code switches in the .ini file to see if they made a difference.
Why I need and want the MSOCache is because there are installations of this MS Office 2003 using a Volume License on different machines. If these machines (different users and different locations) need extras added by the user, then with no Corporate disc and no MSOCache, then they cannot add the desired extras.

Here are some screen snaps of the Explorer window and error messages:

Screen 1 (http://i14.photobucket.com/albums/a337/jetjackson/Screen1.jpg)

Screen2 (http://i14.photobucket.com/albums/a337/jetjackson/Screen2.jpg)

Screen3 (http://i14.photobucket.com/albums/a337/jetjackson/Screen3.jpg)


If I do a normal install of Office 2003, that will cache the install files, and if I then do an update with Service Pack 3, all is fine.
What I am trying to avoid is all the unnecessary installing.


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

Here is the Setup.ini:


; Microsoft Office SETUP.EXE settings file.

[MSI]
; The MSI section gives the name of the MSI file to install. This file must be in
; the same folder as Setup.exe, and both must be in the root of the installation
; tree.
MSI=PRO11.MSI

[Product]
ProductCode={***********************}
ProductName=Microsoft Office 2003
ProductVersion=11.0.8173.0
Recache=1

[MST]
; The MST section gives the full path to a transform that should be applied.
;MST1=\\server\share\some transform.mst
;MST1=D:\transforms\my transform.mst

[Options]
COMPANYNAME=********************
; The option section is used for specifying individual Installer Properties.
;USERNAME=Customer
;COMPANYNAME=my company
;INSTALLLOCATION=C:\Program Files\MyApp

[Display]
; The diplay section is used for overriding the default UI
; Value Default Description
; Display full Option to override the default UI
; [none, quiet, basic, reduced, full]
; CompletionNotice Yes Option to display a setup completion
; notice for otherwise quiet setup
;Display=None
;CompletionNotice=Yes

[Logging]
; The logging section provides settings for controlling the Setup log files.
; Value Default Description
; Type vpiwaeo Logging modes
; [a, c, e, i, m, o, p, r, u , v,
; w, *, +]
; Path %TEMP% Path to create logfiles
; Template SetupLog(*).txt File name for log file should end in
; "(*).txt"; the * is replaced with a 4
; digit number to make the file name unique
Template=Microsoft Office 2003 Setup(*).txt
Type=piwaeo
;Path=\\MyServer\logfiles\
;Template=Product %UserName%(*).txt

[MinOSRequirement]
; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.
VersionNT_1=500
WindowsBuild_1=2195
ServicePackLevel_1=3

[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
ENFORCECACHE=Y
PURGE=0

[OfficeWebComponents]
MSI=OWC11.MSI

[OfficeIntegrator]
Website=http://www.siginetsoftware.com/forum/
OIVersion=1.1.0.18
Method=Admin Install Point
Service Pack=Service Pack 3 (SP3)
KB923618=Office 2003 Service Pack 3 (SP3)

[ChainedInstall_1]
TaskType=exe
Path=Files\Setup\ChainedInstall_1\FileFormatConver ters.exe
Cmdline=/quiet /passive /norestart
IgnoreReturnValue=1



;;;;

Any ideas please?



Cheers,
Jet. :confused:

[Lions]

Hi jetjackson,

I compared my Setup.ini (of a perfectly functioning setup CD) with your, and i noticed only two small differences (except for "ChainedInstall" section, which I did not use):

1)
CDCACHE=auto (in your Setup.ini)

and
CDCACHE=2 (in my)

but I think it is irrelevant to your problem,

2)
[OfficeIntegrator]
Method=Admin Install Point (in your Setup.ini)
and
[OfficeIntegrator]
Method=Direct Integration (in my).

Have you tried using the "Direct Integration" method instead of the "Admin Install"?

Maybe the Admin Install is a procedure for sharing an install source that does not provide for the creation of the MSOcache directory.

Ciao

Lions

[jetjackson]

Hi jetjackson,


Have you tried using the "Direct Integration" method instead of the "Admin Install"?

Maybe the Admin Install is a procedure for sharing an install source that does not provide for the creation of the MSOcache directory.

Ciao

Lions


Thanks friend for your input.
My last two compiles with the additions suggested by Siginet were done using the "Admin" install. I have tried both methods previous to these, but I will try the "Direct Integration" with the additions. One thing with the "Direct" method, is that it takes quite a while to compile, and as I was keen to try the new additions, I opted for the "Admin", which is much quicker in compiling.

I will re-compile and report back here. :)


Cheers,
Jet.

[jetjackson]

Well, I am still in bother with this Slipstream task. :confused:

I must be doing something wrong. I have made the additions suggested and still not been able to get it right.

To make it easier or quicker, I had copied all the files from my original Office 2003 disc, to a folder on my HDD, and had been trying the slipstream from those files. I have done various compiles using both the Admin and Direct methods, and after writing to CD R/W disc, not been able to get the Slipstreamed version to install and to have the installer files cached as normal in the MSOCache directory.
I did have another go, this time directing the Office Integrator to the CD in the ROM drive and using the Direct Integration. This did take over 46 minutes to compile into the selected destination folder, the size of this folder is over 1gb, see pic.

Screen4 (http://i14.photobucket.com/albums/a337/jetjackson/Screen4.jpg)


When I had done the Slipstream, using the files copied from CD to HDD, the folder was only about 640mb.

I am so confused,,,,I must be doing something wrong :confused: :mad:

[jetjackson]

Thanks for all advice, I have sorted out the issues I was having and am now able to report that my Slipstreamed Office 2003 and SP3 have installed properly and the MSOCache has been written to default drive.

Thanks again :)

Cheers,
Jet :)

[Siginet]

Thats great news. :)

May I ask what you found to be the problem?

[jetjackson]

Thats great news.

May I ask what you found to be the problem?


Well,,,,,,,I think some of the problems I had may have been my doing. In an attempt to make things easy :D I copied the content of my Office 2003 CD, to a folder on hard drive. Here I replaced the old setup .exe with the "Enhanced" setup .exe, the modified .ini file and then started the compilation with "Office Integrator".
When I started the compile using the "Direct" method, things progressed very slowly. It took about 46 minutes to complete, but the content of the "Destination" folder was about 1.2gb. I tried the "Admin Install" option, this took only about 4½ minutes and folder size about 680mb.
After each compile, I burnt to CD R/W disc (made 2 coasters in earlier attempts) ;)


I banged my head a few times trying to work out what I was doing wrong, read and re-read the help files and left the job for another day :(

Next task I did the whole process again, this time selecting the original Office CD as the source and used the "Direct" method. This time the job took about 56 minutes, but the destination folder size only 480mb.
I burnt this to CD R/W and tried the install,,,,,,success :D

So I am not really sure what was causing the errors. Could it have been because I copied the CD content to hard drive?


Cheers,
Jet.

[Siginet]

The direct integration method does take much longer due to the fact it is overwriting older files in the cabs. So it must recompress every cab file.

[marockee]

cache is still not working for me. I did everything as said here (direct integration, from CD, new setup.exe, switches), but still no delete-cache-dialog at the end of setup, and MSOCache folder is created but setup still asks for CD when I try to add feature...now, what am I doing wrong? :(

thanks

[marockee]

anybody? :confused:

[benners]

anybody? :confused:

I don't know the reason for this but I have noticed that some of the Office 2003 apps like onenote etc don't show the cache dialog at the end.

Also for 2003 there have to be a few conditions met.
* One of the available hard drives has more than 1.5 gigabytes (GB) of free disk space available.
* The hard disk with sufficient space is not a removable drive or a network drive.

The cache folder is not always located on the drive with the most free space. As long as the two conditions above are met it will favour an NTFS drive, from what I remember reading on the MS site.

[marockee]

first of all, sorry for not answering earlier, now I found time to play with this stupid thing

unfortunately, I'm not installing OneNote and I'm not such newbie to not have enough space or can't see hidden files :)

so, after trying several combinations I found that:

1) if I use custom MST file, MSOCache folder is created when the installation starts and then immediately deleted, so not good

2) if I don't use MST, which is also not good, MSOCache is created as it should be, but I still don't get dialog to delete it at the end of install (this dialog is not really important as I leave cache in 99% cases, but it bugs me)

so, as I don't plan to move to 2010 soon, if anybody can help, thanks :)

[marockee]

please? :)