you could try moudrv instead or something like that

use drivers if you want but never ever use setpoint. it's evil incarnated, last time i had it installed only a format could fix my pc and i know lots of other people who had the same experience.

What are the issues with setpoint? Im using logitech drivers since mx300 was released. I only remember same dpi feeling diffrent on each profile (G3) but thats it. (setpoint 3.x)
For my G9x im using setpoint 5.2 but its not in the autostart and i only use 1 dpi setting on the profiles. (using the dpi buttons for browser navigation)

edit: but yea i think moudrv is the better solution since its lower level, so it really doesnt matter how the game gets its mouse input.

I can't say I've ever experienced real trouble with setpoint but I've used windows xp and windows 2000 only in the past years and xp currently. It is rather bloated alright - i'll uninstall it now..

Thanks a lot for the input guys, I didn't realize moudrv existed.

Last time I checked years ago for driver side accel someone had modified either old setpoint ie 9.78 or perhaps razer drivers for use with different mouse manufacturers.

In case anyone is interested from just messing around with low medium and high in logitech setpoint I would say the values correspond to cl_mouseaccel along the lines of low = accel 1-1.5 medium is about 1.5-2 and high sens around accel 2.5. Much too high and troublesome.