I never had this problem with Parallels (up to version 2.x anyway). There goes any thought of switching to VMware. I was thinking about it because Parallels is a bit slow and a little behind in development (64 bit, other guest OS), hence the unfortunate (in hindsight) trial. I am pissed.
For some reason parallels has never worked with my boot camp partition, don't know why
Which files are these? You need to be specific.
esung,
After I did another system restore to bring my computer back up to the present, I deleted the vmware files again and then they quit coming back after each reboot. I don't remember the names, but they all had vmware in the name and there were about 10 of them. I can't get them back.
But Examsoft's SofTest is still refusing to run because it still detects vmware fusion. Uploaded and attached is the image of the SofTest error window. It seems that it must be detecting some process that vmware fusion is still running. It seems you are an employee there, so I hope you can track down how to fix this, and feedback to your developers to not allow vmware fusion to run anything when vmware fusion is not being used. If I don't get this fixed in about 3 days, I'll have to wipe out my bootcamp image and reinstall Windows. Thanks.
I wonder if they run the detection once on each good start and if it sees one of the giveaway characteristics of VMware, it simply shuts down and never looks again. That would "make sense" in that it would neatly explain the symptoms you are seeing without requiring VMware processes to be running or files to be present. It's also similar to something that my own company does (not with VMware, but with certain other environmental conditions).
But Examsoft's SofTest is still refusing to run because it still detects vmware fusion. Uploaded and attached is the image of the SofTest error window. It seems that it must be detecting some process that vmware fusion is still running. It seems you are an employee there, so I hope you can track down how to fix this, and feedback to your developers to not allow vmware fusion to run anything when vmware fusion is not being used. If I don't get this fixed in about 3 days, I'll have to wipe out my bootcamp image and reinstall Windows. Thanks.
It's possible that we're forgetting to uninstall something and SofTest is picking up on it, but I think Bob's response is more likely. There doesn't seem to be any trial version of SofTest available, and I don't think we can figure out what it's doing without getting our hands on it (or if someone with a copy helps out as Woody suggests).
I would be more then glad to to the forensic analysis if someone would provide access information to the program via private message. I have the tools to examine the changed state between a clean built Boot Camp partition and a Virtual Machine of the Boot Camp partition with VMware Tool installed and removed and then attempt to detect what exactly ExamSoft is looking for however with out the ExamSoft program I can do nothing other then to say ExamSoft is looking at the Windows Registry and or Filesystem for something and my guess it the Windows Registry.
Here is the reply from Examsoft. Note that the link only works from a Windows browser, not a Mac browser (javascript error).
This procedure (deleting the three files) worked. I tried it. Thanks for all the help in this forum.
Evidently SofTest checks for the presence of the following files:
1) Vms_fb.dll
2) Vmx_fb.dll
3) Vmx_svga.sys
These are usually found in the following locations but you may still want to perform a search for them as well.
C:\WINDOWS\system32\vms_fb.dll
C:\WINDOWS\system32\vmx_fb.dll
C:\WINDOWS\system32\drivers\vmx_svga.sys
Please search for and delete these files if found on the machine. These files are drivers used by VM Ware and are usually left behind after uninstalling VM Ware. You can also visit the link below for more information on removing VM Ware.
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1308
Thanks.
Sherrod Seeharack
Thanks for contacting them about SofTest and reporting back. I've filed a bug about these components not being properly uninstalled.
I was going to suggest that maybe they saw some hidden devices left behind in the registry, but never mind, looks like you got the answer about what's happening...
A better way would be to delete any vmware-specific files at shutdown of the virtual machine and reinstall them upon startup of the virtual machine. That would ensure that a natively booted bootcamp volume is not affected by unneeded drivers. This seems to be the approach that Parallels (2.x) takes. At every startup of the virtual machine, there is a short pause where it installs its specific drivers. There is no trace of Parallels when booted in native mode, but for a network protocol for the virtual network interface in each network connection (probably would take too long to delete and reinstall this every time).
Because of this and my dependence on Examsoft for the near future, I will have to stick with Parallels unless/until you come up with something similar. Thanks.
A better way would be to delete any vmware-specific files at shutdown of the virtual machine and reinstall them upon startup of the virtual machine. That would ensure that a natively booted bootcamp volume is not affected by unneeded drivers.
Just because hardware is missing doesn't mean that the drivers should be deleted from disk, that's way too drastic. The driver should detect that there is no matching hardware and not do anything, if the OS bothers to load it at all. The problem is that Examsoft is looking for the files on disk, which doesn't have anything to do with whether you're running in a virtual environment. I think this is sloppy on their part.
I agree that we should uninstall the three files if you uninstall Tools, but that's very different from deleting Tools on every reboot.
This seems to be the approach that Parallels (2.x) takes. At every startup of the virtual machine, there is a short pause where it installs its specific drivers. There is no trace of Parallels when booted in native mode, but for a network protocol for the virtual network interface in each network connection (probably would take too long to delete and reinstall this every time).
I doubt they actually reinstall their Tools each time (rather, it's probably what they do with Windows activation or something).
Now that it's know what ExamSoft is looking for it is very easy to script a solution so one could use ExamSoft on their Boot Camp partition without deleting VMware Tools and still have the ability to run the Boot Camp partition as a Virtual Machine when not needing to use the ExamSoft. There are several ways this could be approached and I'm not suggesting that VMware do anything as this is really more of a User issue and some simple scripting can handle this as needed.