![]() There are cases where Integrators are purchasing only the board and not the chassis, so setting the chassis fields is treated to the same argument. In these cases, they will want to be the ones setting these fields and not be blocked from doing so because Intel already programmed them. ![]() The issue is that there are quite a few Integrators who take the NUCs and rebrand them as their own product (after adding some meaningful hardware and/or software into the mix). Not setting any of the chassis and system strings is, in my opinion, incorrect, but in this too my opinion was ignored. ![]() Ah well, I am retired now and can look back on it, um, more fondly. To me (and obviously to you ), "Don't Change" means, well, "Don't Change It!". This wasn't my choice, but I lost the debate. The "Don't Change" was supposed to indicate that, unless you click on it and make a change, the field's contents were to remain with the previous setting (i.e. I laughed for a good five minutes after reading your response! We (marketing and development team members) debated long and hard on the interface to use when we were designing the product.
0 Comments
Leave a Reply. |