![]() My system was working great, but had some damage to the Macintosh partition catalog that couldn't be fixed by Disk Utility. If it already is, then I apologize for wasting your time and hope the VMWare guys can offer some more insight on this one. You need to set the type of your boot camp partition to 07. There was another post here with instructions already: I really think that the fix is the same as mine, but it will require you to use that scary 'fdisk' terminal command. I was going to paste in my output from the above, but this editor won't let me preserve it and it messes it all up. I did it and survived, and in fact that was the only way I got Fusion to work for me here. I say "potential", because it's there, but in reality it should be quite safe. The post I'll mention below shows you how to fix the problem if the type is set wrong, and at that point there is potential for damage, but there is not yet. You will get the scary bit of info before you put in your password, but this command in that format is safe. In any event, this command will give that information and WILL NOT harm your data, it only prints a bit to the terminal and doesn't change or update ANYTHING. I don't understand about why fdisk gave you a scare just to run it, or maybe you were scared by the obligatory first-time sudo warning. If it failed above, it should at least re-try as NTFS (which I don't see any sign of it doing). VMWare should really fix this, because both Windows and MacOS themselves are smart enough to suss out the volume type without regard to the partition type flag. ![]() VMWare is trying to mount your drive as FAT32 based on the partition table type not the filesystem type. My Disk Utility also identified the drive as NTFS, but in fact it really wasn't. ![]() I still think your base problem is the same as mine. Okay, back to the constantly "preparing partition" question. As I say, I'm not affected by it with the volume licensing I have but I sure don't want to be giving out bad information. Thanks to etung for that added bit of info about not needing to constantly re-activate windows. Hopefully there is an easy solution to my difficulty. This is frustrating as I purchased the software hoping for any easy instal and use. ![]() Once in Windows, use the Startup Disk pane in the Control Panel to select Mac OS X as the startup system, then click the Restart button to return to OS X.' I have done this a number of times (along with other methods of shutting down in both Mac and or Windows and booting up in each in a variety of combinations) and still get the same message. To shut down Windows cleanly, go to System Preferences > Startup Disk and set Windows as the startup operating system. ![]() It appears that Windows did not shut down cleanly the last time it was used. However when I select it and RUN after the message 'VMWare Fusion is preparing your Boot Camp partition to run as a virtual machine.' I received the message 'The Boot Camp partition is not prepared to run as a virtual machine. On installing Fusion from the disk that I'd purchased, the Boot Camp partition wasn't automatically detected, the version of Fusion that I received was version 1, so I updated to version 1.1.0 62573, and happily it did recognise my Boot Camp partition. I have need on occassions to use Windows applications, and from the description of Fusion it appeared that to be able to simply use the existing Windows boot Camp partition would be a simple solution to my needs. I just received my copy of a recently purchased VMware fusion to use as a means to run my existing Windows XP SP2 Boot Camp partition in the Mac environment on my MacBook (2.16GHz Intel Core 2 Duo, 1GB 667MHz DDR2 SDRAM with the startup disk as the Mac partition) running Mac OSX 10.4.10. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |