I have a folder containing a large number of files on D:\dev\tools\eclipse. I decided to move it to my C: drive (at the same path) for speed, since C: is an SSD.
The drag-n-drop move refuses to copy 4 files with extra long names saying they're too long.
- OS is Windows 7 Pro X64
C:is a 250GB SSDD:is on an LSI 9260 hardware RAID card with 3 2TB drives configured as RAID-5 (3.6 TB effective capacity)- Both
C:andD:are formatted NTFS.
Why would the identical path length be OK on the RAID drive but not on the SSD?
ADDITIONAL INFORMATION:
If I use the "Copy as Path" context menu item (Shift-right-click) on the file, on D: it copies a path that has 8.3 short names substituted for path elements longer than 8 characters, while on C: it uses the full names.
However, fsutil shows both drives having 8.3 names enabled
C:\Windows\system32>fsutil 8dot3name query c:
The volume state for Disable8dot3 is 0 (8dot3 name creation is enabled).
The registry state of NtfsDisable8dot3NameCreation is 2, the default (Volume level setting).
Based on the above two settings, 8dot3 name creation is enabled on c:.
C:\Windows\system32>fsutil 8dot3name query d:
The volume state for Disable8dot3 is 0 (8dot3 name creation is enabled).
The registry state of NtfsDisable8dot3NameCreation is 2, the default (Volume level setting).
Based on the above two settings, 8dot3 name creation is enabled on d:.
They're identically configured, So that still leaves the question of why Windows would use 8.3 names in one but not the other.
