Its kinda odd though that when I'm not running a fusion VM, my iMac never crashes. A bit of a pain switching back and forth, but if I'm not crashing then I can live with it. I'll have to use boot camp to make a clean windows partition and run that way. My point in saying that is that VMWare fusion was created specifically to run windows and other OS's on a mac and if the crashes are due to a video problem or some other hardware problem that causes the Whole Mac to crash, not just the windows 7 VM then what does that mean? Anyway, whatever the problem is, it happens often enough that I am going to have to stop using Fusion to do any of my critical work. I can't upgrade the video card as far as I know and yet, I think this is the source of the problem. I have to say though that this is kinda strange because, lots of Macs out there are really not upgradeable in the video card department. I would also tend to agree that it is probably hardware and I am thinking that it is video. Just search for or add your desired NZB then let take NZBvortex control: it will download the minimal required data to complete the download, uncompress, cleanup and move the download to your desired location. I do keep a continuous backup of stuff I work on. NZBVortex is very feature complete and extremely tuned for optimal download speeds and minimal system resource usage. (Typical TS procedure is: 1) test in a new user 2) test after reinstalling the OS, 3) repair hardware). Especially if you've already re-installed the Mac OS. My advice: Contact Apple and ask to speak with a Level 2 tech, as they can associate the symptoms you're experiencing with hardware, and can do something about it. Such are the tenants of the Dark Side of hardware failures. Generally, in my experience, Freezing leads to Crashing, which leads to Cursing. With Virtualization, those banks are more often maxed out and very much need to be correct (there's little room for error at this level), so a flaw will be exposed as 'freezing' and 'crashing', when it might never have been hit if the user isn't using a virtualization platform. Something as benign as a bad bit at the very bottom of a RAM stick might not be hit until the RAM at that location is actually used, which might not be often. So, because we're maxing out the hardware, we expose flaws much more often than when using an Apple on it's own. You're running 2 OS's (or more) after all, so we're pushing the disk hard, using all available RAM banks, and sending complex multi-tiered instructions to the CPU (to accomodate host and guest instructions, assisted by VT, etc.). We push the hardware more than a Mac on itself.
0 Comments
Leave a Reply. |