Slow/delayed action after mouse click

[MikelTC]

When I double click on the drive icon, it takes about a full second before it does anything. This seems to happen anytime there is disc access. It also happens in the browser clicking on links. Is there a setting for this?

Thanks

MIkel

[admin]

That's certainly not normal behavior. In order to be able to help you with this, people would need more information. The absolute basics would be: which operating system are you running in your virtual machine, how much memory does your Mac have, and how much memory did you assign to your virtual machine.

To save time, use this checklist:

I would also be curious to know, in Fusion's Preferences panel, if you changed the default "Optimize for virtual-machine disk performance" to "Optimize for Mac OS application performance."

[MikelTC]

Thanks for getting back to me.

Here is my setup and what is happening.

VMWare version 1.1 (62573)

MacPro Dual 3.0ghz xeon processors, 6 gig ram

VM disc allocation 40gb

VM ram allocation 2gb

Problem 1).All the time. Whenever I click on a drive icon in explorer,

it takes about 1.5 seconds to open that drive. Same with clicking on

the back arrow. Also same when on the internet and clicking on new

links. Does not happen when dclicking on desktop icons. This is

something that would cause me not to buy the product.

Problem 2). I cannot network with any of my computers. When I go to

tcp/ip and input my ip address, subnet mask, default gateway and DNS

server information I am no longer able to access the internet. Wen I

leave it set to automatic, I can get on the internet but cannot

network with my local computers. My network is not set for DHCP, I

have to manually set my information in order to keep certain printers

on the same IP. Without networking, this is not going to work for me.

The guest os is Windows 2000 Profession. The install went flawlessly,

very impressed. This is not boot camp vm.

Running on Leopard 10.5.1

Also, does VMfusion run windows in emulation or is windows running

natively?

Thanks for your help

Mikel

[admin]

Thanks for the info, and also thanks for mentioning the network problem you're experiencing. I think those phenomena are related. (My working theory before this post was that you'd given your virtual machine too much memory in comparison to the amount installed on your Mac, but 2 GB for the VM versus 6 GB for the host is perfectly reasonable.)

Anyway, let's focus first on the networking problem. You said you need to use fixed IP addresses on your virtual machines. That tells me that you need to change the VM's virtual network adapter to bridged mode. (The default is NAT mode, in which the virtual machine is placed behind a little software firewall, but you want your VM to be a peer of your Mac.)

To make this change while your virtual machine is powered on, go to Fusion's Virtual Machine menu, go to the Network submenu, and make sure that Bridged is checked. Next make sure that the virtual network adapter is connected: return to the Virtual Machine -> Network submenu and make sure that Connected is checked.

To make this change while your virtual machine is powered off, go into its Settings dialogue and look in the Network settings. Click the button for Bridged.

Now your virtual machine will be connected to your local network just as your Mac is, and the same IP address range will work.

One quick caution, if you connect your Mac to your local network using Airport: there's a known bug in Fusion 1.1 that can cause problems in bridged mode. You won't be affected by this problem if you connect your Mac using an Ethernet cable. Anyway, if you need the fix, you can download it from this forum here:

I think that the "performance" problem you were experiencing actually was Windows timing out on network accesses. So let me know if this helps with that problem as well.

Also, does VMfusion run windows in emulation or is windows running natively?

VMware Fusion does virtualization, not emulation. In an emulation product like the old Virtual PC for PowerPC Macs, Windows ran on top of an entire PC implemented in software. But Fusion has no such component. Instead, every action taken by the guest operating system inside the VM that can run natively does. Fusion's job is to notice when the guest OS wants to do something that can't run natively, and swoop in and do the right thing so that neither the guest OS nor the user notices that anything interesting is going on.