You are on page 1of 32

The alternative "All one needs to know about

AZbox HD" detailed guide!!!!

The minimum good will required:

Before I begin, let me say this: me I envisaged this to be a complementary

“Manual” to the official AZbox HD Manual, which is telling you ‘what’s what’, in a
usual “ABC manner”. Together, I hope, they will help you unleash the power of
Linux in a Multimedia Centre of AZbox HD quality!!!

In addition, this will not be an exhaustive, comprehensive “how to”! For instance, I
only have an Elite model, so I cannot cover properly the Premium model issues, like
WLAN, built-in HDD etc. New drivers, FW, plug-ins are being written etc. etc.

Also, I do not have any original or pirate cards, so some issues with Cardserver
part of Card Sharing [CS] I cannot fully test and report, but only give other
people’s account of it all.

However, most major stuff will be here, so anyone can sort it out for himself or
herself, given the minimal self-confidence, some time to read - and a bit of
necessary patience, in order to do it, aided every step of the way!!!

This is NOT all my work, even though most of it is and I certainly wrote all of it,
minus the quoted text written by Mower/The_Ripper, Tinos, pr2 and the like, who
helped me understand better the “ins and outs” of various plug-ins for AZbox HD!

Guaranteed, if you persevere: within hours, provided one follows this “alternative
manual” - it will all work well in the end, given the absence of spiritual laziness
and being all ‘majestically princely’. So, if one “can’t be bothered” but one ‘only’
wants it “all working” – one is bound to be “disappointed”, I’m afraid...

Well, how will it all be set up properly, I ask?!? By some magic?!? I know of no
such thing: only of persistence and doggedness. Then and only then “the magic”
happens. Only then can one really enjoy his new toy, after “working on it!!!!!!!


How to redo everything from scratch

0) The minimal necessary requirements!

Before all else, a simple but effective warning: please do it carefully and without
cutting any corners!!! It might save you time and a lot of frustration. The devil
lies in the detail. So, pay attention and concentrate!!!

I will only presume that you have connected your AZbox HD properly to your:

-satellite dish [the lower LNB port, as the upper one is a loopthrough to another Sat
TV receiver/Multimedia Centre];
-TV [SCART or HDMI cable] or Home Theatre system [many possibilities there];
-PC [by LAN or WLAN], directly or indirectly [via a Modem/Router].

For newbies, who just got their AZbox HD:

- On your PC one needs to install a necessary Unix editor for various files - like UE
Studio '06 [UES 06 - freeware!] or Ultra Edit 32 [UE32]. Do not edit it all with
Notepad or Word or WordPad, as they add extra signs, without even showing it;
- FileZilla [freeware] to connect with your AZbox HD;
- 7zip [freeware] application to deal with compressed files from the net, in order to be
able to "unpack/extract" them to your PC. Get it all gratis from the net, of course!
- For basic functions explanations, get the AZbox HD Manual from here:
or here:

If one already has AZbox HD:

-backup your channel list, if you already had your AZbox HD installed and sorted in
this regard [the 3 files are in “DISK2” folder of your AZbox HD: all_channel,
antenna_list, DVBS – all three files with the extension “.dat”]
-backup your AZbox HD's EMU folder, just in case...


1) Cleansing your machine – a “clean” programming

This is the best practice I know of – deleting it all and re-doing from scratch,
eliminating various accumulated mistakes, if at all possible! One doesn’t need to do it
sometimes, if all is functioning well and a new FW came out. In that case, one can skip
the “deleting of everything” one has installed previously! But... if it’s corrupt...

Press the Home button on your remote and use your left arrow [around the OK button]
on your remote controller to go to -> Settings -> Data Reset -> PIN number is
0000 -> Delete all plugins, then Delete all channels [or one can do it using FileZilla]!
2) Get a FW and prepare to put it into your AZbox HD

Download and put a "patch" [= Image = Firmware = FW], the one you want to
programme your AZbox HD with, on your USB memory stick. Then, put the USB
memory stick into your AZbox HD. Reboot your AZbox HD, either using the power
button at the back of the receiver or press the red Power/Standby button on your
remote for about 5 seconds.

A note: a "patch" [FW] usually comes compressed, i.e. as patch.rar -> unpack it, using
7zip programe [right click on it -> “extract here”].

Now, once decompressed/unpacked, sometimes one must also rename it, as it comes as
patch.sit file, in which case -> right click on it -> rename it -> patch.bin -> Enter [on your

Warning: USB memory stick should be formatted in FAT, FAT32 or ext3 format,
NOT NTFS [do not reboot from a USB memory stick or an HDD formatted in

Thanx to Tinos: “You need to remove all partitions [from the USB stick - my edit].
Format with fdisk or macosx to leave only 1 partition. Also make sure there is no special
U3 soft on it.”

3) Format the application area

When AZbox HD reboots it will give you a number of options: firstly use Format the
application area -> confirm it by pressing OK.

4) Install the FW

After formatting, install the FW. You will see on the telly which FW you have and which
FW is on your USB drive and ask you if you wish to proceed. Confirm it [OK].

When it's finished [and it takes a while, as FW is big!] and AZbox HD is rebooting - be
close to the receiver to do this quickly - take the USB stick out or - if you feel lazy -
just choose Reboot without update! When it is up press the USB button on your
remote [lower right hand corner] and take the USB memory stick out. You will see a
little message on the screen [“Eject”, if memory serves].

5) Reset

Now, go to Settings -> Data Reset -> and reset to Factory setting [thanx to Tinos
for warning me!]
6) Settings to be sorted out...

Press the HOME button on your remote -> go to and sort out the Settings, as you
need them, depending on your equipment:
-System Information, check if you're "connected" etc.;
-Language/Time -> choose your preferred Menu Language, Subtitle language etc. + time
format [like European or US], time zone etc.;
-Internet settings, according to your equipment and needs;
-Networking Service: press the right arrow to get in, then OK for each option to
activate it all! If you do not do it, you won’t be able to get into your AZbox with Telnet,
FTP etc.
-Audio/Video -> choose your Video Format, Resolution, Screen etc.;
-TV Channel -> DVB-S -> Antenna etc. or go to IP Channel [not yet fully implemented]

One has various options in DVB-S -> Antenna:

DiSEqC 1.0 [up to 4 LNBs],
DiSEqC 1.1 [up to 64 LNBs, if I remember correctly],
DiSEqC 1.2 for a motorised setup and
USALS, for the same thing but automatized, using your Latitude and Longitude.

I will cover here just a very specific setup: a multi LNB toroidal dish, which uses the
DiSEqC 1.1, with advanced options menu. One can edit it to one's own needs as follows:

The 8in1 older switches [v. 1] are now catered for, too - from FW 0.9.1868 and newer!!!
Instant switching, no waiting, no noise in the dead of night and your neighbours or/and
your darlin' cursing you... Superb!!!

HOME button on your remote -> Settings -> TV Channel -> DVB-S -> Antenna
Setup -> DiSEqC -> hit the left arrow to get to the option named Combination -> press
OK on your remote, then set it all up for your xyz amount of LNBs...

I have 8 LNBs on a toroidal dish, with an 8in1 switch, so here is how I got them all
working, i.e. the winning combination for AZbox HD is:

Sat postion 1 = [I reversed Command Order to] Uncommit./Commit. + [Committed DiSEqC] Switch A 
+ [Uncommitted DISEqC] Switch 1 
Sat postion 2 = Uncommit./Commit. + Committed DiSEqC Switch B + Uncommitted DISEqC Switch 1 
Sat postion 3 = Uncommit./Commit. + Committed DiSEqC Switch C + Uncommitted DISEqC Switch 1 
Sat postion 4 = Uncommit./Commit. + Committed DiSEqC Switch D + Uncommitted DISEqC Switch 1 
Sat postion 5 = Uncommit./Commit. + Committed DiSEqC Switch A + Uncommitted DISEqC Switch 2 
Sat postion 6 = Uncommit./Commit. + Committed DiSEqC Switch B + Uncommitted DISEqC Switch 2 
Sat postion 7 = Uncommit./Commit. + Committed DiSEqC Switch C + Uncommitted DISEqC Switch 2 
Sat postion 8 = Uncommit./Commit. + Committed DiSEqC Switch D + Uncommitted DISEqC Switch 2 

It really seems to be the "intelligent solution", as touted!!!!!

Indeed, I am planning to put up 16 Twin LNBs, each sending 2 cables into 2 different
8in1 switches, each of those sending only 2 cables down to my AZbox HD, one per sat
TV tuner, so I will be able to easily watch something and record something else... Peace!
Then, when you have a good enough signal on all the satellites you need, you can scan
satellites individually, all together, or maybe transponder by transponder, according to
your needs. Those DVB-S "antenna" settings have many options.

Do not use the GOGO-list yet! Not ready!!! It may mess up your channel settings!

7) A channel list into the AZbox HD

Put a channel list in at this point, if you do not want to make your own list, with your
own groups like various "favourites”. Use the latest Telesat's Editor. While you are
searching for it, find some good settings/channel lists, too! Unpack both. Install the

When one installs and starts the Editor, one must create a profile, first. Click on
Options, put in a name to create a profile [like, “AZbox HD”], put in the IP address of
your AZbox HD [something like 192.168.x.x], then click on Update Profile.

Open the three files [already mentioned above!] you got from the net: File -> Open ->
find the folder containing the unzipped files -> open all 3 files.

Edit them, if you need it -> DiSEqC settings are under Organise Sat and TP. Every time
you make a change in a satellite position settings -> Update Sat! Otherwise, you will lose
your changes! One can do a lot more with the editor – discover by trying...

Send the channel list to AZbox, when done editing.

AZbox HD will receive an automatic command to Reboot. Wait, and then check it all out.

Edit internally, if needed

When you are watching a channel, press OK button on your remote, so you get the
channel list on your TV -> then find a channel you want to delete -> press the MENU
button on your remote, which is next to the LEFT ARROW on your remote -> Delete ->
Let’s say you want to delete a whole satellite position and all its channels. Go to a
channel [press the OK button] -> EXIT button -> get to the sat position you want to
delete by pressing < or > “arrow” buttons on your remote, to get into the SATELLITE
tab, press the v arrow and choose the satellite position you want to erase -> press
the MENU button I mentioned -> Delete -> OK.

Don't forget to delete the FAV groups, if you have them connected with the deleted
satellite positions, though...

One can easily add channels to Favs or Country or so... It can all be done via remote.

You may want to rescan at least your favourite satellite positions, just in case!

Put the settings/channel list in manually

One can do the same thing via FTP [FileZilla] -> into DISK2 folder on your AZbox HD.
First delete those 3 files you will find in the setings bundles you may find on the net
[Sofrenic and Telesat made some, for instance; they are fairly comprehensive, made
for motorised users, so others can edit them, to their own needs]. Reboot.

8) Let’s start downloading plug-ins into AZbox HD

Make sure you're online ["connected"] for the next step. How?

See HOME -> Settings -> System Information. If you cannot see “connected”, that
is to say an IP address assigned to your AZbox HD, the first thing you can do is to
reboot. Then, if you're still not online, check the LAN cable or your wireless settings,
your modem/router etc.

There is plenty of help for specific issues on many various forums, like Satdudez, Sat-
Plus, Sat-Universe,, German support forum and so on.

Download and install OpenXCAS [by pressing HOME -> Plugin -> Add plugin via red
button] -> and when done reboot [thanx to pr2 for warning us about it]!!!

This will allow you to add EMU's [Emulators/CS SW/”plug-ins”], which will either read
or emulate original smartcards, connect to your peers/servers in terms of Card Sharing
[CS] etc.

A little “extra” but “basic info”: what is Card Sharing?

Card Sharing is: connecting your receiver [in this case AZbox HD] with a specific SW
in your receiver [the latest FW plus CS SW (installed in your AZbox HD, also)
with your friends' receivers or PCs.

In those “servers” your friends [“peers”] will have Original Smart Cards [OSCs] or
Emulators you do NOT have. You want to connect with them [in order to watch the
programs those OSCs/EMU’s can open].

You connect with them via the internet.

With CS you have those cards, too – if “only” virtually. But you can still watch the
programs those OSCs/EMU’s can open, provided your friends are constantly "online"
and you can connect to their receivers or PCs.

Your AZbox, btw, is connected to the net via your router or PC, i.e. a LAN cable [Elite
and Premium models] or via WLAN [only Premium – no USB dongle possibility for now].

And now the "How to" in small steps:

First, create a DynDNS account. It's free.

Go to -> go to “Account”/"create account”.

Once you enter all the details and create an account, get the confirmation email go
to -> “Services”.
There you will select Dynamic DNS [even if your IP doesn't change all the time, but
very rarely] -> then select “Add Dynamic DNS”.
Just create the name you want and do not use Enable wildcard or Mailexchanger.
Click Add host.
It's done!!

After that put the DynDNS details into your Router to enable your DynDNS Service
updater in it, so DynDNS Service is updated every time you change your IP address and
your friends can find you through the DynDNS address. Namely, in your router's DDNS
options [if you have more than one]:
choose DynDNS, then ->
put your newly created DynDNS account username, then
DynDNS account password, then
Hostname [like - this is just an example, create your own name!!].

That address you just created is always going to be the same, even though your IP
address might change every time you logon/get online/boot your PC.
Now SAVE all that or APPLY or ENABLE, whatever is in your Router's interface.

After that you need to forward some ports in your Router. That allows your CS SW
to go to the net and connect with other PCs, in this case a Server with your friends'
cards, the stuff you want to watch... - some details to learn about - routers

So, let’s explain the principle of Port Forwarding. In my modem, it's under Applications
and Gaming -> Port Range Forwarding.

Now, name an “application” [for instance, your peer’s nickname, if you will open just
some ports for CS -then each could be named after your friend - or just “CS” or
AZboxHD, if many are going through the same port].

Put the Port Range as follows:

-your port [the one you have to give to your friend to put into his cwsahre.cfg,
together with your DynDNS and Pass] and the same port should be in Start and End
little box, then UDP or Both Protocols, and add your IP address, plus tick it at the
end, so it is active. {At least that is how it is in my Linksys Router.}

-his port - the one he gave you, where you will be let into his machine, just do the same
as above but name it after your friend, so you know which one is which.

-check your address by clicking on the Network Icon in the Systray -> Support and
you'll see it. Occasionally it may change, if you get another device connected to the
network, so check it, if CS SW is not working. It looks normally something like or so.

Now go to the bottom of the page and SAVE SETTINGS! If you did it the right way it
should all be saved and you will see it the way you want it to be, right in front of you.

Now, in cwshare.cfg or peer.cfg, or whichever file is used for the same purpose, you
will edit: and yourfriendsdyndns.whatever. Also, the rest of the data
you are given from the people you trust, like theirport but also yourport, the one you
assign to your CS SW, so it can go to the net. Also yourpass and hispass! JUST

Don't give up on me now!!! It will all be plain and simple, once we get to the concrete CS
SW – with clear and obvious examples, trust me!!! We will get back to it soon.

That's all you need to know and do, for AZbox's CS SW to work your CS magic, for
now. I will now describe every EMU/CS SW separately, in detail, so you can’t miss! Chill!

9) Support servers, full of “plug-ins”... of all sorts

If one can’t see online the “plug-ins” one needs, after installing FW, one can fix it!!!
There are two places where one can add/edit the links from which one can download
and install stuff directly into AZbox HD, with ease:

a) Press the HOME button on your remote and go to -> Plug-ins -> RED BUTTON
ON YOUR REMOTE [= "add plug-in"] -> edit the links by pressing the blue button
on your remote.

Here are mine: - thanx to the guys from – not sure who is behind this one...

b) Press the HOME button on your remote and go to Plug-ins -> OpenXCAS -> Manual
install -> edit the links. - thanx to BE-COOL - thanx to DJBlu

One can edit them by pressing the blue button. Leave one of the links in each of the
two parts as - the "semi-official" one, as it were....

A note: one gets the sign " / " by pressing the CAPS/NUM on your remote a couple of
times, then 1 = / etc. etc. Also, use that button to change between the caps, numbers

Now, you're going to get a whole new world of support for AZbox HD, which will, no
doubt, grow and grow... Let me show you just one of them, thanx to our Spanish
colleagues [thanx to terrorman for the list!!!]:

* OpenXCAS 
* OpenXCAS2 
* OneStep_EMU 
* MultiCAS 
* IncubusCamD 
* gCam 
* CCcaminfo_v1.3 
* Tevee4yu 
* GoogleMap 
* WebCamViwer 
* LiveFeeds 
* LiveScores 
* SudoQ 
* TuxChess 
* WeatherForecast 
* mwkeytest 
* SCD 
* dbf4all 
* MBoxInfo 
* Speed 
* MultiCAS_v157D‐4T11‐6_2k90704.tar.gz 
* MultiCAS_v157D‐4T11‐2_2k90613.tar.gz 
* MultiCAS_v157D‐4T10.tgz 
* MultiCAS_v157D‐4T7_2k90514.tgz 
* SBox_v0.0.4‐4.tar.gz 
* NewCS_v1.67.RC1_FULL.tar.gz 
* NewCS_v1.67.RC1_UPD.tar.gz 
* CCcam_v0.2_FULL.tar.gz 
* CCcam_v0.2_UPD.tar.gz 
* CCcam_v0.1_FULL.tar.gz 
* CCcam_v0.1_UPD.tar.gz 
* AutoIncubusChg_FULL.tar.gz 
* IncubusCamd_v0.55.tgz 
* MBox_v6_r0010_FULL.tar.gz 
* MBox_v6_r0010_UPD.tar.gz 
* MBox_v6_r0006_FULL.tar.gz 
* MBox_v6_r0006_UPD.tar.gz 
* Mbox_v0.5b_build.v0024_FULL.tgz 
* Mbox_v0.5b_build.v0024_UPD.tgz 
* Mbox_v0.4b_build.v0023_FULL.tgz 
* Mbox_v0.4b_build.v0023_UPD.tgz 
* NewCS_IncubusCamd.tgz 
* NewCS_IncubusCamd_Mbox.tgz 
* NewCS_Mbox.tgz 
* MGCamD_v1.33_UPD.tar.gz 
* MGCamD_Full.tgz 
* SCDXCas_Full.tgz 
* NAS.tar.gz 
If one hates to use one’s remote, one can [thanx to PR2]:
“...edit the file /EMU/plugins.conf 
...and edit the file /EMU/OpenXCAS/addons.conf 
Do not add more than 4 servers...” 
Of course, there already is a plug-in to do this easily, too... heheeeeee...

10) Let’s get down to the naughty bits, heheeee....

Home -> Plugins -> enter OpenXCAS by pressing the OK button on your remote and go
to Manual Install option -> to -> install MultiCAS “plug-in”->
press OK on your remote, to see whatever's at the link provided -> choose the latest
MultiCAS version -> when done, reboot!

A note: there are various “plug-ins”. Some are Emulators, emulating Original Smart
Cards [OSC], decrypting encrypted satellite, terrestrial or cable channels, if those
encryption systems are hacked and so those cards can be “read” and “emulated”.

One of them is MultiCAS EMU, reading many cards but also opening many channels
that are using various hacked CAS [= encryption systems]. To make an EMU, their
writers are using whatever information is freely available on the internet and from
other, non-public sources. The very same teams or individuals who hacked an encryption
system make some other EMU’s.

Some other “plug-ins” are a mixture of EMU and CS SW [= Card Sharing SW]. We shall
come to it later, when we shall speak of, for instance, MGcamd.

Some other “plug-ins” are simply fetching EMU’s the working keys from the net.

And so on... Enjoy discovering...

10a) Checking if MultiCAS EMU works

Go to, say, TV Globo on Hot Bird and wait for the AU to create a working key, meaning
MultiCAS is active and functioning properly with all the valid Master Keys.

Here is exactly how to do it: Activate MultiCAS via HOME -> Plugins -> OpenXCAS
-> Activate -> MultiCAS must NOT have # in front of it, which is done by using
the blue button, then restart it by pressing the yellow button.
Press OK when it restarts, then go out of the Menu using the Home button -> into TV
part of the Menu -> TV Globo, which should open up very soon... Well, at least it used to.
These days it might not be automatic [= AU = autoroll], so don’t waste your time.

Digi TV on 1'W might also not be AU but both of them are still watchable with our
EMu's. So, you might need to put in the relevant active, working key, as they are
both encrypted in Nagra2, which is hacked! You can do it via your remote.

10b) Putting a working key into MultiCAS, via remote...

Find a key on the net, for educational purposes only, of course... <wink, wink>

Press the HOME button on your remote controller -> Plugins -> OpenXCAS ->
Activation & Priority Settings -> put the # in front of all Plugins, except
MultiCAS, by using the blue button on your remote.

Get out of the Menu, using the Exit button on your remote -> Camd Setup -> OK
-> MultiCAS -> Edit And Convert Keys -> sub-menu Nagravision -> right arrow on
your remote -> "down" arrow on your remote -> find the Digi TV section -> Ident
[2011 - warning: for Dream, Humax etc. receivers the Ident is 2111 but don't let that
worry you!] -> put the key in now...

When I wrote this, key 00 was active. One must edit it in 2 parts, as the Nagra
keys are "broken" in two parts: for key 00, the first part is Index 00 and the
other one is 10; for key 01 it’s 01 & 11.

So, choose a relevant part of the key [in this case it's 00 20 11 00] by pressing the
OK button on your remote and then one gets a new little window to edit the old key.
Put the first part in, then hit the Save button on your TV screen, then the other
part [in this case it's 00 20 11 01], then Save.

Get out of that sub-Menu, using the Exit button, then go to Activation & Priority
Settings, restart MultiCAM, using the yellow and/or OK buttons on your remote ->
OK -> then get out of it all by pressing the Home button on your remote -> TV
-> OK... and.... [if the key is correct and you put it in precisely] – colours [heheeee]!!!

Thanx to Ribolovac from Ex-Yu sat forum, here is the "how to" video:

In addition: MultiCAS should read many, many original "subscription" cards. Plus, the
programmers/SW/plugins writers are always working on its development. If not, try
with NewCS or Mbox plugins [more about those later]. Just to mention, there are no
AZbox HD “internal” editors for keys in any other case, so one must add/edit/exchange
files via FTP, not via remote, like for MultiCAS!

11) MGcamd: the best EMU we have today!

There are 3 ways of doing this one:

11a) The "manual installation" [using FileZilla] and “advanced” info:

Get MGcamd for AZbox HD from the net and unpack. Then, you’ll need to edit it a bit.

Initially, I couldn't get it to work as a CS SW. Because I made a silly mistake: I had
the same line in my peer.cfg file and priority.list - X lines clashed. I removed it from
my peer file and all works just fine!!!

Just edit the details in your peer.cfg file as follows:

M: { { mypassword}} 

D: { mypeer's.dyndns.something { myport hisport { hispassword { A2 A2 }}}} 
D: { mypeer's.dyndns.something { myport hisport { hispassword { A2 A2 }}}} 
After that, in your AZbox HD, make the mgcamd folder in OpenXCAS folder, give it
CHMOD rights to 755 and upload all these files into your AZbox HD and CHMOD to
755, all the files - easy-peasy, hehe...

Here’s Duden's intro, who had problems with it, so he had to delete lots and start from
scratch, in order to “repair” it and make it work [ergo, you may skip the first 2 steps]:

“Remember too backup all configs and other stuff before deleting OpenXCAS. 
1. Delete OpenXCAS in the plugin menu. Reboot. 
2. Download OpenXCAS from the plugin menu. Reboot. 
3. Disable MultiCAS in the OpenXCAS "Activation and priority setting" menu. 
4. Download MGcamd within the OpenXCAS plugin menu, via "Manual Install" 
5. FTP to the box and in EMU/OpenXCAS/mgcamd edit openxcas.conf and add the following 

api = yes 
wait = 15sec 

(Thanks to pr2) 
6. Then edit newcamd.list and enter your server configurations. 
7. Activate mgcamd in OpenXCAS "Activation and priority setting" menu. 
8. Reboot 
Now you should have a running MGcamd. My experience is that every time you enter the 
plugin menu, you will have to restart MGcamd using yellow button in "Activation and 
priority setting". 
I am running it local with Newcs 1.65 on a laptop with Ubuntu.” 
11b) Manual installation of the whole, already edited package 

If one gets [usually my] full package [“augmented” with RedBull’s MGcamd key files]
from the net, and wants to update one’s own manually: simply FTP the whole content
of the mgcamd file and give the rights at least to mgcamd modul, autoroll.key &
softcam.key files -> CHMOD to 755. You can do it for all files, if you want to.

Reboot AZbox HD. Then, restart MGcamd, using your remote's OK button.
Sometimes you must change the channel you’re on, otherwise it won’t start.

11c) Direct download and installation, from the net into AZbox HD

Press the Home button on your remote -> Plugins -> enter OpenXCAS by pressing the
OK button on your remote -> go to Manual Install option to install MGcamd -> OK on
a link -> choose MGcamd and when it's done reboot.

I recommend the link to get the MGcamd_Full version!

Also, from there, install a plug-in called SCDXCas, which updates the working keys for
MGcamd automatically.

Once installed, simply activate both of them by removing the # sign in front of both,
then restart all the EMU’s, then MGcamd in particular - and wait a bit...

If necessary – reboot and change the channel.

11d) What can you get using this fab EMU?

Use this fabulous Emulator to “clear” everything that is publicly hacked, using the
EMU function of this gorgeous SW [as opposed to its CS part, as a client to GBox etc.].

Here is the info re. what it actually opens [thanx to Sorglos, Minicat and RedBull, all
updating their own versions of this fabulous EMU!!!]:

“TV Keys updated: 
[26.12.08] ... 1+1 International 
[14.11.08] ... 24 (haber) 
[11.04.09] ... Arqiva (ex Kingston) (4.8°E) & (9°E) 
[16.11.08] ... Bezeqsat EHA 
[10.01.08] ... CableCom (N1) 
[05.08.08] ... CableCom (N2) 
[11.06.09] ... Canal_6 Feed (5.0W) 
[11.06.09] ... Canal_6 Feed (22.0W) 
[04.04.09] ... DAD‐4 FIBER TX‐11 (15.0W) 
[04.04.09] ... DAD‐5 FT‐12 (15.0W) 
[05.07.08] ... Digital Cable Group (DCG) Swiss Cable 
[10.07.09] ... DigiTV [the biggest publicly hacked and emulated package at the moment] 
[24.03.09] ... Discovery‐Science (8.0W) 
[25.09.08] ... Fox Germany 
[08.05.09] ... Fox News (8.0W) 
[08.05.09] ... Fox Sport (8.0W) 
[04.01.09] ... GTRK Yamal C‐Band 
[28.06.08] ... Kabel Digital Home/Kabel Deutschland (KDH/KD) German Cable 
[07.07.09] ... Mediatech 
[11.06.09] ... Megasport (4.0W) 
[03.12.08] ... Multicanal 
[03.06.08] ... Multi Choice TV Barbados Cable 
[20.01.09] ... Nash Dom (53E) 
[22.11.08] ... NTV Spor 
[01.04.09] ... NTV Turkey (42.0E) 
[11.06.09] ... Programme National (ENTV) (5.0W) 
[11.06.09] ... Programme National (ENTV) (22.0W) 
[03.11.08] ... QTV Ukraine 
[02.07.09] ... RAI 
[04.01.09] ... RTR+REGION C‐Band 
[04.01.09] ... RTR+Pomore C‐Band 
[28.11.08] ... Sat2000 (9.0E) 
[28.07.08] ... STS 
[18.03.09] ... Teleclub Swiss Cable 
[28.07.08] ... Telekanal Domashniy 
[17.05.09] ... Test (8.0W) *** NOT EVERY EMU WORKS *** 
[24.06.08] ... TET 
[09.05.09] ... TRT1 (42.0E) 
[17.03.09] ... TV Globo International 
[13.04.09] ... USUK TV (42,2E) 
FM Keys updated: 
[12.01.09] ... cys Radio Channels 
[05.12.08] ... Rouge FM Radio” 

12) NewCS: the best server/card reader we have!!!

Go to Home -> Plugins -> enter OpenXCAS by pressing the OK button on your remote
and go to Manual Install option to install NewCS, as described above -> reboot.

This will work really well in conjunction with MGcamd, as its card reader, as well as
Mbox, also Incubus and CCcam CS SW. It reads various original and "other" cards.
One must activate it by removing the # sign in front of it, as described above, if one is
to use it, as well as any other EMU/CS SW one wishes to use. It only works in
conjunction with other SW.

To start it manually, via Telnet, like PuTTy, for instance, use the following commands:

cd /EMU/OpenXCAS/newcs 
./newcs –nd 
Here’s more info, thanx to Tinos – just to explain that these are special files, written
for AZbox HD specifically, “without web interface or chameleon code in it.”:

“I can confirm that it is 1.20RC13 there is no webpage support in it. It uses old
xmlserver code and there is no chameleon2 support inside. It is a new compile maybe
with some more card support in it but old code based on 1.20 so nothing from 1.6x like
posted everywhere... But it does support cards like nagra3 R180 from 1.31/1.50, so it is
weird compile.”
NewCS can be run with some arguments when you start it, here are some of them explained: 
‐c configfile, here you can specify the path to a configfile. 
‐h help, will show something similar to this. 
‐v version, this will show when the binary is compiled and which version it is. 
‐nd this is will prevent NewCS from forking 

More info:

Here I will only mention that AZbox HD can also work with the Infinity card reader, in
Phoenix mode, reading various cards, in conjunction with NewCS, via USB cable, thanx
to Zipperolo:

“I connected Infinity USB Smart in module mode (Phoenix 3.58 Mhx module loaded) to the USB port 
of the AZBox, and NewCS works perfectly with Sky Italy. The problem it showed in initializing NDS2 
cards is somewhat related to the internal reader but totally disappears using the Infinity. 
The decoder automatically loaded the correct driver and assigned the ttyUSB0 device to the external 
reader. All I had to do was to configure NewCS properly and now it works perfectly with mgcamd as 
a client: no freezes no nothing, it just works.” 

One must mention that now, with a newer version of NewCS, there is no need for

“Just the standard config files included in the old mgcamd & newcs, with the new binaries 
and it works. 
No freezes at all, except sometimes when you open some menu. 
Very stable combination overall, I'm satisfied. 
Following PR2's advice, I just added 

api = yes 
wait = 15 

in mgcamd's openxcas.conf 
That's the only "non‐standard" setting I use.” 
The newest version is out today [14th July 2009]: v.1.67 RC1 – but it doesn’t work with
the AZ internal reader.
Let me add that one can now download and install – directly into AZbox HD [from the
islaremota link mentioned above] - a pre-configured combination of a full NewCS or
NewCS_IncubusCamd, then NewCS_IncubusCamd_Mbox, as well as NewCS_Mbox!!!

Of course, one must still edit it, in order to make one’s own OSC to work. Different
OSCs may have different requirements, so one must learn and edit the necessary files.

A note: there is a new programmer writing a card reading “plug-in” for AZbox. The
plug-in is called SBox and it can be easily downloaded into your AZbox HD and installed.

13) Incubus CS SW

AZ_Box EMU CCcam Installer_1

Take Damir's CCcam installer [= Incubus 0.55] and put in the details as asked! We can
easily install the Incubus CS SW by using it. Just have a look:

IP address should be something like: 192.168.x.x

Username: root
Password: azbox

The above opens the installer’s access to your AZbox HD.

Furthermore, it needs to add the following CS details into the incubusCamd.conf file,
in order to setup your CCcam part, if you have a peer, whose server you will hook onto:

DNS: your peer’s DynDNS, something like – or if you are hooking onto
your own server, locally, then put the IP address of the server, like 192.168.x.x

User: your CS [CCcam] username

Password: your CS [CCcam] password

Port: usually 12000

That is the one CCcam line added. When you're done – reboot to test. [Incubus 0.55 for
AZbox HD can only have 1 CCcam and 1 GBox line!]

When that is done, go to EMU/IncubusCamd folder and edit the incubusCamd.conf [at
the very bottom], to add another server line, this time a GBox one, if you have a peer.

The first line will be your CCcam server/peer and the other a GBox one:

card_server_url_0=cccam://your username:yourpass@yourpeer's.dynd ns.something:port


Be careful, no empty spaces are allowed in this format!

Now, reboot.

Restart Incubus via OK button on your remote, thanx to Hans for warning me that
now, in new FWs, the yellow button restarts ALL the plug-ins.

If necessary, you may use the yellow button first; confirm it with the OK button. Then,
use the OK button again. That should work.
If it doesn’t – reboot via remote, by pressing the Power/Standby button on your
remote, for some 5 seconds, until you see “Rebooting” on your AZbox HD display.

If it’s not working when it reboots, restart the Emu/CS SW and it should work then.

Incubus “extras” [when you feel adventurous and playful, hehe...]

CCcam can become a bit unstable. Try clearing out the memory with this edit to your
IncubusCamd .sh file, thanx to Tinos and RangerOne!!!

First, back up your old .sh file! After saving it, try editing it like this:

killall incubusCamd.sigma
sleep 3
cd /EMU/OpenXCAS/incubusCamd/
./incubusCamd.sigma &


killall incubusCamd.sigma
sleep 3
cd /EMU/OpenXCAS/incubusCamd/
./incubusCamd.sigma &

Don't forget to CHMOD it to 755!!!


If it’s not working, revert to the old .sh file.

This is to connect Incubus as a client to a NewCS server, internally [Newcamd


# URL of card-server to use, formats are as follows:

# newcamd://<username>:<password>@<hostname>: <port>/<des_key>
# aroureos://@<hostname>:<port>
# radegast://@<hostname>:<port>
# Example:
# newcamd://gorski:lozinka@

Thanx to Sat-Universe forum:

Originally Posted by k2k2000

connecting old incubus to newcamd "newcs" server
### provider configuration ###

#nothing here

Strictly speaking, I can't say much, as I have no OSC to setup my own little server...

14) Mbox CS SW!!!


a) Download the latest Mbox and unpack it.

Note: for AZbox HD you will need only the following files - from the comprehensive
package for all kinds of different receivers, PC's and DVB-S cards: mbox_module and
mbox.cfg [the latter must be edited according to your needs];

b) However, port.list and mbox.prio files in the package are only examples [we shall
come back to it]. For now, let's just say that by using the port file you tell the
module to go to your local card and not to the CS.

c) Find good mbox.prio,, ignore.list and allow.list on the net and edit them
according to your needs. More on that subject later.

d) Note your PC's and your AZbox HD's IP addresses.

e) If you already haven’t, download PuTTy from the net [freeware].

Create or edit your files

- Prior to that, the mbox.cfg file should be edited, using a Unix editor, as follows [only
the important parameters, the rest is not to be touched]:

Z: { 11 01 } { 8000 } - this line you need to edit with your PC's correct IP
address, of course, plus the port, so Black's plug-in Mbox Control Centre would work...

B: { 0 0 0 }

T: { /tmp/ }

K: { /EMU/OpenXCAS/MboxCAS/ }

P: { /tmp/pmt.tmp }

Warning: make sure you get the file from Mbox 0.6 latest package! Then edit that one,
don't just copy the old one, as changes might occur in the meantime.

- Now create your openxcas.conf, which should look like this, as Mower said [you can
create a new one or edit an old one, using UE32 editor, as mentioned above]:

name = MboxCAS
daemon = mbox_module
version = 1.00

- Your cwshare.cfg should look like this [this is but a template but all you need to do is
just edit the M and G lines at the bottom]:

# Mbox cardsharing config file #

# CaID
#H: { 091F0FF3 }
# Send ECM's at maximum 5 cards (please use this as default)
X: { 8 }
# Preffered cards ids (up to 32)
#X+: { 09610000:5 }
#X+: { 093B0000:10 }
#X+: { 0B000000:5 }
# max card's distance to use for ecm
I: { 3 }
#NDS system ->Resending ECM(s) on timeout interval
#N: { 400 200 }
N: { 400 200 }
#NDS system ->Resending ECM(s) on timeout interval
#4000 (4 seconds)-> resend current ecm on boxid if no dcw
#2000 (2 seconds)-> wait 2 more seconds for dcw ,if no dcw on time resend ecm(s) to
all boxid's
O: { 4000 2000 }
#Connecting to newcamd server program Newcs
M: { { mypassword}}
G: { mypeer.dyndns.something { our ports { hispassword { A2 A2 }}}}
G: { mypeer.dyndns.something { our ports { hispassword { A3 A3 }}}}

FTP your files to AZbox HD

- Connect with your AZbox HD via FTP [like FilleZilla client]. Put in your AZbox IP,
use root as username and azbox as password, port 22 [Mbox CC will use port 21] in the
appropriate boxes then click on -> connect -> go to EMU folder -> click on OpenXCAS

- In OpenXCAS folder make the MboxCAS folder via FilleZilla FTP client, [Linux is
case sensitive, so it's MboxCAS] . How do you do it? Inside the OpenXCAS folder
right click on empty space -> Create directory -> name it as described -> OK. It
should be given the rights, this folder, so in FilleZilla: right click on MboxCAS folder ->
File permissions -> 755 -> OK

- Copy [drag and drop] into it: mbox_module, mbox.cfg, cwshare.cfg and port.list.
Give the rights [right click on it -> File permissions -> 755 -> OK] to
mbox_module only.

- In your AZbox HD, using your FileZilla, find the /EMU/OpenXCAS/ folder [one up
from MboxCAS]. In it you should find - and if you haven't got it then create it - a file
called module.seq. Edit it to make Mbox the starting module. [Also, right click on it ->
File permissions -> 755.] It should look something like this:

That's it!!! At this point, we need no other "scripts" [files], says Mower!

- According to Mower's advice all you now need to do is to try to start the Mbox
module, using Telnet [PuTTy or some such proggy], to make sure the module will start
and there are no errors.

So, start the PuTTy.exe by double clicking on it,

log in with root as username [hit Enter on your keyboard],
azbox as password [Enter],
then, the following 3 commands [Copy & Paste and hit Enter for each] to kick-start
Mbox and you'll see the traffic/log/what's going on:

cd /EMU/OpenXCAS/MboxCAS/

chmod 755 mbox_module


- If it isn't working I would advise you to REBOOT, then try the Telnet thing again.

The next Mbox stage – if needed...

- If everything is OK and you didn't mess up the editing [and the files are in good
working order, of course] you can now try to experiment with other "scripts", like file, which looks like this [use your Unix editor to create it - just C&P the
following into it]:

cd /EMU/OpenXCAS/MboxCAS
./mbox_module /EMU/OpenXCAS/MboxCAS/mbox.cfg &

Save it as and put it into the MboxCAS folder via FTP, give it CHMOD rights
to 755, then reboot your receiver and then restart Mbox, if needed.

- If everything isn't working you can then try to add the following files to AZbox
HD's MboxCAS folder and try to start or improve the working of Mbox:
mbox.prio, allow and ignore lists.

- In my OpenXCAS folder I also have openxcas.conf looking like this [one must edit it
according to the plugins one has installed]:

count = 4
active_auto = true
active_1 = MultiCAS
active_2 = newcs
active_3 = mgcamd
active_4 = MboxCAS

name = MultiCAS
daemon = emu_module
version = 1.57D

name = newcs
daemon = newcs
argument = -nd
version = 1.6
xcasapi = FALSE

name = mgcamd
daemon = mgcamd
version = 1.32
# argument = -a 3

ap= Yes
name = MboxCAS
daemon = mbox_module /EMU/OpenXCAS/MboxCAS/mbox.cfg
xcasapi = TRUE
wait=13 sec
version = 0.6-10

For those of you with original or pirate cards

Thanx to Ribolovac from EX-YU forum [my translation and edit]:

Let me add, re. the C lines:

C lines are, in fact, the connections to the NewCS server, either from your local NewCS
(local cards) placed in the AZbox HD or from other boxes.

But what I wanted to mention is: if you want to your peer to see your local card, read by the
NewCS, then he C line in cwshare file must start with a local IP, i.e.

In any other case, like DNS or an IP adres, like, the card won't be seen as
local, provided that the card is in your box, which has installed both Mbox and NewCS.
Re. the latest version of Mbox

Thanx to Playdiune [my edit and additions]:

For the latest version of Mbox you will need

Normal use of mbox:

0- mbox_module
1- cwshare.cfg
2- mbox.cfg

With local cards:

1- port.list ( newcs and mpcs connection )
2-device_number.list ( direct cards )

1- - used to know the providers name
2- ignore.list - used to ignore some providers and allow all the others
3- allow.list - used to allow some providers and ignore all the others
4- prio.list - prioritise in a specific sequence


Mbox Control Centre

What is an Mbox Control Centre?

Mbox Control Centre [MCC] is an Mbox "plugin", i.e. it is written in aid of Mbox
Card Sharing Software, which will allow you to control, edit and monitor the work
of Mbox, installed in your Multimedia Centre, from your PC. It is written for
Windows Operating System [OS].


The minimal requirement for MCC to work under Windows OS is Microsoft .NET
Framework 2.0 or higher. One can easily download it from

The latest version is here

Then, one can install the latest Mbox Control Centre. One can do it without
uninstalling an older version, if one had MCC installed already. In fact, it's better not
to uninstall it, as the new installation, done over the old one, will keep the old one's
settings! So, the new version will just function, without one having to go through setting
it all up, every time from scratch. And this is quite useful, as it takes a bit of time. I
am about to describe all of the steps needed...


Start MCC: in Settings tab choose a language and give the profile a name.

Then, write the IP address of your Sat TV box, so your MCC [which you just
installed to your PC] can make contact with Mbox installed in your Sat TV!

One can check it in one's sat TV box usually by going to -> Settings -> Internet part,
using your remote.

Also, put in the path to your Mbox files, like mbox_module, keys, temporary files and
mbox.cfg, as asked to.

In AZbox HD most files are in the same folder, so it's easier! Examples are in the MCC
Settings and About tabs themselves! Here is what it looks like in AZbox HD setup:

Username: root
Password: azbox [unless you changed it]
Mbox Filename: Mbox
IP address: [whatever it is in your setup]
Path-Mbox: /EMU/OpenXCAS/MboxCAS/
Path-Keys: /EMU/OpenXCAS/MboxCAS/
Path-Temp: /tmp
Path-Mbox.cfg: /EMU/OpenXCAS/MboxCAS/mbox.cfg

You will be able to edit mbox.cfg, for instance, from within MCC itself, while Mbox is in
operation, once you set it up properly. We shall come to that later.

I have ticked the Passive FTP option. Save!

Edit your mbox.cfg

First, one must edit one's mbox.cfg file! In order to see the traffic between your
box and other boxes on the net, as it is happening, one can write the following line
in mbox.cfg file:

Z: { 11 01 } { 8000 } - where xxx stands for your PC's IP address.

Then, Mbox will send the data from your sat TV box to your PC. In the Trace tab
of your MCC you will be able to see what is going on. We shall come back to it.

Check your PC's IP address in your Sys-Tray or Network -> show all -> to Properties.
Check that in your MCC, under tab "Trace" you have the same port, that is: 8000.

For Mbox:

K: { /EMU/OpenXCAS/MboxCAS/ }

Leave the rest be! Make sure you always use the mbox.cfg that comes with the
version of Mbox you are using, i.e. the one appropriate for your version of Mbox!
Why? Some parameters might change, like B: { 0 0 0 } recently changed...

A few functions explained

Start Mbox on an encrypted channel. Then MCC. In the main Mbox tab click on
Refresh. You should see some information regarding the encryption system [CAS], if
you have done everything correctly and you have a connection between Mbox and MCC.
Then, click on Reload, see if your peers are online. If all is well, you will see some of
your peers in green colour [= online]. If it isn't happening and you did everything right –
reboot your receiver and restart Mbox.

When you do have the connection, go to the Trace tab, click on Reload in the upper
hand corner, then click on a drop-down Menu "Select Peer to Trace" at the bottom and
choose a peer, then Start trace. You should see the traffic on the screen. Click on
Reload again, if necessary, to see something like this:

[13:33:23] Searching CW cache for CaID 0x1702, pid CW in cache

[13:33:23] ->[DMX - 0] ECM (0x1742) send to ( C444 DC49 5195
3DD8 DF3E EA06 7036 8B02 )
[13:33:23] <-CW (<-0) received from (xxxx NOT in list) (192 ms)
[13:33:23] ===== Network ECM on CaID 0x1702, pid 0x1742 ====
[13:33:23] prov: D57E
[13:33:23] CW0: 29 97 F7 B7 CD 6B 9D D5
[13:33:23] CW1: F6 1F 53 68 E0 A1 B1 32
[13:33:23] ================================= ================

Now you can C&P the log of your troubles to get help or to report back how Mbox is
behaving under given conditions.

Ignore/allow/prio files for Mbox!

Depending on the log one can then see which PID is [un]successful [“failed with PID...”]
and that gives you the tool to make or edit your preference lists. You have 3
possibilities in the drop-down menu at the bottom of the page, "Select/edit filename":
ignore, allow or prio. After you choose one, click on Download. Now, if you had the file
in Mbox folder of your receiver, you will be able to play with it and try to make your
Mbox function more efficiently.

One can add the data one wants to receive in allow.list.

In the ignore.list it's the opposite - the stuff not to bother with.

Mbox.prio should set priorities in multiple PID streaming cases, so Mbox searches for
an answer from virtual cards in a specific order that suits you better, depending on the
virtual cards you may have.

That should speed up Mbox!!!

On islaremote link one has a full version of Mbox, with all the above files included!

Other functions in MCC

You can now edit other Mbox files, as mentioned above, like your mbox.cfg or
cwshare.cfg from MCC interface. When you're done click on Upload.

There are more functions in MCC but now you have the principles of use and you can
explore it to your heart’s content. It gives you a lot of control over what you are doing!

The last warning!

AZbox HD, its firmware, is still in developmental stage and so are the programs/plugins
that go with it. It all keeps changing, evolving! Ergo, KEEP YOUR COOL, BY KEEPING
THIS IN MIND! Things are not yet perfect but they are improving!!!

Remember, you need to compare files, learn – because they may not be what you need -
you must edit them according to your setup/needs.

15) CCcam for AZbox HD

- Download and unpack the latest compressed CCcamCAS for AZbox HD onto your PC.

- You'll see CCcamCAS folder + an additional module.seq file.

- Edit the module.seq file so it contains the exact names of EMUs/CS SW you have in
your machine; delete those you do not have and add those you do have; make sure you
leave CCcamCAS without # in front of it , which means it will be active, while all the
other EMU's will have # in front of them = inactive.

- FTP into your AZbox HD [or so - using a proggy like FileZilla, which is freeware] and
open EMU -> OpenXCAS folder in your AZbox HD.

- Drag and drop the whole CCcamCAS folder, from PC to AZbox HD’s OpenXCAS

- Give rights or "CHMOD" to 755 the whole CCcamCAS folder, then also the
cccam_module itself, inside the CCcam folder.

- Edit, save and then put into CCcamCAS folder the CCcam.cfg file, in order to add the
server details like so:

#C: 12345 username pass 
C: YourM8's.dyndns.something port YourUsername YourPass

# in front of a line means it's not active. In this case it's just an example-line, hence #
in front of it. Leave it as is.

- Reboot using your remote controller's Power button for 5 seconds or so.

- Restart CCcam via the OK button on your remote.

CCcamCAS for AZbox HD is still in Beta stages of development and can only hook onto
1 CCcam server for now but more is coming. It is not fully working yet - some providers
might not work!

But there is a plug-in to change from one server to another, written by Kanber_Kav!

16) Additional Plug-ins

There are quite a few now. I‘ll only mention a few, mainly the ones helping with the

The principles of installation and usage will easily be seen on those examples.

One can:
-install them from the net, directly into the AZbox HD or
-onto your PC and then into your AZbox HD.

If the former is the case – it’s dead easy, even my dead granny could do it, as
described/made clear above, on numerous pieces of SW!

If the latter is the case, there are two ways. Let me explain the first possibility on the
tevee4yu plug-in, by Chemstar:
a) unpack, put the 2 files you get into /tmp folder of your AZbox HD -> HOME ->
Plug-ins -> OpenXCAS -> Red button -> Install (tmp/plugins.lst) -> OK ->
tevee4yu -> OK -> when installed Exit -> tevee4yu -> OK

Use numbers 1 - 7 on your remote to move between packages.

Use buttons Menu and Check on your remote to move within packages.

Use arrows > & < to move up and down within a channel...

CCcaminfo v1.3, Mboxinfo etc. by Kanber_Kav are all installed the same way.

For instance,
- download mboxinfo.tar.gz by Kanber_Kav, from Satdudez
- extract it to AZbox HD folder /tmp
- You will get two files


- Now, go to HOME -> Plugins -> red button to install mboxinfo

- Alternatively, place it on USB memory stick -> extract -> go to plugins ->
red button -> Install (USB)

b) The other one I’ll explain now, one installs differently...

It’s called CCcam Card Server Changer.

Connect your PC with your AZbox HD using, say, FileZilla.

Get into the EMU folder and create sub-folder: incubusServChg.

Give the folder CHMOD rights to 755 [it already is like that by default - but
just to make sure...].

Edit the cccamserver.conf file on your PC -> add the details as described:

card_server_url_0=cccam:// :12000

or "in English"

Now, copy the content of the folder incubusServChg on your PC -> to your
AZbox HD folder EMU/incubusServChg.

Give CHMOD - 755 to all the files.

Press Exit on your remote to go to OpenXCAS -> go to

incubusServChg plug-in ->
OK to select a server ->
Yellow button to restart the Incubus Camd CS SW ->
Exit button to go to OpenXCAS Menu ->
HOME button on your remote ->
TV ->
choose a channel you know your peer's cards should open...

Many plug-ins to go...

You have seen a list of plug-ins a little earlier, so no need to mention them, one by one.
Just try them out, see if they are something you need or if they amuse you...

One more thing: in the lower right hand corner of your Elite model remote, just above
the USB button, there is a “fast forward” button [“>>|”], which will give you direct
access to various “important” plug-ins, namely EMU/CS SW plug-ins, like Mbox,
MGcamd, CCcam, MultiCAS and the like, once you bother to install them well...


More of such stuff is coming, we are told. The FW itself is still in Beta stages and we
are expecting that it will get faster, more stable and full of features, once the
manufacturers of the chip [Sigma] start writing faster and better drivers for its
product, in a more responsive manner to the needs of their customers – ultimately us!!!

That should be giving us more control and insight into the workings of the FW, in
conjuncture with the plug-ins.

We are being told “another month or two”, for way too long now... But! Even if it’s a bit
late – hopefully the results will be worth the wait!

We are waiting for a lot of good stuff that other receivers have, like a proper “all-in-
one” server/client CS/EMU and a lot more...

I hope they don’t drag it too long, as many are already a the end of their tethers... Even
if our Multimedia Centre is superior - in terms of quality of its HW and its potential to
do great things, no other receivers of its class can do anywhere near as well as AZbox
HD – they should not spend the credit they have... for now!!!

Good luck to us all!!!


P.S. I’ll try to add more info later, when I find where I wrote it all...