Jupiter 2 files |
|
| There are 2 different types of files available for Jupiter 2 cards: - dedicated files that will decode only 1 type of coding - Allcam files that are able to decode multiple coding systems 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. There are dedicated files that are specifically built for use with the Jupiter 2 cards. You will also find however, that some funcard file sets will work just fine on Jupiter 2 cards too. Generally the dedicated file sets consist of 3 files: Flash-, Internal Eeprom- and External Eeprom file. - The Flash file contains the Software Program - The External Eeprom contains the Variables that the Software has to work with - The Internal Eeprom can be used in different ways It is up to the author what kind of functionality is given to the Internal Eeprom. Some authors use the Internal Eeprom to store some comment which generally serves no special purpose. It might for instance be the name of the author or such. In other words, there is no general rule on how to use the Internal Eeprom. Allcam files: The most characteristic feature of Allcam files is that they do not behave like a MOSC at all. They don't simulate a MOSC, they emulate. Allcam files only work in combination with an Allcam patch. To my knowledge, there are no Allcam files, specifically written for use with the Jupiter 2 cards. However, some Allcam file sets, built to work on a funcard, will also work properly on a Jupiter 2 card. Allcam file sets generally consist of 2 files: Flash- and External Eeprom file. - The Flash file contains the Software Program - The External Eeprom contains the Variables that the Software has to work with - The Internal Eeprom is not used Mind you, even if the Internal Eeprom isn't used by the Allcam Software, it is important to ensure that the Internal Eeprom is blank. So you need to erase the Internal Eeprom properly. Sometimes you will find a blank Internal Eeprom file with the other files. In that case you have 3 files to program your card with. The Internal Eeprom file ensures that the Internal Eeprom is blank after programming, like when it would be erased. Although there are many people that offer Allcam file sets, there are only very few distinct authors of Allcam Software. Most people just use the same Flash file and only create a modified version of the Eeprom file. That means that when one file set contains a bug, all others based on the same Software, will contain the same bug. That's why you will very often see that when a bug is discovered in one file set, switching to another file set doesn't solve the problem. You would need to look for a file set, based on another Software. | |