|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
SageTV "Program Error"
After upgrading to v2.2.7, I get an error dialog when I use my remote command for waking SageTV when asleep. After closing the dialog, operation goes 100% fine, and no other problems. I never had this problem on any previous version of Sage, and v2.2.7 is the only change. This has been bothering me weeks, since I upgraded, and now I finally made some time to play on the forum tonight.
1) Ideas on what is wrong / what I can do to 'fix' this dialog from showing up? 2) Where I can find the 'error log' that is created? Didn't see anything in Sage program directory. Maybe Sun java directory, but don't have time to hunt. Thanks in advance for the help, gang! --Program Error dialog: SageTV.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created. --Irremote.ini command: [Default] KEY_ALL_BUTTON2={run(C:\Progra~1\FreyTe~1\SageTV\SageTV.exe)} --SageTV information: program v2.2.7 Cayars STV v17 |
#2
|
||||
|
||||
Look in your Event Viewer for Appliction logs.
It could a Windows error and not an internal SageTV error. Perhaps a problem with the remote drivers?
__________________
SageTV server & client: Win 10 Pro x64, Intel DH67CF, Core i5 2405s, 8 GB ram, Intel HD 3000, 40GB SSD system, 4TB storage, 2x HD PVR component + optical audio, USB-UIRT 2 zones + remote hack, Logitech Harmony One, HDMI output to Sony receiver with native Intel bitstreaming |
#3
|
||||
|
||||
Event viewer/app logs have nothing relevant. Also don't think it's a remove driver issue, as this was working with the same base driver set w/ v2.1.10 (or whatever the previous version was). The only upgrade I did was moving to v2.2.7, and that immediately caused the problem. (Haven't had the time to update any other programs / drivers recently.)
Thanks for the idea though. Keep those cards and letters coming, gang. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|