Recent changes to FAQ

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Thu, 09 Oct 2025 14:04:24 -0000

--- v39
+++ v40
@@ -16,7 +16,7 @@
 * Windows, installed version: `C:\Users\<username>\AppData\Roaming\DocFetcher\conf\settings-conf.txt`
 * Linux, non-portable: `/home/<username>/.docfetcher/conf/settings-conf.txt`
 * macOS application bundle: `/Users/<username>/.docfetcher/conf/settings-conf.txt`
-* All Portable versions: `<applicationfolder>\conf\settings-conf.txt`
+* All portable versions: `<applicationfolder>\conf\settings-conf.txt`

 Now, first close DocFetcher, then open the settings file in a text editor and add the lines `ShowManualOnStartup = false` and `PreferHtmlPreview = false` in it. While you're at it, you may also add the line `HotkeyEnabled = false` to disable the global hotkey, which can cause issues too. Save and close the file, then try to start DocFetcher.

@@ -124,7 +124,7 @@
 * Windows, installed: `C:\Users\<username>\AppData\Roaming\DocFetcher`
 * Linux, non-portable: `/home/<username>/.docfetcher`
 * macOS application bundle: `/Users/<username>/.docfetcher`
-* All portable versions: `<applicationfolder>/indexes`
+* All portable versions: `<applicationfolder>\indexes`

 For customizing the location of the index files, have a look at the file `misc/paths.txt` inside the DocFetcher folder.

</applicationfolder></applicationfolder></username></username></username></applicationfolder></applicationfolder></username></username></username>

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Thu, 09 Oct 2025 14:03:39 -0000

--- v38
+++ v39
@@ -75,11 +75,11 @@
 DocFetcher can't always find numeric strings like 20090614_P6140036.jpg.
 ---

-This is not really a bug, but a consequence of the fact that DocFetcher splits documents into individual words during indexing, a.k.a. tokenization. This is done in order to build a dictionary (i.e. the index), which DocFetcher then uses to do quick searches. In general, DocFetcher works best with natural language, but not quite as well with text containing digits or special characters.
+This is not really a bug, but a consequence of the fact that DocFetcher splits documents into individual words during indexing, a.k.a. tokenization. This is done in order to build a dictionary (i.e., the index), which DocFetcher then uses to do quick searches. In general, DocFetcher works best with natural language, but not quite as well with text containing digits or special characters.

 That being said, there's an Analyzer option in the Advanced Settings which allows you to switch to an alternative tokenization mechanism that works better with source code and other kinds of text not written in natural language.

-Additionally, take a look at the Query Syntax section in the manual. Some of the concepts explained in there, e.g. wildcards and phrase searches, might help to work around the above issues.
+Additionally, take a look at the Query Syntax section in the manual. Some of the concepts explained in there, e.g., wildcards and phrase searches, might help to work around the above issues.

 How do I exclude ".svn" folders from indexing?
 ---
@@ -106,7 +106,7 @@

 Certain errors can be circumvented as follows:

-* Re-saving files in an old format in a newer or an alternative format, e.g. re-saving old MS Office files in the newer MS Office 2007 format or with LibreOffice.
+* Re-saving files in an old format in a newer or an alternative format, e.g., re-saving old MS Office files in the newer MS Office 2007 format or with LibreOffice.
 * Treating unreadable files as plain text. See [this bug report](http://sourceforge.net/p/docfetcher/bugs/8/) for further explanation.
 * Enabling mime-type detection for files on which DocFetcher fails because they have the wrong file extension. For example, if some of your `.doc` files aren't MS Word files, you can enable mime-type detection for `.doc` files by putting the pattern `.*\.doc` in the pattern table on the indexing configuration dialog and setting "Detect mime type" as the action to be performed.

@@ -121,9 +121,10 @@

 The location of the index files depends on the version of DocFetcher and the operating system:

-* If you're using portable DocFetcher, the index files will be in the `indexes` folder inside the DocFetcher folder.
-* If DocFetcher was installed on Windows (i.e. is non-portable), the index files can be found here: `C:\Users\<username>\AppData\Roaming\DocFetcher`
-* If you're using the macOS application bundle of DocFetcher, the index files can be found at: `/Users/<username>/.docfetcher`
+* Windows, installed: `C:\Users\<username>\AppData\Roaming\DocFetcher`
+* Linux, non-portable: `/home/<username>/.docfetcher`
+* macOS application bundle: `/Users/<username>/.docfetcher`
+* All portable versions: `<applicationfolder>/indexes`

 For customizing the location of the index files, have a look at the file `misc/paths.txt` inside the DocFetcher folder.

@@ -189,7 +190,7 @@
 How can I index files that don't have a file extension?
 ---

-To index files without file extension (i.e. without the dot in the filename), add the following rule in the pattern table on the indexing dialog:
+To index files without file extension (i.e., without the dot in the filename), add the following rule in the pattern table on the indexing dialog:

 * Pattern (regex): `[^\.]*`
 * Match Against: Filename
@@ -204,8 +205,8 @@

 The error message means the folder you're trying to index contains more levels of subfolders than DocFetcher can handle with its current settings. The workaround is to either move the subfolders around in order to reduce the maximum folder depth, or to change the settings. How the latter is done depends on your operating system:

-* **Windows**: Move the `DocFetcher.bat` file from the `misc` folder inside the DocFetcher folder one level up into the DocFetcher folder (important, otherwise the `DocFetcher.bat` won't run). Now open the `DocFetcher.bat` file in a text editor. In the last line, you can see a setting `-Xss2m`. Set this to a higher value, e.g. `-Xss4m`. From now on, always launch DocFetcher through the `DocFetcher.bat`.
-* **Linux and macOS**: Open the launch script `DocFetcher.sh` in a text editor. In the last line, you can see a setting `-Xss2m`. Set this to a higher value, e.g. `-Xss4m`.
+* **Windows**: Move the `DocFetcher.bat` file from the `misc` folder inside the DocFetcher folder one level up into the DocFetcher folder (important, otherwise the `DocFetcher.bat` won't run). Now open the `DocFetcher.bat` file in a text editor. In the last line, you can see a setting `-Xss2m`. Set this to a higher value, e.g., `-Xss4m`. From now on, always launch DocFetcher through the `DocFetcher.bat`.
+* **Linux and macOS**: Open the launch script `DocFetcher.sh` in a text editor. In the last line, you can see a setting `-Xss2m`. Set this to a higher value, e.g., `-Xss4m`.

 FYI, the `-Xss` setting is the so-called "thread stack size" in megabytes that, among other things, limits the number of folder levels DocFetcher can handle.

@@ -217,7 +218,7 @@
 If you index a certain folder, say `C:\path\to\folder`, and then try to index a subfolder of that folder, say `C:\path\to\folder\subfolder`, DocFetcher will refuse and complain that overlapping indexes aren't allowed. There are technical reasons for this:

 * If you create overlapping indexes, the same file may show up multiple times on the result list. Theoretically, DocFetcher could make an effort to remove duplicate results, but this would probably slow down searching.
-* If a certain folder occurs multiple times in the Search Scope pane, multiple checkboxes will be associated with it, so it may be possible for the folder to have conflicting check states, e.g. checked and unchecked at the same time. This would raise the question of whether DocFetcher should filter out results from that folder or not. And even if we set an arbitrary rule to resolve this conflict (e.g. show file under this folder if the folder is checked at least once), then this scenario would still complicate the underlying program logic.
+* If a certain folder occurs multiple times in the Search Scope pane, multiple checkboxes will be associated with it, so it may be possible for the folder to have conflicting check states, e.g., checked and unchecked at the same time. This would raise the question of whether DocFetcher should filter out results from that folder or not. And even if we set an arbitrary rule to resolve this conflict (e.g., show file under this folder if the folder is checked at least once), then this scenario would still complicate the underlying program logic.

 Why doesn't DocFetcher show a progress bar during indexing?
 ---
</applicationfolder></username></username></username></username></username>

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Thu, 09 Oct 2025 13:56:37 -0000

--- v37
+++ v38
@@ -13,10 +13,9 @@
 ---
 On some systems, the embedded web browser that is used for displaying the manual and HTML files can crash the entire program. As a workaround, disable the embedded web browser by modifying DocFetcher's settings file. Look for the settings file in one of the following locations:

-* Non-portable/installed versions:
-  * Windows: `C:\Users\<username>\AppData\Roaming\DocFetcher\conf\settings-conf.txt`
-  * Linux: `/home/<username>/.docfetcher/conf/settings-conf.txt`
-  * macOS: `/Users/<username>/.docfetcher/conf/settings-conf.txt`
+* Windows, installed version: `C:\Users\<username>\AppData\Roaming\DocFetcher\conf\settings-conf.txt`
+* Linux, non-portable: `/home/<username>/.docfetcher/conf/settings-conf.txt`
+* macOS application bundle: `/Users/<username>/.docfetcher/conf/settings-conf.txt`
 * All Portable versions: `<applicationfolder>\conf\settings-conf.txt`

 Now, first close DocFetcher, then open the settings file in a text editor and add the lines `ShowManualOnStartup = false` and `PreferHtmlPreview = false` in it. While you're at it, you may also add the line `HotkeyEnabled = false` to disable the global hotkey, which can cause issues too. Save and close the file, then try to start DocFetcher.
</applicationfolder></username></username></username></username></username></username>

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Thu, 09 Oct 2025 13:55:37 -0000

--- v36
+++ v37
@@ -7,19 +7,19 @@
 ---
 Buying a copy of [DocFetcher Pro](https://docfetcherpro.com/), the commercial big brother of DocFetcher, is equivalent to making a donation, plus you get a bunch of new features.

-If you don't need those features and/or DocFetcher Pro costs more than you're willing to donate, you can "buy" the otherwise [free demo](https://docfetcherpro.com/demo-purchase/) of DocFetcher Pro for a price of your choosing.
+If you don't need those features and/or DocFetcher Pro costs more than you're willing to donate, you can "buy" the otherwise [free demo](https://docfetcherpro.com/docfetcher-pro/) of DocFetcher Pro for a price of your choosing.

 I can't start DocFetcher at all. What do I do?
 ---
-If you're running the *portable* rather than the installed/non-portable version of DocFetcher, note that the application folder has to be unpacked to a location where you have write permissions. The reason for this is that on the first start, the program figures out what operating system it's running on and then tries to unpack the right library files into a subfolder under its own folder, and this will fail without write permissions.
-
 On some systems, the embedded web browser that is used for displaying the manual and HTML files can crash the entire program. As a workaround, disable the embedded web browser by modifying DocFetcher's settings file. Look for the settings file in one of the following locations:

-* If DocFetcher was installed on Windows: `C:\Users\<username>\AppData\Roaming\DocFetcher\conf\settings-conf.txt`
-* All portable versions of DocFetcher: `<applicationfolder>\conf\settings-conf.txt`
-* macOS application bundle: `/Users/<username>/.docfetcher/conf/settings-conf.txt`
-
-If the settings file doesn't exist at the expected location, create a new, empty text file there named `settings-conf.txt`. Now, first close DocFetcher, then open the settings file in a text editor and set `ShowManualOnStartup = false` and `PreferHtmlPreview = false` in it. While you're at it, you may also set `HotkeyEnabled = false` to disable the global hotkey, which can cause issues too. Save and close the file, then try to start DocFetcher.
+* Non-portable/installed versions:
+  * Windows: `C:\Users\<username>\AppData\Roaming\DocFetcher\conf\settings-conf.txt`
+  * Linux: `/home/<username>/.docfetcher/conf/settings-conf.txt`
+  * macOS: `/Users/<username>/.docfetcher/conf/settings-conf.txt`
+* All Portable versions: `<applicationfolder>\conf\settings-conf.txt`
+
+Now, first close DocFetcher, then open the settings file in a text editor and add the lines `ShowManualOnStartup = false` and `PreferHtmlPreview = false` in it. While you're at it, you may also add the line `HotkeyEnabled = false` to disable the global hotkey, which can cause issues too. Save and close the file, then try to start DocFetcher.

 Some users reported startup issues caused by faulty NVIDIA drivers, version 378.xx. See [this thread](https://sourceforge.net/p/docfetcher/discussion/702424/thread/1fbbe4ef/?limit=25#4578).

@@ -206,7 +206,7 @@
 The error message means the folder you're trying to index contains more levels of subfolders than DocFetcher can handle with its current settings. The workaround is to either move the subfolders around in order to reduce the maximum folder depth, or to change the settings. How the latter is done depends on your operating system:

 * **Windows**: Move the `DocFetcher.bat` file from the `misc` folder inside the DocFetcher folder one level up into the DocFetcher folder (important, otherwise the `DocFetcher.bat` won't run). Now open the `DocFetcher.bat` file in a text editor. In the last line, you can see a setting `-Xss2m`. Set this to a higher value, e.g. `-Xss4m`. From now on, always launch DocFetcher through the `DocFetcher.bat`.
-* **Linux and OS X**: Open the launch script `DocFetcher.sh` in a text editor. In the last line, you can see a setting `-Xss2m`. Set this to a higher value, e.g. `-Xss4m`.
+* **Linux and macOS**: Open the launch script `DocFetcher.sh` in a text editor. In the last line, you can see a setting `-Xss2m`. Set this to a higher value, e.g. `-Xss4m`.

 FYI, the `-Xss` setting is the so-called "thread stack size" in megabytes that, among other things, limits the number of folder levels DocFetcher can handle.

@@ -267,7 +267,7 @@

 * **Windows**: In the folder `DocFetcher\misc`, there's a file named `DocFetcher.bat`. Open the file in a text editor, add the parameter described in the next section, then save and close the file. Importantly, move the `DocFetcher.bat` file one level up into the DocFetcher folder. From now on, always start DocFetcher by double-clicking the `DocFetcher.bat` file.
 * **Linux**: Open the file `DocFetcher.sh` in a text editor, add the parameter described in the next section, then save and close the file. Launch DocFetcher via the modified `DocFetcher.sh` file.
-* **OS X**: Follow the instructions given in [this forum thread](https://sourceforge.net/p/docfetcher/discussion/702424/thread/59a983b2/).
+* **macOS**: Follow the instructions given in [this forum thread](https://sourceforge.net/p/docfetcher/discussion/702424/thread/59a983b2/).

 Now, regarding the language parameter that needs to be added: The last line of the launcher file starts with a "java" command which launches the DocFetcher process. It looks like this:

</applicationfolder></username></username></username></username></applicationfolder></username>

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Thu, 09 Oct 2025 13:48:22 -0000

--- v35
+++ v36
@@ -11,30 +11,23 @@

 I can't start DocFetcher at all. What do I do?
 ---
-
-If you experienced problems with the *installed* version of DocFetcher, consider using the *portable* version instead ([download page](http://docfetcher.sourceforge.net/en/download.html)). The latter runs on all supported platforms and does not try to detect or download Java runtimes. However, note that the portable version has to be put in a location where you have write permissions. The reason for this is that on the first start, the program figures out what operating system it's running on and whether the operating system is 32-bit or 64-bit. It then tries to unpack the right library files into a subfolder under its own folder, and this will fail without write permissions.
-
-In some cases where DocFetcher doesn't start, the solution is to uninstall all currently installed Java runtimes and then reinstall the latest Java runtime from the [Java website](http://java.com). On that website, be sure to pick either the 32-bit or the 64-bit Java runtime, depending on whether your operating system is 32-bit or 64-bit.
-
-Another potential problem: Running DocFetcher with a memory setting of more than 1 GB requires a 64-bit Java runtime. It will not work with 32-bit.
+If you're running the *portable* rather than the installed/non-portable version of DocFetcher, note that the application folder has to be unpacked to a location where you have write permissions. The reason for this is that on the first start, the program figures out what operating system it's running on and then tries to unpack the right library files into a subfolder under its own folder, and this will fail without write permissions.

 On some systems, the embedded web browser that is used for displaying the manual and HTML files can crash the entire program. As a workaround, disable the embedded web browser by modifying DocFetcher's settings file. Look for the settings file in one of the following locations:

-* If DocFetcher was installed on Windows:
-    * Windows 2000/XP: `C:\Documents and Settings\<username>\Application Data\DocFetcher\conf\settings-conf.txt`
-    * Windows Vista and later: `C:\Users\<username>\AppData\Roaming\DocFetcher\conf\settings-conf.txt`
-* Portable DocFetcher: `DocFetcher\conf\settings-conf.txt`
-* OS X Application Bundle: `/Users/<username>/.docfetcher/conf/settings-conf.txt`
-
-If the settings file doesn't exist at the expected location, create a new, empty text file there named `settings-conf.txt`. Now, first close DocFetcher, then open the settings file in a text editor and set `ShowManualOnStartup = false` and `PreferHtmlPreview = false` in it. While you're at it, you may also set `HotkeyEnabled = false` to disable the global hotkey. Save and close the file, then try to start DocFetcher.
+* If DocFetcher was installed on Windows: `C:\Users\<username>\AppData\Roaming\DocFetcher\conf\settings-conf.txt`
+* All portable versions of DocFetcher: `<applicationfolder>\conf\settings-conf.txt`
+* macOS application bundle: `/Users/<username>/.docfetcher/conf/settings-conf.txt`
+
+If the settings file doesn't exist at the expected location, create a new, empty text file there named `settings-conf.txt`. Now, first close DocFetcher, then open the settings file in a text editor and set `ShowManualOnStartup = false` and `PreferHtmlPreview = false` in it. While you're at it, you may also set `HotkeyEnabled = false` to disable the global hotkey, which can cause issues too. Save and close the file, then try to start DocFetcher.

 Some users reported startup issues caused by faulty NVIDIA drivers, version 378.xx. See [this thread](https://sourceforge.net/p/docfetcher/discussion/702424/thread/1fbbe4ef/?limit=25#4578).

 If none of the above helps, try launching DocFetcher via one of the alternative launchers:

-* **Windows**: In the folder `DocFetcher\misc`, there's a file named `DocFetcher.bat`. Move this file one level up into the `DocFetcher` folder. Then open a command prompt and use the `cd` command to navigate to the `DocFetcher` folder, like so: `cd C:\Program Files (x86)\DocFetcher`. Then try launching DocFetcher from the command prompt by entering `DocFetcher.bat` and pressing Enter. If DocFetcher doesn't start, then chances are an error message will be printed in the command prompt. Post this error message on the [DocFetcher forum](http://sourceforge.net/p/docfetcher/discussion/702424/).
+* **Windows**: In the folder `DocFetcher\misc`, there's a file named `DocFetcher.bat`. Move this file one level up into the `DocFetcher` folder. Then open a command prompt and use the `cd` command to navigate to the `DocFetcher` folder, like so: `cd C:\Program Files\DocFetcher`. Then try launching DocFetcher from the command prompt by entering `DocFetcher.bat` and pressing Enter. If DocFetcher doesn't start, then chances are an error message will be printed in the command prompt. Post this error message on the [DocFetcher forum](http://sourceforge.net/p/docfetcher/discussion/702424/).
 * **Linux**: First, make sure the executable flag has been set on the `DocFetcher.sh` launcher. If that doesn't help, do the following: Open a terminal and use the `cd` command to navigate to the `DocFetcher` folder. Then try launching DocFetcher from the terminal by running `./DocFetcher.sh`. If DocFetcher doesn't start, then chances are an error message will be printed in the terminal. Post this error message on the [DocFetcher forum](http://sourceforge.net/p/docfetcher/discussion/702424/).
-* **OS X**: On OS X, DocFetcher is started via a shell script located inside the DocFetcher [application bundle](https://en.wikipedia.org/wiki/Bundle_(macOS)). If you're using portable DocFetcher, the application bundle is just the "DocFetcher" entry inside the DocFetcher folder that looks like an executable but is actually a folder with the extension ".app". Open a terminal and use the `cd` command to navigate to the folder `Contents/MacOS` inside the application bundle, then launch the DocFetcher script from there. If it doesn't start, an error message might be printed in the terminal. Post this error message on the [DocFetcher forum](http://sourceforge.net/p/docfetcher/discussion/702424/).
+* **macOS**: On macOS, DocFetcher is started via an executable located inside the DocFetcher [application bundle](https://en.wikipedia.org/wiki/Bundle_(macOS)). If you're using portable DocFetcher, the application bundle is just the "DocFetcher" entry inside the DocFetcher folder that looks like an executable but is actually a folder with the extension ".app". Open a terminal and use the `cd` command to navigate to the folder `Contents/MacOS` inside the application bundle, then launch the DocFetcher executable from there. If it doesn't start, an error message might be printed in the terminal. Post this error message on the [DocFetcher forum](http://sourceforge.net/p/docfetcher/discussion/702424/).

 I can't start the PortableApps version of DocFetcher! Help!
 ---
@@ -49,11 +42,6 @@
 `X:\CommonFiles`

 2. There must be a `Java` folder inside the `CommonFiles` folder, containing the Java Runtime to run DocFetcher on. Importantly, if you go with jPortable 64, the folder must *still* be named `Java`, and *not* `Java64`, unlike what the jPortable 64 installer's default path would suggest.
-
-On Windows 2000, DocFetcher crashes when I try to start it, what do I do?
----
-
-In the crash report, there's probably a line that says "SWTException: Unable to load graphics library \[GDI+ is required\]". This indicates that you need to install a package called GDI+ for supporting advanced graphics operations. Here's where you can download GDI+: http://www.microsoft.com/en-us/download/details.aspx?id=18909

 How is the score for each document calculated?
 ---
@@ -135,10 +123,8 @@
 The location of the index files depends on the version of DocFetcher and the operating system:

 * If you're using portable DocFetcher, the index files will be in the `indexes` folder inside the DocFetcher folder.
-* If DocFetcher was installed on Windows (i.e. is non-portable), the index files can be found at the following places:
-    * Windows 2000/XP: `C:\Documents and Settings\<username>\Application Data\DocFetcher`
-    * Windows Vista and later: `C:\Users\<username>\AppData\Roaming\DocFetcher`
-* If you're using the OS X Application Bundle of DocFetcher, the index files can be found at: `/Users/<username>/.docfetcher`
+* If DocFetcher was installed on Windows (i.e. is non-portable), the index files can be found here: `C:\Users\<username>\AppData\Roaming\DocFetcher`
+* If you're using the macOS application bundle of DocFetcher, the index files can be found at: `/Users/<username>/.docfetcher`

 For customizing the location of the index files, have a look at the file `misc/paths.txt` inside the DocFetcher folder.

@@ -319,23 +305,6 @@
 * [Apache Tika](http://tika.apache.org/)
 * [Apache Solr](http://lucene.apache.org/solr)

-Why are the DocFetcher installer and the other packages so large (> 30 MB)?
----
-
-This is mainly due to the fact that DocFetcher is shipped with lots of built-in text extraction libraries, some of which are quite big. The worst offenders are the libraries for MS Office and PDF files. However, the developers of these libraries aren't to blame here: The libraries have to be big because the respective file formats are immensely complex.
-
-Why does DocFetcher require this god-awful thing called Java?
----
-
-The word "Java" refers both to a platform for programs to run on, and to a programming language for writing such programs. Here's why DocFetcher was written in the Java language: Java is a far easier and far more convenient language to develop in than, say, C++. Java's advantages include: Automatic memory management, 10x less error-prone, 10x less effort to make it work on different platforms. If DocFetcher had been written in C++ instead, development time would probably have been twice as long, and the resulting program would have only half the features, but twice the number of bugs. And perhaps you would have to pay for it, or download some crack, because far fewer developers are willing to go through the ordeal of messing with C++ in their unpaid sparetime.
-
-Also, while Java programs still start up slowly and memory usage is still high, the runtime performance has improved significantly in recent years and is now comparable to native code as produced by C/C++ programs, [according to Wikipedia](http://en.wikipedia.org/wiki/Criticism_of_Java#Performance). (Case in point: I've never heard anybody say that DocFetcher's indexing algorithm is "slow".)
-
-As for Java security, here’s the Truth most non-tech people never seem to quite understand:
-
-- The Java runtime by itself is no more dangerous than the .NET framework or any other application runtime. Update the Java runtime if you feel like doing so, but those updates are primarily for the sake of improved performance and fewer bugs and crashes, not for the sake of security.
-- The only serious danger when using Java comes from the Java *plugin* running in your browser. It’s best to disable the plugin altogether. If you’re using a modern, up-to-date browser, the plugin is probably already disabled. If you must run the plugin, then you’d be well advised to keep it up to date at all times.
-
 Why does DocFetcher take up so much RAM?
 ---

</username></username></username></username></username></username></applicationfolder></username></username></username></username>

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Tue, 16 Jan 2024 10:18:15 -0000

--- v34
+++ v35
@@ -45,7 +45,6 @@
 The main problem with installing jPortable or jPortable 64 is that their installers give no clue about where they need to be installed to make DocFetcher work. There are basically two rules you need to follow:

 1. The `CommonFiles` folder needs to be placed *beside* the `DocFetcherPortable`folder, not inside it or anywhere else. For example, if you installed the PortableApps version of DocFetcher into `X:\`, then the `CommonFiles` folder should also be in `X:\`, like so:
-
 `X:\DocFetcherPortable`
 `X:\CommonFiles`

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Tue, 16 Jan 2024 10:15:47 -0000

--- v33
+++ v34
@@ -38,10 +38,18 @@

 I can't start the PortableApps version of DocFetcher! Help!
 ---
-If double-clicking the DocFetcherPortable.exe launcher gives you an error message saying something along the lines of "DocFetcher requires a Java Runtime Environment", you need to make sure jPortable is installed in the right location. There's a simple rule: The `CommonFiles` folder needs to be placed *beside* the `DocFetcherPortable`folder, not inside it or anywhere else. For example, if you installed the PortableApps version of DocFetcher into `X:\`, then the `CommonFiles` folder should also be in `X:\`, like so:
+If double-clicking the DocFetcherPortable.exe launcher gives you an error message saying something along the lines of "DocFetcher requires a Java Runtime Environment", you need to make sure jPortable is installed in the right location.
+
+There are actually two versions of jPortable, called jPortable and jPortable 64. The former runs on both 32-bit and 64-bit operating systems, and the latter only on 64-bit operating systems. However, in the 32-bit version, DocFetcher's so-called memory limit cannot be set higher than about 1 GB. This could result in out-of-memory errors when trying to index large files. In the 64-bit version, the maximum value for the memory limit is much higher.
+
+The main problem with installing jPortable or jPortable 64 is that their installers give no clue about where they need to be installed to make DocFetcher work. There are basically two rules you need to follow:
+
+1. The `CommonFiles` folder needs to be placed *beside* the `DocFetcherPortable`folder, not inside it or anywhere else. For example, if you installed the PortableApps version of DocFetcher into `X:\`, then the `CommonFiles` folder should also be in `X:\`, like so:

 `X:\DocFetcherPortable`
 `X:\CommonFiles`
+
+2. There must be a `Java` folder inside the `CommonFiles` folder, containing the Java Runtime to run DocFetcher on. Importantly, if you go with jPortable 64, the folder must *still* be named `Java`, and *not* `Java64`, unlike what the jPortable 64 installer's default path would suggest.

 On Windows 2000, DocFetcher crashes when I try to start it, what do I do?
 ---

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Mon, 15 Jan 2024 15:21:40 -0000

--- v32
+++ v33
@@ -38,10 +38,10 @@

 I can't start the PortableApps version of DocFetcher! Help!
 ---
-If double-clicking the DocFetcherPortable.exe launcher gives you an error message saying something along the lines of "Error: Could not create the Java Virtual Machine", you need to make sure jPortable is installed in the right location. There's a simple rule: The `Common Files` folder needs to be placed *beside* the `DocFetcherPortable`folder, not inside it or anywhere else. For example, if you installed the PortableApps version of DocFetcher into `X:\`, then the `Common Files` folder should also be in `X:\`, like so:
+If double-clicking the DocFetcherPortable.exe launcher gives you an error message saying something along the lines of "DocFetcher requires a Java Runtime Environment", you need to make sure jPortable is installed in the right location. There's a simple rule: The `CommonFiles` folder needs to be placed *beside* the `DocFetcherPortable`folder, not inside it or anywhere else. For example, if you installed the PortableApps version of DocFetcher into `X:\`, then the `CommonFiles` folder should also be in `X:\`, like so:

 `X:\DocFetcherPortable`
-`X:\Common Files`
+`X:\CommonFiles`

 On Windows 2000, DocFetcher crashes when I try to start it, what do I do?
 ---

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Mon, 15 Jan 2024 15:18:57 -0000

--- v31
+++ v32
@@ -36,6 +36,13 @@
 * **Linux**: First, make sure the executable flag has been set on the `DocFetcher.sh` launcher. If that doesn't help, do the following: Open a terminal and use the `cd` command to navigate to the `DocFetcher` folder. Then try launching DocFetcher from the terminal by running `./DocFetcher.sh`. If DocFetcher doesn't start, then chances are an error message will be printed in the terminal. Post this error message on the [DocFetcher forum](http://sourceforge.net/p/docfetcher/discussion/702424/).
 * **OS X**: On OS X, DocFetcher is started via a shell script located inside the DocFetcher [application bundle](https://en.wikipedia.org/wiki/Bundle_(macOS)). If you're using portable DocFetcher, the application bundle is just the "DocFetcher" entry inside the DocFetcher folder that looks like an executable but is actually a folder with the extension ".app". Open a terminal and use the `cd` command to navigate to the folder `Contents/MacOS` inside the application bundle, then launch the DocFetcher script from there. If it doesn't start, an error message might be printed in the terminal. Post this error message on the [DocFetcher forum](http://sourceforge.net/p/docfetcher/discussion/702424/).

+I can't start the PortableApps version of DocFetcher! Help!
+---
+If double-clicking the DocFetcherPortable.exe launcher gives you an error message saying something along the lines of "Error: Could not create the Java Virtual Machine", you need to make sure jPortable is installed in the right location. There's a simple rule: The `Common Files` folder needs to be placed *beside* the `DocFetcherPortable`folder, not inside it or anywhere else. For example, if you installed the PortableApps version of DocFetcher into `X:\`, then the `Common Files` folder should also be in `X:\`, like so:
+
+`X:\DocFetcherPortable`
+`X:\Common Files`
+
 On Windows 2000, DocFetcher crashes when I try to start it, what do I do?
 ---

FAQ modified by Nam-Quang Tran

Nam-Quang Tran — Mon, 15 Jan 2024 15:10:38 -0000

--- v30
+++ v31
@@ -155,9 +155,9 @@
 ---
 In the DocFetcher folder, open the following file with a text editor: `App\AppInfo\Launcher\DocFetcherPortable.ini`

-In that file, there's a line starting with `CommandLineArguments=`. This line contains various launch parameters, including an `-Xmx` parameter. To set the memory limit to 8 GB, for example, you can change the parameter to `-Xmx8g`.
-
-After editing, save and close the file, then restart the application.
+In that file, there's a line starting with `CommandLineArguments=`. This line contains various launch parameters, including an `-Xmx` parameter. To set the memory limit to 8 GB, for example, you can change the parameter to `-Xmx8g`. After editing, save and close the file, then restart the application.
+
+Note that the application won't start if the chosen memory limit exceeds the amount of physical RAM available. Moreover, you need to take into account that obviously the OS and other process also need some of that RAM. So, for example, if the computer has 8 GB of RAM, a reasonable memory limit to try would be 4 GB.

 I installed DocFetcher on Linux from a Snap package. How do I increase the memory limit (a.k.a. heap size)?
 ---