With all due respect, that's a non-responsive and somewhat patronizing answer. I have a layman's knowledge of VMs and how they work. But, hey, I'll play along, idiot that I am.

If you're saying the guest OS sees, by means of a driver, a notional PS/2 mouse with two buttons and one wheel, why not change the presumed virtual hardware to a notional FOUR-button mouse and wheel?

You know, like every blessed mouse made since 1995!

That way, the mapping is one-to-one for, you know, the 99-percent of us with mice that AREN'T, you know, old PS/2 mice.

IT'S ONLY SOFTWARE.

That's what makes the miracle of Fusion and every other VM product possible.

It is, however, mildly-patronizing-in-the-guise-of-being-helpful blather that really gets up a customer's nose. It smacks of having one's legitimate--It Just Works--expectations "managed."

Try meeting them, instead. Or hell, why not? Try exceeding them.

I've requested support for four buttons in the past, but I'll reiterate here. The OP was requesting a change in functionality, not a description of the current design.

Like everything else I suspect this feature is a matter of priority. Is there anyone else who cares about the extra buttons?

Bravo, Rzn8tor! Exactly. I'm asking for simple functionality. The kind any user sees, each and every moment of a computing day.

And Etung. I didn't take your response as a massive personal attack. I took it as non-responsive and mildly patronizing. Simple.

That said, I am vehement about the little things that make owning a product frustrating, instead of delightful.

I understand that redoing the Murine functionality may take more than changing a "2" to a "4" in an LOC. But we're talking about some of the slickest programmers in the known universe. Making VMs and emulators ain't beanbag, after all.

And of course it comes down to priorities. I'd only hope that somebody at VMWare (maybe you?) understands that fixing unglamorous-but-visible crap like virtual mouse drivers can matter more than the neatest bit-flipping trick, deep under the hood. It is, after all, what the customer sees.

To do otherwise lends the daily impression, odd as it sounds to somebody who knows things from the inside, that VMWare might not be competent on the BIG stuff.

It's like wearing a five-thousand dollar tuxedo with the fly open.

Tried it once and failed. Device manager still reports one HID compliant mouse on tree and VMWare's PS/2 mouse. Disabling the HID item kills the mouse, BTW. Any clues? Is the (mouse.vusb.enable = "TRUE") entry position-dependent?

Thanks for chiming in.

Here's my VMX file:

1. Edited with VMX Extras 0.2007.07.04

config.version = "8"
deploymentPlatform = "windows"
displayName = "Windows Vista"
ehci.pciSlotNumber = "34"
ehci.present = "TRUE"
ethernet0.addressType = "generated"
ethernet0.connectionType = "nat"
ethernet0.generatedAddress = "00:0c:29:5f:d9:31"
ethernet0.generatedAddressOffset = "0"
ethernet0.pciSlotNumber = "32"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.wakeOnPcktRcv = "FALSE"
extendedConfigFile = "Windows Vista.vmxf"
floppy0.clientDevice = "FALSE"
floppy0.fileName = ""
floppy0.fileType = "file"
floppy0.present = "FALSE"
floppy0.startConnected = "FALSE"
guestOS = "winvista"
ide1:0.deviceType = "cdrom-raw"
ide1:0.fileName = "cdrom0"
ide1:0.present = "TRUE"
isolation.tools.hgfs.disable = "TRUE"
MemAllowAutoScaleDown = "FALSE"
memsize = "2192"
mouse.vusb.enable = "TRUE"
nvram = "Windows Vista.nvram"
pciBridge0.pciSlotNumber = "17"
pciBridge0.present = "TRUE"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.reset = "soft"
powerType.suspend = "soft"
RemoteDisplay.vnc.port = "0"
scsi0.pciSlotNumber = "16"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
scsi0:0.fileName = "Windows Vista.vmdk"
scsi0:0.present = "TRUE"
scsi0:0.redo = ""
sharedFolder.maxNum = "1"
sharedFolder.option = "onetimeEnabled"
sharedFolder0.enabled = "FALSE"
sharedFolder0.expiration = "never"
sharedFolder0.guestName = "marshall On My Mac"
sharedFolder0.hostPath = "/Users/marshall"
sharedFolder0.present = "TRUE"
sharedFolder0.readAccess = "TRUE"
sound.autodetect = "TRUE"
sound.fileName = "-1"
sound.pciSlotNumber = "33"
sound.present = "TRUE"
tools.syncTime = "FALSE"
tools.upgrade.policy = "upgradeAtPowerCycle"
usb.present = "TRUE"
uuid.bios = "56 4d 09 04 0e 0f a4 3f-97 e4 68 71 b7 5f d9 31"
uuid.location = "56 4d 09 04 0e 0f a4 3f-97 e4 68 71 b7 5f d9 31"
virtualHW.productCompatibility = "hosted"
virtualHW.version = "6"

I'm running 1.1 and it still doesn't appear to work. What do I need to do to activate this feature?

BTW, it appears BOTh mice HID-USB and PS/2 are using the same driver. Could that be why I'm seeing no functional difference? And why is the PS/2 device ineradicable? The "Disable Device" option is grayed-out in Device Manager. File protection gone awry?