Cant use innerspace with everquest since patch

zarkuth · Post by **zarkuth** » Mon Jun 28, 2010 3:29 pm

Cant seem to start Everquest from innerspace since 1.10 patch. Receive:
Software: Inner Space Kernel 1.10 Build 5136 (Mon Jun 28 13:05:58 2010)
Crash: 0x7E37B38B: Exception 0xc0000005 reading from address 0x46F10014 in module USER32.dll

Registers:
-----------------------------------
eax=46F10000 ebx=00000000 ecx=46F10000 edx=00000000
edi=00000000 esi=7FFDF000 ebp=0013FA90 esp=0013FA90

Have tried reinstalling and create a new game profile, still no luck.

Is there any way of being able to install the 1.09 as it worked flawless for me?

Best Regards
Zarkuth

Post by **Lax** » Mon Jun 28, 2010 3:43 pm

I'm working on any crashes that get reported.

In the meantime if you are having trouble with the new build, here is the old build: http://www.lavishsoft.com/downloads/Lav ... e.5039.zip

Make sure to disable "Always patch" first, in the IS Patcher window (right click IS and select Patcher)

Post by **Lax** » Wed Jun 30, 2010 2:31 pm

This issue should be fixed as of IS build 5162, now live.

zarkuth · Post by **zarkuth** » Fri Jul 02, 2010 4:38 pm

Thanx, Lax now that issue seem fixed. Now I only have an issue with eqgame.exe crashing when using my ISBoxer Charset. Might be something with the windowed mode settings. Any changes done to this in the latest updates of these programs?

/Zarkuth

Saffronica · Post by **Saffronica** » Fri Jul 02, 2010 5:42 pm

Still crashing with eqgame. Happens most of the time with ISBoxer profiles but also happened a couple times with the default "no patch" profile. Most of the time no crash/report error box pops up and the window just closes.

The initial drawing of the window works. The crash/close happens when isx attempts to reposition the window to it's desired location.

Post by **Lax** » Sat Jul 03, 2010 12:08 pm

Thanks for the info guys, I'll check it out and get it fixed asap. If you want you can revert to IS build 5039 for the time being:
1. Right click IS and select Patcher
2. Uncheck "Always patch" and close IS
3. Extract http://www.lavishsoft.com/downloads/Lav ... e.5039.zip over your Inner Space folder

Your settings will be kept in tact.

zarkuth · Post by **zarkuth** » Sun Jul 04, 2010 6:05 am

Hi again,

I managed to solve my issue by using force windowed mode in innerspace.

Have no idea why this was needed as it had worked perfectly until I got patched with new ISboxer and innerspace.

Oh well, am happy I can box efficiently again.

BR
Zarkuth

Saffronica · Post by **Saffronica** » Wed Jul 14, 2010 9:29 am

zarkuth wrote:I managed to solve my issue by using force windowed mode in innerspace.

Just wanted to add, I tried this but it did not fix the issue. Reverting to 5039 did though, so using that for now until we hear otherwise. Thanks!

Post by **Lax** » Wed Jul 14, 2010 10:08 am

Saffronica I sent you an email asking about your version of ISBoxer, your crash reports say there's a command being used that is no longer used in ISBoxer 36, which specifically addressed some startup crashes (which should include your particular crash). What version of ISBoxer are you using?

Saffronica · Post by **Saffronica** » Fri Jul 16, 2010 7:21 am

You were correct that updating to 36 seems to have fixed the issue, thanks. I never have a need to run the configuration utility anymore so didn't realize there was an update.

It may be useful to have an update notification for ISBoxer added to ISX launching/patching, if installed?

Post by **Lax** » Fri Jul 16, 2010 9:18 am

You make a fair point, I will have to see what I can do

Saffronica · Post by **Saffronica** » Fri Jul 30, 2010 3:40 pm

windowframe none

in a startup sequence was the cause of my crashes. One box kept doing it after upgrading boxer & isx but rather than come here complaining I tracked it down and removing that startup entry allowed me to use my character sets again.

Have had that entry in there for over a year with no issues and rolling back to 5039 allows it to function without the border.

Something in one of the recent builds has a conflict with trying to remove the window border.

Post by **Lax** » Fri Jul 30, 2010 4:10 pm

Yeah ISBoxer works differently now for the startup, and might react differently to manually adjusting the window during that time. Also, to remove the border just check the box in your Window Layout