TV-Server Version: 1.0
MediaPortal Version: 1.0
Windows Version: Windows XP Prof SP3
CPU Type: AMD
HDD: 80GB Boot & 500GB Storage
1. TV Card: Hauppage HVR-2200
Hi,
I am presently experiencing two problems:
1) After restarting the PC (manually or after power failure), the MP Client starts-up, but the TV Service does not automatically start. When running TV Server Configuration, I get the message dialog "TV Server not running, Start it now?". Checking "Services and Applications", the TV Service is set to start automatically. I then have to either confirm the dialog or start the service from Windows Services Manager.
2) When either scheduling a recording or starting one manually, the TV guide as well as scheduled recordings shows the desired scheduled setting (in red). However, the recordings never start (no record symbol on main screen) and no file results. Also, after the elapsed time, the scheduled recordings are still shown in the list.
I never experienced these issues prior to updrading to v1.0 (from 1.0 RC4 and 3). Logs are attached.
Best Regards
Rich
MediaPortal Version: 1.0
Windows Version: Windows XP Prof SP3
CPU Type: AMD
HDD: 80GB Boot & 500GB Storage
1. TV Card: Hauppage HVR-2200
Hi,
I am presently experiencing two problems:
1) After restarting the PC (manually or after power failure), the MP Client starts-up, but the TV Service does not automatically start. When running TV Server Configuration, I get the message dialog "TV Server not running, Start it now?". Checking "Services and Applications", the TV Service is set to start automatically. I then have to either confirm the dialog or start the service from Windows Services Manager.
2) When either scheduling a recording or starting one manually, the TV guide as well as scheduled recordings shows the desired scheduled setting (in red). However, the recordings never start (no record symbol on main screen) and no file results. Also, after the elapsed time, the scheduled recordings are still shown in the list.
I never experienced these issues prior to updrading to v1.0 (from 1.0 RC4 and 3). Logs are attached.
Best Regards
Rich