![]() It just happened again, and this time all I did was run disk utility on my mac partition and then chkdsk booting into windows. Thanks for the reply, provides good insights. Have you been having any OS X System Lockups that have necessitated you doing a hard reboot of the system? I would run the usual utilities under OS X to verify that the OS X Filesystem is okay and also use a utility that tests the disk at the block level to ensure there are no bad spots on the platters. ![]() I suspect that something is corrupting the meta-data of the Boot Camp partition Virtual Machine and exactly what I cannot say because there is not enough information being presented to formulate a valid hypothesis. When you delete the Boot Camp partition Virtual Machine you're enabling Fusion to recreate the pointer to the real MBR and is written into the virtual hard drive use by the Boot Camp partition Virtual Machine to then access the physical partition that Windows is on. ![]() Under normal circumstances on both a Physical Machine or VMware Product Virtual Machine at the point that the BIOS passes control to the Windows OS by reading the Boot Sector and Master Boot Record this white cursor appears at the start of that process and if it hangs at that point it's because there is a problem reading the MBR and when it hangs at that point there is not much that can be done other then to repair the MBR. I can still restart my computer and boot into the windows partition just fine, but it doesn't let me use VM with VMware. After the VMware BIOS (whatever VMWare screen is supposed to be) loads, the screen turns black except for a stuck white cursor as shown in the attached picture. What you download is the normal release version and you get a 30-Day Trial Serial Number which has no effect on the functionality of what you downloaded vs using a purchased serial number.īasically my virtual machine based on the bootcamp partition will freeze on startup before the Windows XP screen will show up. This happened with previous versions too, btw, and I first noticed this problem occurring when I was using the evaluation version.įWIW VMware does not have or use an Evaluation Version of Fusion. I've run into a bit of a snag and I'm using VMware Fusion, 2.0.1. I then have to reinstall vmware tools and I'm off and running (picture 4).Ĭan anyone tell me why this is happening and how to permanently fix the problem? The next time I start VMware it sets up the virtual machine again (picture 2) and it will work. ![]() The fix has always been the same: delete the 'Boot Camp' folder under ~/Library/Application Support/VMWare/Virtual Machines. This last time I went from one day using it just fine, to another getting this screen. I used to think it concerned vmware tools, but that doesn't seem to be the root cause. Basically my virtual machine based on the bootcamp partition will freeze on startup before the Windows XP screen will show up. This happened with previous versions too, btw, and I first noticed this problem occurring when I was using the evaluation version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |