PVR remote control blocked by ZoneAlarm 7

[rnslucas]

Firstly, I'm still using GBPVR v0.96.12 with a Hauppauge 350! Yes, I know it's not supported, but I can't afford a new card yet, and the time to totally reconfigure my computer!

I've upgraded my Zone Alarm anti-virus/firewall, and now GBPVR won't reach the remote control. Here's the error message from gbpvr.exe.log:

18/01/2008 09:10:50.906 VERBOSE [2] getValue() loading new key/value into cache: /settings/HardwareDecoder
18/01/2008 09:10:50.906 VERBOSE [2] getValue: /settings/HardwareDecoder : Hauppauge PVR350
18/01/2008 09:10:50.906 VERBOSE [2] Initializing renderer: PVR350
18/01/2008 09:10:54.453 VERBOSE [2] getValue() loading new key/value into cache: /settings/DirectRemoteAccess
18/01/2008 09:10:54.453 VERBOSE [2] getValue: /settings/DirectRemoteAccess : true
18/01/2008 09:10:54.468 VERBOSE [2] HauppaugeRemoteDirect() starting
18/01/2008 09:10:57.125 ERROR [2] Access is denied
18/01/2008 09:10:57.140 ERROR [2] at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited)
at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId)
at System.Diagnostics.Process.get_Modules()
at System.Diagnostics.Process.get_MainModule()
at System.Diagnostics.Process.get_ProcessName()
at xeac631af6df616bc.xa10842e3b8de7997..ctor()
at xeac631af6df616bc.xa10842e3b8de7997.x479a7b07c9d5bd70()
at xae10db17d26ba033.xbb1566157f5f8b1f..ctor(String x2b67e84843b345a4, Boolean x16a8bfd49ea44853)
at xae10db17d26ba033.xbb1566157f5f8b1f.xfb409e85bd292293(String[] xf18a926310372520)


The program GBPVR.exe has 'Super' access but this does not help. I've given 'Super' access to all other relevant programs.

I can locate relevant .ini and .dll files, but can't find a way of telling Zone Alarm, that they are allowed.

The remote works fine with another TV program, and works fine through GBPVR when ZoneAlarm is turned off.

Does anyone perhaps have an answer (before I roll back my Zone Alarm)?

[sub]

Your only chance is probably to rollback the version of Zone Alarm. Sorry.

In case you're a coder, this is what it was doing:

Code:

            Process[] processes;
            processes = Process.GetProcesses();
            foreach (Process process in processes)
            {
                if (process.ProcessName.ToUpper() == "IR")
                {
                    Logger.Verbose("Hauppauge IR.EXE is already running - direct remote access disabled");
                    hauppaugeRemoteProcessRunning = true;                    
                }                
            }

Its just checking IR.exe was running, but Zone Alarm is for some reason not allowing to do this. I'd ask the zone alarm people why it is doing this. Your only other option is finding a way to disable this behaviour in the zone alarm settings, or roll it back to the old version.

That check wasnt strictly necessary, and was just a simple nicety. Unfortunately I cant provide you a patch though, since I only have a 1.1.5 development environment, I can only provide patches for 1.1.5.

[rnslucas]

Thanks for your help Sub!
I've asked Zone Labs support to look at it, but I'm not holding my breath!
I think the quick answer is to roll back Zone Alarm.
The long answer is to place a begging bowl outside my door, buy another TV card (we've got to go digital at some point anyway), and take a day off to rebuild with wonderful new PVRX2.
Cheers.

[Spamdini]

I had the same thing happen to me with Zone Alarm and my Hauppauge remote. I set ir.exe and pvrx2.exe (or gbpvr.exe) to super and set everything to allow access, I also clicked on options and selected allow application interaction. Anyway something in there got it working for me.

[rnslucas]

I've given 'Super' access to all of the programs I can think of, and also added in the 'Allow Application Interaction' for all of them too.
Still no success.
Spamdini, did you have to manually add any of the programs?

[Spamdini]

No, I didn't add anything. I have a 150 and a 1600 using 1.1.5. You could try the beta at http://www.zonealarm.com/beta/ to see if that changes anything. Or you could always give 1.1.5 a whirl. Just back up your files first so you could go back to 96.12.