I have a mapped network drive and it doesn’t seem to want to index. I added it to the index list but it always says last index was Never.
When I tell it to manually index by hitting Update Now it says it’s indexing but it says it’s finished within 30 seconds which I’m skeptical of because there is a ton of stuff in that drive.
No matter how many times I have it update or what I set the interval to, it always says Last Updated is never.
I saved this as a draft because after writing it I realized that the network drive did seem to be indexed, but after rebooting my PC it seems to no longer by indexed anymore. So it seems like I lose the index whenever I reboot and I have to manually re-index?
Update on this, I have a network drive that says the index was rebuilt 1 minute ago but I get zero search results for it. I can type folder:foo and it finds nothing except things on my C drive.
I purchased pro specifically for this and have found that it doesn’t work. There are other threads in here complaining about the same and so far, no word from the dev. I have emailed support asking for a refund. Not a word in response. Seems like I spent 20 bucks for nothing.
Ok, i am experiencing the same issue. I have been using the latest Listary v6 as well as the Beta and external network drives i mapped do not get index. i have the same issue as described above. It shows up as “indexed never”.
There is one thing i noticed though, its not ideal, and i hope to find a solution for the actual issue, but it seems you can make it work if you index not the mapped drive letter, but the network path instead.
So i have a drive, P:, this is mapped to //nas-server/projects
If i add P:\ to listary, it does not index it.
If i add //nas-server/projects, it does.
The only issue i have is that, if i use it to open files, it also opens it following the //nas-server/projects/ file path, which is actually a problem because i mapped it to P:/ for a reason because i do the same for other PCs, where P is mapped to another folder. So while it works on one PC, this workflow is causing problems for me and my specific workflow when i open edited files on another computer where P: is mapped to another drive location.
So i would still love to have a solution for that if possible.
Maybe with this hint, its easier to find the issue and fix it.
Well it was previously working on the same machine using Listary V5 so i would assume its possible. But if you know by any chance what these registry settings are i would give it a try.
Thanks for the info.
I was actually under the impression i am using the latest beta as i was auto updating and just updated this morning via the auto update, but the latest beta that got installed was V6.3.1.81
So i manually installed it, now it seems to work and actually scan my network drive as usual.
