KWiCFinder Support


To request support, or ask a question, either send an e-mail to the developer or post a message on the Users' Forum. There are direct links to both from the KWiCFinder 'Help' > 'About' dialogue box.

FAQ

When reporting problems, please run KWiCFinder, then click the menu "Help" > "Feedback to Developer".  This adds essential information about the version of KWiCFinder and of Windows that you are using to your message.

Troubleshooting
I get a JScript error message when I try to display a search report in the KWiC Sort & Analysis format.
This enhanced KWiC format requires some features of the version of JScript (Microsoft's implementation of JavaScript) that shipped with Internet Explorer 5.5. If you are using IE 5.0 and prefer not to update your browser, please click here to download the appropriate version of JScript for your system.
I cannot enter a search term in a search term field, so the "Run" button is never enabled.
The input routine both blocks out characters which are not supported by search engines and attempts to ensure that [ ] { } are balanced; supposedly incorrect characters are filtered out. Editing a search field can confuse this routine and block all input. This feature will be made more robust in the final release. Interim workarounds:  Press the "Clear" button to reset the field, then enter the text in a different field, or copy and paste text from another field or application.
When I run KWiCFinder, I get an empty search report with no citations.
Possible causes
  1. You have entered a query which matches no documents online.  
    Checklist
    • Are there spelling errors in the query?
    • Is the correct language specified? (note: KWiCFinder currently supports only the Western European character set; searches with other languages give unknown results.)
    • Are there criteria specified on the "Include" / "Exclude" panes (domain, specific terms) which eliminate possible matches?
  2. AltaVista has changed the format or redirection syntax of its search report pages and KWiCFinder has not yet responded to these changes. Please report the problem.
    KWiCFinder currently only uses the US-based version of AltaVista. Ultimately it will support various international AltaVista sites to improve performance from other countries and to provide alternatives when AltaVista modifies its search report pages. Plans call for supporting the Google search engine to provide an additional alternative.
  3. Since AltaVista has not always reported the number of matches, KWiCFinder now attempts a search and generates a search report no matter what. This confusing behavior will be addressed in the future.
KWiCFinder takes forever to complete my search.
Possible causes
  1. AltaVista is returning many false matches to your query. While KWiCFinder reports that it is fetching document number n, it may have downloaded, analyzed and rejected numerous documents.  False matches may include...
    • dead links (the document is no longer available, or the content has changed)
    • AltaVista found the terms you were seeking in portions of a document which are not displayed (KWiCFinder ignores comments and scripts, which usually contain extraneous material).
    • KWiCFinder options were chosen which focus search more narrowly than AltaVista (remedies:  try less-restrictive options, use "tamecards" instead of wildcards)
      • KWiCFinder options BEFORE, AFTER, or else NEAR with closer than 10 words apart specified (AltaVista NEAR reports all matches within 10 words on either side of your search terms)
      • KWiCFinder wildcards % or ? specified (AltaVista wildcard * reports all matches of 0-5 characters)
      • KWiCFinder sic specified (AltaVista reports all matches of lower / UPPER case, plain / special character, possibly including many combinations more common than a strict match of your query term)
  2. KWiCFinder's auto-update feature is downloading large program updates over a slow connection (either at your end or at the server end).
  3. KWiCFinder is trying to access a slow server or to download or analyze a very large document (the download timeout feature does not always work; limited memory or slow system speed can make these tasks very time-consuming).
  4. KWiCFinder's parser may not be robust enough for ill-formed HTML of source document.
When I launch the program I get an error message telling me that the file kfCore.dll could not be found. When I looked, it was in the same directory as KWiCFinder! What's the matter?
The most likely cause of this error is that kfCore.dll did not load properly because it could not find Internet Explorer version 5.0 or greater on the system. Please follow this link to download and install the current version of Internet Explorer.
When a search has completed, I get the error message "XML Display requires installation of MSXML3.DLL or greater."
If this file did not install properly, please download the latest version of the the Microsoft XML Parser. Please note which folder you save it in. Double-click on the file icon to install this update. You may have to reboot your system to complete the installation.
If this does not resolve the problem, please...

miniAPPolis Home | KWiCFinder Home
Screen Shots | Report Formats | Sample Search Reports
Download KWiCFinder | Register Interest
Support | Forum

Feedback Questions or Suggestions
Author William H. Fletcher
Version 14 September 2006
URL http://miniAPPolis.com/KWiCFinder/KWiCFinderSupport.html