I think we have a simple misunderstanding here; that of OT vs reasonable place to ask for help. This is not an unreasonable place to ask for help; you just have to understand that it's a gamble as to whether anyone here has actually done the repair you're contemplating and can help. If not, then you'll not get anyone who can answer; it's that simple.
Other threads may be more likely to have users with the knowledge in question; that doesn't necessarily mean they have the time or inclination to help neo grok in fullness.
![Wink ;)](https://www.eevblog.com/forum/Smileys/default/xwink.gif.pagespeed.ic.cldandycH0.png)
I don't think it was unreasonable for neo to ask in here; he knows there are a lot of good-hearted folks who frequent the forum who would be INCLINED to help, and maybe even able & willing to break it down into simpler terms he can more readily digest. This is often not the case with more technically-oriented threads.
When asking for help, you need to consider both; I think he just decided to ask here where he felt like he had friends first.
neo, I don't know enough about the data structure of the NVRAM in question to help you read it with an EEPROM burner; that was why I suggested you do the "shoot video of the memory dump from within the service menu" method mentioned in several of the threads I linked to when you first asked about this.
Right now, what I'd do is clean up the pins on the chip, install a low-profile DIP socket on the mainboard and then reinstall the DS1225 to see if the scope still appears to work properly. If so, get that video back up of the data ASAP.
Cheers,
mnem
I fought the lawn and the lawn... LOST!
![Grin ;D](https://www.eevblog.com/forum/Smileys/default/xgrin.gif.pagespeed.ic.QVVz6XIT20.png)