On Friday 08 September 2006 12:50, cl@isbd.net wrote:
On Fri, Sep 08, 2006 at 10:36:09AM +0100, Ten wrote:
.I *think* I understand what Player is now, it can be used to run 'already created' VM system images but that's all. Thinking about it it's probably not very useful except in an environment where there are a lot of pretty similar machines as, presumably, an image created on one machine will only run satisfactorily on another where the hardware is *reasonably* similar.
As a note on this one, to support a few "windows-only" apps that wine wasn't having (and in light of an abundance of disk space), I've happily taken a VMWare image (It may have been a syllable OS one, and this was purely to make the image creation process instant) with decent hardware and ram from an LXF cover disk, booted into it, then reset it with the XP install disk in the hard drive, installed XP Pro on it and closed/saved/backed up.
I then used that as a basis for multiple VMs with different setups for those windows-only apps. Everything was hunky dory.
If windows XP happily installs and runs on a fairly low-spec machine using nothing more than VMWare player, 2k probably will too.
That's excellent information, thanks. So I can get a VMWare image like you have, run it on a Linux host (using just VM Player) and (if Win2k works like XP) install Windows on it and run it?
Yep. I was able to install and run it on a very modest machine with fair performance,use USB devices etc.
You'll need to install the VMware bits for the guest OS to get best use out of it. To do this you can wget http://download3.vmware.com/software/wkst/VMware-workstation-5.5.0-18463.tar... and extract the windows.iso from it.
Mount that windows.iso as a cd in your guest windows installation and use the ensuing windows installer.
Have fun.