Printable View
I have been using the ISBoxer suite for many months with great success until today. This morning none of my character sets will launch. None of my default profiles will launch. There are no errors. Is anyone else seeing this behavior? Does anyone know of a way turn on verbose logging or debugging for Innerspace or ISBoxer?
Scrap if you have time visit the isboxer chat room and see if lax is there, I know he had been helpin a couple others with a problem similar last night :) I had some issues but I ended up closing inner space and reopening it and it had patched and all was well.
One thing I did note when my wow's tried to patch last night it caused issues loading them with innerspace so I had to open each of my 6 wow folders and patch the game THEN re open with is boxer
Hope you get it working ! :)
Most of the times my teams load, no issues, but sometimes one client will load then stop loading the others. You can close the hung up client out, or, if you can, reload the team with the one client open. Most of the time I just close everything out and try again. I can't tell you whether this is a machine problem or a software problem since some people seem to have this issue and some don't.
When I upgraded Norton the other day, it didn't play nice with ISB. It quarantined ISB after an initial scan. It didn't like WoW either, but that's a common and well known issue. I know you said you've been using Innerspace for months with no problems, did you change security software maybe? Any automatic updates?
This particular issue is caused by the EAX support for ASUS Xonar cards, scrapdogg is the 3rd person I've seen with this problem (confirmed in the ISBoxer chat room).
For anyone else, if you get this problem, until I get this fixed you can check the Task Manager process list for HsMgr.exe and HsMgr64.exe, kill them both and IS will launch sessions properly.
I am working on getting this fixed asap, along with a couple other rare issues that cropped up
Jebus, how did you figure out it's a specific card?
That was some sage advice. Went to the chat room and Lax took care of me. The fix was
open up task manager, go to the processes list, and kill HsMgr.exe and HsMgr64.exe
Apparently I have a xonar sound card. I have an asus p6 deluxe mobo and the first thing Lax asked was if I had an asus xonar soundcard. I answered no because I have some xfi soundblaster card, he had me launch the innerspace console and type in diag. This gives some output and in that we found i had the xonar. It took me longer to write this post then it did to get fixed thanks again!
Impressive :)
Definitely impressive. Compare this to taking over a month to get another software author to understand complaints about his package (despite being given exact steps to reproduce). Results instead of "You're doing it wrong." Bravo.Quote:
Originally Posted by Owltoid
+1 rep for ISBoxer
Scrapdogg when you get a chance I have potentially fixed this bug, but I can't test it personally.
Here's how to see if the fix works:
1. Reboot so that HsMgr.exe is running again
2. Patch IS to the development build. To do this, right click IS and select Patcher. Check "Download development (test) patches", then close and restart IS. You should be on IS build 1.10 build 5162 or later after it patches up.
3. Launch and see if it works or is still broken
4. Let me know if it works or not
Thanks :)
ahhh... I have a soundblaster xfi sound card as well. Was / have been having issues with the sound for a few weeks now. It started right after the "Ninja fix 36", and it wasn't there before that. http://www.dual-boxing.com/showthread.php?t=30367 . I'll try that fix when I get home from work.