I have a problem w/ my Everything install not indexing my F: drive. During an explicit index build, I captured the debug screen, which had these errors:
Are these related to the F: drive not being indexed? Some files from that drive are in the index, newer files are not. The forced rebuild did not help.
I am on 32 bit Windows 7 running Version 1.4.0.713b (x86).
Thanks.
Errors in debug screen
Re: Errors in debug screen
These "errors" are normal, and do not indicate any issue with your f: drive.
Please check if the f: drive is included in the index:
Please check if the f: drive is included in the index:
- In "Everything", from the Tools menu, click Options.
- Click the NTFS tab.
- Is the f: drive listed in the NTFS volumes?
- If so, select the f: drive.
- Please make sure Include in database is checked.
- If it is checked, please make a back up of any important on your F: drive and check it for errors:
- In My Computer, select the f: drive:
- Right click and select Properties.
- Click the Tools tab.
- Click Check now....
- Select Automatically fix file system errors.
- Click Start.
- If prompted to schedule the disk check the next time you restart the computer select Yes.
- Are any errors found? Is Everything able to index the f: drive after the disk check?
Re: Errors in debug screen
I ran through your checklists and everything is as should be. The disk did not any report errors.
I noticed something strange: searching for "lucene" (example) returns all folders with string lucene, but no files. I have a tone of PDF files, but when I type pdf or ext:pdf, the list is empty.
Should I ditch the beta version and do a re-install? Or is this something you'd be interested in having me debug? Thanks.
I noticed something strange: searching for "lucene" (example) returns all folders with string lucene, but no files. I have a tone of PDF files, but when I type pdf or ext:pdf, the list is empty.
Should I ditch the beta version and do a re-install? Or is this something you'd be interested in having me debug? Thanks.
Re: Errors in debug screen
I realized this all started happening after enabling Bookmarks. I deleted all bookmarks and things are now back to normal.
It seems that selecting a bookmark seems to have a persistent and lasting effect. Maybe there should be a visual indicator that a bookmark is in effect. Would save a lot of time.
It seems that selecting a bookmark seems to have a persistent and lasting effect. Maybe there should be a visual indicator that a bookmark is in effect. Would save a lot of time.
Re: Errors in debug screen
If it happens again, please check the bottom right of the status bar, any selected filter, or search option that may effect your search is displayed.
You can right click the status bar to toggle search options, or double click an item in the status bar to disable it.
You can right click the status bar to toggle search options, or double click an item in the status bar to disable it.