Umm - Why is Sage 6.1.8 looking for the wiz file in the beta dir?

[tawpgk]

Since I was confused in still seeing the beta directory i copied out the old program files directory to a backup location.

Uninstalled sage and removed the remaining files left out in the sage directory. Installed fresh 6.1.8 and copied the wiz and propertied files back into the SageTV\SageTV directory.

When i started sage it went into the initial configuration wizard and i was surprised. After i ran, it created a new wiz file in the beta directory. Very odd....

So i copied my backup into the beta directory SageTV\beta\SageTV and it worked ok. But it still begs the question why is the production release running out of the beta directory.

Are there remnants in the registry that are pointing it in the wrong places?

I will add it in the bugs area as well.

Tom

[Opus4]

This is most likely not a bug; it is related to how you are doing your installations. The paths to wiz.bin & some other files are stored in the properties files, so when you copy those files, you copy all those old settings. If you install to a different location, then copy in your properties files from the previous location, you can get all kinds of strange things happening.

There is no need to uninstall & delete dirs when doing an upgrade -- just install on top of the previous version. You can make a complete backup of the current install before upgrading & that is covered here.

- Andy

[tawpgk]

Well that is what I did originally, but everything still stayed in the beta directory which is why i was confused.

The new install did not pick up the old properties file i believe since it ran through a fresh configuration.

I will look at the properties files. thanks.

[tawpgk]

I surmise that when I originally loaded out the beta, I told it to load to sagetv\beta figuring that i would maintain a uniqueness between the beta and production versions of the product.