Parallels won't launch!!!

OK, I guess you can now count me among the people who are having problems with Parallels. Up until now, I have had no problems to speak of and have breezed through every upgrade and update without any issues. .......

I am using Build 5160 and have been happy with its improvements, having had NO problems. This morning, I go to launch Parallels and it will not launch completely. The configuration window comes up that says it was suspended. When I click to start it, it begins to start up; you see the Windows desktop but not completely. It only shows for about 1 or 2 seconds, long enough to see a jagged blackness about the bottom 2/3 of the screen as if the window had not been completely drawn. Then, it quits. No message, nothing. It is not up there long enough for me to shut down Windows.

Can anybody help with this? I thought that I could copy over the Parallels folder, etc. in the Library folder from my backups using Apple Backup, but I am having problems with Backup finding what it needs. Another story, another forum. Oh, stupid that I am, I never used the Snapshot function thinking I had it covered by my laptop having Parallels, too (it's in the shop being repaired) and my backup, which is not functioning. After this, I can assure you I will use the snapshot feature!!!

Back to my problem. Anybody have a thought about this? I could sure use some advice!

Kathy

 

the jaggies ae when Parallels grabs / lets go the graphic card
a long standing "feature"

just refreshing the front window clears that

try opening Parallels
selct but don't run a VM
and from the file menu
clone your Vm onto an external hard disk
best FW800
and run the clone from there

it also seems to free up the Mac OS too

you need about 20% empty on the macintosh HD to allow the machine to write and delete invisible cache files

and the VM disk C needs empty space too jist liek any olf Windows machine

Hugh W

 

Thank you, Hugh for responding. Actually, I have 135 GB free on my Mac and about 3GB free on the Windows C Drive so that does not seem to be the problem.

It appears I am back running now .....quite by accident. A few minutes ago, I tried again to launch Parallels. At the configuration screen, I clicked on Edit VM. Of course it said it was suspended and if I continued, the suspended state would be dropped. I figured I had nothing to lose at this point so I stopped it. I didn't change any of the configuration on the VM but started it up and it booted Windows normally! Of course, this happened AFTER I uninstalled and re-installed Parallels!

I don't know what happened but at least it is back now. Thank you for your help!

Kathy

 

I never suspend
I always do the windows shut down ritual.

I never put my MacBook Pro to sleep either
I let the mac OS control power saving if I don't manually shut down to save electrity

the daily start rituals
Mac OS use log on
then
wait for my mail to be collected in three programs
then start a VM
usually while I finish off a coffee or clean my teeth etc if before breakfast

then user log on to Win Xp sp2

the only serious trouble I had was out of disk space with too many old clones
and I rushed out to buy a La Cie FW800
at the Apple Store

trouble free computing needs good house keeping

my appartment is a mess but my machines are tidy
all my data is in shared folders
shared exteranal disk
shared Mac OS user desktop

good luck

let the OS do their error corrections at start up and shut down

Huh W

 

As I am sure is the case with many others, I often suspend my VM (I have the preference checked to automatically do so upon quitting Parallels) and put my Mac to sleep manually with no problems.

David
MacBook Pro Core 2 Duo 2.33 GHz, 3 GB RAM
OS X 10.4.10
Parallels 2.5 (Build 3214)

 

I, too, suspend my VM, as well as put my Mac to sleep. Have always done that with no problems. Guess each of us may have different ways of doing things.

Thanks!

 

For what it's worth, I've been having the same issue with 5160. If suspended, it intermittently will not properly wake up, usually after I've taken the MacBook between work and home.

Force quits and OS X reboots do not resolve the issue--the only workaround is to edit the config and drop the suspended state. Note that every menu bar option for Parallels is grayed out, so it is not even possible to stop the Parallels VM without a force quit.

While composing this posting, my VM just finished restoring itself from the suspend state. That took maybe ten minutes--I haven't waited that long before to see if it would finally wake up.

Note that this particular issue did not happen to me before 5160, including with the 5144 beta. I'm tempted to downgrade to hopefully get around this annoyance.

 

Hello everybody!

It's a really big problem. It's accidental, as I see.
We are trying to reproduce and fix it.

Thank you for your feedbacks.