patches
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
patches [2024/08/22 11:23] – emozolyak | patches [2024/08/22 12:02] (current) – [Case A. Older firmware which don't generate link to patch] emozolyak | ||
---|---|---|---|
Line 5: | Line 5: | ||
To handle this, we developed a patch mechanism, to minimize possible issues. The process is similar to firmware upgrade with the code - you just get the patch code and apply it. | To handle this, we developed a patch mechanism, to minimize possible issues. The process is similar to firmware upgrade with the code - you just get the patch code and apply it. | ||
+ | ===== 1. Getting to the patch page ===== | ||
+ | Depending on your firmware version there are 2 possible methods to getting to the page. Both methods require **admin** rights to do this operation. | ||
+ | ==== Case A. Older firmware which don't generate link to patch ==== | ||
+ | In this case you have to enter right URL in the browser address field. | ||
+ | <code http> | ||
+ | http:// | ||
+ | </ | ||
+ | Here // | ||
+ | ==== Case B. Newer firmwares which create neccessary link ==== | ||
+ | The links to patches (if your system requres it) are located on the About page: | ||
+ | {{: | ||
+ | |||
+ | ===== 2. Checking and applying the patch ===== | ||
+ | Press //Check// button to check the patch. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | if the patch has been check, //Apply// button will become available. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | In case of failed check you may see similar message: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | After successful applying you will see the following message: | ||
+ | {{: | ||
patches.1724325831.txt.gz · Last modified: 2024/08/22 11:23 by emozolyak