I am working on a Windows desktop that has 3.4.x [.5 or .6] on it.
I am using Control Panel to remove it before I install 3.5.5.
Well it has taken over 1/2 hour to remove it, and still has time to go.
This is on a Sempron 3500+ CPU, 512 MB ram, running XP.
This very slow removal is also happing on a much faster XP CPU laptop [1
GB ram] and a Vista dual core laptop [3 GB ram].
For this Sempron CPU machine, I will be installing 3.5.5 for a friend.
The drive is defraged and there is not much running in ram, like
security programs.
I noticed that on the Vista dual core laptop, the Ubuntu boot version of
LO removed many times faster than on the Windows version, when I did the
3.4.6 to 3.5.5 upgrade on both Windows boot and Ubuntu boot.
SO, and not to bash Windows, is there any problems/issues with LO
removal on Windows, before upgrading to the next line, that makes it so
much slower than it should be? The installing is so much faster, like 5
times as fast as fast.
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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
- [libreoffice-users] why does Windows version take so long to remove? · webmaster-Kracked_P_P
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.