[Solved] Find sparse files with sparse: or whathaveyou

[Herkules97]

So I was going to ask in an unsent post if you could see size on disk like in Windows file properties.
I decided to not be lazy and I checked and became disappointed when I haven't indexed it on any of my databases .
Anyway, is there a way to sort sparse files or only search for them doesn't use attributes?
Because I have files like..
"Size: 22,9 GB (24 621 875 200 byte)"
"Size on disk: 25,6 MB (26 869 760 byte)"
that does not have the P attribute, I think that's the sparse one.
All it has is A for "Archive".
Hmm, cmd doesn't say there is a sparse one. I thought there was one that was either O or P but neither are for that.

For example I search sparse: and it finds them? Not sure there is a tag for this stuff that Windows has.
It's not just comparing the size and size on disk, if I copy the file above to a different drive it will take 22.9GB on both entries, but it's still just as incomplete.

Even if I use something like http://www.flexhex.com/docs/articles/sparse-files.phtml (Internet Archive) I would still not be able to easily find them.
I found the file above because it's one of the larger files on the drive and I know it's incomplete from before.
But that could be a way to at least keep the sparseness for this full drive copy I am hoping I can do.

[void]

To find sparse files in Everything, include the following in your search:

attributes:0x00000200

There's no attribute-letter for sparse in Everything or Windows Explorer (and likely cmd).

attributes:

[Herkules97]

To find sparse files in Everything, include the following in your search:

attributes:0x00000200

There's no attribute-letter for sparse in Everything or Windows Explorer (and likely cmd).

attributes:

Yeah, just one of those things I dreamt up and then treated as if it existed.
A shame it doesn't work for files that have already been copied off without keeping sparseness.
But they can be compared with the drive originally containing them.

[void]

Everything 1.4 did have P for sparse.

Microsoft Windows added P for Pinned in Windows 10.
Everything 1.5 will use P for Pinned.

[AntonyD]

[SUGGESTION]

Dear developer, with your permission, I would like to return to this topic.
In the sense that your help indicates the fact that for some attributes there does not seem to be any one predefined letter,
the support of which would be end-to-end stretched through all windows-specific utilities/commands.... That's why I need
to consult Microsoft help and get the hex values of the attribute flags I need from there, which are involved in my search.
So, I checked that list of flags and that list of attributes "through one letter", which is supported in the program, and
it turns out like this, that the ONLY flags that have not received one-letter support are TWO flags! JUST TWO!

FILE_ATTRIBUTE_SPARSE_FILE
512 (0x00000200)
+
FILE_ATTRIBUTE_RECALL_ON_OPEN
262144 (0x00040000)

In other words, it turns out that you are suggesting using hex values ONLY for these two flags when creating a search string.
In the form of: "attributes:0x200 (find sparse files)"
But wouldn't it be much more logical to simply introduce TWO special constant flags that would be equal to these values,
and it would be simpler and more logical for users to use these exact letter counterparts than to constantly remember
about only 2 exceptions to the one-letter practice of setting attributes for search? And enter them as hex numbers.

Something like:
"attributes:_SPARSE_" = (find sparse files)
"attributes:_RECALLONOPEN_" = (find recall on open files)

[Herkules97]

Something like:
"attributes:_SPARSE_" = (find sparse files)
"attributes:_RECALLONOPEN_" = (find recall on open files)

For now you could make them in filters.
So for example attributes:0x00000200 can be made macro as _SPARSE_. You could name it anything. Sparse: could work
Search tab -> Organise filters...

[AntonyD]

I'm not looking for a solution at the moment - I'm suggesting to make a solution for everyone and on a permanent basis, not just for cases when someone didn't forget to make these macros/filters or something else like that. You might have made a bookmark, or stuck a sticky note on the monitor))))

Thus the meaning of the proposal is to support it, and not to come up with a bunch of workarounds for third-party work.

[void]

I will consider single-letters and words for sparse and recall-on-open.
I'm more likely to remember the hex value than the words..
Thanks for the suggestion.