goog64 wrote:Reorx wrote:On the basis of what you have written in your first post in this thread - Doing a destructive upgrade (overwriting your current installation) might be something you want to avoid completely. As an alternative, I might suggest >>>
...........
2) If the system is a laptop, I suggest getting another "economical" laptop..............
Good luck...
Hi Reorx,
That's what I'm trying to find out i.e. whether it "might be" something to avoid or "is" something to avoid.
OK, I'll be less diplomatic/subtle - it IS something to be avoided if you value your time or digital stockpile. Destructive upgrade is working without a net in the sense that if you trash something about your virtual box setup, you can not recover other than restoring an image and starting from scratch... that is IFF your image is "good" (i.e.restorable). The only way to know if your image is restorable is to actually restore it... of course if you were experienced in using imaging software in this fashion, you could be confident on the restorability issue... but you're not experienced and there is no easy way to get experience... The data isn't the problem - that is a simple copy operation... the problem is that you do not have a Win disk to recreate your VB/VM in the event that the port over does not go according to plan... the processes being described in this thread are just a bit complex for a neophyte to accomplish successfully on the first try... there are many opportunities for errors even if only minor... any error could rapidly deteriorate into an unretrievable disaster. If you have a good, restorable image, even a disaster can be quickly recovered from and all you have lost is your time/effort. Do you have a good restorable image? I'm not completely sure and I don't think you are either - so this all boils down to gambling... do you really want to gamble with your data? You can if you like but there is no shortage of threads here that are authored by users who have lost data and hope to recover it... some succeed but most don't... Ultimately, it's your call but I occasionally teach students at the graduate level that deal with important issues and it seems as though they are always in a hurry... I have told them on more than one occasion that it seems as though there is never enough time (resources?) to "do it right" the first time but there is always enough time (resources) to do it over again or to wish that you could (sometimes you don't get a second chance)...
goog64 wrote:Thanks, but I can't afford another laptop
Sorry that $250 is over the budget for this project... You could buy a nice laptop HD and enclosure and assemble it yourself for a tad under $100. You could install the new OS on the External USB HD and work out the kinks... then port over your stuff from you current installation and when everything is working swap HDs and you should have a working system with Mint 17 and a very useful ext USB HD for future use as you see fit... You could even save a few $ and do without the enclosure although then you would have to swap HDs whenever you wanted to boot the "other" system (I wouldn't recommend this though)...
An even cheaper alternative is to boot the live Mint 17 medium and use Gparted to free up some HD space for the Mint 17 installation... dual boot until you have the Mint 17 system settled in and then just run with it... total cost - $0
In case you are interested in testing the restorability of your image - all you need is an empty HD at least as big as the one in your laptop... put the blank disk in the laptop and restore the image to it... Then reboot the system and test it... if everything works perfectly - you have succeeded... in which case you can use either HD to install the new system and at least you will have a safety net if the new installation doesn't work out...
Well that's it for my ideas - YMMV... I wish you luck...