Sending Bug Reports

If you encounter a problem with the program that may be a result of a programming error, you can report it to the following e-mail address:

While all bug reports are welcome, they need to contain relevant information if they are to be of any use, especially all necessary details on how to repeat the problem. "It doesn't work" type of reports are of no help. The goal of your bug report is not to describe the error message dialog, for example, but rather the events leading to it. Almost always the first, the most important and necessary step to identifying a problem is to find a way how can it be repeated - once this is established, fixing it is usually done in a matter of minutes.

Note that this is not a support address, and is not replied to. If you require support, use the email address for the purpose and properly identify yourself as a registered user.

Please note!
Before sending a bug report, always make sure that you are using the latest release, or at least check the development history if the issue was already addressed in one of the subsequent releases.
For other available contact addresses, please click here.

When to send a bug report

The purpose of bug reports is to let the developer know about a possible problem in the program for later investigation. Some 95% of reported issues are not bugs, they result from users not knowning how to do things, inapropriate system configuration, poor system maintenance, etc. You should be able to understand and identify the problem if sending a bug report.

Details to include in bug report

Always include in the message your system configuration, such as operating system used, and exact version of WhereIsIt (you can find it in the Help/About dialog, or -better- by right-clicking the WhereIsIt.exe file in Explorer and checking the Version tab in its Properties dialog). Also include any other system configuration details that may be related to your problem - for example, if it is a printing problem, include the type of your printer, connection details (local/network) etc. If the problem results in any kind of error message, write it down exactly and include with your report, or include a snapshot of the error dialog ONLY. Try to specify whether the same problem occurs always or just sometimes, and under what conditions. Note that many problems will likely be data-related, meaning that your catalog file and the contents in it may play an important part.

What not to include in a bug report

Do not attach big screenshot images unless they are truly relevant to the problem and contribute a great deal to the presentation and of the issue in question. If sending a screenshot, do not send uncompressed BMP files, choose a compressable format such as GIF or JPEG. Do not send attached catalog files larger than 100 KB - if a data sample is necessary to repeat and investigate the problem, you will be contacted back.

Please do NOT send e-mails with long attachments unless specifically asked to do so. All e-mails with large, unasked for attachments are deleted automatically at the moment they reach the server. Attaching 1 MB file to your e-mail is a guarantee your message will not reach anybody.

Guidelines to follow when submitting a bug report

For your reference, you can follow these guidelines to help you send a useful report:

Version of WhereIsIt used
(right-click the WhereIsIt.exe file in Explorer and check the Version tab)

Your operating system type and version

Quick summary of your hardware
(CPU type, speed, memory installed, video device type, video driver version, other details that may be relevant to the problem)

How does the problem exhibit
(error message reported, if there is one, or a descriptions of what has happened)

What were the actions preceding the problem, when did the problem occur

How can the problem be repeated in your case
(try to be as detailed as possible here, step-by-step instructions are among the best)

Any of your own observations related to the problem
(anything else you may have noticed, such as details that a problem may only appear after doing something else first. Figuring out an error is often like being a detective; every useful hint can help fill in the puzzle, or at least direct the investigation into the right track)