progdvb.com

Hello,
Many thanks for ProgDVB - the best program to watch sat tv.
But since I have change my old comp (AGP) to new one (PCI-e) I have big problem to run it because of BSOD. I have already try drivers 2.19c-pcie and 219h-pcie - both hangs up my comp. I have checked two mobo's A8N32-deluxe and Asus rog commando, VGA= Asus 7600GT with WHQL last drivers.
When I start device in soft mode its work perfect.
Do someone has something like me or I'm alone? any ideas how to solve this?
regards,

try the 2.19 without ´c´ or ´h´ ...

i've got A8N32-deluxe + Hauppauge DVBs
and A8N32-deluxe+ Hauppauge Nexus
At WinXP i don't have problems (i had used 2.19, now ive got 2.19h-pcie)
At Vista I have some problems, usually i got some BSOD, but not always(2.19h-pcie) with 2.19 doent works"BSOD", both drivers works ok with Radio channels.
Do you have the latest Bios for your modo?
Check your codecs, use the latest version.
And latest drivers for mobo and graphic card.

Hello,
I do not know hauppage dvbs card but I my problem is with hardware mpeg not soft - softmode working ok so there is no codecs needed in hard mode.
I have find solution and card starting ok:

when you instal your TT 1.3 you will be asked about drivers:
->Instal from a list of specific location->Do not search. I will choose the driver to instal ->then we have to instal "Technotrend TT-PCLine premium S (KS).

All BSOD i have on on Technotrend TT-PCLine premium S (version ......)

I do not know what is the diferent between S and KS - do not ask me.

Now new problem - there is no syncing audio and video. - got any ideas?

regards,

As told here several times already, the KD drivers are those, that are made specially (and only) for PCI-e boards, and they do force software decoding for the PC screen picture, though TV out will still be active and in HW mode.
This means, when using KS drivers, you won't be able to control codecs in ProgDVB, if started in HW mode, though they are in use even then.
To set up codecs, start in SW mode, or use the original software first, to access codec properties.

No idea on your BSOD, as you did not post details.
But that may be codec / renderer related, for example.

Precision rules, full details are mandatory...

Post details. Please

...some BSOD

What kind of?
Quote it's message, else no way to help...

And before, use the search function, here and on the old forums as well, on it's main description.
Several types of BSOD have already been discussed.