ext isxeve will not load

Jerkjohnny

Active Member
For about a month now I have been trying to get the ISXEVE extension to work. When I get to the command prompt and type "ext ISXEVE" is when it hangs, client is still operating in a loop, but never changes the amount of resources it uses.

I have reinstalled innerspace and ISXEVE dozens of times, cleared my cache, I even copied the entire innerspace directory from a working computer just to see if I could narrow down a file(s) to try and get it to work. No luck.

This has been ongoing since many weeks before the latest release from EVE, so it does not have anything to do with the patch, perhaps the patching process for ISXEVE though. I was hoping with the new release of an ISXEVE file with the expansion this problem might fix itself, but to no avail.

When I echo to try and find the latest version (which is the latest one from the forums here regardless) it returns a 'NULL' response.

I'll be happy to give up any extra needed info, and even run a error dump, but since it never actually crashes, just sits there in perpetuity, it might not help.

Anyway, I'm at the end of my patience guys, usually I figure this stuff on my own and have been very successful for many years (it's not like it's rocket science to get it working, just the coding =p) but I'm done now, out of any plausible options short of formatting the harddrive and starting over. Your wisdom, intuition, and bullshit are highly welcome, thank you.
 

Jerkjohnny

Active Member
Yes I just checked again and retried the entire process. That ISXEVE file is the same one I've been using.

even if I delete the file with my subscription info it never gets that far, nor will it create a blank file like it used to long ago if unable to detect one. The subscription confirm window never pops up anymore either. I noted another post or 2 where people had to input the information manually, while this did work on the other computers I use, I am baffled as to why on this one it does not.

I will get the teamviewer info shortly after looking around one last time for any possible interference from alternate programs or other anomalous human error stuff.

Has anyone had other programs, like Steam or other 3rd party stuff from random games pop up and ruin the party for them?
 

Jerkjohnny

Active Member
just noticed that the computer with the crashing version of ISXEVE is from march 13th of 2012, while the working computer(the one that was able to update itself normally through the command prompt) is dated april 24th, 2012.

is there any place I can get the most recent version of the ISXEVE file? I know there was an archive around here someplace.
 

Amadeus

The Maestro
Staff member
The link I gave you in my previous posting is the most up-to-date ISXEVE.

This computer that you're using isn't using windows 8, is it?
 

Jerkjohnny

Active Member
Using windows 7.

What I meant was that when I un-install the ISXEVE using the uninstall utility, it still says its from march 13th, not the .dll extension, which I am now, and have been, trying.

But when I watched the other 'working' computer patch versions, they went from march 13th, to april 24th, as per the loaded ISXEVE info from the command prompt.

Now everytime I uninstall ISXEVE it states that it's still the matrch 13th version , but I'm betting that's just typo/leftovers.

I used the isxeve.dll file that was updated this morning as well. When I type 'ext isxeve' it still hangs indefinetly, does not check subscription status, nor does the client use any extra resources from that moment on.
 
Last edited:

Jerkjohnny

Active Member
I made some progress./ As long as I do not use the latest version of the .dll file it at least goes through the motions of acting like it checks the subscription.

Of course it neither checks the subscription nor opens the utility to try.

So at this point I manually input the Sub info for ISXEVE into the .xml file and save it accordingly, this worked on the other computer.

The brand new message i got was :

"Invalid Extension Version. Innerspace is using ISXDK v32, and this extension was built with a different version. To use this extension you need to download a new version that supports the latest interface."

So I patch ISXEVE.ex3e over it again and re-try and the client freezes again. I remove the .xml subscription file, and put the old ISXEVE.dll file back, and the process is repeatable after force closing and restarting eve through innerspace.

I found this post from a while back :

http://www.isxgames.com/forums/showthread.php/4443-InnerSpace-Update-(ISXDK-32)

That's as far as I've gotten so far.
 

Amadeus

The Maestro
Staff member
Are you sure this computer has the latest version of Innerspace on it? Make sure you've enabled "download patches" or whatever it's called so that it will update itself as needed.
 

Jerkjohnny

Active Member
Latest version of innerspace, fully patched.

Those are the responses I get from command prompt using the .dll file that comes with the ISXEVE.exe package.

If I use the one directly from the link you provide elsewhere and above here in this post, then it hangs forever right after the 'ext isxeve' command is entered.

Everything is running as admin, the subscription info is entered correctly, everything is installed as before.

Innerspace just really doesn't like any of the new isxeve files.
 

Jerkjohnny

Active Member
Somehow I got it to work. Through some creative gymnastics (more like spasms).

I create the file I need with blank sub info as text file, then try to load it, with both a txt, and an xml file in the right folder, both with generic 'yourusername" info in it, no specifics.

Then I 'ext isxeve" it looks for sub info (won't work if there isn't a txt file as well in the same folder with the same name) tells me I have no sub, blah blah blah...

Then I 'edit' the isxeve.xml file, adding only the username and password. And poof, it seems to work now.

The only step I added was to leave the txt file with the generic subscription info in the extensions folder alongside the actual .xml file. I guess.


Yeah, Hell if I know. I know it was me, not like I can blame it on the dog.
 
Top Bottom