teknow <teknowledgist@gmail.com> writes:
My less OSS friendly colleagues decided it was LO's install process
that was at fault and uninstalled it while arguing that it shouldn't
be installed in the first place. That just made it worse because
then additional MS Office file types were "broken". Running a
repair-install of MS Office 2010 fixes the problem, but only for the
currently logged in user - all existing users (and any future users
if the default profile isn't re-generated) have .doc files that open
in WordPad, and .xls files that have no association.
Been there, done that; was with OO.o; about 24 months back. Never caused
a problem though, because both Windows and MS Office are clean
re-installed every 2-3 months anyways.
This is what happened - a friend wanted to try an alternative to MS-o;
and I recommended OO.o. The machine however had very low RAM, and OO.o
was toooo slow. He finally uninstalled OO.o; and later complained that
file associations were too messed up, that he had to re-install MS-O.
--
Mahesh T. Pai ||
Learn from the mistakes of others.
You won't live long enough to make all of them yourself.
--
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
In case of problems unsubscribing, write to postmaster@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.