ST19 went down for me today (Feb 18)

[cover]

I had finally gotten st19xl to work after playing with it for days. I constantly got the 005 nag: "Your smart card does not currently have authorization to view or purchase this program. Please wait or channel up or down." flashing on...off...on...off...

I got it working around noon today by getting a public ROM102rev10C image (dated Feb 8) and used GenDT08 to add my ROM102 info to it along with the RSA keys that match my IRD's TSOP and some local tiers and blackout string. Everything came in ok after about 8 minutes. Just before 2 pm it had already rolled some keys. I knew this because I had saved the cor and compared it to the original. It was working still at 2PM along with my Coolsat5000 FTA, when I went out for awhile. When I came back at around 6PM, I had the 005 nag and only the barker channels worked. My Coolsat5000 FTA was also down at the same time.

There must be a connection... both going down at the same time...

The fix for the Coolsat5000 was to load a bin from December 8 as that was now working again.

I tried loading st19xl- 2.6.8 from Dec 5 thinking that might address what ever ECM there was occurring today. No help.

I went back to the original st19 2.6.26 and original cor that worked from noon today. No help stil have the 005 nag and blackscreen.

Is there a patchthat I need to make to my cor for the new ECM???

Any other ideas?

Cover

[smilingjack]

Dish is back to MAP 22
So all of the DEC 07 program should work

[cover]

Does that mean that st19 v2.6.26 from Feb 14, is down???

I tried using todays update v2.6.27 (Feb 18) but it just said released to fix a bug in the program, and that did not fix my problem. Also tried usingv2.6.08 from Dec 5 and that didn't fix it either.

I don't find any chatter on any web sites complaining about it being down so I don't knowif it is just me or if there are others in the same boat....

I did see some chatter about the repeated MECM and MAP 22 from December.

For st19, do I need to put a patch on my cor for the MECM update that came down on Feb 14? That's the repeat of the MECM MAP22 from December...

Cover

[dssexpert]

You need to leave it on with the 005 nag for a while before your cor updates. sometimes up to 1/2 hour for me..

I'm still expertiencing freezing, but I am using superforge which I assume is the cause of the problem

[retiredguy]

Im using superforge without any freezing here using the new file that was released yesterday afternoon.

[midgetcoach]

Have a 921(rom 103) with ST19 also getting the 005 nag. Was up until yesterday. Tried to use an old version of ST19 and then the New release. Still getting the nag. Keys and expire dates look good. Any ideas?

[midgetcoach]

Loaded the 9F patch (Feb 14) for the 103. Channels are runnung open now no nag 005. Have some freezeing on locals but I can work on that.

[harrybuckman]

duh missed the last post lol

[cover]

OK, I've been going mad with my st19 emulator and the latest MECM as discussed here. I tried two different AIO ROM102rev10C public images, that were supposed to include the update and the keys. that didn't work. I used an old version of st19 and that didn't work. This is the abbreviated version of the story... This all took most of last night and 5 hours this evening.

What did work was to use the MECM 9F ROM102 patch listed in the post by smiling jack in the ROM102 programming forum. I applied it to my stream updated .cor file (ROM102) which had been working before yesterday afternoon, and which I saved before I shut down the failing st19 emulation when it developed the black screen yesterday.

I did not clean the .cor, nor did I remove the tiers. I did not add the keys as I already knew the keys had been stream updated.

I just patched the update as-is and put it back on my boot disk as my .cor file. It booted up and had video on all channels almost immediately.

All better now.

I had posted this in the ROM102 programming forum in the sticky thread about the Feb 14 MECM patch, but I wanted to close out this thread by posting here with the result that fixed the problem.

Thanks,
Cover

[midgetcoach]

Cover,
I did basicly the same thing with my 921 (rom 103). I now have a freezeing problem. Have not had a chance to see if its on all channels or just the locals. Will be interesting to see if the freezeing is on the HD channels I had open before the 9F patch. Are you getting any freezeing ?

[pope29]

Use 2.1.6.19.

[cover]

Cover,
I did basicly the same thing with my 921 (rom 103). I now have a freezeing problem. Have not had a chance to see if its on all channels or just the locals. Will be interesting to see if the freezeing is on the HD channels I had open before the 9F patch. Are you getting any freezeing ?

I have not had any freezing, but I'm running st19 v2.6.27 with a 3900 and no HD. My locals are fine as well. My usual emuation PC is a P100 that I've had set up for emulation from the H card SLE44 (PGM) days. Later I used it for CEMU ROM10 emulation. It has no HDD and just the bare bones set up with two com ports and a floppy drive. With that P100 setup I still get no freezing but it takes about 7 seconds for a channel change.

When I run it with a PII-433 I get very smooth channel changing and each change take 1-2 seconds.

This whole thing is a continuous learning experience and I still don't understand even half of what I know ;)

For example, the AIOROM102rev10C image that I found posted after the ECM on Feb 18. It was described as having the keys updated and the 9F MECM included. It didn't work... Adding the 9F MECM patch to my stream updated .cor did work. But I didn't follow the detailed instructions about cleaning the image and applying a blocker or locking the card image. In fact in GenDT08 I always set the image lock/unlock to unlock before I save it. Guess that's one of the advantages of emulation - since you don't actually write the image back to a card, who cares if they loop you .cor? ;) I'm going to need to go look at the AIO image eeprom to see if the MECM patch is actually on it as well as the updated keys.

Cover

[midgetcoach]

Thinking the freezeing is a bug in the ST19.