This afternoon I’m going through the process of installing VMWare Workstation onto my PC at work. We’ve gone for the product as it is generally better regarded than the equivalent Microsoft virtualisation products.
Having said that, it has given me this classic example of a nonsensical error message. You can click on the image to see it at full size.
What it is actually complaining about is that the existing Virtual Server virtual machine I am trying to import is write protected, as it is one of my base configuration images that I want to ensure can’t accidentally be corrupted. This would be fine, if it wasn’t for the last line of the error, where it maintains that the import process will not change the original files. If that is the case, why does it need me to turn off the read-only flag on the files?
Having said that, there is apparently one pretty impressive feature I’ve spotted so far – the manual seems to imply that it will be able to host a virtual machine running a 64-Bit operating system, even though the host operating system is only 32-Bit, as long as the processor in the machine is 64-bit…