That one is written to take advantage of several non-obvious facts.
As pointed out in another thread here, after renaming a directory, it puts a file of the same, original, name in its place.
This leverages an obvious programming error in the SO code -
It is only testing for the existence of a name, not of its type (file or directory).
But it is not possible to add filenames (new screensavers) as members of a file, only as members of a directory (folder).
Evidently the SO support code either does not check the error code from trying to put a new screensaver file into what is now a file.
The SO support code assumes that any error code that is returned means the (what was) /var/local/adunits directory is full.
Recall also that some firmware versions will "auto-brick" when /var/local fills up.
So in an attempt to avoid that situation, this exception to the SO support operation has slipped into the code.
@GM: If I failed to clearly summarize what is happening, please correct this description.
Two points -
- HarryT is correct, your Amazon account panel is the proper way to deal with the SO function.
- Don't forget to revert this change before next updating your firmware.