Renaming a file by only changing case results in Permission prompt

We have a user who is unable to rename a file on their desktop if just changing a letter to upper or lower case. For example, if a user has a file "file123.txt" and they attempt to rename it to "File123.txt", the user gets a pop
up saying they need permission from their own account. However if we try to rename that same file to "file456.txt" it works no problem.
Some environment information:
-Domain Workstation and User
-The problem affects ALL files in the same respect
-The Desktop is redirected to the server
-The user does have Full ownership and Full NTFS permissions to their files
-The issue only happens when making the subtle case change, not fully renaming the file or adding to it
Lance

Hi,
I would say this is not what you think----this is an issue with your system. In fact, about Windows File
System, File and directory names can be up to 255 characters long, including any extensions. Names preserve case, but are not case sensitive. NTFS makes no distinction of filenames based on case.
If you have any feedback on our support, please click
here
Alex Zhao
TechNet Community Support

Similar Messages

Renaming a file to match a wildcard result

I am trying to compress a file using built-in Windows tools. I need to use a wildcard to read the file because the input filename changes slightly each day (to reflect the date stamp). The current batch file that I have found will ZIP up a file based on
a wildcard, but it gives the resulting ZIP output file a static name.
I need it to have the exact same name as the input file.
E.g.: if the input filename is blahblahblah02132014.txt, the output filename needs to be blahblahblah02132014.zip.
Please help?
Here is my current script:
set FILETOZIP=C:\Users\<my.name>\Documents\blah*.txt
set TEMPDIR=C:\temp738
mkdir %TEMPDIR%
copy %FILETOZIP% %TEMPDIR%
echo Set objArgs = WScript.Arguments > _zipIt.vbs
echo InputFolder = objArgs(0) >> _zipIt.vbs
echo ZipFile = objArgs(1) >> _zipIt.vbs
echo CreateObject("Scripting.FileSystemObject").CreateTextFile(ZipFile, True).Write "PK" ^& Chr(5) ^& Chr(6) ^& String(18, vbNullChar) >> _zipIt.vbs
echo Set objShell = CreateObject("Shell.Application") >> _zipIt.vbs
echo Set source = objShell.NameSpace(InputFolder).Items >> _zipIt.vbs
echo objShell.NameSpace(ZipFile).CopyHere(source) >> _zipIt.vbs
echo wScript.Sleep 2000 >> _zipIt.vbs
CScript _zipIt.vbs %TEMPDIR% C:\Users\<my.name>\Documents\someArchive.zip
echo Y | del %TEMPDIR%\blah*.*
rmdir %TEMPDIR%
pause

Thanks.
I can get the right filename now, with the ZIP extension and everything.
But I'm still getting the error when I try to rename the file. This line:
rename C:\Users\<my.name>\Documents\ZipFile.zip %OUT_NAME%
gives the following error when it executes:
"The syntax of the command is incorrect."
The environment variable %OUT_NAME% is not being set in your last example, but I think you were doing that to teach me something.
I used the code from your prior example again:
for /f "delims=" %%I in ('echo %IN_NAME%') do set OUT_NAME=%%~dpnI.zip
and I can see that the correct filename ("C:\Users\<my.name>\Documents\Blah blah blah 20140218.zip") is being set in the environment variable %OUT_NAME%. But again, when I go to rename "ZipFile.zip" to that new name, I get the syntax error. I think
it is because of the spaces in the filename.
Sorry for making this harder than it needs to be...

Help please, spacific file update only changed files when moved

I record live bands and file size can be very large when i make changes to files i want to save time and resources by only updating what has changed without replacing the whole file. when moving files from desktop to external drive.
say i have a file named "jam" that i add files to on my external drive then i copy it to my internal drive, do some edditing and add some files. when i move it back to external drive i want to update the "jam" file add the new files and changed files without having to keep track of the changed files and not transfer the files that havent changed. can anyone help?

Only files and folders below directory "/emmc" will show up in windows explorer.
You will also not be able to edit (add/delete) files to the /system/media/audio/notifications folder (or just about any folder above /emmc) . This is because you do not have administrator access (for lack of a better term) to the phone.
So, if it's that important to you, you'll have to find a way to tell the phone you're an administrator
Windows Explorer correctly identifies these as two separate drives. There is, after all, a built in drive as well as the swappable SDcard.
Sorry I can't be of more help.

Renaming a file in Finder changed with Snow Leopard somehow?

I've used an AppleScript for ages to:
1. choose a file (a screenshot)
2. prompt for a new name
3. File is renamed by Finder with new name
4. compose a command to copy it to another server
It seems Finder is not updating the "alias" to the file since I upgraded to Snow Leopard; this very code has worked for the last few versions of OS X:
set screencap to (choose file with prompt "Choose the screen shot: ")
display dialog "Enter new file name: " default answer "foo"
set newname to (the text returned of result as string)
set newnamepng to (newname as string) & ".png"
log "newname is " & newname & " newnamepng is " & newnamepng
log "screencap is " & screencap
tell application "Finder"
set the name of screencap to (newnamepng as string)
end tell
log "the name of screencap is now: " & screencap
set posixscreencap to the POSIX path of screencap
set scpcmd to "scp " & posixscreencap
log scpcmd
Here's what happens when I run it:
tell application "AppleScript Editor"
choose file with prompt "Choose the screen shot: "
--> alias "Einny:Users:swain:Desktop:Screen shot 2010-09-13 at 2.06.44 PM.png"
display dialog "Enter new file name: " default answer "foo"
--> {text returned:"newnameforscreenshot", button returned:"OK"}
end tell
(*newname is newnameforscreenshot newnamepng is newnameforscreenshot.png*)
(*screencap is Einny:Users:swain:Desktop:Screen shot 2010-09-13 at 2.06.44 PM.png*)
tell application "Finder"
set name of alias "Einny:Users:swain:Desktop:Screen shot 2010-09-13 at 2.06.44 PM.png" to "newnameforscreenshot.png"
--> "newnameforscreenshot.png"
end tell
(*the name of screencap is now: Einny:Users:swain:Desktop:Screen shot 2010-09-13 at 2.06.44 PM.png*)
(*scp /Users/swain/Desktop/Screen shot 2010-09-13 at 2.06.44 PM.png*)
For some reason the file alias "screencap" does not get a new name. Any suggestions?

When I run your script, the file name does get changed, it is just that the Finder is not keeping up with the script. There are a few fixes:
1) add a short delay after the rename (delay 1 seems to be enough)
2) use *System Events* instead of the Finder
3) add an update command after setting the name in your FInder tell statement (e.g. update screencap)
Note that an alias will still point to the same file item (even if it does have a different name), but the POSIX path of the alias object does need to be updated before you can use that.

Renaming NEF file no longer changes JPG file automatically (NOT BATCH RENAMING)

For the last year I have been able to select a file in Bridge under the 'Content' tab and in renaming an individual NEF file, Bridge would automatically change the corresponding JPG for me. Suddenly it no longer works and I have to change each file independently. Batch renaming still works fine, but I don't want to use that every time, as that is a bit conveluded to change one letter/number in the file.
Not sure if it was an update that changed something since the updates are automatic. I'm not finding anything in the 'Preferences' or any other area to change the setting back. How do I get it back to the way it was???

Hi Don, and a warm welcome to the forums!
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair. Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.

Batch rename song titles and/or change case

Importing cd's makes a mess of my song title format.
The most common problem is a mix of cases: Proper Case (Capital for each new word) is the most common, but sometimes it's all lower case or all upper case. Especially the last one requires a lot of typing, title by title. Using an external renaming program does not affect the titles within iTunes. Is there a way to do that?
Similar problem often happens to classical music. Some cd's mention the composer and/or performer in the title field, followed by the 'song' (track name). I want to delete the composer/performer or transfer them to the appropriate fields. Can I do that in one 'batch rename' action within iTunes?
Thanks,
Wim

reposted the question, so marked this one as answered

Moving files on share from Windows results in permission loss

Here's the setup:
-- Leopard, with shared SMB folders; specific user and everyone have read/write permissions for the share
-- Windows machine is accessing the share via the specific user & password, connecting fine
When I access the share from the Windows machine, and move files between folders, the file loses all permissions (they are set to 0000) so it cannot be read by anyone at all. The only way of getting access to them again (from either machine) is to chmod them back to 0644.
Copying files is OK, as is creating files and moving a folder from Win -> Mac. It only affects moving files between folders on the Mac.
Can anyone else confirm this, or is it a setup issue here?

10.5.1 has not helped the situation. Any ideas???

The file "Notes" was change with out my permission, how do I recover the erased notes?

The File with my notes in the IPhone (IPad as well) was changed with out me asking, there where some critical notes eliminated from this File, how can I recover this information??

Hide the App store via Restrictions. See:
iOS: Understanding Restrictions

Can't RENAME a file like Windows can?

Real easy. I just need to rename a file from this:
A2Capital.jpg
to this:
a2capital.jpg
I do this in Windows and of course every OS I have used since the 1990s at least. Why can't this be done in OS X 10.4.9?
I am on a network drive of a Windows Server, if that makes a difference. The error I always get is
The name a2capital with extension ".jpg" is already taken. Please choose a different name.
Oh, come on. This is an easy one, right?
It happens whether I click the filename or if I Show Info.
Mac Pro Quad 3.0 Mac OS X (10.4.9) I usually run Windows XP

OS X's filesystem, HFS+, is case-preserving, meaning
it stores the upper and lowercase characters of
file/folder names, however it's not case-sensitive
(unless you specify it as such when formatting the
disk in Disk Utility). In a case-preserving
filesystem, MyFile, mYfILE, myfile, and MYFILE all
reference the same file. There is no need to be rude
to Kappy, he was just trying to help. Here's some
reading if you want to learn more:
http://en.wikipedia.org/wiki/HFS_Plus
http://en.wikipedia.org/wiki/Comparisonof_filesystem
s#fn_35
http://en.wikipedia.org/wiki/Case-preserving
Note: HFSX in 10.3 added the ability to format a disk
as Case-Sensitive. If you didn't reformat your disk
when you got your Mac, it's Case-Preserving, not
Case-Sensitive.
I see what you mean by case sensitive. I think Macs and Windows are similar in this regard. All that means is that if I type in a command to run, or I type a filename to launch, the OS is forgiving if I say "BLaH.JpG" for a file that is really "blah.JPG" -- if it's on the hard drive like that already.
You bet. But in both Mac and Windows it seems, I can rename the file to whatever mixed case I want and get no errors.
I only have this problem on the network drive,
which like I said is a Windows 2003 Server share.
Because your question is in the context of renaming a
file on a remote Windows share, then all the talk of
whether HFS is case-sensitive or not doesn't matter.
I'm assuming the share you're connected to when
trying to do this rename is NTFS? Macs use Samba to
connect to Windows shares. I've never tried to do
what you're doing through a samba share. It could be
Samba, or it could be how you have your share set up.
It does look like a Samba idiosyncrasy. I have used Samba before in FreeBSD (a relative to Darwin/OS X) but I would have no idea if that was the case there.
Samba has traditionally had some oddities, bugs, and problems due to the nature of open-sourcing a Windows custom secret network system. But Macs do claim to be interoperable with other networks and systems. This can't be unusual. Lots of people need to connect to a Windows share.
Ha, to be honest, I don't think I would even try to setup a NFS share on the Windows server, and there aren't any UNIX servers at this location.
Who heads up the Samba stuff for Mac OS?

When using Quite Imposing Plus the resulting file is only given a Temp name which will be sent as the document name.

Our company has recently upgraded form Acrobat Professional 8 to Acrobat professional XI. We also use the Quite Imposing Plus plug-in in both versions. Now when using Quite Imposing Plus the resulting file is only given a Temp name which will be sent as the document name to the printer unless the imposed document is first saved. This was not the case in Acrobat Professional 8. I have attached a screen shots that shows an example.
Is there any reason why this is happening and how can we stop it.

Thank you for your advice although I think you may be incorrect as the naming of the documents made with Quite Imposing is correct in Acrobat 8.
After reading the comment below it would seem something has changed from version nine onwards.
Going forward we plan on changing the way we save and send our imposed documents to print but thank you for your time.

File Created time changes when file renamed to previously used name

Any ideas on this one would be very gratefully received:
I am trying to rename a file then create a new one with the original name, as part of a solution to roll over log files after x days.
I found that the new file had the 'created time' of the original file, which messed up the logic badly. I tried to unpick this by creating the new file with a new name, then renaming it. The new file got the correct created time initially,
but as soon as I renamed it to the original name, the created time reverted to the created time of the earlier file.
I even tried simply deleting the old file altogether, but every attempt to get a new file with the original name resulted in the created time being that of the old file.
I have used different filesystemobject instantiations for the old and new files, and I even tried creating the new file in a different run of the script, and in a different cmd session. The only thing that worked was logging out and in again before
creating the new file!
Since the created time attribute is not writeable, I'm struggling to get round this.
Here is a stripped out version that demonstrates it. I have put 5 second waits in, so you can watch the created time get reset in front of your eyes when the new file gets renamed to the old name (might need to add a column for 'created time' to Windows
Explorer)
(OS is 2008 server R2 Enterprise)
$logdir = ".\"
$logfname = "roll.log"
$RollAtDays = 0 # for testing - so it always creates a new file
If ( -not ( test-path $logdir) ){ $newdir = New-Item $logdir -type directory }
$logfile = $logdir+$logfname
$newlog = $logdir+$logfname+".new"
$fso = New-Object -comobject Scripting.FileSystemObject
$date = Get-Date
# if file exists, test whether it requires rolling over
If ( test-path $logfile ){
$fo = $fso.GetFile( $logfile )
$dc = $fo.DateCreated
$RollDate = $dc.AddDays( $RollAtDays )
# write-host "$dc $RollDate"
If( $RollDate.CompareTo( $date ) -lt 0 ){
  write-host "Roll"
  $newPath = "$logdir$date-$logfname"
  $newPath = $newPath.Replace("/", "")
  $newPath = $newPath.Replace(" ", "-")
  $newPath = $newPath.Replace(":", "")
  $fo.Move( $newPath )
  #$fo.Delete( ) #tried both renaming and deleting the original file
  start-sleep -s 5
# some code to create a file if one doesn't exist
If ( -not ( test-path $logfile) ){
$header = "Date"
$fso1 = New-Object -comobject Scripting.FileSystemObject
$ts1 = $fso1.CreateTextFile( $newlog, $True )
$ts1.close()
start-sleep -s 5
$fo1 = $fso1.GetFile( $newlog )
$fo1.Move( $logfile )  # this is where the created date gets changed back
#add-content $logfile $header
# some code to add a line to the log
[string]$logline = "$date"
#add-content $logfile $logline

I have to disagree with the assessment that creation time is not writable:
Get-Item test1.txt | select creationtime
(Get-Item test1.txt).CreationTime = '07/03/2014'
Get-Item test1.txt | select creationtime
CreationTime
3/20/2014 1:15:43 PM
7/3/2014 12:00:00 AM
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Good evening. When I try to rename a master file or export a master file, it only allows 9 spaces for my new name, even though Aperature 3 allows many more spaces than that for version names. This creates a lot of problems and headaches for me.

Good evening. When I try to rename a master file or export a master file, Aperature 3 only recognizes the first 9 spaces for raw .NEF files, even though it easily uses twice that many spaces for version names. I have a system in place that works really well for me, wherein by changing the file name I can recognize what's important to me just by glancing at the file name, no matter what system it is in, I do not have to open or mouse over anything to know what the file is. My files also arrange themselves in order no matter what file system they are in. Can someone please tell me if there is a setting, or something I am doing wrong, that prevents me from using a longer Master file name. I can't be the only person who would like to have his Master File names correspond to the name that appears in the Aperature library, and would like to use at least 16 spaces (numbers, letters, etc.)
Thanks,
Photo Al

Hi Frank,
As you suggested, I am attaching several screen shots. In the first one you can see how I set up my preset. I used "Custom Name" and "Counter" with a dot between the two drag ins, followed by "D90". I also have a dot to seperate the 8 digits in the Custom Name and make it easier to read.
I then click "OK" which takes us to the second screen shot. Here you can see that in the Example File Name everything looks perfect, and you can see I have clicked on "Apply to Master Files".
In the third screen shot you can see that the version in my library did in fact change correctly. With the "mouse over" pop up screen you can see, however, that the Master File name was changed to "1933.1017.NEF". It failed to carry the "12D90" and if I go to where my masters are stored that is exactly what the name was changed to.
In the fourth screen shot I attempt to export the master. You can see how my "Version Name" is set up.
And finally on the 5th screen shot you see in the File Name Example the name "1933.1017.NEF" once again, which when I export the master is exactly how the name will appear. Since I will export more than one file at a time , a (1) and a (2) etc., will appear at the end of the names because all the files are being given the same "1933.1017.NEF" name.
I hope this reply does a better job of clarifying my problem. I am anxious to see if this is something I simply misunderstood, or if I am simply doing something wrong.
Thanks,
Photo Al

Can't rename files/folders after changing extension of a file

This has gone on for a while and is quite the pain.
So I need to change the extension of a file. I change it, it asks me do I really want to do this, and I do. Sometimes immediately, and sometimes in a while, I lose the ability to rename a file/folder - I highlight it but can't type anything. Only a restart cures it, until the next round. Really annoying.
I've seen this syndrome posted here and there, but no real solutions. Any ideas welcome, I'm using 10.4.11 btw.
Thanks

Very Important, how much Free Space is on your Hard Drive first of all? Click on the Macintosh HD on the Desktop, then do a Get Info on it.
First, Safe Boot , (holding Shift key down at bootup), use Disk Utility from there to Repair Permissions, test if things work OK in Safe Mode.
Then move these files to the Desktop...
/Users/YourUserName/Library/Preferences/com.apple.finder.plist
/Users/YourUserName/Library/Preferences/com.apple.systempreferences.plist
/Users/YourUserName/Library/Preferences/com.apple.desktop.plist
/Users/YourUserName/Library/Preferences/com.apple.recentitems.plist
Reboot & test.

How do I import old FCP projects that have mysteriously changed to Linux Executable files? Is it as simple as renaming the files with the.fcp extension?

I had some FCP projects on an old G3 tower that I finally want to finish. I was able to grab everything, media, etc. to my macbook pro but all of the Final Cut Pro actual movies/projects have turned into "linux executable files" that FCP X won't import.
I tried googling this issue but didn't really see any good answers. Would it be as simple as renaming the files with the .fcp extension? I can't recall if my old version (really old) of FCP saves projects as .mov or .fcp files, but I'm assuming I'm not the only person this has happened to.
Thanks for your help!

I had some FCP projects on an old G3 tower that I finally want to finish.
What version of FCP was this? The project files can probably no longer be opened in the newer version of the OS. You could try adding the .fcp suffix, but I don't think it will help for this. Projects files are .fcp.
Regardless of the version, no legacy FCP projects will import into FCPX.
Media is a different matter. These are probably QuickTime .mov files. If these are appearing as Unix ececutables, they're probably not recoverable either.

"completion insight" and "change case as you type" won't work for sql file

Hi there,
Just updated to 3.1 on my Mac Lion. It's very likely a bug since it used the work with 3.0.
I have a "temp.sql" file where I store several queries. I start SQL Developer, open "temp.sql", connect to a DB but "completion insight" and "change case as you type" won't work anymore.
If I click in "Unshared SQL Worksheet", the new worksheet tab will work fine with completion and change case, but I want to use my temp.sql and save things there when closing the application.
To reproduce yourself the issue:
Open SQL Dev, connect to a DB (it will open a worksheet), do some queries and check that change case and completion are working, quit SQL Dev, but save the worksheet in a sql file before. Re-open SQL Dev and open the sql file. Connect to the same DB and try to change the queries or create another. Completion and change case won't work anymore.
About
Oracle SQL Developer 3.1.07
Version 3.1.07
Build MAIN-07.42
Copyright © 2005, 2011 Oracle. All Rights Reserved.
IDE Version: 11.1.1.4.37.59.48
Product ID: oracle.sqldeveloper
Product Version: 11.2.0.07.42
Version
Component     Version
=========     =======
Java(TM) Platform     1.6.0_31
Oracle IDE     3.1.07.42
Versioning Support     3.1.07.42

Well, it's partially working, if your sql file is big (like mine), say with more than 1000 lines, then, maybe because of memory usage, the automatic completion won't work as expected, though, sometimes, after a while, crtl-space would stil work.
So, the problem may have been addressed, but I believe this feature can be definitely improved.

Renaming a file by only changing case results in Permission prompt

Similar Messages

Maybe you are looking for