fixed bug where settings are not correctly deemed "unset" and so the default values are not used, causing the device to start up with invalid data in the settings.
the code was checking for 0xff in the first byte of each value to determine the "unset" status, but in my testing this was not always correct.
testing for [a-zA-Z] seems reliable enough, although it's not a very elegant fix.