Ron@RonPinkas.com
Junior Member
Hi All,
Today I attempted to update my 2.5 Build 3188 to new 3.0 Build 4560. When starting the new version it prompted me that it must update the VM/HDD(?) to new version. Few seconds after I confirmed, it crashed my Mac Mini (Core Duo 1.66 2GB 10.4.10) and I was forced to power off.
On reboot it became apparent that the upgrade attempt had corrupted my HDD file. Both the new build 4560, and the previous build 3188 are NOT able to open the file (I tried both Paralles Desktop, AND the Paralles Image Tool in both builds).
Beside the immediate help I need, I wonder why would Parallel's try to Upgrade the file INPLACE, risking such corruption?
All help will be greatly appreciated - especially any response from Parallel's Tech Support.
Ron
Today I attempted to update my 2.5 Build 3188 to new 3.0 Build 4560. When starting the new version it prompted me that it must update the VM/HDD(?) to new version. Few seconds after I confirmed, it crashed my Mac Mini (Core Duo 1.66 2GB 10.4.10) and I was forced to power off.
On reboot it became apparent that the upgrade attempt had corrupted my HDD file. Both the new build 4560, and the previous build 3188 are NOT able to open the file (I tried both Paralles Desktop, AND the Paralles Image Tool in both builds).
Beside the immediate help I need, I wonder why would Parallel's try to Upgrade the file INPLACE, risking such corruption?
All help will be greatly appreciated - especially any response from Parallel's Tech Support.
Ron