I don't know if this is known or not, or just common sense to most folks. I'm not an XML guy, so maybe this is a known xml thing. Anyhow... on with the show:
Directory names that have "~" in them will cause GBPVR to crash if:
1) This directory is explicitly defined in GBPVR's config.
2) And you access the function related to that folder in the gui, or you try to run the config program.
I got pages of errors that made it look like a .NET issue.
For example, you define a video library directory that points to c:\Videos\~hidef
This will cause it to crash.
The reason is that "~" is used in the xml stringto separate the directory name you defined from the path to that directory.
The fix is:
Remove the ~ from the directory name.
Make a back up of your config.xml in the gbpvr directory.
Edit the config.xml
Search for the directory name
Remove the ~ from the directory name in the string.
Save config.xml
Restart the gbpvr service.
Its possible that the ~ causes additional corruption in the string. My string had additional corruption with ~
s in it. If thats the case, you might want to just delete the xml string leaving the tag intact and restart the service and redefine it using the config gui.
Directory names that have "~" in them will cause GBPVR to crash if:
1) This directory is explicitly defined in GBPVR's config.
2) And you access the function related to that folder in the gui, or you try to run the config program.
I got pages of errors that made it look like a .NET issue.
For example, you define a video library directory that points to c:\Videos\~hidef
This will cause it to crash.
The reason is that "~" is used in the xml stringto separate the directory name you defined from the path to that directory.
The fix is:
Remove the ~ from the directory name.
Make a back up of your config.xml in the gbpvr directory.
Edit the config.xml
Search for the directory name
Remove the ~ from the directory name in the string.
Save config.xml
Restart the gbpvr service.
Its possible that the ~ causes additional corruption in the string. My string had additional corruption with ~
s in it. If thats the case, you might want to just delete the xml string leaving the tag intact and restart the service and redefine it using the config gui.