181–189 of 189 posts
I miss Ubuntu (minus their amazon scandal...)
It's amusing (and infuriating) that file search - IMO, one of the most important features for a desktop O/S - has been utterly broken in Windows since Vista. On Windows 10, half the time it just hangs with "Searching files", displaying zero results. The other half, search simply says "Nothing found", even when I know there is a match. I just tested it with %USERPROFILE%/.docker - open up File Explorer and search for…
https://windowsforum.com/threads/windows-7-file-search-index...
Some of my scientific instruments are decades old and I like to be able to search back quite a number of years compared to most offices.
It's worth the effort to be the most reliable and repeatable you can get.
I don't like search to be slow or questionable, and of course it needs to return the same results from the same archive every time.
And indexing is not helpful, I usually want to search within every file.
Using a 2GHz processor with adequate memory and identical HDD, with no indexing and background services minimized, Best performance was found with W95, then W98, then Wxp, all on FAT32 volumes.
Wxp on NTFS, not so good.
NT6.x not acceptable.
On a modern 2GHz multicore processor and adequate memory and identical HDD (but different than above), with no indexing and background services minimized, Best performance is found with Wxp on FAT32 volumes. _its nice to know W9x would help out in this situation if really needed
Wxp on NTFS, not so good.
NT6.x less acceptable than ever.
.
The good thing about Google search was when it would return the same first-page results for anyone anywhere until something different had newly gained higher ranking among everyone altogether.
Going back a lot further, the promise of TV without commercial interruption was so long overdue it was wonderfully realized decades earlier in the 1970's by your friendly neighborhood cable TV company. That's why a private content-providing network was installed to premises to begin with, having better bandwidth than the original communication lines from the phone company monopoly.
Maybe they are all just trying to improve shareholder results through time at the expense of customer results, the old-fashioned way.
It's amusing (and infuriating) that file search - IMO, one of the most important features for a desktop O/S - has been utterly broken in Windows since Vista. On Windows 10, half the time it just hangs with "Searching files", displaying zero results. The other half, search simply says "Nothing found", even when I know there is a match. I just tested it with %USERPROFILE%/.docker - open up File Explorer and search for…
Use Everything instead. https://www.voidtools.com/
++This. Does the essentials such as real time [NTFS] drive monitoring from journals, small memory footprint, presents an accessible and responsive cancel dialogue when a operation will require lots of STATs (like sort many files by size), and has good boolean operators and semi-smart parsing of search lines and Bingo, ""quotes, optionally includes paths, stores file class (audio, video, doc etc) in short-index.
For full content search with several viewers and "jump to it and see" preview -- but only for selected document folders, I use DocFectcher. Matching files are presented in a windowpane you can further sort by relevance or -Date (my default), name or size. Reindexing is not done in real time when you change or add files but a small process watches indexed folders and just saves flags of what changes so index update can happen quickly when the main program is run.
The search behaves “as if” it’s using randomly-ordered keys in a random source dictionary, and it’s maddening. If I type what seems to be the same 3 letters a few times in a row, the result is always different: one time it acts like the app isn’t even installed, another time it finds the app (first choice), another time it finds some other random sub-component instead of the app with a weird file extension. Oh, and m…
https://open-shell.github.io/Open-Shell-Menu/ solves this problems for W10.
Can't say I ran into this particular bug, but I tend not to trust the search on Windows much anyway. I myself have implemented better text/prefix matching and ranking using a very simple SQLite database schema, on a far larger dataset than 'the local machine', yet Microsoft repeatedly fail at a task which should succumb easily even to brute-force approaches. They don't get to claim that it's a harder problem than ind…
Jeffrey Snover[1] likes to say that "Microsoft is incapable of sustained error", yet they've been incapable of building a good search for at least 15-20 years that I've experienced. Bing search is no competitor to Google, Explorer filesystem search is slow and untrustworthy, the search which integrates desktops to Windows server indexing of fileshares is slow and untrustworthy, on-premises SharePoint search has never…
Seriously though, have you checked out the search in O365? It is starting to get really good and wait till you see how this progresses in the next couple of years.
I think I’ll be proven right. :-)
Earlier quoted context omitted.
'sudo find / | grep ' has always worked as local search for me.
there's also, you know, locate
Earlier quoted context omitted.
I know why this happens. It happens because someone doesn't understand that search rankings vs. queries have to have a 'smooth' solution, and thinks they can tweak a few weightings here and there to get the results they think are 'correct' for the very specific cases they have in mind, without realising that this has a knock-on effect on the entire scoring space and you get odd singularities and stuff popping up as a…
I try not to say things like that anymore, you've never met the person and have no idea of the context or their skills. Could be that they were forced to change it at the 11th hour just before Windows 10 was being demo'd and it was never changed back. Could be a committee decision. Could be the programmer hated the surveillance installed by MS and so deliberately made the search bad.
I'd bet the engineer was listening to the 'someone' saying things like 'why don't you just' or 'it just needs to do this', or other things including the word 'just'.
I'd bet the engineer tried to explain the realities of how this stuff works, to 'someone' who's job didn't involve understanding what they were asking for, and reacted by demanding with the word 'just' instead of pretending to ask.