Sorry, not trying to be stupid but do I need to run Setpoint as admin every time I log in to make it work properly with ISBoxer, or just once initially to get ISBoxer to recognize the mousebuttons as keystrokes?
Sorry, not trying to be stupid but do I need to run Setpoint as admin every time I log in to make it work properly with ISBoxer, or just once initially to get ISBoxer to recognize the mousebuttons as keystrokes?
"Tact is for those that lack the wit for sarcasm."
_________________________________________
Every time. It is my understanding that anytime you want a program to modify another program it must be run in admistrator mode.
Just to be clear, if you start up setpoint, ISboxer, and IS in admin mode you only need to do that after you start up the computer. If you put it to sleep, re-log on or what ever then you don't need to do that. I hope this is clear.
----------------------------------------------------------------
Shu'Halo
Warrior - Warlock - Druid - Priest - Mage
Adamus - Azzeddar - Elistriel - Jazeela - Zimrinauth
So start up the computer, open IS as admin, open ISBoxer as admin, then open Setpoint as admin and it should work fine?
"Tact is for those that lack the wit for sarcasm."
_________________________________________
Yes.
----------------------------------------------------------------
Shu'Halo
Warrior - Warlock - Druid - Priest - Mage
Adamus - Azzeddar - Elistriel - Jazeela - Zimrinauth
If you go Properties, Compatibility tab, check the option box for "run as administrator".
Do it once, and just double-clicking will run the program as an administrator from now on.
EverQuest I: Bard / Enchanter / Druid / Wizard / 2x Magician.
Diablo III: 4x Crusader & 4x Wizard.
My Guide to IS Boxer http://www.dual-boxing.com/showthread.php?t=26231 (somewhat dated).
Streaming in 1080p HD: www.twitch.tv/ualaa
Twitter: @Ualaa
Awesome everyone, I really appreciate all the help!
"Tact is for those that lack the wit for sarcasm."
_________________________________________
My setpoint quits working after some random amount of time.
I'm using IS & boxer, Windows 7 x64, and setpoint 4.8 for x64
It works for an hour sometimes and other times 5 minutes. I have to tab out and shut setpoint down and then re-start it and it works again for some random amount of time.
I've tried turning UAC off, and tried changing to older versions of setpoint - nothing seems to have helped.
Ideas?
Connect With Us