config.xml corrupted GBPVR wont start

[divinehammer]

This happened to me last night on 99.05. Sometimes my GBPVR likes to hang the machine. This always seems to happen with comskip enabled and a badly fragmented drive. So yesterday the lockup did not seem out of place because I was recording and deleting many shows causing lots of fragmentation. So the machine was hung I manually restarted and GBPVR which should auto start would not kept getting a general fault error would not start and the recording service had like 6 tuners listed all empty. I only have one tuner.
The error details said something about system.xml so I looked at my config.xml because config would not come up either. So I opened the config.xml and it was one line of symbols. I renamed the file and restarted GBPVR and it created a new one minus some of my settings which was not to bad it kept all of the other information just a few check boxes and such had to be redone. All is well now just wanted to help out anyone else. I am running the weather plugin so it is possible that it was updating when I restarted it.

Moral of the story is when you get your system running how you like it zip up the devnz directory and tuck it away had I done this I could have just overwriten the xml file and been back on track in a reboot.

[sub]

I think you missed the moral of the story, which is actually 'fix your machine so it doesnt hang regularly, since random reboots or flicking the power switch will eventually lead to data loss'.

[divinehammer]

Nah, looked for the problems never was able to find out what caused the hangs. Even with forum support could not find out the source my idea of the source of random hangs seems to be that comskip does not like a drive that is fragmented very much. Storing at high quality on a smallish drive seems to cause havoc. Either way GBPVR really should not corrupt the config.xml file as it should only be read on opening of GB right. So a reboot should not corrupt the config file correct? data is already lost at the time of the hang as recordings just fail.

[sub]

Either way GBPVR really should not corrupt the config.xml file as it should only be read on opening of GB right. So a reboot should not corrupt the config file correct?

GBPVR.exe only opens the file for read access, but having reboots or flicking the power switch can cause unpretictable data loss or corruption. On this one case it was config.xml, but it could have just as likely been some important system file leaving your machine unbootable - I've seen it before myself.

A reboot or unexpected power off are evil, and should really be avoided if you can.

[windsorl]

I have experienced the same problem several times. The PC becomes completely unresponsive and must be hard reset. After rebooting, the config.xml file is corrupt. I've noticed no other side effects. This has only happened to me when I was recording one program while simultaneously viewing a previously recorded program thru an MVP. I have 99.12 installed on my system. I will defrag my hard drive as you suggest to see if that has any effect on this problem.