Hello everyone!
COPY from Everything-Window into Win-Explorer works sometimes and sometimes NOT.
My OS is Win10. And I am using Everthing on a network drive.
The searched files show up correctly.
I am also able to call up the path where the file which I want to copy into a Windows folder resides.
The COPY from the path works with Windows, but it does not always work from the Everything window.
Very strange: sometimes it works. But even then: it does not copy all files found in the Everthing window with all search results.
What is wrong?
Cheers,
Hipoh
Copy - not always working
Re: Copy - not always working
What version of Everything?
Anything peculiar, particular with the particular files, file locations, that it does not copy?
(Like file name length?)
Might it be a permissions issue?
Anything peculiar, particular with the particular files, file locations, that it does not copy?
(Like file name length?)
Might it be a permissions issue?
Re: Copy - not always working
Everything Version is 1.4.1.1026 (x64).
Ok, nothing particular with the files. The files I want to copy (with drag and drop from Everything to Windows-Explorer) are ASCII-Txtefiles.
With explorer I can copy them without problems. So it should not be a permissions issue.
With Everything sometime it works, sometimes not (which most very strange).
The names of paths and names are quite long.
I will check if it could be a name length limit. Please let me know if there a length limit?
Cheers,
Hipoh
Ok, nothing particular with the files. The files I want to copy (with drag and drop from Everything to Windows-Explorer) are ASCII-Txtefiles.
With explorer I can copy them without problems. So it should not be a permissions issue.
With Everything sometime it works, sometimes not (which most very strange).
The names of paths and names are quite long.
I will check if it could be a name length limit. Please let me know if there a length limit?
Cheers,
Hipoh
Re: Copy - not always working
It could be ? that Everything is sending a SFN.
So the file could be there, only you're not seeing it, cause you're looking for a LFN where the copy was named as a SFN.
(I wouldn't particularly expect that, but might be possible.)
So take 1 file that fails to copy, & try to copy that into a new directory.
Does anything make it into that new directory?
So the file could be there, only you're not seeing it, cause you're looking for a LFN where the copy was named as a SFN.
(I wouldn't particularly expect that, but might be possible.)
So take 1 file that fails to copy, & try to copy that into a new directory.
Does anything make it into that new directory?
Re: Copy - not always working
Tried with one file where copy did not work: after length reduction the COPY was possible.
So, I conclude: there is an issue with path and/or filename length.
How this can be resolved?
So, I conclude: there is an issue with path and/or filename length.
How this can be resolved?
Re: Copy - not always working
What OS?
I wasn't looking for a name length reduction particularly, but rather to see if a Short File Name version of the file ended up being created.
So if you had
"this is a really long ... 255 char file name.TXT"
& when you copied the file, it ended up as an 8.3 (SFN),
"THISIS01~.TXT"
So the file did copy, but you were looking for "this is ...", but instead the file ended up being named "THISIS01...", so you didn't "see" it.
Anyhow, since shortening worked, what was the original file name, or at least how long was it, & to where were & how were you coping it? Is the destination also an NTFS drive?
I wasn't looking for a name length reduction particularly, but rather to see if a Short File Name version of the file ended up being created.
So if you had
"this is a really long ... 255 char file name.TXT"
& when you copied the file, it ended up as an 8.3 (SFN),
"THISIS01~.TXT"
So the file did copy, but you were looking for "this is ...", but instead the file ended up being named "THISIS01...", so you didn't "see" it.
Anyhow, since shortening worked, what was the original file name, or at least how long was it, & to where were & how were you coping it? Is the destination also an NTFS drive?
Re: Copy - not always working
Everything under Win10 and Win11 show the same behavior.
- Copy tried per drag & drop from Everything Window fails. Nothing happens! NO SFN filename found in destination folder!
- Direct copy with Win-Explorer works.
And yes, I can confirm that the total lenth of path/filename is the problem.
Path/File-name together were >259 char. Only 3-5 char more (say: e.g. 263)
When shortened <259 char copy works.
Q: Is it possible to copy files with (>259 char) long path/filname in Everything?
How can it be done?
Thanks!
Hipoh
- Copy tried per drag & drop from Everything Window fails. Nothing happens! NO SFN filename found in destination folder!
- Direct copy with Win-Explorer works.
And yes, I can confirm that the total lenth of path/filename is the problem.
Path/File-name together were >259 char. Only 3-5 char more (say: e.g. 263)
When shortened <259 char copy works.
Q: Is it possible to copy files with (>259 char) long path/filname in Everything?
How can it be done?
Thanks!
Hipoh
Re: Copy - not always working
See if enable Long Path Support in Windows changes anything?
(And somewhat related, Everything & SendTo & drag&drop & CustomCommands & LFN & SFN.)
(And somewhat related, Everything & SendTo & drag&drop & CustomCommands & LFN & SFN.)
Re: Copy - not always working
Long Path Support in Windows is enabled on my PC. This is not the issue.
BTW: There is NO problem for MSExplorer with drag and drop of files with long (>259 char.) path/filename.
About the second link (your voidtools forum entry): to complicated for me. Is there somewhere an easy solution for Everything?
Thanks,
Hipoh
BTW: There is NO problem for MSExplorer with drag and drop of files with long (>259 char.) path/filename.
About the second link (your voidtools forum entry): to complicated for me. Is there somewhere an easy solution for Everything?
Thanks,
Hipoh