pipe output of CMD batch file different in W7 vs XP

[rperkins@wb]

I have several FTP windows batch jobs that have run for more than a year as scheduled tasks on an XP PC with no problems, now I am running them on a new W7 64bit PC and they run OK, but the piped output is not exactly the same. after the message "226 Transfer complete." there is an ftp status line that displays the bytes, Seconds & Kbytes/sec, this is the different line(s) between Windows versions (and in W7, if it is piped or not).
here is the line: ftp -i -s:C:\FTP-Check\Getomr.scr > C:\FTP-Check\ftp.txt
WRONG W7 piped output has this: 226 Transfer complete.
ftp: 4464218 bytes received in Seconds Kbytes/sec.
ftp> 2.072160.80close
RIGHT W7 not piped output and XP (both piped and not) has this: 226 Transfer complete.
ftp: 4464218 bytes received in 2.07Seconds 2160.80Kbytes/sec.
ftp> close
you can see that the (2.07Seconds 2160.80Kbytes/sec) have inserted into the ftp> close line. WHY?
Can anyone help?

[Squashman]

It is technically redirected output. Not piped.
Yes I bitched about this a few years ago on this very same forum. I am sure I could dig up the old thread. It seems to be fixed in Windows 8 as Foxidrive tested it on that OS and the logs show correctly just like they did in XP.

[rperkins@wb]

Squashman,
Could you dig up the old thread (if you think there is some sort of a fix or workaround)? We are actually just getting everyone set up on W7 64-bit and I don't even want to think about W8 yet...when we get new PC's, we put W7 on them.

[Squashman]

the work around is to use a version of ftp from xp or windows 8.