> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/pdf-converter-for-notes/how-to/how-to-find-your-notes-installation-and-notes-data-directories.md).

# How to find your Notes Installation and Notes Data directories

## Locating the Notes Installation Directory

1\. In order to find your **Notes installation directory**, right-click on the shortcut you use to open Lotus Notes and click **Properties**.

![](https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlEi5u5vkdIRtfAV7CA%2F-MlEigAhj6ydIlgr4wmQ%2Fimage.png?alt=media\&token=92c239c8-f650-4c02-af36-9dbb1ffd6a20)

2\. The location of your **Notes installation directory** will now be shown in the Properties window. 

In the below example, the path to the Notes installation directory is \
`C:\Program Files (x86)\IBM\Lotus\Notes`

Some other typical install locations are\
`C:\Lotus\Notes\Data` or `C:\Program Files\IBM\Lotus\Notes\Data`.

![](https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MlCAurE6RSGoCmtmAET%2F-MlEi5u5vkdIRtfAV7CA%2F-MlEinA1knhxPVGnvbe2%2Fimage.png?alt=media\&token=7b18dc94-f8e2-4aee-bca6-cf1604e30f89)

## Locating the Notes Data Directory

The **Data directory** (where the PDF Converter database is typically copied) is located within the **Notes installation directory**. 

In the previous example, the **Data directory** is located in \
`C:\Program Files (x86)\IBM\Lotus\Notes\Data`

If you're using an ICAA or HCAA client, then the installation folders are usually located in: \
`C:/Program%20Files%20(x86)/IBM/ICAA` 

or \
`C:/Program%20Files%20(x86)/HCL/HCAA`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.swingsoftware.com/pdf-converter-for-notes/how-to/how-to-find-your-notes-installation-and-notes-data-directories.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.