Innerspace Windowsnapper, Repeater, and a little extra sumptin sumptin

[moosejaw]

I ordered a G13 today to compliment my rev 1 G15. I may experiment with with the MWII software for the USB Xkeys and IS. Without the direct binding capability of IS, the Xkey USB is not very useful for me anymore. Should the ergonomics of the G13 agree with me, I may dump both Xkeys and only use the Logitech products for direct binding.

I'll wait for at least 3-4 weeks before I try to sell the Xkeys to give this issue time to shake out.

[Lax]

ISBoxer Toolkit has entered beta: http://www.lavishsoft.com/wiki/index.php/IS:ISBoxer
I'm looking for some people who'd like to try it out, it's intended to make multiboxing with Inner Space so easy to set up that your grandma could practically do it. Feel free to sign up for a free 7-day trial of Inner Space and mention ISBoxer Toolkit in the application. I'm hoping that I can get a few people who can tell me what they think, what wasn't obvious, what they need help with, and so on. If anyone was having trouble figuring out how to configure multiboxing with Inner Space, now is the perfect time to try again

[Draken]

Lax.. where do you want the bug reports sent to?

[Lax]

Lax.. where do you want the bug reports sent to?

Anywhere you can reach me -- the IRC channel you asked in this morning you could send me a private message there, you can send me a PM here on these forums (note: I don't always check forum PMs, out of all the options that'll get the slowest response), you can email me at lax@lavishsoft.com, or use the bug report form in the Support section at lavishsoft.com

[propagandalf]

How's ISBoxer coming along? I've been out of commission, rebuilding my system so I haven't had a chance to check it out. Should it be installed on top of our current scripts and interface files? Does it write to those files, or does it create it's own, etc? Does it import our current settings?

[Tanntyn]

ISBoxer is intended for the person who knows nothing about IS. Based on this, grab IS and all the usual scripts, install the scripts to their usual places (This will be done for you when the final release is ready) and unzip ISBoxer to where ever you want. Then run it and go to town. If you cann't figure something out, then that needs to be more noob proof. Send in a note about it.
That's what I did. I like it so far.

[zanthor]

ISBoxer is intended for the person who knows nothing about IS. Based on this, grab IS and all the usual scripts, install the scripts to their usual places (This will be done for you when the final release is ready) and unzip ISBoxer to where ever you want. Then run it and go to town. If you cann't figure something out, then that needs to be more noob proof. Send in a note about it.
That's what I did. I like it so far.

I'm working on a general guide to ISBoxer, it won't be highly detailed it will be more of a 10 steps to multiboxing with ISBoxer. The internal documentation is amazing, the text guides you through it all, but there's no bigger picture given to give you the basic tasks you need to setup:

• Key Broadcasting
• Round Robin
• Mouse Broadcasting
• WindowSnapper
• WoW Profiles (for saved settings/etc)

[Lax]

How's ISBoxer coming along? I've been out of commission, rebuilding my system so I haven't had a chance to check it out. Should it be installed on top of our current scripts and interface files? Does it write to those files, or does it create it's own, etc? Does it import our current settings?

Install and run from anywhere, it will detect the IS folder and if it can't detect it, it'll ask you for it. It will not overwrite any of your existing scripts and interface files. When you select Export to Inner Space from ISBoxer Toolkit, it will output separate XML configuration files, a script called isboxer.iss, and another script in init-uplink in order to add things to the Inner Space menu. It unfortunately can't import your current settings, since that would generally require interpretation of various scripts (e.g. wow.iss, multi.iss, etc). I will probably make it able to read existing XML configuration files for KeyMapper and Repeater soon though.

At the moment I'm building the portions for multiple PC configurations, so that it's not seen as exclusively for 1-PC setups.

Once we're at the full release feature set, I'm planning to have pictorial guides to setting things up and I'll probably take some cues from what Zanthor is writing up for that as well. Then it's a matter of building that additional information into the program.

As it stands, the current beta release of ISBoxer Toolkit takes care of 99% of my personal setup and should do the same for anyone else using 1 PC. The next release in development takes care of that last 1% among other things.

[propagandalf]

I see, thanks. I'll try it out in a different folder, as I pretty much have all my script and interface folders set up to my liking.

Another question... I upgraded to an i7 920 processor and I was reading this thread on setting up affinity on an i7. After reading the thread I'd like to try out two configurations. One, setting it up so all 5 sessions use all 8 cores. The second config I'd like to try is this scenario:

WoW 1 on cores 0 and 4
WoW 2 on cores 1 and 5
WoW 3 on cores 2 and 6
WoW 4 on cores 3 and 7
WoW 5 on cores 3 and 7

How do I set this up in multi.iss. My current script looks like this (taken from zanthor's multi.iss)... which I'm assuming is for a quad-core sytem (and is setting all five sessions to use all 4 cores?).

case 1

proc 1 on 2 on 3 on 4 on
break
case 2
proc 1 on 2 on 3 on 4 on
break
case 3
proc 1 on 2 on 3 on 4 on
break
case 4
proc 1 on 2 on 3 on 4 on
break
case 5
proc 1 on 2 on 3 on 4 on
break

Thanks for the help!

[zanthor]

WoW 1 on cores 0 and 4
WoW 2 on cores 1 and 5
WoW 3 on cores 2 and 6
WoW 4 on cores 3 and 7
WoW 5 on cores 3 and 7

I think:

proc 1 only 5 on

Etc... cores in IS are 1 based vs OS beign 0 based. You may need to go something like

proc 1 only 
proc 5 on

The two seperate lines the first turns all off but 1, and then turns 5 on as well.