icyfire

[Log in to get rid of this advertisement]

This mouse is USB and is supposed to be plug and play. When I plugged it in, it barely worked at all. The pointer moved up and down; when the buttons were clicked it caused the pointer to move a set distance to the right. After about 2 hours of messing with it, I took it back to the store and spent the extra 10 bucks for a good Logitech. I don't recommend this mouse at all.

tk31337

Don't know about USB, but through PS/2 this mouse works flawlessly. Very responsive, and all buttons work (although side buttons are mapped to right click and middle mouse). Only thing that's that bad about it is that it's from Microsoft :-P, but, oh well...

Thetargos

I've used this mouse with several distributions: Red Hat 7.3, 9, Fedora Core 1, Gentoo 1.4, Mandrake... It works excellent. In Red Hat you can always use 'setup' to change the mouse's properties for example from USB to PS2 or viceversa.

xconspirisist

I confirm that is works flawlessly within rh 8, rh9, fc1, and fc2.

Had a few problems with slackware - needed the HID kernel module. If it is moving about rather oddly, check this module is loaded.

nullz0r

This mouse worked great in Red Hat 8.1, SuSE 8.2, and in Mandrake...dont remember what version of Mandrake. However, to get this mouse up and running in Slackware takes some work. Once you know what to do however it only takes minutes

Unregistered

Does not work in usb or ps2 mode when loaded into installer. DOES NOT WORK!

arst05

Works perfectly, I have used this mouse with Redhat Linux 9, Fedora Core 3, Redhat Enterprise RHEL 3 and it is one word-awesome.


If you want a perfect mouse working under USB buy this one!

thehamburgian

ms wireless intellimouse explorer for bluetooth

i plug into usb, nothing happens. standard /etc/bluetooth file in ubuntu:

# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann Exp $
#

# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;

# PIN helper
pin_helper /usr/bin/bluez-pin;

# D-Bus PIN helper
#dbus_pin_helper;
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h-%d";

# Local device class
class 0x3e0100;

# Default packet type
#pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;

# Authentication and Encryption (Security Mode 3)
#auth enable;
#encrypt enable;
}

authentication and encrytion are commented out. what's the problem?

thehamburgian - a newbie's newbie