Quote:
Originally Posted by
jamie_123
I probably missed seeing the question, these files were created by tcpdump, with basic filename being * and a value that increments and creates a new file each time the file reaches beyond a value. These were created on a unix system and then moved to another harddisk without any trouble.
Tried that, get a response saying the filename is not valid or too long.
Upon further reflection, since you mentioned that even the windows file manager cannot remove the files, I don't think this is a cygwin issue. I now believe that the unix system used to create these files allowed you to use characters which windows forbids but which ntfs can handle.
Windows does not allow the asterisk at all. When creating a file which contains an asterisk, Cygwin translates it and in its stead writes a utf8 character that looks like a solid dot (which is a valid character as far as windows is concerned). When reading the filename, Cygwin then translates it back to an asterisk for cygwin apps. The windows file manager does not do this and will show you the solid dot.
From what you said about creating the files on unix, I suspect that it wrote a literal asterisk into the filename. The NTFS implementation supports the asterisk, but windows will not accept it when it reads it. And, since ultimately cygwin depends on windows, it fails as well.
If this is correct, the most expedient solution may be to mount that filesystem with the unix system that created it and rename those files.
Regards,
Alister