Need some IS help

[Xar]

Lax, I just downloaded the window snapper from the wiki page and looking in the zip the dates are 11/18/2008 on autolayout.iss, 01/17/2009 on pipsqueak.iss and 01/18/2009 on windowsnapper.iss. Looking in my IS Scripts folder autolayout is the same, pipsqueak.iss is 05/31/2009 and windowsnapper.iss is 04/20/2009.

Also, I like to be as close to hardware style of boxing as possible and don't use ISBoxer macro system at all and the add-on is disabled in every wow. Partially because I already have Bind Pad and lots of regular standard WoW macros and if I want to play any single toon by themselves I have everything I need with just loading WoW.

I only recently started playing with keymaps because I haven't found an easy way to bind non-shared keybinds to a do-nothing button. It used to be very easy when using Bongos and then Macaroon to bind tons of non used keys to a single unused spot but as Blizzard has updated the addon system Bongos went away then I've had problems with Macaroon (since vehicles and the last couple patches).

Right now my ideal setup would be to use Keyclone for keybroadcasting and IS for window management and swapping windows but I can't get the two working together.

[Lax]

Lax, I just downloaded the window snapper from the wiki page and looking in the zip the dates are 11/18/2008 on autolayout.iss, 01/17/2009 on pipsqueak.iss and 01/18/2009 on windowsnapper.iss. Looking in my IS Scripts folder autolayout is the same, pipsqueak.iss is 05/31/2009 and windowsnapper.iss is 04/20/2009.

Should I take that as a "no, I did not install an older WindowSnapper"?

Also, I like to be as close to hardware style of boxing as possible and don't use ISBoxer macro system at all and the add-on is disabled in every wow. Partially because I already have Bind Pad and lots of regular standard WoW macros and if I want to play any single toon by themselves I have everything I need with just loading WoW.

Funny enough, that's one major reason why I do use ISBoxer for macros. ISBoxer does not change WoW config at all when not playing through ISBoxer -- it is designed to be as unintrusive as possible and does not require changing your action bar buttons. I'm not sure how that makes you "close to hardware" though (and IMO there is no reason for that to be a goal if you're software boxing -- you're as equally unlikely to get banned as everyone else on the forums... but... up to you and what you are comfortable with, obviously).

Right now my ideal setup would be to use Keyclone for keybroadcasting and IS for window management and swapping windows but I can't get the two working together.

1. If you're using Vista or Win 7, you will need to run Keyclone as Administrator because IS is running as Adminsitrator and this makes your game run as Administrator
2. Add the windows manually to kc

5) No key "pause" built in like keyclone makes it harder up front to configure and I'm curious on the system impact of frequently loading and unloading keymaps via hotkey, could that be contributing to the freezeups and other problems? I get whispers all the time and chat in guild, etc.

I see this one didn't get answered. Loading and unloading keymaps via hotkey is just adjusting configuration in memory, and doesn't do any disk access. It only affects anything at the instant you press the key.

[Xar]

Hi Lax,

Yes that's correct to my knowledge I did not download and install an older WindowSnapper. I did not use Zanthor's package though I did have him refer me so he would get credit and I downloaded all from the Lavish site.

The reason for wanting to be like I'm hardware boxing is because that is my goal in the end...but I'm talking maybe 8 months to a year from now. I'm keeping an eye on the new ION based mini computers as a way to cheaply do hardware boxing. I want to see full frame rates on all 5 windows. I thought I'd be hardware boxing by now but things in RL just keep coming up. It's also a partial interest in seeing how to do multiboxing the original way.

I have tons of keybinds using all kinds of modified keystrokes to different bind pad macros already since I just started using ISBoxer and that's partly why I'm not using the IS macro system. If I were just starting out with multiboxing it would be different.

Thanks for the tip on running kc as admin, I was able to use IS for windows and swap only (still have border around main window and they stack when launched) but I did all my keys through KC and it worked out great.