On 12/7/2016 11:29 AM, Philip Jackson <philip.jackson@nordnet.fr> wrote:
It would be nice if I could just create a VB machine and tell it to load
the hard disk which already has the workable installation of Windows 10,
together with the couple of applications I use from time to time.
You mean something like this:
https://www.virtualbox.org/wiki/Migrate_Windows
?
Trying to just use an existing partition/install is possible with VB,
but you will encounter issues occasionally. The above is a much cleaner
way to go.
Also, if you have problems re-activating, it is usually very painless
and automated - you call a toll free number, walk through the prompts,
and get a new code to activate. I've done this many times and never not
gotten reactivated, but everyone has to decide on the moral question
regarding the licensing.
--
To unsubscribe e-mail to: users+unsubscribe@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
- Re: [libreoffice-users] MS Anniversary upgrade warning - not LO issue (continued)
Re: [libreoffice-users] MS Anniversary upgrade warning - not LO issue · Tim---Kracked_P_P---webmaster
Re: [libreoffice-users] MS Anniversary upgrade warning - not LO issue · Virgil Arrington
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.