NPVR Client Lockup

[jcjefferies]

I have had two long standing client /server problems but have not reported it because both my XP server and client were very old hardware and the server has minor hardware problem. However I now have a new Vista server which avoids the DVBfix problems with XP and also a newer XP client.

Currently the main problem I have with NPVR is pressing “Esc” (Clear) on the remote to end playback on the client sometimes causes NPVR.exe to run at max. At first it seems to do nothing as the recording continues playing for about 20 seconds then locks up. I don’t yet know at what point the processor starts to run at max but the remote stops working after the initial press. This happened several times in the last few days but with the old setup happened less often. The client sees that Esc was pressed and saves position but does not quit. I have had the same happen once when “Pause” was pressed but never when skipping forward or back. The server seems to stop sending data when “Esc” is pressed on the client. Then when NPVR is killed on the client the server reports an “Unexpected exception in ClientConnectionHandler”.

Enclosed are server and client logs which dont seem to offer any clues. The event happened at 22:47:31 which is at the end of both logs.

[sub]

Can you create a c:\temp directory on the client, and set HKEY_LOCAL_MACHINE\Software\NPVR\LogSlipFile=1 (DWORD) and HKEY_LOCAL_MACHINE\Software\NPVR\LogClientStream=1 (DWORD), then reproduce the problem and post the client npvr.log, server's nrecord.log and client's c:\temp\stream.log and c:\temp\reader.log?

[Reddwarf]

Does the same happend if you press ctrl-s (Stop) before esc on the client?

[jcjefferies]

I have added the registry settings requested. I notice that "Esc" does not seem to be listed as an official NPVR key. From when I started using NPVR with a keyboard I found that Esc took you back up one menu level but also stopped playing a recording so used it instead of Stop. I will mix using Stop and Esc plus Pause to repeat the problem but I think it seems more likley to happen if the recording has been playing for at least 5 minutes.