Support and General Use > Hardware

Sansa Clip+: cleaning filesystem, which files are (not) important?

(1/2) > >>

Marnes:
Hi

I just installed rockbox 3.13 on a refurbished clip+ with firmware 01.02.18. Everything's working nicely, like it did on my previous clip :thumbsup:

I like to keep my filesystems and such neat and tidy, and would like to remove any unnecessary files from my rockboxed clip+. This is the current filesystem root:


Obviously anything inside .rockbox aside from themes and such is important.

Does anyone have an idea about the other files?

* DID.bin
* MTABLE.SYS
* SYS_CONF.SYS
* UPGRADE.FIN
Are they still involved in any way in the player's operation or are they still important in some other way, or do they serve no real purpose anymore? Is anyone running their clip+ without these files? (I'd rather not try myself because I'm afraid I might brick it if I'm wrong)

Thanks for any info

johnb:
The only thing needed is the .rockbox directory. All of the files you listed can be deleted (and will be re-generated if you boot into the original firmware).

However, you should install the development build instead of 3.13. This is way outdated (lots of improvements over the years).

Marnes:

--- Quote from: johnb on September 16, 2016, 01:50:24 PM ---The only thing needed is the .rockbox directory. All of the files you listed can be deleted (and will be re-generated if you boot into the original firmware).

However, you should install the development build instead of 3.13. This is way outdated (lots of improvements over the years).

--- End quote ---

Thanks

Is using the development builds safe? I know from being a programmer myself that development builds are not normally used as-is for good reason, unless the rockbox devs made it a habit to run tests and everything before publishing on the development branch (making it more of a beta). :P

Marnes:
-removed, nvm-

saratoga:
The releases are just 3 year old development builds, so they're at least as safe as that. 

Regarding your problem, USB is not very stable for some people in the old builds. You can reboot into the Sandisk firmware, check the disk for errors, and then put a newer build onto it.

Navigation

[0] Message Index

[#] Next page