I wanted to copy a large number of files from a ntfs disk attached via usb, to my external hfs drive. When I opened a cmd window do use xcopy, the xcopy failed. Doing a similar thing with windows explorer works, but it is cumbersome, as it is really slow. Z:\volumes\bdf\dc>dir test Volume in drive Z is Shared Folders Volume Serial Number is 0000-0000 Directory of Z:\volumes\bdf\dc\test 02/13/2008 03:08 PM <DIR> . 02/13/2008 03:08 PM <DIR> .. 0 File(s) 0 bytes 2 Dir(s) 179,555,008,512 bytes free Z:\volumes\bdf\dc>xcopy x:\dc\*.* /s/e/d/c File creation error - A device attached to the system is not functioning. Unable to create directory - Z:\volumes\bdf\dc\test 0 File(s) copied Z:\volumes\bdf\dc>xcopy x:\dc\*.* /s/e/d/c File creation error - A device attached to the system is not functioning. Unable to create directory - Z:\volumes\bdf\dc\test 0 File(s) copied Z:\volumes\bdf\dc>
Hello, please, try to create a new folder inside that folder where you are trying to copy files via cmd. Run md test2 inside the Z:\volumes\bdf\dc\test> folder. Will it be successful?
Some diagnosis done Hi, I was experiencing the same issue and did some digging around. It seems that Parallels Shared Folders is behaving differently from other filesystems in a certain way. Hopefully Parallels can fix it. Here's part of the support e-mail I sent. This is Parallels support ticket #637977. Adrian Reproduction instructions: 1. Mount your MacOS Home Directory as U: under Windows using Parallels Shared Folders. 2. Open command prompt. 3. (In some local drive) mkdir testfolder 4. attrib +A testfolder 5. xcopy /E/I testfolder u:\Desktop\testfolder Results: C:\data>xcopy /E/I testfolder u:\Desktop\testfolder File creation error - A device attached to the system is not functioning. Unable to create directory - U:\Desktop\testfolder 0 File(s) copied The same command works: a) If you do not use 'attrib +A' or b) If you instead mount the home directory as an SMB share using MacOS X's built-in Samba. Diagnosis: Using Process Monitor to see the system calls which xcopy.exe makes: xcopy is failing because two successive calls to the Windows 'QueryBasicInformationFile' system call are failing with the error code 'FAST IO DISALLOWED'. Judging by the behaviour of SMB filesystems, the first call may fail with this error code, but the second should succeed. Because of this, xcopy is unable to read file attributes for the newly created folder within the Parallels shared folder. It is therefore unable to determine whether it has successfuly set the 'A' attribute. It therefore has no choice but to bomb out. (All that, of course, is speculation).
I doubt they will address this. I filed a ticket also against this, #443831 on February 16th 2008. No reply on that one.