Serious mouse issues with GTK

my mouse and touchpad for my laptop have always worked without any sort of problem. i recently switched to openbox from gnome and it's been a wonderful experience so far. i tried cleaning out unnecessary gnome stuff and installed KDE to toy with it a little. needless to say shortly afterwards i ditched KDE and switched back to openbox, only to discover my mouse being screwed. i can move the cursor around and such but after a few seconds of running my ability to click and right-click is gone. i tried re-installing gnome completely hoping it might effect it and logged into a gnome session instead but the problem is persisting here as well. if i am using my mouse in a window, i cannot select anything on the panels with it whatsoever without repeatedly right clicking in the window close to the panel and then clicking the panel. and whenever i have the panel selected i can interact with it fine but cannot switch over to any windows. it's making me believe there's something going on with the mouse thinking it's "stuck" on the panel or window so clicking outside of it is rendered useless. i really don't know, i've tried searching online and such for any help on the topic but could not find anything and this is my final resort before going completely mad. any help would be greatly appreciated.
EDIT: i've tried toying with settings in gnome in regards to the mouse and stuff, basically just doing anything i possibly can and while using a window from the control panel for the mouse and clicking within it i started opening a ton of control panel items (appearance, etc.) leading me to believe it's definitely an issue of the mouse being stuck in a window or something.
Last edited by hustletrees (2010-07-01 04:11:28)

Your mouse is handled by xorg, so you need to make sure it's configured correctly. "mouse issues with GTK" simply doesn't make any sense.
My guess is that somewhere in the middle of changing WM/DE, you also did a system upgrade (a good thing) without reading Arch news (a bad thing), so you now have xorg 1.8 and you need to change your config accordingly.

Similar Messages

  • SERIOUS lag issues with Intel iMac

    Hello everyone,
    I'm pretty frustrated right now. I've been having this serious lag issue with my new iMac for the past few days. I think it may have started after I ran the last security update.
    What happens:
    When switching between apps, the system will hang for 1-3 seconds between doing anything. This includes typing, mouse requests, etc. It's VERY frustrating. I have activity monitor open currently, and I am seeing both Safari and SystemUIServer hogging up the CPU resources like CRAZY. I've even seen Safari recently give a CPU usage of 120%, right before I loaded this webpage. tis isn't just centralized to Safari too.... I have the following apps running:
    Adium 0.89.1
    FoireFox 1.5.0.8
    Safari
    Activity Monitor
    My Memory stats currently are:
    175MB Wired
    708MB Active
    618MB Inactive
    1.47GB Used
    There should be no reason I'm getting these lags with just two web browsers and a chat client open.
    Has anyone else expierenced the lags?? Any suggestions? I'm almost ready to reinstall OS X and not run the last security update. Thanks
    iMac 1.83 GHz Core Duo   Mac OS X (10.4.8)   1.5GB RAM, Extermal LaCie 160GB FW Porsche Drive, Griffin iMate, iPod Min 4GB, JBL Creature Speakers

    Hello Matthew
    Are you running any maintenance scripts on a regular basis?
    http://www.thexlab.com/faqs/maintscripts.html
    I would manually run this script from The X Lab, and my load times would improve greatly. The problem was, I would forget to run them untill I noticed web pages loading slow or iTunes and iPhoto taking for ever. It wasn't untill someone here in discussions suggested Anacron that I saw the light. WOW what a difference Anacron has been making in my overall system speed. My iMac has not been shutdown for 11days 5hrs 34mins (sleep or use only) and opening new App's, switching App's and web pages load as fast or faster than after a fresh start up. If your system is operating properly and you are having only what seems to be a slow or sluggish issue Anacron will make a difference.
    http://members.cox.net/18james/anacron-tiger.html
    Dennis
    17" iMac Intel Core Duo 1.5GB Ram   Mac OS X (10.4.8)   Maxtor 300GB FireWire 2G Nano

  • Serious resolution issues with After Effects CC (2014) on Windows 8.1 Pro on Dell Precision M3800 laptop??

    My new company installed Adobe Creative Cloud (There was some annoying Proxy issues at first, because of the seriously tight I.T policies) but we are having some serious resolution issues with After Effects CC 2014 (also have this resolution problem with Adobe Premiere, Media Encoder, Muse) on Windows 8.1 Pro on a Dell Precision M3800 laptop with icons and interface looking too small and hard to see, is there a fix, an update or a work around, can anyone help?
    Any help will be appreciated!
    k.regards
    Ramon

    Hi Todd is there a time-frame for this fix, there is a lot of pressure on me, because I convinced my company to get the Creative Cloud and quite a lot of the CC software is not compatible with the latest Windows 8.1 OS.
    Is there at least a work around, until this big fix comes along?
    k.regards
    Ramon

  • Wacom or Bluetooth Mouse issues with most recent Beta??

    Wacom or Bluetooth Mouse issues with most recent Beta??
    All I was wondering if anyone was having issues with Lightrooms beta and pointing devices… while I’m sure the Wacom Introus4 is dying in Lightroom I can’t verify that my Mouse is as well.
    I’m using the most recent Beta of Lightroom and Wacom Tablet Driver 615-3a… I’m sure the issue dosent reside with another program because the tablet only stops working in Lightroom. Basically I loose all tablet functionality until I reboot whin I attempt to access the Film Strip… I’ve repeated a few times and with each it dies…

    Unfortunately, although you are getting problems with your Wacom and Lr, the solution for the short term is to re-install an older driver for the tablet until Wacom come up with a new update to fix the prolem. This has been a long running problem for users when operating Lr with Wacom tablets.
    (I offer this solution not from personal experience, but from what other tablet users have reported in previous threads, and there have been several).

  • Serious Power Issues with T61

    All,
      The organization I work for has started to have some serious power issues with our T61 model Thinkpads. Additionally, the problem now seem to be carrying over into our T500 Thinkpads.
      About 4 months ago we started receiving consistant calls regarding users that can't power their laptops on. These are T61 and T500 laptops mounted to mobile carts in our various nursing units in numerous hospitals. These laptops sit stationary for 95% of the time and are almost always plugged into wall power. We quickly discovered that the only way to get the laptops to power on was to unplug them from all power sources and reseat the battery, after which they powered right on. We've had this problem in the past with users T61s that aren't on carts, but this is slightly different as the batteries on the cart mounted laptops are always 100% drained after we reseat them.
      I'm completely baffled by this issue. I've tried every variation of 3 different carts, -- one with external battery on cart, two without -- both 90 and 65 watt power supplies, and standard and 9 cell batteries that I can come up with and the problem continues to occur. Initially we had atributed the problem to ESD because this started during the low humidity months of winter, but it is now spring and the problem is still happening.
      Under normal circumstances I'd just replace the few ailing laptops and call them in under warranty, but this seems to be a general model issue as this is occuring across the board on 100+ laptops at this hospital alone. Any assistance to help identify the issue and/or how to resolve it would be appreciated.
    Thanks,
    David

    Slider5634,
    Do you have a critical situation open for this?  If so, while you are free to post here, working through the project office as a managed account should get you to the right level of support to address an issue that sounds pervasive, and may or may not be influenced by unknown environmental factors.
    If you don't have a situation open, then I would urdge you to contact your account rep.  If you need help, or unsure of this, please send me a PM with your contact information, and your hospital or corp account name so I can get you the right level of assistance.
    jgm1234,
    What model type T61's are you experiencing this issue with?  Can you provide some more information here about the situation?  Configuration, when this first started occuring,  environment (connected to lan, wired / wireless, stand alone, all in same physical location, or distributed at multiple locations, etc)
    Thanks!
    Mark
    ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
    Mark Hopkins
    Program Manager, Lenovo Social Media (Services)
    twitter @lenovoforums
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Serious locking issues with Main Stage 3

    Having serious locking issues with main stage 3.  I just did a music gig over the weekend with main stage 3, and the application locked up 8 times during my performance.  There were also several times where there was a delay between the time I struck a key on the midi controller and the time sound actually came out of the audio interface.  Has anyone else ran into this problem??
    10.
    I am running mountain lion 10.8.5, on a 2009 Macbook 2.53 GHz Intel Core 2 Duo. w 8 GB Ram.
    Anyone know how to fix this, if even possible?  

    Just read some reviews. There seems to be a lot of problems with the latest main stage update.  I didn't notice these latency problems until did the latest update..
    Apple please fix this quickly!!!

  • Thinkpad X1 Mouse Issues with USB 3.0 Dock and WIndows 8.1

    I have a new X1 (3444-CUU) that I recently upgraded to Windows 8.1. When I connected to the Thinkpad USB 3.0 Dock, there was an automatic updated of the firmware on the docking station.
    Everything seems to be working except issues with my Keyboard and Mouse.Periodically, the mouse will disappear of the keyboard will simply stop working. Most recently, it was as if the delete key was stuck causing it to delete all my email (actually a feature I liked but unfortunately, can't allow).
    Is there a known issue with wireless keyboard?

    I have a possibly similar issue that seems to be related to the keyboard dock. In my case this is with logitec unified receiver, but what I found may help you narrow the issue's root cause.
    I found that after a reboot, the dock's USB ports (bothh SS or USB 3.0) will not recognize logitech's unified receiver. Even though it is Windows reporting it, it seems to be related to the hardware. What I do to have minimally invasive 'functioning' system is to undock the Helix (use as tablet). This makes the genuine USB 2.0 port of the tablet accessible. I then plug the receiver into that port and wait until the mouse is recognized. Then remove the receiver, re-dock the tablet on the keyboard dock and plug the receiver into the dock's usb 3.0 port. Then everything works.
    That seems to somehow circumvent part of the refreshing of the USB connected devices and allows them to work correctly.
    I wonder if that addresses your issue. Of course I am opening another thread and ticket with that issue (will post a link after that)

  • I got a mouse issue with Photoshop.

    When trying to use the brush or any tool, the tool doesn't Hold   drag. Clicking and holding to use the brush only creates the initial mark (dot). I have a MacBook Air and Photoshop Elements 11. I searched on the internet and people say its got to do with a program named Synergy but I really do not know. Hope you can help me.

    Hi,
    We sincerely apologize for the problem customers are facing while using a trackpad with Photoshop Elements 11 & 12 on Mac OSX 10.10 (Yosemite).
    We have been actively working with Apple to resolve this problem as quickly as possible. We're hopeful this will get completely resolved in an upcoming update of Yosemite(MAC 10.10).
    In the meanwhile, you have two options to work around this problem:
    1. Option1: Use a mouse instead of the trackpad
    2. Option2: Install a plug-in which should workaround the problem
    Plug-in installation instructions:
    1. Close Photoshop Elements
    2. Download this zip file to a location you can easily find (e.g. your desktop)
    3. Unzip the file, WhiteWindowWorkaround.plugin, and move it to the Plug-In folder:
    • For Elements 12 – //Applications/Adobe Photoshop Elements 12/Support Files/Plug-Ins/
    • For Elements 11 - //Applications/Adobe Photoshop Elements 11/Support Files/Plug-Ins/
    You can verify the plug-in is installed by launching the Photoshop Elements Editor and choosing Help > System Info... Scroll to the bottom of the text in the dialog and look for the plug-in name "WhiteWindowWorkaround.plugin".
    Note: This plugin is a temporary workaround and should be used until this issue is addressed in Mac OSX 10.10 (Yosemite). Please remove this plugin once the issue is officially resolved by Apple.
    If you are using a stylus in conjunction with a trackpad, you might see issues with your trackpad. Workaround in this particular case is to use mouse instead of the trackpad.
    Hope this helps!
    Regards,
    vaishali

  • Ultraslim Plus keyboard and mouse issues with windows 8.1 (hesitation/jerkiness)

    I'm just wondering if anyone else is experiencing issues with their Ultrslim Plus keyboard and mouse after the update to windows 8.1? Mine seems very hesitant missing lots of key presses and the mouse pointers movement accross the screen  is jerky. I've uninstalled and reinstalled drivers but it still isn't working like it was yesterday. Batteries for both show as 100% and nothing else has changed.
    Solved!
    Go to Solution.

    My mistake. I'd installed version 1.5, the updated version 1.8 (specifically mentions windows 8.1 on download link) works perfectly.

  • Serious boot issues with Powerbook G3 (Wallstreet II, OS 9.2.2)

    Hello,
    I have major issues with a Powerbook Wallstreet II I got recently. When it's finally running, it works just as well as Wallstreet Powerbooks usually do, no errors, no crashing, smooth performance, everything fine.
    But booting it up is, to put it mildy, a bloody pain. First off, it does not power up, when it's only connected to batteries. I have two of them, both working fine for several hours when put in after bootup, but no matter if I place one or both of them in any bays, nothing happens when pressing or holding the power button (apart from screen flickering and speaker crackling). I'm always forced to connect the power adapter, which immediatly (without pressing the power button) causes the power LED to light and the cooling fan insanely spins up for a mere couple of split seconds until everything wents silent again.
    Having reached this point, I can disconnect the power supply (if at least one battery is in) and usually hear a nice "BONG" when pressing the power button once again. Thereafter, nothing happens for a oppressive 30 seconds, then, the screen finally lits and shows the Mac OS 9.2.x splash screen on monochrome background. Sadly, this is already the end of most of my first boot up tries, because at this point, I usually get told by a dialogbox that a bus error has just happened. The box also has a nice "Reboot" button, which I cannot click as the trackpad hangs as well.
    Pressing ShiftFn+CrtlPower works here in about one out of three time, so in most cases, I have to go through the same procedure. Pull out power sources, give a shot via PSU, have it iddling for 30 secs. In most cases, this second try lets me pass splash screen, loader, yes, it even lets me see the desktop, the taskbar, the HDD icon and... pouf. Success is so close but no, it has to suddenly drop into sleep mode and
    a short press on power proves the apprehension true, that it won't be easy to wake it up again. Hrmph. But I don't give that easily. So pulling everthing out for the second time, connect PSU for the third time and look there, it fully boots.
    Three tries to successfully boot is about average at first try series. Afterwards, it seems to be "warmed up" and things get easier. I made a log recently with 5 test series, made at very frequent intervals:
    Series 1:
    1. Bootup: Bus Failure (Hard reboot fails) (bays empty)
    2. Bootup: Sleep Mode (bays empty)
    3. Bootup: Sleep Mode (bays empty)
    4. Bootup: Sleep Mode (both batteries)
    5. Bootup: Bus Failure (Hard reboot successful)(both batteries)
    6. Bootup: Success (left battery, right bay empty)
    Series 2:
    1. Bootup: Success(left battery, right bay empty)
    Series 3:
    1. Bootup: Bus Failure (!!!) (left battery, right bay empty)
    2. Bootup: Success (bays empty)
    Series 4:
    1. Bootup Success (left bay empty, right battery)
    Series 5:
    1. Bootup Success (both batteries)
    Thanks in advance for any helpful suggestions.

    jpl,
    Thank you for continuative support.
    If you plan on buying a 256MB memory module, the Wallstreet requires
    a 256 specifically made for it (and the early iMac
    and Lombard). Modules 128MB and smaller can be
    generic if they meet the Wallstreet's specs.
    Thanks for this information.
    You might find it useful to disassemble the 'book to the PMU, carefully remove/reseat the PMU card, then test.
    Well, to be honest, I don't have the time to perform this very labour-intensive work. However, I pulled out the large PMU connector (the one that can be reached by lifting the keyboard) and reseated it, without any results. Shouldn't that suffice? Or is there another connection that could need maintenance?
    Regarding sleep: There is no display position sensor, only a simple magnet in the right display bezel approximately 4" from the bottom...you can stick a paperclip to it. When the display closes, it triggers a sleep switch located next to the delete key in the side rail.
    Ah, okay.
    According to Apple, if the powerbook will not run on battery, it could be the charge card or PMU board or power supply card or logic board. However, your 'book apparently runs on battery once started via power adapter.
    Actually, it does not allow me to power up, if I attach the adapter right after an unsuccessful try to operate from battery. Even if I remove the batteries (after adapter connection).
    It's like it is "crashed" before it's even running. Which means, I have to pull all power sources to be able to perform the resuscitating power up via adaptor.
    A normal power manager reset on the Wallstreet is this:
    1. If the computer is on, turn it off.
    2. Simultaneously press Shift-Fn (function)-Ctrl >(control)-Power.
    3. Wait 5 seconds.
    4. Press the Power button to restart the PowerBook >computer.
    A successful reset will briefly flash the sleep light plus >spin up the fan for a second. If a reset does not solve the >startup and sleep issues, then you will have to look >elsewhere.
    I can see the sleep LED and I do hear the fan, however, this didn't help in most cases. After perfoming this action (in a freeze situation), I usually only got rattling noises out of the speakers or screen flashes when trying to power up.
    Be sure the powerbook only freezes when closing the display to sleep it.
    Well, I noticed it sometimes also freezes when left idle directly after start up (and power save is activated). Later, it comes right back again.
    - Is the sleep light blinking before you open the display?
    Yes.
    - When the display is opened, does the sleep light continue to blink? (It should.)
    Yes.
    - When you press the power button, do you hear a 'buzz' or some similar noise? If you do, you may have another issue to explore.
    No. I usually only hear speaker noise when trying to power up from battery. But oddly enough, the lenght of the sleep light blinks changes when power button is hold down in "frozen sleep".
    I would also go to the System Folder > Preferences folder and drag the Energy Saver Preferences to the Trash, close all windows, then restart...a new preference file will be created on restart. You can reset the Energy Saver to your like, then test sleep.
    Done.
    -Does sleep/wake always work when NOT closing the display? Try this after resetting the power manager and trashing the pref file mentioned below.
    If I initiate sleep, yes. If it suspends automatically, well, usually. But not always (see above).

  • Serious performance issue with LV 7.1 Development Environment

    I'm posting this issue to the forums prior to submitting a bug report to ensure that the problems I'm having are reproducible. To reproduce this bug, you're going to have to be an advanced user with a large project (hundreds to thousands of VIs) as the performance problem is related to the number of VIs loaded.
    The issue is the increasingly poor performance of the LabVIEW 7.1 Development Environment as the number of VIs in memory increases. The actions affected include switching between front panel and diagram, saving a VI, copy and paste, clicking a menu, and the mysterious time spent (compiling? editing the runtime menu? changing the toolbar state?) between pressing the run button and when the code actually starts executing. Scrolling and, interestingly, copying via a control-drag are not affected. Running time of entirely on-diagram code does not seem to be affected.
    These problems are quite severe and significantly decrease my productivity as a programmer. Since they are development environment UI issues, it's been difficult for me to find a good example VI; the best I can do is the attached "LV Speed Test.vi". It doesn't test the issues that affect me most, but it seems to suffer from the same problem.
    This simple VI just shows and hides the menu bar 100 times in a tight for loop. When it is the only VI loaded, it executes in about 350 msec on my machine. (2.4 GHz P-IV/640 MB RAM/Win2k). However, when I load a single project-encompassing VI (let's call it the "giant") that references a total of about 900 user and VI-lib subVIs, the test routine takes almost a minute and half to run...about 240 times slower! I've tried this on my laptop with similar results.
    The problem appears to be related to the *number* of VIs loaded and not the memory utilization. For example, if I close the "giant", and create a new VI ("memhog") that does nothing but initialize a length 20,000,000 array of doubles and stores it in an uninitialized shift register, LabView's overall memory usage (as shown in the task manager) jumps enormously, but LV Speed Test executes in about 450 msec...only slightly slower than with a fresh copy of Labview.
    The problem seems to be related to excessive context switching. The Windows task manager shows over a thirteen hundred page faults occur when "LV Speed Test" is run with the "giant" in the background, versus zero or none when run by itself or when "memhog" has used up 160+MB of space.
    The problem only seems to affect the frontmost window. (Unfortunately, that's where we LV programmers spend all of our time!) If you start "LV Speed Test" and then put "giant" in the foreground "LV Speed Test" runs much faster. In fact, if you use the VI server to put the "giant" VI in the foreground programmatically at the start of "LV Speed Test", execution time drops back to 450 msec, and there are no page faults!
    These results show the issue is not related to video drivers or the Windows virtual memory system. My suspicion is that there is a faulty routine in LV 7.1 that is traversing the entire VI hierarchy every time certain events are thrown in the foreground window. It could be due to a problem with the Windows event tracking system, but this seems less likely.
    I have been programming LV for about 7 years and switched from LV 6.1 to 7.1 about four months ago. I know NI engineers have put thousands of hours developing and testing LV 7.1, but honestly I find myself wishing I had never upgraded from using LV 6.1. (To whomever thought "hide trailing zeros" should be the default for floating point controls...what were you thinking?!)
    I know each new version of LabView causes old-timers like me to grouse that things were better back in the days when we etched our block diagrams on stone tablets, etc., and honestly I'm not going to go back. I am committed to LabView 7.1. I just wish it were not so slow on my big projects!
    Attachments:
    LV_Speed_Test.vi ‏22 KB

    Hi,
    I can confirm this behavior. Setting the execution system to "user
    interface" helps a bit, but there is still a big difference.
    I get a feeling it has something to do with window messages, perhaps
    WM_PAINT or something, that is handled differently if a VI is not
    frontmost... But what do I know...
    Don't know if it should be called a bug, but it sure is something that could
    be optimized.
    Regards,
    Wiebe.
    "Rob Calhoun" wrote in message
    news:[email protected]...
    > I'm posting this issue to the forums prior to submitting a bug report
    > to ensure that the problems I'm having are reproducible. To reproduce
    > this bug, you're going to have to be an advanced user with a large
    > project (hundreds to thousands of VIs) as the performance problem is
    > related to the number of VIs loaded.
    >
    > The issue is the increasingly poor performance of the LabVIEW 7.1
    > Development Environment as the number of VIs in memory increases. The
    > actions affected include switching between front panel and diagram,
    > saving a VI, copy and paste, clicking a menu, and the mysterious time
    > spent (compiling? editing the runtime menu? changing the toolbar
    > state?) between pressing the run button and when the code actually
    > starts executing. Scrolling and, interestingly, copying via a
    > control-drag are not affected. Running time of entirely on-diagram
    > code does not seem to be affected.
    >
    > These problems are quite severe and significantly decrease my
    > productivity as a programmer. Since they are development environment
    > UI issues, it's been difficult for me to find a good example VI; the
    > best I can do is the attached "LV Speed Test.vi". It doesn't test the
    > issues that affect me most, but it seems to suffer from the same
    > problem.
    >
    > This simple VI just shows and hides the menu bar 100 times in a tight
    > for loop. When it is the only VI loaded, it executes in about 350 msec
    > on my machine. (2.4 GHz P-IV/640 MB RAM/Win2k). However, when I load a
    > single project-encompassing VI (let's call it the "giant") that
    > references a total of about 900 user and VI-lib subVIs, the test
    > routine takes almost a minute and half to run...about 240 times
    > slower! I've tried this on my laptop with similar results.
    >
    > The problem appears to be related to the *number* of VIs loaded and
    > not the memory utilization. For example, if I close the "giant", and
    > create a new VI ("memhog") that does nothing but initialize a length
    > 20,000,000 array of doubles and stores it in an uninitialized shift
    > register, LabView's overall memory usage (as shown in the task
    > manager) jumps enormously, but LV Speed Test executes in about 450
    > msec...only slightly slower than with a fresh copy of Labview.
    >
    > The problem seems to be related to excessive context switching. The
    > Windows task manager shows over a thirteen hundred page faults occur
    > when "LV Speed Test" is run with the "giant" in the background, versus
    > zero or none when run by itself or when "memhog" has used up 160+MB of
    > space.
    >
    > The problem only seems to affect the frontmost window. (Unfortunately,
    > that's where we LV programmers spend all of our time!) If you start
    > "LV Speed Test" and then put "giant" in the foreground "LV Speed Test"
    > runs much faster. In fact, if you use the VI server to put the "giant"
    > VI in the foreground programmatically at the start of "LV Speed Test",
    > execution time drops back to 450 msec, and there are no page faults!
    >
    > These results show the issue is not related to video drivers or the
    > Windows virtual memory system. My suspicion is that there is a faulty
    > routine in LV 7.1 that is traversing the entire VI hierarchy every
    > time certain events are thrown in the foreground window. It could be
    > due to a problem with the Windows event tracking system, but this
    > seems less likely.
    >
    > I have been programming LV for about 7 years and switched from LV 6.1
    > to 7.1 about four months ago. I know NI engineers have put thousands
    > of hours developing and testing LV 7.1, but honestly I find myself
    > wishing I had never upgraded from using LV 6.1. (To whomever thought
    > "hide trailing zeros" should be the default for floating point
    > controls...what were you thinking?!)
    >
    > I know each new version of LabView causes old-timers like me to grouse
    > that things were better back in the days when we etched our block
    > diagrams on stone tablets, etc., and honestly I'm not going to go
    > back. I am committed to LabView 7.1. I just wish it were not so slow
    > on my big projects!

  • Serious performance issues with no solution in sight

    I hate to be in such desperate need of help, but these forums have been extraordinarily helpful before, so I'm hoping someone will be able to help me with this series of problems.
    I honestly don't know how to describe the problem beyond that it seems like the computer is coming apart.
    The problem started about a week and a half, maybe two weeks, ago. I was having problems with Safari at first. Every time I used it, I would get the spinning ball, and it would take several minutes to open. If Safari was opened, the computer seemed to just lock up. No other applications could be opened, and no folders could be used. On top of that, whenever that spinning ball appeared, a series of clicking sounds could be heard coming from the upper left hand portion of the laptop (not the screen). The only way I could make it stop was to force quit (and even that was a luck of the draw issue).
    I took the computer in to be checked out, but their scans and tests showed the same results as mine: nothing is wrong. The problem has since spread beyond Safari, which I ended up erasing from my computer. That same rhythmic clicking happens whenever the spinning ball appears. I have tried to find some kind of pattern to the sound/spinning ball, but have thus far been unsuccessful.
    It has happened when using iTunes, saving with appleworks, having AOL instant messenger open, using Firefox, using quicktime. Whenever it happens, my system basically locks up and renders all applications useless. Force quitting is the only way I can get things going again, and even then it can take several minutes for me to even be able to force quit.
    Also, software updates quit before I can download them.
    I apologize for the long post, but I want to try and provide as much information as possible.
    To me this sounds like a failing hard drive, and that is what the tech thought, but the tests just show nothing is wrong, and I cannot comprehend why.
    My many thanks in advance for any help you can provide.

    Hi Samuel,
    I will agree that louder than normal clicking is a sign of something wrong with the hard drive. But you might just be hearing the hard drive working normally, it just might be doing it a lot more.
    If you haven't tried a permissions repair, try one. It's worth a try, and I have known it to improve the performance of my Macs to some extent.
    Also, if you have access to it, Try DiskWarrior. DiskWarrior is a program that will take your hard drive and rebuild the directory for it, clearing up errors and improving overall performance.
    If you've got the means to do this, try reformatting your system. It's a lot of work, I'll admit, but perhaps something got corrupted and it could be messing up your performance.
    Another thing you can try is to boot OS X from some sort of external hard drive (if you happen to have a friend who happens to own an external hard drive with OS X on it... wait, am I the only one??? darn.) and see if the problem exists when running off the other drive. If you don't happen to have such a hard drive (I mean, everyone's got a spare external hard drive with OS X installed on it, don't they?) you can simply boot a friend's Mac in FireWire target disk mode (boot the computer while holding T key), connect the 2 computers, and boot your system from the friend's hard drive (by holding the option key at startup). Of course, if none of your friends own Macs, you need to find better friends!
    Basically, though, if your computer successfully boots from one of these other systems and doesn't exhibit these symptoms, then it's something with your hard drive. Try first to reformat (or at least re-install OS X), and if that doesn't work, you'll have to do a repair.
    If you have to resort to calling tech support, I'll bet you $10,000 that they're going to ask you to reset the PMU and/or the PRAM on your system. Your computer could have dirt on it, and they'd have you reset the PRAM and the PMU.

  • IMac/Magic Mouse issue with multiple iMacs.

    I bought two new imacs last month with wireless Magic Mice.  The mice one both of them keep having communication issues.  I returned them to the genius bar and they replaced them.  I'm still having the issue.  I keep having to reset the SMC for them to work, but they only work temporarily.  I've also tried zapping the PRAMs  Any suggestions?

    Do a search of this forum, Just look down this page for two or three other posts with the same theme. Many folks report the issue. Many folks report different ways of solving it for themselves.
    I have had the MM for three weeks now without one issue. I am even experimenting with BetterTouchTool for added utility of my MM.
    Dah•veed
    PS - The Provost of St Mary's Cathedral on Great Western Road is an online friend of mine!

  • Wireless mouse issues with technical preview

    I installed the technical preview with no problem on my laptop running windows 7 - except now the wireless mouse (Microsoft 4000) does not work and is not found when I try to trouble shoot. Any help is greatly appreciated.

    Hi Michael,
    Regarding current information, I recommend to check the setupapi.dev.log under %windir%\inf, locate the device (wireless mouse) and find the line under this device name as below:
    dvi:             Rank         - 0x00000000
    Then, corresponds the score in this link:
    Identifier Score
    http://msdn.microsoft.com/en-us/library/windows/hardware/ff546297(v=vs.85).aspx
    The value 0x00003000 is the best identifier score and the value 0x00003FFF is the worst identifier score.
    The score near 0x00003FFF means that the driver and device may not compatible with current system.
    Since Windows 10 tech preview is the newest released version and still in test, we may need to wait for the menufacturer’s driver update to compatible with Windows 10.
    Thanks for your understanding.
    Kate Li
    TechNet Community Support

  • Mighthy Mouse Issues with security update.

    I just installed security update 2009-006 on my MAC BOOK PRO about two days ago and my wireless mighty mouse stoped working, I know the mouse is fine because I paired it with two other MAC laptops that dont have that update installed yet, I have not been able to fix this, I'm trying to uninstall the update to see if that will do the trick but don't know where to uninstall.
    Please help.
    Thanks

    Try posting over in the Bluetooth Keyboard/Mouse area - http://discussions.apple.com/forum.jspa?forumID=1002

Maybe you are looking for