42 characters long file names in iCloud 3 photo stream

Windows icloud 3, in a shared photo-stream, makes file names with 42 random characters long. It didn't do this in iCloud  2. I have installed iCloud 3 on a windows 8.0 and 8.1 machine and two Windows 7 machines. They all do the same thing.  It used to give me file names like "IMG_0001.jpg" now it gives me random file names like "01a9fc3363330464233a142486180f0c1622eb9fca.jpg" all the pictures are out order. Does anyone have fix for this?

I have never found a solution for this.
I did find a Work Around. What I do when I receive a folder full of pictures from another ios iPhone user, I copy all the photos as a batch from the PhotoStream folder into a free Windows program called "FastStone Photo Resizer" from www.FastStone.org. This program allows you to resize the photos as a batch to what ever size you wish. In my case I resize them to 2560 x 1440 which fills my 27" monitor and reduces the file size of each picture from 2MB or 3MB down to about 450 KB without degrading the picture as far as what you see on the screen.
This program will also within the same batch operation, allow you to sort the pictures by "Date Taken" which is the Date and Time the picture was taken. It gets this information from the EXIF data in the jpg file. This program will then rename the files with different numbering format options including date, time, alphanumberic and with just simple numbers starting at what ever number you wish to start with. I can get files that look like this again "IMG_0001.jpg" and have all the pictures in the correct order that they were taken. At this point, I save the pictures directly to a folder on my PC. The cool thing about this is, all the EXIF data is preserved as well. I can process a 100 pictures in less that 60 seconds. I hope this helps. For me, I can now live with this iCloud numbering defect.

Similar Messages

  • Destination file characters too long (File names) , while copying from one external to another

    I have a external my book fat32 formated and a new mybook ntfs formated external as well.  Now when I copy my files from the fat32 to the ntfs external all files copy fine but some give that destination location file characters are too long, meaning that the file names are too long.  Now I could change the file names but that would conflict with programs that need that file name.  I am using vista ultimate and would like to copy all the files over from the fat32 to ntfs so I can reformat the fat32 to ntfs.  The files got on the ntfs from a simple drag and drop from my IDE NTFS internal hard drive.
    I hope you guys to tell me what to do.
    Thank you :)

    Here's the fix....for error message "your file name is too long to be copied, deleted, renamed, moved" :
    1.   problem is this: the "file name" has a limit on number of characters.....the sum of characters really includes the entire path name; you gotta shorten it first (i.e, if the total number of characters in the file name + Path name are over the
    limit, the error appears).  The deeper your file folder sub levels are, the more this problem will come up, especially when you copy to a subfolder of a subfolder/subfolder of another path ...adds to character limit)
    2.  How do you know which combined file names + path names are too long if  you are in the  middle of a copy operation and this error pops up?  Some files copied but the "long files error message" says "skip" or "cancel" ... but not which
    files are the "too long" ones.  If you hit "skip" or "cancel" the "too long" files are left behind...but are mixed in with non-offender "good" "short name" files.   Sorting thru 1000s of "good" files to find a few "bad" ones manually is impractical.
    3.   Here's how you sort out the "bad" from the "good":
    4.    Let's say you want to copy a folder ..."Football" ...that has five layers of subfolders; each subfolder contains numerous files:
      C:/1 Football / 2 teams/ 3 players/ 4 stats/ 5 injuriessidelineplayerstoolong 
           There are five levels root "1 football" with subfolders  2, 3, 4 and lastly "5 injuries"
    5.    Use "cut" and "paste"  (for example to backup all five levels to a new backup folder):
           select "1 football" ....cut....select target folder....paste 
           ("cut" command means as the files are copied to the target destination, the file is deleted from the source location)
          Hint: avoid "cut" and "paste" to a target folder that is itself a sub/sub/sub folder ...that compounds the "characters over the limit" problem ...because the characters in the sub/sub/sub folder are included in the "file name
    character limit"...instead "paste" to a C:/ root directory.
           Suppose in the middle of this operation...error pops up: "5 files have file names that are too long"  Skip or cancel?
           select "skip"  ...and let operation finish
    6.    Now go back and look at the source location: since the software allows only the "good" "short name" files to be copied (and because you "skipped" the "bad" "Long name" files so they are not copied or deleted) ...all that remains
    in the source location are the "bad" "long name files" (because "good" ones were deleted from the source location after the "cut" operation...the bad ones stick out like a sore thumb.
    7.   You will find ....all that remains in source folders are: the "bad" "too long" files; in this example the "bad" file is in level 5:
          C:/ 1 football / 2 teams /3 players /4 stats /5 injuriessidelineplayerstoolong
    8.   select folder 5 injuriessidelineplayerstoolong (that's right...select folder, not file) gotta rename the folder first.
    9.  hit F2 rename folder..folder name highlighted...delete some of the letters in the folder name:
           like this:   5 injuriessidelineplayers  ....you should delete 'toolong'....from the folder name
    10.  then go into folder 5....and do the same operation ...with the too long file name:
            hit F2 rename file....file name hightlighted...delete some of the letters
               like this:  injuriessidelineplayers.....you should delete 'toolong' from the file name
    11.  Now..."cut and paste"  the renamed file to the target backup folder.  
    The Error message will pop up again if you missed any "bad" files....for example, it will indicate "5 files too long" ....then repeat process 5 times until you fix all of them
    12.     Finally, copy the target destination files back to the source location (when you are certain all source location file folder locations are empty) 

  • Time capsule won't allow long file names

    Hello,
    I've managed to solve every problem I've had through searching other people's forum posts - apart from this one.
    I've got a MacBook Pro and Dell PC (Windows 7) connected to a Time Capsule. Soon I'll happily bin the Dell but am moving gently to Macs while I learn about them.
    The Mac connects happily to TC and will allow creation/editing of long file names.
    The Dell allowed this for a week, but now doesn't like it. When I go to the Time Capsule/Data folder in Windows 7 Explorer, I can copy over files with long names, but I can't create them, nor can I change any existing file/folder names on TC to be longer than 8 characters.
    I've searched and searched online and can't find anything that would suggest why this is happening.
    Thanks in advance,
    Adrian

    Tried DHCP & NAT but had the double NAT issue.
    If you got the TC working and had double NAT .. sorry but the TP-Link is exactly the same.. you cannot distribute a single IP without double NAT.. the TC tells you it is a problem.. the TP-Link doesn't.. otherwise there is no difference.
    But it is important the double NAT is setup right.. ie you must use different ranges.. please tell us the IP you get from a directly connected computer..
    If it is 10.x.x.x then you should move the TC to 192.168. rather than default IP of 10.0.1.1 .. the TP-Link already will use 192.168.x.x. which might also explain why it works better.

  • BIG PROBLEM: CSS files not loading because of international characters in file name

    I have Muse Beta 7 in Spanish.
    The program creates a css file called master_a-página-maestra.css in css folder. It is referenced in the resulting HTML code here:
    <!-- CSS -->
      <link rel="stylesheet" type="text/css" href="css/site_global.css?3951792836"/>
      <link rel="stylesheet" type="text/css" href="css/master_a-p%c3%a1gina-maestra.css?fileVersionPlaceholder"/>
      <link rel="stylesheet" type="text/css" href="css/index.css?3948175564"/>
    When you work locally in your Windows formatted har drive, everything looks fine, but when you upload your files to a server, everything is screwed up. The server doesn't recognizes the URL and returns an error page, resulting in style errors in the entire site.
    This can also happens with html files if the title of the page contains international characters or with images if the image file name in your Hard Drive contains international characters.
    I already pointed out long time ago Muse was generating file names with international characters like á, ñ, etc but nobody cared about it. Too bad. I had to activate file name customization but I think that Muse should replace automatically this characters in the same way that it replaces other conflictive characters like commas or ampersands.
    This is not a fault of the FTP client. Accented characters are not web safe regardless of the FTP client you are using. It is a server side issue. Some servers support it some others don't. I don't mind if it works in Adobe Catalyst server because the final website is going to be in another server and maybe next year when paid hosting is ended the client may move it to another server.
    It makes more sense to replace accented characters in file names by their not accented equivalents ('a' instead of 'á', 'N' instead of 'Ñ', etc) and avoid all this problem.

    Zak, It is funny you mention it, because the site I am talking about is hosted in 1and1. try this: http://www.artofwalls.com/rosannawalls/biografía.html
    As you can see, the offending "í" in the file name causes 1and1 server to throw a "page not found" error. And this has happened with many other servers I have tried since.
    Muse boast of generating code fully compatible with all major web browsers but by using international characters in file names it ggenerates code suitable only for very few web servers. International characters have been always a no-no for internet URLs. Internet was designed by people who didn't care about ascii codes beyond 127 so using international characters in html file names is just call for problems.
    "to work with your hosting provider to determine how to enable Unicode encoded (UTF-8) file names and HTML files on their servers" is not a viable solution most of the time unless you are a Very Important Client of your host provider. If not, making changes means money for them and if you are the only one who complains, they are going to just tell you to not use international characters in your names.

  • Long file names-won't copy

    how can i turn off my macs irritating annoyance at not wanting to copy files with long file names ? some of these files come straight from CD's, so I can't change the filenames unless I went to a PC, copied them, changed the name and then copied them to my Mac. that is way too much to do.

    Hi, Ted.
    It would also help to know if you're trying to copy the files to your Mac's internal hard drive(s) or an external drive, such as a FireWire drive. If an external drive, knowing the format of that drive also helps.
    Along the lines of your question:
    • The maximum length for a file name in Mac OS X is 255 characters. See Mac OS X: About Long File Names.
    • However, I've seen cases in some Carbonized applications, i.e. those written originally for Mac OS 9 and ported to Mac OS X using the Carbon developer tools, that still insist on enforcing the 31 character limit of Mac OS 9. That is an issue with the application, not Mac OS X, and occurs when you attempt to File > Save or Save As... a new file created in that application.
    • Certain characters are prohibited in Mac OS X file names. See "Mac OS X 10.4 Help: I can't use some characters in file and folder names."
    • Likewise, if you plan to share files with PCs running Microsoft Windows, avoid Windows-prohibited characters in the file names: see "Mac OS X 10.4 Help: Copying files to a Windows computer from a Mac stops."
    Good luck!
    Dr. Smoke
    Author: Troubleshooting Mac® OS X

  • Maximum characters in file name of links?

    Is there a maximum number of characters in file names of links that InDesign can handle?
    If so, what is the character count?
    What about Mac OS X?
    Thanks in advance.

    One thing to bear in mind on the Mac is that the method used to connect to a server also influences how many characters a file name can have before being truncated. This may not be relevant if you work with files on your local drive but we used to connect to our (Windows) server via AFP and occasionally we'd receive Quark or ID docs and links (images) with long file names. Either you couldn't copy the files to the server as the name was too long, or if it had been copied to the server on another computer the doc would have broken links as it expects the link to have full names but the names of the files on the server (or how they appeared when connected by AFP) were truncated, so different. For those instances we'd connect via SMB which allows longer names.
    Now we connect via SMB across the board.
    Iain

  • Long File Names via smb ethernet

    I'm trying to transfer files from my old Vista box to my new MacBook Pro. I'm set up with a direct ethernet connection and using smb protocol. Problem is I cannot transfer files with long file names. Only a problem when you consider that I'm transfering about 400 gigs of files at a time... it would be rather tedious and take me a considerable amount of time to go back and shorten so many file names. Is there any way around this? Any help would be greatly appreciated.

    maybe try zipping up the files as a folder or something. SMB follows similar rules the the older FAT32 based windows oses followed back in the day. If the zipping doesn't help, then you'll have to rename the files.
    you might try a renaming utility to look for files with blank spaces or the following characters:
    "SMB, files can’t use the following characters: ” / \ [ ] : + | = ; , * ? and space, and the period ‘.’ can only be used once."
    http://www.rossolson.com/dwelling/2007/03/notes-on-nas-and-mac-os-x/
    Message was edited by: kmac1036

  • Can't view files with long file names?

    Hi, Im using Mac OSX 10.3.9 and I have a problem viewing files on a server that have long file names (i.e over about 20 characters) they do not show up on my mac but when viewed on a PC computer they are all there. Strange thing is though I have another mac on the same network running exactly the same operating system and version and files with long name can be viewed on that system ?? it is some simple preference does anybody know? Any help would be much appreciated. thank you.

    Hi, I tried accessing a test file that I have made up with a long name through a browser and through FTP and cannot see it on either one. I can however see it on the other Mac that I have access to that is running the same OS and version etc... and also this file can been viewed on the PC's that are around me....

  • Logic 7.2 - long file names?

    I read the messages from the few people who looked at the new 7.2 version at NAMM. Besides all the known and unknown features/bugfixes, does anybody know if they got rid of the 31 character filename limitations.
    OSX is out now for how many years?
    The strange thing is that GarageBand files supports 255 characters, , but it limits the EXS file names which it uses in its plugins:
    If you open the The CurchOrgan Software Instrument in GarageBand3, which is like a "EXS24 light", and click on the "Registration" popup menu then you see a list of EXS instruments which are located in the following directory: /Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Instruments/Church Organ
    You can place any EXS Instrument file inside that directory and it will show up in the "Registration" popup menu (after you restart GarageBand).
    OK. if I place now an EXS instrument file inside that folder and rename the file with a very long file name, it will show up truncated inside GarageBands Software Instrument.
    Does that mean that even in GaraBand3 there is still legacy code which doesn't support full 255 file names. And does that mean that the long filename support for Logic and especially EXS24 is still not implemented in Logic 7.2?
    G5 Dual 2.5G - 4.5GB RAM   Mac OS X (10.4.4)   Logic 7.1.1

    No, Logic 7.2 doesn't bounce and name files with more than 31 characters.
    G5 2x2.5 GHz 2.5 GB RAM / PowerBook 1,67 GHz 1,5 GB RAM   Mac OS X (10.4.5)  

  • Windows sharing long file names

    Just after a bit of advice with regards long file names with OSX/Win.
    I have a user that uses a mixture of SL and ML connection a shares on a Win 2008 R2 server.  They had some issues a while back with long file names ( I think folder depth more than anything) and a previous engineer installed ExtremeZ-IP.  However ever since they've been having random file permission issues.
    I'm keen to remove the ExtremeZ software as I see it as an extra piece of management and failure and with the news of Apple dropping AFP, makes sense to lose it when possible.  I do have other users using OSX and Win 2008 servers with no 3rd party software and not having any issues.
    I'm thinking that the original problem was with using AFP not liking the Win file names and instead of moving to SMB, the software 'fix' was used. I feel that removing this software and forcing the clients to use SMB, will hopefully resolve the permission issues and have no implications on file names.
    I would be grateful if someone could shed some light or thoughts on this if anybody has similar experience.

    I suspect they are connecting to the server using Samba and you're using afp ?

  • Mail.app hang if mail attachment have special characters in file name

    Hello,
    I have upgraded to 10.5.1 from last version of Tiger.
    After upgrade is not possible send message with attachment which have a czech special characters in file name (like á, í, é, ý, ú, ů, ě, š, č, ř, ž) with Mail.app. If I try it, CPU is overloaded and I must kill Mail.app process.
    The same problem have my friends who are running a clear installation of Leopard 10.5.1.
    Thanks for correction.

    I have the same problem with Hungarian chars. I tried out Tomas suggestion and it really worked. It is so dissaponting to have this kind of bug in a system like this. They never tested against this situation.
    I hope somebody at apple read this discussion and somehow this will be fixed in the near future.

  • How to Make Itunes Recognize Foreign Characters in file names?

    How to Make Itunes Recognize Foreign Characters in file names?
    Any Body, please
    DELL Windows XP Pro

    That's not how it's supposed to work according to this: http://www.griffintechnology.com/support/italkpro/
    By default, a playlist will be created in iTunes called "Voice Memos" and those files will be transferred there automatically. The files themselves can be found on your computer in your iTunes Music folder in Unknown Artist > Unknown Album.
    It may be worth working through any trouble shooting articles on that site.
    Regards,
    Colin R.

  • Sqlldr does not understand unicode characters in file names

    Hello,
    I am trying to call sqlldr from a .net application on Windows to bulk load some data. The parameter, control, data, log files used by sqlldr, are all located in the C:\Configuración directory (note the unicode character in the directory name).
    Here is my parfile:
    control='C:\Configuración\SystemResource.ctl'
    direct=true
    errors=0
    log='C:\Configuración\SystemResource.log'
    userid=scott/tiger@orasrv
    When I make a call as
    sqlldr -parfile='C:\Configuración\SystemResource.par'I am getting
    SQL*Loader-100: Syntax error on command-line
    If I run it as
    sqlldr -parfile='C:\Config~1\SystemResource.par'I am getting
    SQL*Loader-522: lfiopn failed for file (C:\Configuraci├│n\SystemResource.log)
    If I remove the log= parameter from the parameter file, I am getting
    SQL*Loader-500: Unable to open file (C:\Configuraci├│n\SystemResource.ctl)
    SQL*Loader-553: file not found
    SQL*Loader-509: System error: The system cannot find the file specified.
    Can anyone suggest a way to handle unicode/extended ASCII characters in file names?
    Thanks,
    Alex.

    Werner, thank you for replying to my post.
    In my real application, I actually store the files in %TEMP%, which on Spanish and Portuguese Windows has "special" characters (e.g. '...\Administrador\Configuración local\Temp\'). In addition, you can have a user with the "special" characters in the name which will become part of %TEMP%.
    Another problem is that 8.3 name creation may be disabled on NTFS partitions.
    Problem #3 is that the short file names that have "special" characters are not converted correctly by GetShortPathName windows API, e.g. "Configuración" will be converted to "Config~1", but for "C:\ración.txt" the api will return the same "C:\ración.txt", even though dir /x displays "RACIN~1.TXT". Since I am creating the parameter and control files programmatically from a .net application, I have to PInvoke GetShortPathName.
    Any other ideas?
    Thanks,
    Alex.

  • French Characters in File Names

    Hello,
    Despite my instance not use French and/or other special
    characters in files names, we have inherited a project (approx 2500
    topics) with French characters in the file name. When we generated
    the project and post it on an Apache server, the topics do not
    display as the server replaces the characters with symbols.
    RX5, during the generation process, replaced the French
    characters with underscores, RX 7.0.1 keeps the characters within
    the file name. In RX 7.0.1 is it possible to replace the characters
    with underscores during the generation process?
    Regards,

    If this is the other thread, then you did get a response, several in fact. It may not have been the answer you wanted but that's another matter.
    http://forums.adobe.com/message/129875#129875
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Long file name support on DVD??

    I'm not a hardware or software person, but one of our guys who is is having trouble getting a DVD in a V120 running Solaris 9 to consistently recognize long file names on DVDs that were created on PCs running XP with various combinations Sony and Memorex DVD burners and Nero and Roxio RecordNow software. Focus has been on the software and burners, but has anyone encountered the same problem and found something that had to be tweaked on the Sun side? If so please let me know of the fix so I can pass it on.

    It's a software issue.
    Windows uses the Microsoft Joliet ISO9660 extension to allow somewhat
    longer (unicode) filenames than standard ISO9660.
    But Solaris doesn't support the Microsoft Joliet extension. Solaris supports
    the RockRidge ISO9660 extention for long filenames (and posix support).
    Try to find a CD mastering application that allows to write RockRidge
    format CD/DVDs.
    E.g. the unix "mkisofs" utility allows to create ISO9660 filesystems with both
    the RockRidge and Joliet extension, so that you get long filenames on
    both unix and windows.

Maybe you are looking for