My Cryptoworks module is not recognized by DM8000 is there a solution?
Edited by ricki, 4 November 2021 - 18:31.
Posted 4 November 2021 - 19:43
Remove the module, restart Enigma in debug mode, pliug the module back in, wait a minute or so, restart Enigma in normal mode, get the debuglog from your box, and post it here.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 5 November 2021 - 13:37
Doesn't help much, the last message is
CI module inserted in slot 0
Chances are the latest CI+ code isn't compatible with the old DM8000.
If it is a CI module ( without the + ), can you try OpenPLi 7.3, and does it work there?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 5 November 2021 - 14:13
So it's probably related to the new CI code, which may not be compatible with the DM8000...
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 5 November 2021 - 14:26
The DM8000 has known issues when ‘hybrid’ CI modules are used (CI+ modules that don’t advertise the ‘+’ function and react as normal CI modules). Sometimes it simply helps to boot the box without the CI module. Once booted, insert the CI module and make sure that CommonInterfaceAssignment is used to force the CI module.. In your case CAID 000B…
Posted 5 November 2021 - 14:36
The DM8000 has known issues when ‘hybrid’ CI modules are used (CI+ modules that don’t advertise the ‘+’ function and react as normal CI modules). Sometimes it simply helps to boot the box without the CI module. Once booted, insert the CI module and make sure that CommonInterfaceAssignment is used to force the CI module.. In your case CAID 000B…
Doesn't work in this case, see above. As soon as the module is inserted, the box hangs...
p.s. that means the same issue should apply to the CAM701, which is also a 'hybrid' module. Which we have, so it can be tested.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 5 November 2021 - 14:47
Do you think it will work with 8.1?
I thought you wrote 8.1 was the version with the problem?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
0 members, 10 guests, 0 anonymous users