> And what's the maximum path length FFS can handle? Its limits are and why my filenames come up against them. Of all the people, forums and packages, FFS is best placed to tell me what Messenger asleep in the manger who didn't even bother getting on his horse. No, don't shoot the messenger who delivers a message. I still don't think in terms of filename length because my Thunarįile browser, like FFS, doesn't bother to tell me what its limits actually Only, sometimes my system tells me IĬan't use a filename (at the point at which I'm naming it) because it's too No, actually, I was wrong to say that as a user I think in terms of file > Don't blame the messenger (=FreeFileSync), blame the sender (=your > They mean nothing to anyone but software programs, software programmers > You do realise I am a user? I think in terms of file length. "Okay, but I'd better do a quick backup first." I was too distracted by my words from this morning still echoing around my Oh your other message slipped in without me noticing before I'd finished Perhaps I should ask the nymph at the bottom of the river. Perhaps I should ask the jailor in debtors' prison. Perhaps I should ask the genie at the end of the bottle. So what is the FFS path limit? Perhaps I should ask the big beefy bulldogs in town who laugh at you for being a loser. Perhaps that's why they don't say what the actual limit is. Hardly seems worth bragging about when the increase is so small anyway. And anyway, that seems a nonsense number because the path length on these files is about 316 to 323 chars. That makes it less a FAQ than marketing chuff. It doesn't bother to tell you what the maximum is. Its FAQ page brags about being able to handle path names "with more than 260 characters". They mean nothing to anyone but software programs, software programmers and system administrators.Īnd what's the maximum path length FFS can handle? It doesn't say. You do realise I am a user? I think in terms of file length. If no characters are removed and FFS is told to, FFS will reject it, even if the filename length is less than other files it has accepted.ĭon't tell me it's not file length that FFS measures but path length? Īs long as any number of characters is removed from the filename, FFS will accept the renamed file, even if its length is greater than other files it has rejected. In each case I removed a number of characters then told FFS to. The following test shows the filename length of files FFS said were too long to process. Here's a good game - guess the FFS filename limit: And of course this folder is Read Only.The function has some very odd behaviour. Does this mean it temporarily creates such files in each of the source folders its copying from? Presumably to stop the folder changing while being copied. It seems as if it's trying to write to the Start Menu folder on C:\ to create lock and database files - presumably temporary. Įrror Cannot write file "C:\ProgramData\Microsoft\Windows\Start Menu\sync.ffs_db.d425.ffs_tmp". Warning Cannot set directory locks for the following folders:Ĭannot write file "C:\ProgramData\Microsoft\Windows\Start Menu\sync.ffs_lock".ĮRROR_ACCESS_DENIED: Access is denied. Source folder: C:\ProgramData\Microsoft\Windows\Start Menuĭestination folder: I:\PCs - key folders\Tower PC\Start Menu In particular one pair seems to give a couple of error messages. One use is to backup to an external USB stick (I:\) certain files and folders. Only recently discovered FFS, so much better and more friendly than my previous program.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |