Jupiter 1 files

There is only 1 type of file available for Jupiter 1 cards:
- dedicated files that will decode only 1 type of coding
- Allcam files are not available for the Jupiter 1

Dedicated files:
The most characteristic feature of dedicated files is that they work much the same may as an original card does. You could say that dedicated files are built in such a way that they simulate being a MOSC.

A sample of a dedicated file is the Secanix file set, described in the opening page of this chapter.
Dedicated files will decode only 1 type of coding (Irdeto or Seca or Viaccess etc.). In most cases, dedicated files support Auto Updating, just as a MOSC would. In some cases though, you will find file sets, not supporting Auto Update. That's when the file set contains a built-in blocker facility. The blocker will not allow any changes to be made to the eeprom file on your card. That ensures that your card will not be vulnerable to ECM attacks, but at the same time it prohibits your card to Auto Update.

Generally the dedicated file sets consist of 2 files: Flash- and Eeprom file.
- The Flash file contains the Software Program
- The Eeprom contains the Variables that the Software has to work with

There are hardly any file sets around anymore for the Jupiter 1 cards.
Most Jupiter 1 file sets consist of a. hex file (for the AVR) and a. crd file (for the Eeprom).