Hello,
I'm having an issue with credential authentication in Everquest when I run it through Innerspace. I can log into the game when I run the Everquest client stand alone, or through WinEQ2, but when I try to log in through an Innerspace instance, I get a message that my username and/or password were invalid. When I stop trying to log in using Innerspace and launch the game normally or through WinEQ2, I get a message that there were X unsuccessful attempts to log into my account prior to this login.
Please help, I'm enjoying multi-boxing with WINEQ2, but I'd love to try windowsnapper and maybe repeater/clickboxer.
I'm running Windows Vista and I've made sure that I am running Innerspace as an administrator and that it has a rule to allow it through the firewall.
Thanks. =)
EQ Login issues when using Innerspace
Moderators: Lavish Software Team, Moderators
Sorry, sometimes when I get a lot of things thrown at me at once something slips through the cracks.
Is there something unusual about your password that perhaps maybe Inner Space isn't treating right? Is this with a US English keyboard? Unless we're talking about potential issues with umlauts or caps lock issues, I can't imagine what'd be happening here.
Is there something unusual about your password that perhaps maybe Inner Space isn't treating right? Is this with a US English keyboard? Unless we're talking about potential issues with umlauts or caps lock issues, I can't imagine what'd be happening here.
Thanks for the reply. Sorry, didn't mean to be a pest about it.
I'm using a standard keyboard with a US character set. I do use non alpa-numeric characters in my password, so I could try changing it. However, I assumed (maybe a bad idea) that wineq2 is handling the authentication pretty much the same way as innerspace and I have no problems with wineq2. Is it different?
I'm using a standard keyboard with a US character set. I do use non alpa-numeric characters in my password, so I could try changing it. However, I assumed (maybe a bad idea) that wineq2 is handling the authentication pretty much the same way as innerspace and I have no problems with wineq2. Is it different?
No, it's not different. Neither Inner Space nor WinEQ 2 know anything about EQ authentication, just that you're moving the mouse or pressing keys.
What is different is that Inner Space is virtualizing all of the input, and WinEQ 2 doesn't. So for example if you hit ALT+156 with WinEQ 2, Windows is doing the work to turn that into ?. However, since Inner Space is virtualizing the input, that particular feature has to be implemented at the Inner Space level. And I think that's broken at the moment but nobody's complained about it.
What is different is that Inner Space is virtualizing all of the input, and WinEQ 2 doesn't. So for example if you hit ALT+156 with WinEQ 2, Windows is doing the work to turn that into ?. However, since Inner Space is virtualizing the input, that particular feature has to be implemented at the Inner Space level. And I think that's broken at the moment but nobody's complained about it.
Ok, that did the trick. THANKS!
The non alphanumeric characters (allowed by eq) were causing the problem. Changing my pwd fixed it.
New problem, however...
Now that that's working and the game is launching in a IS session (I know it is, because windowsnapper works and I can see the FPS and memory info), I can't get the console to open from within a session. I tried changing the bind from the uplink configuration using---general tab>session-startup button>clicked console in the left pane and changed "`" to ";" (tried a few others too) in the "command to execute" box>clicked apply>finish and restarted IS.
Help is appreciated. =)
The non alphanumeric characters (allowed by eq) were causing the problem. Changing my pwd fixed it.
New problem, however...
Now that that's working and the game is launching in a IS session (I know it is, because windowsnapper works and I can see the FPS and memory info), I can't get the console to open from within a session. I tried changing the bind from the uplink configuration using---general tab>session-startup button>clicked console in the left pane and changed "`" to ";" (tried a few others too) in the "command to execute" box>clicked apply>finish and restarted IS.
Help is appreciated. =)
; is a special character used to separate commands, so that's why that one wouldn't have worked. You wouldn't necessarily have known this but you could have put it in quotes e.g. literally ";" to make it bind console ";" console toggle for that key to work.
It does sound like you are following the right process to change the console bind, though. Unless IS isn't properly registering your input I can't imagine why ` doesn't work. You can try doing F12 instead, that's another popular one.
What other keys have you tried?
It's possible that something is breaking the startup sequence before the console bind gets applied. Have you made other startup sequence modifications?
To find out if the bind is there, you can open the console in the Uplink (right click the IS menu and select Console for this one) and do something like "relay is1 bind -list". The command will execute in the is1 session, and the output from the command will output to where it was sent from. It should show you the console bind, among others.
It does sound like you are following the right process to change the console bind, though. Unless IS isn't properly registering your input I can't imagine why ` doesn't work. You can try doing F12 instead, that's another popular one.
What other keys have you tried?
It's possible that something is breaking the startup sequence before the console bind gets applied. Have you made other startup sequence modifications?
To find out if the bind is there, you can open the console in the Uplink (right click the IS menu and select Console for this one) and do something like "relay is1 bind -list". The command will execute in the is1 session, and the output from the command will output to where it was sent from. It should show you the console bind, among others.
Ok, thanks again for the feedback.
Some other keys I tried were "~", "*", and even "1" just to see if it worked.
I used the relay command as you described, and "`" is the console bind. By the way, "`" works fine in the uplink. I do have "`" bound to a key in the game, would that make a difference? I'll try to change it to eliminate that as an issue.
Other relay commands do work. I Used relay to change the window size via windowsnapper and it worked like a charm. I couldn't managed to get clickboxer to launch relaying from the uplink, however.
Anyway, I'll try th in-game bind change and then let you know how it works.
Thanks again. =)
Some other keys I tried were "~", "*", and even "1" just to see if it worked.
I used the relay command as you described, and "`" is the console bind. By the way, "`" works fine in the uplink. I do have "`" bound to a key in the game, would that make a difference? I'll try to change it to eliminate that as an issue.
Other relay commands do work. I Used relay to change the window size via windowsnapper and it worked like a charm. I couldn't managed to get clickboxer to launch relaying from the uplink, however.
Anyway, I'll try th in-game bind change and then let you know how it works.
Thanks again. =)
Well, ~ is actually shift+`, and * is actually either shift+8 or "Num *", so that's why those wouldn't have workedSome other keys I tried were "~", "*", and even "1" just to see if it worked.
To see a list of all of the available keys for binding, you can do "bind -keylist" in any console. If the name of the key has a space in it, you would need to surround it with quotes for the bind.Either way, glad you got it working (and no, an in-game bind to ` shouldnt affect it)