Geoffrey Kline Posted December 6, 2009 Posted December 6, 2009 I get a runtime error several times a night from the Microsoft Visual C++ Runtime Library. I've included a picture of the error message I get. It states:Program: C:Program FilesLight-O-RamaLORMonitor.exeThis application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more informationI am running Light-O-Rama v 2.3.8 on Windows Vista Home Premium with Service Pack 2 installed (32-bit)It is a Sony Vaio laptop with an Intel Core 2 Duo CPU at 2.26 GHz with 3 GB of RAMDoes anyone have any ideas on how to resolve this issue? Attached files
Guest wbottomley Posted December 6, 2009 Posted December 6, 2009 Geoffrey Kline wrote: Does anyone have any ideas on how to resolve this issue?Upgrade to the latest version might help.http://lightorama.mywowbb.com/forum55/21007.html
Geoffrey Kline Posted December 6, 2009 Author Posted December 6, 2009 I will give that a try and post the results. Thanks for the information.
Geoffrey Kline Posted December 7, 2009 Author Posted December 7, 2009 I upgraded to LOR v2.6.2, and still it just stops with the same error message. I'm going to install the LOR 2 on a different computer and swap them out tonight and I'm hoping there is just something conflicting on the current machine, since no one else seems to have this issue.
bob Posted December 8, 2009 Posted December 8, 2009 Hmmm... not sure about this one. Did you happen to notice anything in the status log (click on the LOR Control Panel light bulb to get to it)? Perhaps it dies during the same sequence every time, for example?Maybe try Windows Update?Please let me know whether it occurs on the other computer or not.
Geoffrey Kline Posted December 10, 2009 Author Posted December 10, 2009 It seemed to die on the same sequence, but not every time. It appeared to die after it played that particular sequence 3 or 4 times.I installed on an old computer running XP that I had sitting around, and copied all the same audio and sequence files to it, and it runs like a champ. It has not stopped working yet (knock on wood). At this point I'm going to assume that there is a conflicting piece of software on the original machine that was causing the S2 software to fail.
Recommended Posts