![]() In many ways I'm actually grateful that this problem occurred as it's given me the reason I needed to finally dump Setpoint! I recommend you remove Setpoint and try using the native Win 7 driver for the keyboard - I appear to have all the orange 'FN' functions available to me without Setpoint! And now I've decided I don't need it for the mouse either. I had been using Setpoint as a 'necessary evil' despite my view that Logitech driver software is astonishingly intrusive and generally seems to attempt taking over your PC! I never used the Illuminated Keyboard driver for example as I discovered while Beta testing Win 7 that it interferes with Win 7 Aero settings (I also run Win 7 Pro 圆4). On your 'off-topic' point - I completely agree with you. So I dare say I'll find out over the next day of two if the start-up problems all stem from this one piece of software. I've now removed Setpoint completely and of course the log is empty apart from those below. I was using a third party add-on to Setpoint called 'uberoptions' which extends Setpoint's functionality, but after removing that first I still saw the same warnings appear in the HIPS log. I'm the 'reverse' to you, in that I'm using Setpoint for the MX Revolution mouse and not the illuminated keyboard, so it may be something to do with the 'intrusive' mouse driver / settings that NOD32 doesn't like.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |