TV-Server Version:
MediaPortal Version: 1.0
MediaPortal Skin:
Windows Version: XP Pro sp3
CPU Type: AM2 X2 5200
HDD: Western Digital 320
Memory: 2gig DDR2 667
Motherboard: Gigabyte M55S-S3v1.1
Video Card: EliteGroup 8600GT 256meg DDR2
Video Card Driver:
Sound Card: onboard
Sound Card AC3:
Sound Card Driver:
1. TV Card: Winfast DTV2000H
1. TV Card Type: DVB-T and Analogue
1. TV Card Driver: 4.0.112.3223
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: MPV
MPEG2 Audio Codec: MPA
h.264 Video Codec: ffdshow
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply: Thermaltake 430
Remote:
TV:
TV - HTPC Connection:
I've just installed v1.0 and it all seems to run fine, bar one thing. The TVService service isn't starting when Windows boots up. The service is listed and is set to auto.
If I run MP (the client) I get asked where the server is, but of course as the service isn't running it never finds it even if I specify it. If I run the Server config tool it asks if I want to start the TVService service. If I ok it the service starts and then everything proceeds as normal from there on in.
If I check services.msc after Windows has booted up, the TVService service is there, set to automatic, but it is not started. I haven't touched the service itself and as far as fiddling in MP goes all I've really done is scan for channels, setup the EPG config and set my weather location.
The machine has a single DTV2000H card in it and a single onboard nforce ethernet port. I changed the TV Server name in the server config tool, so it showed the fixed IP of this PC rather than its 'name', hoping that may help but it didn't. (I can't figure out how you change that back either)
This is all only on a cold boot, or reboot. After resuming from S3, or logging out and back in, the TVService seems to recover normally (so far anyway).
Apologies for making what must be a stupid mistake. Any clues on what's going on here?
Server logs in case it helps. View attachment 31810
MediaPortal Version: 1.0
MediaPortal Skin:
Windows Version: XP Pro sp3
CPU Type: AM2 X2 5200
HDD: Western Digital 320
Memory: 2gig DDR2 667
Motherboard: Gigabyte M55S-S3v1.1
Video Card: EliteGroup 8600GT 256meg DDR2
Video Card Driver:
Sound Card: onboard
Sound Card AC3:
Sound Card Driver:
1. TV Card: Winfast DTV2000H
1. TV Card Type: DVB-T and Analogue
1. TV Card Driver: 4.0.112.3223
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: MPV
MPEG2 Audio Codec: MPA
h.264 Video Codec: ffdshow
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply: Thermaltake 430
Remote:
TV:
TV - HTPC Connection:
I've just installed v1.0 and it all seems to run fine, bar one thing. The TVService service isn't starting when Windows boots up. The service is listed and is set to auto.
If I run MP (the client) I get asked where the server is, but of course as the service isn't running it never finds it even if I specify it. If I run the Server config tool it asks if I want to start the TVService service. If I ok it the service starts and then everything proceeds as normal from there on in.
If I check services.msc after Windows has booted up, the TVService service is there, set to automatic, but it is not started. I haven't touched the service itself and as far as fiddling in MP goes all I've really done is scan for channels, setup the EPG config and set my weather location.
The machine has a single DTV2000H card in it and a single onboard nforce ethernet port. I changed the TV Server name in the server config tool, so it showed the fixed IP of this PC rather than its 'name', hoping that may help but it didn't. (I can't figure out how you change that back either)
This is all only on a cold boot, or reboot. After resuming from S3, or logging out and back in, the TVService seems to recover normally (so far anyway).
Apologies for making what must be a stupid mistake. Any clues on what's going on here?
Server logs in case it helps. View attachment 31810