VM catalogue trouble

P

Pat.fr

Bit poster
Well I'm running the last 2.5 version of parallels on my machine.... in fact I'm trying to use it.

Why because I'm having trouble with the available VM catalogue.
The catalogue still trying to connect to an old mapped drive (where I had some VM on it) that I'm not using anymore.... and then nothing to do, just to kill the application.

So my questions are :
- Why parallels is not able to refresh the list of available VM ?
- How to edit this list ?
- or How to delete this list ?

I have also tried to delete the application with the installation menu and then look at parallels files in the finder... but even after removing parallels, I'm just able to do an upgrade (installation option is not available).

Any ideas ?


Thanks in advance
 
Pat.fr said:
So my questions are :
- Why parallels is not able to refresh the list of available VM ?
Click to expand...

Probably because Parallels doesn't know how to handle broken network file links (I'm assuming you were using a networked drive for the VM?). It might be hoping to resolve the link and won't give up until it times out. A while back someone else had also posted about having this problem.

Pat.fr said:
- How to edit this list ?
Click to expand...

You're not supposed to need to, usually if a VM doesn't exist it simply isn't displayed, and deleting a VM is supposed to remove it from the list.

Pat.fr said:
- or How to delete this list ?
Click to expand...

Use this script that I created for that purpose.
 
Last edited:
Thanks for your answer brkirch !

In fact I'm using 2 local VM and I had 2 networked drive VM.
At this time the only one solution to have parallels running is to connect the network drive.

Well I haven't find the post you talking about..... Is that mean that there is no solution for the moment ???
 
Pat.fr said:
Well I haven't find the post you talking about..... Is that mean that there is no solution for the moment ???
Click to expand...

The solution is to run the script I mentioned in the last part of my post. Here's the post I was referring to, their problem was in fact resolved after clearing the VM list using the script I created.
 
You must log in or register to reply here.
Back
Top