I'm attempting to run a simple "cp" command from the Terminal app in Mac to move a file over to the mounted C:\ of my Windows bootcamp installation: cp testFile.txt "/Volumes/C/Program Files/SomeFolder/testFile.txt" I've worked out the original permissions errors I was having, but now I get the following error: cp: /Volumes/C/Program Files/SomeFolder/testFile.txt: Bad file descriptor I just played around with this some more and I believe the issue is related to how "SomeFolder" was created. I created it from the Mac OS terminal app. I can see this folder in the Windows File Explorer. However if I perform an ls on the Program Files directory, it is not there. Furthermore, if I try to do a mkdir again to recreate it, I get an error saying it already exists. So it seems that folder was created in a special way through parallels. Any hints on this? Thanks. Some system details: Running Mac OS 10.8, Windows 7 originally installed as bootcamp, and Parallels version 7.0.15106
This is an OS/file system issue.The cause is the directory paths in the system is longer than 255 characters (including spaces).You may see the error "Can't copy or delete file.".The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters," under the following circumstances:Opening an assembly with .NET ReflectorExporting source code for an assembly using an add-in such as FileDisassembler,or FileGenerator.There's a lot of additional softwares which can fix this problem like Long Path Tool. http://PathTooDeep.com Long Path Tool can simplify and probably end your problems in unlocking, managing and renaming files that appear to have a long filename.
MattAG, is you bootcamp vm running when you are trying to copy file ? What exactly does ls -la "/Volumes/C/Program Files/SomeFolder/" show ? Also a problem report could be usefull (Help->Report a problem).
