Problems with Cinergy Hybrid T USB XS FM

Anzeige

Has anyone had problems with the Cinergy Hybrid T USB XS FM using Vista?
Every time I start Home Cinema following a Hibernate, it reports "Bad Signal". The solution is to restart Home Cinema.
Every time (almost) that I start Home Cinema from a Windows Shutdown, Home Cinema crashes. It will not display anything and refuses to be shut-down from Task Manager. I often have to re-start the PC may times before Home Cinema will respond.

Does anyone know how I can fix this. It is very frustrating.

Computer details:
Toshiba P200 laptop
2GB RAM
Vista 32 Business
Cinergy Hybrid T USB XS FM
TerraTec Home Cinema: 5.78.00.557
Remote Control Editor: 4.94.00.366
Cut!: 0.05.47.90

Dlcllib.dll (tvtv): Dlcllib.dll not found
EPG database: TerraTec EPG Database Version 2.0 (2007/03/05)
TT_Vtx.ax: 4.65.00.329
TTDvrSubtitle.ax: 1.00.00.01

Windows: Windows Vista Professional Service Pack 1 (Build 6001)
Administrator rights: Yes
DirectX: 10.0
Internet Explorer: 7.0.6001.18000

(Sorry this is in English. I don't speak German)

 

AW: Problems with Cinergy Hybrid T USB XS FM

Could you also get the stick running after hibernate, if you disconnect it from USB beofre starting THC?

Are you already using the latest driver for the Cinergy Hybird T USB XS FM?

 

AW: Problems with Cinergy Hybrid T USB XS FM

I will try this. Are there any instructions for installing this driver?

So far it seems to be working today (another BSOD on startup though.... Don't know whether this is just normal Vista)

Update (15 minutes later): No improvement. Home Cinema would not start and I had to restart the PC to kill the program. It seems to hang at the same place each time. The control panel and the TV window are shown but Windows says the program is not responding.
Even with debug level set to 3 there are lots of errors reported in the log files. Is this expected?

 

AW: Problems with Cinergy Hybrid T USB XS FM

No, there are no specific installation instructions. You just need to point to the extracted drivers directory when Windows recognized the device.

Just do some more tests and let us know, if it works now.