Single instance check not working in 1.5.36

[mvallevand]

I got multiple with that but the log has

2010-12-28 14:34:12.642 [DEBUG][1] Created mutex. Must be only instance.
2010-12-28 14:34:12.759 [DEBUG][1] Version: 1.5.36
2010-12-28 14:34:12.761 [DEBUG][1] SingleInstance()

FWIW I was testing some code and this works but Global doesn't

Code:

Mutex mutex = new Mutex(true, "Local\\NPVR_INSTANCE");
            if (!mutex.WaitOne(0, false))
            {
                MessageBox.Show("Instance already running");
                return;
            }

Martin

[sub]

That patched changed from ""Global\\NPVR-instance-mutex" to "NPVR-instance-mutex", which is the way GBPVR did it.

I also realised the logs wont help, since the first instance will get access to npvr.log. The second instance wont create logs, since the first one already has the file open.

[Reddwarf]

Didn't work here.

[thawk]

Hi

Im also getting this same problem with version 2.0.3 Im on windows XP. Has any solution been identified yet? Many thanks

Tim

[Reddwarf]

Hi

Im also getting this same problem with version 2.0.3 Im on windows XP. Has any solution been identified yet? Many thanks

Tim

I think Sub just gave it up, it doesn't work here in 2.0.3.

[thawk]

Oh dear - i just changed over from gbpvr which almost everything was working great on for me to get quicker channel changes and avoid out of sync jumps on the timeline. Npvr is certainly better from those repsects, but i like to use itunes for music and program the remote to switch to itunes with the 'music' button and back to npvr with the most of the other buttons (videos, guide, TV, pictures), but now with those buttons i open a new instance of nPVR and its gets itself into a real tangle!

Any ideas if this seems to be an unfixable problem with npvr? Eg a script i can put in the irremote.ini file against those command that does a switch somehow instead of TV={run(c:\npvr.lnk)}?

Thanks

Tim

[sub]

It works fine here, and it's doing the same thing as GBPVR did, so should work for you if it used to work in GBPVR.

If someone bumps the thread after the next release (when I'll be in a position to provide patches again), then I can provide a patch which collects logs for the second instance of nextpvr.exe so we can see why its not working for some of you.

[JP23]

Any ideas if this seems to be an unfixable problem with npvr? Eg a script i can put in the irremote.ini file against those command that does a switch somehow instead of TV={run(c:\npvr.lnk)}?

Single instance check is working fine for me, (W7 Ult x64), but to answer your question, I believe you can use the 'FindWnd' and 'fgnwnd' commands to bring a specific window into focus.

See here: http://www.hazeveld.demon.nl/Docs/irremo...v22180.txt.

[thawk]

Great

Many thanks

Tim

[b00sfuk]

Don't know if this is relevant but I found that my choice of remote hardware/software made a difference. Using an MCE remote with the Microsoft USB IR receiver/blaster (and IRSS) gave me this problem. When I switched (back) to my iMON remote/receiver (& software) the problem went away.