My player was working fine until I recently left it uploading 40+GB of music. Since then it has taken around 2mins to load the playlist file. My MP3 tags weren't all that tidy so I though it might be that. I removed ALL the music from my player and still it takes just as long to load the "empty " playlist.

Next step was to try going from V2.0beta11 back to original V1.02 that came on CD. Still...2mins loading playlist. Am i now stuck with this? :-(

Regards

Scoopz

Try deleting the /empeg/var/database file. Mine was doing that too. It was a corrupt playlist in the database.

BTW, don't worry. It will rebuild the file on it's first boot.

Thanks for the advice but I wouldn't know how to go about deleting it...? Just finished solving the problem, ended up downloading the test builder image and starting with two fresh hard drives, flies through it now, altough only got round to putting 3 albums back on so far :-(
Oh well only a day or so of uploading left! How quick should it do an album ripped at 320kbs via ethernet, is 5mins for 160MB about right?

Regards

Scoopz
(5am....should really start my coursework!)

Sounds pretty normal to me. I usually get about 25 Mb / Min. (Ethernet)

you know...you might not have needed to clear everything...
it sounds like you had the known config.ini growth error...
you can find that in the FAQ...it would have been an easier fix...
and if you use favorite visuals, it will happen again...
you should do a search for it in the faq, or Tony can find it for you

Just incase it hasn't been fixed yet...

A freeze on startup like this is usually a bad database as people here have indicated. Doing a full proper sync with no errors is the first step. That may resolve it. If not, download the developer image if it's not installed, and delete the file "/empeg/var/database"

To do this, hook the serial cable up, and follow the procedure in the FAQ for Hyperterminal (Just search for Hyperterminal to find it).

Then type this into it:
q
rw
rwm
rm /empeg/var/database
rom
ro
exit
--end commands--

That should take care of it.

I have FAQed this now, thanks.

Incidentally, I am not convinced that his problem was a database rebuild. Sounded more like a hosed scratch partition or disk drive troubles (or the former caused by the latter). Too bad he formatted the hard disks, now we'll never know.