If I I'm correct this is on a XP based OS, this is a windows bad net-framework update goggle it....
Hello!
I thought I'd give back a little. A friend of mine was having a problem with the WinTV-based multimedia computer I set up for him. Every few days he would get a .NET error while booting that related to WinTV. From that point on, WinTV would not run. It would take a wipe of WinTV and reinstall to get it working again. In the course of trying to fix this, I had him send me a copy of the error message and I was able to figure out the problem. The start of the error message:
************** Exception Text **************
System.TypeInitializationException: The type initializer for 'TVServices.Core.SystemSettings' threw an exception. ---> System.Xml.XmlException: Unexpected end of file while parsing Name has occurred. Line 191, position 31.
From research done in this forum, this means that the Settings.xml file was cut off at line 191. It turns out he had run out of drive space on C: several times, corrupting Settings.xml. This was also proven by the fact that his Settings.xml file was exactly 8192 bytes, which is exactly two 4K clusters. I sent him a copy of my Settings.xml file and after a little tweaking we got his system up and running again.
I hope this might help someone else who experiences this.
DarF
If I I'm correct this is on a XP based OS, this is a windows bad net-framework update goggle it....
It is Windows XP Pro, but the problem was simply that his C drive had 0 remaining bytes free and his Settings.xml file was trashed in the process. He had not updated .NET since the Hauppauge install and his multimedia PC has no network connection.
DarF