only one instance launching?

Well, I've tried everything I could find on these forums and a whole bunch of program/driver/etc installs/uninstalls, including the steps mentioned in the other post. I have been able to occasionally get two instances to load. Unfortunately it is not repeatable and I can't get a third. One the second instance loaded after I messed around with the window settings in ISBoxer and exported. Unfortunately, repeating that doesn't seem to work. I also deleted all the toon .ini files and reloaded each one through ISBoxer manually one at a time. Still not working. The charater slots and window positions seem to work fine through ISBoxer when I manually load a slot. Manually loading any second slot with one already running fails. It's always the same, launcher window disappears like it is going to begin loading the game, but nothing happens. Task manager shows turbingclientlauncher.exe using around 3% CPU and 25MB, lotroclient.exe using around 20% CPU with 12MB memory. About the only thing I can do now is reload a backup of my hard drive from last week when it was working and see what happens.

[bob]

I don't know what to tell you.

I am using Innerspace build 6036 (this was the current build at the time the issues with Update 15 started).

After scanning closely through your diagnostic, and comparing it to mine, there are only a few differences I can see. They are pretty pedantic differences.

Code:

5. C:\Program Files\Bitdefender\Bitdefender 2013\Active Virus Control\Avc3_00284_078\avcuf32.dll
24. C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
52. C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
76. C:\Windows\system32\nvspcap.dll
82. C:\Windows\system32\nvwgf2um.dll
106. C:\Windows\SysWOW64\CtHdaCtl.dll

So the first is obvious.

The next two, in my diagnostic my 2005 Visual C++ runtime is reporting build 6229. This is coming from the SideBySide installs (the funny path).

Code:

23. C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6229_none_d089f796442de10e\MSVCR80.dll
51. C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6229_none_d089f796442de10e\MSVCP80.dll

This difference is probably an update you don't have. Check your Windows Updates.

The next two look like NVidia dlls. I have ATI dlls in this place, so they can probably be ignored, although one of them (76) looks like NVidia Shadow Play, which is reported on the NVidia forums as causing a few issues. If you have Shadow Play installed, I'd look at removing it.

And the last difference (106) looks like a dll for your sound card. Perhaps if you make sure all the clients are using the Generic Software sound device.

As you said, you might be looking at a restore/rebuild.

Bob, it's interesting you say you are running Build 6036. Mine is 6040. IS patches automatically for me. Do you know if your's works under 6040? Is there a way I can roll back to 6036?

[bob]

Yep. Patched up to 6040 and still starting up normally. It does appear to be a tad slower to get the next launcher running, but we are only talking 3-4 seconds.

You can roll back to prior releases, but 6030 is the next one available.
You can find it here https://www.lavishsoft.com/innerspace/archives. You will need to login to you lavishsoft account to access it. Follow the instructions.

Got it!

So... Build 6030 did not work with the launcher. I browsed through my backup files (thank goodness I back up often) and found Build 6038. I restored the entire folder and I won! I have all 6 instances running. The launcher was a bit slower on the response than it used to be, but at least I am in game.

My question now is, what changed in 6038 to 6040 that would cause mine not to work, but works fine for others? I would be nice not to have to worry about updating going forward.

Well I don't know what to say. I am still having the login issue even with all the innerspace updates. Microsoft is up to date, good hardware, no bugs. I would be happy to send someone my diagnostics again.

[lax]

This topic is not informative or useful, let's please stop bumping it. The original issue with the LOTRO update has been solved. If you are having an issue with launching the game, please start a new thread (as detailed in the sticky post What to do if ISBoxer, or your game, will not launch), and I need your diagnostics. If the game instance is freezing, "Diagnostics for game freezes" is useful (and you must get it from the frozen instance of the game), otherwise just get "Diagnostics for game crashes" and pray that it has useful information in it.

If you got me diagnostics information prior to Inner Space build 6053, then I need new diagnostics with you on Inner Space build 6053 or later. This is currently the development build of Inner Space; to try it out, right click Inner Space, select Patcher, tick "Download development (test) patches" and then close and restart Inner Space to let it patch up.