nPVR cannot record or delete files...disk access problem?

[dshoup]

2 days ago my nPVR program stopped recording programs and began producing errors when I tried to delete previously recorded shows. I can watch previously recorded programs with no issues. I assume this means nPVR somehow lost privelages to modify files, but I can't see why. I can delete files I have watched manually using windows explorer.

Things I have tried:
I had not yet updated to v 3.5.7, so I tried that...no effect

I used windows explorer to "share" my recording directory with "everyone" and gave read and write permission...still has same problem.



I've attached my logs. Anyone have any ideas on how to fix this?...going to be a real bummer when the fall season begins next week

[sub]

Can you reboot, try recording, then post your logs again?

[dshoup]

Ok...after a fresh reboot things worked perfectly. I recorded a minute or so of a show, could play it back, and then deleted it successfully. I'm posting the logs just in case it is still useful, but I suspect you were hoping to find new error information. At least this shows my problem must be due to something that happens after the computer has been running a while (maybe a conflict with some other program for a driver or something?). Any thoughts/suggestions?

[HarryH3]

I haven't had any problems with NPVR/Windows oddities since I added this PostEPGUpdate.bat file:

echo off
REM Reboot if not recording
set NSHelper=c:\"program files (x86)"\npvr\nscripthelper.exe

:check
FOR /F "tokens=*" %%i in ('%NSHelper% -isinuse') do SET condition=%%i
echo %condition%
IF %condition% =="NOT RECORDING" goto reboot

:delay
sleep 60
goto check

:reboot

echo "About to reboot"
shutdown /r

Now it reboots in the middle of the night so Windows gets a fresh start and the ghosts in the machine are banished.

[sub]

Ok...after a fresh reboot things worked perfectly. I recorded a minute or so of a show, could play it back, and then deleted it successfully.

Ok, let us know if it returns.

I'm posting the logs just in case it is still useful, but I suspect you were hoping to find new error information. At least this shows my problem must be due to something that happens after the computer has been running a while (maybe a conflict with some other program for a driver or something?). Any thoughts/suggestions?

It was pretty hard to follow your logs, so I was just hoping to see a cleaner set of logs after a reboot, but if it fixed itself that's even better

[dshoup]

Sadly, the problem has been here for about 3 days and I shut the PC down (not just hibernate, but actually turned off) each night...I suspect it will be back, so let me know if you have ideas for the next step. Could I do something to "clear" the logs and make them easier to follow for the next time I have the problem?

[sub]

Just post the logs next time, and I'll take another look.

[2leftfeet]

@HarryH3

:delay
sleep 60
goto check

"sleep" is not an a standard internal command or program, what does it do and where would I find it?

[Graham]

"sleep" is not an a standard internal command or program, what does it do and where would I find it?

"timeout" is built into Windows and does the same thing ... http://ss64.com/nt/timeout.html

[2leftfeet]

Thanks!