Wireless Logitech keyboard

If anybody has a positive experience of compatibility the K800 wireless Logitech keyboard with MAC OS X Version 10.7.3?
I connected the KB to Mac mini with "Unifing" (Logitech) software installed, but I do not have full functionality: I have no NumPad working. Some of keys respond not correctly. For example, there is no "point" key at the Russian layout.
I asked Logitech support for the driver and they told: "All Logitech products works on standard OS drivers and if you have any problems with it it is better to contact Apple..."
Below - my correspondence with the Logitech support:
Logitech 02/28/2012 10:35 AM Dear Aeksei  Thank you for contacting Logitech's Customer Care. Sorry, but no one has experience K800 on the MAC OS X Version 10.7.3  Best advise to you is to contact apple. They might help you with drivers.   Kind Regards Denis M. Logitech Customer Care - Asia-Pacific
Aleksei Pariy     02/27/2012 08:47 PM Thank you for the prompt reply. First of all, I want to assure you that the keyboard itself is working. It works without any problems in Windows 7.  Mac Mini also properly functioning, I believe. It had been just bought and tested true. But, the keyboard in Mac OS X ... When I try to change the keyboard type, system reports that the keyboard should be identified and invites to press the key, right to "left shift" key. Then the system prompts to select the keyboard type of the three options:
- ISO European
- ANSI U.S.
- JIS Japan
None of these options lets work NumPad. I have no NumPad working. Some of keys respond not correctly. For example, there is no "point" key at the Russian layout.  Please let me know if anybody has a positive experience with the K800 an the MAC OS X Version 10.7.3?
Logitech 02/27/2012 03:38 PM Dear Aeksei  Thank you for contacting Logitech's Customer Care.  You can use your keyboard on Mac. Only we do not have Software for it, but it should work without any s/w. All Logitech products works on standard OS drivers and if you have any problems with it it is better to contact Apple of Microsoft.  To test keyboard you can try it on different PC and if problem stays - it is hardware, if not - software.   Kind Regards Denis M. Logitech Customer Care - Asia-Pacific
Aleksei Pariy     02/26/2012 10:50 AM Could I use Your K800 keyboard with Mac Mini (OS X Lion) and Unifing software installed? I use it, but not complete functionality. Could You indicate me the driver.

I have tried advice of Klaus1at http://bit.ly/wgi53h
Unfortunately it does not help. Logitech Control Centre says: No Logitech Device Found. The KB and Logitech mouse are possible to be controled only thpough Unifing software.

Similar Messages

  • Will both ipad mini and wireless Logitech keyboard fit In the Logitech case that opens like a book?

    I have an ipad mini and the wireless Logitech keyboard and I want to know if the Logitech case will fit both my ipad and the keyboard ?

    Hi emsiecat,
    Here is an article that will explain some Bluetooth troubleshooting steps for you:
    iOS: Troubleshooting Bluetooth connections
    http://support.apple.com/kb/TS4562
    You may also want to check your manual for the keyboard for further troubleshooting steps. Thanks for coming to the Apple Support Communities!
    Regards,
    Braden

  • Wireless logitech keyboard - unable to set keyboard map in X.

    Hi,
    i have a wireless usb keyboard - logitech k360. When I restart X i always have to manually set keyboard layout using "setxkbmap pl" which is little annoying.
    My laptop keyboard has polish layout set correctly. I tried to modify /etc/X11/xorg.conf.d/keyboard.conf, but cannot find the right options. Here's how it looks now:
    Section "InputClass"
    Identifier "Keyboard Defaults"
    MatchIsKeyboard "yes"
    Option "XkbModel" "logii350"
    Option "XkbLayout" "pl"
    Option "XkbOptions" "terminate:ctrl_alt_bksp"
    EndSection
    I've tried to remove option XkbModel, tried to set it to pc105 and now it is set to logii350 (I've searched through the /usr/share/X11/xkb/rules/ to find my exact keyboard model but it isn't there).
    Funny thing is, that when I type some polish character at my laptop keyboard, suddenly wireless keyboard gets good layout.
    Any thoughts?

    Is this one with the Logitech Unifying Device receiver?
    There are a few threads on this forum about it defaulting to the default QWERTY layout (hell, I have an AZERTY layout - not just as a locale, the key prints are AZERTY). It seems to be some udev bug.

  • Wireless Logitech keyboard won't work

    Hi guys,
    I have a wireless Logitech diNovo edge keyboard that used to work fine. A few months ago it stopped working and I never bothered to look at it. The keyboard works fine in other PCs running Windows. When I plug it into the Archlinux box the keyboard never synchs to the bluetooth dongle (just blinks).
    This is what happens when I plug the keyboard in (NOVATEK is a wired USB keyboard):
    dmesg
    [ 51.878109] usb 4-2: USB disconnect, device number 2
    [ 55.840026] usb 4-2: new full-speed USB device number 4 using ohci_hcd
    [ 56.045166] hub 4-2:1.0: USB hub found
    [ 56.048080] hub 4-2:1.0: 3 ports detected
    [ 56.345080] usb 4-2.2: new full-speed USB device number 5 using ohci_hcd
    [ 56.479450] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input11
    [ 56.479739] generic-usb 0003:046D:C713.0004: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.2/input0
    [ 56.548115] usb 4-2.3: new full-speed USB device number 6 using ohci_hcd
    [ 56.703434] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input12
    [ 56.704162] logitech 0003:046D:C714.0005: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.3/input0
    [ 56.948094] usb 4-2.1: new full-speed USB device number 7 using ohci_hcd
    [ 57.089411] Bluetooth: Core ver 2.16
    [ 57.090507] NET: Registered protocol family 31
    [ 57.090518] Bluetooth: HCI device and connection manager initialized
    [ 57.090529] Bluetooth: HCI socket layer initialized
    [ 57.090535] Bluetooth: L2CAP socket layer initialized
    [ 57.090563] Bluetooth: SCO socket layer initialized
    [ 57.093514] usbcore: registered new interface driver btusb
    [ 90.226597] usb 4-2: USB disconnect, device number 4
    [ 90.226605] usb 4-2.1: USB disconnect, device number 7
    [ 90.227663] usb 4-2.2: USB disconnect, device number 5
    [ 90.283551] usb 4-2.3: USB disconnect, device number 6
    [ 93.210021] usb 4-2: new full-speed USB device number 8 using ohci_hcd
    [ 93.415200] hub 4-2:1.0: USB hub found
    [ 93.418081] hub 4-2:1.0: 3 ports detected
    [ 93.715081] usb 4-2.2: new full-speed USB device number 9 using ohci_hcd
    [ 93.849470] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input13
    [ 93.849808] generic-usb 0003:046D:C713.0006: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.2/input0
    [ 93.918121] usb 4-2.3: new full-speed USB device number 10 using ohci_hcd
    [ 94.057378] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input14
    [ 94.058052] logitech 0003:046D:C714.0007: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.3/input0
    [ 94.291136] usb 4-2.1: new full-speed USB device number 11 using ohci_hcd
    [ 96.400094] usb 4-2: USB disconnect, device number 8
    [ 96.400102] usb 4-2.1: USB disconnect, device number 11
    [ 96.402936] usb 4-2.2: USB disconnect, device number 9
    [ 96.460224] usb 4-2.3: USB disconnect, device number 10
    [ 99.843366] usb 4-2: new low-speed USB device number 12 using ohci_hcd
    [ 100.047501] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/input/input15
    [ 100.047781] generic-usb 0003:0603:00F2.0008: input,hidraw0: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-0000:00:06.0-2/input0
    [ 100.060244] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.1/input/input16
    [ 100.060670] generic-usb 0003:0603:00F2.0009: input,hiddev0,hidraw1: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-0000:00:06.0-2/input1
    See here for udev events.
    Xorg log:
    [ 56.500] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event2)
    [ 56.500] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
    [ 56.500] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
    [ 56.500] (**) Logitech Logitech BT Mini-Receiver: always reports core events
    [ 56.500] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event2"
    [ 56.500] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc713
    [ 56.500] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
    [ 56.501] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
    [ 56.501] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input11/event2"
    [ 56.501] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 8)
    [ 56.501] (**) Option "xkb_rules" "evdev"
    [ 56.501] (**) Option "xkb_model" "evdev"
    [ 56.501] (**) Option "xkb_layout" "us"
    [ 56.720] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/mouse1)
    [ 56.720] (II) No input driver specified, ignoring this device.
    [ 56.720] (II) This device may have been added with another device file.
    [ 56.721] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event3)
    [ 56.721] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev pointer catchall"
    [ 56.721] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
    [ 56.721] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
    [ 56.721] (**) Logitech Logitech BT Mini-Receiver: always reports core events
    [ 56.721] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event3"
    [ 56.721] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc714
    [ 56.721] (--) evdev: Logitech Logitech BT Mini-Receiver: Found 16 mouse buttons
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found scroll wheel(s)
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found relative axes
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found x and y relative axes
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found absolute axes
    [ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Forcing absolute x/y axes to exist.
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
    [ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as mouse
    [ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
    [ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Adding scrollwheel support
    [ 56.722] (**) evdev: Logitech Logitech BT Mini-Receiver: YAxisMapping: buttons 4 and 5
    [ 56.722] (**) evdev: Logitech Logitech BT Mini-Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 56.722] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input12/event3"
    [ 56.722] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 9)
    [ 56.722] (**) Option "xkb_rules" "evdev"
    [ 56.722] (**) Option "xkb_model" "evdev"
    [ 56.722] (**) Option "xkb_layout" "us"
    [ 56.723] (II) evdev: Logitech Logitech BT Mini-Receiver: initialized for relative axes.
    [ 56.723] (WW) evdev: Logitech Logitech BT Mini-Receiver: ignoring absolute axes.
    [ 56.724] (**) Logitech Logitech BT Mini-Receiver: (accel) keeping acceleration scheme 1
    [ 56.724] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration profile 0
    [ 56.725] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration factor: 2.000
    [ 56.725] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration threshold: 4
    [ 90.266] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
    [ 90.267] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
    [ 90.267] (II) UnloadModule: "evdev"
    [ 90.363] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
    [ 90.364] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
    [ 90.364] (II) UnloadModule: "evdev"
    [ 93.870] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event2)
    [ 93.870] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
    [ 93.870] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
    [ 93.871] (**) Logitech Logitech BT Mini-Receiver: always reports core events
    [ 93.871] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event2"
    [ 93.871] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc713
    [ 93.871] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
    [ 93.871] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
    [ 93.871] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input13/event2"
    [ 93.871] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 8)
    [ 93.871] (**) Option "xkb_rules" "evdev"
    [ 93.871] (**) Option "xkb_model" "evdev"
    [ 93.871] (**) Option "xkb_layout" "us"
    [ 94.083] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event3)
    [ 94.083] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev pointer catchall"
    [ 94.083] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
    [ 94.083] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
    [ 94.084] (**) Logitech Logitech BT Mini-Receiver: always reports core events
    [ 94.084] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event3"
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc714
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found 16 mouse buttons
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found scroll wheel(s)
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found relative axes
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found x and y relative axes
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found absolute axes
    [ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Forcing absolute x/y axes to exist.
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
    [ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as mouse
    [ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
    [ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Adding scrollwheel support
    [ 94.090] (**) evdev: Logitech Logitech BT Mini-Receiver: YAxisMapping: buttons 4 and 5
    [ 94.090] (**) evdev: Logitech Logitech BT Mini-Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 94.090] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input14/event3"
    [ 94.090] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 9)
    [ 94.090] (**) Option "xkb_rules" "evdev"
    [ 94.091] (**) Option "xkb_model" "evdev"
    [ 94.091] (**) Option "xkb_layout" "us"
    [ 94.091] (II) evdev: Logitech Logitech BT Mini-Receiver: initialized for relative axes.
    [ 94.091] (WW) evdev: Logitech Logitech BT Mini-Receiver: ignoring absolute axes.
    [ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) keeping acceleration scheme 1
    [ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration profile 0
    [ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration factor: 2.000
    [ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration threshold: 4
    [ 94.094] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/mouse1)
    [ 94.094] (II) No input driver specified, ignoring this device.
    [ 94.094] (II) This device may have been added with another device file.
    [ 96.443] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
    [ 96.444] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
    [ 96.444] (II) UnloadModule: "evdev"
    [ 96.536] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
    [ 96.537] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
    [ 96.538] (II) UnloadModule: "evdev"
    [ 100.084] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event3)
    [ 100.084] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 100.084] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
    [ 100.084] (**) NOVATEK USB Keyboard: always reports core events
    [ 100.084] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event3"
    [ 100.084] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
    [ 100.084] (--) evdev: NOVATEK USB Keyboard: Found 20 mouse buttons
    [ 100.084] (--) evdev: NOVATEK USB Keyboard: Found keys
    [ 100.084] (II) evdev: NOVATEK USB Keyboard: Configuring as mouse
    [ 100.084] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
    [ 100.085] (**) evdev: NOVATEK USB Keyboard: YAxisMapping: buttons 4 and 5
    [ 100.085] (**) evdev: NOVATEK USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 100.085] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.1/input/input16/event3"
    [ 100.085] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 8)
    [ 100.085] (**) Option "xkb_rules" "evdev"
    [ 100.085] (**) Option "xkb_model" "evdev"
    [ 100.085] (**) Option "xkb_layout" "us"
    [ 100.087] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event2)
    [ 100.088] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 100.088] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
    [ 100.088] (**) NOVATEK USB Keyboard: always reports core events
    [ 100.088] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event2"
    [ 100.088] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
    [ 100.088] (--) evdev: NOVATEK USB Keyboard: Found keys
    [ 100.088] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
    [ 100.088] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/input/input15/event2"
    [ 100.088] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 9)
    [ 100.088] (**) Option "xkb_rules" "evdev"
    [ 100.088] (**) Option "xkb_model" "evdev"
    [ 100.088] (**) Option "xkb_layout" "us"
    Anyone have a clue what's wrong? Thanks,

    Splex wrote:
    I also prefer to not run the dongle in bluetooth mode... it causes so many headaches.
    There may be a better way to disable the bluetooth mode, but you can comment out the 'Logitech devices' rule in /usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules:
    # Logitech devices
    #KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \
    # RUN+="hid2hci --method=logitech-hid --devpath=%p"
    Once you save the changes, simply replug your dongle, hit the connect buttons and it should work as if it is wired.
    Whenever udev is upgraded, the rule file will be overwritten...  you can add this to your /etc/pacman.conf to prevent it from being overwritten:
    NoUpgrade = usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules
    If anyone knows of a better way to prevent the default udev rules from switching the dongle to HCI mode, please speak up
    Just tried this, didn't work for me :-/
    grr.

  • PRINT SCREEN WITH A LOGITECH KEYBOARD

    CAN YOU PLEASE HELP ME I BOUGHT THIS WIRELESS LOGITECH KEYBOARD AND PAIRED IT WITH MY MAC DESKTOP COMPUTER. AM TRYING TO PRINTSCREEN BUT IT DOES NOT WANT TO. CAN ANYONE PLEASE HELP ME WITH THIS? THANK YOU!

    Press the Shift, Command, and 3 keys to capture the whole screen.
    Press the Shift, Command, and 4 keys to capture a draggable part of the screen, or follow it with the spacebar to capture a window.
    Open the PNG on the desktop. Alternatively, combine either of the above with the Control key to put the screenshot onto the clipboard instead of the desktop.
    (124233)

  • Logitech wireless solar keyboard K750 for MAC OSX OS 10x8x

    is the logitech wireless solar keyboard K750 an acceptable paring choice for the MAC OS X Mountain Lion OS 10x8x

    You have the MacBookPro6,2, the Edsel of Macs. It may be covered by this program:
    MacBook Pro (15-inch, Mid 2010): Intermittent black screen or loss of video
    Make a "Genius" appointment at an Apple Store to have the machine tested. The routine hardware diagnostics used by service providers may not detect the fault. There is a specific test for this issue.
    Print the first page of the panic report, and the support page linked above, and bring them with you.
    Note that the replacement program only applies within three years of purchase. If you wait beyond that date, Apple may refuse the service.
    Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
    *An SSD doesn't need to be zeroed.
    You may be able to stop the panics by disabling automatic graphics switching in the Energy Saver preference pane, but that's not a solution. 
    Most likely, the logic board will be replaced. Sometimes the replacement part is also defective, so be prepared for that possibility.

  • Wireless Aluminum Keyboard Troubleshooting

    If you're having issues with your Apple Wireless (Aluminum) Keyboard disconnecting, there are a few things you can try.
    First, check your wireless network configuration to see if you can avoid interference. See this post in another topic:
    http://discussions.apple.com/message.jspa?messageID=5783742#5783742
    Although I did have success with tweaking my wifi setup, my keyboard disconnect problem returned again a couple of weeks ago. I had recently upgraded to Leopard (10.5.1) which may have contributed - although I had been using wired ethernet, and switched back to wifi around the same time as my Leopard upgrade.
    Like others have posted, I also noticed the bluetooth daemon log errors in my system log. To look for them, you can open console.app, and search for "blued" in the system.log and also its archive history. Here's an example:
    +Jan 25 09:17:22 Macintosh-2 kernel[0]: IOBluetoothHCIRequest::Create [0x55da000] Request OpCode 0000 Generated by: blued (47) status: 0 timeout 1000. has a too small timeout, a reasonable value would be 5000 (5 seconds)+
    Here are some other things to try. You should only try one at a time - so that you can tell which change fixed your problem.
    1. In the Bluetooth System Preferences panel, unpair your keyboard, and re-pair it again
    2. Also in the Bluetooth System Preferences panel, add the keyboard to your favorites. To do this in Leopard: select the keyboard in the bluetooth devices list. Click on the tasks cog at the foot of that pane (just beside the plus and minus). Select "Show more info". Select "Add To Favorites".
    3. Reset the bluetooth preferences by moving system preference files. Warning: only try this if you are comfortable using the OS X terminal!! :
    sudo mv /var/root/Library/Preferences/blued.plist /var/root/Library/Preferences/blued.plist.old
    sudo mv /var/root/Library/Preferences/com.apple.Bluetooth.plist /var/root/Library/Preferences/com.apple.Bluetooth.plist.old
    (you will need to enter your password at least once, and then will need to restart your machine).
    Keep a log of all the things you've tried. If none of these work, its probably time to call AppleCare. If you have one of the new Apple (Aluminum) Wireless Keyboards, it is still covered by warranty at this point.

    It sounds like the bluetooth in both of your keyboards has simply died. If it's still under warranty (if it has one), take it to the apple store and show them. They may give you a new one. For future reference, the new wired USB keyboard is now exactly the same as the wireless (except that it has a wire), and you won't face any bluetooth issues like that. You can get the new wired keyboard here:
    http://store.apple.com/us/product/MB869LL/A?fnode=MTY1NDA1Mg&mco=NDE4NjI4Mg
    Also, if you're willing to spend a bit more money, Macworld rated the Logitech DiNovo Edge Keyboard very highly. Here's a link to that:
    http://store.apple.com/us/product/TU938LL/A?fnode=MTY1NDA1Mg&mco=MjgzMTkxNA
    Hope this helps.

  • How much longer before wireless ThinkPad keyboard?

    How much longer do we have to wait for a wireless ThinkPad keyboard?
    Current ThinkPad USB keyboard with TrackPoint is ridiculously priced, considering it's on a wire, while you can buy a very decent wireless keyboard from Logitech for half the price. (I'm referring to the K340, which has quite a decent key-press experience.)
    Seriously, nowadays wireless keyboards are no rocket science, nor expensive to manufacture. Lenovo totally dropped the ball here. Or maybe Lenovo thinks its Lenovo-branded wireless keyboards are reasonable competition for the ThinkPad family? Well, either way, Logitech wins.
    Get your act together!
    Of course I realize I'm most likely talking to a wall. After all this is the company that has just released it's a top-shelf laptop family (X220) that lacks USB 3.0. And in the past - workstations for CG artists and CAD engineers (T61p) with a TN display and a D-Sub port. Also, 16:9 displays (i.e. a ratio useful only in movies) in business laptops.
    Seriously, you need to hire a new person for feature policy. Someone with common sense.

    I second that, third that and fouth that.  Instead Lenovo seems to be heading in the opposite direction w/ the latest USB keyboard dropping the UltraNav and keeping trackpoint only.  
    A wireless UltraNav would be a kick butt wireless accessory which I'd buy in a flat heartbeat.  Just think how useful it would be home theater setups or just in general... as I am having so many issues w/ my USB Ultranav and doc 3.
    My dentist office uses a wireless setup in each patient room and they have a wirelss keyboard and mouse.. you should see them using the mouse sometimes.  A wireless UltraNav is the best of both options! 
    If I could take the keyboard off my W510 and the fingerprint reader and integrate that into a wirelss ultranav.. then there's perfection.
    Later. G.Mobley

  • Non-wireless backlit keyboard

    Looking for a non-wireless backlit keyboard. Have done lots of searching online and in forums but finding very little useful info. Anyone have one that they really like?
    Thanks.

    I tried a few shortcuts that make use of the "control" key on the Mac, and the Logitech keyboard's CRTL key works just fine. Examples:
    Control+mouse click = right click
    Control-Command-Up Arrow = "Open enclosed folder in a new window"
    The dedicated "Windows" key performs the "command" function just fine as you'd expect.
    The only thing I haven't tried is getting the Logitech's F1-F12 keys to map to the respective functions on the MacBook's built in keyboard, namely brightness adjustment, keyboard backlight adjustment (as useful as that could be in this case anyway), volume, and eject. I should note thought that for volume/mute the dedicated Logitech keys on the right side work just fine without any tinkering, and for the rest (Exposé/Spaces/Dashboard) you can just map the F key directly to trigger them.
    Hope this helps!

  • I'm having problems with a wireless Logitech mouse

    Since upgrading to ML i'm having problems with a wireless Logitech mouse that worked well prior to the update. I'm using the current Logitech Control Center software. No other mouse software is on my Mac Mini. If I use a Guest Aacount the problems ( wheel and back button ) are not present. Any suggestions?

    You might try the Logitech support site. There are communities on there:
    http://www.logitech.com/en-us/support/keyboard-mice-combos
    Here is a link to drivers:
    Logitech Drivers
    You might check your home folder/Library to see if you can find a Logitec .plist.
    You need to look in your user Library/Preferences for the .plist. Hold down the option key while using the Finder "Go To Folder" command. Enter ~/Library. Delete the .plist(s) for the mouse.
    If you prefer to make your user library permanently visible, use the Terminal command found below.
    http://osxdaily.com/2011/07/04/show-library-directory-in-mac-os-x-lion/
    You might want to bookmark the command. I had to use it again after I installed 10.8.2. I have also been informed that if you drag the user library to Finder it will remain visible.

  • Does apple plan on ever having a wireless backlit keyboard for the iMac line

    Does apple plan on ever having a wireless backlit keyboard for the iMac line

    Meanwhile Logitech makes one that might suit:
    http://www.logitech.com/en-us/product/illuminated-keyboard-for-mac-ipad-iphone

  • Apple wireless BT keyboard with TEXT MESSAGING?

    I know that I can sync the Apple wireless bluetooth keyboard with the my iPhone 4, but I just want to verify that it will work with text messaging, in addition to the usual email, etc. apps. Frankly, that's the main reason I need it. I messed up my elbow from texting so much. I don't want to, but I MUST text a lot, so I figured I'd get the keyboard to save elbow injuries. Sounds silly -- lugging around a wireless keyboard in order to text... but it actually wouldn't be so bad. I do a lot of texting from my house, anyway.
    One more thing -- The wireless keyboard can only be paired with one device at a time, right?

    The Bluetooth keyboard will work with the messaging application.
    I know I always turn the Bluetooth off on the iPhone so when I pull out my keyboard it is a bit of a pain in the ***. Granted I only use it with long emails on the road that would take an hour to write with the keyboard on the iPhone, so it's not too bad. The iPad dock keyboard will also work with the iPhone and iOS4.x so if you need a keyboard and don't want to deal with the Bluetooth than that is an option too, just a thought.
    As far as the Bluetooth keyboard goes it can only be paired with one device at a time.

  • A s d f g keys not working on a wireless Apple keyboard for Imac

    a s d f g keys not working on a wireless Apple keyboard for Imac.
    When I type they on't work.
    *Exmple o complete entence.
    Plee help! Thi i very rutrtin. I on't wnt to ue cut n pte or ome letter.
    Thnk you in vnce.

    Make a Service appointment for the keyboard at your local AASP.
    Apple - Find Locations
    I'm not sure how old it is, but it is covered for 1 full year as long as it didn't take that 19 story dive.

  • Wireless mouse/keyboard intermittent dis-connects

    In the last three days, I have looked at over 20 different posts regarding wireless mouse/keyboard disconnect problems. Thew fixes ranged all over the board and NONE fixed it. And, none of these problems matched mine exactly, except for one other. I too, have two iMacs and this problem has over the last few days gotten increasingly worse and irritating. Regardless of what you're doing, whether it is actual productive work, or playing a stupid game on your computer, when your mouse quits responding, and the graphic flashed on the screen "MOUSE DISCONNECTED", it irritates.
    I think a senior apple tech finally pin-pointed the problem, at least for my two systems. It has nothing at all to do with Bluetooth or Wireless networking. I tried ALL of those fixes including resetting the SMC. None fixed it.
    Here is what the tech had me do. Under System Preferences > Users & Groups > My Login, I then clicked on "Login items. I was astounded to see a list that exceeded the size of the window of "startup" programs that have been installed from iTunes Helper, to Dropbox to blah, blah, blah. You name it. He had me remove ALL of them except iTunes Helper. one item "Connect service (all users) could not be removed. However, as we later discussed, the specific item the I believe to be the culprit was "Bittorrent". I've forgotten what I downloaded that used that as the download agent, but in the future, I shall NEVER AGAIN use it for ANY reason. I also removed from the applications area, some non-used programs (that probably weren't the problem, but...), emptied the trash, re-booted and have not had the problem since. I want to stress here, that if your problem is actually Bluetooth or Wireless network related, this will not fix it. However, my mouse had gotten really molassesy in that when I would try to quickly move from one spot to another on the screen, it took some time to catch up, as if something else had control. That's what I think Bittorrent or someone trying to share one of my files was causing. I don't share my files. Period. I didn't realize that it could be subverted to that use of I wouldn't have ever used it in the first place.
    Anyway, neither one of my iMacs has exhibited ANY of the former symptoms since clearing that list on each system. Turns out, my second iMac also had Bittorrent in the list. That's about the only thing the two have in common besides Yosemite 10.10.3. Maybe this will help, maybe it won't. I sure hope it does. Forums like this one are extremely helpful to me.

    I had the same problem... didn't find anything useful in the forums.  Just on a whim, I went to the
    Control Panel | Device Manager | Universal Serial Bus Controllers
    For each "Hub", right click and select "properties"
    On each properties page, select "Power Management" tab
    On each power management tab "uncheck" the "Allow the computer to turn off..."
    I did this for the Generic USB Hubs, the USB Root Hubs, and the Reneasas...Hub.   After that was completed, all USB ports started working immediately.  So far, they are staying working but it has only been an hour or so.   Will report back if this doesn't stick.    Also, there may be a more elegant solution... but this works for now.

  • Wireless PRO Keyboard - no longer works on G4 10.4.11 but does on iMac 10.6

    Wireless Pro keyboard will no longer pair with my wireless mouse. My G4 w/dongle, will recognize my wife's new iMac keyboard in another room. The Pro board works fine on the iMac, which confuses the dickens out of me?
    Tried deleting pref files for Bluetooth, but all that did was get the iMac board to be found and now no longer finds the Pro board. The wireless mouse works fine.
    Background: spilled some Cabernet on the Pro board, but I'm certain it didn't fry it. Took it apart and cleaned it as good as new, but neither of my bluetooth dongles (D-Link DBT-120s) are no longer able to get it to pair up?
    Considering it has no issue at all with the iMac I'm wondering it the dongles are too old an architecture and I need to get a newer version of bluetooth adapter?
    Message was edited by: Dusty Rhoades

    The Magic Mouse is not compatible with your operating system. See here, at the bottom:
    http://www.apple.com/magicmouse/
    I imagine that your new wireless keyboard, if it's Apple branded, is this one, which is also not compatible with your OS:
    http://www.apple.com/keyboard/
    Again, the system requirements are on that page. They should also have been on the boxes at the store or on the web site before you bought them.
    You need to upgrade to either 10.5 (Leopard; call the Apple phone sales line, as there are no more available in stores) or 10.6 (Snow Leopard; available everywhere Mac software is sold).

Maybe you are looking for

  • Payables Trial Balance

    Hi, We are on 11.5.10, we have 2 questions on using XML publisher with AP trial Balance.. 1. Even if we run the report for a specific supplier the text output is only a page, but the XML output is so huge it cannot be save on our desktop... i have se

  • IMessage says that my Apple ID password is incorrect, so I changed it and it continues to give me the same message. What is the problem?

    I have an iPhone 5 and it kicked me out of iMessage. When I went to reactivate it, it told me that my username or password was incorrect. So I changed my password. Still said it was incorrect. However, I can login to iTunes (and here) with the same p

  • Generating RSA keys based on p, q, and public exponent

    Hi, The problem is the following. I need to generate an RSA key pair on the card based on pre-defined P, Q and public exponent. The KeyPair specs syas that if the public exponent is pre-initialized it will be retained. All other values are overwritte

  • Drilldown report error

    Hi experts We have BW reports .. From main report,at any hierarchy level,if we rightclick we get option to jump to other reports via Go To. Suppose I open one Go To report called 'A' from one hierarchy level in main report . Then I add drilldown in m

  • Bisecting a line segment with smart guides?

    Is it possible to use smart guides to place an anchor point exactly in the middle of a line segment?