New
#1
Can I safely change NtfsDisable8dot3NameCreation in registry
Some of my file "full-path-names" are getting rather long (230 characters)
- a bit too close for comfort to the absolute 260 (including drive, folders, separators, file-type, null char, 8.3 file name.
I have always assumed there was no limit to (character-length) of nested folder etc ... but I have discovered I am wrong.
Windows File Name Restrictions – Why a File Name Can be too Long
Limits on the Length of File Names and Paths -- Table
Microsoft Technet Registry value "NtfsDisable8dot3NameCreation"
Can I safely disable creating 8.3 truncated file-names (stored along with the "normal" full-name) ?
- from my reading, 8.3 is a hangover from 16bit programs
In HKLM\SYSTEM\CurrentControlSet\Control\FileSystem (key)
Value Name:- NtfsDisable8dot3NameCreation
- what would be the safest "data" value without sabotaging my file system
- the table of parameters in the Microsoft Technet "Descriptions" table is not as clear as I would like.
- I am aware the 8.3 name is only 12-characters) ... but every "inch" counts.
In the meantime I am trying to workout how to restructure our filing "system"
- we use long integers as part of folders + file names to indicate series/changes to AutoCad files
- long term I am considering creating an Excel file to open files using VBA (we still use Excel 2003)
Would appreciate any advice :)
-----------
SPECS
Win7 Home Premium 32 bit
AutoCad 2006 32 bit
Office 2003 (32 bit)
Last edited by bawldiggle; 10 Apr 2015 at 18:12. Reason: corrections