File Transfer Software for Windows 7?

[Kushina]

So I'm always transferring images and other large files (50GB+) and during this time I also always end up running updates and I figure why not restart and then I see the built in Windows 7 file transfer dialog box saying 35 hours remaining...

Something which would allow me to pause, close/put on hold, restart would be good.

 

[NikolaeVarius]

BitTorrent

 

[Kushina]

This is more for transferring stuff between drives and network drives.

 

[RampantAndroid]

There is no way a copy over the local network of a single 50GB file should take 35 hours. Unless you're on 10MBit.

 

[Elixer]

There is no way a copy over the local network of a single 50GB file should take 35 hours. Unless you're on 10MBit.

Or the destination is a really, really slow device.

 

[mikeymikec]

So I'm always transferring images and other large files (50GB+) and during this time I also always end up running updates and I figure why not restart and then I see the built in Windows 7 file transfer dialog box saying 35 hours remaining...

Something which would allow me to pause, close/put on hold, restart would be good.

Robocopy. When you run the command, you can do Ctrl+C, then re-run the command later and it'll (essentially) pick up where it left off (typically the command is used to make one folder structure match another and be completely up-to-date, so when it notices that a load of files already are up-to-date, it'll skip past them).

It can do other clever things too like retrying a file that it couldn't access the first time, and waiting a length of time between retries, or neither if you prefer.

It comes with all versions of Windows starting with Vista. The basic command is this:

robocopy C:\sourcepath D:\destinationpath /MIR

The destination path will be created if it doesn't already exist.

I normally run it like this:

robocopy C:\sourcepath D:\destinationpath /MIR /R:0

So it doesn't retry any failed files. If I'm copying user profiles, I throw in /XJ so it avoids NTFS junctions that have been set up. /XD excludes specific folder names (and their contents). /XF excludes specific file names (wildcards work).

Another advantage of using it is that it preserves file dates.

 

[BonzaiDuck]

Robocopy. When you run the command, you can do Ctrl+C, then re-run the command later and it'll (essentially) pick up where it left off (typically the command is used to make one folder structure match another and be completely up-to-date, so when it notices that a load of files already are up-to-date, it'll skip past them).

It can do other clever things too like retrying a file that it couldn't access the first time, and waiting a length of time between retries, or neither if you prefer.

It comes with all versions of Windows starting with Vista. The basic command is this:

robocopy C:\sourcepath D:\destinationpath /MIR

The destination path will be created if it doesn't already exist.

I normally run it like this:

robocopy C:\sourcepath D:\destinationpath /MIR /R:0

So it doesn't retry any failed files. If I'm copying user profiles, I throw in /XJ so it avoids NTFS junctions that have been set up. /XD excludes specific folder names (and their contents). /XF excludes specific file names (wildcards work).

Another advantage of using it is that it preserves file dates.

Robocopy is good. I forgot the name of the app you can dow. . . I remember . . . RichCopy.

 

[RampantAndroid]

Or the destination is a really, really slow device.

Sure...but that's not Win7's problem, and paralellizing the copy won't help either.

 

[Ketchup]

This is one big reason I got a new (new to me anyway) router not to long ago. Fast Ethernet just wasn't cutting it anymore. Just make sure your devices are Gigabit.

Robocopy is also a good suggestion for the OP.

 

[mikeymikec]

Re: performance - I'd check (with say Task Manager) that the transfer is going at a consistent and decent speed. If Windows is sticking to its guns when it reckons '35 hours', then my guess is that the NIC/NIC driver at one end is doing something stupid.

Maths isn't my strong point, but based on the (reasonably recent) hardware I have here, a network running at 100mbit/sec, a 50GB file should take just under 75 minutes to transfer (based on my observation that the transfer speed in megabytes/sec is normally about 11.5MB/sec)? However my previous AM3 build could 'only' do about 10MB/sec via the same network).

Other factors that might affect transfer off the top of my head:

- One machine hasn't enough memory and gets caned by say Windows Update during the transfer.

- One machine's AV is doing something stupid that is messing with the transfer speed.

- One or both machines' disks need defragging (or is on its way out).

Taking a look at the performance tab of Task Manager on both machines during the transfer might result in some interesting evidence being found.

 

[paulcheung]

To the OP,
If you always have to copy large files between 2 computers, I suggest you get a USB portable hard drive, copy from one computer then copy back to the other. That is what I do. it also give me a backup in the portable drive in case the computers caught and virus.

 

[DrGreen2007]

Replicator from Karens Power Tools, free and works great

 

[Jembo]

Teracopy is good at this too. I recommend the old version though. Version 3(I think) ended up packing features into the premium model. The version before that has everything you need. Keeps detailed logs of any failures without quitting. Love it.