pankov Posted January 4, 2009 Posted January 4, 2009 I'm having a strange problem with DVBViewer. I was trying to move it to the secondary monitor ... or may be I was rebuilding the graph while already being on the secondary ... sorry can't remember exactly ... and then DVBViewer crashed with "Runtime error 217". That's not the big problem though. After this crash when I try to start it again nothing happens - I mean it doesn't start anymore - no Splashscreen no nothing. If I do start it a few times I can see it for a second in my ProcessExplorer and I'm pretty sure that DVBViewer starts but exits quickly. I think it has something to do with the algorithm for preventing multiple instances. I think that DVBViewer is fooled that the previous instance (the crashed one) is still running. I tried starting in debug/safe mode but nothing happens ... I don't even see a debug.log created The only thing that I have to do to get DVBViewer working is a full restart Is there a way to manually reset this flag/mutex/semaphore/registry or whatever is used so I don't have to restart? This happens only for second ... may be third time ... but I'm feeling it has something to do with changing monitors ... which I'm planning to do very often now. In this line of thoughts will there be an easy way to control which monitor DVBViewer starts? support.zip Quote
Lars_MQ Posted January 4, 2009 Posted January 4, 2009 dvb recording service, dvbserver, ge or transedit running? they will prevent a start of the viewer also. Quote
pankov Posted February 9, 2009 Author Posted February 9, 2009 Lars, sorry for posting so late but I never received an e-mail that you've posted to this topic even though I'm subscribed to it ... Now back on topic: You were right - after I close the crash message of DVBViewer the DVBRecService starts right away. Then when I start DVBViewer it doesn't stop the service as it normally does. If I stop the service manually DVBViewer starts nicely :-). Then I can close it without error and the service/DVBViewer start/stop pattern returns to normal. So I guess that the problem is not in starting DVBViewer but in stopping the recording service. I'll be glad if I can help you fully solve this problem but nevertheless I'm very happy that you've pointed me to a solution so I don't have to restart the whole PC. 10x. Quote
Lars_MQ Posted February 9, 2009 Posted February 9, 2009 I'll be glad if I can help you fully solve this problem but nevertheless Unfortunatly the only solution is to not letting the viewer crash. We are well aware why you can't start the viewer after a crash if one of the above mentioned programs are running. The solution would be to abandon the inter program communication about used devices and not to use devices and this would not be acceptable... Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.