Ccam info problem

[Satphoenix]

Re: Ccam info problem

still the same problem over here, original cccam.cfg disappears when using cccam.info
Eaven on latest bh on vu+ duo, but not that often as with vti image.
Any idea if there is (software) solution yet to avoid the diappearing?

It sounds like the software problem: sometimes something went wrong
By the way, a known problem for a computer crash.

What cccam do you use?

If you use ver 2.30 it might be a software bug because of the permanent checking addititional cccam files.

See: http://www.satlover.eu/forum/cccam/4...tml#post264105
Post 4

A multi-usage off the cfg can cause its delete.

[digicon]

Re: Ccam info problem

still the same problem over here, original cccam.cfg disappears when using cccam.info
Eaven on latest bh on vu+ duo, but not that often as with vti image.
Any idea if there is (software) solution yet to avoid the diappearing?

Its a Bug in the original CCCam info software and will probably never be fixed due to the fact that CCcam is not supported anymore

[runmo]

Re: Ccam info problem

I use the 2.2.1, happened with 2.30 to, but if it's bug as mentioned don't think version makes difference.
Is there maybe alternative for cccam.info or fixed version? If yes you can post (not direct) link in this thread.
Sure you mention the different c-lines in the same cfg file, but don't think is good idea for channel stability and channel opening speed.

[digicon]

Re: Ccam info problem

I am not sure if there is a fixed version i know images like Vix incorporate it in the image but on blackhole its a downloadable plugin, i know putting all lines in a .cfg is a pain but if you screen out packages you dont require then it would work

[bokkie]

Re: Ccam info problem

That's what I did to solve the problem. I wanted certain lines to always open certain packages so I never run the risk of a double login.
So I just set the lines to ignore the packages I didn't want them to open, which kind of solved the problem for me.

[Satphoenix]

Re: Ccam info problem

I use the 2.2.1, happened with 2.30 to, but if it's bug as mentioned don't think version makes difference.

@runmo,

is it possible for you to downgrade to ver 2.011?
I don't have a vu+ but expect to buy one soon.
It's would be interresting if 2.011 has the same effect, because it doesn't have this permanent additional file-checking routine.

[runmo]

Re: Ccam info problem

Does anyone know other tool to switch between cfg then cccam.info. ? Still same problem with cfg file that vanishes, eaven with latest bh oe 2.0. Or maybe bug free cccam info version or trick ? It's frustrating this way. Version of cccam has no influence at all.

[bokkie]

Re: Ccam info problem

I tried to find a solution, but couldn't get it to work either.
Only solution I could suggest is maybe to use different cams.
For example I use cccam for my clines and mgcamd for my nlines.

[runmo]

Re: Ccam info problem

I have feeling that the cccam.info bug could be conflict with installed cam next to cccam, more particularly oscam. I noticed that cfg file often vanishes when using oscam and switching back to cccam. Message that cccam is started but oscam stays active as cccam.cfg can't be found, when you go into cccam.info menu the selected cfg is unchecked and when you select new cfg green screen. Then you need to install original cfg again and reboot receiver (hard reboot) to be able to use cccam again. Don't know if same problem with mgcamd. Don't eaven know if combi cam oscam/cccam and combi cfg oscam/cccam would help. Stand alone oscam or cccam work faster in my eyes.
A fast repair solution is using new menu addon. There you can backup your cccam.cfg
to hdd or usb and repair from. After repair pitty enough reboot is still needed.

Strange that this problem didn't happenend in older image versions from bh and vti.
Downgrading image version is option but don't think it's good idea to be able to use receiver in optimal way and think it also could have influence on cs to be able to open some channels.
If anyone founds solution please mention it here,thx.

[bokkie]

Re: Ccam info problem

When I had problems with this I was only using Cccam 2.2.1 and had no other cam installed.
I have only installed Mgcamd since then as a remedy to my problems.
It could be due to conflict, but it wasn't in my case as only one cam was installed.

[Satbeam]

Re: Ccam info problem

Hi all.
I have 2 clines and want to use 1 for sly uk and the other for the rest.
So I installed cccam info 1.3, made the 2 files in etc named CCcam_01.cfg and CCcam_02.cfg no problem, leaving the original cccam.cfg as is.
I put the respective clines in the folders and can switch between them no problem.
Problem is the cccam.cfg keeps getting overwritten which then throws up an error on the stb.
Any ideas how to overcome this?
Thanks all

I too was using CCcam_0.cfg , CCcam_01.cfg , CCcam_02.cfg etc. More times than not it would wipe CCcam.cfg . What has solved it for me (so far) was to instead use CCcam_0.cfg , CCcam_1.cfg , CCcam_2.cfg etc. (drop the zero before 1 and 2) . Vix image is now creating CCcam.cfg.backup .

[runmo]

Re: Ccam info problem

Don't like vix that much but will try to see if it helps with latest vti and bh.
I eaven saw somewhere that 0.cfg should be the same as original cfg without any c-line. Doesn't work for me, but didn't removed the zero from the other cfg's.
If it works maybe changing the zero's in 1 could work to, so the cfg's stay in order in the cccam info (1 = 11 , 2 12 , 3 = 13, etc)
Anyway bh and vti images create cfg backup to as vix, but doesn't help.

Makers from vti images don't have clue. BH team won't support such topics.
To be continued I guess...

[runmo]

Re: Ccam info problem

update : the dropping of the zero's not working with vti image, can't eaven switch between cams without hard reset.
will try out with bh tomorrow, if that doesn't help, guess no other option than to try vix image out, but really didn't like this image in past.
To know for sure, is there a c-line in your 0.cfg or is this just copy of original cfg?

[sonc]

Re: Ccam info problem

You can always create your own scripts to do the switching

If you put the scripts in /usr/script they are then accessible (on Blackhole) from the Scripts panel (Green --> Blue) - see image below.

For example, create a file called /usr/script/CCcopy_1.sh to copy CCcam_1.cfg to CCcam.cfg :

#! /bin/sh
#DESCRIPTION=Script to switch CCcam.cfg files

echo "#######################################################################"
echo "Updating CCcam.cfg ......"
cp /etc/CCcam_1.cfg /etc/CCcam.cfg
echo "#######################################################################"

exit 0

Repeat for each CCcam_X.cfg file you have, changing the name of the script and the line "cp /etc/CCcam_X.cfg /etc/CCcam.cfg" as appropriate.






Tested and working ok on Vu+ Duo with BH 1.7.9.

[runmo]

Re: Ccam info problem

I'll try that out after testing the no zero tip from satbeam in latest bh version to see if cfg don't vanish. Just started with that since a few minutes.
I'll allready manished to do the input as you mentioned above sonc in bh 2.0, that's allready fine to know, thx for this great tip
Question to be sure, putting the x_cfg in var/etc and as script is enough, you don't need cccam.info plugin anymore, am I right right?
Quess it must be possible to do the same in other images to, certainly something to try out in vti.