Posts by cazuela

just browsed around,, most seem to be a sim problem suggesting you open ,check/clean the sim contacts and start all over again...

menu button>plugins>blindscan ... its the last on the list ...my list is a little longer and comes at the very bottom of the list ;)

might not be of any help but worth a read:http://linuxsat-support.com/cc…ng-cccam-possibility.html

try this: leave it in common interface for about 6 mins(more than the 5 mins) on an unsubscribed ppv channel and see if it kicks in/starts up ....

I read somewhere about HD probs on thor..the searchbar is your friend ;)
just a thought :: ¿ are you sure you are in inside the footprint of these channels ?' I certainly can´t from the northern Spain..

as for installation of CCcam ,check this post + pictures to give you an idea : http://linuxsat-support.com/cc…y-terminology-basics.html
CCcam.cfg ---> / var / etc chmod 644
CCcam.bin ---> / var / bin -----> this is the binary(like the .exe in windows) this should be set to chmod(attributes) 755 otherwise CCcam wont start up.
CCcam_emu.sh ---> / var / script -----> This is the script file(like the .Bat in msdos). This file has to have chmod 755. Inside it should contain the route of hte file.bin of the version we are trying to start,(for example 2.1.4).
always make a backup of the CCcam.cfg file independently before/after adding/eliminating peers just as a good practice,it doesnt take more than a click of a mouse´s button ;)

Chameleon just didn´t do itself justice......
sbox + Cccam is the "norm" here in Spain , although many insist on continuing with mbox/gbox as there are n´t as many bugs as E1 CCcam....
Oscam is quite taboo in many forums as it is conseidered to leave itself wide open to all sorts of attacks..this is the general consensus..
the saying : where there is a will there is a way could also be interpreted as while there is a market there will be marketing ;)
last word : enjoy it while it´s here and now in which ever shape or form it presents itself ;)

@ Ratius -- make a personal backup of what you have at the moment.
Then go try another image,,,this is twofold,, you will be able to compare and discover what it is you really like/dislike(advantages/disadvantages) and also get that "confidence" that you mentioned you lack in another post!!
We´ll all get there together ;)
Although this poll was started pre -UNO/ULTIMO I think it is relevant for us UNO users too !!

somewhere,someday,somehow....

seems to be the "norm"...
I just found this info from a duo user( javier007 ):
scan start frequency 0950000000 = should be frequency 9500 and so if the feed is 12300 for example then it would be=1230000000

scan start symbolrate 0002000000=2000 so if the feed was sr 6100 it would be=0006100000 and if it is sr 14400 it would be 0014400000
If time permits I´m going to give it a try the weekend ..
lets know your results ;)

In both examples you can see that a switch is used for manual ON/off if the need arises thats all ;)
Glad you got it sorted either ways ;)

nowhere like home ;)

they´ve probably changed PIDs ,you need to update the settings like I stated in previous post as I thought that was your intial problem ;)

- Support for USB-Inputdevices like Keyboard/Mouse for several applications which support it, like Webbrowser, external IR-Receiver, (untested!)
found this for the vti image: vti-solo-image-v0.1-01072010_usb(check the date, lol)
havent found anything for BH yet...still looking ;)

For a correct setup follow these posts : http://linuxsat-support.com/ca…7275-lost-connection.html , there are all the links, please.
Otherwise use the searchbar above right corner and you will find just about everything before you ask as it has already been answered.
Something else to help you : http://linuxsat-support.com/cc…ogy-basics.html#post26704

When we start to investigate CCcam we get lost with doubts:

. What are these files?
. Where do I put these files in my Dream ?

These are the general routes( paths) for Enigma1

CCcam.cfg ---> / var / etc ----->Configuration file ,where we add servers and clients (Clines/Flines/Nlines,etc) and additional configurations like open port to server , listen port, sid assign, etc.

CCcam.bin ---> / var / bin -----> this is the binary(like the .exe in windows) this should be set to chmod(attributes) 755 otherwise CCcam wont start up.

CCcam_emu.sh ---> / var / script -----> This is the script file(like the .Bat in msdos). This file has to have chmod 755. Inside it should contain the route of hte file.bin of the version we are trying to start,(for example 2.1.4).

CCcam.prio ---> / var / etc -----> This file you can configure which cards to give priority or ignore.

CCcam.channelinfo ---> / var / etc -----> This file is to view through webinfo the name of the channel rather than just see the SID.

CCcam.providers ---> / var / etc -----> This file is to view through webinfo the name of the providor and the encryption instead of the CAID

SoftCam.Keys ---> / var / keys -----> This file is where you would put ,if any, package of "keys" to open channels( there are few nowadays)

AutoRoll.Keys ---> / var / keys ---->This file is where you would have the AU( auto update) providor keys to automatically update.

Constant.cw ---> / var / keys ----> This is the file which woul have the providor keys manually introduced .

Other files that we could create to get information of CCcam.

Warnings.txt --- / tmp ----> This is where you would find the intrusion /attack attempts to CCcam without your permission.This is only applicable if you previously had the line in your CCcam.cfg.**** LOG WARNINGS: / tmp / **** warnings.txt , be careful with this file that it doesnt fill up with warnings and leave the Dream without enough memory to carry on working correctly.

Ecm.info ---> / tmp ----> This file shows the information about the encrytion of hte channel that we are viewing.

A hop is the distance away from a card.
Hop one = 1 step away, ie: card server, receiver.
hop 2 = 2 steps away, card server, server, receiver.
Hop 3 = card server, server, server , receiver.
And on and on.
Anything above hop 4/5 is virtually unwatchable as the time it takes for ecm to reach you would surpass the ecm change (on 0963 anyway)

If there is anything you would like to add to this "dictionary" ,please do so as this is only the basics ;)

rigrat1 -read these posts -although its for a gemini image ,the setup is basically the same: http://linuxsat-support.com/en…g-cccam-gemini-image.html
you know that you can use either dreambox edit or dreamset to put an up to date channels settings list or simply scan the sat.
to install CCcam -download the version you want to use and ftp it to the appropiate folders for example : http://linuxsat-support.com/cc…ls/386-cccam-2-1-4-a.html or the e1-CCcam_2.1.4_100204.tar.gz‎ both are also in the posts.
then add the lines needed etc in the .cfg. If its only going to be used as client then no need to open ports.

FTP flashExpander into tmp(using DCC for example), then install it through the remote(yellow-green on the UNO), then reboot , as Master G has explained ,,any plugins that you wish to install will be installed onto the usb rather than the usr/directory in the box which means it will use the usb to store plugins ,etc to save space +ram on the box.
FlashExpander does all the necessary organising automatically, you don´t need to do anything except the above to install it.

I had to as i just couldnt find the root of the problem with mutliquick button and thought it might have been the backup somehow being corrupted.
when you do get the time and you find any problems -post them and we´ll get there together ;)
the most time consuming is the so-many-reboots....
the rest is practice..
caz

13/09/2011 Germany

Unknowns have hacked the database of online stores "*** Line" were offered on the Card-sharing packages on the illegal reception of pay-TV channels. The shop is now no longer accessible.
Ad

When card-sharing an activated subscription card is used in parallel in order to allow pay-TV services on multiple digital TV receivers. The clients (receivers) get there - in simple terms - the need for encryption control word from a central server, where you put the subscription card. To communicate with the server must be running on the receivers, a special software (called Soft-CAM).

Card sharing is usually operated in a manageable group of people, but there are also some commercial vendors that offer this "service" fee. The necessary data is delivered over the Internet to the receiver. The attacked service had offered different packages, which were priced between 50 and 100 euros per year.

In H this e-mail explaining the alleged hacker, security gaps that the software used by the store owner osCommerce 2.2 RC2 had exploited to run PHP code on an unsecured upload feature in the admin panel to upload and execute. This has succeeded to create a new administrator account and save all data in the shops. Moreover, when analyzing the vhost accounts had noticed that all access to the sharing system without safety precautions could be achieved via HTTP. Among these data are the DynDNS hostnames and passwords for all customers who need server software to connect with the clients.

The imaged data were stored in a file hosting services. Actually contain the relevant files including real names, addresses, email addresses and names from DynDNS accounts of alleged customers from Germany and neighboring countries. Also can read about how the benefits were paid. As expected, in many records, but also fantasy information.

According to the alleged hacker of the operator of the shop as well as hosting a busy (and now also no longer accessible) boards had occurred. This should have been mainly the development of "open source CAM" (OSCam) driven, which can be used for card sharing. In the attack went according to the authors of the mail to H, therefore, primarily concerned that the project OSCam of the Board "adopted and thus retains its good reputation." In addition, you no longer want to have to tolerate that the operator "earned at the expense of our favorite television a fortune." The mail ends with an indirect threat against further commercial card-sharing providers.