PDA

View Full Version : Installation Enigma cards


smilingjack
01-11-2007, 08:00 PM
Enigma cards
.
http://i3.photobucket.com/albums/y96/smiling77551/100_4611.jpg
.
http://i3.photobucket.com/albums/y96/smiling77551/100_4612.jpg
.
They support:
.
2700
2800
3700
3800
3900
301.010
301.013----Go to www.bellexpress.vu and find the VID mod How To and do it.
501
508
510
6000
.
sofware new 3.4 version is out
.
.
In order to use the Enigma software, you need to install the USB drivers on your PC. The drivers are in the "Drivers" folder.
1. Copy the contents of the /Drivers folder to your C:/Windows/System32/Drivers folder.
2. Connect your Enigma card to your USB port using a mini USB cable
3. Hardware Wizard will ask: "Can Windows connect to Windows Update to seach for software?". Select "No, not this time" and click "Next".
4. Hardware Wizard will say: "If your hardware came with an installation CD or floppy disk, insert it now." Select "Install from
a list or specific location (Advanced)." Click on "Next".
5. Hardware Wizard will say: "Please choose your search and installation options." Select "Don't search. I will choose the driver to install." Click on "Next".
6. Click on "Have Disk". Browse and select the ENIGMA.INF driver file from the EnigmaEdit3.1/Drivers folder. Click "OK".
7. Hardware Wizard will say: "The driver file is not digitally signed and may not be stable". Ignore this message and click on "Continue Anyway".
8. Hardware Wizard will install the driver and indicate that the installation was successful. Ignore any future messages from Hardware Wizard that the hardware was not installed properly or will not function properly. Since the driver files were not digitally signed with Microsoft, Hardware Wizard may display such messages.
9. Start EnigmaEdit3.1.exe and click Test Card the test should result as you can see below
.
http://i3.photobucket.com/albums/y96/smiling77551/new-1-4.jpg
.
http://i3.photobucket.com/albums/y96/smiling77551/new-2-3.jpg
.
10. Click Load ROM, this has to be done only once and never again. Browse to and select from the /Bins folder the ROM.bin file
.
http://i3.photobucket.com/albums/y96/smiling77551/2loadrom.jpg
.
If it loads correctly -may take a while- you get the screen below
.
http://i3.photobucket.com/albums/y96/smiling77551/new-10-1.jpg
.
11. Click Load EEPROM, this EEPROM file can be your your own Married Sub/ExSub card's BIN which matches your IRD or you can use the one but add your tiers to it beforehand. If you use our BIN the tiers are there already but you will have to edit your IRD's TSOP. For the sake of this tutorial we will use our own BIN and DishNet
.
http://i3.photobucket.com/albums/y96/smiling77551/4loadeeprom.jpg
.
If it loads correctly you get the screen below
.
http://i3.photobucket.com/albums/y96/smiling77551/5screenshot3.jpg
.
12. Select your provider, in this case since we loaded a DishNet BIN it is DishNet
13. Select your IRD type, if it is an HDTV receiver then HDTV otherwise Normal
14. Click UPDATE CARD
.
http://i3.photobucket.com/albums/y96/smiling77551/6screenshot5.jpg
.
If it updates correctly -may take a while- you get the screen below
.
http://i3.photobucket.com/albums/y96/smiling77551/7screenshot7.jpg
.
15. It is time to edit your receiver's TSOP.
15. Use jKeys to save your TSOP flash.
16. Open Flash Edit
17. Select your IRD's model from the "Model" drop-down.
18. Browse for your own ird tsop file (the one you just saved with Jkeys)
19. "Open" your TSOP image in Flash Edit
20. Click on "Advanced"
21. Change IRD#(HEX) to the one we have provided you with:
IRD #: 011C746C
22. Change Box Keys to the one we have provided you with.
Boxkeys: 8CA6A88CFDE2E263
23. "Check" on Fix CRC
24. Click on "Save As..." to save your modified TSOP flash.
25. Use jKeys to write the new modified TSOP to your IRD.
26. Disconnect the cable and insert the card in your IRD. Keys will roll in less than 60 seconds, if not then change to channel 202 and wait. Alternately you may just enter the current keys in the software and click Update Card or edit your BIN.
.
__________________________________________________ __________________________________________________ ____

mili
01-11-2007, 09:03 PM
Hi Jack
THanks for posting this.
Well here are my personal observations with the card.
When I got three about a month ago I was afraid that they were too flimsy.
While it maybe a problem if people bend them too much and the solder joints pop so far I killed one only by puting in my back pocket and sitting down forgeting about it. The card is indeed thin because in case of a new MAP call it can be used as an AUX device with a real ROM102 card protecting it (I assume software for such use would be released if needed). The most important feature I found was that it needs no programmer, you program it using a mini USB cable (not included) and that it has no crystal like Atmega/Magic/AVR-X used to have.
The software had it's growing pains namely freezing and incompatibility which for the time being seem to have been solved. I myself have tested the cards in my 6000, 301.013, 301.010, 3900 and 510 receivers (DishNet only). With version 3.4 it works fine, reacting as a normal ROM102 would. I would like to point out the good and the bad things I found.

First the bad:
1, Thin card must be handled with care.
2, Features must be added
3, It ignores Time Zone and Blackout Bit changes in the supplied BIN
4, Supports your own private BIN but ignores tiers all the personalisation in it too.
5, Lack of source code as promised (they say once the software is final they will release it)
6, The card is thin and in some worn out card slots you will have to put one or two business cards on TOP of it to ensure good contact.
7, You must not have another USB to Serial device attached to the computer when trying to program the card or it will not find the card. I have a USB ISO programmer and when I forget to unplug it I always think the card is dead.

Now the good:
1, The card does not freeze with the 3.4 software in any of my receivers
2, The card can NOT be looped by an ECM
3, In case of a new MAP call it will support AUX mode and can protect a ROM102 card when used in tandem with one. leting the ROM102 handling MAP calls.
4, Uses a USB port to program, big problem with devices that need a serial port as most new PCs have no serial ports on them.
5, Simple programming
6, Large internal memory and fast ARM processor ensures ample space to store even full TSOP data from receivers should it be needed as well as the ability to handle 1024 bit decryption in time.
7, You can use your own sub or ex-sub card's private BIN not relying on public BINs (supplied by the way)
8, AUTOROLL!!! no need for multiple daily reprogramming. (hope it stays that way)
9, Has space to store a full ROM and EEPROM of a real ROM102 card, hashes are calculated properly

So here it is for what its worth. Let us hope that the remaining annoyances are addressed and the missing features will be added in version 3.5 but even now the device is working fine.

mili

Crazy1_79
05-15-2007, 03:41 AM
Just got one today, had it up and running in 2 minutes flat with private info on my 510 player. the only disadvantage i have at this time is my locals are not remapped properly.