"Synchronise failed while writing player configura

I know everyone is saying this is cosmetic but I am unable to connect to my EMPEG via USB at all now. On my Win2k machine it now locks up EMPLODE: I start emplode, it shows the Found Player box but then that box disappears before I can do anything. And now Emplode is locked up. Shows 0 CPU usage but is listed in my Applications on Task Manager. I have to kill emplode.

On my XP Pro machine, it found the player, I clicked OK and then it says there is no player attached (or something like that). Now, Emplode can not see my EMPEG at all. It just does the searching (flashlight animation) but it does not lock up.

I am going to try Ethernet today/this weekend. How do I hardcode the IP on the EMPEG? I tried looking for that last night but could not see it on 2.0b3.

Thank you.

I would advise changing back to 1.03 until the the next beta release is available. Lots of synchronisation problems have been fixed.

Rob

I know everyone is saying this is cosmetic but I am unable to connect to my EMPEG via USB at all now.

What you're describing is not the "known cosmetic bug". The known cosmetic bug was one very specific error message. What would happen is the synch would be successful, but at the very end of the synch it would say "Timeout error writing player configuration" or something like that. In that particular case, it was harmless and the synch was still fine.

But if you can't connect with USB at all, it's a different thing. Go ahead and do as Rob suggested and downgrade the player and Emplode to 1.03 until the next public beta is released.

The sync is OK, but the session cookie is dead...

Marius (Escort Cab + Mark II)

In reply to:

---

What would happen is the synch would be successful, but at the very end of the synch it would say "Timeout error writing player configuration"

---

Actually it did happen at the very end and all seemed well. The files i selected for removal were removed. I did not add files at that time.

I switched back to 1.03 and all my Settings were lost: Dimmer, Volume, Equalizer, etc.

But, since my files are okay, I am happy. Although I liked the 2.0b3 features. I may try going to b3 again and then only try ethernet to see what happens. Even if I lose my files, I figure I can reload 1.03 and just load the files on. I know that works via ethernet!! :)

I went ahead and put 2.0b3 back on and synched using ethernet and all seems well. Synching works without problems. Although I got an Email from Dave about turning logging on and then sent the results back to him (i assume of the USB failure...)... I will try that tonight...since I can just go to 1.03, then back to 2.0b3 and use ethernet only. :)

I have noticed there are less collisions on my hub with 2.0b3 in comparison to 1.03.