I just upgraded from Vmware Fusion 1.1.3 to version 2.01. The device manager now shows a yellow exclamation point and the device status shows "This device cannot start. (Code 10)". The virtual machine does run but the guest window does not seem to size correctly as the desktop will no longer fill the window which it used to do in version 1.1.3. Does anyone have any suggestions as to how to correct the driver status and/or the window behaviour?
Host machine is Mac Pro Core Duo (yes, a measly 4 cores ).
Host OS is Mac OS X version 10.5.5 build 9F33
Host machine memory: 10 GB
Guest OS is Windows XP Pro Service Pack 3, 32- bit
Configuration: 2 Virtual Processors, 3 GB RAM, Unity Disabled, 3D Enabled.
A further note for the Vmware staff.
My first step, in the finest Windows tradition, was to attempt to run Repair to see if the installer could correct the problem. This led to frustration followed by disaster. Or at least it would have been disaster if I had not zipped an image of the virtual machine before upgrading it. It was an illuminating experience.
Item: You can't just run Repair from the Add/Remove programs control panel because the VMWare installer (contrary to Microsoft requirements) does not leave a copy of its database on the Guest.
Item: I did activate the Repair option by initiating another upgrade using the VMWare. It presented the usual Modify/Repair/Uninstall menu so I selected repair. It started out OK and seemed to be removing the tools installation but when the reinstall phase started, the install hung at the SVGA install. I gave it 10 or 15 minutes (although it should not need anything like that amount of time) and it remained hung. I attempted to Cancel ( the button was lit) but it ignored this entirely. I was eventually forced to use Task Manager to terminate the repair. I rebooted and tried again; several times but never successfully. Interestingly, while it always hung, it wasn't always at the SVGA driver. Sometimes it was the network driver (Vmxnet), sometimes the VMCI (whatever that may be). All had to be forcibly aborted. Always, it refused to Cancel (the Cancel button is supposed to work, Gentlemen).
Item: I powered off the Guest, and disabled 3D as an experiment. When I powered up the Guest, it booted until it became time to display the desktop. At that point, it announced that it could not find the desktop and declared a System Exception. It counted down and then rebooted. At that point, chkdisk ran, reported and corrected a number of file system errors, and booted. Still no desktop. At this point the virtual machine was completely corrupt so I deleted it completely.
Using a new copy of my original virtual machine, I did the upgrade again. It took a couple of tries but I finally got the tools installed. The SVGA problem mentioned earlier, remained. Also, the USB controller reported the following device status: "The drivers for this device are not installed. (Code 28)" and a big yellow question mark. I pressed "Reinstall Driver" and the system found and installed the standard USB driver. Isn't this supposed to be a Vmware specific driver?.
Observation: If you run install Vmware tools from the Vmware Fusion application and then Cancel it at the first opportunity (before installation starts) it leaves a copy of msiexec.exe running. It is not supposed to do this.
Observation: While performing the attempts described earlier, I saw as many as 6 copies of msiexec.exe running and three copies of runonce.exe. I don't know what you are doing, but this is not normal.
Observation: Out of curiosity, I brought up Orca and ran the ICE validation checks on your installer. The result was an incredible number (too many for me to count, life is short) of errors and warnings. In my limited experience, I have never seen so many validation errors in a shipping product. I realize it is difficult to completely avoid validation warnings but this is ridiculous. Taken with the flakey way that your installer behaved, I would suspect that these errors need some attention. It may be that some of the weird and wonderful problems that have been reported on this forum could be accounted for.
Thank You for your time.