dhh;324424 Wrote: > 3. If the issue truely was a client software, device firmware mismatch, > which makes no sense because I wasn't connected to the client while the > firmware was updated, then couldn't there be a hash value that the > device compared in the firmware and desktop client software, with a > mismatch giving the user a warning or message of some sort? Actually this doesn't seem to make sense. Firmware updates are tied to server updates. You said earlier "If the firmware is updated on the device (Squeezebox 2) before the SqueezeCenter is updated, the volume can get stuck on full, regardless of setting." -- How exactly did you update your firmware before updating the server? Your suggested resolution of updating SC first and then the firmware is the way it normally works.
-- aubuti ------------------------------------------------------------------------ aubuti's Profile: http://forums.slimdevices.com/member.php?userid=2074 View this thread: http://forums.slimdevices.com/showthread.php?t=50398 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
