Minor incompatibility with subst drives

[cwm9]

If you use the SUBST command to map a folder in a drive to a new drive letter, Everything doesn't quite behave as expected.

When looking at the volumes list, select the mapped drive will cause an access error unless you are logged in as an administrator or running as a Everything as a service; which is fine, but if you do not exclude the mapped drive using the exclude folder function, Everything crawls to a halt frequently as it repeatedly times out, even if the drive is marked "do not index".

If you are in administrative mode and try to index the mapped drive, Everything indexes the mapped drive, but very, very slowly, and without updates from the NTFS log.

Ideally, Everything would recognize that SUBST has been used and drive the contents of the mapped drive directly from the parent drive so that it can receive updates from the NTFS log and not have to treat the drive as a networked drive.

Thanks.

[therube]

select the mapped drive will cause an access error unless you are logged in as an administrator or running as a Everything as a service

So this happens when you are NOT running as Admin & also do NOT have the Everything service running?
(And at that point, you wouldn't be seeing much of anything, results wise, except maybe from preexisting .db data.)

If you are in administrative mode

So you have SUBST the same drive both as an Administrator & also as a "normal" user?

(As with mapped drives, SUBST looks like you would need to do it both ways - for the map/SUBST to be seen by both Admin & normal.)

[void]

Everything cannot see subst drives from other users.

Please make sure you run Everything as the same user that adds any subst drives.

Everything should be treating SUBST drives to NTFS folders as a NTFS volume under Tools -> Options -> NTFS.

Could you please share some more information about your setup.
Have you added the SUBST drive as a folder index under Tools -> Options -> Folders?
Do you have different drive mappings for each user?