BOB!

I can't thank you enough, and boy am I ashamed to have missed that silly
little backslash!

The first part of the command file ran without errors to apply SP1 to the
main Office 2K3Pro file. However, the second line of the command file still
fails as before (the one that is supposed to spatch the OWC11.msi file). I
have tried to recheck all my typing on this second command line (and have
removed the ; from its beginning) , but can find no typo in it. There are
two OWC*.msp patches in the fullfile download. OWC11SP1ff.msi and OWC
10200SP1ff.msi. I have NO IDEA which to apply to the OWC11.msi file, but
assumed that I should use the one whose filename was most similar to the
original msi filename, since Microsoft provided such fine guidance in its KB
article about how to patch the admin instal ;{).

Any further guidance from you would be greatly appreciated -- and once
again, MANY THANKS for the enlightenment!

Steve
"Bob Buckland ?:-)" 75214.226(At Beautiful Downtown)compuserve.com wrote
in message ...
Hi Steve,

There is a 1314 error (bad path) in the log file
for the MainSP1 when it's trying to find the PRO11.MSI

If you look at the log file it appears that you're
pointing to the MSI at

D:Software...

rather than
D:\Software...

If so, there's no way for Windows to know to start at
the root level of the D:\ drive when it's trying to
follow the path.

As for the root names question. The MSI files are edition
specific (i.e. Professional, Standard, Basic, etc) where the
updates are usually Version (2003) wide.

=========
"Stephen Longmire" wrote in message
...
Sorry for the repost, but I am desperate for a solution to this problem
which is holding up deployment of Office 2003 Pro Enterprise Eidition.

Per Glenn's suggustion I have now attached three files: the CMD file I
used
to try to apply the patches to the admin install point, as well as the two
log files generated during the failed patch attempts.

I've read and read the KB articles. I've carefully fully specified the
filenames of the MSP and MSI files, but I get the same error message
telling
me that "This is not a valid Windows Installer Image file." Well Both of
the files in question ARE, as I can run them on their own.

I am also frustrated by the fact that the Full File version of the SP1
extracts to MAINSP1ff.MSP, whereas the filename of the install file for
O2k3Pro is PRO11.MSI. Shouldn't M$ have made the root names at least
similar???

How can I patch this admin install? ANXIOUSLY awaiting enlightenment
........

Steve
--
Let us know if this helped you,

Bob Buckland ?:-)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/a...andtricks.mspx