Hi,
looks like I messed up my VompClient. When I start it, it connects with the server, reads the settings and terminates.
Beside upgrading PowerDVD from Version 5 to 6, I've played kind of with the settings and it looks like I found one which causes the VompClient to terminate right after connecting with the vomp server. So my guess is, that the current problem has nothing to to with the PowerDVD upgrade.
Any idea where the settings get stored and how getting them back to default?
Thanks a lot,
sun
looks like I messed up my VompClient. When I start it, it connects with the server, reads the settings and terminates.
Beside upgrading PowerDVD from Version 5 to 6, I've played kind of with the settings and it looks like I found one which causes the VompClient to terminate right after connecting with the vomp server. So my guess is, that the current problem has nothing to to with the PowerDVD upgrade.
Code Select
20:12:43.000718 [debug] VConnect - Draw done
20:12:43.000718 [debug] Command - processing message 11
20:12:43.000718 [debug] Boxx - Destruct, now 2
20:12:43.000734 [debug] Boxx - Destruct, now 1
20:12:43.000734 [debug] Boxx - Construct, now 2
20:12:43.000734 [debug] Boxx - Construct, now 3
20:12:43.000734 [debug] TBBoxx - Draw
20:12:43.000734 [debug] Command - Phew, no dangerous on-the-fly mode switching to do!
20:12:43.000734 [debug] Command - Load power after boot
20:12:43.000750 [info] Command - Config says Power After Boot = Off
20:12:43.000750 [debug] Boxx - Destruct, now 2
20:12:43.000750 [debug] Boxx - Destruct, now 1
20:12:43.000765 [debug] TCP - Have closed
20:12:43.000765 [debug] VDR - Disconnect
20:12:45.000156 [debug] UDP - Wait for packet
20:12:45.000156 [debug] Command - processing message 28
20:12:45.000171 [notice] Core - BoxStack module shut down
20:12:45.000171 [notice] Core - Command module shut down
20:12:45.000171 [debug] VDR - Disconnect
Any idea where the settings get stored and how getting them back to default?
Thanks a lot,
sun