Whenever I synchronize my empeg it locks up, meaning that the synchronizing logo stops moving on the screen. This happened the first time while I was uploading a file. Now anytime I try to synchronize, it does the same thing. Even if I just make a change to configuration and synch. The error message in emplode is: "Synchronize failed while writing player configuration. An established connection was aborted by the software in your host machine. (error 0x80072745)"

I have to unplug the player to get it to reboot. If I then try to connect with empeg, it stays on the checking media step for several minutes. After that it goes into standby mode, while the software says waiting and eventually times out. I have to unplug it to get out of standby mode.

It has the same behavior under emplode and Jemplode. I reflashed the Hijack kernel, but it didn't make any difference. I am running 2.0b11 with Hijack v251 on an Mk2a.

The player seems to function properly otherwise.

Does anyone know what would cause this? Is there any way to check the file database on the player or rebuild it?

You might be having this problem. Check that first, and get back to us on it.

I have never used the Favorite visuals feature before. Also, I don't see anything weird in the config.ini file.

I don't have the developer kernel installed. Should I still install it and remove the file?

Thanks,
Chris

are you using usb in windows xp?

I had your same problem. I solved it putting the player in standby mode before sync.
With this trick I uploaded 10gb+ without problems...

I am using ethernet. I tried it under W2k and XP.

Greetings!

Note: I always have trouble with syncing while running hijack. I suspected it was because of the disks that I was using. No one else seemed to have the problem, so I was just putting off trying to fix it, until I got the button kit and got that installed. I found that it was a problem strictly with hijack, and that the default kernel was fine.

You might want to try flashing back to the unmodified kernel (available on Mark's sourceforge page) and try using that. Also, if you had to pull the plug to reboot out of the lockup, you will have to fsck the filesystems during sync, so emplode will enter its disk check and stay there for a while. But it should sync cleanly. After you are done, put the hijack kernel back on.

Symptoms I see:

- Sync: with any tool, ethernet or USB (haven't tried serial). While running hijack, the sync fails in trying to remount the disks writable. Usually the error appears trying to delete the old configuration. No recovery available, requires pulling the plug on the empeg. This, of course, does nasty things to the filesystem requiring an fsck on the next sync.

- Shell: While in shell, if you mount the drives writable, it seems fine. However, significant disk access (uploading, copying, moving or deleting a lot of files) will again lock the player as above. There are no visible errors generated.

- Environment: Hijack 2xx and higher. Currently running 251. Mark2a. ReserveCache set in config.ini at 32. Empeg software 2.0 beta 11, but I saw this problem with 7 also.

I tried the suggestion of putting the empeg into standby before synching, but it still didnt' work. So I flashed back to the unmodified 2b11 kernel and synch while in standby, and it seems to be working now. I have done three sucessful synchs. Later, I will try it with hijack reinstalled.

I just started having this problem.. I never had it before, but here are the two factors that have changed (maybe it will help diagnose).

1. Before I always connected via a crossover cable - now I'm trying with a simple hub.

2. Before I was using my RioCar and now I'm using my Mk2 empeg.

I did a little experimenting...

With HiJack 265 and 2.00B11, I had this problem on a hub. I switched to a crossover cable and still had the problem. I installed 2.00b11 again and it was fine. Then I installed hijack 266 and it was still fine. Could this have been because of HiJack 265?

I guess I spoke too soon... with HiJack 266 it hung after a few sync's... (but it gets further in the process). This is fucking awesome - I've done 6 "disk integrity" checks today (not intentionally) trying to get this to work... I should have gone back to USB... This has eaten my whole day...

i had the same problem with xp over ethernet. i found that if i unplugged the ethernet cable, connected with serial, added a new song and synchronised that worked ok. then i connected again with ethernet and it worked fine - transferred over 600mb.

I'm thinking that somehow my filesystem got messed up.. I did a fsck and all is well now. I had a bad chip on my Rio and that may have messed things up as well... ?