ISBoxer issue

JamieW · Post by **JamieW** » Wed Aug 05, 2009 10:04 pm

The recent change to ISBoxer to remove the timer between client loads has an unintended fatal side-effect:

If a client crashes during the load-process, it will forever wait for that client to load

This is a problem specifically with LOTRO as I have an issue where it crashes, on occasion, due to a DINPUT8.dll app-error. Turbine's answer to the problem is to "change the USB port of your input devices and hope for the best".

For loading 1 client, it's not a big deal, but when you have a 10% chance of crashing, and you're trying to string together 4 successful loads, it can be frustrating. I recommend putting an optional timeout value back in ISBoxer.

Post by **Lax** » Wed Aug 05, 2009 10:44 pm

The way it works is it'll wait 60 seconds for the session to launch. If it launches, then ISBoxer will automatically kick off the next character. If it does not, then you can manually launch the next character by re-launching the Character Set. At the moment if you do this during that 60 seconds, it will fail. I will correct that tomorrow.

So anyway, if one crashes, wait 60 seconds and re-launch the set (you do not need to close any), or watch the console in the uplink for the message that says you'll need to manually launch (or "endscript isboxer" in the uplink console if you get impatient)