v0.97.9 (maintenance release)

[UncleJohnsBand]

Update: I have tried the e.0 dongle as well as the gbdongle and get the same results.

I lowered the transcode delay window from 16 seconds to 5 and now I actually get about 1/2 -2 seconds of video before there is a freeze on the MVP.

What I notice on the server is the FFMPeg process starts up begins running fine....then this dw20.exe process starts up and begins taking all the CPU...the FFMpeg gets a few seconds and then the MVP reboots.....

Has this dw20.exe process always been in the transcode process?

That's 3.0 dongle.....:p

[David]

Has this dw20.exe process always been in the transcode process?

Previous messages here have indicated that dw20.exe is actually Dr. Watson from Windows. I don't think it is supposed to be running.

[UncleJohnsBand]

Update #2......took the dw20.exe out of the picture....that is windows defender so that is no longer around.....

Now the MVP reboots much faster.....

So I am still getting the same thing.....

[UncleJohnsBand]

Update #3: With dw20.exe out of the way (which was Dr. Watson by the way) It is GBPVR that gacks during the transcode which is what is causing the MVP to reboot.....

I can now see the GBPVR abend on the server since the Dr. has left the house.....no info on the Abend....just an indication that it has died....nothing in the windows event logs either......

[UncleJohnsBand]

Update #4: Well.....I go transcoding to work again.....don't know how....but it is now working.

I do want to note one thing.....when it started to work I noticed in the logs that GBPVR was picking the PAL transcode line instead of the NTSC.....

I then realized I was now using the 3.0 version of the dongle.bin.....so I went back to the original dongle.bin and rebooted the MVP.

GBPVR now is using the NTCS transcode line....very strange......

Here is the log that shows that it picked the PAL line....for evidence....

[dfdario]

Anothe minor issue came out starting from 97.7 is FF/RW (not skip) behaviour. If used FF/RW play forth and back at normal speed and upon resume sound is lost. 96.12 hadn't this kind of problem.

[sub]

Anothe minor issue came out starting from 97.7 is FF/RW (not skip) behaviour. If used FF/RW play forth and back at normal speed and upon resume sound is lost. 96.12 hadn't this kind of problem.

Some users have reporting this for at least a year. I've no idea why some people get this.

Try deleting the following registry setting incase HKEY_CURRENT_USER\software\devnz\LastKnownVolume - It might help.

[sub]

OK I screwed up. I thought I had .NET 2.0 already on the conputer, but I didn't, and I di the upgrade anyway. I got error messages that 2 modules couldn't be registered. Then I installed the right version of .NET and re-ran the upgrade, choosing "repair".
Noe everything works OK (I had to reconfigure Zap2it) but all of my recordings are gone as are all the scheduled recordings. (Of course, the actual program files are safe, they are just gone from the GBPVR Recordings window.)
I have the backup copies of gbpvr.mdb and config.xml, but you cautioned about restoring them.
What can I do to get back the listings for the already recorded programs and the schedule of future recordings?

Walt

You'll need to uninstall. Delete the GB-PVR directory. Reinstall you old version. Restore the gbpvr.mdb and config.xml, then try the upgrade again.

[sub]

UncleJohnsBand. Have you tried playing an AVI from a local drive rather than UNC path?

[Lindsay]

Installed latest ver last night and all seemed to go fine. Tested OK on PC and MVP. However, this morning gbpvr couldn't find the 150's. Running config.exe fixed this problem. Looked at logs and system error reports. It seems that gbpvrrecordingservice.exe is causing a .net 2 error when it tries to transcode a recording at 1:00:18. (What is this transcoding it is doing?). The error is system.argumentoutofrange (screenshot in attachment with logs). This error also occurred at the same time on the 3rd so it must have happened before I updated as well.

I notice the installer logged a warning that it couldn't find blue skin task.png. Suppose this is not important.