 Short Filenames, 8.3 Windows naming convention |
Welcome Guest ( Log In | Click here to Register a free account now! )
Register a free account to unlock additional features at BleepingComputer.com
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.| Important Announcement: We have two terrific contests running on the site that I wanted all our members and guests to know about. The first contest is the HP Magic Giveaway, which is underway as of November 28th. More information can be found at this topic, which will be updated very soon with further information. The second contests, is for the chance to win two Seagate FreeAgent external hard drives. More information about this contest can be found here. These are both amazing contests and I suggest everyone submit an entry for them. - BleepingComputer Management |
  |
 Jun 10 2004, 03:50 PM
Post
#1
|
|
 Member  Group: Members Posts: 38 Joined: 5-April 04 From: TX Member No.: 81  |
|
 |
 
|
|
Jun 10 2004, 03:56 PM
Post
#2
|
|
 Bleep Bleep! Group: Admin Posts: 29,464 Joined: 24-January 04 From: USA Member No.: 3 |
It is on by default for win2000 as well. Has it ever been disabled in the past that you know of?
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation What is the value of that key in the registry? -------------------- Lawrence
|
|
|
|
|
Jun 10 2004, 04:03 PM
Post
#3
|
|
|
Member Group: Members Posts: 38 Joined: 5-April 04 From: TX Member No.: 81 |
It is on but only with default Win2k folders and files. Which is really confusing because that means it is 16bit. here is how to disable it.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem Change or add the following value: Data Type: REG_DWORD Value Name: NtfsDisable8dot3NameCreation Value: 1 It was at 1 by default. We put it to 0 and it changed nothing. We created files with long names before and after the regitry setting( you must reboot for it to take effect everytime you change it.) I am also looking through all of our default DoD templates to find if it is a DoD setting. Then that means we can't do anything about it. We have other security templates as well and I haven't gotten to them yet. |
|
|
|
|
Jun 11 2004, 08:44 AM
Post
#4
|
|
|
Bleep Bleep! Group: Admin Posts: 29,464 Joined: 24-January 04 From: USA Member No.: 3 |
This is strange. With the registry entry set to 0 or even missing, then any new folders/files with long file names will also create the corresponding 8.3 variants. At least that is what it is supposed to do by the book.
As you said changes do not go into effect until you reboot and then create files. I would try deleting the key and then rebooting and seeing what that does. It really should work once you set it to 0 and reboot. From that point forward all new files on a ntfs partition should get the 8.3 naming convention. Have you tried creating a folder called "this is a long filename folder" on the c: drive, going to a cmd prompt, cd \, and typing dir /x ? This will show if the 8.3 file name is being created. You may have already done all of this, but just trying to cover all the bases. -------------------- Lawrence
|
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 4th December 2008 - 04:55 PM |
© 2003-2008 All Rights Reserved Bleeping Computer LLC.