Clarke Tech Softcam Question

[Josh]

I'll think about that one... I don't use the softcam part of the box these days, except for back up when Diablo doesn't work for a channel and the other ones does, but these days that isn't the case. With diablo opening up more than the softcam solution.

The question is do other CT5000 owners get anything from their softcam ?.

Slight change of subject from another board:

>>
Internal naming 205p for clarketech is similar to 25p for Dr. HD F16, you can patch it (using coolsat 8000 tools) and load into clarketech, but it is very problematic itself, since very early alpha stage. Currently firmwares for all of these recievers (For your reference, Clarketech HD5000C+, Dr.HD F16, Technomate TM6900+ Combo, Diamond 9000 all are manufactured by HUB TECH - A korean company) being done by single group of programers in Korea, but one of their testing center (they simply can't check all european sats in corea) is located in Belarus.
<<

After that moderator got uptight:

>>
we don`t want Questions or other things about Dr.HD Firmware in the Threads from the Clarke-Tech Receiver. I hope you understand this.
<<

Perhaps that's a rip off from the mother company HUB TECH.

Still interesting whilst I thought it was German programmers lashing this stuff up it seems to come out of Korea.

[parad0x_i]

Nine times out of ten it is the box manufacturers who do the patches and then pass them on to the retailers..

So most of those patch 'heros' don't write anything themselves and are just passing-on what they've been given..

[Josh]

Thanks... I was thinking that myself especially when the official releases contain the bugs of the "patched" software ie. the official release gets the bugs of the patches before they were ever released as official. But interesting that the development is back in Korea although the Belarus dimension could be interesting. Perhaps in the end the distributor doesn't have much control over the quality of what gets put in the code, linked to my frustration that they stopped supporting the drive that I used for about 18 months and you had to be in the know, to know which drive to buy. That seems to be fixed now with code that seems to be more stable.