XP SP2 USB2 Cannot copy, path is too deep

[AlanV]

I am trying to copy 500MB of MP3 files from an external USB 2.0 drive (FAT32) to the internal hard drive (NTFS) on my PC. I receive the message "Cannot copy, path is too deep" for some files, but for others going between the same two folders there is no problem. There are successful copies with longer filenames and larger file sizes, but particular files won't copy.

I have read a number of threads about problems with Windows XP SP2 (both home and pro editions), some having to do with network copying and some with USB or FireWire copying. There are lots of reports of this problem, but only a couple of solutions.

Since I am not networking, I doubt that the networking policies apply to my situation, particularly since I disabled Microsoft's firewall as soon as I installed the OS. (Zone Alarm works fine for my needs.)

The other solutions are to reseat or replace my internal drive cable, or to udpate the driver for my USB drive. However, most folks acknowledge that this is a problem with XP SP2 (did not occur with SP1 or prior). Searching microsoft.com for "path is too deep" does not yield any solutions.

Does Microsoft actually have an USB Removable Drive patch that I can't find? Or is there a non-Microsoft solution/workaround?

Thanks, Alan

[kev7555]

I am fully updated with SP2 on all of the systems in my network and I regularly transfer mp3, wma and other types of audio and video files via external usb drives with none of the issues you mentioned.

I doubt that SP2 is the culprit, though I'm sorry to say I do not know the solution.


-Kev

[Mesaeus]

Mmmmm.... I've been reading a really long thread about this problem (probably the same AlanV wrestled through, since it's the only one with some answers ). And to me it seems it IS SP2 related, at least I haven't seen anyone with SP1 or lower experience it, but lots of them do have it after installing SP2. The problem is that it seems to be a generic error message. It can happen for networks (usual fix : changing duplex/speed settings), copying between internal hard drives (some people report bad ide cables) and copying to/from an external(USB 2.0) hard disk. Now I've seen at least one person claim the problem is gone if he uses a USB 1.1 socket instead of USB 2.0. This may point in the direction of a bug only brought out by high speeds. The network connection error can also be avoided by lowering speeds, so my conclusion for the moment is that MS has another bug in SP2, but there's no solution at the moment. AlanV, can you try connecting to a USB 1.1 socket and see if it works ?

[AlanV]

Kev and Mesaeus,

Thanks for your replies. I'm convinced this is problem with Windows XP SP2 since it is a common thread in so many posts. No, I do not have a USB 1.1 socket to test, but I did solve the problem: USE A USB PORT ON THE BACK OF THE PC WHICH IS MOUNTED DIRECTLY ON THE MOTHERBOARD. I don't know why I didn't think of it earlier, but maybe NOW I'll remember it.

A couple of years ago I had what I thought was a problem with a USB printer under Windows 98 SE; it had worked OK, but then apparently stopped working because it would hang. The solution: remove the 4-way USB hub and plug the printer directly into one of the ports in the back of the PC (on the motherboard).

In January I bought a new scanner to along with my move to Windows XP, and one day it froze. I actually had to unplug the power cord to solve that one, but one thing the tech had me try: move the USB cable from one of the ports on the front of the case to one of the ports in the back of the PC (on the motherboard).

Now for the good part: I have been copying files back and forth to my USB external hard drive, but no individual file has been very large. The difference now is, MP3 files are ALL large. Tonight's solution: move the USB cable from one of the ports on the front of the case to one of the ports in the back of the PC (on the motherboard).

I will be re-reading my motherboard manual and doing more Internet browsing to find out why the ports on the front of my PC should behave differently than the ones directly on the motherboard, but for now this solution will work.