Check your reader card mhz etc cant be anything big thats causing this have you tried another reader also whats your logs showing when you insert the card into the reader is it detected ps... if you post the log remove your post code if it reads that far
Posts by stevejo
-
-
10964 h 22000 h 5/6 qpsk
-
sorry was wrong with protcol ive had a few beers trying to cure last nights suffering
0963:000000
and boxtype is pc if i remember right ...I assume you have it all setup on the tvheadend side ??
-
boxtype not dreabox ident is wrong not 0000;000000 for 0963 and you have cccam protocol set up and trying to use Newcamd
-
It can work but you have an issue of constant charging not the best device
-
Just another challange give it some time ......
-
You can use catseyes list for other satellites and still use ABM ....load catseyes list first then run ABM.... loading catseyes will wipe the ABM bouquets so runing ABM last will leave you both im sure by default its set to keep other bouquets but can be set if need be .....a lot of other sats are on ABM but i dont bother setting them as I find it easier for the weekly ABM scan I set
-
On the plus side the porn is ok :clap:
-
mtv8 and deejay tv thats one hell of a package for 13e lol ....before April we will be gone also thats a sure thing
I dont think this is directly aimed at cs itll be the run up to 4k or sly Q
-
Not all channels are gone but maybe just a few alive cards
-
Now youll know what to expect next year in the UK .......The scale of things comes to light then the hand is forced to change things once more
-
Not just that build ? has he tried set up a fresh install ? might be a faster route
-
So in short after a years investigation they caught 9 server operators and only 83 punters .....something tells me they weren't trying too hard PMSL !!
:hmmm: -
Here you go
-
if you make the reader for the nline group 2 lets say then the dvbapi user must also be allowed group 2
-
why not remove oscam and just use cccam as a client then
-
There must have been a change to the image in the updates after that date its not ABM its self
-
Thanks Abu but cant see how it can work perfect on a version i got from 16.11 then not .....only issue is the 16.11 version the box goes into standby after an update and then wont boot at all would be good to know where the ABM break occurrs i know im not in tune with current events as ive been off and busy for ages ill dig about now and post back any findings
:14_002:
-
Abm crashes and cant be used 16.11 was the best but since its poor wont start a scan crashes non stop and 16.11 image wont update it crashes once updated am i missing something lol
-
d000704510c84.jpg Hope this comes out as a picture as im on my phone