Windows Explorer Problem after Suspend/Resume not fixed in Beta 6

J

jsolderitsch

Member
I have reported in other threads dealing with beta 5 that Suspend/Resume with Parallels makes the Windows Explorer app lead to a hung VM (Windows XP/SP2).

I just updated to beta 6 and I want to report that this problem is still there.

It's a 100% reproducible for me.

Boot up your XP VM. Observe that Windows Explorer can be used successfully to browse your XP disk files.

Now suspend the VM.

Then resume the VM -- it comes back to where you left it as expected. I can fire up Firefox and make a network connection just fine.

BUT, now try to use the Windows Explorer to open a folder with files in your VM.

The VM freezes -- one core of my Macbook Pro is maxed out but the VM is frozen

I will file another problem report.
 
Confirmation

I can confirm I have the same problem with XP sp2 when I bring a VM out of suspend. Funny thing is that my % usage is 102% on my duo core mini.
 
Disable sound in VM to get suspend/resume to work better

I did some more experimenting and if you disable sound in your VM config, it looks like suspend/resume and file browsing with Windows Explorer do NOT freeze the VM.

I was using beta 6 (hotfix version) and after I disabled sound I no longer see the VM freeze like it did. I suspect that the recent sound work done by the Parallels engineers has introduced a bug in regard to saving sound state so that resuming correctly recoves the saved suspended state.

Just a hunch at this point.
 
Last edited:
You must log in or register to reply here.
Back
Top