Keyboard Layout Problem in Bootcamp Using Windows 7

Both OSX, bootcamp and Windows 7 are the latest versions and all up to date and I have had this problem ever since I first started using Windows 7. Everything has worked smoothly and without problems except for my keyboard. No matter what program I am in when using windows 7 certian keys do not work as intended. All of the letters and numbers work as intended but things like the question mark key type this like É instead.
Question mark =É
Greater than symbol= '
Less than symbol = "
The bracket keys = ¨Çç
backslash = à
forward slash = É
Quotation mark = È
My question would be is this something that always happens in bootcamp Windows 7 that just needs to be changed or is it out of the ordinary for the characters to be bound to keys incorrrectly like this.

You prob do not have the drivers installed. Takes a separate disc sometimes. There is a box to check during the partitioning and installation which has to do with downloading the latest drivers. You gotta do that to make much of anything work. If nothing else, go to an Apple reseller in your area or Apple Store if you are so lucky, and get some help. Is not the easiest thing to get all that set up correctly, but it does work well if you got the drivers installed. I have an aviation site which is not yet Mac compatible, so also do the Bootcamp thing with Windows, in order to do my thing on Jeppesen. Hang in there and get some help if you need.

Similar Messages

  • Keyboard layout problems in Gnome

    I'm not sure if it was a recent upgrade that did it or not, but in gnome my keyboard layout is only half right. I checked the keyboard manager in the gnome menu and it was set to Generic 105 key (INTEL).
    In xorg.conf the keyboard is listed as pc105. In KDE the keyboard works normally.

    bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
    You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbLayout" "us"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc104"
    EndSection
    Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
    Last edited by Captain Spaulding (2007-04-03 16:50:46)

  • Dwm and non-english keyboard layouts problem

    Hi all,
    I am using dwm 5.5. I'm Greek so I change between keyboard layouts all the time,
    see the relevant xorg.conf section:
    Section "InputDevice"
    Identifier "Generic Keyboard"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us,gr"
    Option "XkbVariant" ","
    Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
    EndSection
    Now the thing is that whenever I switch to Greek (by pressing Alt+Shift) the
    dwm tags (1,2,...,9) are not clickable (keyboard shortcuts do work
    though, so it's not a very big problem).
    Do you have any ideas about how to fix that behavior? I'd go to the dwm irc
    channel and ask them, but I'll be a "newbie asking stupid questions" so I
    preferred to ask here
    Thanks in advance
    Last edited by geo909 (2010-01-08 17:23:29)

    thayer wrote:Your best bet would be to post your problem to the dwm mailing list:
    [email protected]
    Will do...
    Thanks!

  • Non-US keyboard layout problem with VNC

    Hi everyone,
    I've got an arch box at work running tigervnc through an ssh tunnel so that I can work from home when I need to.
    Everything is great, as long as I'm using and ASCII keyboard layout.
    When I switch layouts, the keystrokes just don't get through to the server.
    Here's  what I use to switch layouts:
    setxkbmap -layout us,ru -option 'grp:alt_shift_toggle'
    So I need to type in russian, and I hit alt-shift, as usual, and start typing, but nothing is echoed back to me.  I can tell that the keystrokes are just not getting to the destination because if I'm at a terminal and I'm switched to the ru layout and I type something and hit enter, I just get a newline, as if there was nothing typed at all.
    Any ideas?

    Hi,
    Why are the characters mixed up in the session?
    This issue can occur if the keyboard language has been switched on the remote PC while running a remote desktop session. In the case you would like to switch to a different keyboard
    language follow these instructions.
    Important:
    The remote PC selects the system language of the device running the remote desktop client and not the keyboard language. When switching the keyboard language on your device,
    you need to manually switch the keyboard language on the remote PC.
    1. Open settings on your device.
    2. Tap General and then tap International.
    3. Tap Language and select the language running on the remote PC.
    4. Open the RD Client and connect to the remote PC and check if the Windows keyboard language matches the language that you selected.
    Quote from
    Remote Desktop Client on Mac: FAQ
    Thanks.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • [E17] lock and keyboard layout problems when suspend

    Hello,
    I just installed E17 on my Dell Vostro laptop. The main problem I have is related to the suspend mode.
    In settings > screen > screen lock, I enabled the option "lock on suspend" and the keyboard layout is selected to "be (default, basic)" (I have a belgian keyboard).
    When I use the menu system > suspend, the screen is locked. But when I suspend my laptop by closing the lid (I see the power light indicator blinking on the side, so it's suspended) the screen is not locked when I open it.
    Also related to the suspend mode. The layout is set to belgian (in the screen config as explained above but also in vconsole.conf and in /etc/X11/xorg.conf.d/10-keyboard.conf). When I put the luks decryption key or when E17 starts at boot, I have the right layout. However when I resume the laptop after being suspended, the layout is switched to qwerty (en_us I guess).
    Any idea why ?
    Thank you
    PS: this problem is maybe more related to E17 than to Archlinux but I haven't found any forum about enlightenment. If you think I have better chances somewhere else, let me know.

    I was having problems with E17 after a fresh install (mixer problem, key bindings, etc), and I fixed it by deleting the configuration files at
    ~/.e
    as the wiki says.

  • [SOLVED] Keyboard layout problems

    Hi community,
    I fresh installed arch linux and I rly like it. After playing a little around and installing the awesome wm I can't set the croatian keyboard layout.
    My xorg.config file:
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    Option "Xinerama" "0"
    EndSection
    Section "Files"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbModel" "logicd"
    Option "XkbLayout" "hr"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Arnos Instruments F-417"
    HorizSync 24.0 - 80.0
    VertRefresh 49.0 - 75.0
    Option "DPMS"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 6600 GT"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "1"
    Option "TwinViewXineramaInfoOrder" "DFP-0"
    Option "metamodes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    My Xorg.0.log file:
    [ 2186.778]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 2186.778]
    X.Org X Server 1.8.1.902 (1.8.2 RC 2)
    Release Date: 2010-06-21
    [ 2186.778] X Protocol Version 11, Revision 0
    [ 2186.778] Build Operating System: Linux 2.6.34-ARCH x86_64
    [ 2186.778] Current Operating System: Linux arch 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 22:12:11 CEST 2010 x86_64
    [ 2186.778] Kernel command line: root=/dev/sda5 ro
    [ 2186.778] Build Date: 21 June 2010 12:01:49PM
    [ 2186.778]
    [ 2186.779] Current version of pixman: 0.18.2
    [ 2186.779] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 2186.779] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 2186.779] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 22 13:23:50 2010
    [ 2186.779] (==) Using config file: "/etc/X11/xorg.conf"
    [ 2186.779] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 2186.779] (==) ServerLayout "Layout0"
    [ 2186.779] (**) |-->Screen "Screen0" (0)
    [ 2186.779] (**) | |-->Monitor "Monitor0"
    [ 2186.779] (**) | |-->Device "Device0"
    [ 2186.779] (**) |-->Input Device "Keyboard0"
    [ 2186.779] (**) |-->Input Device "Mouse0"
    [ 2186.780] (**) Option "Xinerama" "0"
    [ 2186.780] (==) Automatically adding devices
    [ 2186.780] (==) Automatically enabling devices
    [ 2186.780] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 2186.780] Entry deleted from font path.
    [ 2186.780] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 2186.780] Entry deleted from font path.
    [ 2186.780] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 2186.780] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 2186.780] (WW) Disabling Keyboard0
    [ 2186.780] (WW) Disabling Mouse0
    [ 2186.780] (II) Loader magic: 0x7ce880
    [ 2186.780] (II) Module ABI versions:
    [ 2186.780] X.Org ANSI C Emulation: 0.4
    [ 2186.780] X.Org Video Driver: 7.0
    [ 2186.780] X.Org XInput driver : 9.0
    [ 2186.780] X.Org Server Extension : 3.0
    [ 2186.786] (--) PCI:*(0:1:0:0) 10de:00f1:0000:0000 nVidia Corporation NV43 [GeForce 6600 GT] rev 162, Mem @ 0xf8000000/16777216, 0xe0000000/268435456, 0xf9000000/16777216, BIOS @ 0x????????/131072
    [ 2186.787] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 2186.787] (II) LoadModule: "extmod"
    [ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 2186.787] (II) Module extmod: vendor="X.Org Foundation"
    [ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
    [ 2186.787] Module class: X.Org Server Extension
    [ 2186.787] ABI class: X.Org Server Extension, version 3.0
    [ 2186.787] (II) Loading extension MIT-SCREEN-SAVER
    [ 2186.787] (II) Loading extension XFree86-VidModeExtension
    [ 2186.787] (II) Loading extension XFree86-DGA
    [ 2186.787] (II) Loading extension DPMS
    [ 2186.787] (II) Loading extension XVideo
    [ 2186.787] (II) Loading extension XVideo-MotionCompensation
    [ 2186.787] (II) Loading extension X-Resource
    [ 2186.787] (II) LoadModule: "dbe"
    [ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 2186.787] (II) Module dbe: vendor="X.Org Foundation"
    [ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
    [ 2186.788] Module class: X.Org Server Extension
    [ 2186.788] ABI class: X.Org Server Extension, version 3.0
    [ 2186.788] (II) Loading extension DOUBLE-BUFFER
    [ 2186.788] (II) LoadModule: "glx"
    [ 2186.788] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 2186.813] (II) Module glx: vendor="NVIDIA Corporation"
    [ 2186.813] compiled for 4.0.2, module version = 1.0.0
    [ 2186.813] Module class: X.Org Server Extension
    [ 2186.813] (II) NVIDIA GLX Module 256.35 Wed Jun 16 19:10:31 PDT 2010
    [ 2186.813] (II) Loading extension GLX
    [ 2186.813] (II) LoadModule: "record"
    [ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 2186.814] (II) Module record: vendor="X.Org Foundation"
    [ 2186.814] compiled for 1.8.1.902, module version = 1.13.0
    [ 2186.814] Module class: X.Org Server Extension
    [ 2186.814] ABI class: X.Org Server Extension, version 3.0
    [ 2186.814] (II) Loading extension RECORD
    [ 2186.814] (II) LoadModule: "dri"
    [ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 2186.814] (II) Module dri: vendor="X.Org Foundation"
    [ 2186.814] compiled for 1.8.1.902, module version = 1.0.0
    [ 2186.814] ABI class: X.Org Server Extension, version 3.0
    [ 2186.814] (II) Loading extension XFree86-DRI
    [ 2186.814] (II) LoadModule: "dri2"
    [ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 2186.814] (II) Module dri2: vendor="X.Org Foundation"
    [ 2186.814] compiled for 1.8.1.902, module version = 1.2.0
    [ 2186.815] ABI class: X.Org Server Extension, version 3.0
    [ 2186.815] (II) Loading extension DRI2
    [ 2186.815] (II) LoadModule: "nvidia"
    [ 2186.815] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 2186.816] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 2186.816] compiled for 4.0.2, module version = 1.0.0
    [ 2186.816] Module class: X.Org Video Driver
    [ 2186.816] (II) NVIDIA dlloader X Driver 256.35 Wed Jun 16 18:45:02 PDT 2010
    [ 2186.816] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 2186.816] (++) using VT number 7
    [ 2186.820] (II) Primary Device is: PCI 01@00:00:0
    [ 2186.820] (II) Loading sub module "fb"
    [ 2186.820] (II) LoadModule: "fb"
    [ 2186.820] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 2186.821] (II) Module fb: vendor="X.Org Foundation"
    [ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
    [ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 2186.821] (II) Loading sub module "wfb"
    [ 2186.821] (II) LoadModule: "wfb"
    [ 2186.821] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 2186.821] (II) Module wfb: vendor="X.Org Foundation"
    [ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
    [ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 2186.821] (II) Loading sub module "ramdac"
    [ 2186.821] (II) LoadModule: "ramdac"
    [ 2186.821] (II) Module "ramdac" already built-in
    [ 2186.821] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    [ 2186.821] (==) NVIDIA(0): RGB weight 888
    [ 2186.821] (==) NVIDIA(0): Default visual is TrueColor
    [ 2186.821] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 2186.821] (**) NVIDIA(0): Option "TwinView" "1"
    [ 2186.822] (**) NVIDIA(0): Option "MetaModes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
    [ 2186.822] (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
    [ 2186.822] (**) NVIDIA(0): Enabling RENDER acceleration
    [ 2186.822] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
    [ 2186.822] (II) NVIDIA(0): enabled.
    [ 2188.363] (II) NVIDIA(0): NVIDIA GPU GeForce 6600 GT (NV43) at PCI:1:0:0 (GPU-0)
    [ 2188.363] (--) NVIDIA(0): Memory: 131072 kBytes
    [ 2188.363] (--) NVIDIA(0): VideoBIOS: 05.43.02.39.00
    [ 2188.363] (II) NVIDIA(0): Detected AGP rate: 8X
    [ 2188.363] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
    [ 2188.363] (--) NVIDIA(0): Connected display device(s) on GeForce 6600 GT at PCI:1:0:0:
    [ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0)
    [ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0)
    [ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0): 400.0 MHz maximum pixel
    [ 2188.363] (--) NVIDIA(0): clock
    [ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): 155.0 MHz maximum pixel clock
    [ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): Internal Single Link TMDS
    [ 2188.363] (**) NVIDIA(0): TwinView enabled
    [ 2188.363] (II) NVIDIA(0): Display Devices found referenced in MetaMode: CRT-0, DFP-0
    [ 2188.364] (II) NVIDIA(0): Assigned Display Devices: CRT-0, DFP-0
    [ 2188.364] (II) NVIDIA(0): Validated modes:
    [ 2188.364] (II) NVIDIA(0):
    [ 2188.364] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
    [ 2188.364] (II) NVIDIA(0): Virtual screen size determined to be 3200 x 1080
    [ 2188.364] (--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config
    [ 2188.364] (--) NVIDIA(0): option
    [ 2188.364] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
    [ 2188.364] (--) Depth 24 pixmap format is 32 bpp
    [ 2188.365] (II) NVIDIA(0): Initialized AGP GART.
    [ 2188.373] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 2188.373] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [ 2188.373] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [ 2188.373] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [ 2188.373] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [ 2188.373] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [ 2188.373] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 2188.373] (II) NVIDIA(0): Config Options in the README.
    [ 2188.373] (II) NVIDIA(0): Setting mode
    [ 2188.373] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
    [ 2188.613] (II) Loading extension NV-GLX
    [ 2188.657] (II) NVIDIA(0): Initialized OpenGL Acceleration
    [ 2188.659] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 2188.659] (II) NVIDIA(0): Initialized X Rendering Acceleration
    [ 2188.659] (==) NVIDIA(0): Backing store disabled
    [ 2188.659] (==) NVIDIA(0): Silken mouse enabled
    [ 2188.660] (**) NVIDIA(0): DPMS enabled
    [ 2188.660] (II) Loading extension NV-CONTROL
    [ 2188.661] (II) Loading extension XINERAMA
    [ 2188.661] (II) Loading sub module "dri2"
    [ 2188.661] (II) LoadModule: "dri2"
    [ 2188.661] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 2188.661] (II) NVIDIA(0): [DRI2] Setup complete
    [ 2188.661] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [ 2188.661] (==) RandR enabled
    [ 2188.661] (II) Initializing built-in extension Generic Event Extension
    [ 2188.661] (II) Initializing built-in extension SHAPE
    [ 2188.661] (II) Initializing built-in extension MIT-SHM
    [ 2188.661] (II) Initializing built-in extension XInputExtension
    [ 2188.661] (II) Initializing built-in extension XTEST
    [ 2188.661] (II) Initializing built-in extension BIG-REQUESTS
    [ 2188.661] (II) Initializing built-in extension SYNC
    [ 2188.661] (II) Initializing built-in extension XKEYBOARD
    [ 2188.661] (II) Initializing built-in extension XC-MISC
    [ 2188.661] (II) Initializing built-in extension SECURITY
    [ 2188.661] (II) Initializing built-in extension XINERAMA
    [ 2188.661] (II) Initializing built-in extension XFIXES
    [ 2188.661] (II) Initializing built-in extension RENDER
    [ 2188.661] (II) Initializing built-in extension RANDR
    [ 2188.661] (II) Initializing built-in extension COMPOSITE
    [ 2188.661] (II) Initializing built-in extension DAMAGE
    [ 2188.664] (II) Initializing extension GLX
    [ 2188.842] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 2188.842] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2188.842] (II) LoadModule: "evdev"
    [ 2188.842] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 2188.842] (II) Module evdev: vendor="X.Org Foundation"
    [ 2188.842] compiled for 1.8.0, module version = 2.4.0
    [ 2188.842] Module class: X.Org XInput Driver
    [ 2188.842] ABI class: X.Org XInput driver, version 9.0
    [ 2188.842] (**) Power Button: always reports core events
    [ 2188.842] (**) Power Button: Device: "/dev/input/event2"
    [ 2188.842] (II) Power Button: Found keys
    [ 2188.842] (II) Power Button: Configuring as keyboard
    [ 2188.842] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
    [ 2188.842] (**) Option "xkb_rules" "evdev"
    [ 2188.843] (**) Option "xkb_model" "evdev"
    [ 2188.843] (**) Option "xkb_layout" "us"
    [ 2188.883] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 2188.883] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2188.883] (**) Power Button: always reports core events
    [ 2188.883] (**) Power Button: Device: "/dev/input/event1"
    [ 2188.883] (II) Power Button: Found keys
    [ 2188.883] (II) Power Button: Configuring as keyboard
    [ 2188.883] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
    [ 2188.883] (**) Option "xkb_rules" "evdev"
    [ 2188.883] (**) Option "xkb_model" "evdev"
    [ 2188.883] (**) Option "xkb_layout" "us"
    [ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event3)
    [ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
    [ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event3"
    [ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found 3 mouse buttons
    [ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
    [ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found relative axes
    [ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
    [ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
    [ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 2188.887] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE)
    [ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
    [ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
    [ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
    [ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
    [ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
    [ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
    [ 2188.887] (II) No input driver/identifier specified (ignoring)
    [ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
    [ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
    [ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
    [ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
    [ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
    [ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
    [ 2188.888] (**) Option "xkb_rules" "evdev"
    [ 2188.888] (**) Option "xkb_model" "evdev"
    [ 2188.888] (**) Option "xkb_layout" "us"
    [ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
    [ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
    [ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
    [ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
    [ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
    [ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
    [ 2188.889] (**) Option "xkb_rules" "evdev"
    [ 2188.889] (**) Option "xkb_model" "evdev"
    [ 2188.889] (**) Option "xkb_layout" "us"
    [ 2188.891] (II) config/udev: Adding input device PC Speaker (/dev/input/event0)
    [ 2188.891] (II) No input driver/identifier specified (ignoring)
    Xorg.0.log important (I think):
    [ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
    [ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
    [ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
    [ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
    [ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
    [ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
    [ 2188.888] (**) Option "xkb_rules" "evdev"
    [ 2188.888] (**) Option "xkb_model" "evdev"
    [ 2188.888] (**) Option "xkb_layout" "us"
    [ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
    [ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
    [ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
    [ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
    [ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
    [ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
    [ 2188.889] (**) Option "xkb_rules" "evdev"
    [ 2188.889] (**) Option "xkb_model" "evdev"
    [ 2188.889] (**) Option "xkb_layout" "us"
    Why is he adding the keyboard 2 times, and why  "xkb_layout" "us"? I need hr (croatian).
    My first post Sorry, for the bad english.
    Last edited by b3no (2010-07-22 23:45:29)

    [  2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    Add this
    Section "ServerFlags"
    Option "AllowEmptyInput" "no"
    EndSection
    EditL If the above didn't help, read this http://wiki.archlinux.org/index.php/Xor … d_settings
    Last edited by karol (2010-07-22 12:06:04)

  • Keyboard layout problem at the login screen

    Hi there!
    I'm having a huge problem at the login screen just after installing OS X Lion 10.7. It seems like the keyboard layout has changed, and I need to enter some numbers in my password. I can't find the digit 9, and I really don't know if the other numbers are in the right place either. Maybe it's changed to a us layout.. What to do?

    stoneheart,
    the numbers are in the same position on a US English keyboard as they are on a Norwegian keyboard.
    If you select the Users & Groups pane of System Preferences, and select its Login Options, do you have the “Show Input menu in login window” checkbox checked? (That’s where the checkbox’s location is in Mavericks; I don’t have Lion, so I don’t know if it’s in the same location there.)

  • E70 Keyboard layout problems

    I have a brand-new E70 bought from Expansys a week ago. I have the same problem reported by other here regarding incorrect keyboard layout (e.g. "(" key produces ")" and "/" produces ","). I have not upgraded the firmware, this is the way the phone was shipped.
    I haven't found any solution in this forum or on the web yet. Any advice is appreciated. Thanks,
    -- Terrence

    bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
    You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbLayout" "us"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc104"
    EndSection
    Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
    Last edited by Captain Spaulding (2007-04-03 16:50:46)

  • Unable to change keyboard layout for all users on Windows Server 2012 R2

    Hi,
    I have a requirement where I need to support national keyboard layout for Danish for all users on that machine. When I ran the powershell with script Set-WinUserLanguageList
    -LanguageList da-DK it only sets the Danish keyboard layout to the specific logged in user.However the for other users its same English(US) keyboard which is not expected.
    Please help me how to set the Danish keyboard for all users on the machine. Its Urgent!Thanks

    Hi Mike,
    Thanks for reply.
    But I need to configure everything using powershell script. Is it possible to use powershell script to setting group policy/ adding logon script ?
    These are pretty basic administration tasks and almost always quicker to accomplish with the GUI. Why do you want to use a PowerShell script?
    EDIT: Here's some information on the topic however:
    https://technet.microsoft.com/en-us/library/cc781361%28v=ws.10%29.aspx
    http://blogs.technet.com/b/heyscriptingguy/archive/2011/01/06/use-powershell-and-group-policy-for-your-logon-script.aspx
    Don't retire TechNet! -
    (Don't give up yet - 13,225+ strong and growing)

  • Problems working offline using Windows 2003

    Hi all,
    this is not really a topic for this forum, but maybe some of you had the same problem.
    We are working with Symbol Pocket PC / Windows Mobile 2003 / Symbol Pocket Browser 2003 / SAP Mobile Engine.
    Our web application consists of an offline and an online part. The offline part is served by the Tomcat/SAP ME which is installed on the device. The offline part works as long as we are in range of the WLAN Accesspoint. As soon as we leave the range, Pocket Browser 2003 notifies that it cannot connect with the current connection settings. But the offline part does not need to connect using the WLAN connection, it just has to connect to 127.0.0.1:4444/some/application.
    Our previous configuration was:
    Symbol Pocket PC / Microsoft Pocket PC Version 3.0/ Symbol Pocket Browser 2002 / SAP Mobile Engine.
    This worked fine.
    Did anybody have similar problems? How can we fix it?
    Regards Sascha

    Hi,
    the problem is that on Windows mobile 2003 the Pocket IE cannot connect to 127.0.0.1 if no active connection is available. I found a fix on microsoft.public.pocketpc.developer. Here is the link:
    http://groups.google.com/groups?q=(localhostOR127.0.0.1)+group:microsoft.public.pocketpc.developer.*&hl=en&lr=&ie=UTF-8&selm=AE26D501-0D21-46C6-8B94-B8947FBC956C%40microsoft.com&rnum=3
    Just follow the steps desribed there and everything works fine.
    Regards,
    Sascha

  • Keyboard layout problem

    My wife has an old iBook running Mac OS X Tiger and it's been working just fine. Never any trouble at all with this sturdy old thing but today, for some odd reason, the keyboard layout got messed up out of nowhere. We're Swedish and need the Swedish layout ( åäö ) but it suddenly stopped working. The layout has changed and the @-character is now accessible while pressing Shift+2 instead of Alt+2. I have no idea why this happened and I have no clue as to how to change/restore the default layout. I've looked around in the International preference pane but nothing I did there changed a thing. Anyone else bumped into this particular problem?

    Forget this question, I found out what was wrong. My father-in-law ( who isn't too good at computers ) changed the layout by mistake by clicking the little flag and so switched the layout from Swedish Pro to US English. Problem solved.

  • Problem with bootcamp and windows xp disc

    Hi! I've been using mac for about 3-4 years now and I am fairly acquainted with my Macbook pro.
    My problems surfaced 2 days ago when a friend of mine opened it up and changed the harddrive to this: http://www.overclockersclub.com/reviews/seagate_momentus_500gb/
    My friend then did a clean install of OS X Snowleopard (not with the OS X-disc that came with my MBP) and all seemed to work fine.
    But the problem is that my MBP don't seem to recognize or can't read Windows-installation DVD's. I insert the disc, the MBP reads the disc 2-3 times and then just spits it out. I have tried this with two diffrent Windows XP SP2 discs and one Windows 7 home disc with the same result.
    Sometimes though (completely random) it seems to recognize the Windows disc and I can start the Windows installation via bootcamp, but halfway through the installation the disc still ejects.
    The funny thing is that I ONLY have this problem with Windows-discs. OS X-discs, media-DVD's and unwritten CD's is no problem at all.
    And I have repeatedly "repaired" and "reinstalled" OS X with both the snow leopard-disc and the OS X-discs that came with my MBP but I still get the same result. I have also tried SMC-resetting and doing a "safe start" but it still doesn't work.
    So... Halp? :3

    Boot Camp forum.
    https://discussions.apple.com/community/windows_software/boot_camp

  • Flash 8 Pro: Publish Preview & Keyboard Layout Problems

    Hi,
    Hoping someone can help. I am a NEW Flash 8 Pro user and have
    discovered two problems I cant seem to resolve:
    1. When I press F12 (or select Publish Preview | Default
    (HTML) in the menu), although my project publishes correctly,
    producing all the correct files (including a working HTML file), my
    browser does not open and display the swf. I tried changing my
    default browser and on several projects, but the problem persists
    2. For some reason, my keyboard is set to the US layout
    instead of the British layout...this is the only application that
    is doing this and it doesnt appear to be an option that I can
    change inside Flash.
    Can anyone help me with these issues? It would be grately
    appreciated.
    PS: I am on a high-spec Windows XP SP2 PC (if that is of any
    assistance)

    Did you ever get your issue with the F12, publish preview,
    not loading your browser? I have just upgraded from MX 2004 to 8
    and now have this issue.
    T Peluso
    [email protected]

  • Firefox cannot be closed; the following message appears: "Can't load resource file, can not run". How to solve this problem; I am using Windows XP SP3

    Whwn I want to close Firefox 9.x , a pop-up appears with the message: "Can't load resource file ......" . First I have to close this pop-up, then Firefox is closed. Also with other versions of Firefox I had this problem.

    i deleted the rdf and now the first window only (and any tabs in it) are maximised. i found this in the rdf
    <RDF:Description RDF:about="chrome://browser/content/browser.xul#main-window"
    screenX="4"
    screenY="4"
    width="1008"
    height="461"
    sizemode="Normal" />
    i tried changing normal to maximised; no effect. either i need also to change the numbers (to match a maximised window) or ff ignores this. i want to be able to open different sites in different windows, and not have to maximise them manually. ff never used to be broken, why break this? what possible security flaw was fixed by screwing up ff to never open maximised unless u hack it or delete certain config files?

  • Bootcamp: using Windows Briefcase on Mac OS

    I have just moved from Windows to Mac :)) but need to run some proprietary (Windows-based) software. So I guess bootcamp is the answer. BUT: I also made extensive use of Windows Briefcase to sync data between a server and my notebook, and want to do the same with my MacBook. So the question is: will creating a new partition and installing Windows XP on the new partition allow me to run briefcase successfully? Will it need both OS's to be running at the same time? Is that possible?
    Thanks ...!

    Both?
    A MacBook running Windows XP is almost 100% the same (outside of drivers) as it is or would be on any PC or laptop.
    If you want to run XP inside of Mac OS, you can, rather than running natively, too, using VMware Fusion or Parallels as a VM.

Maybe you are looking for