Whats wrong with this picture?

[acerunner]

Got this error while copying files from a network drive. This is running on windows 7 RTM. Can you spot what's wrong?

Conclusion: Windows 7 is not without its bugs.

 

[Anti-Hero]

The filenames are different.

 

[Burning1]

The filenames are different.

Not entirely. afm160~2.jpg is very likely the same 8 character file name used for AFM1600L-Top-Vertical.jpg

Long File Name support is actually a major hack of the old FAT file-systems from the MS-DOS days, which created these kinds of file management strangeness.

It does surprise me that this got past Microsoft's QA department.

 

[Anti-Hero]

Ah good catch! When I took a look, I didn't realize that was a tilde. On a first glance it looked like a hyphen.

 

[acerunner]

i fully understand the DOS style naming convention, sometimes called 8.3 (ie 8 char, followed by period, followed by 3 char extension). However that has long been obsoleted since the FAT filesystem existed. Windows should be able to tell the difference between a long name and a short name. XP figures it out just fine. Now why would windows 7 convert the files to 8.3 format before comparing the file names? To me, that's a bug.

I still run some DOS software which is where these files came from. Also, lots of software generate backup files or temp files that make use of the tilde character. I hope windows 7 isn't always going to confuse that.

 

[Burning1]

i fully understand the DOS style naming convention, sometimes called 8.3 (ie 8 char, followed by period, followed by 3 char extension). However that has long been obsoleted since the FAT filesystem existed. Windows should be able to tell the difference between a long name and a short name. XP figures it out just fine. Now why would windows 7 convert the files to 8.3 format before comparing the file names? To me, that's a bug.

Yes, it's obviously a bug.

No version of FAT exists that supports long file names without the hack described in the link. Since most removable media is still formatted with the FAT32 file-system, Windows 7 still includes VFAT long file name support. Given that the file in question is being copied from the 'Z' drive, I suspect the original media is either VFAT formatted, or a network share.

 

[GhostRider]

anyone remember the good old C:\ONGRTLNS.W95 ads?

http://www.allbusiness.com/marketing-advertising/marketing-advertising-channels-print/7146512-1.html

why mess with a perfect thing, eh?

 

[Burning1]

It took me a while to figure out what "C:\ONGRTLNS.W95" meant.

Either the ad makes an effective point, or I'm very slow.

 

[acerunner]

lol "C:\ONGRTLNS.W95". good one!

 

[Diezel]

Not entirely. afm160~2.jpg is very likely the same 8 character file name used for AFM1600L-Top-Vertical.jpg

Long File Name support is actually a major hack of the old FAT file-systems from the MS-DOS days, which created these kinds of file management strangeness.

It does surprise me that this got past Microsoft's QA department.

+1