Glad it worked out for you!
If your goal is to prove that writing the EXER 02 values into the NVRAM works, that's already been verified.
There have been multiple conversations about it on TekScopes groups.io. Which one are you referring to? The last one I recall was the thread "tektronics 2465b 400mhz nvram battery info" where someone verified it with a 2467B in April.
Although I didn't mention it in a post a couple of weeks ago (reply #1182), I also verified that both the EXER 02 and the GPIB dump of the cal data was an exact copy of what's in the NVRAM on a 2445A. But I didn't bother mentioning it because it had been done before.
It's also been verified on a 2465, although that scope is a little different since it doesn't use a Dallas NVRAM.
So, we have all the versions covered for this series (A, B, and plain).
More verification is always nice, but it may not be worth the extra hassle if you don't already have a programmer or other equipment to do it.
That being said and you still want to experiment, I'm willing to drop your BIN data in a fresh DS1225AD-150 for you for free, if you want to send me the chip and a self-addressed, pre-paid return envelope. PM me if you want to set this up.
I was not sure yet that it had been verified. It seems to be a touchy subject for some members over at TekIO when asked, as can be seen on some past messages. In a situation where a scope lost the calibration constants, some of them will tell you to rather invest the time in getting the scope properly calibrated than to thinker trying to rebuild the cal data with exer02 values, as it might not work, or at best be no longer accurate and on the dot anyhow. I get their point, but then again, my scope is intended for hobby use only, not on a bench at NASA. Also, I can understand the interest in using Exer02 data in a situation where someone lost the cal data, and has no intentions to send the scope out for calibration, or does not have the means to calibrate it himself. 10x better, maybe even 100x better to have your own Exer02 data to play with than having to use a third party bin file from another scope just to bring yours back to life.
I did not see the message thread over there that you mentioned. Will look it up later.
In my case I am just trying to do it mostly as an academic exercise, and of course to possibly avoid having to read my aging NVRAM to replicated the data as a first choice. As it has happened before to some people, the programmer itself might kill the data while trying to access it if the backup battery is on its very last legs. Yes, I've also seen the PDF about repowering the internal battery, and its of course yet another option to go.
Thanks for the offer to program a DS1225 for me and mail it back, I will keep it in mind. Thing is I don't have a programmer, and this would probably the only instance I would ever use it, so trying to decide if I should order one. I have read the GQ-4X4 programmer is probably the one to get, as it will handle both the DS1225, and also the FRAMs in case I decide to thinker with them in the future and get rid of the battery backup issue for good. Or if anyone can suggest a better alternative programmer I'll be happy to listen to recommendations.
Yesterday went again over my handwritten list of the Exer02 values and checked them against the video which I also made. Turns out that in one data pair I transposed two numbers (I had written 2647 and should have been 2674). Other than that I'm good to go, and I updated your BIN template file as well.