Hi. I'm Brandon. I'm a geek, and I work on Search technology for Windows at Microsoft. This is my blog.
Picture
categories:
- All
- Africa (11)
- Apple (19)
- April Fools (1)
- Blog updates (12)
- Blogging (17)
- cars (6)
- Cool Stuff (26)
- Desktop Search (54)
- Funny stuff (6)
- Games (29)
- Imported from old blog (80)
- iPhone (8)
- Life of Brandon (35)
- Macintosh (15)
- Microsoft (24)
- Movies & TV (6)
- MSN (6)
- Music (14)
- News (92)
- Other (67)
- Podcasts (1)
- Politics (17)
- Search (48)
- Seattle (15)
- Start++ (19)
- TED (1)
- The worst ever (19)
- Vista On MacBook (6)
- WDS Development (22)
- WDS FAQ (9)
- Weight loss (3)
- Windows Live (20)
- Windows Search Blogs (1)
- Windows Shell (14)
- Windows Vista (39)
- WS4 (4)
August 22nd, 2006 at 10:54 am
How stable is Beta 2?
Do I need to uninstall any existing version of WDS before I install this?
August 22nd, 2006 at 10:59 am
You should be able to upgrade from previously released versions.
Overall it’s a stable release and pretty close to final. That’s why we want your feedback if you do run into any trouble =)
August 22nd, 2006 at 12:13 pm
How close is this to WDS 3.0 in current Vista builds, particularly the indexing engine and API as opposed to the search UI?
Will there be updated API docs for WDS 3.0 soon?
Cheers
August 22nd, 2006 at 12:30 pm
Sean - The engine and API are essentially the same as what’s in Vista RC1 (most of the binaries are in fact identical) and the builds are very close.
I’ll make another post as soon as I find out about the API docs, I believe there should be an update soon.
August 22nd, 2006 at 12:58 pm
Hi Brandon,
Great stuff X64 support!
Can WDS 3.0 be used within a Terminal Server environment (well Citrix Presentation Server 4.0) now that its service based rather than per user? Has testing been done for this scenario? I’m involved in a project later this year to deploy X64 Windows Terminal Servers, this may just be a ‘killer app’ :o)
Cheers
August 22nd, 2006 at 1:04 pm
Janson - Yes it should work great in a TS environment. The service-based indexing model is extremely compelling in that scenario.
Please do share your experiences!
August 22nd, 2006 at 1:51 pm
Brandon - cheers for the comment. I sure will report what I find! Is it possible to add a network location to the search locations? If not… why not??
Thanks
August 22nd, 2006 at 1:54 pm
Unfortunately this release cannot index network shares (or FAT32 volumes for that matter). Both of those should be supported either in an upcoming release.
August 22nd, 2006 at 2:02 pm
Thats a real shame… in a corporate environment where users files are held on network locations (folder redirection) this really loses its usefulness (for exmaple I don’t know of anyone who would save users data to the Terminal Servers in a Terminal Server environment). I’m hoping the ‘upcoming release’ will be 3.0 RTM and not say 3.1
August 22nd, 2006 at 4:09 pm
Hi Brandon, how will we approach indexing network shares.
I had the problem described here:
http://channel9.msdn.com/wiki/default.aspx/Channel9.DesktopSearchBugReports
See “Multiple WDS Indexers pointing at a network share causes file sharing violations”
I’ve had people email me personally asking if I found a solution. My answer is no and in addition I’ve never had any feedback from a Microsoft representative that they’re even aware of the problem. Is this something that will be doable without problems 3.0?
Also, where’s the best place to send feedback/feature requests for 3.0 beta 2? Thanks.
P.S. - WDS kicks some desktop search ass. Thanks for the great product.
August 22nd, 2006 at 5:07 pm
You can post feedback to the forum here:
http://forums.microsoft.com/msdn/showforum.aspx?forumid=127&siteid=1
WDS 3.0 and Vista have undergone huge amounts of testing around file locking. I’ll check with them, but I’m certain that the team testing the UNC/FAT protocol handler are considering the scenario you mentioned.
August 22nd, 2006 at 5:25 pm
[...] Brandon who works on the Search Technology team for Microsoft said that “the engine and API are essentially the same as what’s in Vista RC1 (most of the binaries are in fact identical) and the builds are very close.” Hey, if they find something in Vista that can add more value to XP then I highly welcome it. [...]
August 22nd, 2006 at 8:25 pm
FAT32 indexing is working fine here.
August 22nd, 2006 at 8:26 pm
[...] Microsoft today has released Beta 2 for Windows Desktop Search 3.0 (WDS) for Windows XP SP2 and x64 too. I’ve been waiting for the UI end to be included with WDS 3.0. Previously, only the Search Indexer was part of the Beta, which was needed for Outlook 2007 Beta 2’s enhanced search. [...]
August 23rd, 2006 at 2:15 am
please please please add RSS searching and *.eml searching (Live Mail Desktop EML files). I cannot search my RSS feeds and emails from WLMD in this version.
August 23rd, 2006 at 3:32 am
RSS (Outlook Feed) is indexed, just tested. I don’t use Live Mail / ELM Files but I can see in the options menue, that the filetype is also included.
August 23rd, 2006 at 4:13 am
I have redirected “My Documents” folder to the other computer in my 2-computer peer-to-peer network. In Desktop Search 2.x it worked perfectly. In Desktop Search 3, I cannot even find a way to add the mapped network drive to the index. My pst-file is also on the other computer, and that gets indexed just fine. So what’s up with that? I have to store my documents inside my local computer to get them indexed, but e-mail I can store on another computer?!! So please could somebody help me out, how do I get Indexer to index My Documents.
August 23rd, 2006 at 8:03 am
I intall WDS 3.0 and restart. When i go to
Windows Desktop Search Options… | Advanced | File Types, then a dialog appear with that message:
An exception occured while trying to run “shell32.dll,Control_RunDLL “srchadmin.dll””
August 23rd, 2006 at 8:47 am
FindMyStuff dead? I don’t see any mention of this on the FindMyStuff page. Did the death of WINFS kill FindMyStuff?
August 23rd, 2006 at 9:57 am
@Jonne:
From Brandon’s reply in comment 8 above:
“Unfortunately this release cannot index network shares (or FAT32 volumes for that matter). Both of those should be supported either in an upcoming release.”
August 23rd, 2006 at 10:04 am
FindMyStuff is not dead and has nothing to do with WinFS. We should be talking about it more soon.
At the moment we’re focused on being able to *show* something before we do more talking =)
August 23rd, 2006 at 10:22 am
[...] The improvement is in the speed at which it searches - lightning fast. What took 4-5 seconds to pull up before now takes less than a second…I’m truly impressed. The resources that WDS consumes have also been cut down. The flaw, on the other hand, has prompted me to uninstall the app within 30 minutes of installing it: no support for network shares. According to Brandon Paddock’s blog, this - as well as support for FAT32 drives - will be added in the next release. Access to network shares is a must for me so, unfortunately, I’m going to have to bail on this beta but WDS 3.0 certainly shows promise. There’s no doubt about that. [...]
August 23rd, 2006 at 10:46 am
@Jeremy
Ok, I missed that.
I guess I have to go back to Desktop Search 2 or Google desktop then. Wonder what “both of those should be supported either in an upcoming release” exactly means; will it be supported in Desktop Search 3.0 Final or Desktop Search 4 in two years… I would call this a major feature cut, though… Unless is it just cut from Beta 2, but then there would have to be a Beta 3 or similar to test it out, I assume. I find it rather ridiculous though that the main search indexer of Vista cannot search and index anything but local hard drives, it sounds like a bad joke…
August 23rd, 2006 at 6:30 pm
Hi Brandon,
Was having separate installers for XP and 2003 necessary? The sad consequence is that as a Windows 2003 Server SP2 beta tester I cannot install WDS 3 beta 2. This is the log file:
[KB914783.log]
1.031: ================================================================================
1.031: 2006/08/23 22:29:06.437 (local)
1.031: d:\32c418bdd8d10fcfcc0115\update\update.exe (version 6.2.29.0)
1.031: Hotfix started with following command line: /quiet /norestart
1.031: CheckSystem: ServicePack version Mismatch
1.031: DoInstallation: CheckSystem Failed: 0xf06b
1.031: Setup has detected that the Service Pack version of this system
is newer than the update you are applying.
There is no need to install this update.
1.031: Update.exe extended error code = 0xf06b
1.031: Update.exe return code was masked to 0×643 for MSI custom action compliance.
August 24th, 2006 at 8:27 am
Diego - that’s a known issue that’s being worked on (supporting 2003 SP2). I believe the seperate installer is necessary because of a dependency on other system updates that are different between the two versions.
Jonne - WDS 3.0 on XP and Vista can search more than just local hard drives. It supports the same Protocol Handler interface that has been used in the past to index all kinds of data stores including Outlook, Lotus Notes, Mozilla Thunderbird, and others.
However, due to the change to a service-based indexer (instead of per-user) there are additional complications with indexing networks shares. The default File System handler runs in the context of the service, and thus doesn’t have the permissions necessary to index remote shares. Our goal is to offer this support at or around the time WDS 3.0 is released. It is a key feature not only for corporate scenarios, but also for a lot of us on the team (including myself!).
It’s also worth noting that on Vista you can already index redirected folders or network shares that have “Offline Files” enabled. This is because there’s already support for indexing the Client-Side Cache of this data. However I’m not sure if that works on XP/2003, I’ll have to ask around.
August 24th, 2006 at 12:25 pm
Brandon,
Is there any log or debug file that we could lookup in order to determine why a particular file failed to be indexed?
August 24th, 2006 at 3:45 pm
I was really hoping that the registry key permissions problem that crashed installation in Beta 1 would get resolved for this release. Unfortunately, it’s pretty much exactly the same, but instead of “Access Denied”, the error message is now more generic-the installation failed, check the log. When I check the log, I see that its failing when trying to install registry keys.
There’s already a KB article about the registry key problem, advising going one by one to change perms on the keys. That’s not possible-there are tons. I’ve probably adjusted 20 & there’s always another one causing the crash.
Any chance this issue will be resolved before release or any advice to get around the problem now? It’s really constraining my satisfaction with Office 2007, an otherwise fantastic upgrade.
August 27th, 2006 at 8:10 am
In the final version of v3, will WDS be able to…
1) Search the contents of Windows Live Desktop Mail emails?
2) Search through our Window Live Contacts information?
August 29th, 2006 at 4:25 pm
Does the production version of WDS really support Lotus Notes indexing via that add-in or is it all FUD? I have not been able to get it to work nor have I seen anyone else get it working. It doesn’t appear to have any integration with the Notes UI and it doesn’t prompt for the password. (The way Google Desktop Search does this is by having you allow the action from the Notes client itself.)
Any guidance?
August 29th, 2006 at 10:50 pm
Does v3.0 index more files than v2.6.5? - My situation: wds doesn’t index more than 165,000 of my 1,500,000 local files.
2nd: Will WDS support classifying other file types as photo or music. I’d like to see .flac files supported.
September 2nd, 2006 at 3:48 pm
[...] Windows Desktop Search 3.0 Beta 2 released. [...]
September 5th, 2006 at 7:13 pm
Brandon, I’m looking for information about the WDS administrative APIs. More exactly I what to add programatically a specified folder to the WDS.
Any guidance?. Thanks. Please contact me if you want.
September 6th, 2006 at 7:07 am
How should problems be reported? After upgrading, when I preview a found Outlook document, I get a popup that says
“A Runtime Error has occurred. Do you wish to Debug? Line: 22 Error: Syntax Error” The line of JavaScript shows: if ( == 1)
September 7th, 2006 at 7:27 am
To Matt re Lotus Notes add-in: I had it working with 2.6.5. I don’t know if it works with 3.0. For 2.6.5, I followed
http://www.microsoft.com/technet/prodtechnol/windows/search/dtstshoot.mspx#EPH and also installed WindowsDesktopSearch-KB917979-x86-ENU.exe
September 12th, 2006 at 2:20 am
You had shown example to use APIs of WDSQuery.dll. This dll was part of SDK for WDS 2.X release. How can I achieve same with WDS3.0 as there is no SDK avilable for 3.0 version?. Please let me know if there is any other method? Basically I want to create my own search index for my own documents and wants to get the result progrmatically.
September 12th, 2006 at 3:05 am
How to query WDS programmatically(VB.NET) so that the results can be displayed by .NET application. Since WDS 3.0 does not contain SDK, how to query existing index from .NET application.
September 13th, 2006 at 9:53 pm
Regarding the SDK -
The WDS 2.x “BETA” SDK is no longer supported in WDS 3.0. However, the new APIs are no longer BETA (or won’t be when WDS 3.0 and Windows Vista ship) and are part of the Windows SDK (formerly “Platform SDK” for Vista).
Uriel - Sounds like you want the Crawl Scope Manager APIs. Try here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/reference/ifaces/isearchcrawlscopemanager/isearchcrawlscopemanager.asp
September 14th, 2006 at 4:08 am
Are you planning to implement proximity searches (a NEAR b; a WITHIN/n b; a AFTER b). This is a must for serious searches.
September 19th, 2006 at 12:50 am
Brandon, can you suggest any approach to integrate WDS 3.0 in VB.NET . From my program(VB.NET) I want to query for a given string. I had no issue with WDS 2.6.5 since it had SDK.
September 19th, 2006 at 9:37 pm
Hi,
I installed the wds 3 beta 2 and cannot make it work with pdf. It acts as if it s indexing pdfs but actually cannot get from ifilter v 6.0 the content of the file. I also tried ifilter pdf+. Nothing. (I did enable searching the content of pdfs).
Do you know how to make it work? I did not see any one complaining about this.
I have windows XP and office 2007 B2TR.
Thanks
September 25th, 2006 at 11:44 pm
Hi Brandon, I got the news that SDK for WDS3.0 is avilable and it is integrated in Windows vista SDK (http://www.microsoft.com/downloads/details.aspx?FamilyId=117ECFD3-98AD-4D67-87D2-E95A8407FA86&displaylang=en). Cit it really true? If so how can I identify WDS3.0 related dlls and query interfaces?
October 4th, 2006 at 8:48 am
This product is useless without it working with folder redirection. The fact that other services from Microsoft require/install this makes it doublely so. when is this feature slated to become reality?
October 4th, 2006 at 9:06 am
Pressorv - I’m not sure what you mean. WDS should work fine with Folder Redirection.
If you’re talking about redirecting to a UNC, then you should install the UNC FAT protocol handler:
http://www.microsoft.com/downloads/details.aspx?FamilyID=f7e981d9-5a3b-4872-a07e-220761e27283&DisplayLang=en
Or on Vista, you can enable Offline Files and the client-side cache will be indexed automatically.
October 4th, 2006 at 11:21 am
Hi Brandon,
Updated Office 2007 to B2TR.
Decided to get the new version of WDS reqiured by B2TR.
Tried installing. It fails. Reading through the log file below denotes a partial install.
It causes Explorer to crash every time I run search.
Please see my post here for more details: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=787321&SiteID=1
Thanks,
/e
October 5th, 2006 at 8:29 am
Brandon,
As this seems the best place to get to SOMEONE who can answer non-dev questions about WDS 3 I thought I’d run this one by you.
I use https://www.foldershare.com to sync files between my work and home computers. It was also great to be able to search for any file on either machine (even the ones not in a shared folder) from the website UI. However, it seems the foldershare devs haven’t picked up the changes to the 3.0 sdk making 3.0 unusable for the foldershare search functionality.
So here’s my question. Is there anyone actually working on foldershare since it’s purchase by MS? If so do they plan to enhance the site/feature set to utilize 3.0? Maybe they don’t know about the changes to the SDK yet? Someone should let them know.
As I was originally a paid subscriber to the foldershare service, before it was purchased and made a free product by MS, I hope it survives and isn’t left to simply be a feature of feature of Windows Live Messenger.
Thanks for any feedback you can provide.
-Jeremy
October 5th, 2006 at 8:58 am
Hi Jeremey,
Unfortunately I can’t comment on unannounced/unreleased products and services =/
October 5th, 2006 at 2:07 pm
Hi Bradon,
Windows Desktop Search: Add-in for UNC/FAT http://www.microsoft.com/downloads/details.aspx?FamilyID=f7e981d9-5a3b-4872-a07e-220761e27283&DisplayLang=en
is only for “Windows Server 2003; Windows XP Service Pack 2″
Do you know when will a version for Win 2k3 x64 be published?
Thanks
October 5th, 2006 at 2:44 pm
Does it not install on x64?
I don’t know anything about x64 support with that add-in off-hand, but I’ll try to follow-up with someone who does.
You might also want to ask about it on the forum here:
http://forums.microsoft.com/msdn/showforum.aspx?forumid=127&siteid=1
Actually, from the post there it sounds like it installs but that the control panel applet doesn’t work because it’s 32-bit. I’ll see what more I can find out.
October 13th, 2006 at 9:41 am
Any chance we will see soon a new beta for this product?
When is the final launch date?
Thx,
John
October 13th, 2006 at 9:53 am
Hi John, we aren’t planning any more public releases before the final WDS 3.0 release. I don’t know an exact date for that but it shouldn’t be far off.
October 15th, 2006 at 4:38 am
Can the WDS (with SDK) be used to create an index of a specific folder tree rather than everything. FOr example just to index and search c:\docsarchive. Then be able to search through my own application just this index and document collection?
October 18th, 2006 at 1:29 pm
WDS 3.0 Beta 2 is required for beta 2 of office 2007 with the beta 2 technical refresh. Problem is install fails……Great product guys. Can’t wait for the release! Perhaps it will actually install properly and not fail with permission errors.
October 26th, 2006 at 10:07 am
What do we need wds for, if not to index pdf’s. Yet microsoft is persistant at not enabling this in their latest WDS 3.0.
I have no words to describe this behaviour.
October 26th, 2006 at 10:43 am
WDS supports indexing any data format or data store for which you have the appropriate add-in installed.
However, Adobe has a very significant bug in their IFilter implementation that prevents it from working with WDS 3.0. *They* are aware of the problem and are working on a release that supports WDS 3.0. As much as we all want that add-in, Microsoft has no control over their release schedule.
October 31st, 2006 at 7:45 pm
So if indexing PDFs is important to you then you are best not to install WDS 3.0 until Adobe updates their IFilter? Is that the reason that version 3 hasn’t been linked up on the main Microsoft WDS page?
November 1st, 2006 at 6:50 am
Hey Brandon,
I am supposed to customize WDS (especially WDS 3.0) in a way that it should crawl through the web pages
using HTTP address of the seed (parent) url.
I am trying hard from my side but I would be happy to get some suggestions and approaches (ideas)
from your side.
Waiting for early response.
Regards,
Vivek Singh
November 2nd, 2006 at 3:55 pm
I have a huge Exchange inbox - multi-gig, and I rely on WDS to find my email. Now 3.0 looks to insist on Exchange Cached Mode, which I do not have/want due to the size of my inbox. Sigh, looks like I will have to uninstall and go back to 2.5.
November 2nd, 2006 at 4:53 pm
WDS 3.0 can index uncached exchange, but it is disabled by default. It needs to be enabled via group policy, and this is a change I’m going to suggest for the next update to WDS 3.0 that’s being planned (to go back to the enabled-by-default settings from 2.x).
You can enable it by creating a DWORD registry key in:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search
called “PreventIndexingUncachedExchangeFolders” and setting it to a value of 0.
November 3rd, 2006 at 7:42 am
Hey Brandon,
I am supposed to customize WDS (especially WDS 3.0) in a way that it should crawl through the web pages
using HTTP address of the seed (parent) url.
I am trying hard from my side but I would be happy to get some suggestions and approaches (ideas)
from your side.
Waiting for early response.
Regards,
Vivek Singh
November 14th, 2006 at 7:50 am
Hey,
1. Is it possible to run WDS on a Windows2003 SBS server and have it index all files in certain folders?
2. Is it possible for it to index all emails and email attachment of certain email accounts?
3. Is it possible for the server to maintain these indexes and give the client computers read-only access to them? That way, each client would not have to build and constantly maintain a separate index? I’ve read about GDS and http://www.dnka.com which gives a similar functionality.
4. Is it easy to restrict user-access to this common index on a per-user basis? E.g. allow Peter to have access to John and Audrey’s email accounts but not to the bosses? Allow Peter to have access to the common files on the server but not to sensitive folders?
If this sort of question is inappropriate for this forum, please disregard it. Any advise would be greatly appreciated though.
Thanks.
Erik
November 20th, 2006 at 5:25 am
Brandon,
was checking on WDS3.0 and saw tat it doesnt support keywords like NEAR, AFTER,.. (keywords like
AND, OR, NOT are only supported). I was not sure if these keywords are really not supported by
WDS3.0. It would be of gr8 help if you can comment on this asap.
can you also tell me as which interface can be used for reindexing, start/stop/pause indexing,
get status of indexing. thnx in advance!
December 10th, 2006 at 7:18 pm
I read everything and I am confused. I want to add desktop search within Terminal Server.
1) Will WDS 3.0 work?
2) Will Vista and the new server programs support this feature?
We have a TS that access data on a seperate Data server.
Thanks.
December 28th, 2006 at 12:07 pm
The unc indexing add-on doesn’t work under XP Pro X64 edition, do you know if it will be fixed or another option made available?
December 28th, 2006 at 5:07 pm
64-bit OSes are currently not supported (which affects me as well since I run Vista x64).
I don’t know what the plan is around x64 support but I’ll try to find out after the new year.
January 5th, 2007 at 2:27 am
I wondered if someone could help me out. I’m trying to index every file stored on a network drive (the network drive is located on a NetApp SAN device). All I need is an index of the filenames - I don’t need to search any file metadata. I’ve tried WDS v2 and have taken out all the extension exceptions but will this index the filenames of every single file on the drive - if not can I force this? Am I right in thinking v3 will only index extensions which are in the list and ticked?
Also, how does WDS know when and where any changes happen on a network drive?
Thanks in advance.
January 6th, 2007 at 6:30 pm
Will we be able to launch programs with WDS again?
Thanks
January 11th, 2007 at 2:26 pm
I have several questions. First, I’ve installed the add-in for files on Microsoft Networks, but I am unclear if 3.0 beta 2 indexes NTFS drives.
Second, on the message about installing the DWORD value to index uncached Exchange, should the Windows Search key already exist, or do I need to also create that key?
Third, after creating the DWORD for uncached Exchange, do I need to force manual re-indexing? restart? both?
January 15th, 2007 at 11:16 pm
I love WDS, but want to search network drives… something that the Add-in for Files on Microsoft Networks should resolve, if I can every finish the installation. The installer hangs on “This may take a few minutes.”, which stays up for hours, until I hold down the power button (TaskMan availed me not). I waited 6 hours on a Win2K3 SP1 system and this is my first time trying it on an XP SP2 system — I’m stuck on the same dialog and will let the computer sit overnight. I’m 0 for 2 on installing the UNC/FAT add-in and wondering if you could point me in the right direction because I am having terrible luck finding info on the it.
January 20th, 2007 at 10:41 pm
Windows desktop search 02.06.5000.5378 gets installed when installing SolidWorks 2007 (a popular CAD software). When telling WDS to index a UNC path & all indexing is complete. Opening modifying & saving a word doc a few times (between 1 - 10 times repeatedly) to this UNC path can cause your modified word 2000 or 2003 file to suddently become read-only & the user is forced to as SaveAs & change the filename in order to not loose their work. This happens when:
1. your the only one indexing this location & you have “prioritize indexing” enabled & you modify & save a word doc a few times…. or
2. multiple machines without “prioritize indexing” turned on index the same UNC location & a few of them are idle & start indexing while users are saving word docs. Obviously this one is the bigger problem & compounds itself the more machines out there.
Is this a known issue? any workaround for this while we wait for updates? I found this link: http://support.microsoft.com/default.aspx/kb/927018/en-us — but it seems confusing & offers no solution.
I provide techsupport with this CAD package & I fear this one will come up many many times soon as people start to use this search more & more - I am hopeing to find the answer before I get bombared. crossing my fingers that you may be able to help!
January 24th, 2007 at 2:43 pm
Steve,
I’m not an MS person, but I’ve tried to report this error to as many places as I can think of without success in getting an answer.
The easiest way to reproduce the problem is to create a large file 40 MB file (Excel or Word preferably but I don’t think it matters) and put it in the UNC path your WDS is indexing. Open the file from your machine and click save. This should cause the error your seeing every time. It happens with 2.x and 3.0.
I’m pretty sure WDS only knows not to index a file if it’s LOCAL hard drive has no activity. Since the save is being carried out on a network drive WDS sees the new file and, even though it’s not complete, starts to index it. When it starts to index it puts the “SHARE ACCESS = READ” lock on the file. When Word is done saving the file it tries to re-access the saved version but WDS has a lock and Word will through the error. Virus detection programs had this problem years ago. I’m surprised the WDS team can’t use the same sort of trickery to solve it as the anti-virus guys did.
February 9th, 2007 at 6:54 am
Brandon,
It is cool that you have this site. I have a question that I dont know how to get answered. In the 3.0 Search, I would like to index my C, CPP, CS, ect. I try to add these extensions in the Advanced options File Types. It looks like it adds them, but when I revisit that tab nothing is there. Any Ideas?
February 9th, 2007 at 1:36 pm
Hi Howard - those filetypes should be indexed by default using the Plain Text IFilter, which means they should work automatically.
Are you running on XP or Vista? Unfortunately they won’t be preview in the preview pane for those on Vista out-of-the-box, though I’m sure someone will make a previewer available soon.
Are the folders with your source files included in the list of locations to index? (you need to be an Administrator to alter those)
February 16th, 2007 at 9:38 pm
Brandon Says: “64-bit OSes are currently not supported (which affects me as well since I run Vista x64). I don’t know what the plan is around x64 support but I’ll try to find out after the new year.”
Have you found anymore out about this, (or a way around the problem). I unfortunately tried installing UNC-FAT in Vista64 before finding this site and realizing that it was not working
March 9th, 2007 at 6:25 pm
Brandon,
I am on vista. I use mail and live mail desktop. the problem is that vista does not seem to do an instant search on my mail from the os shell. it searches great from the apps. when I put in a term, it just seems to go on and on and on and pulls up one or two. Any tips?
thanks
May 10th, 2007 at 11:49 am
Hi brandon,
I’m sure you will be able to help. I have just removed Windows Desktop Search from my computer coz it doesn’t close down properly when I shut down my machine. I get two other messages at the end about windowssearch.exe and spssearch and have to close these down manually too. My machine was also working very very slowing in fits and starts. I haven’t shut down again since rebooting after the removal, so don’t know if the messages will still come up, but machine is definately responding much quicker.
My question is; will I have caused a problem on my system by removing WDS? ie will programmes not run properly without it?
Please help
Regards
A novice!
May 11th, 2007 at 8:20 pm
I just downloaded WDS for win XP Pro and it is a real pain. Under “email” search, I ask it to search on partila character strings on either the subject or the sender and I get “0″ results returned. What kind of serch is that?
Help would be appreciated.
I remember about a year ago I downloaded an unsupported MS search tool that allowed me to search on folder or email and it worked fine for partial email subjects or senders. Do you know the name of it and is it still available? I am on a different machine otherwise I would use it.
Thanks.
June 29th, 2007 at 5:25 pm
Brandon,
The following MS website HAD been tracking a problem with re-indexing every time you rebooted your machine.
It has gone all quite with MS completely silent the past month.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1297957&SiteID=1
What’s up? This is frustrating at best!
Thanks,