Mice - Software

[Ash123]

Hi All,

I keep losing my custom mouse settings after resuming from sleep. Reloading Setpoint fixes the problem, but it is a pain!

Using;

Setpoint : 4.60.122

Vista 32

Mouse: MX Revolution

Cheers,

Ash

[CJChew]

Hi,

Please try performing a clean install of SetPoint.

[QuietKungFu]

I am having the same problem with the same setup. I use Setpoint 4.60, and whenever my computer comes out of sleep mode, the keyboard commands I have bound to a few of the buttons are reset. I uninstalled Setpoint, and tried 4.60 and 4.40 again, and had the same problem. Any chance of getting a fix for this? Thanks,
-mpn

[CJChew]

Hi,

If clean isntalling SetPoint doesn't help, please try changing the property of the 'uers.xml' file to 'Read Only'. This will prevent your settings from being reset.

Note: You might need to enable hidden/system file viewing for th is file to be visible.

[stevebiko]

I'm having the same problem, a re-install of the latest SetPoint software does not fix this problem.

[QuietKungFu]

Hi I thought I had fixed the problem, but it still continues even after a reinstall, and changing users.xml file to read only.  In Vista, where is the file supposed to be located?  Maybe I didn't change the properties on the correct one?  Any help would be appreciated.

[stevebiko]

Hah, love how the answer for everything is "Do a clean install". Hah great tech support.

I fixed it myself with a bat file that I execute on Logon (which runs when you wake from sleep. Found this script in another thread in this forum.

echo "Killing Task"
ping -n 10 127.0.0.1>nul
TASKKILL /F /IM SetPoint.exe
echo "Task Killed"
echo "Starting Task"
ping -n 5 127.0.0.1>nul
START SetPoint.exe

The Pings put in 10 and 5 second pauses, not sure if they are needed but just incase the script runs too quickly.

[CJChew]

Hi,

Thanks for providing your solution

[QuietKungFu]

That little script works pretty good and seems to have solved my problem.  It means I usually end up with a bunch of duplicate setpoint icons on the taskbar, but they go away with a mouse wave over them.  I currently use a program called Hibernate Trigger to launch this script after Windows Vista resumes from Sleep mode.  Anyone have any ideas on how to lauch the script minimized, or a slicker way of running the script?  Thanks.

[erevo]

Hi All,

same problem here under Vista X64 with G5 and Logitech Illuminated and latest Setpoint, also tried new Setpoint in Beta.

By the way, also the custom settings of the keyboard are gone after a resume from sleep.

So my question is: When will this bug fixed?

Asked already german logitech support: no answer except, that it may be my motherboard which is from asus.... ok i'm the only one in the world who is using a market leader... but guess what: No problems with other drivers or other software... ahhh and they closed my call because i didn't complain again within 168 hours.

In the meentime and to Logitech Support: "No!!!!!!!!!!!!! this is not an acceptable solution for this bug!!!!!!!!!!!!!!!!!!!!!!!" a second workarround for vista:

Step 1

create a batchmacro called restartsetpoint.cmd with the following contents:

taskkill /IM SetPoint.exe /T /F
taskkill /IM SetPoint32.exe /T /F
taskkill /IM KHALMNPR.exe /T /F
start /D "C:\Program Files\Logitech\SetPoint" SetPoint.exe

Step 2 (sorry have german version so you have to look how it is really called in english)

Launch the taskplanning module from vista

Right click on the folder/clock symbol and select  New Folder

Name the Folder what ever you like may be "mytasks"

Right click on the new folder "mytasks" and select"create new task"

Name it "restartsetpoint"

on the top select trigger and below "new"

In the new window select task starts with an event

Protokoll: System

Quelle (next dropdown): Power-Troubleshooter

next drop down Event-id typein 1

verify, that on the bottom left side activated is selected andclick ok

Select on the top Action

the new

select start program

typein the whole path including the batchmacro eg:  D:\system\VistaMacros\restartsetpoint.cmd

click ok

 and save the task with ok

So every time you resume from sleep the batchmacro is executed. you will see for 2 seks or so a dos windows which is closing automatically.

Well, i hope, that logitech is fixing their drivers so that we didn't need any workarrounds anymore...

Batchmacros for getting the drivers to work

autohotkey for missing functionality

what have we to do next if we wish to use logitech hardware?