I don't know if you'd classify this as a bug or not, but when syncing from an SMB mounted drive, Emplode uses 100% of the CPU and almost none of the network bandwidth. I figured it'd be just the opposite.

I'm using XP, everything over 100BT switch (except empeg on 10BT, of course). It's an 800mhz P3.

Just seems odd that it would need so much cpu for what would seem to be a primarily network based operation.

Also, we need a cancel on syncing ... though I doubt this is possible. It seems crappy that I have to kill the app whenever anything bad goes wrong while syncing up.

g
_________________________