Tue Apr 15, 2014 9:17 pm by lax
Close both ISBoxer and Inner Space.
Then open up your Inner Space folder, and find the InputDevices.XML file. E-mail this file, as an attachment, to
lax@lavishsoft.com.
After e-mailing it to me, delete InputDevices.XML, and launch Inner Space. Inner Space will re-create the file without the error in it. This will correct the issue for a while (may take months to happen again).
Launch ISBoxer.
What I will do is look at the XML file to see which input device caused this error, and permanently correct the issue with an Inner Space update, probably before the issue happens to you again
