Originally posted by mgb17:

---

Delete keylist.txt first at your box and than upload the new one.
If your box is still connected to your cable feed during your upload switch to a none scrambled channel before.

---

Originally posted by fred66:

---

Originally posted by mgb17:

---

Delete keylist.txt first at your box and than upload the new one.
If your box is still connected to your cable feed during your upload switch to a none scrambled channel before.

---

tried that too still doing the same - I am always on RTE2 when rebooting or reloading.. would the "AU" settings in cam_cfg have a bearing on the keyfile yupdate i.e. should it be "02" or maybe "00" for ignored..? should I look elsewhere in my settings to avoid the wipe out?

---

Originally posted by Scoopdog:

---

Originally posted by robio:

---

Originally posted by ruprect:

---

The keylist did not work for slunk but did work for you (robio)
please let me know what image you are both running. I think commando might only be reading the first 2 lines or something, and maybe other images are fine as long as the correct keys are somewhere in there.

---

I'm Running Sportster 1.75 (2x)

---

N 5401 00 067AF388D22415FD ; ROM7 AU Key Time Tue Apr 8 17:52:53 2008 and we need to change it to N 5401 00 067AF388D22415F5 ; ROM7 AU Key Time Tue Apr 8 17:52:53 2008
this is the current code change for nokia d box running on blade trinity final working in dublin 12

---

Originally posted by ruprect:

---

Originally posted by Scoopdog:

---

Originally posted by robio:

---

Originally posted by ruprect:

---

The keylist did not work for slunk but did work for you (robio)
please let me know what image you are both running. I think commando might only be reading the first 2 lines or something, and maybe other images are fine as long as the correct keys are somewhere in there.

---

I'm Running Sportster 1.75 (2x)

---

N 5401 00 067AF388D22415FD ; ROM7 AU Key Time Tue Apr 8 17:52:53 2008 and we need to change it to N 5401 00 067AF388D22415F5 ; ROM7 AU Key Time Tue Apr 8 17:52:53 2008
this is the current code change for nokia d box running on blade trinity final working in dublin 12

---

1. a load of keys were posted up the first 2 were the correct 01 and incorrect 00 code, both were the current codes. The correct 00 code was also down the bottom.
2.robio who was running sporster 1.75 and the keylist worked.
3.slunk load up the same keylist and it did not work.

Now I am guessing slunk is running commando. I put the last keylist on 2 blade nokias, and on 2 sporster sagem 1x boxes, all these had autoupdate on and still worked. I put it on nokia commando 8.2 and the keylist went down.

I do not know what is going on there, mgb17 has recommended turning off autoupdate. I have turned it back on blade for the moment. I fixed the autoupdating commando box an hour ago. Its code it autoupdated was 067af388d22415fd using evocam

Now my blade trinity final has the right 01 code but the 00 is 067af388da2415f5 this was autoupdated using evocam too.

now I go back in and I only have the 01 code again, the other 2 got deleted.

So it seems to me some images can handle the autoupdates, once the right keys go in. So if you had this image there might be a way to let it autoupdate, then change the 1 incorrect digit and save it. Then it might update with the incorrect one again, but as long as a good key is there it is fine.

EDIT: Look at the codes I posted
Correct 067af388d-2-2415f5
Incorrect 067af388d-a-2415f5

and the last key change
Correct 5b7436a3b-2-30cb46
Incorrect 5b7436a3b-a-30cb46

Coincidence? maybe there is a pattern, has anybody else gotten different incorrect generated codes?

---

Originally posted by mgb17:

---

@ruprect
There are 2 different emm's in use for each rom version.
Depending which one arrives you, you get the wrong digit at a other position.
Beside that the discrambling job is done from the selected emu and not from a image.

---

Originally posted by ruprect:

---

Originally posted by mgb17:

---

@ruprect
There are 2 different emm's in use for each rom version.
Depending which one arrives you, you get the wrong digit at a other position.
Beside that the discrambling job is done from the selected emu and not from a image.

---

I am not sure I understand. The numbers I saw being incorrect were the same on most dboxes, running evocam or gbox. Is this normal?

I am currently running blade trinity, evocam, 001A, AU{02} in camd_cfg, only ROM7 enabled. My keylist was getting new keys and then losing them. Now I have loaded on the following

N 5401 00 067AF388D22415F5 ;ROM10 AU Key Time Thu Apr 3 19:34:44 2008
N 5401 01 7375C3CC596DDFFA ;ROM10 AU Key Time Thu Apr 3 19:34:34 2008

and it is working fine for the last while. I just tried ROM10 to see if it worked. I now presume this does not matter.

Another sagem, andromeda 1.3, evocam, 0013, AU{02} in camd_cfg, only ROM10 enabled. This appeared to have gotten the correct codes. BUT that was turned on at around 6pm today, after the codes had changed. I am not 100% certain the codes were correct, maybe a new digit changed that I was not looking for very well. But I know ROM10 was mentioned by you (mgb17) before regarding these changes happening.

Now I wonder if I had enabled only ROM10 if it would have updated with the correct codes, then I could disable it and turn on ROM7 and be working OK.

I know very little about how the software works, I am just trying some things out.

---

Originally posted by oggnogg:

---

ya have a point there why not backup your image with rom 10 and upload on my shared files for more to try

---

Quote:

---

# debug messages level

# EMM messages
# 00 don't show any EMM's
# 01 show only valid EMM's, default setting
# 02 show valid and bad EMM's with complete data display
M: { 00 }

# ECM messages
# 00 don't show any ECM's
# 01 show only valid ECM's, default setting
# 02 show valid and bad ECM's with complete data display
C: { 00 }

# AU
# 00 is ignored (default)
# 01 enable AU
# 02 AU Auto
A: { 02 }

# Key update
# 01 update only new keys, default setting
# 02 update all keys (used for valid PMK checking)
U: { 02 }

# Key files folder
# 00 keyfiles in /var/keys
# 01 keyfiles in /var/tmp
T: { 00 }

# # Hash pids
# 00 hash all pids
# 01 hash only pids with implemented algos (default)
H: { 00 }

# share Mode
# 00 Pure emu
# 01 Pure emu
# 02 Pure emu
# 03 alle network clients
# 04 newcamd share
# 05 radegast share
# 06 camd35 share(not in use)
G: { 00 }

# On Screen Display for Multicam
# 00 No OSD (default)
# 01 display Smartcard messages, box IP required
# 02 display Smartcard messages new nhttpd format, box IP required
O: { 00? }
USER = root
PWD = dbox2

# To use UDP log
# 00 disabled
# 01 enabled
L: { 00 }192.168.1.6 10000

---