Black Screen After Upgrading to Release Version 2.0

[comprat]

I just went from RC3 to the release version of SageTV 2.0. When I launch Sage, the splash screen pops up as normal, and then all I get is a black window where the menu would appear. There are no buttons... nothing. I uninstalled, then reinstalled. Same thing, a black screen. I then uninstalled, then reinstalled RC3, and everything works great. Any suggestions?

Thanks!
comprat

[falchulk]

When you uninsall, are you renaming the frey directory? If not, you are just using the same settings over and over when you reinstall.

[comprat]

Actually, you should not have to reinstall into a different directory, but I did install to a completely new directory anyway. Here's exactly what I did:

1) Uninstall RC3
2) Install SageTV release version into new directory
3) Copy over my properties, Wiz, and Wiz.bak files from RC3 install to the new directory
4) Tried to start... black screen
5) Unistalled, then did steps 1-3 again after a reboot. Still a black screen.
6) Uninstalled again
7) Installed RC3
8) Copied over properties, Wiz, Wiz.bak from previous RC3 install
9) Started SageTV... everything is fine.

Don't know what else to do. If RC3 is working fine, the release should work as well. It doesn't seem like anyone else is having this problem. Any other suggestions would be appreciative.

Thanks!
comprat

[justme]

Comprat said:but I did install to a completely new directory anyway.

If I followed everything you did, which I'm not sure of right now(its' late). I'd guess your problem has to due with SageTV trying to find the STV and it's acompaning images. Does an uninstall remove the STV and images from the original dir? If so when you install to a different dir it will write the subdir for the STV and images there. Sage will then put a setting in the properties file saying where to look for the STV. If you are overwrittting the new properties file with your old one, then the setting will point to the wrong STV and images. Try looking at these values(mine are in default dir) in your sage.properties file. Make sure they point to the correct dir(STV) for that version of Sage.

last_stv_browse_dir=C\:\\Program Files\\Frey Technologies\\SageTV

wizard/widget_db_file=C\:\\Program Files\\Frey Technologies\\SageTV\\STVs\\OriginalV2\\OriginalV2.stv

[falchulk]

comprat, trust me, I am pretty good at this, if you have a problem YOU SHOULD DO THE FOLLOWING first:

1. delete sage.propertiesbackup
2. rename sage.properties
3. Start sage (this will likely solve the issue)
If you get video, its something in the sage.properties.

If you dont, do this:
1. copy Frey dir somewhere else.
2. UnIninstall sage.
3. Delete frey directory.
4. Install sage.
5. start sage (DO NOT COPY YOUR files yet)
If you get video, close sage and copy your wiz.bin over.
1. Start sage see if you get video.
If everything is still ok, copy the sage.properties over.
start sage

Also, nowhere in the initial message did I ask you to install it to a diffrent directory. I said you need to delete the frey dir after the uninstall. The uninstall does not remove the files that are likely casuing the problem. reinstallinmg into the same dir just gives you the same problem because it KEEPS those files.

[comprat]

Thanks to all for replying! justme, your tip on checking the directory path in the properties folder did the trick. It was pointing to my old directory where the STV files were. I created a seperate directory while I was beta testing and didn't think about the dependencies that might exist in the properties file. I corrected the path and all is well now.

Version 2.0 is great! I have been using it now since the first public beta and love it! The excellent help in these forums is just the icing on the cake.

Thanks again!
comprat

[falchulk]

comprat, just for future reference, most problems are casued by the sage.propertis file. Letting sage rebuild it and then redoing your settings is the easiest way of fixing it. In most cses, you dont even need to know what the cause was. The whole process should take less then 15 minutes.

[justme]

comprat,
Glad to hear it. It(the path) just seemed to stick out, to me. I guess this comes from having multiple installs and going thru every beta since 1.3.x something.

True enough falchulk, but that's no fun. Personally I love to know exactly what's going on(good or bad) and why. I guess, I'm just a tinkerer.

Anyway, alls well that ends well.

[Llamas]

I went through this same process a couple of days ago with a client. I moved my client to a new machine. The old machine had f:\program files\... and the new machine c:\program files\...

I had to let the client regenerate the sagetvclient.properties file, then copy and paste in my remote control mappings to the new file. I probably could have edited the paths in the properties file.

Anyway, this same thing can happen on a client, too, and for different reasons.

--Mike