Remote Problem + Zap2it issue

[sub]

send 'em all

[sub]

Please do an 'Empty EPG' followed by an 'Update EPG', then resend the logs.

[aplc0r]

okay, now I am getting a .NET fatal error and cannot boot the program. I've reinstalled once already but I'll give it another shot =/

[aplc0r]

everything is working fine now after another reinstall, thanks for all you help and sorry for the drama ^_^

[sub]

okay, now I am getting a .NET fatal error and cannot boot the program. I've reinstalled once already but I'll give it another shot =/

Not at you specifically, but just makes me laugh when people say they had to reinstall. I've seen a few of these comments recently. What a crock of shit...

If things wont start, or gives an error at startup, there is always a good reason for it. I occasionally recommend the user reinstalls the application because it saves me having to work out what they have done to damage the installation.

The most common reason is a misbehaving plugin. Easy solution is delete *everything* from the 'c:\program files\devnz\gbpvr\plugins' directory.

There is no registry setting or anything that can get corrupted, so nothing to worry about there.

This is two important configuration files that the user can damaged:
1) config.xml - usually as a result of fiddling setting in a text editor and stuffing something up. Deleting this file will cause the Windows Installer to restore the original file.
2) or, gbpvr.mdb which can be damaged as a result of the user manually edit in Access, or a plugin writing some crap data to the database. Forcefully killing the application from task manager can sometimes result in a damaged database. Deleting this file will cause the Windows Installer to restore the original file.

In general there is no good reason to just reinstall, other than saving time on diagnosing what you've done wrong.

[aplc0r]

I understand that, because after my first reinstall I searched for registery keys, didn't find anything, and I kept getting the error. What solved the problem was an uninstall + reboot + reinstall. I suppose a few corrupted files stayed in memory. So I'm not exactly saying that a reinstall magically fixed it, I know a bit more about programs to believe that =P

[sub]

As I said, it wasnt aimed at you specifically.

Glad you got it going.