Hello -- Thanks for the info -- I was using the /g option -- it was cranking at about 50,000 kb/s -- towards the then end of the copy it was consuming most of the cpu -- a suggestion would be
to add a /w option to "wait" some time before the next r/w operation. Thx