bug: weird issue with filenames that end in ~1

Emerson · Post by **Emerson** » Tue Nov 23, 2010 5:31 pm

DC2 seems to have a problem processing files (for hardlinking at least) if the filename is of an 8 character format ending in ~1 (ie. ######~1.ext).

It seems to be some sort of weird edge case, not sure what's going on. Watching DC2 using ProcMon it appears that there is a NAMECOLLISION return value from certain file operations that isn't usually there for hardlinking operations that succeed.

Fool4UAnyway · Post by **Fool4UAnyway** » Tue Nov 23, 2010 9:14 pm

These ~1 filename endings are typical 8.3 "conversions" of long filenames for backward compatibility to allow DOS 8.3 filename access.

DV · Post by DV » Wed Nov 24, 2010 9:03 am

Will test this - I'm reviewing the hardlinking process in the current beta due to other issues you raised so I'll see if we can improve things.

Emerson · Post by **Emerson** » Wed Nov 24, 2010 7:24 pm

Fool4UAnyway, yeah, I realize where these names come from. It just seems that DC2 has issues processing them for some reason or another though. I was just bringing it to DV's attention.

DV · Post by DV » Wed Dec 01, 2010 3:55 pm

This bug fixed in upcoming beta 3

Emerson · Post by **Emerson** » Wed Dec 01, 2010 9:12 pm

Cool

Out of curiosity, what was happening?

DV · Post by DV » Thu Dec 02, 2010 8:51 pm

Not completely sure - it was just throwing an exception when renaming the temp file back to the 8.3- seemed to think the file already exists. Must be something going on at a deeper OS level.
Anyway, i've changed the process a bit and that seems to have cleared the problem.