Hardware Support - Skystar 2 Black Screen Syndrome...

[DocPookias]

I’ve just acquired a DVB-S Skystar2 rev2.6 and am looking for some advice. I installed the driver from the CD, it was version 3.3.3.0 and quickly upgraded it to BDA driver 4.4.0.0. Here’s the problem I am having… I noticed when initially opening DD for the 1st time, the some of the time the channels do not come in right away, you simply get a black screen. You need to re-click on a channel to get picture. I've used a Twinhan 1020a with WDM drivers in the past and never had this problem with the same multiswitch and diseqc setup. I was informed that the Skystar2 had a much better tuner and had better performance, but this is not what I am seeing. The problem really lies when recording programs, it's hit or miss because if the channel does not immediately come in you end up recording a black screen. Is there a fix to my problem? I even tried using the drive 3.3.30 from the CD & the newest driver 4.4.1.0 from the Technisat website with the same results. Can someone help me to fix this problem?

[rel]

1) try to use latest WDM driver
2) try the following options:
preferences->performance->"Always force to resend diseqc commands"
preferences->performance->"Diseqc repeat count"
preferences->performance->"Delay after diseqc switching"


I recommend following driver and use of "B2C2 Direct" device in DVB Dream

[DocPookias]

There are a lot of files in the download. Do I need to install all of them? Can you give me some instructions? Is this driver just for DD or will it work with other applications as well?

[rel]

it is a driver, not a DD specific file or files.


just remove your current ss2 driver (my computer->proporties->device manager) and install this one specifiy the path where you extracted the content of the compressed file.

[jerryt]

When you select update driver (in device manager) browse to either "Oemsetup.inf" or "Skynet.sys" and then OK, OK til driver updates.

[DocPookias]

I was on the DVBN site I from what I was reading this problem may be an *****tion 2.0.0.6 problem? Am I the only one experiencing this problem? Has anyone tried V***plug to see if this eliminates the problem?