Trailblazer said:
For my problem, do you think that reflashing would solve it, or is this a 'send it in' type problem. Have you ever seen this?
I have seen this exact screen before and it has been reported on the thread - just never spontaneously occurring. As izeman related, in these cases a re-flash always fixed it. If you send it back the first thing they will do is re-flash it, so it might as well be done by your hands.
So - you might
email Grin Tech about you issue and request that they process your cable order with all due haste. They are good about this stuff and you will get it really quickly. Do the flash and chances are that all will be well.
But - here's the thing - Setup expects the values of certain parameters to be in certain ranges -- it always
stores 'good' values and so expects them to still be good when it
fetches them again. In select cases, if a stored value gets trashed for some reason, Setup may refuse to operate properly (you can't save a new value) because it can't understand the old wonky value.
The problem arises because the 'NoCal' firmware versions like Prelim6 don't really initialize all values. If a bogus calibration value lingers, things may not work 100%. Justin has fixed a lot of these entry issues, and there aren't any new posted problems, but here it is just in case you have a second dose of Bad Karma...
If this happens you will need to do as izeman outlined and go back to B19 (available
here) which is a full memory image and will initialize/clobber everything - including all factory calibrations. This is really a last resort. But once done, you can then flash with Prelim6 which drops in the new code but leaves a few calibration values unchanged and with acceptable values as set by B19. With a bit of luck, you won't need to go all the way back to B19....
EDIT - Oops - got your issue and rscamp's screen confused - I actually haven't seen your exact failure before, but I think the re-flash remains the best next step.