gibvictory
Inspired
that will update Axe-Edit, not really affect the Axe itself.
Duh.
that will update Axe-Edit, not really affect the Axe itself.
Duh.
If something gets corrupted in the download process, that should be the container (the .zip file) not the continent (the .syx, and the other stuff). If the .zip gets corrupt you simply cannot extract what's inside.
There is no way to have the inside stuff of a zip file "corrupted"... Or the zip is corrupted or it's valid (and valid what's inside too).
So, If something goes wrong upon a firmware update it should be:
1. In the extraction process. The .syx gets damaged once you extract the file to your computer. If that was the case, the verification process in the Axe should stop the update... But for some reason passes the verification process.
2. In the update process. Something goes wrong when the Axe is updated. The verification process in the Axe should stop the update... But for some reason passes the verification process.
So... To me the redownload thing does nothing. People says that it actually works so I'm not going to stop anyone to do it.
I bet the reinstall is the thing that makes it work as it should. It just happens that you redownloaded the file again to reinstall.
In the end, a redownload cost seconds so there is no harm to do it... But it makes no sense.
If something gets corrupted in the download process, that should be the container (the .zip file) not the continent (the .syx, and the other stuff). If the .zip gets corrupt you simply cannot extract what's inside.
There is no way to have the inside stuff of a zip file "corrupted"... Or the zip is corrupted or it's valid (and valid what's inside too).
So, If something goes wrong upon a firmware update it should be:
1. In the extraction process. The .syx gets damaged once you extract the file to your computer. If that was the case, the verification process in the Axe should stop the update... But for some reason passes the verification process.
2. In the update process. Something goes wrong when the Axe is updated. The verification process in the Axe should stop the update... But for some reason passes the verification process.
So... To me the redownload thing does nothing. People says that it actually works so I'm not going to stop anyone to do it.
I bet the reinstall is the thing that makes it work as it should. It just happens that you redownloaded the file again to reinstall.
In the end, a redownload cost seconds so there is no harm to do it... But it makes no sense.
The fact remains many of us have had issues with firmware installing and/or not performing correctly.
I do wonder if it is an old data over write issue.
Publishing a SHA or MD5 hash of the download would ensure that the file, as received, was the same as the one published.