I have been using the latest build of Parallel Desktop 7 on my MacBook Pro running MacOS X Snow Leopard, with Windows XP SP3 on the Bootcamp partition. I have experienced no problems whatsoever with the virtual configuration under MacOS X Snow Leopard and the software has remained error free.
Today I upgraded to MacOS X Lion and was subsequently unable to fully boot up the Virtual Windows XP OS.
The load failed very early with a Windows error "computer disk hardware configuration problem. Could not read from the selected boot disk. Check boot path and disk hardware."
I closed down MacOS Lion and rebooted my MacBook Pro into Windows and found that the Windows XP OS in the Bootcamp partition functioned perfectly and loaded Windows XP without any problems. I went into disk managment and checked the health of the disk and found no problems.
Thinking that this error is normally associated with boot.ini problems, I checked out the boot.ini file but it appears in this case that the file is as it should be. Perhaps that is obvious as the OS booted up without any issues! The issues seem to reside within the virtual disk configuration where I confess that I am lacking in skills.
I have posted a support ticket but thought I would ask whether anyone in the forum has a similar experience and can advise me of the steps I may be able to take to correct the problem.
Tim.
Today I upgraded to MacOS X Lion and was subsequently unable to fully boot up the Virtual Windows XP OS.
The load failed very early with a Windows error "computer disk hardware configuration problem. Could not read from the selected boot disk. Check boot path and disk hardware."
I closed down MacOS Lion and rebooted my MacBook Pro into Windows and found that the Windows XP OS in the Bootcamp partition functioned perfectly and loaded Windows XP without any problems. I went into disk managment and checked the health of the disk and found no problems.
Thinking that this error is normally associated with boot.ini problems, I checked out the boot.ini file but it appears in this case that the file is as it should be. Perhaps that is obvious as the OS booted up without any issues! The issues seem to reside within the virtual disk configuration where I confess that I am lacking in skills.
I have posted a support ticket but thought I would ask whether anyone in the forum has a similar experience and can advise me of the steps I may be able to take to correct the problem.
Tim.