Inner Space Launcher ERror Code -12 (With Lineage 2)

Discussion of Inner Space

Moderators: Lavish Software Team, Moderators

Post Reply
Miyara
GamingTools Subscriber
Posts: 1
Joined: Mon Feb 02, 2009 6:08 pm

Inner Space Launcher ERror Code -12 (With Lineage 2)

Post by Miyara » Tue Feb 03, 2009 1:04 pm

Hi there,

I'm new and currently interested in dualboxing about 5 characters up in Lineage 2 on a private server. I bought the 90 days subscription to this program but am unable to launch Lineage 2. This is what it tells me:

Failed to execute 'e:\games\lineage ii - Hellbound\system\l2.exe'. Inner Space Launcher Error Code -12 (it will help to report Inner Space Launcher Error Code -12 if reporting this issue!)

So I am wondering whats wrong. Starting up WoW works fine.


Thanks in advance and greetings,

Miyara.

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Tue Feb 03, 2009 5:45 pm

Thanks for the report, I will see what I can do to solve this problem. Lineage 2 apparently has some protection built in that happens to confuse the Inner Space launcher

shinkux
GamingTools Subscriber
Posts: 9
Joined: Sun Aug 10, 2008 4:10 pm

Post by shinkux » Tue Mar 17, 2009 9:22 pm

hey guys, im back =). Sorry to resurrect an old thread but I'm trying to get InnerSpace working with Lineage 2..again.

So my current problem: first instance of Lineage 2 opens fine.

Now, in order to open up more clients, I do the same thing, Lineage II>Lineage II Default Profile, and it gives me this error:

WinLicense
An internal exception occured(Address: 0x10ac2dac) Please, contact support@oreans.com. Thank you!

I was hoping during the time since I last tried that issues were resolved for Lineage 2 heh. Any advice on getting L2 working? Thanks.

eqjoe
GamingTools Subscriber
Posts: 221
Joined: Wed Oct 13, 2004 2:34 pm

Post by eqjoe » Tue Mar 17, 2009 10:01 pm

L2 uses Gameguard. It most probably does not play nice with IS.

-j

shinkux
GamingTools Subscriber
Posts: 9
Joined: Sun Aug 10, 2008 4:10 pm

Post by shinkux » Tue Mar 17, 2009 11:23 pm

yeah..well manually opening l2.exe in LineageII\system\ works fine, so it's got to be the way in which IS tries to open multiple instances of the game. first one opens fine, but if there are any existing l2 clients open, it always throws the internal exception error

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed Mar 18, 2009 9:54 am

If you werent getting the -12 error you should have started your own thread ;)

The way IS opens multiple instances of the game is precisely the same as it opens the first one. There is no difference between launching the first, and launching the second. So I don't know what the exception is for, I would have to get L2 specifically to test this issue. That's not something I am planning on doing soon, so if you'd like a refund let me know.

Post Reply