Separate names with a comma.
Discussion in 'macOS' started by netdog, Oct 26, 2007.
Anybody try this yet?
Yes, it runs fine. However, when you first start it in Leopard, it asks you to download an update, which is in beta. It will run absolutley fine after that
I can no longer connect to my network in the virtual machine. Is anyone else getting this?
Runs like a champ! Groovy in its own desktop with Spaces too
As above poster said, make sure you get the 1.1 RC from the website before you run tho.
working great here.
Works fine for me.
Even snappier than under Tiger. Imagine that: Leopard is so good it improves Windows!
Getting the same thing. Running vista ult. and cannot connect to network or internet. Ran fine under tiger and currently using v1.1 of fusion.
running xp pro with fusion build 61385 and everything is perfect... although i really haven't tested unity at all since running windows full screen in its own "space" is amazing
I just discovered how you can make VMWare full screen in another space too.
Working great for me as well!
It sends audio to the internal speaker if you ran it on a mac pro.
After upgrading I had to reinstall VMWare Tools (or something like that). It was in one of the drop down menus on the menu bar. After that I was able to connect to the network.
Wow, I never thought of that, LOL. I might actually have a use for spaces after all!
I was running windows XP in full screen in a space....its dead cool !!
Vmware fusion 1.1 RC here BTW...
For those that can't connect to the vmnet device (networking broken).
Install the 1.1 RC version over your existing. It will rebuild the VMnet devices and all will be good....
I had this problem on two different machines, and installing Fusion 1.1 over the old install helped in both cases.
Got the latest beta version, runs great so far.
Running the latest 1.1RC it works great most of the time. I have had it lock up 2 times where I couldn't even do a force quite on it though. I have it's virtual machines excluded from TM and it was not doing a backup at the time of the lockups so I don't believe that was the problem. It's been running now for about 24 hours without another lockup so they seem to be pretty random.