Image problem with VMWare
We have a sysprep image running on 12 different computer models.
With VMWare 4.0, we had no problem to make the image running since upgrading to VMWAre 4.5, the image is making BSOD.
If we go to the BIOS and change teh PCI Controller from Both to secondary the image will run fine until VMWare tools is install. Then the BSOD are coming back. If we change the PCI controller to Both then the image will run fine.
In my image I changed the controller to standard controller and reimage. The problem is still present.
The error message is: STOP: 0x0000007B
With VMWare 4.0, we had no problem to make the image running since upgrading to VMWAre 4.5, the image is making BSOD.
If we go to the BIOS and change teh PCI Controller from Both to secondary the image will run fine until VMWare tools is install. Then the BSOD are coming back. If we change the PCI controller to Both then the image will run fine.
In my image I changed the controller to standard controller and reimage. The problem is still present.
The error message is: STOP: 0x0000007B
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Francoisracine
19 years ago
XP
Seems there is a text file saying to VMWARE what is the hardware configuration. In that file the SCSI is set to true. By settings the value to false then the computer was ok. With RIS we looked in the hardware configuration and there was RAID and SCSI with a !.
Is it a way to set the value for this file by default?
Seems there is a text file saying to VMWARE what is the hardware configuration. In that file the SCSI is set to true. By settings the value to false then the computer was ok. With RIS we looked in the hardware configuration and there was RAID and SCSI with a !.
Is it a way to set the value for this file by default?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.