Hm. I saw something similar a week or two ago, but I thought it was because I'd transferred some files from Windows...
Sometime since going to 10.3.6, the following very bad problem has occurred semi-frequently.
File/folder names will change on their own
For example, from:
Midland-DOW-Compressor-Room-PANO.mov
to:
Midland-DOW-Compresso#24BE9.mov
I know that such a name is typical of an app that makes a temp file (InDesign, Dreamweaver, etc.), but this is different. I'm talking about files that are NOT temp files, but the normal file that is just changing in front of my eyes. In fact, the above example changed from the original, to the wrong name and back to the correct and finally to the wrong in a span of one minute. I was actually able to watch it change on its own.
This is a major problem obviously since it breaks links and otherwise screws up files.
Here's what I know:
It only seems to be happening on files that I access over the network from our iMac file server (not a real server). I have not seen it happen on local files.
All machines are running 10.3.6, although one of them was upgraded a week after the others.
My machine (one of three) is the only one that seems to experience this so far, but the other two don't get used nearly as much as mine.
If I manually rename the wrong name file sometimes it will pop back to the wrong name again.
It seems to only have happened on long file names.
I have not yet repaired permissions, which I will do now, but I wanted to get a headstart on the problem.
Thanks for any help.
"You are" = you're • "It is" = it's • It's really that simple
Hm. I saw something similar a week or two ago, but I thought it was because I'd transferred some files from Windows...
OS X 10.8.2
MacPro 4-core 2.9Ghz
Apple 23" Cinema Display
After putting some more time into tracking down the problem, I can now duplicate it. Can someone please try to duplicate this with me? I am able to duplicate it on several machines.
1. Make sure all your machines are running 10.3.6
2. make a file with a long name (use any Adobe CS app, Flash or Final Cut HD). or rename an existing file to be excessively long (warning, you may lose the file, so make a copy)
3. save it over the network
4. open that long file named file over the network on your local machine's application. It should now show as truncated in that app.
5. Close the file, you will now see it renamed in the finder (on the network volume)
However, it is inconsistent. These applications do not exihbit the same problem. There are probably others, but I only tested a few.
Not Broken:
Fireworks
Textedit
So, something between how a given application sees and handles long file names over a network is now broken (my guess only since 10.3.6).
MAJOR BUG.
Finally, does anyone know where I can send this bug to at Apple?
"You are" = you're • "It is" = it's • It's really that simple
-An apple a day keeps Bill Gates at bay.
AIM: 0r8it
MSN: angrylittlemonkey@hotmail.com
It's a newly-discussed problem some are experiencing:
http://www.macfixit.com/article.php?...41115074502651
It seems to happen over networks and on FireWire drives.
2009 Mac mini 2.0GHz • 2010 MacBook Air 11" • 2010 MacBook Pro 13" • LED 24" Cinema Display
PowerMac G4 MDD dual 1.25GHz • PowerMac G4 Yikes! • iPad 2 32GB • 2 x iPhone 4 16GB • iPod Touch 8GB • iPod nano 1GB • iPod shuffle 1GB • AirPort Extreme dual-band • AppleTV
http://www.jeffhoppe.com
From that link, the thing that really struck me:
My guess on reading this is, that the file name on the server is not changed; the problem is only in the Finder's display of the filename (that we know of - moving the file with the Finder might do ugly things).only the Finder reported the filename being wrong. I fired up the Terminal and is a ls on the directory where the file resided. The Terminal always reported the file being named the original "This filename is way longer than thirty two characters.doc", regardless of what the Finder reported, even after saving changes on the distorted file in Word. Then, when I logged out of the server and logged back in, the Finder reported the name correctly again. Then, upon opening it in Word again, distortion continued in the Finder, but not in the Terminal.
Can you confirm this mindbend?
And - the filename you quoted was 31 characters. That was the old OS <= 9 limit, wasn't it?
Last edited by scruffy; November 16th, 2004 at 11:01 PM. Reason: html doesn't recognize a lessthanequal
What is the robbing of a bank compared to the founding of a bank?
-- Bertold Brecht
Sounds like whatever app you are using doesn't support long filenames. At least that's the characteristics of what would happen in OS 9.
MacBook Pro 2.16GHz Core2Duo 3GB RAM, G4 1.4GHz OSX Tiger 1.25GB RAM, Dual 2GHz G5 OSX Tiger 2GB RAM (freakin shweet)
Athlon 64 Windoze XP for school work (programming) 1GB RAM
dferns@macosx.com
I think this is a problem with the FIRST version of Microsoft Office v.X. I experience the same problem say in and day out with M$ Office v.X. To get around the problem, create your Borg Word document with a filename no longer than 32 characters. Save the file, quit Word, go to the Finder and rename the newly created file to whatever you want. Open the file, the filename will appear jumbled beyond recognition in MS Word; you can edit and save the file and it will be "OK" in the Finder, but "messed up in Word." It's a limitation Microsoft placed on us non-comformers with the first version of Borg Office; I don't think the newer versions have this problem.
Bookmarks