Ever see this error when syncing?

<song> could not be synchronized. An existing connection was forcibly closed by the remote host. (error 0x80072746)."?

After that, the rest of the mp3s that are next to sync will time out...

- Jon

Oh my god... please don't tell me it's happening again. I had to reboot my empeg because it was taking forever to time out the rest of the songs after I got the error described above...

Now, the player sits at "Building music databases..." forever and I get "! tags.cpp : 61:Failed to open tags (0xc0041002)." from the console.

What the heck is going on, and is my empeg hosed again? I can't spend 2 days trying to reorganize my playlist again...

Help!

- Jon

Ok, another update... After about 5 minutes or so of rebuilding, the empeg comes up, but I can't get to it with emplode. Also, I'm getting "! mp3_decoder.cpp :1052:Failed to seek to offset 199633, error=0xc0044000
spindown_chunk_cache_runner.cpp: 292:Filling up space (44)
spindown_chunk_cache_runner.cpp: 292:Filling up space (40)" in Hiperterminal.

I think my empeg is in trouble. Mierd.

- Jon

Damn it. My player is now very hosed. I give up. I'm going to puke.

- Jon

You have to exit to a prompt 'q'

Then make sure the database & playlist files are deleted (I don't think the database will be there since the player rebuilds the db on each boot). I believe it's in
/drive0/var

now mount the file system as read & write. 'rwm'. The files are database, playlists. Someone correct if i'm wrong

Then 'exit' and the player will rebuild the database again (Like you saw before but this time it's able to write to the disk). Then sync with emplode once the player has restarted.

I had the exact problem your having and this is what I did to save my player

Greetings!

You would probably want to delete the "tags" file also, but I don't know if you really need to. Also, make certain you set the drives read only again (rom / ro), or you may force a full fsck. Sync with emplode, and you will be all set.

Those errors aren't anything to worry about.

Hey, Roger, from a quick check, it looks like those debug messages are finally removed from the serial line (in the internal beta). Is that true?

Hi All,

Well, I've had problems with the latest Beta stuff and went back to 1.03 and was pretty happy. Then, I started to really miss the new features and am now running B7 again... I installed Jemplode and am experimenting with it now.

Questions:

Does Jemplode have the same drag & drop issues that Emplode has?
Does Jemplode have any other critical issues that I should be aware of?
Can I safely sync large amounts of data with Jemplode?

- Thanx
- Jon

Does Jemplode have the same drag & drop issues that Emplode has?

What issues?

Can I safely sync large amounts of data with Jemplode?

You ought to be able to safely sync large amounts of data with emplode -- I transferred 40Gb onto my new mk2a (in one hit) the other night without any problems.

Perhaps if we had more information about your PC setup (OS version, etc) -- you may have mentioned it before (I don't recall), we'd be able to find out what's going wrong for you.

If you have a specific problem, you should send me the log files.

We'd like to make sure that v2.0 is at least as stable as v1.03.

You ought to be able to safely sync large amounts of data with emplode -- I transferred 40Gb onto my new mk2a (in one hit) the other night without any problems.

Others have reported crashes in Emplode/player Beta7 when synching large amounts of data. You, of course, get to use the latest internal build.

Does Jemplode have the same drag & drop issues that Emplode has?
What issues?

The one where it erases your files if you do a drag/drop "move". You know, I think you're spoiled by your internal builds and don't realize when the rest of the world has to keep living with the bugs you fixed three weeks ago.

And the answer is, No, Jemplode does not have that bug so you can safely use it.

Can I safely sync large amounts of data with Jemplode?

I have done about 20Gigs at a time with no problems. I haven't had any major issues with the last several builds of JEmplode but you should grab the latest version from Mike's preview site http://www.batmanthehorse.com/jemplode as the last release version was kind of buggy.

-Mike

Well, it's better than when we'd been using v1.1 for almost a year before the first public beta....