mrfearless47
Member
I've been running the 5570 beta version of 3.0 for about 8 weeks or so. Before that I've had Parallels running successfully since version 1 and have paid copies on several machines. The particulars of the machine where the trouble occurs are: Mac Pro, 8 GB RAM, 2 Terabytes of Mass Storage (4 - 500 GB drives), quad core 2.67 GHz, and the 7300 Video card. Up until yesterday I wasn't having any trouble. I noted that the final build 5582 was out (for about a month) and downloaded and installed it (I have nightly backups of everything). After installing, I tried running parallels. It would load, get to the screen where I had my VM's listed and would let me select a VM to run. The moment I pressed the green arrow to start the VM, Parallels would enter an endless loop and even "killing the task" would leave shards of Parallels still running. Although it doesn't show up in activity monitor or at the command line using "top", the Parallels icon is still active in the dock with a little windows logo in the lower right hand corner. I can click on that all day and the choices always tell me the application "is not responding" and gives me the option to "force quit". The only way to rid myself of this scenario is to restart the system - a not terribly pleasant option. Moreover, restarting doesn't regain control over parallels. If I try running the VMs, the same thing occurs over and over again.
So, I try my Ubuntu installation - also running just fine before the 5582 install. It does the same thing.
Since the install did not, to the best of my knowledge, touch the VMs themselves, I assume I've got a bad install of Parallels. So, I use the Parallels uninstaller to remove the application from the machine. I restart the machine, download a completely new copy and reinstall Parallels from a fresh dmg file. After doing so, the same thing happens.
OK. Let's assume that the install somehow corrupted the VMs. So, I wipe the folder containing the VMS (hdd and pvs files) and move over last night's backup of same onto the main drive. Restart machine, run parallels, and instant freeze.
Now I'm getting pissed. So I wipe out all the VMs on the main drive, all ancillary files I can think of, and I use Parallels transporter to import a VM that I have in Fusion. It does its thing, creates the new Parallels VM from a fully working (checked five minutes before) VM from Fusion and at the very end tells me it is finished and asks whether I want to run the new VM in Parallels. I say, of course. I brings up a VM configured about the way it ought to be configured and when I click on the green arrow to start the VM, the same damn thing happens again.
I *could* start a fresh install of Windoze (I have a site license CD with XP2), but this is an awful lot of effort without any assurance it is going to do anything. To me there has got to be a file corrupted somewhere that isn't getting deleted when the uninstall occurs and which got overwritten and corrupted during the upgrade process. Before I go through all the trouble of reconstructing a Windows (and Linux) VM from scratch, I'd like to explore other options. If I mount the Parallels VM disks (hdd), everything is in tact and all files that are supposed to be there are. So I'd hate to lose all that information for no reason if there is another solution.
If I were to do a complete removal of EVERYTHING Parallels installs everywhere on the system, how would I go about doing so? Where are the hidden files such as the license files, the plist files. I can't seem to locate them anywhere and I'm betting on a corrupt plist somewhere.
I'd like to keep using Parallels (along with Fusion) if I could, but this experience has put me in an ugly mood.
Thanks.
So, I try my Ubuntu installation - also running just fine before the 5582 install. It does the same thing.
Since the install did not, to the best of my knowledge, touch the VMs themselves, I assume I've got a bad install of Parallels. So, I use the Parallels uninstaller to remove the application from the machine. I restart the machine, download a completely new copy and reinstall Parallels from a fresh dmg file. After doing so, the same thing happens.
OK. Let's assume that the install somehow corrupted the VMs. So, I wipe the folder containing the VMS (hdd and pvs files) and move over last night's backup of same onto the main drive. Restart machine, run parallels, and instant freeze.
Now I'm getting pissed. So I wipe out all the VMs on the main drive, all ancillary files I can think of, and I use Parallels transporter to import a VM that I have in Fusion. It does its thing, creates the new Parallels VM from a fully working (checked five minutes before) VM from Fusion and at the very end tells me it is finished and asks whether I want to run the new VM in Parallels. I say, of course. I brings up a VM configured about the way it ought to be configured and when I click on the green arrow to start the VM, the same damn thing happens again.
I *could* start a fresh install of Windoze (I have a site license CD with XP2), but this is an awful lot of effort without any assurance it is going to do anything. To me there has got to be a file corrupted somewhere that isn't getting deleted when the uninstall occurs and which got overwritten and corrupted during the upgrade process. Before I go through all the trouble of reconstructing a Windows (and Linux) VM from scratch, I'd like to explore other options. If I mount the Parallels VM disks (hdd), everything is in tact and all files that are supposed to be there are. So I'd hate to lose all that information for no reason if there is another solution.
If I were to do a complete removal of EVERYTHING Parallels installs everywhere on the system, how would I go about doing so? Where are the hidden files such as the license files, the plist files. I can't seem to locate them anywhere and I'm betting on a corrupt plist somewhere.
I'd like to keep using Parallels (along with Fusion) if I could, but this experience has put me in an ugly mood.
Thanks.