Hey Drew,

Thanks for that tip...it worked! All is well again. I'm still very curious what that was about and would love to hear any theories. If it's of any "evidentiary value," NSP reported only 27% memory usage after the hard reboot. Then after the configuration update, it was back at 58%, roughly where it had been before all this.

You know how the remote seems to have something that functions like a cache, i.e., some actions are a little slow the first time you use them (after a fresh download) but then they're faster in subsequent use? Maybe something there gets corrupted or doesn't flush properly, resulting in erroneous memory reporting? Just a thought...might be WAY off but just trying to figure this out.