Suspend/Resume majorly improved in 3170

[jkneen]

I was having some major issues with suspend/resume in 3150 and previous builds. I tended to pause the VM as it was quick and sleep my MBP. This wasn't an issue unless the Mac didn't come out sleep which sometimes it fails to do. I was therefore using suspend to ensure my VM was safe but I was getting some real issues - it just wouldn't wake up (Windows) despite the screen firing up and the CPU monitor in Mac OSX going high so a kill and reboot would be required.

In 3170 I have a 100% record so far of sucessfull suspends and resumes and it's really quick and doing both which is great. good job guys.

Jason

 

[MarkHolbrook]

I didn't have many problems with suspend/resume in the other versions like 3120. What I did notice was that on resume (and 3170 seems to do this as well) it fires up the XP screens and taskbar but they are inactive for almost 30 seconds. Finally they all blink and start working.

It is like they are restoring the last screen image first then restoring all of the pieces of memory then suddenly they flip the switch and it comes alive.

I have just learned to wait a while.

M

 

[unused_user_name]

I noticed this also. It seems that they are making use of some MacOS tricks with RAM. I like the new suspend/resume much more then the old one. It makes Windows seem much more "lightweight" then it actually is.

I think they are restoring the memory while the VM is running, because sometimes if I have a Windows app the uses a very small amount of RAM, like notepad, then this app becomes responsive much faster then apps that use lots of RAM.