Since my upgrade to Parallels 6, I have a problem with my MacBook when it resumes from disk. In detail:
I have configured my MacBook in a way that it does usually suspend to disk, rather then suspend to RAM. This never used to cause any problems whatsoever.
Since my upgrade of Parallels to version 7, I experience problems when my Mac wakes up. After the display shows that about 50% of the main storage image has been loaded from disk, the resume process stops and the MacBook freezes at that point. The only way to get my MacBook back to work, is to hard-reboot it.
It took me quite a while to find out when exactly this happens, as it did not happen every time. The point is, this problem occurs only when Parallels was running at the time when my MacBook suspended to disk. When I stop Parallels first, there are no problem with the wake-up process.
Also, I did not have these kinds of problems with the Parallels versions prior to 6. My assumption is that it may have something to do with the improved resuming for Windows within Parallels 6? Just a guess.
I hope you can find and fix the problem, since this is quite annoying. If I can provide you with any additional information, let me know, and I'll be glad to do so.
I have configured my MacBook in a way that it does usually suspend to disk, rather then suspend to RAM. This never used to cause any problems whatsoever.
Since my upgrade of Parallels to version 7, I experience problems when my Mac wakes up. After the display shows that about 50% of the main storage image has been loaded from disk, the resume process stops and the MacBook freezes at that point. The only way to get my MacBook back to work, is to hard-reboot it.
It took me quite a while to find out when exactly this happens, as it did not happen every time. The point is, this problem occurs only when Parallels was running at the time when my MacBook suspended to disk. When I stop Parallels first, there are no problem with the wake-up process.
Also, I did not have these kinds of problems with the Parallels versions prior to 6. My assumption is that it may have something to do with the improved resuming for Windows within Parallels 6? Just a guess.
I hope you can find and fix the problem, since this is quite annoying. If I can provide you with any additional information, let me know, and I'll be glad to do so.