Mice and Pointing Devices

[jumblies]

I like my MX Revolution , and I like sleep mode.  I'm not terribly fond of vista, but I'm not going to change my OS over a support issue.  This problem plagued me so I eventually got an MX 1100 which didn't forget and actually had a configurable middle click. 

(If you're reading this logitech, why haven't you fixed this in setpoint to allow that nice "search" button to do middle click?  You must not care about product improvement since Uberoptions fixed it while you ignored it.)

To fix this problem:

Open Task Scheduler and event Viewer:

#Find an event that can be used as a trigger on wake from sleep.

Event Viewer:

Open Windows Logs

Look in System

Find a log entry that is issued when your computer wakes from sleep. 

for me:  Power-Troubleshooter

(The system has resumed from sleep.  Sleep Time: 2/25/2011 3:36:45 AM  Wake Time: 2/25/2011 11:17:12 AM
Wake Source: Device -USB Root Hub)

#Killing Setpoint

Create a text file called setpointkill.bat with these contents:

TASKKILL /F /IM SetPoint.exe
Exit

#Save that somewhere you'll remember b/c the new task you'll create will be pointed to this. 

#first you need to kill setpoint on wake, then restart.

Go to Task Scheduler and create a task that uses an event triggered by the log entry you found above. 

go to actions and click "New", Start a program, in the Program/Script box put the location of your setpointkill.bat file.

#Restarting Setpoint, but minimized/in the system tray.

go to actions and click "New", Start a program, in the Program/Script box put C:\Program Files\Logitech\SetPoint\SetPoint.exe /MIN

Put it to sleep and wake it up.  See if it works. 

If you choose to import my XML file below, make sure you change the locations of the files you created.

XML for task scheduler below:

<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
  <RegistrationInfo>
    <Date>2011-02-24T22:07:32.1148</Date>
    <Author>jumblies</Author>
  </RegistrationInfo>
  <Triggers>
    <SessionStateChangeTrigger>
      <Enabled>true</Enabled>
      <StateChange>SessionUnlock</StateChange>
    </SessionStateChangeTrigger>
    <EventTrigger>
      <Enabled>true</Enabled>
      <Subscription>&lt;QueryList&gt;&lt;Query Id="0" Path="System"&gt;&lt;Select Path="System"&gt;*[System[Provider[@Name='Microsoft-Windows-Power-Troubleshooter'] and EventID=1]]&lt;/Select&gt;&lt;/Query&gt;&lt;/QueryList&gt;</Subscription>
    </EventTrigger>
  </Triggers>
  <Principals>
    <Principal id="Author">
      <UserId>jumblies</UserId>
      <LogonType>InteractiveToken</LogonType>
      <RunLevel>LeastPrivilege</RunLevel>
    </Principal>
  </Principals>
  <Settings>
    <IdleSettings>
      <Duration>PT10M</Duration>
      <WaitTimeout>PT1H</WaitTimeout>
      <StopOnIdleEnd>true</StopOnIdleEnd>
      <RestartOnIdle>false</RestartOnIdle>
    </IdleSettings>
    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
    <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
    <AllowHardTerminate>true</AllowHardTerminate>
    <StartWhenAvailable>false</StartWhenAvailable>
    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
    <AllowStartOnDemand>true</AllowStartOnDemand>
    <Enabled>true</Enabled>
    <Hidden>false</Hidden>
    <RunOnlyIfIdle>false</RunOnlyIfIdle>
    <WakeToRun>false</WakeToRun>
    <ExecutionTimeLimit>P3D</ExecutionTimeLimit>
    <Priority>7</Priority>
  </Settings>
  <Actions Context="Author">
    <Exec>
      <Command>E:\setpointkill.bat</Command>
    </Exec>
    <Exec>
      <Command>"C:\Program Files\Logitech\SetPoint\SetPoint.exe"</Command>
      <Arguments>/MIN</Arguments>
    </Exec>
  </Actions>
</Task>

[stormseye]

I was also experiencing this same problem with my Marathon Mouse (M705) which I really love now that I've configured it the way I want.

I implemented the above solution suggested by jumblies.  It works and thank you, jumblies.

One slightly irritating side effect of using TASKKILL is that a small black window appears momentarily as TASKKILL runs.  The solution also leaves SetPoint minimized to the TaskBar and I would rather keep the TaskBar uncluttered.

I therefore tried a slightly different solution broadly based upon the original idea from jumblies.

This solution uses an AutoHotKeys script.  AutoHotKey info and free download is here:

http://www.autohotkey.com/

This script uses native AutoHotKey functionality.  (Note that I use SetPoint /launchGaming rather than /MIN; this sidesteps its appearance in the TaskBar.)  [Revised Apr 29/11.  This version seems to work more reliably.  Uses WaitClose instead of Close.]

;------------------------------------------------------
;  Closes the Logitech SetPoint process and then restarts it.
;  Intended to ensure that SetPoint works properly (eg, after Sleep).
;------------------------------------------------------
;------------------------------------------------------
#SingleInstance force
#NoEnv
;------------------------------------------------------
;------------------------------------------------------
; Global variables
;------------------------------------------------------
setpoint_name := "SetPoint.exe"
setpoint_program_path := "C:\Program Files\Logitech\SetPointP\SetPoint.exe"
setpoint_startup_parameters := /launchGaming
;------------------------------------------------------
;------------------------------------------------------
Process WaitClose, %setpoint_name%, 1
Run %setpoint_program_path% %setpoint_startup_parameters%
;------------------------------------------------------
ExitApp

;------------------------------------------------------

I created an .ahk file for that script and then compiled it into an .exe file.

I then created a task in Task Scheduler much like that which jumblies had done.  In the Actions, though, there is only 1 entry and it points to the .exe file I compiled withAutoHotKey.

That seems to work fine.  It may be possilbe to improve on the script.  So far, no problems though.

BTW, AutoHotKey is a very handy tool for customizing mouse and keyboard activities.  It's also good for creating Windows scripts in general.

Many more thanks to jumblies.

[Quatrix]

My MX 518 just started having a similar problem in Windows 7 a few days ago, but when waking the monitor, not the PC.  It happens maybe 20% of the time.  If I go into SetPoint and click "OK", the speed and acceleration return to normal.  I don't recall changing any hardware of software when it started happening.  Weird.

[jumblies]

I've been away from this thread for a while.  I like the Autohotkey solution a lot.  My solution mostly behaves, but sometimes gets triggered multiple times, leading to failure.  I'll try your script out tomorrow.  

Also, I've found that a few second delay in one of the scripts seems to help things along.  

I don't really understand the reason for all these weird **bleep** errors.  I'm going to presume it's a fault in setpoint.  

Quatrix:  Did you update setpoint recently?

[stormseye]

Incidently, just something I discovered which might help someone (Logitech??) figure out why this whole phenomenon happens at all.

The AutoHotKey script I described above works well for me.  Even so, I found that very occasionally the scroll wheel would temporarily slow way down.  I tracked it down to the following set of circumstances, though I don't know why it happens:

---------------------------------------------------

I use Firefox as my web browser.  I also use Mozilla Thunderbird for my email client, and within Thunderbird, I use the Lightning add-on as my calendar and reminder app.  All free, richly featured and convenient.

I've noticed that if I am browsing the web with Firefox when Lightning raises a calendar reminder alarm, then the mouse scroll wheel slows down bigtime in Firefox and elsewhere.  When I acknowledge the Lightning reminder and its reminder window closes, then the scroll wheel returns to normal quick scrolling in Firefox and elsewhere.

(This phenomenon does not happen with Thunderbird itself or with Lightning within Thunderbird.  It only happens when Lightning opens a small window for the reminder alarm.)

---------------------------------------------------

Obviously, there may be any number of other programs which also interfere with the mouse in a manner similar what I described above.

So far, with my AutoHotKey script working fine, it is not a big enough issue for me to pursue.  I only write about it here to aid others (Logitech??) in trying to solve the root of the problem.

[Quatrix]

No, haven't updated SetPoint in a while.  I did upgrade my core hardware (motherboard, CPU, memory, GPU) two weeks ago, and obviously there were a lot of driver changes related to that, but not around the time this started happening.

Are you guys really having problems with the whole PC going to sleep, or is it just the monitor shutting off like me?  And does it happen every time or just sometimes?

[stormseye]

Quatrix, I don't recall having these problems when the monitor is put into and out of sleep.  That may be because the monitor rarely goes through that cycle.  I've set up my power options so that the monitor does not sleep unless there is 30 minutes with no PC activity.

Sounds like you made some major, major h/w changes.  I'm actually surprised that Windows worked after that without needing a complete re-install.  I would suspect that the problem you are seeing might be a side-effect of those changes, perhaps to do with the GPU.  I'm not really qualified to get too deeply into this, but do you have the latest drivers for the new GPU?

Good luck.  Sorry I can't help any more than that.

[jumblies]

Where is your transmitter plugged in?  Some monitors have USB hubs and if the power shuts off of the hub when the monitor goes to sleep, that could produce your symptoms.  Is it plugged into the CPU box or a hub?

[Quatrix]

I don't want to get into it, but changing core hardware rarely requires reinstalling.  I was able to boot into Windows 7, XP, and Ubuntu without much trouble.  They all detected the new hardware and installed the right drivers, and everything runs great.  I hadn't changed anything in at least a week before the mouse started acting funny, so I doubt it's related.

Thanks anyway.

And it's a wired mouse plugged directly into the back of the case.

[Quatrix]

Okay, it's not only when the monitor wakes up.  It seems to happen randomly even when I'm actively using the PC.  It was fine for a couple of weeks and then happened two or three times the last two days.