|
SageTV Beta Test Software Discussion related to BETA Releases of the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. regarding SageTV Beta Releases should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Why Would Reinstalling 7.0.22 RC6 Fix Problems?
I've been wrestling with a series of system lockups, where I have to cycle the system power in order to get it functioning again. During the lockup the mouse pointer is unresponsive, keyboard input is ignored, the display is frozen and the system hard disk is being continually accessed, based on the fact that the drive LED is glowing steady. The lockups appear to be associated with accessing Sage from an HD200.
I tried a lot of different things to fix the problem, including downrevving to 7.0.21 (which I don't recall having the same problems when I was using it). I also did a disk check on all the disks (I get nervous when I have to hard crash the power on a system ). The only thing that seemed to work -- meaning the system hasn't locked up yet, and I can access Sage from an HD200 -- was to uninstall Sage and then reinstall it. I've seen recommendations on this forum in the past about that sometimes being a good thing to do. But I'm curious as to why it should be helpful, and would appreciate any technical perspective that folks would like to share on the subject. p.s. I do wonder if maybe this isn't a "wrong version of Java" issue. A long time ago I remember that being an issue with a particular version of Sage. And Java, in my experience, is very difficult to keep "frozen" at a particular rev level. Does uninstalling and reinstalling Sage force Java to a particular rev level? Unfortunately I neglected to note which version of Java was running before I uninstalled Sage, so I can't tell based on my experience today. |
#2
|
||||
|
||||
Instead of reloading the application, Rename the sage properties file with the application stopped. You also need to get rid of the backup properties file. Restart the application and let sage regenerate it from scratch. You will have to set tuners, channel guides back up.. But this is a quick way to isolate issues. You will still have your original properties file that can be put back in place if the new properties file doesn't resolve the issue. If the system runs smoothly after this, add your customizations back and get rid of that old properties file.
__________________
Serv:ECS H61H2-T1 ITX I7 3770S CPU@3.1GHZ 8G Ram WIN1064 HDPVR, HD Homerun|network encoder Unraid Server:B75MU3B I5-3550 CPU@3.30GHz 9TB 16G Ram|Network HDPVR encoder:Win10 VM 8G Ram with Processor passthrough. Directv Http tuning to Genie, exemultitunplugin to Genie client. Http scheduled task bat file to defeat screensaver on Genie. Usb uirt scheduled task bat file to defeat screensaver on Genie client. Clients Android TV, Samsung TAB A |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
FIX for some MVP problems | Jabroni | SageTV Media Extender | 4 | 04-17-2007 09:20 AM |
Nividia driver problems and fix | garyellis | Hardware Support | 2 | 10-17-2006 03:00 PM |
2.1 RC6 to 2.1 Release | srothwell | SageTV Software | 2 | 11-03-2004 10:47 PM |
Reinstalling server | Llamas | SageTV Beta Test Software | 1 | 05-07-2004 10:46 AM |
VIA chipset latency fix (fixes some h/w problems) | laurenglenn | SageTV Beta Test Software | 0 | 04-08-2003 04:19 PM |