Unable to Connect

Very Frustrated with this application. So far, when i launch WoW through Inner Space and try to login to my account within WoW, i get an "Unable to Connect". I've read several other forums, and tried every suggestion ive found. I've literally terminated every last application besides the default windows processes. And reading the repeated 'its not our program, its obviously some other program that's interfering that's causing a network problem' is beyond ridiculous. I have 6 days left on my 'trial' and I feel like the only way to solve this is to install this on a fresh image of Windows.

What do i need to provide to help? And so far the 'diagnostics' that people have uploaded has provided zero help in a resolution, so lets do something else

[bob]

The diagnostics are for us, too see if you have an application compatibility setting, another piece of software which doesn't always play nice, or in some cases even whether you might need to run a different version of Innerspace (despite the Update, this post still applies in some cases). You could probably glean the same information from them yourself, if you know what you are looking for (which just takes a bit of reading of the forum posts or hanging out in the IRC chatroom).

All that said. If you could provide a diagnostics (this is pretty much going to be the starting position for this kind of issue).


edit: because I felt like it.
There are a few references in the forums to "unable to connect" and "error 114". This post about speedbit is the only one which seems promising for an immediate solution.
The others not so much, although they do seem to reference other language keyboards, or even the most obvious problem (to us anyway) which is, you still have Key Maps enabled (which you can disable with SHIFT+ALT+M or the left A-> Z overlay button) or you have an AltGr key and did not select this option during the Quick Setup Wizard (you can test both of these out by typing your password into the username field and see if it comes up correctly).

Beyond that, the diagnostic which you don't want to provide, is still going to be the starting point, whether you think they will provide help or not. Sometimes they point to stuff you don't want to discuss because you are using a private server and have read the FAQ, but in some of those cases, that might be the problem - i.e. the hacking that the private server people have had to do to the game client means that it no longer play's nice with the standard Windows functions because they haven't accounted for the shift in some offset or another. For the most part, we don't care about what software you are running, or where it came from, we are just interested in getting you up and multiboxing provided it is within Lax's rules).

[lax]

And reading the repeated 'its not our program, its obviously some other program that's interfering that's causing a network problem' is beyond ridiculous.

Most people don't understand (or, frankly, care) what Inner Space is actually doing or why other programs may interfere. It is totally magic to you, so it is okay that it seems ridiculous.

When Inner Space launches the game, Inner Space replaces a lot of Windows API within the process (this is extremely complicated); it has to do this in order to provide the feature set you want with ISBoxer. Then, other software will then often load a DLL within the game, and sometimes use the API in an unexpected fashion... sometimes just blatantly wrong, not checking for error conditions... or sometimes entirely correct, but using some undocumented detail or obscure behavior or side effect... or even a bug in how Inner Space is handling the API. The problem is there is no way to know in advance which programs will have an issue and which ones will not, and this is where we seem to be with you -- you've found something that is breaking it and now we first have to determine what program it is. The easiest way to tell a lot of the time is process of elimination, which is why we say to rule out other programs by shutting them down. Various security software (antivirus, firewalls, etc) will continue to load these DLLs within the process even when "shut down"; this is why we sometimes have to suggest completely uninstalling that type of program to rule it out (install again after ruling it out).

Windows almost exactly the same stuff as well in its Application Compatibility system. This is why we also have to tell people to disable their Application Compatibility settings for Inner Space and games -- it creates a conflict with Inner Space that can only be resolved by disabling it. For most programs we can suggest alternatives or setting adjustments that can help.

I agree it does get a bit ridiculous. There is no better way to multibox, so we do what we can to continually improve compatibility -- identifying problems and either fixing Inner Space or providing another solution. What you are experiencing right now is part of that process. I apologize that it is frustrating

I have 6 days left on my 'trial' and I feel like the only way to solve this is to install this on a fresh image of Windows.

Another way to put this is: "I've had it for one day, asked a question one time, and I feel like the only way to solve this is to install this on a fresh image of Windows". I will point out that a fresh image of Windows is a last resort and certainly not a typical suggestion. Most of the time it is much better to identify and resolve the actual problem, which is what we are here to help you do.



So .. as Bob said, we want "Diagnostics for game crashes" (http://isboxer.com/wiki/Diagnostics) from ISBoxer's Help menu to move forward.