I agree...a boot sequence entry code would be TERRIFIC! What I mean by that is when forcing a download instead of using 02468, we could use 01357 or some other number to load a firmware set we like. Now....there is one really big problem with this....D* cannot support multiple firmwares...they can hardly (and poorly at the CSR level) support the current national release. If they are put in the position of trying to support two or three or four versions at the same time....it's a formula for disaster. This multiple firmware would be fine as part of "Cutting Edge"....i.e., totally unsupported release candidates ...which is how the RC's are handled now. It is forbidden to call D* with any issue on a release candidate. So, they could theoreticaly (although it's still a scary thought, and would require some code tweaking) allow those of us testing release candidates to choose from among several options, and continue to test. It would be VERY important for us to test two versions the same way and report the results...which increases the burden on us, to be sure, and on them to try to make sense of what we are saying. Keep in mind, the goal of the RCs is to TEST, not find one we like and sit on our hands. Part of the agreement of forcing downloads of RCs is to report on performance of the RC. We're VERY lucky they let us do this....we get to play (and benefit from improvements) and they get a lot of "data points" that help them develop the code. Again, all my comments are related to the "Cutting Edge" aspects. I could go on for weeks about the other issues (including support) that have plagued others more than me.