2008-03-22, 03:04 PM
In order to upgrade to 1.2.9, I had to not only uninstall 1.1.5, but also remove all my .NET 2.0 software and re-install. (It is more complicated than that, since I have to use the DOT .NET Framework Cleanup Tool as well, etc.). At any rate, everything now works fine.
But I have in the past found that a registry cleaner can cause problems with .NET 2.0, and hence with installing GB-PVR. In particular, an earlier version of RegSeeker (I think 1.52) caused .NET problems that immediately appeared in the event logs, and could be cured only by re-installing .NET 2.0. The current version of RegSeeker (1.55) does not cause that, so I thought all was OK. But the problems I had with 1.2.9 lead me to believe that there were still some registry problems left over from past use of RegSeeker, which I no longer use. There could be other culprits, since I use other registry cleaners as well, but I see few if any entries related to .NET 2.0 in their logs. Has anyone had similar problems?
But I have in the past found that a registry cleaner can cause problems with .NET 2.0, and hence with installing GB-PVR. In particular, an earlier version of RegSeeker (I think 1.52) caused .NET problems that immediately appeared in the event logs, and could be cured only by re-installing .NET 2.0. The current version of RegSeeker (1.55) does not cause that, so I thought all was OK. But the problems I had with 1.2.9 lead me to believe that there were still some registry problems left over from past use of RegSeeker, which I no longer use. There could be other culprits, since I use other registry cleaners as well, but I see few if any entries related to .NET 2.0 in their logs. Has anyone had similar problems?
HDHomeRun Prime, Win7 64-bit, NPVR 3.4.8