"found count" in RED font

[admin]

Still I don't see how merely selecting items could take so long. Let's see what else you forgot to mention...

1) How do you select?
2) Do you use any Custom Columns?
3) Show Folder Sizes enabled?
4) Your computer is extremely old and slow and your WLAN is shaky as quicksand?

[chasster123]

As i wake this morning....
My system is is 4Ghz XEON 8-core, Hmmm. not slow. (W10 Enterprise)
Gig. network at all points.
Primary access is to QNAP NAS or second system with 2-SATA chassis attached (8-drives).
I run xyplorer from my system or the second system which holds the extra SATA drives.
The second system is a AMD 3-Core, 2.6 Ghz system (W7).

[chasster123]

config is what is in the previous attachment - nothing special, select top folder and search within.

[admin]

config is what is in the previous attachment - nothing special, select top folder and search within.

What are we talking about, selecting or searching? Please read and reply carefully.

[chasster123]

Problem, from client view, multiple User Profile sets are stacked into one set - creating duplicates.
Need to reach that folder structure (several in different locations on this network).
Select target directory (top) and Search using several filters (i.e. *(?).*, desktop.ini, etc.).
Each search produces results, from a few to 300,000+.
Select the search results (unwanted item list) and delete and wait.
Expecting to wait longer for larger sets but - how long to wait is the question.
In the last few weeks i've identified and deleted ~1TB of duplicates.
A slow process with Windoze.....

[admin]

So, it is about deleting.

Well, deleting is outsourced to Windows at the moment. Cannot make Windows faster.

There are plans to come up with a native delete in XYplorer. No date yet.

[chasster123]

Great plan - hope sooner than later.
I'm in the process of deleting 368,000 (?) files and soon to seek these (??).
So far, i'm near 20-minutes in the queue "preparing to recycle" this first batch.
I'll try to be more patient and allow more time for this batch to finish being prepared before seeking smaller sets of these discovered and then deleting batches.

Otherwise - great program.

[chasster123]

So it took an hour to locate the files and near the hour to have this error (attached).
Error 14
Out of String Space.

I'm attempting to delete ~1/3 at a time this moment.

[admin]

Looks like you are hitting physical boundaries. 368,000 files in one go is just too much. You have to split the job in smaller bites.

[chasster123]

What's the limit. This is a pain to get to the error (time) and have to restart and chop up in chunks not knowing how much is going to be accepted.

[jupe]

I'm sure Don will answer your query (personally I doubt there will be a set hard limit because it probs depends on path lengths) but in the meantime, not sure if you think it helps, but if you weren't aware already you can limit the search results returned, eg: *(?).* /l=200000 of course you'd need to run multiple searches if it returns the max, but it should enable you to "Select All" the results to delete after each search. Also if it is always going to be a number within the brackets it theoretically might be slightly faster to use a search term like this *(#).* /l=200000 /E instead. edit: in retrospect probs not true, untested though.

[chasster123]

Great feedback. I have a small group of folders to explore this week and will try the count limit string.