> 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/v20-zh-tw/parallels-desktop-for-mac-20-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/zai-wai-bu-xian-shi-qi-huo-tou-ying-ji-shang-yan-shi-wen-gao.md).

# 在外部顯示器或投影機上演示文稿

您可輕鬆地連接 Mac 到外接顯示器或投影機並顯示 Windows 應用程式的演示文稿，幾乎不需要配置。

要實現此目的：

1. [啟動 Windows](/landing/pdfm-ug/v20-zh-tw/parallels-desktop-for-mac-20-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/kai-shi-shi-yong/qi-dong-windows.md) (如果尚未在執行中)。
2. 如同往常般，將 Mac 連接至外部監視器或投影機。會出現訊息，詢問您是否要顯示簡報。<br>

   <figure><img src="https://content.gitbook.com/content/NPLQPyrTCZG7rj2GnqwJ/blobs/EYo44lya1vyataVr6ols/image.png" alt="" width="300"><figcaption></figcaption></figure>
3. 如果您想要在外接顯示器或投影機上顯示您電腦上文稿的內容，可選取「**鏡像顯示**」。<br>

   如果您不選取「**鏡像顯示**」，某些應用程式，如 Microsoft Powerpoint，可能只會在外接顯示器或投影機上顯示文稿而在您的電腦上顯示簡報者檢視。
4. 按一下「**是**」。Windows 切換到演示模式，會在您的電腦顯示器與外接顯示器或投影機上以全螢幕顯示。之後，您可以開始顯示您的文稿。

{% hint style="info" %}
**注意：**&#x8981;瞭解如何選定顯示文稿的顯示器，可參閱您正用於演示文稿的應用程式的幫助。
{% endhint %}

{% hint style="warning" %}
**重要！**&#x7576;您正在演示模式中執行時，在 Windows 中變更顯示器設定可能會引起演示出現異常。
{% endhint %}


---

# 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/v20-zh-tw/parallels-desktop-for-mac-20-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/zai-wai-bu-xian-shi-qi-huo-tou-ying-ji-shang-yan-shi-wen-gao.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.