waiting for code update

[wilf]

sorted it, just left on sly sports 1 for 5mins

well done it appears that some boxes are taking longer than others to update because there was 2 keyrolls together glad you sorted it

[Fspiders]

I cant say in an open forum why VM are rolling the keys as they go through spasms of twice daily to none for months though the last few rolls are slightly different it's basically to do with moscs and VM boxes.. In a very basic description VM are changing certain bytes on the cards.

As said above I'd leave in stand-by with power mode option on. Main reason for that is the amount of movement VM are doing to make room on certain transponders for the up coming channels they want to transmit. The next 6 months is going to be fairly unsettled.

As for the what channel to leave it on in standby.. I really don't think that matters as the box has to on to monitor the keys.. People who tend to just watch the scrambled channels never even notice a key roll as the box is doing the maths in real time.. If the box is on a fta channel when the key rolls it has no idea about the roll.. The first time the box knows anything is when it's sent to a scrambled channel and that's why we then see the "waiting for code update" cos the box has to start from the beginning and work on 2 sets of keys instead of the one in real time.

*edit* I've had a box back today that refused to update and eventually got it to update by deleting the keys and resetting the default key pattern for that network. Seems to have sorted it as it now updates within 5 minutes from a fresh install. Weird how some boxes take forever and some handle it within minutes.

Regards.

[Striker10]

How would you go about deleting the keys and then resetting the default key pattern?

[bitchmonkey]

left mine on sp1 did nothing else at all and its all working again.

thanks