Originally Posted by pachinko
1. Did you have a chance to try what MKS13 suggested, that is, other Flash Drive brands? That’s new to me, and definitely worth a try, especially if both Flash Drives that you’ve tried are the same brand.
2. Maybe the update files you tried are corrupt. I have my copy of 124R in my Hightail account
, which you’re welcome to download and try.
3. Perhaps try the other USB Port.
4. I only wait about 10 to 15 seconds when I Cold Boot, and never have a problem.
Has anyone else attempted reverting to an older version from 132R? I will give it a try once I update to 132R, but I’m still at 124R for the time being. I sure hope that the developers have not destroyed our ability to revert to an earlier version should we not like the new version, or the new version is horribly buggy. IMHO, our having control is a great selling point.
My two Flash drives are a (1) a sony brand and (2) a micro center brand. These are quite old but work w/ my Win 7 PC but just have limited storage.
I only have one USB port on my DVR+ model. That's where the HD is attached.
When I initiated the cold boot, (power on while pressing front button/release/press again), The DVR+ responded properly and found my Flash drive in the USB port. It presented the load screen and started to load the file from the USB Flash drive. It got to the end of the load, paused and then "aborted" the update and showed an Update Fail message and then proceeded to do the update again. It cycled through this routine 3 times then looked for an IP address connection to get the most recent update from the server. I manually aborted the load at this point.
I am not sure what the problem is but I did resolve my Slingbox issue. I prefer not to mess w/ any of the firmware files especially when they are automatically updated.
FWIW I think the 124R firmware file on the Flash drive was ok as I downloaded it twice from the drop-box link and also tried the 114R release too w/ the same results.
I too would like control but a better option might be to allow the owner to flash back to previous firmware from the settings menu. This may/could provide good trouble shooting information for the developer.
Slingbox allows end users to upload custom " .bin" configuration files used for specific device configurations. Probably not applicable for DVR+ owners. These " .bin" files sit on top of the firmware and/or are called by the firmware. Somehow when Slingbox did their latest firmware update, they corrupted some of these pre-canned " .bin" files so my workaround was to write my own for the DVR+. Everything now appears to work as before.
I am still testing and since both the devices (DVR+ & Slingbox 500/350) must work together, it is difficult to isolate problems especially when both devices do automatic firmware updates.
Too many users are impacted when a firmware update goes sour. In my case it was just a certain sub-class of users so none of the tech service reps even knew of the problem (especially Slingbox as it was eventually determined by me that it was a SB corrupt file).
My suggestion is only do Firmware updates for major changes (like once a year) and have some other way to do minor updates more often (then maybe roll into a major update). Also use some naming convention to show the date of the firmware release and/or complementary configuration " .bin" files. This way an end user can easily go back to the previous settings/configuration until the new release gets fixed.