Wasn't there a thread recently on the official board talking about it being dangerous to flash the firmware in the Red box, and if it fails the prom has to be removed from the board and reprogrammed manually? It sounds like the Red box doesn't have this second processor. If the key checking routines are in this second processors code that would sure explain why the Red boxes don't need keyed drives.
Any thoughts?
I originally took this to mean that the newer "non-Red" phatboxes were designed to be safe from a bad firmware flash (i.e a dumb user unplugging the DMS while flash was happening), because the initial boot always used the protected firmware.
So I thought it was put there to ensure the Phatbox was ALWAYS in a position to check if the modifiable firmware was to be upgraded on this reboot or not. A good way of eliminating the inevitable return of PBs for re-flashing after a bad flash...
But you have raised a good point, it might also imply that the "blessed-drive" checking is in there too.
And hence does not apply to Red Phatboxes.
So, the BIG question: can you upgrade the user firmware using a non-blessed drive? (i.e. the forceupdate file exists in root of PHTSYS on a non-blessed drive)
If you can, then we know that the first boot check is for a firmware upgrade and only later (probably in the linux code somewhere) is the blessed-drive checking.
If you can't, then it must be the protected firmware that is doing blessed-drive checking as it's first task.
Anyone care to try? Might help narrow things down...