Quicktime on Windows clients can't open files in folders with long names!!

Hi,
we've got a really strange problem. We have an Intel Xserve with Leopard Server 10.5.4 which is sharing files over SMB. Everything works fine, except Quicktime on Windows clients (XP Pro and Vista). It looks like the length of the folder names is the problem. If a single folder in the path to the mov has a name that's longer than 8 characters, Quicktime fails with "Error -43: A file could not be found."
x:\test1234\test.mov works
x:\test12345\test.mov doesn't work
Same for UNC paths. VLC on Win and Quicktime on OS X work without problems over SMB. Also the problem doesn't exist on other Samba based fileservers.
Any ideas? Perhaps some smb.conf tweaks to fix this?
Best regards

Just found this post
http://discussions.apple.com/thread.jspa?threadID=1360461&tstart=0
Seems like a well known problem

Similar Messages

Can't open file--"not compatible with this version"

I can not open a photoshop file, although it was saved with the same version. "The file is not compatible with this version" can someone help me.
thanks

hi kirsti
I use windows 7 and photoshop cs5
thank you
Am 02.05.2012 19:06, schrieb Kirsti Aho:
>
Re: Can't open file--"not compatible with this version"
created by Kirsti Aho <http://forums.adobe.com/people/Kirsti-CA> in
/Community Help Application/ - View the full discussion
<http://forums.adobe.com/message/4374618#4374618

Sherlock - Can't open files - Invisible Folders?

Not sure if it's related or not, but ever since I installed Tiger, my Sherlock for OS9 is messed up. Everytime I search for something, I can't open any seach results.....error says that they are in Invisible Folders. My computer at home is having the same problem. Anyone have any idea why this is happening? I still use OS9 at work until we can upgrade our hardware, and it's taking me tons of extra time to open files without just double-clicking in Sherlock.

I would try the usual first trouble-shooting steps on the X and 9 sides.
In Mac OS 9 (if you are booting directly to 9), do the rebuild desktop file routine by holding down the Option and Command (Apple) keys during startup until prompted to confirm. If you are running 9 under Classic only, the equivalent action is in the Classic panel in System Preferences, in the Advanced tab (button for Rebuild Desktop).
In Mac OS X, run Disk Utility and run Repair Disk Permissions. Also, I notice a command in the Disk Utility menu that is not on the window. In the Menu under File, there is a choice called "Fix OS 9 Permissions." I've never used that command, but it sounds like it might be relevant to your situation.

How can I open files in folders on iCloud Drive on my iOS8 device?

Have created folders and moved parts of my documents and pdf files to iCloud Drive on my MAC (Yosemite).
I can see the folders on my iOS device in Manage my iCloud, I can delete the folders and documents but HOW can I open the documents?
On Apples homepage I can see a simliar layout as when I log in to iCloud.com with my folders etc. plus the Apple Pages folders.
But where on my iPad / iPhone do I navigate to find the same?
Tried to login to iCloud.com on Safari on my iPad but it did not show my folders/files on iCloud Drive.

So what is the point of upgrading to iCloud Drive when there is no "Drive" on your iOs 8 device? I also added a new folder through Safari on desktop- as instructed by Apple- and I have no way of accessing it on the iPhone! This seems pretty bogus and a huge waste of time!
And... If Apple was developing an app for the "Drive" why have us upgrade to something you have no way of using?
And... I did try opening files through apps that allow it but I do not see anything.
And... Pages docs do NOT show in the "Drive" on Safari.
WHY?

Can't Open Files Or Folders By Double Clicking on Its Icon

I'm unable to open any file or folder by double clicking on its icon whether the icon is on my desktop or in a folder.
For example, I can't open my hard disk or any DMG file on desktop by double clicking on its desktop icon, but I can open it or any file or folder by control-clicking on the icon and then clicking on 'open'.
In my Finder, If I double click on an item in 'list' I can open it and in' columns' if I double click on an icon in 'preview' it will open/ launch and in 'cover flow' if I select an icon and double click on it there the file will open/launch.
I've repaired permissions, 'verified disk' in Disk Utility (no problems found),
run Disk Warrior as well as Applejack but the problem persists.... I just can't open by double clicking.
Anyone have any ideas?

Pretty weird...but I think I've heard of it before. I have no direct answer, but when weird stuff like this happens, I think of trying things like:
-boot from OSX DVD and check operation
-Time Machine backup
-Safe Boot - might correct something
-log out of user account and/or log into another user account, and see if doubleclick returns
-and the usual SMC/PRAM reset
I'm assuming you've diddled with the mouse/trackpad settings. Did you try a mouse?

Can't see location of item with long name in Spotlight search?

I can find the location of an item in a Spotlight search by selecting it and holding down the Command key, whereupon its position is displayed at the bottom of the Spotlight window.
However, if the item has a long name, the location is "offscreen" as shown in the screenshot below.
Is there any way of displaying it?

Somebody in another forum told me it couldn't be done in Spotlight but the word "no" must have kick-started my stubborn streak and I started hitting every other key I could find whilst holding down the command key to keep the incomplete location revealed.
Eventually I struck lucky when I pressed Return (or Enter) . . . the window below opened and I was able to do a "Get Info" on the item to find its exact location.

Itunes 11.1.5.5 can not add files or folders with accents?

Hello,
I'm using Itunes 11.1.5.5 and when I use the add folder to my library all the files with no accents are added propperly but all those folders or files with an accent (á é í ó ú) that are commonly used in spanish are not well recognized and will add only the song without all the related information (artis, album, etc) so it is impossible to add an keep ordered. This didn´t happened to me in previous versions. Can someone help with a solution? Is this a bug and how can I solve?
Thanks

More details for this scenario. With only one file (song) with an accent, all the songs on that folder would be added with no tags under "unknown album" no artist. The same will happen for all the songs within a folder with an accent.

I'm trying to export a raw image from lightroom 5.6 to Photoshop cc 2014 2.1. I right click to export menu in lightroom as I've always done to export to Photoshop. Photoshop opens, but it can't open file, window opens to find a file to open. I'd like t

I'm trying to export a raw image from lightroom 5.6 to Photoshop cc 2014 2.1. I right click to export menu in lightroom as I've always done to export to Photoshop. Photoshop opens, but it can't open file, window opens to find a file to open. I'd like this to export my lightroom images to edit in photoshop as it has always been able to do for me. What fix do you recommend?

Hi Ashley Clavette,
The Initial view setting works perfectly when the file is opened in Acrobat after setting the desired Initial View.
When you upload the file onto Wordpress, and view it on that website in the browser...it might be using a different pdf handler program which might be causing this issue ( it would be helpful, if you could provide the screenshot) , however when you download the pdf again from wordpress server...and open in Acrobat/Reader...then what exactly happens ? Does the pdf opens in the desired Initial View setting?
Rahul

Can't open files Windows machine from on OS X 6.8

I mapped a Windows 7 volume to my Mac. I can see the files and folders. However, when I try to open any file, like a plain text file, Mac reports that the file cannot be opened. I use the same workgroup, username, and password on both machines. I'm an Admin on the Windows box and have full control of the files. Thanks for some help!

See if these are any help:
http://support.apple.com/kb/PH10779
OS X Mountain Lion: Set up a Windows computer to share files with Mac users
http://support.apple.com/kb/PH10777
OS X Mountain Lion: Set up a Mac to share files with Windows users
Don't be concerned these articles refer to 10.8 -- the procedures have been the same for quite a while.

Vi error on nfs mount; E212: Can't open file for writing

Hi all,
I've setup a umask of 0 for testing on both NFS client (Centos 5.2) and NFS server (OSX 10.5.5 server).
I can create files as one user and edit/save out as another user w/o issue when directly logged into the server via ARD.
However, when I attempt the same from an NFS mount on a client machine, even as root I get the following error using vi;
"file" E212: Can't open file for writing
Looking at the system.log file on the server, I see;
kernel[0]: add_fsevent: no name hard-link! dropping the event. (event 2 vp == 0xa5db510 (-UNKNOWN-FILE)).
This baffles me. My umask is 0 meaning files I create and attempt to edit as other users are 777, but I cannot save out edits unless I do a wq! in vi. At that point, the owner of the file changes to whomever did the vi.
This isn't just a vi issue as it happens using any editor, but I like to use vi.
Any help is greatly appreciated. Hey, beer is on me!

Hi all,
Thanks for the replies
I've narrowed it down to a Centos client issue.
Everything works fine using other Linux based OS's as clients.
Since we have such a huge investment in Centos, I must figure out a workaround. Apple support wasn't much help as usual however they were very nice.
There usual response is "its unsupported".
If Apple really wants to play in the enterprise of business space, they really need to change there philosophy. I mean telling me that I shouldn't mount home directories via NFS is completely rediculus.
What am I supposed to use then, Samba of AFP? No, I don't think so. No offense to Microsoft but why would I use a Windows based file sharing protocol to mount network shares in a Nix env???

Can't open files in Camera Raw while in Bridge CS6

05/30/2014
Believe this issue/problem happened after automatic update from Adobe (but can't be sure).
Have always uploaded files from camera into Bridge then do some editing by opening JPEG and RAW (NEF) files in Camera Raw from Bridge.
Now, "Open in Camera Raw" is greyed out and I am unable to find a way to open files with Camera Raw from inside Bridge CS6. This seemed to happen suddenly and without any new software or applications being added to computer. All other apps/software working well.
Have tried various fixes found on Adobe community discussions without success. Problem now ongoing for over a week +.
Am able to open files in Photoshop with no problem but want to be able to do some quick edits using Camera Raw opening files from Bridge CS6.
I'm using Bridge CS6 Version 5.0.2.4. (as part of Adobe Creative Suite 6). Updater states I have most current version of Bridge installed.
I'm using an iMac computer with Intel Core i7 processor
OS X 10.8.5
Have found others with this same or very similar problems on forums but either can't understand patches/directions or unable to complete instructions on my computer.
for example see: Camera RAW update issue with Bridge CS6
From that link/discussion, one finds this "solution":
After you update to Camera Raw 8.4, Bridge CS6 in Mac OS doesn't display image metadata or allow you to edit images in Camera Raw.
To the top
Manually install the Camera Raw 8.4 plug-in.
Exit Adobe Bridge.
Download the file below.
Locate and double-click the downloaded file to decompress it. The resulting file is Camera Raw.plugin.
Navigate to the Macintosh HD folder.
Open the Library/Application Support/Adobe/Plug-Ins/CS6/File Formats folder.
IMPORTANT: Navigate to the root Library folder on your hard disk, not the Library folder under your user folder.
Copy the Camera Raw.plugin from step 3 into the File Formats folder.
IMPORTANT: This new file overwrites the file already in this folder. It's important that only one Camera Raw.plugin file is in this folder.
Open Adobe Bridge.
Camera Raw.plugin.zip
Mac OS Camera Raw 8.4 plug-in for manual installation
However, when I try the above, I have these issues:
1. When I double click on the downloaded file, my computer opens PhotoShop and an error message is displayed that states "Could not complete your request because Photoshop does not recognize this type of file." (I suspect this may mean my computer has automatically decompressed the file, but I am not certain of that).
2. Not completely certain I know how to "Navigate to the Macintosh HD folder" as suggested in step 4. above (OK, I'm new to Mac; long-time PC user….)
3. When I am in "Finder" and click on "GO" while holding down "Option" key, I find "Library". within that, I can find "Library/Application Support/Adobe" but there is no "Plug-Ins" folder within the "Adobe" subfolder.
4. Not sure how to tell if I am in the "root Library" on my hard disk vs. "Library under my user folder". (Again, new to Mac….)
I have NOT yet tried doing an "Uninstall" and then Re-installing the whole Adobe Creative Suite 6 and would like to avoid that if possible.
Would absolutely LOVE it if Adobe would simply push an update that would fix this problem or if someone would explain to me how I could restore the earlier version that worked perfectly for me.
Any help, suggestions (in very basic, simple terms that any idiot new to the world of Macintosh can understand) would be appreciated. Very frustrated with Adobe at the moment.
Mostly have liked the switch to Mac, but with this and my photo workflow coming to a screeching halt, having second thoughts. (But I suppose Adobe update for PC may cause problems as well.)
Thanks in advance for any help/suggestions.

05/30/2014
Literally minutes after I posted the above, I figured this out myself and now I'm a happy camper and things are back to normal!
Here was my error/issue: as a new Mac user, I was not negotiating/finding files on my hard drive correctly.
In case there are others out there with this same issue (and as dense as I apparently am ):
Here is what I did that resulted in a fix:
First Steps:
1. Quit/close Bridge
2. As noted in post above, go to this link to download Camera Raw Plugin file:
Camera RAW update issue with Bridge CS6
Link to get to download is near end of instructions, but I will attempt to insert that link to download here:
Camera Raw.plugin.zip
3. Once file has been downloaded, find it by using "Finder" Click on "Finder" and look on list of options on left side of Finder window to find "Downloads". On my computer, when clicking on "Finder" these options appear in the list at the left:
All My Files
Airdrop
Applications
Desktop
Documents
Downloads
Movies
Music
Pictures
4. Download you just did should be at or near the top of your downloads list and should be named as "Camera Raw.plugin" and will be 83.5 MB in size
5. I right-clicked (two fingers on touchpad) to bring up drop down options and selected "Copy 'Camera Raw.plugin'" from that list to copy file.
Now, you have copied the plug in that will fix this issue. The second set of steps below will walk you through how to replace the file that is on your hard drive with this plug in file that you have copied.
Second set of steps (and this is where, as a new Mac user, I was confused initially)
1. Again, click on "Finder" on your Mac
2. On top of screen, find "GO" and click on that. (You should see "Finder" in the upper right corner of your screen, then "File, Edit, View, GO, Window, Help" Click on the GO
3. In drop down menu that appears, click on "Computer"
4. Then, double click on "Macintosh HD" to open your hard drive
5. Next, double click on "Library" folder to open that.
6. Next, click on "Application Support" folder to open that.
7. Then, double click on "Adobe" folder to open that.
8. Then, double click on "Plug Ins" folder to open that
9. Now, double click on "CS6" to open that folder.
10. Finally, double click on the "File Formats" folder that appears.
11. NOW, you should see this:
12. Right click (two finger press if using a touch pad) to open window with options. Select "Paste Item" by clicking on that option.
13. You will be prompted with an option to keep existing file OR replace the file. Choose "Replace" to past the new "Camera Raw.plugin" file to this folder.
Finally, if you now go back and open Bridge CS6, you should be good to go.
Hope that helps someone out there.
Hopefully future updates will from Adobe will be better.

Iweb installed on a new computer but i have this error message: Can't open file "~/Library/Application Support/iWeb/Domain.sites2."

I have just installed ilife on my new computer from my disk. I have several backups of my webpage from my old computer. Everything would be great if I could just run the program. When I click the icon for iWeb I get the following message: Can’t open file “~/Library/Application Support/iWeb/Domain.sites2.”
Somebody please help! I desperately need to update my website.

In Lion the Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.
To open your domain file in Lion or to switch between multiple domain files Cyclosaurus has provided us with the following script that you can make into an Applescript application with Script Editor. Open Script Editor, copy and paste the script below into Script Editor's window and save as an application.
do shell script "/usr/bin/defaults write com.apple.iWeb iWebDefaultsDocumentPath -boolean no"delay 1
tell application "iWeb" to activate
Just launch the application, find and select the domain file you want to open and it will open with iWeb. It modifies the iWeb preference file each time it's launched so one can switch between domain files.
You can download an already compiled version with this link: iWeb Switch Domain.
WARNING: iWeb Switch Domain will overwrite an existing Domain.sites2 file if you select to create a new domain in the same folder. So rename your domain files once they've been created to something other than the default name.
OT

Error message: "Can't open file "[File path, file name].key"

If I attempt to open any Keynote files, I now get this error message.
"Can't open file "[File path: file name].key"
To clarify, the text in the square brackets above would be the file path and then the file name.
The file then will appear on the screen, but is unresponsive to any clicks or menu commands.
The files will open successfully on other Macs, so they aren't corrupt.
Also - I've just checked, and opening Keynote and trying to create a new presentation leads to the same problem: All screen menus / buttons are dead - all I can do is drag the window around the screen.
I've tried to reinstall Keynote, but this hasn't resolved the problem.
Is there some corrupt preference file (or similar) that I need to get rid of? Is there an easy way to do a complete uninstall of Keynote so I can try another install? Or is this a symptom of something else?
All ideas gratefully appreciated!
Message was edited by: Brendan Donlon

All the issues I describe in my questions around this time re: Keynote were actually symptoms of a soon-to-die laptop. The Hard Disc was corrupting, and Keynote was the first application to be affected.

[Solved][VIM] E484: Can't open file syntax.vim

Hi all,
I've installed Archlinux few days ago on my netbook and yesterday i decided to configure Vim using plugins.
During plugins configuration, i messed up and i decided to revome all Vim files in my ~ folder in order to restart configuration.
However, since I've executed the `rm -R .vim .vimrc .viminfo` command, I can't re-activate Vim's syntax coloration using `syntax on` into my .vimrc file nor into Vim directly.
Here is the error message when I start Vim :
Error detected while processing /home/romain/.vimrc:
line 1:
E484: Can't open file /home/romain/.vim/syntax/syntax.vim
Press ENTER or type command to continue
I've found this topic on BBS which seems to be the same problem as me but reinstalling vim or vi doesn't solve this problem.
I've tried to copy this syntax.vim file from /usr/share/vim/vim73/syntax/syntax.vim but it doesn't solve the problem and I want a clean solution without hacking my ~ folder ; moreover, this bug also appears being root while I haven't configured vim with the root account so it may be a problem into Vim's installation folders or something.
Thanks for your help and sorry I my english contains mistakes,
MicroJoe.
Last edited by MicroJoe (2012-06-14 16:16:45)

This is the output :
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun 7 2012 00:41:40)
Rustines incluses : 1-547
Compilé par ArchLinux
Grosse version sans interface graphique.
Fonctionnalités incluses (+) ou non (-) :
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs
-dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path
+find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv
+insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape
+mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse
+mouse_xterm +mouse_urxvt +multi_byte +multi_lang -mzscheme -netbeans_intg
+path_extra +perl +persistent_undo +postscript +printer -profile -python
-python3 +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent
-sniff +startuptime +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
-toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp
-xterm_clipboard -xterm_save
fichier vimrc système : "/etc/vimrc"
fichier vimrc utilisateur : "$HOME/.vimrc"
fichier exrc utilisateur : "$HOME/.exrc"
$VIM par défaut : "/usr/share/vim"
Compilation : gcc -c -I. -Iproto -DHAVE_CONFIG_H -I/usr/local/include -march=i686 -mtune=generic -pipe -fstack-protector --param=ssp-buffer-size=4 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Édition de liens : gcc -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -L/usr/local/lib -Wl,--as-needed -o vim -lm -lncurses -lacl -lattr -lgpm -ldl -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -fstack-protector -L/usr/local/lib -L/usr/lib/perl5/core_perl/CORE -lperl -lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
(I've noticed that some part were in French but I hope that it'll not be a problem).

Snow Leopard 10.6.2 CS4 InDesign can't open files with a "#" in file path

Snow Leopard 10.6.2 CS4 InDesign can't open files with a "#" in file path using any of these perfectly normal methods:
1. double-click file in the Finder (e.g in a Folder on your Mac or on your Mac desktop etc.)
2. select file and choose "File... Open" command-o in the Finder
3. drag file to the application icon in the Finder.
4. Select file in Bridge and double-click, choose File.. Open.. or Drag icon to InDesign icon in dock.
If you try to open an ID file named with a "#", you will get an error message "Missing required parameter 'from' for event 'open.'"
This happens to any InDesign file that has a "#" (pound sign, number sign, or hash) in the filename or in the file path (any parent folder).
To reproduce
Name an InDesign file Test#.idd Try to open it in the Finder or Bridge (as opposed to the "Open" dilaog of InDeisng itself).
"Solution"
The file WILL open using File... Open... command-o while in InDesign application.
Rename the file or folders that have a "#" (shift-3) in the filename.
Report to Adobe if it bugs you.
This does not occur in "plain" Leopard 10.5 nor Tiger 10.4
Untested in Panther or before and
Untested with CS3 and earlier in Snow Leaopard.
Anyone have those and want to try this... ?

In case this really bothers you: we've added a workaround for this into Soxy. If you enable the option, these documents will open fine on double-click.
You need Soxy 1.0.7 from:
http://www.rorohiko.com/soxy
Go to the 'Soxy' - 'Preferences' - 'Other' dialog window, and enable 'Open InDesign via Script'
(Irrelevant background info (it's all invisible to the user): the workaround works by special-casing how Soxy opens documents in InDesign: instead of using AppleScript, Soxy will use ExtendScript to instruct InDesign to open the document - which works fine).

Quicktime on Windows clients can't open files in folders with long names!!

Similar Messages

Maybe you are looking for