Hi!
Im trying to deploy Office Compatibility Pack but have a problem with documents opening by doubleclicking on the .docx files. The Compatibility Pack writes the "dos shortnames, eg. c:\Progr~1\..." as open path to winword, when this happens Word freaks out (?!?!?). The sollution is to change it to "long winodws names". I could do it by a custom action, but it is several registry entries to change.

My quistion is: is there a way to change this in the .mst file, some property to overwrite that the msi takes the office path from, that I could overwrite? An example of a registry key that should be altered:
"HKEY_CLASSES_ROOT\Word.Document.12\shell\Open\command"

kindly,
Piotr
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi Piotr,
this sounds like a long/short file name issue on installation.
Make sure, 'Long Filenames' is selected in the Summary Info dialog.
And that you not have set to use 'short filenames' thru a policy accidentally.
If you don't get further, please log the installation and post the log to senduit.
Regards, Nick
Answered 06/23/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
thanks for the reply.
My .MST file don't get any Dialogs under Setup Editor->Dialogs->All Dialogs...just a bug, or maybe I have missed something?

kindly,
Piotr Kuczkowski
Answered 06/23/2008 by: piotr.kuczkowski
Orange Belt

Please log in to comment
0
I don't understand why Word would "freak out": a normal registry will be chock-full of short path and file names. I can practically guarantee that other entries for it will feature them....
Answered 06/23/2008 by: VBScab
Red Belt

Please log in to comment
0
I don't undrestand that part either, neverless it creates a problem... If I manually alter the path to long names it works perfectly, why no one of us udnerstands....
Answered 06/23/2008 by: piotr.kuczkowski
Orange Belt

Please log in to comment
0
ORIGINAL: piotr.kuczkowski

I don't undrestand that part either, neverless it creates a problem... If I manually alter the path to long names it works perfectly, why no one of us udnerstands....


Explain, and start from the beginning, where did you get the media, what did you do to it, how did you package it, how did you install/deploy, etc. From the information you've given it would be impossible to tell you what the problem is. Windows Installer understands "Short paths" so no reason their presence would make word "freak out" -- we've installed the compat pack across thousands of machines and nobody's reported anything like this.
Answered 06/23/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Allright here it comes.....
1) I retreived the msi file "officecompatibilityoack.msi, o12Conv.cab + the folder Catalog from the FileFormatConverters.exe that I downloaded from microsoft
2) Made a mst file just to be able to hadle version the way we do
3) installed it on a test PC... it works on the stationary PCs but not on the laptops.. weird
The error consist of, if you doubleklick on a .docx file and close Word (not the document but the whole application) you get an error message "Microsoft Word has experienced an error and have to end" and it asks if i want to repair my document (but in swedish so I dont have the exact english error text).
If I start word and open the file from the application, it works perfectly.
So the conclusion was maybe there is an error in the fileassociation. When I checked for a difference between the doc and docx association the doc files had windows long names and the docx dos short names. So I changed the docx to the whole path and "Tada..." it work perfectly....

I agree that this is weir, neverless I still have the problem and need to send the compatibility pack out....
Any suggestions?

kindly,
Piotr
Answered 06/23/2008 by: piotr.kuczkowski
Orange Belt

Please log in to comment
0
ORIGINAL: piotr.kuczkowski

Allright here it comes.....
1) I retreived the msi file "officecompatibilityoack.msi, o12Conv.cab + the folder Catalog from the FileFormatConverters.exe that I downloaded from microsoft
2) Made a mst file just to be able to hadle version the way we do
3) installed it on a test PC... it works on the stationary PCs but not on the laptops.. weird
The error consist of, if you doubleklick on a .docx file and close Word (not the document but the whole application) you get an error message "Microsoft Word has experienced an error and have to end" and it asks if i want to repair my document (but in swedish so I dont have the exact english error text).
If I start word and open the file from the application, it works perfectly.
So the conclusion was maybe there is an error in the fileassociation. When I checked for a difference between the doc and docx association the doc files had windows long names and the docx dos short names. So I changed the docx to the whole path and "Tada..." it work perfectly....

I agree that this is weir, neverless I still have the problem and need to send the compatibility pack out....
Any suggestions?

kindly,
Piotr


That sounds right, same way we got it set up. Just a thought....did you try restarting the computer. Also you said it works the second time. Had Word been opened before the first time (double clicking docx with error), or are you talking about a fresh build. Try opening word and closing it before opening the compat pack for the first time. or double clicking your docx file.
good luck that does sound strange.
Answered 06/24/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
nono....it NEVER works when having the short filename... and I the strange part is that its only word that gives me this errer... Yes Word has previousely been installed and used.
I solved the "problem" with a custom action that alters the path to "long path name"... not the best way to go but "if its stupid and works its not stupid" right?

thaks for your input guys,
kindy Piotr Kuczkowski
Answered 06/25/2008 by: piotr.kuczkowski
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity