Beta wont boot unless it sees my other computer!

[shaneblyth]

This is sure wierd.. using new Beta.
I started parallels today on my macbook pro and it said something like afp searching for macmini
something like that anyway.. it had the option to cancel and parallels hung
no matter what I did it just came up looking for my mac mini ? really wierd.
so I turned it on and it boots fine
so i did it again and same result.
next i booted but then i turned the macbook pros network connection off and sure enough bang parallels stops responding. So I turn the network connection on again and after a mintues parallels starts to respond again.. (this was with WinXP fully booted in parallels the last time

I have checked my settings for the VM and it all looks fine nothing looking for the macmini

Now the VM image and he little file it uses was originally made on my macmini so i simply copied that across to the new machine. I dont see why that should make a difference as i said I see no where to change a setting at all that relates to the other machine

I have used the new Beta for a few days no worries but the Macmini was always on and visable on the network

what the heck is going on here and why and how do I fix it

cheers

 

[shaneblyth]

Surley someone else has seen this or has some idea.. it is bizzare!

 

[joem]

The .pvs file is a text file. Open it in a text editor and look for mini references.

 

[bscinc@mac.com]

I have the same issue, even with the latest beta. It isn't a reference in the .pvs file, checked it. I went through and uninstalled Parallels, removed every last remnant (pref files, even hidden files with references to Parallels) reinstalled and created a new VM and connected it to my boot camp partition. Unfortunately, same exact result, unless I have a shared connection to my desktop that I transferred over a VM from originally, which as since been deleted from my laptop, I still get the "looking for... afp connection" then the system slows to a crawl unless I forcequit Parallels. Unfortunately I spoke to support about it, and they say it's an Applecare issue and I should calll Apple!!!