ST19XL not Working

[Greystone]

I am using the 2.5.1.9 Version and it works for a while, then the not authorized nag appears, then it works for a while, then the same problem. The dates are fine until October 07.

Is there a newer version or is there something just screwey ??

Thanks

[skinerd]

Either your tiers or possibly use of public numbers is the problem, not sure.
I know a guy up 100% with ST19, and I just helped him change to private numbers, so maybe that is your problem

[Greystone]

Yes I have been using the public numbers for over a year without incident. Not really sure of how to use Private Numbers.

I will recreate the Tiers and see if that is the problem. Will let you know. I have just been using N2Tierupdater the last year for updates and all has been well. Guess it's time for Tierworks.

Thanks

No Go.

I made new tiers and it works for a while then flashes Not Authorized, then goes back to picture okay. Perhaps it is the Public Info.

[midgetcoach]

Make a copy of your COR. Put the new CS blocker on it and update the keys. Should be good to go and the keys will roll.

[Crazy1_79]

you do not need to put a blocker on a st19 image. don't put a blocker, get a real 10B image and then put in yoru own numbers. with st19 it is very easy to go private once you ahve your rom 102 married image. just add tiers to the image and rename it st19.cor it does the rest for you.

Sounds to me you are getting false keys from the use of public numbers. they have been targeted. time to by a private keyfile from mili if you do not have a private married rom 102 keyset of your own. the how to to married the receiver to a rom 102 image is here:
http://www.dssftp.com/forum/showthread.php?t=71649 for SK receivers and here for legacy receivers http://www.dssftp.com/forum/showthread.php?t=71650

[ruciz]

I went private last night and no justice. Always got 005 nag..
applied CS blocker over image, works like a charm. You don't have to go private this way. I suggest looking into how its done while the CS blocker sits in for ya.

Might try unblockered image later tonight to see if it works or not. CS blocker working 100% atm on ST19.

[midgetcoach]

Crazy1
A month ago I would have agreed with you and up until the last ECM I was able to work with the tiers on the COR. After two weeks of my 510 having the NaG problem I tryed a non B1 blocker. It worked good but the keys would not roll as it was not a autoroll blocker. When the CS blocker became public last week I tryed it and it works great. No nag and it does autoroll. Don't even have to redo the tiers or anything, no password nothing just patch it to the COR and you are set. Make a copy of a COR and try it. I think youll like it.

[midgetcoach]

I went private last night and no justice. Always got 005 nag..
applied CS blocker over image, works like a charm. You don't have to go private this way. I suggest looking into how its done while the CS blocker sits in for ya.

Might try unblockered image later tonight to see if it works or not. CS blocker working 100% atm on ST19.

ruciz,
I'm not a coder but when the CS blocker was released last week I looked at it. Near the bottom was something about checking B1 code. I knew the B1 was part of the Nag problem because I could block it with a non B1 blocker. That one didn't AR but if I updated keys manually it worked fine. When I saw the B1 stuff on the CS I tryed it and it works great.

[Greystone]

So what really needs to happen is a new release of ST19XL due to the recent changes to the stream ??

I don't mind doing private keys but if it is not working perhaps it is best to wait.

[ruciz]

its easier to try to get private going and fail when you can resort back to public, then when you have to go private along with everyone else when public isn't an option... I presume forums will be swamped when this new rev comes out, and likely public won't be an option unless you are using CEMU which can code (usually) around anything (hell, a Rom10 image is still working on an N2 system)

[Greystone]

I don't mind doing Private, it actually sounds pretty straight forward, but a few people say it is not working as well. Just want to confirm it is currently working before undertaking it right now.

Thanks

[bigeee]

I currently have 6 dvr's running ST19XL all 510's running cloned private no's (thanks for your help Skinerd)
I have 15 x 311's and two 301-13's all running ST19XL
I have one 322 running ST19XL

All running just fine.......................

[ruciz]

holy frig bigeee. you have like 20 kids or something? power bill must be horrendous as you would need at least 5-6 computers going to keep ST19 up on that many receivers.

Public number ECMs can currently be coded around - but it makes more sense to not have to worry about that down the road when you can fix it up now.
had great success on a 301/3100 getting private.. took longer to jtag them than to switch back to their private #.. if you go RSA over SK method, you will have to re-do the firmware after every firmware update.. this isn't appealing on very old IRDs like the 2700, 3900, and I Think 501/5100?

not to hi-jack.. but I got a 2700 using GenDT08 which isn't seeing the receiver info so it makes bunk firmwares and the IRD won't work.. I checked the cfg file and referenced the addresses with hededit and they are all there.. tried firmwares I got off the net and same issue.. any ideas?

[bigeee]

holy frig bigeee. you have like 20 kids or something? power bill must be horrendous as you would need at least 5-6 computers going to keep ST19 up on that many receivers.

Public number ECMs can currently be coded around - but it makes more sense to not have to worry about that down the road when you can fix it up now.
had great success on a 301/3100 getting private.. took longer to jtag them than to switch back to their private #.. if you go RSA over SK method, you will have to re-do the firmware after every firmware update.. this isn't appealing on very old IRDs like the 2700, 3900, and I Think 501/5100?

not to hi-jack.. but I got a 2700 using GenDT08 which isn't seeing the receiver info so it makes bunk firmwares and the IRD won't work.. I checked the cfg file and referenced the addresses with hededit and they are all there.. tried firmwares I got off the net and same issue.. any ideas?


LOL Ruciz, naw, I have two teenage brats and only one 510 running in the family room plus a 311 in my work shop to watch while setting up IRD's.
All the set-ups are at friends, family, co-workers houses. I just maintain them.
Sometimes I wonder why ??? LOL
I'm just in the process of emu modding a 522 for my kids - just to shut them up !!!
I set up two independent 311's for the kids but they were not happy - has to be a PVR GRRRRRRRRRRR now I have a couple of 311's to get rid of - hey that's kids !!

[Greystone]

Ahh and I have one of those lovely 4900 models. Guess it's time to dust of the Jtag and give it a try with Private Numbers.

Odd though I tried Cemu and no problem. I much prefer ST19XL though.


Public number ECMs can currently be coded around - but it makes more sense to not have to worry about that down the road when you can fix it up now.
had great success on a 301/3100 getting private.. took longer to jtag them than to switch back to their private #.. if you go RSA over SK method, you will have to re-do the firmware after every firmware update.. this isn't appealing on very old IRDs like the 2700, 3900, and I Think 501/5100?

not to hi-jack.. but I got a 2700 using GenDT08 which isn't seeing the receiver info so it makes bunk firmwares and the IRD won't work.. I checked the cfg file and referenced the addresses with hededit and they are all there.. tried firmwares I got off the net and same issue.. any ideas?

[Greystone]

Were you able to get the Private Numbers working ?? Before I buy some just checking to make sure that it is the Public Numbers messing up st19xl.

Thanks

I went private last night and no justice. Always got 005 nag..
applied CS blocker over image, works like a charm. You don't have to go private this way. I suggest looking into how its done while the CS blocker sits in for ya.

Might try unblockered image later tonight to see if it works or not. CS blocker working 100% atm on ST19.

[JT]

st19xl with private numbers is working great.