@LIaB, My point that you don't seem to agree with is that if an application offers to find files to import and then finds a file, but when it opens it crashes the system that is NOT acceptable behavior. It's like Word offering to import a document, you let it find something, it identifies a file in a non-Word format for import and then when you let it import that document, it crashes your system as a result. Would that be acceptable?
To take your questions in order:
Can Parallels import everyone else’s vms?
What Parallels does or does not do is immaterial. What this discussion is all about is what VMWare offered to do and then crashed the Mac.
Can VirtualBox? All the others? No?
Again, totally immaterial to the abject failure of VMWare.
Is this something you think only developers of virtual machines should feature?
Immaterial. I didn't ask VMWare (or the developers) to do anything it didn't already offer. VMWare DID offer the import, found the files, started the process (the progress bar even moved along for a while), so I think it reasonable that it should work, or at least not crash the entire computer. As I said in the Word example, if Word identifies the file type as one it thinks it can import, it should at least gracefully handle any error it encounters in the effort. And never crash the entire system.
Do you EXCLUSIVELY use open file formats as a lifestyle choice? Ok then.
What does my choice of file formats have to do with VMWare's inability to do what it offered to do? I didn't point to the Parallels images, it found them. I didn't force it to import them after it complained, it offered to do so.
As for the rest, no such problems here.
Happy for you. It didn't work for me.
Can we agree to disagree on the usability of VMWare?
