On 11/8/2014 10:40 AM, Bob Henson wrote:
On 08/11/2014 3:06 PM, philo wrote:
On 11/08/2014 08:39 AM, Bob Henson wrote:
On 08/11/2014 2:29 PM, Jeff Gaines wrote:
On 08/11/2014 in message Bob Henson
wrote:

Hmm, it would appear I can't do that with the VM player - I have to fork
out £160 quid for the paid version.


Why not just manually make a copy of it ?


How can it not be possible?


Which files do I need to copy - there are a lot of them, and it is far
from clear which ones I would need to copy to act as a back-up. I have
three different operating systems set up within VMware, and it is not
obvious which are which, apart from a couple of very small (around
250Kb) files which bear the name of the O/Ss.


Hi Bob,
I am running VP Player 6.0.4 build-2249910 and here is how I found where
the files were being stored so I could copy or even move them to another
drive or directory. Possibly I was lucky but all of my virtual machines
get stored in individual folders as I create them. I do have hidden
folders being shown on my system but don't know if that makes a
difference with the following.

1. Start the VMware Player icon so you can bring up the list of
available virtual machines you have already created.

2. Right-click on the virtual machine session you want to copy which
brings up 4 choices on my machine. Power On, Settings..., Remove from
the Library, and Delete from disk. Scroll down to Settings and left
click on that.

3. Now Left-click on the Options tab.

4. You should now see a small Working directory window on the right
middle of the window. That should be the directory where your virtual
machine is stored in. Locate it and just copy the entire directory and
you will now have a duplicate of the existing machine.

Above the Working Directory is the Virtual Machine Name window where you
can change the name of a copy so it shows up as an individual version in
the VMPlayer main menu.

5. To use the new copy, usually after renaming the folder, I start the
VMPlayer from scratch and pick the new folder and click on the .vmx file
or main .vmx if you have multiple ones. Tell the system you copied it
if you are keeping it on the same hardware or moved it if you are going
to try that virtual session with different hardware.

Good luck Bob, hopefully our systems are near enough the same for the
above to work for you.