I'm really tired and in a hurry, so this may not be written very eloquently.... sorry....

I have had lots of problems with network syncs too. I also have a 10/100 autosensing switch.

Digging around, you can find quite a few others with the same issues, and it isnt just with 2b7.

I also had it when transferring large amounts of data. Rather, it was more pronounced when transferring large amounts, but happened off and on anyway.

My solution was to use USB, which is a shame, 'cos the whole LAN thing would have suited me better.

I *did* find a page which lists error codes and documents in heaps of detail likely problems and stuff. I will post it when I find it again.

Just wanted to say don't lose hope, and dont be disheartened by people telling you you're wrong. I got some flak when I bought this same thing up, and had people "in the know" telling me I was wrong and there is no problem. Thing is, quite a few people do get it, under uncannily similar circumstances.

I am in no way knocking the Empeg/Riocar - it is a fantastic product and those involved have well and truly outdone themselves in every respect and continue to do so. I just find it odd that people who all find similar problems under similar circumstances should get scorn heaped on them and get accused of not knowing what they're doing or being somehow responsible for it. Or even just flat out deny the problem.

Which seems odd to me - people don't go around reporting errors for fun.

I would suggest trying a 10 megabit hub, rather than a switch - preferably a commonly used one of a "good"/reliable brand. Failing that, get a straight crossover cable and plug straight into the back of one machine. I haven't got round to trying either of these options properly, 'cos USB worked so I went with it.

I *REALLY* haven't looked at much info about it, but I think it may be something to do with the transfer protocol Emplode uses not being friendly or robust with "unstable" connections, and depending on how our switches handle the data, it may goad Emplode into unhappiness. And stuff. Would also be *possibly* relevant theory in that some XP USB drivers are dodgy, thus reproducing the problem.

By the way, I commend you on your reporting - the spider solitaire reference was a good call. You reported every factor you can see, whether they seem relevant to you or not. A lot of people wouldn't have said that for fear of sounding stupid. I'm an IT consultant, and the number of times troubleshooting has been made harder by someone not mentioning factors of a problem just because they didn't want to or something are numerous to say the least.