VB hangs on Win 7 32-bits install from CD
Posted: 2. Apr 2012, 11:57
Greetings from Paris to all !
Any help to solve VB crashing while installing Win 7 32-bits from an original MS Win 7 CD would be greatly appreciated...
The environment :
VB latest (4.1.10-76795) and matching extension pack
on an late 2009 I7/12 Gb/1Tb Intel iMac 27" under Mac OS X 10.6.8 (10K549)
with a plain vanilla VB Windows guest : memory to the max (3584 Mb) and storage at 205,44 GB
The facts :
The Windows 7 install process starts normally with the opening of a new window.
After a few seconds a larger windows opens where the installation continues.
After about a minute, that window closes and the installation reverts to a smaller window.
After about 20 seconds there is an abort "due to critical error" message from VB that overlays the install windows.
When one chooses the "debug" option the following message appears :
"Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM"
with a "more details" link that shows nothing.
The log file :
Any help to solve VB crashing while installing Win 7 32-bits from an original MS Win 7 CD would be greatly appreciated...
The environment :
VB latest (4.1.10-76795) and matching extension pack
on an late 2009 I7/12 Gb/1Tb Intel iMac 27" under Mac OS X 10.6.8 (10K549)
with a plain vanilla VB Windows guest : memory to the max (3584 Mb) and storage at 205,44 GB
The facts :
The Windows 7 install process starts normally with the opening of a new window.
After a few seconds a larger windows opens where the installation continues.
After about a minute, that window closes and the installation reverts to a smaller window.
After about 20 seconds there is an abort "due to critical error" message from VB that overlays the install windows.
When one chooses the "debug" option the following message appears :
"Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM"
with a "more details" link that shows nothing.
The log file :