Home | Arachnophilia | Documentation |     Share This Page
Common Problems with Arachnophilia
Arachnophilia is © Copyright 2015, P. Lutus.

Arachnophilia is CareWare

Starting Arachnophilia | Browser Launching | Search & Replace | Memory Issues | FTP Service | Windows Suggestions

Now that the new Java version of Arachnophilia has been available for a while, I have seen certain problems reported again and again. Here is a list of the most common ones.
Starting Arachnophilia
  • First time
    If you have downloaded and installed the correct Java runtime engine from http://java.com , and you can't seem to run Arachnophilia, open a command window (Linux: shell console), move to the place where the file "Arachnophilia.jar" is located, and type:

    java -jar Arachnophilia.jar

    This launch method has the advantage that you can read any errors that may appear during launch.

    This launch command is what is invoked by the default Windows program icon, and it is the appropriate way to launch Arachnophilia on other platforms. Linux users can create a batch file containing this command, or use one of the various desktop-environment launching methods.
  • Subsequently
    If, after successfully running Arachnophilia, you find that you cannot run it any more, you have the option of editing the configuration files located in the directory (user home directory)/.Arachnophilia, or, the simplest approach, just delete that directory. If you delete the directory and run Arachnophilia, the program will re-install itself with a fresh set of configuration files.
  • Running from shell scripts / batch files
    It turns out that, unlike more sophisticated operating systems, it is nearly impossible to directly associate a Java program with a file type in Windows. To get around this, you can create a Windows batch file like the following:

    @echo off
    java -jar "c:\Program Files\Arachnophilia\Arachnophilia.jar" "%1"

    Remember to change the path to the executable JAR if your path differs from that shown above.

    This obviously launches a command window that won't close, but that is what it's like using Windows (pay more, get less), and there are no remedies for this bug that can be explained in less than the length of an overly wordy spy novel.

    Once you have created a batch file like the above, you can name it "Arachnophilia.bat" and place it in your Windows directory (so it can be found in a path search). Then you can use the Windows File Explorer's file association dialog to create an association between one or more file types and the Arachnophilia batch file.

    On more sophisticated operating systems such as Linux, you can either create the required association directly within X windows, or use a shell script similar to that used in Windows:

    java -jar (path to Arachnophilia JAR file)/Arachnophilia.jar "$@"

    Name this shell script "Arachnophilia", make it executable, and place it in the /usr/local/bin directory. This simply creates an easy wasy to launch Arachnophilia or create file associations, without the drawback of the Windows approach.

    If you use Linux and X windows, you can also create a plain-text desktop shortcut like this:

    [Desktop Entry]
    Exec=java -jar (path to Arachnophilia JAR file)/Arachnophilia.jar

    Name this file "Arachnophilia", place it in your desktop directory (in Linux, normally located at /home/(user name)/Desktop), and you have an easy way to launch Arachnophilia.
  • Error log file
    Most kinds of program errors are trapped and logged in the file (user home directory)/.Arachnophilia/Aracherrorlog.txt. If you have difficulty launching Arachnophilia, reading this log file should be the first step. If you decide to report an Arachnophilia bug, be sure to include the contents of this log file.
Browser Launching
The main help pages cover browser location and installation, this section covers a few problems that may come up on some systems, or with some browsers.
  • Launch Argument

    The default launch argument is "file:$1". During the launch procedure, the token "$1" is replaced with a temporary file name that contains the Web page to be viewed. Some browsers may not accept this specific launch string. In that event, you can change the launch string and your changes will be remembered.

    It is important to realize that the same browser can be launched using different launch properties. Simply create a new browser profile, type in the same program path, and change the options.

  • Jump to Doc Position
    This feature tries to synchronize the browser preview with the editing position in long documents. But it has one flaw — the document marker might end up in the middle of a script segment and cause runtime errors in that script, for a page with <script></script> blocks. In such a case, simply disable the "Jump to doc position" feature.
  • Toolbar buttons for different browsers
    You may want to create a toolbar button for each browser, to save time previewing and comparing browser behaviors. This is easy — the macro "[LaunchBrowser]" accepts an optional argument. To launch a browser you have named "MyFavorite" in the browser configuration dialog, use this macro argument:


Search & Replace
  • Search do's and dont's

    The search & replace panel contains a very easy way to search for things, but it should not be used for every kind of search. If you want to search for a very long string, or provide a very long replacement string, use macros instread of typing them directly into the search & replace panel.

    To make this easier, the search & replace panel text entry windows can be right-clicked and a list of user macros is displayed. So type your long entry into a macro, then enter the macro name into search & replace.

    Also, macros can be written for specific searches, this formalizes the search process and makes it easy to collect your favorite searches as a set of toolbar buttons.
  • Recovery

    Some people have tried pasting the entire text of "War & Peace" into the search text window. This will have a very bad effect, distorting Arachnophilia's display entirely. One solution is to press the "clear" button in the extended search & replace panel. But in truly pathological cases, to recover the display, simply delete the (user home directory)/.Arachnophilia directory, and let Arachnophilia reinstall itself.
Memory Issues

Arachnophilia runs under the Java virtual machine, which normally allocates enough memory for itself and for most Web development applications like Arachnophilia. But in some environments (that I won't identify but whose name starts with "Windows") the Java virtual machine defaults to a small memory allocation, which prevents some Arachnophilia users from loading and editing either a very large page, or a large set of pages simultaneously. Here is the solution to this problem:

  • Under most operating systems other than Windows, memory problems rarely come up because the Java virtual machine allocates plenty of memory for itself. But, since I don't test on every operating system, this issue might come up. In case of memory problems, find the shell script that launches Arachnophilia, and edit it as follows:
    • Find the line that contains something like: "java -jar Arachnophilia.jar".
    • Edit it so it looks like this: "java -Xmx1000m -jar Arachnophilia.jar".
    • Save the result and any memory problems should be history.
  • For Windows XP, follow this procedure:
    • Open a file browser.
    • Select "Tools ... Folder Options ... File types"
    • To save time, when confronted by the list of file types, type "j" at the keyboard. In most cases this will jump to "JAR", the file type of interest. If not, scroll down to get to the entry for "JAR".
    • Click "Advanced", then "Edit".
    • After the string "javaw.exe" and before the string "-jar", put this: "-Xmx1000m".
    • The section of interest should now look like this: "(path)/javaw.exe -Xmx1000m -jar (path to arachnophilia)".
    • Click "OK, "OK" and "Close".
  • For other Windows versions ... well, I don't know, because I don't run Windows. One can only hope that the above method will work for other versions, but in any case, the key is to instruct the Java virtual machine to allocate itself more memory as shown above.
FTP Service
There is a subtle aspect of the FTP service that has caused some problems. The user-provided remote path should be "anchored," that is, it should be a full path beginning either with "/" or "~", depending on the requirements of your service.

For example, if you know that the path to your Web pages is understood by your service's FTP service as "wwwdocs", be sure to enter this as:




but not as:


If the latter example is entered, it creates a very annoying result — a series of directories is created in the wrong place, because the FTP protocol interprets each new change-directory command as an addition to the last, rather than a lateral movement as intended. To summarize, this produces any number of useless directories in the wrong place.

If you didn't find what you were looking for here, try the Arachnophilia FAQ
Windows Suggestions
My favorite Windows suggestion is that everyone dump Windows in favor of Linux, but since that's a bit unrealistic, I have these Windows-specific hints:
  • The Arachnophilia desktop shortcut will accept a drag & drop of one or more filenames and will launch Arachnophilia with those files opened. Simply drag the selected file names from Windows File Explorer onto the Arachnophilia desktop shortcut.
  • Arachnophilia is listed in the "Send To" context menu, which allows files to be opened within Arachnophilia by right-clicking the file name(s) and specifying "Send To".
  • Windows users who have memory and resource issues should read the suggestions on this page under "Memory Issues".
  • Oh, one more thing. Did I remember to mention that everyone should dump Windows in favor of Linux?

Home | Arachnophilia | Documentation |     Share This Page