Issue with wired mouse

I recently upgraded my mid-2011 iMac from Lion to Mountain Lion (10.8.2).  I am now having trouble with my wired mouse.  I use a two-button Microsoft mouse which worked fine for a year with Snow Leopard and lion, but now gets a "sticky" pointer within a few hours.  If I reboot, the problem goes away for a few hours. Similarly, if I unplug the mouse and plug it back in the problem seems to go away for a time.
I found a few other references to this problem, but I have yet to see a solution.  Has anyone found a solution that I simply have come across yet?

EDIT:
ACTUAL FIX, AND YOU'RE NOT GONNA LIKE IT!
I've found that I only ever experienced mouse lag, when my RAM (memory) usage peaked, resulting in Windows being forced to do disk paging to cope with my lack of RAM.
You can see if this is your problem, by hitting CTRL-SHIFT-ESC to open the Task Manager, and go to the Performance tab (do this just after a fresh reboot!!! See why below.). Leave it open, and try doing a lot of things at once (open a browser with many start-up
tabs while opening some RAM-heavy program, like a programming IDE or a video editing suite). If it peaks, and your mouse subsequently lags, you probably need more RAM for your purposes.
This also explains why people can be posting so many different false "fixes". Whenever the lag occurs, because some operation needs more RAM, the data is cached
in the page file. So when people have experienced lag while using their computer, and then do something to try and fix their problem, and try the same things that made the computer lag before, all those things are already cached, and therefore won't lag anymore...until
you restart your computer, or the pagefile has been filled with new data.
The fix for me, ended up being installing more RAM. If you do not have that option, try to limit the number of programs simultaneously running on your computer. One way
to do this, is by unchecking unneeded start up programs, using these steps:
1. Start ==> Run
2. Type in: msconfig
3. Hit enter the Startup tab
4. Untick all programs THAT YOU KNOW, which you do not need to have available at start up.
Another way, is to remember to close programs when you're done with them.

Similar Messages

  • Premiere Elements 13 issue with the mouse on When I select a clip of video and move to a different place in my time line, Premiere Elements 13, will not release the clip rom the mouse.    The clip follows my mouse movements and goes to other places in my

    Premiere Elements 13 issue with the mouse on MAC OSX Yosemite 10.10.1
    When I select a clip of video and move to a different place in my time line, Premiere Elements 13, will not release the clip from the mouse.
    The clip follows my mouse movements and goes to other places in my time line.
    I try to delete these extra insertions, but the mouse will not release the clip.
    Action I’ve taken: I’ve re-installed Premiere Elements 13. Problem remains.
    This issue has consumed too much of my time and does not go away.  It ruins my video.
    Help please.
    Thanks

    I tried using the Guest Account on my Mac. In the Guest Account, Illustrator works perfect!
    Then I started wondering what processes (tools/tweaks) I run by default on my account. Turned out the problem was called by a little background tool called RightZoom. RightZoom let's the green 'zoom' button always maximize your current window.
    So thanks! Problem solved!

  • Strange issue with USB mouse and USB headset.

    Good day everyone.
    I was experiencing a rather strange issue with my mouse and headset(both USB).
    I am using KDE and ALSA, if that matters.
    They are working just fine, but sometimes, when I try to lower\raise volume, my mouse derps out. I can move it around, but I can't click on anything(sometimes though, I can click on stuff in window that was active before and sometimes only on KDE panel) until I re-plug my headset. Then, nothing can use my headset until I reboot.
    Anybody ever had that problem?

    I've had similar problems for some time now. Unfortunately, I don't know what the issue is either, but perhaps we can come up with some setup similarities and narrow it down. I have similar trouble with just alsa or with pulseaudio, so that's not it. It is unrelated to the DE, as it happened for me in both gnome 2 and xfce 4. It is not related to the machine either, as the same quirks occur in other machines with the same headset. I have had inconclusive results with downgrading to kernel26-lts, the ancient kernel. I thought at some point it messed up and I was sure the older kernel didnt help, but after trying recently-ish, I had no trouble for days -- until I found that I didn't have trouble on the main kernel either. ... then a few days later, it showed up again. Very irritating!
    https://bbs.archlinux.org/viewtopic.php?id=122475
    Does my old thread sound like your issue somewhat?
    Essentially, at times, if the headset (wireless) is changed into a different power state (unplugged/plugged) or the mic state is toggled (mute/unmute), things that could be clicked on normally cant unless theyre in the window already focused -- mostly.
    What headset are you using? 32 or 64 bit arch? Have you tried downgrading to kernel26-lts?

  • Can an iMac 10.6.7 snow leopard with wired MOUSE be upgraded to LION OX?

    Hi can you help,  Can my iMac OS X 10.6.7 that uses a wired mouse be upgraded to Lion OX if so how could I zoom the screen with my fingers as I dont have a magic mouse or magic pad?  Also can my iMac work okay if I got rid of the mouse for the pad.  I bought the iMac just 2 mnths before the new ones came out pity but love it anyway as I have had 3 windows PCs and 2 laptops but nne of them are as good as the Apple iMac.

    As long as your iMac meets the system requirements, you can buy Lion - having a wired mouse has nothing to do with the operating system; it just will not allow you to use any gestures. But I can't see why you just couldn't use it as you always have. And, as long as your iMac supports bluetooth, I'm sure you can buy a trackpad if you like - then you'd be able to use gestures.

  • Strange issue with left mouse clicking freezing other inputs on the Mac

    I'm having a strange issue with my game. I'm using Flash CS6 and a Mac.
    I've got a character that I move around the screen with keys, and you can click the left mouse button to make him throw something. The weird issue is when I click the left mouse button a lot, it seems to stop any other inputs from coming in, so for example, if I hold the right arrow key down while I'm doing a left clicking, and then let go of the right arrow key, the character will keep on moving right for a few seconds, until it finally get's the key_up event and stops.
    Even not using any mouse event handlers, so the mouse is doing nothing in the game still causes the key inputs to be delayed just by left clicking, any ideas?
    I've just tested the .swf on a PC and there was no problem, the mouse clicking was not causing any issues, so it's something peculiar to the Mac.

    Hi,
    This could be an issue if you were using Safari 5.1+ in 64bit mode. This should go away if you run Safari 5.1+ in 32 bit mode. You can change this by
    1. Go to /Applications
    2. Find Safari->RightClick->Get Info->Check 'Open in 32-bit mode' check box.
    3. Relaunch Safari 5.1 again.
    Thanks!
    Mohan

  • AVRCP Buetooth issues with Mighty Mouse interference (?) and SONY CMT-HX5BT

    Hello:
    Just got a SONY Bluetooth enabled mini stereo system (CMT-HX5BT). Knowing my iMac with OS X 10.4 doesn't support AVRCP Bluetooth (another issue entirely!) I downloaded the Softstick Audio Gateway for Mac. This will allow me to play my iTunes music on the SONY stereo. However, when the Mighty Mouse is switched on, the playback is exceptionally fragmented and almost non-existent except very short bursts. When the MM is switched off everything works wonderfully.
    I am hoping that whomever is responsible for BT in general did think that BT Mice would be used at the same time as stereos/headphones. Hopefully this is an issue with something other than BT in general such as Softstick, the MM, or OS X. Any ideas?
    Does anyone think upgrading to Leopard, and using the operating system's built -in AVRCP support be better than a third party application? Although I haven't found conclusive proof that OS X 10.5 actually has AVRCP support either. Does this mean Logitech will be getting my business as I switch back to a regular radio frequency cordless mouse?
    Thanks for any suggestions.

    Thanks for your answer, no problem... it's OK
    why don't you try with OS X 10.5... I guess the A2DP is built in Leopard (natively)
    Today I saw the CMT-HX5BT at the local shop, they obviously have no clue about its functionality with a Mac, but that mini hifi looks great and it's not even that expensive...
    maybe I should buy it anyway...

  • Does apple have an issue with magic mouse and adobe

    does Apple have a problem with magic mouse and Adobe Photoshop/Indesign/Illustrator, scrolling uncontrollable, pages moving of their own accord etc.
    If so, whats the cure and why does Apple not admit to it?
    Badgolfer4

    it's rare that a mouse would perform in a different manner between different applications
    I would troubleshoot with other apps to see if it was just adobe apps
    and then I would troubleshoot by trying a different mouse
    could be the mouse was defect

  • Delay issue with mighty mouse and macbook pro. help?

    Connected but delayed in movement. I am connected to an HD tv via HDMI and only a delay issue on the tv monitor. The mouse responds as normal on the laptop screen if I have it open, but on the TV it is delayed. Any clue as to what might be wrong? I am running HDMI to a converter for the mini display port and have seen it work many times with no delay. I have changed the batteries and reconnected/restarted the computer and the mouse numerous times. 

    Hey there, I'm on the forums because I can't get my wireless mouse to connect to my new MacBook Pro either (just got it yesterday). Bluetooth Device Manager seems to "see" it when it searches, but insists it can't connect to it, saying either "device not found" (which is ridiculous, since it's right up there in the list) or "cannot find the necessary services." Yet I cannot find anything definitive on the tubes to say that the two don't work together. Anyone else have any ideas for us??
    I should mention I changed the batteries b/c at first I thought that's all it was. When it didn't work I brought it to a 2009 MacBook Pro, and that one connected no problem ::shaking head::

  • Issues with HP Mouse, does it only work with HP devies?

    I have an HP mouse, that I am trying to use with my ASUS tablet.  It worked for a few days and then when I click my device under available devices it does not connect. I got another mouse and the same issue occured after a few days of using it. 

    Nope, an HP mouse is like any other mouse and will work on what ever Windows type machine its plugged into.
    Im not a tablet user but I will offer one thing it could be.
    BTW you didnt mention what the ASUS tablet model number is so its even harder to troubleshoot.
    Does this tablet have a keyboard dock?
    If so, connect it and check to see if the mouse was disabled with the button on the keyboard on the top row.
    I hear they have an enable/disable button on them. Possibley the 4th key from the left.
    If not then Im sorry, you will need to contact the ASUS forums.

  • I have an issue with my mouse and trackpad operating simultaneously

    I use a mouse almost exclusively with my macbook pro because I'm editing video (FCP). Recently the trackpad is working at the same time as the mouse so that if I drag my hand or wrist accidentaly across the pad it does something (very disruptive) to my video. I've looked under trackpad and bluetooth preferences and can't find any way to shut the pad off when the mouse is on. I'm not sure how it ever got turned on (the trackpad).

    Never mind. I found it under Universal Access. Problem solved.

  • Suddenly have issues with Magic Mouse

    I have used the Magic Mouse almost since it was first put on the market and really love it.
    I upgraded to Mavericks when it first came out, too. I am currently running Mavericks 10.9.2
    However, this morning I turned on my iMac and all of a sudden, when I am in Safari and swipe, it catches and freezes Safari to the point that I have to quit Safari altogether and then log back in. It scrolls up and down in Safari just fine, it's just when I attempt to go right or left. Also, when I open Calendar, the Magic Mouse won't do any scrolling at all. I can click on something within the window and it works ok, but attempting to scroll the calendar up and down to a different month/week and nothing happens. I am also running the same version of Mavericks on my MBP and the mouse of it works just fine.
    Anyone out there experiencing this also?
    Anyone out there have some helpful tips for Dummies?
    Thanks.

    Sometimes I assume things...bad idea :)
    PRAM=parameter random access memory. Reset like this:
    http://support.apple.com/kb/PH14222
    SMC=system management controller. Reset like this:
    http://support.apple.com/kb/HT3964
    Barry
    P.S. There are no dumb questions...answers, yes, but not questions.

  • Windows 7 Pro DNS issue with static IP

    0
    down vote
    favorite
    I have been unable to solve a DNS problem I am having as follows:
    I have a Windows 7 Professional (64 bit) computer running VirtualBox with a couple of Windows XP guests (not sure if this bit is relevant). After heavy file copying/transfer on both of the Windows XP machines, both the guest machines AND the host loose anything
    DNS related, so I cannot call anything by name, but by direct IP works fine. The only resolution is to reboot the (host) machine and it will then work OK for a while until it happens again. The only trigger to make it seem to happen quicker is to re-initiate
    the heavy file transfer and this then causes the DNS resolution to stop working again.
    The machine has a fixed IP address, so it isn't related to DHCP.
    I've tried the machine connected wired and wireless, no difference.
    The IP settings are manual and I have tried giving it the DNS settings of the router (normal settings) and I have also tried giving it Google's DNS servers (8.8.8.8 & 8.8.4.4). No difference.
    It seems to happen (sooner) during heavy traffic.
    Other Windows 7 machines in the network work fine (though they are Home version, not Pro).
    ONLY DNS fails, direct IP works OK.
    Reboot seems only solution at the moment.
    I am now lost as to what to try to resolve this issue, I do not really want to reload Windows 7 as it is a relatively new install... I have read about issues with wired connections on my router (BT Home Hub 2.0) so tried a wireless connection, still the
    same.
    Here is my ipconfig /all (it shows the BT Home Hub router DNS settings, but it also failed with Google's 8.8.8.8 and 8.8.4.4 entered here and also with the routers 192.168.1.254 (default).
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:\Users\G>ipconfig /all
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : e1
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
    Physical Address. . . . . . . . . : 30-85-A9-AD-07-81
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::59f:484a:827f:42ba%11(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.87(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCPv6 IAID . . . . . . . . . . . : 238060969
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
    DNS Servers . . . . . . . . . . . : 217.32.171.21
    213.120.234.30
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter VirtualBox Host-Only Network:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
    Physical Address. . . . . . . . . : 08-00-27-00-28-56
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::8d2d:7418:381b:8dc0%15(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    DHCPv6 IAID . . . . . . . . . . . : 336068647
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Tunnel adapter isatap.{486D4DCC-9CB7-417E-A796-596E0E6B1D54}:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter isatap.{67455999-75A5-436E-9EAC-12B093363132}:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    C:\Users\G>
    Any ideas where to look, or what other info to provide for any assistance?
    Many thanks in advance.

    Hi,
    This has just happened again, here is the content of the netstat results as requested...
    If I kill the VirtualBox virtual machines, it starts working again. It is as if there are no ports left, but I am not occupying that many? Surely Windows 7 can cope with this?
    I feel I am missing something important, but cannot put my finger on it...
    Further below, I have re-run the netstat command AFTER I have closed the VirtualBox machines and the system works OK.
    netstat results DURING ISSUE:
    Active Connections
      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:21             0.0.0.0:0              LISTENING       1444
     [FileZilla Server.exe]
      TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1692
     [MESMTPC.EXE]
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    0.0.0.0:110            0.0.0.0:0              LISTENING       1660
     [MEPOPS.EXE]
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       752
      RpcSs
     [svchost.exe]
      TCP    0.0.0.0:143            0.0.0.0:0              LISTENING       1524
     [MEIMAPS.exe]
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    0.0.0.0:1221           0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:2199           0.0.0.0:0              LISTENING       4820
     [VirtualBox.exe]
      TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING       1756
     [mysqld.exe]
      TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       1104
      CryptSvc
     [svchost.exe]
      TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
     [WinVNC.exe]
      TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
     [WinVNC.exe]
      TCP    0.0.0.0:8300           0.0.0.0:0              LISTENING       3464
     [sc_serv.exe]
      TCP    0.0.0.0:8301           0.0.0.0:0              LISTENING       3464
     [sc_serv.exe]
      TCP    0.0.0.0:8360           0.0.0.0:0              LISTENING       3080
     [sc_serv.exe]
      TCP    0.0.0.0:8361           0.0.0.0:0              LISTENING       3080
     [sc_serv.exe]
      TCP    0.0.0.0:9022           0.0.0.0:0              LISTENING       4804
     [VirtualBox.exe]
      TCP    0.0.0.0:9023           0.0.0.0:0              LISTENING       4804
     [VirtualBox.exe]
      TCP    0.0.0.0:9080           0.0.0.0:0              LISTENING       4804
     [VirtualBox.exe]
      TCP    0.0.0.0:10001          0.0.0.0:0              LISTENING       4828
     [VirtualBox.exe]
      TCP    0.0.0.0:10002          0.0.0.0:0              LISTENING       4828
     [VirtualBox.exe]
      TCP    0.0.0.0:10003          0.0.0.0:0              LISTENING       4828
     [VirtualBox.exe]
      TCP    0.0.0.0:10011          0.0.0.0:0              LISTENING       4780
     [VirtualBox.exe]
      TCP    0.0.0.0:10012          0.0.0.0:0              LISTENING       4780
     [VirtualBox.exe]
      TCP    0.0.0.0:10013          0.0.0.0:0              LISTENING       4780
     [VirtualBox.exe]
      TCP    0.0.0.0:25566          0.0.0.0:0              LISTENING       3648
     [TerrariaServer.exe]
      TCP    0.0.0.0:30001          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30002          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30003          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30004          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30005          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30006          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30007          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30020          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30021          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30039          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30080          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30081          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30082          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30083          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30084          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30085          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30086          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30087          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30088          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30089          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30090          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30091          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30092          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30093          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30094          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30095          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30096          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30097          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30098          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30099          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30101          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30102          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30103          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30104          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30105          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30106          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30107          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30108          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30109          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30110          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30111          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30112          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30113          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30114          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30115          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30116          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30117          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30118          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30119          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30120          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30121          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30139          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30180          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30181          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30182          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30183          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30184          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30185          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30186          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30187          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30188          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30189          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30190          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30191          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30192          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30193          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30194          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30195          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30196          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30197          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30198          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30199          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30201          0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:30239          0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:33306          0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       440
     [wininit.exe]
      TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       880
      eventlog
     [svchost.exe]
      TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       1000
      Schedule
     [svchost.exe]
      TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       508
     [lsass.exe]
      TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING       500
     [services.exe]
      TCP    0.0.0.0:49158          0.0.0.0:0              LISTENING       3048
      PolicyAgent
     [svchost.exe]
      TCP    127.0.0.1:8361         127.0.0.1:49364        ESTABLISHED     3080
     [sc_serv.exe]
      TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING       1444
     [FileZilla Server.exe]
      TCP    127.0.0.1:14147        127.0.0.1:49162        ESTABLISHED     1444
     [FileZilla Server.exe]
      TCP    127.0.0.1:49162        127.0.0.1:14147        ESTABLISHED     3156
     [FileZilla Server Interface.exe]
      TCP    127.0.0.1:49212        127.0.0.1:49213        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49213        127.0.0.1:49212        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49214        127.0.0.1:49215        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49215        127.0.0.1:49214        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49216        127.0.0.1:49217        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49217        127.0.0.1:49216        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49218        127.0.0.1:49219        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49219        127.0.0.1:49218        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49220        127.0.0.1:49221        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49221        127.0.0.1:49220        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49222        127.0.0.1:49223        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49223        127.0.0.1:49222        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49224        127.0.0.1:49225        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49225        127.0.0.1:49224        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49226        127.0.0.1:49227        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49227        127.0.0.1:49226        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49364        127.0.0.1:8361         ESTABLISHED     3100
     [Instore_Radioboss.exe]
      TCP    192.168.1.87:139       0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    192.168.1.87:3389      217.156.134.12:22971   ESTABLISHED     1104
      CryptSvc
     [svchost.exe]
      TCP    192.168.1.87:8360      81.148.248.221:1026    ESTABLISHED     3080
     [sc_serv.exe]
      TCP    192.168.1.87:25565     0.0.0.0:0              LISTENING       4288
     [java.exe]
      TCP    192.168.1.87:50644     37.139.0.151:8233      ESTABLISHED     4796
     [VirtualBox.exe]
      TCP    192.168.1.87:51019     81.27.96.46:21         TIME_WAIT       0
      TCP    192.168.1.87:53126     192.168.1.86:445       ESTABLISHED     4
     Can not obtain ownership information
      TCP    192.168.1.87:60462     192.168.1.86:445       CLOSE_WAIT      4
     Can not obtain ownership information
      TCP    192.168.1.87:65029     37.139.0.151:8231      ESTABLISHED     4796
     [VirtualBox.exe]
      TCP    192.168.56.1:139       0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    [::]:21                [::]:0                 LISTENING      
    1444
     [FileZilla Server.exe]
      TCP    [::]:25                [::]:0                 LISTENING      
    1692
     [MESMTPC.EXE]
      TCP    [::]:80                [::]:0                 LISTENING      
    4
     Can not obtain ownership information
      TCP    [::]:135               [::]:0                 LISTENING      
    752
      RpcSs
     [svchost.exe]
      TCP    [::]:445               [::]:0                 LISTENING      
    4
     Can not obtain ownership information
      TCP    [::]:3306              [::]:0                 LISTENING      
    1756
     [mysqld.exe]
      TCP    [::]:3389              [::]:0                 LISTENING      
    1104
      CryptSvc
     [svchost.exe]
      TCP    [::]:30239             [::]:0                 LISTENING      
    4796
     [VirtualBox.exe]
      TCP    [::]:49152             [::]:0                 LISTENING      
    440
     [wininit.exe]
      TCP    [::]:49153             [::]:0                 LISTENING      
    880
      eventlog
     [svchost.exe]
      TCP    [::]:49154             [::]:0                 LISTENING      
    1000
      Schedule
     [svchost.exe]
      TCP    [::]:49156             [::]:0                 LISTENING      
    508
     [lsass.exe]
      TCP    [::]:49157             [::]:0                 LISTENING      
    500
     [services.exe]
      TCP    [::]:49158             [::]:0                 LISTENING      
    3048
      PolicyAgent
     [svchost.exe]
      TCP    [::1]:14147            [::]:0                 LISTENING       1444
     [FileZilla Server.exe]
      UDP    0.0.0.0:123            *:*                                   
    964
      W32Time
     [svchost.exe]
      UDP    0.0.0.0:500            *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    0.0.0.0:3702           *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:3702           *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:4500           *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    0.0.0.0:5355           *:*                                   
    1104
      Dnscache
     [svchost.exe]
      UDP    0.0.0.0:53274          *:*                                   
    4780
     [VirtualBox.exe]
      UDP    0.0.0.0:53727          *:*                                   
    4788
     [VirtualBox.exe]
      UDP    0.0.0.0:54111          *:*                                   
    4828
     [VirtualBox.exe]
      UDP    0.0.0.0:54112          *:*                                   
    4828
     [VirtualBox.exe]
      UDP    0.0.0.0:54113          *:*                                   
    4780
     [VirtualBox.exe]
      UDP    0.0.0.0:55421          *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:58596          *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:59838          *:*                                   
    4812
     [VirtualBox.exe]
      UDP    0.0.0.0:62498          *:*                                   
    4796
     [VirtualBox.exe]
      UDP    127.0.0.1:1900         *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    127.0.0.1:55045        *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.1.87:137       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.1.87:138       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.1.87:1900      *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.1.87:55043     *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.56.1:137       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.56.1:138       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.56.1:1900      *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.56.1:55044     *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [::]:123               *:*                                   
    964
      W32Time
     [svchost.exe]
      UDP    [::]:500               *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    [::]:3702              *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::]:3702              *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::]:4500              *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    [::]:5355              *:*                                   
    1104
      Dnscache
     [svchost.exe]
      UDP    [::]:55422             *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::]:58597             *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::1]:1900             *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [::1]:55042            *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::59f:484a:827f:42ba%11]:1900  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::59f:484a:827f:42ba%11]:55040  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::11a6:2283:bc40:c0cb%16]:1900  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::11a6:2283:bc40:c0cb%16]:55041  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]

  • Types of batteries compatible with Magic Mouse

    Hi There,
    Recently I bought a magic mouse, and till now it has been amazing. But as all users, I too face serious battery drain issue with magic mouse, but I think its worth its usage .
    So I thought to switch to couple of rechargeable batteries for my magic mouse after reading some threads here. But now I have got a doubt. I read the magic mouse user guide and it says :
    +You can use alkaline, lithium, or rechargeable AA batteries in your mouse.+
    So My doubt is that whether I can use rechargeable Nickel Cadmium(Ni-Cd) batteries or not? Also what all kind of batteries are compatible with magic mouse?
    Message was edited by: zulficarr

    Hi zulficarr
    Welcome to Apple Support Communities
    If you have Nickel Cadmium(Ni-Cd) batteries they will work just fine, however if you shopping for rechargeable's the NiMH batteries are better and last longer.
    http://www.maxellcanada.com/battery/nimh/NiMHvsNiCd.htm
    Also note that the Apple Store sells a Battery Charger with 6 NiMH batteries.
    http://store.apple.com/us/product/MC500LL/A?mco=MTY3ODQ5OTY
    Dennis

  • New iMac user.  My mouse doesn't seem to work properly on websites.  I just want to be able to click and have it do whatever I've clicked on automatically, for example "print" or "open link".  Has anyone else had problems with their mouse?

    Has anyone else had problems getting used to their mouse and how the clicks work or don't work on the internet?  I click and it doesn't automatically do what I click on.  So frustrating!

    Hi ndearborn0273!
    This is most likely just a settings issue with your mouse that you are able to change through the System Preferences. I have an article for you that can help you set this back to default, and that article can be found right here:
    Mac Basics: Set your preferences
    http://support.apple.com/kb/ht2490
    Specifically, you will want to pay close attention to this section of that article:
    Customize your mouse
    The Mouse preferences pane looks different depending on what kind of mouse you use. These settings let you set the sensitivity of the mouse to control how fast the pointer moves across your screen when you move your mouse, and adjust for your double-click reflexes. Other controls may be available, depending on the type of mouse you're using.
    Open System Preferences.
    Choose View > Mouse, or simply click Mouse.
    To control how fast the pointer (cursor) moves across your screen when you move the mouse, click Point & Click and use the Tracking slider to adjust speed.
    If Double-Click Speed appears, you can use the Double-Click slider to adjust speed.
    If your mouse has a scroll wheel, you can use the Scrolling slider to adjust speed.
    To change gesture settings, click the More Gestures tab. You can enable and disable gestures for swipe and Mission Control.
    Judging by your post, I believe your secondary click setting is set to use the left side of the mouse. The default set up for a former Windows user to be most comfortable would be having the secondary click set to the right side of the mouse, as is shown in the picture I have inserted above. Note that these settings will be explained by the little video on the right hand side of this window as you hover over the description of the action on the left hand side.
    Thanks for using the Apple Support Communities!
    Cheers,
    Braden

  • Wired mouse still needed for emergencies?

    I bought my iMac with wired mouse and keyboard but later bought the bluetooth ones. Very nice. It appears I can do away with the wired keyboard, but there are circumstances when the BT Mighty Mouse does not work, such as when booted from a system disk (OS X install DVD). At those times I have to get out the old mouse and plug it in. I reckon the wireless mouse should work at all times, or forget about it.

    Hi Jeffrey Shaw-
    I actually have a wired keyboard in addition to a mouse.
    Just in case.
    Luck-
    -DaddyPaycheck

Maybe you are looking for