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.
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.