Installed 3186 and image now corrupt

S

scott_mac

Bit poster
Hi Folks,

I updated to Build 3186 a couple of days ago and yesterday the whole thing went a bit mad on me, XP rebooted and forced a CHKDSK and spent about 10 minutes reorganising files, this culminated in an infinite loop of Parallels rebooting and finding a corrupt image file...

I have a backup from a couple of days ago, but it's from a previous build.

Can i repair the current image in any way? Or can i use the old version? Can anyone advise on the best/easiest course of action to resolve this?

Cheers

Scott
 
scott_mac said:
Hi Folks,

I updated to Build 3186 a couple of days ago and yesterday the whole thing went a bit mad on me, XP rebooted and forced a CHKDSK and spent about 10 minutes reorganising files, this culminated in an infinite loop of Parallels rebooting and finding a corrupt image file...

I have a backup from a couple of days ago, but it's from a previous build.

Can i repair the current image in any way? Or can i use the old version? Can anyone advise on the best/easiest course of action to resolve this?

Cheers

Scott
Click to expand...

To repair the trashed image, you would need some kind of PC recovery program, and it is likely going to be a very painful process (if it works at all; low level recovery software is likely to run into limitations of the emulated environment). I'd say your chances for success are better by going back to your backup VM. Open it in the new release, uninstall the old Parallels Tools, restart the VM, and then install the new ones. That extra uninstall step seems to reduce the chance of corruption.

While you are at it, you might as well try the latest 3188 build. I don't find much difference from 3186, but it ought to have some bug fixes.

One hint for decent performance is to not give Parallels too much memory for its virtual machine. My performance went way up when I reduced the parallels memory to 512M. That's about the minimum memory for decent performance from a real XP PC, and anything more seems to starve the Mac side for memory.
 
Thanks.. i have 2Gb in the Mac and 684Mb allocated to the VM... am happy to reduce it if need be :)

I had a feeling the image repair was going to be PC based recovery stuff, i'll give that a miss then!

I'll give the steps a go - thanks for the help!
 
You must log in or register to reply here.
Back
Top