Apparently d*sh is using a longer CMD07 ......

[seaboard18]

Some folks have reported an "unknown MECM Algo 20" error on some of the 400 channels, e.g. 431, 438, etc.

Apparently d*sh is using a longer CMD07 that is not handled correctly by the current eeprom bin. Not sure when they started using this.

In order to handle this CMD07 which is 8 bytes longer than the current eep is coded for, I've included this patch to apply to either your d*sh or b*v eep bin.

NOT the rom10.bin.

This patch effectively allows the larger CMD07s to be fully decrypted, thus eliminating the "unknown MECM Algo 20" error.
Has been tested in d*sh, but should also work for b3v should that provider start using the longer CMD07 (57h), if they haven't already..

Apply patch with nagraedit 4.1, or as the edit is only 1 byte...hehe...you can also edit the eep bin at location CA7F with the cemu debugger then save the bin, or other hex editor(remember offsets may be different).

Change at location:
$CA7F 27 ---> 24


Old
$CA70=AE0FD60110E7B05A2AF8C60304A14F27

New
$CA70=AE0FD60110E7B05A2AF8C60304A14F24

[smilingjack]

........................mew....................... ......

hahahaha

[seaboard18]

Yea, this new Keyboard has a mind of its own! :D

[Crazy1_79]

don't you hate giving up that favorite keyboard? keys sticky and won't push but it seems the new one just dont' have the "feel" of that old one! Trust me SB i know exactly where you are.

[PigBenis]

Soooo, pardon the ignorance, but that does this mean? Not the sticky keys part, trust me, I watch pr0n too, but the CMD thing.

[seaboard18]

I still have the old keyboard and the mouse too! I decided to go wireless, maybe that was a bad idea! I can't see the mistakes until I make the post most of the time. The keys are much smaller on this keyboard and forget about seeing the writing on the keys! :D

[seaboard18]

Soooo, pardon the ignorance, but that does this mean? Not the sticky keys part, trust me, I watch pr0n too, but the CMD thing.

It means that the cmd07 gets truncated. Its decrypted incorrect all the way back into the rom10to102, doing the 47 and 4d... not 55. This change in the eeprom bin fixed the problem.

[PigBenis]

Hmm, well, seems like im not affected by this.. Unless im not checking thoroughly, which im not... Erm, thanks for the info dude. And also, thanks for the 'compile cemu' guide, just did my first compile, all is working, except a tiny thing thats bothering me (maybe its just me) but it takes a little bit more to get image, sound comes on, but the image takes a bit longer. But oh well, not everything is perfect the first time.

[seaboard18]

It could be the computer that you are using. If you are using it under windows xp in a dos box, it will have an affect such as that. The best way to set this version up is in pure dos. Most older computers will run this version fine with limited memory. You should use at least a Pent 233 MMX, however others will work OK.

[PigBenis]

Hmm... Wow, well I get over the image thing, but now I encountered something weird.... My times are 3 hours ahead of my local time... I dont get it, i didnt change anything... What do I need to adjust here? Oh nevermind, I think its the cemu.ini. All i need to do is copy my old (backup) one and not the one I used from the DJGGP installer... I hope thats it.

[M.E.]

I never got the chance to welcome you to the group Seaboard18. Good to see you out and helping the community. It was suggested to me that I do some reading up on the enigma jtag. I made a slip of the keyboard after reading for over an hour.

;)