Problem with drive listing - no files/folders displaed

[findexer]

So I have a special problem with my U: drive.

I had years ago another drive attached as U: and now this year I had a new drive also called U:
In the local index this worked perfectly.

But recently I removed the drive (the other one had been removed years ago) and put it into another computer.

So when I now export the contents of the local DB into a file list and import it on my main PC, it doesn't show anything anymore for the U: drive(s).
I also removed the older data from the index in the NTFS and folder settings.
The file list is ok, when I open it using the File List Editor it shows the contents correctly.
But included as file list in the main index, it doesn't show (probably of the clash of U: naming).

Is there any way I can rename one of the drives to another letter or query only one of the drives to remove it from the index?
I have not found a way to differentiate between both drives yet (as there is no serial number of the drive in the file list or anything that makes it identifiable)

image.png (6.97 KiB) Viewed 264 times

[therube]

Your picture appears to show that you have not opened a filelist?
As in, no .efu file name appears in the (whatever you call it) bar.

[findexer]

The picture shows the main database which has the file list added per "Indexes > File Lists"
as said, only the files/folders from drive U: are not shown, which is twice in the index, somehow Everything gets confused by that, but only when a File List is used.

[therube]

I'm not sure what is going on or why, but,
in the .efu, if you were to manually change the drive letter in the .efu, then reload it, then you should be able to access its' contents via the newly changed drive letter - I would think.

So in Vim (text editor), I did something like,

%s/^"C:/"Z:/

,
which says to find all lines that start with "C: & replace that with "Z: .

On reload of the .efu, I can then distinguish between my local C: drive files & my .efu C: drive files, as they are now shown as Z:.

You could try something similar, going from U: to V: (or whatever).

Backup first.
And even better if you tested in a different, test -instance.


You might check in Everything.ini (or similar), ntfs_volume_paths=, is U: shown in there?
Or for that matter, any place that U: may happen to turn up?

[findexer]

What helped was removing the top "u:" in the file list editor for the older drive I did it already, but I think it's not the best solution.

Btw: I can't just search and replace the whole file, since both drives which were initially there are mixed in the EFU file.

That's why I asked if it was possible to to only export one drive (regardless of the letter) to an EFU. But it seems there is no way to differentiate both drives when it's in the main database anymore.

The problem is, I had both drives in my main database on both systems. On the main system I removed both from the database, but on the other it's still there.
So I exported everything matching u: from the second system to the file list. And that's where the problem happens on import on the main system.

I think a possible workaround would be to give the U: drive another letter on the system where it's attached and remove it from the database. But I fear this will happen again, since I have used all my drive letters already and begin to double use the ones I had in the past.
Possibly best would be to have a serial number column in the index, to differentiate both drives.
What also would help if file lists behave the same as the main database. Possibly this is even a bug, having two same letter drives in the EFU, while it's working having them in the main database.

[findexer]

You might check in Everything.ini (or similar), ntfs_volume_paths=, is U: shown in there?
Or for that matter, any place that U: may happen to turn up?

ntfs_volume_paths shows this:

ntfs_volume_paths="A:","B:","C:","C:","D:","E:","E:","F:","F:","H:","I:","I:","K:","K:","M:","O:","P:","Q:","R:","R:","S:","T:","V:","V:","W:","Y:"

which means, that I have successfully removed U: from the main DB (also since the drive is not attached anymore).

The problem is only with it conflicting within the EFU file it seems.

In the main DB, does it use the ntfs_volume_guids to differentiate the multiple drive names?

So would it be possible to extract only one of the U: drives from my other machine's main database somehow using the GUIDs to a EFU file? I think then I could make 2 EFU files and rename each drive within to another path. So I could even make the drives mapped to a global root like C:\u1\ C:\u2 etc.

[void]

In the main DB, does it use the ntfs_volume_guids to differentiate the multiple drive names?

Yes.
Everything tracks volumes by Volume mount path, Volume GUID and volume root.

For Example:
Volume mount path = C:
Volume GUID =\\?\Volume{01234567-0123-0123-0123-012345670123} (also known as the volume name)
Root = usually blank, but can be a relative path if using SUBST (for example: Program Files\Everything )

So would it be possible to extract only one of the U: drives from my other machine's main database somehow using the GUIDs to a EFU file? I think then I could make 2 EFU files and rename each drive within to another path. So I could even make the drives mapped to a global root like C:\u1\ C:\u2 etc.

Please try the fsi: search function.

fsi: will limit the results to a specific File System Index.

For example, to find files on your first file system index, include the following in your search:

fsi:0

To find files on your second file system index, include the following in your search:

fsi:1

It will require some trial and error to get the correct file system index for your U: drive.