Tutorial : How to install softcam (OSCam/CCCam) manually, if you hate ipk packages

:hello

:don-t_mention:

The ___how_to_manual_installing_Oscam.txt file now contains some info about installing on the "systemd" method ... and not only "init.d" method.

The "systemd" method is used in Enigma2 distributions, which are based on the new Enigma2 core - close to the original Dreambox. Or on Enigma2 distributions that come from Dreambox. But, of course, open-source Enigma2 distributions usually use the "init.d" method.

Quote from s3n0

Discussion of article Tutorial : How to install softcam (OSCam/CCCam) manually, if you hate ipk packages:

Quote

OMG ... don't use IPK packages. Don't be lazy to learn something. Use the manual installation method to install SoftCams like OSCam or CCcam.

but why to hate ipk packages when it does it all for urself? I dont get the point of doing it manually :D

Mastering the Linux process, for installing any new service (binary file) is unprecedented :).

The Linux installation-way will work anytime and anywhere... and under any circumstances.

During the installation via the Linux Shell, if something does not work, you will immediately find out what does not work and why.

IPKs are packages made up of different (random) people, often people without a good knowledge of Linux.

IPK is just an installation package and nothing more. The IPK should ensure that everything is "done automatically per user".

There are already a lot of IPK packages on the internet today, but almost half of them may not work (fit) in your Enigma2 distribution unless they come from a feed-server designed specifically for your Enigma2 distribution.

Very often, users use these IPK packages downloaded from the internet. But these IPK packages are not always universal (so-called "_ALL"). Even if it is an IPK package that is designed for "all" ("_ALL") Enigma2 distributions and for all CPU/chipset architectures, there may still be a problem. And there can be many of these problems ! For example: The IPK package will include an Oscam binary file that was compiled without USB external reader support or without SSL support. But what then, if the user needs these modules in Oscam ? He must then look for another IPK package ? :) It's really complicated. Unfortunately, Linux is not Windows :). Although Linux appears to be a universal OS, the opposite is true.

The manual installation method using a binary file is quick and easy. You don't even need a feed server. BTW, many Enigma2 distributions, even on the feed server do not even have Softcams packages. Even then, you must use the manual Softcam installation procedure.

Running the right Softcam in a set-top box is often accompanied by many problems.

You may also update your Enigma2 distribution and Softcam will immediately stop working. Even then, you have to use the Linux Shell again to find out why your Softcam doesn't start. If you have your init.d script ready and you know where the binary is, then you can easily find out why it doesn't start.

Some IPK packages may have forced directory settings for softcam configuration files. Then, when you reinstall Softcam or use a different IPK package, the default directories for configuration files can be used there. But the newly-launched Softcam will not find your previous / alternate configuration directory.

It could take a long time ... there are really many causes and problems with Softcam startup.

The average user will usually not encounter problems. If a problem also arises, it will be solved, for example, through a discussion forum and then it will definitely forget about its troubles.

I have personally dealt with X cases of a malfunctioning Softcam start on set-top boxes. Thanks to the Linux Shell, I have always solved everything. Even less experienced users can then write a question to the discussion, with the error message in the Linux Shell.

////// EDIT :

I would like to add, that some users (although in my view it is nonsense) also requires running multiple Softcams at the same time, on one Linux set-top box. And in this case, again, the knowledge of manual installation of the service (its auto-start) will serve best. Many IPK packages do not address these ideas at all.

If you want to install 2 x OSCam, it will simply overwrite the original, including the default configuration + without backing up the original configuration... because most IPK packages are really primitive (without an intelligent algorithm in the installation script).

However, this also applies to the installation of two different Softcams (for example Oscam + Ncam). Many "Softcam-Panels" for managing Softcams in GUI / SKIN do not allow to start, several Softcams at the same time.

Since I also mentioned the lost Softcam configuration, this is also a common problem for users if they use IPK. Users reinstall the IPK package, but often forget to back up their own Softcam configuration. This configuration is usually silently overwritten, the default configuration, after a new IPK package is installed. Therefore, again, the advantage is to stop the Softcam service, swap the binary in Linux, and restart this Softcam service.

As you can see ... the method of manual installation of the Softcam service ultimately has a lot of benefits.

Minor update of archive containing information - how to manually install SoftCAMs in Enigma2 set-top boxes.

_{hello i need help about softcamstartup on vu zero original receivers and dreambox 800hd se original receiver ....}

i got NCAM on all of them latest version installed but it does not autostart

any config or ipk or what to do to install i tryed already this command

Code

wget -O /etc/init.d/softcam --no-check-certificate https://github.com/s3n0/e2scripts/raw/master/softcam
chmod a+x /etc/init.d/softcam
update-rc.d softcam defaults 90  # to remove: update-rc.d -f softcam remove
reboot

i copy and paste this but now the ncam does not even like to start at alll even with restart or anything....

Hello.

You must first edit the "softcam" shell-script. Change the variable

BINFILENAME="oscam"

- to :

BINFILENAME="ncam"

... and also rename the binary file in the "/usr/bin" folder to "ncam" if it is not there.

Also, one of the default configuration files for Ncam is different than in the Oscam case, for example here:

/etc/tuxbox/config/ncam

You also have to change the names of the configuration files from:

oscam.*

- to :

ncam.*

Everything else is described inside the "softcam" shell-script.

Hi.

Here is another small update to the series of instructions for installing softcams in Enigma2 set top boxes.

Quote from s3n0

Hi.

You should have started your own / separate topic. It doesn't belong here.

As for Conax encoding, I don't know it very well. Maybe it also needs to send EMM (AU - AutoUpdate) updates to the card. Check that EMMs are being written and that everything is set up correctly regarding AU / EMM writing. Also try to always use the latest Oscam.

And btw... for Conax... as far as I know, you don't need to use OscamEMU (with the EMU-lator module / patch).

Display More

The latest versions don't work on the Xtrend ET9000; only older versions do. The emu is needed for sharing to work on the card.

There's no other way, as I tried another version and it didn't work

thanks bro

I don't know CONAX as I wrote, but a friend has a CONAX card that can be shared normally... in Oscam without the need for an EMU patch/mod.

The EMU patch/mod is used for certain types of encoding (for example BISS), but CONAX is not among them. It is actually an emulator of card. So no CONAX card has anything to do with it in that case.