Current build manuals

[Datman]

I've realized now   that manuals are very important for the various builds, because they may contain unique informations about a function implemented in THAT build.

I have installed r29005 and modified/adjusted/optimized all. After that I have had some little problems, so I simply replaced the build with a new one:   many problems for wrong codecs and wrong messages and functions!

Could be the build manual put INSIDE the build in a "Manual" folder, with the build number clearly in the filename?

I think there is no solution, but do you have any hint to avoid future problems when using experimental functions? Is RSSI (%tr) only a build function or it is already a stable function in the 3.7?

In this specific case: will I have problems with my .fms if I'll install a future 3.8 o similar official release?

Thanks
Gianluca

Ooops... Another question:

Can I use a simulator some days older than the build? I don't understand why if I copy the .rockbox folder from my Fuze player (working!) to the simdisk I read (my translation from Italian language): "E:\...\simdisk\.rockbox\codecs\mpa.codec is not a valid Windows image. Verify by the installation disk."

[saratoga]

I have installed r29005 and modified/adjusted/optimized all. After that I have had some little problems, so I simply replaced the build with a new one:   many problems for wrong codecs and wrong messages and functions!

This means you didn't install the new build entirely, usually because you're using a broken unzip program, or stopped the install midway through resulting in a mix of new and old builds.

Could be the build manual put INSIDE the build in a "Manual" folder, with the build number clearly in the filename?

Manual == PDF instructions that tells you what all the things in rockbox do.  Is that what you're referring to?

[Datman]

Yes. I'm referring to the .pdf manual.

[saratoga]

Then sure, you can put it anywhere you want.  I usually just read it online. 

[Datman]

Could be the build manual put INSIDE the build in a "Manual" folder, with the build number clearly in the filename?

My idea was to distribute the manual in a specific .rockbox folder, so that downloading any build there is already the manual inside, with a name like 37r29005manual.pdf

[torne]

The manual is not automatically built as part of the build; we build the binaries for every code change but we only build the manual once per day, because it requires a lot of complicated tools that our build machines aren't guaranteed to have. So, there isn't an exactly matching manual for every build in the first place. Also, this would dramatically increase the size of the zipfiles... PDFs are big.

[Datman]

I understand. Thanks to all of you.
Gianluca from Roma, Italy

[Llorean]

Can I use a simulator some days older than the build? I don't understand why if I copy the .rockbox folder from my Fuze player (working!) to the simdisk I read (my translation from Italian language): "E:\...\simdisk\.rockbox\codecs\mpa.codec is not a valid Windows image. Verify by the installation disk."

You should never copy the .rockbox folder from a player to a sim. The sim and the player build are very different, and the codecs and plugins from one will not work with the other.

[Datman]

You should never copy the .rockbox folder from a player to a sim. The sim and the player build are very different, and the codecs and plugins from one will not work with the other.

!!! I had done many adjustments in wps, fms, cfg, config.cfg in the simulator; after all the work my idea was copying all as-is to the Fuze... What can I/can not copy-and-paste?
Can I copy eqs, fmpresets, langs, recpresets, rocks, themes, wps, config.cfg? What else can I copy or not?

If in the Italian.lng file some words are wrong can I edit with some trick without recompiling? Is there some program to edit it similar to a text file?

I have already done years ago a donation to Rockbox for my H120; I will do another for my new Sansa Fuze. I like Rockbox very much. God bless you for your work.
Some time ago I asked a Rockbox SW for the menu's of LCD TV's like my Samsung. A simple menu system, with computer editing and backup of TV/Radio channels and presets would be fantastic!... (without modifying codecs and video/audio processing).

[saratoga]

Can I copy eqs, fmpresets, langs, recpresets, rocks, themes, wps, config.cfg? What else can I copy or not?

You can copy anything thats not machine code, since your computer and your mp3 player do not use the same processor.  So text files and such are ok, most other things are not.

If in the Italian.lng file some words are wrong can I edit with some trick without recompiling? Is there some program to edit it similar to a text file?

You can edit the .lang file and compile a new .lng from it if I remember correctly.  I believe its documented in the wiki. 

[torne]

You should never copy the .rockbox folder from a player to a sim. The sim and the player build are very different, and the codecs and plugins from one will not work with the other.

!!! I had done many adjustments in wps, fms, cfg, config.cfg in the simulator; after all the work my idea was copying all as-is to the Fuze... What can I/can not copy-and-paste?
Can I copy eqs, fmpresets, langs, recpresets, rocks, themes, wps, config.cfg? What else can I copy or not?

Generally you should be okay to copy all the files that *don't* come inside rockbox.zip. You shouldn't be editing any of the files which do come with the build in any case, generally. Taking a simulator's .rockbox and extracting the target's rockbox.zip over the top of it, overwriting existing files, should be sufficient to preserve your settings/themes/etc.

[[Saint]]

Just to clarify/expand on Torne's post...

It is perfectly safe to edit a theme (.wps, .sbs, .fms, .rsbs, .rfms, .cfg etc) from the sim to the player.
As I understand it, all of the plain text files should be fine to copy.



[St.]