Windows8 Problem

[vhurst]

sflamm, I had been working with Sean (Stuckless) directly to debug the problem. My last message to him was:

Sean,

Well, I stopped the sage service, then found in sage.properties:

STV=C\:\\Program Files (x86)\\SageTV\\SageTV\\STVs\\SageTV7\\Phoenix.xml

And changed it to:

STV=C\:\\Program Files (x86)\\SageTV\\SageTV\\STVs\\SageTV7\\SageTV7.xml

Then found:

debug_logging=false

and changed it to:

debug_logging=true

Then, deleted the files in the SageTV\logs folder, which is what I had sent last time.

Restarted the server, and from my HD-300 did the change to Phoenix.xml.

It worked this time. So, I don’t know what to tell you. After the half dozen other failed attempts, I don’t know what changed. Oh, and I found the sagetv_0.txt file too.

The logs are attached, but there’s probably nothing worth looking at.

So ther you have it. After that, Phoenix just worked.

[vhurst]

Not that this fix I found belongs in this thread, but I had mentioned the problem with the lack of Server 2012 BDA Support. I found the fix! Works great!

http://www.tenniswood.co.uk/technolo...s-server-2012/

Now to finish dialing in this does-it-all server!

[sflamm]

vhurst,

I followed the exact same steps previously - that works to load Phoenix initially. The problem is that if you stop/shutdown the client (HD300 or software client) then it will fail again - hanging on startup.

It is not practical to have to stop/start the service, change config files and the reload the Phoenix STV everytime especially if you have multiple HD300 and software clients as I do.


That is unfortunately not a fix...the problem is still there. Only the 409 clients works across restart.

[sflamm]

Any up date on the fix to this problem?