cover
03-31-2009, 05:22 AM
I currently have been running st19 using MAXMEL and Dish4900 TSOP/ROM102 eeprom married with SK with my ROM102 image (cor file) running wide open with a real AUX.
I do not have the original TSOP or original ROM102 eeprom image. Can this st19 cor file (ROM102) image be used as-is with slinger? Or, does it need to be cleaned with all tiers removed? If it is cleaned, then what rev level should it be?
The Slinger Client setup instructions do not mention what rev level is needed - just a "eeprom that is married to your receiver" and then gives an example for BEV of ROM102 rev 240.
If this is a ROM102 eeprom, and the example is for BEV, then it seems to prove the Slinger will work after the switch to N3 using a N2 image, which has been the big question in my mind.
Has anyone up and running noted what what ROM and rev level is being seen in the IRD?
In subsequent IRD updates, would it seem likely that there would be a check implemented by BEV and DN for N3? If so, then the Slinger would need to be reporting itself as an N3 ROM.
Any ideas?
Thanks,
Cover
I do not have the original TSOP or original ROM102 eeprom image. Can this st19 cor file (ROM102) image be used as-is with slinger? Or, does it need to be cleaned with all tiers removed? If it is cleaned, then what rev level should it be?
The Slinger Client setup instructions do not mention what rev level is needed - just a "eeprom that is married to your receiver" and then gives an example for BEV of ROM102 rev 240.
If this is a ROM102 eeprom, and the example is for BEV, then it seems to prove the Slinger will work after the switch to N3 using a N2 image, which has been the big question in my mind.
Has anyone up and running noted what what ROM and rev level is being seen in the IRD?
In subsequent IRD updates, would it seem likely that there would be a check implemented by BEV and DN for N3? If so, then the Slinger would need to be reporting itself as an N3 ROM.
Any ideas?
Thanks,
Cover