PIP hotkey/session name issues. Using ISBoxer [FIXED]

[moosejaw]

I used Isboxer with EQ2 and it worked well. I previously used manual scripts with windowsnapper etc. when playing Wow.

The issue. I can set my session pip hotkey in Isboxer, export then launch the group but the pip hotkey will not work. It is related, I think, to the session naming. The sessions are being named IS2$ instead of IS$. I can press the hotkey and I see a syntax error for the 'focus' command in the console. Scrolling up the console I see the session name accepted as IS20, IS21 etc. This is different naming from what I remember it doing when I ran EQ2.

What is displayed on the task bar mouse over is- IS20(G1) charname-setname and so on. I tried different hotkey configs with the same results.

Could this be a video issue not related to IS and it is carrying over a wonky name?

I have wiped my entire IS install by using the uninstall feature and retrieved ISboxer fresh from the wiki. I removed Ati catalyst software and installed an updated driver only.

Repeater, keymaps and windowsnapper work well with the above exception.

Windows7, Ati 4870. Holler if you need more info.

Edit: Using the global hotkeys ctrl-alt-z and x works and spews "switching to session is2$" to the console.

[zanthor]

The name convention appears to be:

IS$ (Hotkey) CHARACTER - CHARSET

Could you post a pastebin.com link to your setup here? Or attach the XML?

[Lax]

It's unclear from your post what game you're playing now. I see you mentioned playing WoW and EQ2, but didn't specify whether it is one of these two games, or something different, that you're having the problem with. If the session numbering is is20 or higher, the problem is that IS thinks whatever you're playing is a launcher. It makes this guess based on comparing the process executable name with names of known launchers. In order to solve this issue, I will need to know what game you're playing and, if possible, what the name of the client executable is (e.g. for WoW it's wow.exe, for EQ1 it's eqgame.exe, and so on)

[moosejaw]

Sorry about the delay, working night shift this week. Additionally I haven't played in a while but my only isboxer teams were eq2 teams a couple months ago.

Playing Wow currently. Using the default profile generated by IS for all characters. Default profile is pointing at wow.exe and I only have one wow folder setup. I turned UAC off for testing and made IS, ISboxer and wow run as admin. The wow folder is a stand alone folder that is not in the program files directory.

All the IS files are untouched with no pre startup or post startup scripts by me. I regenerated the ISboxer configuration from scratch.

[moosejaw]

While trying to figure out what the heck I screwed up on the current machine, I thought I would test it out on my HTPC. This is my old boxing machine with a quad core. When I get home from work in the morning I will set up IS, ISboxer and WOW to see if it isn't just the user (me) screwing this up.

[moosejaw]

I got it fixed but it is rather strange. I made two changes this morning. I turned off the windows gagdets through add/remove programs, then I renamed my Wow folder (it had a naming convention from when I used multiple folders). I then removed Wow from the IS menu and added it back in.

When I reloaded the sessions naming was back to normal i.e. IS1,IS2 etc. So I reinstated the windows gadgets and loaded a few on the desktop and IS still worked fine. So it must have been the folder name. I had restored the folder from my Windows Home Server backup when I loaded the Windows7 RC, if that has any bearing on things.