> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/readme/qi-ta-zuo-ye-xi-tong.md).

# 其他作業系統

{% hint style="info" %}
**重要**：本指南的重點為在 Windows 10 和 11 中使用 Parallels Desktop。
{% endhint %}

除了 Windows 之外，您也可以在 Mac 上執行[多個其他類型的作業系統](/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/jin-jie-zhu-ti/shi-yong-xu-ni-ji-qi/zhi-yuan-de-ke-hu-zuo-ye-xi-tong.md)，例如數種 Linux 和 Unix、macOS Server 等。

{% hint style="info" %}
**附註**：在 App Store 版本的 Parallels Desktop 上建立及執行 macOS 虛擬機器，需更新至 1.26.1 或更新版本。如需 Standard Edition 和 App Store Edition 差異的詳細資訊，請前往此[連結](https://kb.parallels.com/123796)。
{% endhint %}

### **找到有關執行其他作業系統的資訊**

您可以檢查列於「[**更多資源**](/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/geng-duo-zi-yuan.md)」的資源，找出在 Mac 上使用 Parallels Desktop 執行其他作業系統的更多資訊和詳細資料。

此外，雖然未明確指出，但是該指南中的許多說明還適用於除了 Windows 以外的其他作業系統。一些與其他作業系統相關的重要指示列舉於＜[**進階主題**](/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/jin-jie-zhu-ti.md)＞一節。


---

# 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.parallels.com/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/readme/qi-ta-zuo-ye-xi-tong.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.