Sage Crashes, reboots, Sage = black screen

AWS · #1 01-09-2005, 04:37 PM

Once and a while Sage crashes (dunno why yet) and then I reboot the computer. When I reload Sage or if I let Sage re-load itself, all I see is a black screen except my mouse pointer is white and I can move it around. I can use Windows like normal, but just that Sage is nothing but a black screen. If I use Sage in a window mode, Sage is still all black. Any ideas why and what's up?

I've tried re-installing Sage via the Sage installer and select the "Repair" method, but it still shows nothing but black.

band80 · #2 01-09-2005, 06:48 PM

bounce

band80 · #3 01-09-2005, 06:49 PM

I meant bump... what the hell is wrong with me?

Opus4 · #4 01-09-2005, 09:55 PM

Are your video card drivers up to date? Did you enable 3D Acceleration in Detailed Setup -> Advanced? If so, try disabling it. If you can't see anything in SageTV, exit & edit the properties file. If I recall correctly, you would set ui/accelerated_rendering=false.

If you do a reinstall to resolve an error, remember to remove the properties file & its back first, or else any errors may remain. You could always try removing the properties files in the first place w/o even reinstalling.

- Andy

AWS · #5 01-09-2005, 10:46 PM

Ok, I've set ui/accelerated_rendering=false and I still have the same error. I'm going to back up everything and "upgrade" to 2.2.2 BETA. I don't like BETA software but I'm getting desperate since 24 is on (recorded). Sage looks like it's doing it's job by recording stuff but it's just not displaying (I'm seeing the HDD LED activate and files are being written to my HTPC HDD.

AWS · #6 01-09-2005, 10:52 PM

Ok, I followed your advise Opus4 and backed up the properties files, deleted them both then I did a reboot...and now Sage is working. I didn't end up installing the BETA after all. What is strange, though, is that I manually set the Sage service to NOT autoload on boot up, but it did still. But at least I have my Sage program back so I can see it.

Opus4 · #7 01-09-2005, 11:03 PM

Quote:

Originally Posted by AWS

Ok, I followed your advise Opus4 and backed up the properties files, deleted them both then I did a reboot...and now Sage is working.

Great.

I think that sometimes a crash can cause something to get corrupted in the properties file. I don't think I've had that happen (of course now that I said that...), but I keep backups anyway.

Quote:

What is strange, though, is that I manually set the Sage service to NOT autoload on boot up, but it did still.

How did you tell the service not to load at boot up? Inside SageTV or by using services.msc & setting it to "manual"? I'm asking because SageTV itself can't affect how the service is loaded.

- Andy

AWS · #8 01-09-2005, 11:17 PM

I told Sage to manually load via the Sage program, didn't work, so I went under the Windows Services window. Then I tried loading the Cayars16 STV and it didn't do anything...so then I tried loading the Original 2.1 STV and it went back to black. Ugh. I'm going to try the BETA. I did a full directory backup. If all else fails, like I suspect it might, I'll save the Wiz and other file needed and do full uninstall then reinstall and go from there.

AWS · #9 01-09-2005, 11:45 PM

Well I'm trying the BETA Sage now and everything seems to be working fine once again - even with the the Cayars16 STV. I really dont think there is a problem with the ebhanced STV but with some setting within my corrupted (previous) version of Sage itself. If I have problems again I'll post them.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)