MobileRead Forums - View Single Post

pepe2602 · 10-28-2011, 12:11 AM

Only a few days after releasing FW 1.27 iRiver released this new FW update.

Reports have been from one brave user who succeeded to install it.

To Frostschutz: Well spoken, Sir! Good advices that techies should follow.

But: Many down-to-earth users will not have the ability to dig through thousands of lines of linux-code as you have.

And:

Who in his right mind would name a patch file in the same way as the original OS?

Who in his right mind would name all update-files the same (storyeb07.hex) so no one can distinguish between different versions?

Who in his right mind would give the user not a single line of text desribing how to install things? It would cost the writing of 20 lines of text for a readme-file.

What good software practice is it, not checking the integrity of a patch/update before installing the same?

What good software/hardware practice is it, not having a way from recovering from faulty updates?

A lot of questions remain unsolved ...

10-28-2011, 12:11 AM	#106
pepe2602 Junior Member Posts: 6 Karma: 10 Join Date: Oct 2011 Device: iriver story hd	New Firmware V 1.28 for story HD (Basic) Only a few days after releasing FW 1.27 iRiver released this new FW update. Reports have been from one brave user who succeeded to install it. To Frostschutz: Well spoken, Sir! Good advices that techies should follow. But: Many down-to-earth users will not have the ability to dig through thousands of lines of linux-code as you have. And: Who in his right mind would name a patch file in the same way as the original OS? Who in his right mind would name all update-files the same (storyeb07.hex) so no one can distinguish between different versions? Who in his right mind would give the user not a single line of text desribing how to install things? It would cost the writing of 20 lines of text for a readme-file. What good software practice is it, not checking the integrity of a patch/update before installing the same? What good software/hardware practice is it, not having a way from recovering from faulty updates? A lot of questions remain unsolved ...