Mo-Search is a secure, powerful and easy to use Indexed Desktop Search that puts you in control of your data. By quickly and easily locating files and data, your time once again becomes your own.
Upon installation your computer is indexed (much like Google + Bing index the web). Once complete, AutoIndexer maintains your Index by transparently incorporating new files, and updating details on modified files. This search Index is what sets Mo-Search apart. Not only is blazing search speed achieved within the content of a million+ files, but results are ranked by relevance using a weighted average of factors including Hits, HitsDensity, ModifiedFrequency and ModifiedDate. Once initial indexing has completed, Mo-Search makes searching easy: Just start typing and AutoSearch shows results as you type. Optionally - Search filters provide finer grained filtering by Filename, Path, Modified Date, and Search Domain. Wildcards may also be used to broaden a search. And the more you search, the more your index is optimized searching gets faster! Hashtag Search Operators: Such as #NoDups (hide duplicate files in your results) provide additional seamless capabilities. To explore possible hash operators, in Advanced search mode simply type # into the search Text filter and Autocomplete will show the entire list. The Results list automatically Sorts by relevance, but can also Sort by filename, location (path), Size, Modified Date, and further Filter by File Type. The FileViewer provides quick navigation of matching files, plus a host of File tools: Analysis, Checksum, Email, Export, Print, Word Counts, Properties, IndexWords, and more. A suite of other tools are also included: File Duplicates (cleanup duplicate files), File Types (what's using the most space?), File Analyzer (Line/Frequency Analysis - great for Log files), Whois internet lookup, and File Index analysis.
Yes - 40 day timeout
- Optimization: Lower-overhead/faster AutoIndexer due to redesigned PathManager (Reworked Omit/Noise folder calculation, GetParentFolder heuristic, Path/File splitting, SystemVolume change ignore, simplified/consolidated maps, map 2x larger)
- Feature: Enhanced #NoDups search operator (2nd iteration) now properly works for *any* given query/combination of search filters. Previously for many query combinations, #NoDups resulted in files missing from search results (required newly developed zTemp
- Feature: New search operator #PathTooLong, which shows files having paths too long
- Feature: Save/Load dialog size + position for Tool dialogs: FileAnalyzer, FileDuplicates, FileTypes, and Whois
- Feature: By default TextIndex .properties files using the Text indexer
- Feature: When user right-clicks a folder in Windows Explore (or 3rd party Windows Explorer replacement) that is not an include path, allow the user to add this path (and do so before bringing Indexing dialog to the foreground)
- Bug: In AutoComplete boxes you may have encountered the "The parameter is incorrect" dialog. (6.x issue: new AutoComplete feature)
- Bug: In Search results list, only part of the matched Path and/or File highlighted. (6.x issue: new Results Highlight feature)
- Bug: When indexing/reindexing, a Path+File longer than MAX_PATH (260 characters) may have caused a crash. (longstanding: all versions)
- Bug: When indexing/reindexing, Paths were sometimes considered Includes, when they were actually Noise/Omit. This resulted in both index bloat and decreased performance. (longstanding: all versions)
- Bug: When indexing/reindexing a single drive, files weren't correctly counted. This resulted in the wrong count of files to index, and thus an incorrect time-remaining calculation. (6.x issue: New multithreaded counter)
- Bug: In FileAnalyzer, Files added with the [Add] button sometimes were not added. (6.x issue: new FileAnalyzer tool)
- Bug: In ResultsList, Filename not highlighted when it is a match for Text search terms. (6.x issue: new Results List highlighting feature)
- Bug: In ResultsList, at times only part of the matching text was highlighted. (6.x issue)
- Bug: In Search UI, Path AutoComplete list failed to show the most relevant paths. (6.x issue: new Autocomplete feature)
- Bug: In Search UI, Hang in AutoComplete due to logging race condition. (6.x issue: new AutoComplete feature)
- Bug: In Search UI, Small memory leak in AutoComplete lists. (6.x issue: new Autocomplete feature)
- Bug: In IndexWords Dialog, if AppDiag was not enabled the group box drew ghosted when it should not have been visible. (6.x issue: new IndexWords dialog)
- Bug: In Option, Crash when adding many extensions at the same time (e.g. [.xxx .yyy .zzz etc..]) into Options > More... > Text Index > Advanced > Add. (6.x regression)
- Bug: In ProgressDialog setting topmost showed the Progressbar when it should not have been visible. (6.x issue: new TopMost feature)
- Bug: General, Crash in screens like TextIndex > Advanced, where rows are loaded... and then *more* rows are loaded as the user add items. (6.x issue)
- Cleanup: Search ModifiedDate filters, when not enabled display as empty [ ] instead of empty with slashes [ / / ]. This streamlines control UI state recognition - easier to see when enabled
- Cleanup: In ProgressDialog, font and background headers have been tweaked to be more visually appealing
- Cleanup: FileViewer: In FindInFile field don't show dropdown when there are no matches. (Before - user typing within built-in FindInFile resulted in an empty drop box obscuring a chunk of FileViewer)
- Cleanup: Revised button theme - replaced garish blue with more a subdued silver
- Cleanup: Index words dialogs - consolidated a bunch of Statics controls into one single line-wrapping Edit control. Now complete info can be easily seen, scrolled, and copied
- Cleanup: Auto-omit SYSTEM.SAVE path, during Installation and in Options > Index > Defaults. (e.g. AutoDetect Paths)
- Cleanup: Quote'd Search (deep search) now searches files by Alphabetical order of Path. (previously, ordered by path-length which was seemingly random - not a good UX)
- Cleanup: Search screen draw tweaks (re-position logo upon screen widen/maximize, don't ghost controls after Options, case detect+fix in Path AutoComplete
- Cleanup: Reduced log noise for AutoWord_SearchText when AppDiag is enabled. (now only log when query duration greater than 0 milliseconds)
- Cleanup: When Path filter is specified generate SQL consistently employs inner join. (previous a mash of equa-joins and inner-joins)
- Diag: During indexing, when cleaning paths show the number of files cleaned at the each path within the log
Reviewing 6.0.0 Alpha (Oct 7, 2015)
I'm biased to Mo-Search for my needs. But I agree Archivarius is a good alternative that supports a very impressive number of file formats!!!
Unrelated - I want to comment on Mo-Search Indexing + Searching speed, and its evolution.
Mo-Search 3.x had a JET backend, and with 3 years of revisions + optimization it was slow. It worked fine if you had a limited amount of files to index/search, but otherwise not good. Really not good at all. Over time, this became a problem and led to...
Mo-Search 4.x switched the backend (database format) to SQLCE 3.5, which worked better. It scaled a lot better than 3.x, and improved slightly during 18 months of iterations, but still left a lot to be desired for larger amounts of files.
Mo-Search 5.x switched (again) to SQLCE 4.0. Also 5.x received a major architectural change of horizontal partitions (FullText index spread over 27 tables, instead of 1). Over the course of 3 years performance improved some more. But these iterations (up to 5.6.2) still hit a performance bottleneck for really large sets of files (including my 1+ million file test environment).
Mo-Search 6.x internally started as 5.6.3 (minor tweaks/fixes), but as development went along (and more feedback received) bigger changes/ improvements led to internal version 5.7 (also never released) mostly geared towards scalability. But as focus moved further to higher scale, and breaking the 4GB backend index barrier, the following major architectural changes coalesced. Items 1 and 2 improved performance; 3 and 4 were somewhat built on the new performance.
1) DataDeduplication - Can really improve indexing scalability in environments where duplicate files exist, such as software development with multiple branches. This works by de-duplicating index data (in RAM) during indexing, to reduce the amount of data written into the index. Then upon searching, very small/specific data subsets are re-duplicated into horizontally partitioned cache to facilitate proper ranking, combined filters, all the things the search UI provides. (Initially the goal was to perform search re-duplication purely in RAM, but complexity started to spiral - may possibly revisit in 7.x)
2) Database Sharding – Previously we’ve always had a single backend database file (3.x, 4.x, 5.x). Now it’s been split into 3, each holding different segments of the indexed data (and each of those horizontally partitioned). This allows us to break the 4GB index barrier (previous versions started performing poorly when the backend grew into the high 3GB range), and also improves performance regardless.
3) AutoSearch - In Simple Search mode (Just Text search box is visible), as you type... the results auto-populates (as does Google, and other tools including the very popular Locate32). This feature has been on the back burner for years, so its about time. Just a first rev, but still about time.
4) AutoComplete - in Advanced Search mode (Text search box, Filename search box, Path search box, etc, all visible), as you type... all relevant indexed data is used to AutoComplete. Previously only recent search terms were used to AutoComplete, and at most 400 recent terms. Now *ALL* indexed words, filenames, paths, are used in AutoComplete for the corresponding search box. If you have 1million files, that list is used to AutoComplete within the Filename search box. This feels a lot more productive to me, but... its a big change. (Like everything else - feedback is requested and hugely appreciated!!)
Internally, different versions of Mo-Search are re-tested to identify and track regressions (including indexing + searching performance). For a quick indexing performance comparison ran today on my 2011 Laptop (Intel SSD 320 + Core i7-2760). Here are the full index build durations:
4.0.13: 44 minutes (383k files, 1.52GB index, 132million words)
5.6.2: 21 minutes (383k files, 1.08GB index)
6.0.1: 12minutes (383k files, 681MB index)
And as the corpus size (volume of files) increases, older versions slow further at an increasing rate.
Your desktop/workstation/laptop and corpus (volume of files) will differ, and likely has different performance. But the points I'm trying to make: Performance matters. Usability matters. And so does constant work to keep moving forward.
Also, great comparative feedback on meauxsoft/Archivarius sites. Archivarius really makes meauxsoft.com look quite sad :-( I need to work on that.
Reviewing 4.0.16 (Apr 30, 2012)
Mo-Search *will* take longer to build the initial index because it indexes: file names AND file content too (Locate32 does NOT index file content). Once this initial index is built (33 minutes for me with 163,000 files/80 million words), the index is auto updated.
Locate32 works fine but doesn't search inside files, which is what I need daily.
@NyaR – how many Files & Words were indexed in those two hours? I bet a lot.
Reviewing 4.0.16 (Apr 30, 2012)
Thanks for making the app but it is unusable to me... nearly an hour to scan two terabytes of drives? Locate32 does this in minutes.
Reviewing 4.0.14 (Feb 22, 2012)
Mo-Search saved my life - or at least hours and hours of work. I've been doing a lot of revision of a lengthy academic paper and in cutting and pasting footnotes, I lost some of my original source documentation. Fortunately, I had saved a pre-revision copy and, with appropriate word choices, I was able to use Mo-Search to find the unedited footnotes in the unrevised manuscript to get me straightened out again in the revision document. I have lots and lots of Word files on my computer and I've found this program to be a tremendous help. You have to noodle around in it a bit to find all the features, but it's worth it. One hint I've found is that when you get ready to open a Word document (either file or folder), you can click on Mo-Search from that screen and search just that file or folder. It really is a terrific program. Thank you to the software writer for making it available.
No comments yet