.... the fact that XP doesn't support two mice?
XP supports two mice....
Both statements are true (in english, at least).
It's due to the fact that "mouse" and "mice" can mean different things. "This mouse works on any surface" refers to the physical mouse device, while "Move the mouse over the button" refers to the pointer on the screen.
"XP doesn't support two mice (mouse pointers)."
"XP supports two mice (mouse devices)."
No conflict, both true. So why does this matter?
Mame needs to see the each of the mouse devices data as seperate to support two/multiple "mice"

, and having XP support two pointers would be the most straight forward way. But pointers are not the only mame/applications can do this, so "mouse" has a
third meaning in the context of "does mame support two mice?"; this meaning isn't seeable or touchable, so it's harder to describe. "Mouse instances" or "mouse data streams" are probably the best terms for this meaning. XP doesn't support two mouse data streams navtively (win32 api) or through directX, but it does through RawInput. (mame doesn't use RawInput)
Okay, to review:
"XP doesn't support two mice (mouse pointers)."
"XP supports two mice (mouse devices)."
"XP doesn't support two mice (win32 api)."
"XP doesn't support two mice (directX)."
"XP supports two mice (RawInput)."
"Mame uses directX for trackball, and win32 api for lightgun."
"AdvanceMame can now use RawInput."
"MameAnalog+ ver. 0.84 could use RawInput."
I hope this clarifies more than it confuses.
