Piranha
Member
I will endeavour not to transgress the forum rules!
If, like myself, you have been trying to use MGCamd on an E2 box without success for a long time, thinking that you must be thick (true in my case!) and everyone else a genius, take heart - it is only a minor change or two away from where you have always been!
After many attempts, I have finally got MGCamd running on two TM Twin boxes, using the same, shall we say "configuration files"! The main connection "file" has only worked in CCCam until a few hours ago, but for a long time. Nothing has changed at 'the other end' so to speak, it was just my setup that I have consistently got wrong time and time again, when trying to use MGCamd instead of CCcam.
For those few that haven't solved the MGCamd riddle (next one up is Oscam for me!!) herewith a couple of pointers:
1. For me, with a Technomate Twin OE box, the mg_cfg setting for the box type I previously left at {00} (Auto detect), until changing it to:
# box type
# 00 autodetect, change only if you think wrong type detected.
# 01 dbox2
# 02 dreambox
# 03 triple-dragon
# 04 relook
# 05 openbox
B: { 06 }
#06 Was not shown in the mg_cfg file that I was playing with, but I found a version elsewhere that showed #06 Dreambox/mips, so I gave it a go! Guess what?!
2. Another factor is almost certainly the attribute assigned to the mg_cfg file - by default, if you are using DCC to inject the file to var/keys, it will be given a '644' attribute (something like 'Read/Write I think?) but it evidently needs to have '755' attribute (which is additionally executable, I believe)
3. THEREFORE:
A. In your mg_cfg file, check that the 'B:' parameter is correct for your box!
B. Ensure that the mg_cfg file has the attribute '755'
Finally, make sure that you do not have any typos in your newcamd.list file! (I would be very surprised if that hasn't caused many thousands of people the same problems I have created for myself!)
Feel free to PM me if you are struggling with MGCamd - perhaps I can help you!
If, like myself, you have been trying to use MGCamd on an E2 box without success for a long time, thinking that you must be thick (true in my case!) and everyone else a genius, take heart - it is only a minor change or two away from where you have always been!
After many attempts, I have finally got MGCamd running on two TM Twin boxes, using the same, shall we say "configuration files"! The main connection "file" has only worked in CCCam until a few hours ago, but for a long time. Nothing has changed at 'the other end' so to speak, it was just my setup that I have consistently got wrong time and time again, when trying to use MGCamd instead of CCcam.
For those few that haven't solved the MGCamd riddle (next one up is Oscam for me!!) herewith a couple of pointers:
1. For me, with a Technomate Twin OE box, the mg_cfg setting for the box type I previously left at {00} (Auto detect), until changing it to:
# box type
# 00 autodetect, change only if you think wrong type detected.
# 01 dbox2
# 02 dreambox
# 03 triple-dragon
# 04 relook
# 05 openbox
B: { 06 }
#06 Was not shown in the mg_cfg file that I was playing with, but I found a version elsewhere that showed #06 Dreambox/mips, so I gave it a go! Guess what?!
2. Another factor is almost certainly the attribute assigned to the mg_cfg file - by default, if you are using DCC to inject the file to var/keys, it will be given a '644' attribute (something like 'Read/Write I think?) but it evidently needs to have '755' attribute (which is additionally executable, I believe)
3. THEREFORE:
A. In your mg_cfg file, check that the 'B:' parameter is correct for your box!
B. Ensure that the mg_cfg file has the attribute '755'
Finally, make sure that you do not have any typos in your newcamd.list file! (I would be very surprised if that hasn't caused many thousands of people the same problems I have created for myself!)
Feel free to PM me if you are struggling with MGCamd - perhaps I can help you!
