When I'm using my empe... er, Rio Car in my car, it has to rebuild the database every time I power up (i.e. turn on my car's ignition). It never did this before I switched to 2.00 beta 7; it was even fine for a few days after I made the switch.

When I hook my Rio Car up at home, it plays fine. No database rebuilding, everything appears to be intact. However, when I attempt to run Emplode, I get "Failed to open database connection" at the "Connecting to player" step. So, I am now unable to alter the contents of my Rio Car unit.

Also, why can't I select any visuals? When I attempt to do so, nothing happens.

Tony (ynot) just posted about a database corruption on his unit. I've also had a constant rebuild problem (when connected at home though). It was suggested that deleting the playlist files from the drive and then rebuilding with emplode should fix it up.

In my case I was able to sync to fix the problem.

Find the other thread (I believe in the bugs forum) and take a look. I'd probably downgrade to 2.0b3 if I were you, try and connect, force a rebuild by making a change to a temp playlist, make sure everything's working fine at home and in car and then try upgrading to 2.0b7 again.

Bruno

I'd probably downgrade to 2.0b3 if I were you, try and connect, force a rebuild

I think you meant downgrade to 1.03 and force a rebuild.

Bruno wrote:

"I'd probably downgrade to 2.0b3 if I were you, try and connect, force a rebuild by making a change to a temp playlist, make sure everything's working fine at home and in car and then try upgrading to 2.0b7 again."

I did this. Got the same error, i.e. "Failed to open database connection." I really hope that #!@%ing beta 7 hasn't ruined my database.

I'd like to know why my player has to rebuild the database every time I start my car, but at home it plays without rebuilding. Anyone know?

In any event, what can I do now, assuming my database is beyond recovery? Do I need to perform some kind of fundamental wipe, and re-upload all of my music to my Rio Car unit?

The database is very hard to corrupt; it's just all the *1 files containing song information built into a packed format.

If you use hyperterminal, you can force a rebuild like this:

rwm
rm /drive0/var/database
rm /drive0/var/playlists
exit

(don't do a "rom" before the exit; the player will rebuild the database and save it back to disk, then remount read-only).

Hugo

If this is still happening to you, head over to the Bug Reports forum and look at the thread entitled "Database size mismatch error." Roger has some steps you can take which will help get to the bottom of this problem (a problem I had yesterday as well. How odd is that?)

Is there a solution that I can effect with the Windows OS? I don't have Linux installed on either of my machines.

Is there a Windows tool available that will allow me to perform lower level operations on my empeg?

In the meantime, I'll try downgrading to non-beta, and see how that works out.

Yes you can use hyperterminal and the bash prompt to do that. (If you have developer installed) hyperterminal is under accessories in windows. Let us know how it goes!

I have downgraded to 1.03. This seems to have fixed everything; I can alter the contents of my player again, and the interminable in-car database rebuilding is gone.

Thanks for your help, all!

I have downgraded to 1.03. This seems to have fixed everything; I can alter the contents of my player again, and the interminable in-car database rebuilding is gone.

Ah, good. You might be OK to upgrade to 2.0b7 again at this point if it has some features you can't live without. If you run into trouble, you can always drop back to 1.03 again.

Use of Hyperterminal Windows terminal emulator to access empeg shell prompt is covered in FAQ (of course, you can use some other terminal emulator as long as you set it up properly).