t-60 wiht IVAC and 745

[ylafont]

Does any one know why i would get IVAC and then 745 after a reboot on the Sony T-60 with a Valid HU card the works Perfectly on a regular sony b-3 box.??

[captain_video]

Which box is the Hu subbed to?

[ylafont]

The card is sub to another box which i have. A sony a55 box. and it works perfectly there.

[T_RJ]

The Card is married to the other box

[captain_video]

You're getting the IVAC and 745 because the card is not valid for the T60. You may be able to get the preview channels but when you tune into a regular subbed channel, you'll either get an IVAC or 745 message because the card is married to another IRD. The IRD info is placed on the card when the card and receiver were first activated with DTV (they are married together). The receiver checks the IRD info on the card to verify that you are using the correct subbed card for that IRD. If the info doesn't match you get the error messages on a blank screen. If you insert an unsubscribed virgin card, you will get either 711 or 721 messages (I forget which) instructing you to contact DTV to sign up for service.

[ylafont]

captain_video thank you for your response, Just one studid question, should that accour even if i unmarry the card?

[groundhog]

should that accour even if i unmarry the card?

An unmarried card should work. I would assume that you should have received a "You have inserted the wrong access card" message, and not a 745 message. The 745 message is for cards that have been canceled and are no longer subscribed. I've never run into the 745 problem doing the same thing that you are doing. Strange?

[ylafont]

That's what I thougth. However at this stage my next step is to re-install Xtreme and hope for the best.

Thanks for all you help.

[dastalliteguy]

This is a cut and paste:
Original author is unknown.

When you receive a call 745 message from your receiver, the message means that the receiver has stored the cam ID number of the current inserted card into non-volatile memory as a bad card number. This happens because something has caused the receiver to believe that this cam id number is bad and that for continued "joy" the end customer needs to get a new access card to prove he isn't stealing service from D*v*. When you see the 745 messages the receiver has stored the cam ID in memory and will not let that cam ID work in that receiver again. Thus requiring a new access card with a new cam id (with exceptions to be noted later in this post).

So what triggers a receiver to store the cam id into memory as a bad number that will cause a 745 message to appear when that cam id is inserted? Well, Numerous things can cause it... here's a few...

1. The cam id blacklist is being constantly fed down the stream from above and it is the most common reason, the cam number appears in this always changing and ever growing list of numbers, and instant 745. The list has numbers added to it EVERY MINUTE of EVERY DAY. They add numbers that have never been used, numbers that have stopped paying their bill, numbers that have been swapped, numbers that have never been sold, and numbers that have never even existed. D*v* knows every number of every card ever made, and he knows the numbers of everyone paying their bills. So subtract the paying card numbers from the total batch of card numbers ever made, and you'll have what he is making the blacklist look like. Virgin cards are not exempt from this list, nor are cards never subbed. The only cards that will never be in this list are CURRENTLY PAYING CUSTOMER CARD NUMBERS, all others are fair game to D*v*.

2. Your receiver number is in the stream as requiring an update for you card, or a marry command is sent to your receiver for the card number that belongs in it in real life (they all have a card assigned to them, and D*v* has a list of those numbers, weather you have that card or not, it is married in a database somewhere. Send command down the stream to receiver an instant 745. (P.S. this works also if the card number is sent down to marry a different receiver, your receiver will go, "that isn't me, I've been divorced, the card is marrying some other receiver, and 745.)

3. Anything that makes the receiver believe the card has been tampered with, some hashing, as well as some other changes to the card can cause a 745 when the receiver believes it's detected something out of the norm on the card. Rare, but it does happen.

4. The card is getting targeted for a card swap and the keys are getting checked and stored for a new card and receiver number. Wrong keys and 745.

5. Anything else D*v* can come up with, to make the receiver go 745. Now that you've got it drilled into your head that YOUR RECEIVER is what makes a card 745, you can see why some people using the same cam ID # will, and some won't go 745 at the same time. It could be that channel your watching has a different data stream on it with a different set of cam id numbers being fed down then what your friend with the same copy of your emu disk and cam # is watching and receiving. It could be a marry command sent to one receiver number, and it could just be luck that a receiver didn't catch the data stream the first time by and didn't react. Why do you think they need to leave updates in the stream so long? It's because not all receivers get the data the first time by, because of weather, data errors, noise, whatever, etc., all could cause a receiver to miss something in the stream. Adding what some have been saying about normally seeing "Your access card has expired" right before a 745 in the past, but now everyone is saying their getting a "Please call 744" right before the 745... This means that D*v* is taking a different approach than just pure blacklisting of cam id's to getting the receiver to mark the cam # as bad and store that number in memory. Probably some command that manages to check the receiver number and it's match to the card number (such as a marry). But the neat thing is, no matter what caused your receiver to display the 745 error; the fix is always the same.

[groundhog]

Thanks, that explains a lot dastalliteguy. The only thing that I still don't understand is why his card would go IVAC. If a valid card married to a different receiver can go IVAC, then how could someone verify if a P4 is a valid card?