after update, Ipod 5.5 taking a long time to load

[playitleo]

OK, I had messing up my Rockbox'd ipod a bit, and decided to un-install it, then Re-installed 3.5.  Works great now, except it takes at least 30 seconds to load up when first turned on (can still see the Rockbox splash screen).  It is not "committing database" either. 
When I was using 3.4, it seemed to turn on in about 5 seconds or so.

Not sure if it is due to me screwing with the database options (all I did was set it to "Load to RAM").

[karashata]

I would imagine that would be why it's taking longer to load, because it's pulling the database information into RAM from the hard drive...

If you want it to start up faster, try turning that off, unless you prefer to have the database respond faster during normal use and are willing to wait a little bit longer at start up for it to be loaded...

[playitleo]

Sounds good, I will turn it off and see if that helps any.  Thanks for the response.

I get confused about how I should update the database and somehow possibly corrupted things last time around, had all kinds of database errors with albums and songs all in messed up order.  Weird stuff that ended in an "abort" error.  Also, Windows 7 scanned it and found some sort of file naming error and had to truncate a name or something.  So, I wanted to do a fresh install.

So, if I turn off Load from RAM, it will just update itself while the machine is running instead?  Does it really have to do that everytime you turn it on?   (and now I feel like I should put this in the database forum instead...)

[torne]

Load to RAM is nothing to do with updating the database. If you turn it off, then every time you *access* the database the disk will have to spin up and the data will be loaded from disk as you move through the database menus. If you turn it on, the entire database is loaded into ram on poweron so accessing the database is instant.

However, loading the database to RAM is done in the background, *after* the main menu has been displayed, so this shouldn't be causing your problem. Try turning it off anyway, but maybe you have changed some other setting as well?