Why Some Unit remain up while others go down with an ECM.

I will try to explain this in (layman’s terms) without breaking the rules, but I feel with everything this kind lady has done for the site and members here she deserves the best answer I can supply. Now I’m sorry to say it’s not because of the following reasons, (Smoke & Mirrors) or it’s (MAGIC),it’s all about the (MATH).


with every new (ECM) that comes down the stream after all viewsat go "AUTOROLL" and lose their signal. I also know you "test" every bin file available to see if it will bring up your viewsat alot like I do, but I don’t follow dates as you do. I personally try to see what the (stream log) tells me, and what MECM mapcalls is being used. Each mapcalls has its own bin file to fix processing "Audio" and "Video" Signals.

Under (Mapcall57) every mapcalls has its roots in this mapcalls and everything is made after this and used in making new mapcalls i.e.; oX03A, oXB3 and so on. Now what you're asking is why some receivers do work better, or hold up better than compared to 'Viewsat when it comes to a new "ECM" or electronic counter measures.

The answer is plainly; all bin files are based on the "Mapcall57" Code, which Viewtec owns after paying for. Now with that said, and since Cyphris has said' many times that the "Coders" are working hard in producing a "FULL and complete Bin File" that will not go down because of ECM's.
Which is bs to continue sorry about that now I have the "Source Code" from which the coders write ever new bin file from Viewtec, it (Incorporates only 256 known mapcalls) in each new release "A/R" Fix. This amount seems very large, but compared to the actual number of "mapcalls" that are used by DN, it remains small.
So what does this mean, and why? Does Sonicview stay up longer than Viewsat well its simply that sonicview incorporate more mapcalls tables than viewsat does, they will not allow there coder to uses more than the already known number of 256 tables. Why? Because they do not want any other fta manufacture from knowing how many map tables they have by reverse engineering there bin files.

So why do we not have a "FULL DUMP" File? Well I think most of you can guess it's all about MONEY!, nothing more. So I would think the only reason Cyphris even continues to post that type of rumors are for sales' to allow viewsat to continue sale to people with hopes they will come up with a fix that will last, or contain a fix for n3 codes, this of course is just hopeful thinking,


The reason sonicview and other boxes work on old file’s, are because they have incorporated more mapcalls tables into each bin file they released in the past. Where my Sonicview receiver has almost 800 mapcalls included in their files from "Oct", "Nov" and "Dec" 08, using something called; Montgomery Multiplication [ mapReg"A" = [ptr] * mapReg"M" ] coding. Now Map "A" is abbv. For “Aladdin” and "M" is abbv. For “Mervin” these of course are names of what type encryption DN is using at the time.

Note: this is not a Code, I just used this as an example to describe N2 codes used by DN.

Viewsat only remains with a set (number of 256), now old files on say "pansat" and "captive works" and of course other units contain several different amounts of these mapcalls, and so i.e.; will work on some versions of ECM because DN has only a set number they are now sending out at any one time.
The good news is that DN is no longer writing anymore "ECM" nor changing the map tables so what we see now are old version already used with just some modification made in the math.

So "BINGO" some older files continue to work with ECMs.

So does this answer why viewsat boxes need new bin files each time a "ECM" comes down the pike? well yes, because they simple will not change anything but the math involved, and their lies the problem. Without adding more map table numbers to each version of their bin files only a very few modified older files will work with some,(very few) "ECM"s. which one's I
One more point I want to make here, viewsat uses a single coder, not a group but sonicview does uses several people South Koreans as their coders. So by looking at each bin file for example: VS2000 "extreme unit" you will see after each date (PGM) that’s the coders name, no sonicview file has these after them that’s how you can tell if he wrote the file or not.

Since "Aladdin" N2 codes are still used and the new N3 encryption is still based on this code I do not think viewsat will just give it away. But there might also be another for reasons most people do not consider. Now if VS wrote a "Full Dump" code file was released, or say even 90% of the actual codes where put out in a new file, I believe some units would not be able to actual hold the amount of information involved, nor may not be able to full the full functions because of lack of CPU power, and Memory needed.

Also one more point, if 90% of the mapcall57 was used to produce a "full Dump" bin file then DN could finally write a new ECM to completely knock us down for good. Whether this is there legit reason for holding back, I personally do not know. But it's as good of a reason I would worry about if I owned the source Code.

Written by; 0dd Thomas/c/p