Invalid MS-DOS function

[lurk&jerk]

I've researched this all over the Net & no one seems to have a solution, blaming everyting from bad cd-rom media, to bad disks to excessively long file names.

In my case this happens when one drive is formatted in NTFS and the drive I'm copying from is formatted in FAT32. My guess is that the inability to copy files is related to the security streams in NTFS or file incompatibility.

For example, I can't copy the windows 2003 service pack from FAT32 to the NTFS drive, but XP SP and Windows 2000 SP copy just fine. If both drives are formatted in FAT32 I don't have this problem so I suspect this must be some kind of permission's issue. Anybody got a fix, the permissions are now set so that "everyone" has full control of the file. I tried adding administrator and it makes no difference.

Edited August 26, 2006 by lurk&jerk

[allen2]

If you're using an antivirus software, try disabling it before the copy.

[lurk&jerk]

Not running any anti-virus. The three files mentioned were downloaded from the same source, but from a different machine...

[Takeshi]

You haven't told us what the USB drive is, is it an ext. HD, or optical drive or memory stick. You haven't said either how you copy the files, in Explorer, using cmd commands or what.

And how about trying the same in another computer or using another ext. drive?

Whatever the cause is, it's not NTFS permissions.

[lurk&jerk]

It's an external 2.5" hard drive, if that makes a difference. But I've had this problem with USB sticks too. I'm using Explorer to copy files.

[jaclaz]

Try using ycopy:

http://www.ruahine.com/

http://www.ruahine.com/ycopy-file-copy-utility.html

How does Ycopy help?

Ycopy will copy the files from one drive to another just like a regular copy. The difference being that when it encounters a file that it can't copy (for whatever reason) it doesn't just give up. Instead it makes a note of the file(s) that couldn't be copied and moves on to the next one. When the copy process completes you are left with a printable report that you can then give to the client detailing the files which were unable to be copied. Making the job not only easier and much more predictable for you (you set it going and leave it to get on with the job, no more wasted time poring over directories and files) but more professional from the customers perspective (not only did you copy all their precious data that you could but you've given them a detailed list of files that were unable to be saved due to problems with the original disks file system.)

jaclaz

[lurk&jerk]

Interesting software but it does not give any additional information other than to say it can't copy the affected files.

[jaclaz]

Yep, the idea was just to check it wasn't Explorer related.

I'm using Explorer to copy files.

Next thing to check would be if you are (under current login) the OWNER of source files AND what level of permission is granted to your login on BOTH source and destination.

A thing you can try (WARNING, using second one is risky business), is to use programs like these:

http://grubletrang.com/Software.aspx?app=FreeFile

http://grubletrang.com/Software.aspx?app=PowerPrompt

To check if the files are busy, and to try using COPY, XCOPY or YCOPY from a command prompt with SYSTEM credentials.

jaclaz