- Joined
- Nov 26, 2004
- Messages
- 913
- Reaction score
- 38
- Points
- 28
- Location
- Oklahoma
I asked this question in another forum, but never got an answer so I thought i would give it a try here.
While doing some cataloging and editing of a music collection I noticed an odd thing regarding re-naming files. Every now and then i would run across a file that would not let me re-name it until after i rebooted. I was using iTunes to do the cataloging, but I don't think iTunes had anything to do with it as I had an open window to the drive with the files and was doing the actual re-naming there, not in iTunes.
To head off the obivious, yes I know about permissions and locking files, but this was not the case. I used the "file info" function and made sure the files were not locked and were set to read/write. Yet, i still ran across a few files that could not be re-named until after i rebooted.
My question is why... is this possibly a glitch/bug/feature of OS X? Has anyone else come across this problem and can tell me what is up?
While doing some cataloging and editing of a music collection I noticed an odd thing regarding re-naming files. Every now and then i would run across a file that would not let me re-name it until after i rebooted. I was using iTunes to do the cataloging, but I don't think iTunes had anything to do with it as I had an open window to the drive with the files and was doing the actual re-naming there, not in iTunes.
To head off the obivious, yes I know about permissions and locking files, but this was not the case. I used the "file info" function and made sure the files were not locked and were set to read/write. Yet, i still ran across a few files that could not be re-named until after i rebooted.
My question is why... is this possibly a glitch/bug/feature of OS X? Has anyone else come across this problem and can tell me what is up?