> For the complete documentation index, see [llms.txt](https://support.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.tiger.com/english/how-to-start/register-and-setup.md). # Recommended system requirements ### System requirements For the Tiger.com terminal to operate at its best, your computer needs to meet the following requirements: * Processor: Intel Core i5-7500 / Intel Core i3-8100 / AMD Ryzen 5 2400 processor or more recent * RAM: at least 16 GB * Hard drive: at least 80 GB * Network card: Integrated Internal Card 10/100 * Operating system: Windows 10 (64-bit) or higher ### Connection requirements * Internet connection with a speed of at least 30 Mbps * Using monitors with Full HD resolution (1920×1080 pixels) or higher is recommended Installation may be required for successful installation [.NET Framework 4.7.2](https://support.microsoft.com/en-us/topic/microsoft-net-framework-4-7-2-offline-installer-for-windows-05a72734-2127-a15d-50cf-daf56d5faec2) or [.NET Framework 4.8](https://go.microsoft.com/fwlink/?linkid=2088631). {% content-ref url="/pages/AZxLjtdVH5VSRZmZNTNs" %} [How do I optimize the terminal to improve performance?](/english/frequently-asked-questions/how-do-i-optimize-the-terminal-to-improve-performance.md) {% endcontent-ref %} --- # 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://support.tiger.com/english/how-to-start/register-and-setup.md?ask=&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.