diff options
Diffstat (limited to 'po/zh_TW/preparing.po')
| -rw-r--r-- | po/zh_TW/preparing.po | 278 |
1 files changed, 120 insertions, 158 deletions
diff --git a/po/zh_TW/preparing.po b/po/zh_TW/preparing.po index 6f76963dd..c3417f61b 100644 --- a/po/zh_TW/preparing.po +++ b/po/zh_TW/preparing.po @@ -3,7 +3,7 @@ msgid "" msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-29 19:35+0000\n" +"POT-Creation-Date: 2006-12-31 03:15+0000\n" "PO-Revision-Date: 2005-07-18 13:49+0800\n" "Last-Translator: Jhang, Jia-Wei<dreamcryer@gmail.com>\n" "Language-Team: debian-chinese-big5 <debian-chinese-big5@lists.debian.org>\n" @@ -3029,48 +3029,13 @@ msgid "FIXME: more information needed — from a Redbook?" msgstr "FIXME: more information needed — from a Redbook?" #. Tag: title -#: preparing.xml:2046 +#: preparing.xml:2047 #, no-c-format msgid "Hardware Issues to Watch Out For" msgstr "需要留意的硬體問題" #. Tag: para -#: preparing.xml:2047 -#, no-c-format -msgid "" -"Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It " -"sometimes works, but is sensitive to temperature and other factors and can " -"actually damage your system. One of the authors of this document over-" -"clocked his own system for a year, and then the system started aborting the " -"<command>gcc</command> program with an unexpected signal while it was " -"compiling the operating system kernel. Turning the CPU speed back down to " -"its rated value solved the problem." -msgstr "" -"有很多人嘗試過把他們的 90 MHz 的處理器超頻到 100 MHz 使用，以及其他諸如此類的" -"做法。這有時可行，但是這賴於外界的溫度和其他因素，而且超頻可能會損毀您的系" -"統。這份文件的作者之一曾把他的系統超頻使用了有一年，從那以後他在編譯操作業系" -"統核心時，<command>gcc</command> 總是會被意外的訊號中止。後來，把處理器的頻率" -"調回標準速度後，問題迎刃而解。" - -#. Tag: para -#: preparing.xml:2057 -#, no-c-format -msgid "" -"The <command>gcc</command> compiler is often the first thing to die from bad " -"memory modules (or other hardware problems that change data unpredictably) " -"because it builds huge data structures that it traverses repeatedly. An " -"error in these data structures will cause it to execute an illegal " -"instruction or access a non-existent address. The symptom of this will be " -"<command>gcc</command> dying from an unexpected signal." -msgstr "" -"如果記憶體模組有故障的話 (或者出現其他會使資料發生異變的硬體故障)，" -"<command>gcc</command> 編譯器經常是第一個停止工作的程式。因為它會生成龐大的資" -"料結構，並在記憶體中頻繁移動。一旦這些資料結構中有錯，就會導致程式執行非法指" -"令或者存取不存在的位址空間。症狀就是 <command>gcc</command> 被一個意外的訊號" -"中止執行。" - -#. Tag: para -#: preparing.xml:2067 +#: preparing.xml:2049 #, no-c-format msgid "" "Atari TT RAM boards are notorious for RAM problems under Linux; if you " @@ -3084,114 +3049,14 @@ msgstr "" "menfile 來排除部分記憶體。 <phrase condition=\"FIXME\"><emphasis> FIXME: " "more description of this needed. </emphasis></phrase>" -#. Tag: para -#: preparing.xml:2079 -#, no-c-format -msgid "" -"If you do have true-parity RAM and your motherboard can handle it, be sure " -"to enable any BIOS settings that cause the motherboard to interrupt on " -"memory parity errors." -msgstr "" -"如果您配備有真奇偶檢驗的記憶體，而且您的主機板也支援這種記憶體，那麼請一定要" -"在 BIOS 的設定裡開啟相應的選項，好讓主機板在發現奇偶檢驗錯時送出中斷呼叫。" - -#. Tag: title -#: preparing.xml:2087 -#, no-c-format -msgid "The Turbo Switch" -msgstr "加速 (Turbo) 開關" - -#. Tag: para -#: preparing.xml:2088 -#, no-c-format -msgid "" -"Many systems have a <emphasis>turbo</emphasis> switch that controls the " -"speed of the CPU. Select the high-speed setting. If your BIOS allows you to " -"disable software control of the turbo switch (or software control of CPU " -"speed), do so and lock the system in high-speed mode. We have one report " -"that on a particular system, while Linux is auto-probing (looking for " -"hardware devices) it can accidentally touch the software control for the " -"turbo switch." -msgstr "" -"有許多系統配有一個 <emphasis>turbo</emphasis> 開關，透過這個開關可以控制處理" -"器的運行速度。請把它調節到``高速''。如果您的 BIOS 能讓您停用讓軟體控制加速開" -"關的功能(或者對軟體對處理器速度的控制)，那麼就請停用它，這會將系統鎖定為高速" -"運行模式。我們曾受到過報告稱，在某特別的系統上， Linux 在自動檢測 (搜尋硬體設" -"備)時，會無意觸動加速開關的軟體控制。" - -#. Tag: title -#: preparing.xml:2101 -#, no-c-format -msgid "Cyrix CPUs and Floppy Disk Errors" -msgstr "Cyrix 處理器和軟碟錯誤" - -#. Tag: para -#: preparing.xml:2102 -#, no-c-format -msgid "" -"Many users of Cyrix CPUs have had to disable the cache in their systems " -"during installation, because the floppy disk has errors if they do not. If " -"you have to do this, be sure to re-enable your cache when you are finished " -"with installation, as the system runs <emphasis>much</emphasis> slower with " -"the cache disabled." -msgstr "" -"許多 Cyrix 處理器的使用者在安裝時，必須停用系統的高速快取 (cache)。如果不如" -"此，就會發生軟碟錯誤。如果您停用了高速快取，請在安裝完成後重新開啟它。因為如" -"果您繼續停用，系統會變慢<emphasis>很多</emphasis>。" - -#. Tag: para -#: preparing.xml:2110 -#, no-c-format -msgid "" -"We don't think this is necessarily the fault of the Cyrix CPU. It may be " -"something that Linux can work around. We'll continue to look into the " -"problem. For the technically curious, we suspect a problem with the cache " -"being invalid after a switch from 16-bit to 32-bit code." -msgstr "" -"我們並不認為這一定是 Cyrix 處理器的過錯。Linux 或許能想辦法避免它。我們將繼" -"續 關注這個問題。基於技術上的好奇，我們猜測這可能是系統從 16 位元切換到 32 位" -"元模式時，導致高速快取失效造成的。" - -#. Tag: title -#: preparing.xml:2120 -#, no-c-format -msgid "Peripheral Hardware Settings" -msgstr "周邊硬體的設置" - -#. Tag: para -#: preparing.xml:2121 -#, no-c-format -msgid "" -"You may have to change some settings or jumpers on your computer's " -"peripheral cards. Some cards have setup menus, while others rely on jumpers. " -"This document cannot hope to provide complete information on every hardware " -"device; what it hopes to provide is useful tips." -msgstr "" -"您也許必須得修改您周邊設備卡上的一些設定或跳線。有的卡有設定選單，而另一些則" -"使用跳線。本文件無意為您提供所有硬體設備的全面資料，只不過希望能提供一些有用" -"的提示。" - -#. Tag: para -#: preparing.xml:2128 -#, no-c-format -msgid "" -"If any cards provide <quote>mapped memory</quote>, the memory should be " -"mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 " -"megabyte) or at an address at least 1 megabyte greater than the total amount " -"of RAM in your system." -msgstr "" -"如果有周邊卡提供了<quote>記憶體映射</quote> (mapped memory)，那麼這塊記憶體應" -"該被映射到介於 0xA0000 和 0xFFFFF (從 640K 到正好 1M) 的某個地方，也可以映射" -"到您系統中總記憶體 1 MB 以後的位址。" - #. Tag: title -#: preparing.xml:2139 +#: preparing.xml:2064 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "USB BIOS 支援與鍵盤" #. Tag: para -#: preparing.xml:2140 +#: preparing.xml:2065 #, no-c-format msgid "" "If you have no AT-style keyboard and only a USB model, you may need to " @@ -3209,29 +3074,13 @@ msgstr "" "<quote>USB keyboard support</quote> 選項。" #. Tag: title -#: preparing.xml:2153 -#, no-c-format -msgid "More than 64 MB RAM" -msgstr "大於 64 MB 的記憶體" - -#. Tag: para -#: preparing.xml:2154 -#, no-c-format -msgid "" -"The Linux Kernel cannot always detect what amount of RAM you have. If this " -"is the case please look at <xref linkend=\"boot-parms\"/>." -msgstr "" -"Linux 核心有時不能檢測出您系統中的記憶體大小。如果您遇到這種情況，請參閱 " -"<xref linkend=\"boot-parms\"/>。" - -#. Tag: title -#: preparing.xml:2163 +#: preparing.xml:2079 #, no-c-format msgid "Display-visibility on OldWorld Powermacs" msgstr "" #. Tag: para -#: preparing.xml:2164 +#: preparing.xml:2081 #, no-c-format msgid "" "Some OldWorld Powermacs, most notably those with the <quote>control</quote> " @@ -3245,6 +3094,119 @@ msgid "" msgstr "" #~ msgid "" +#~ "Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It " +#~ "sometimes works, but is sensitive to temperature and other factors and " +#~ "can actually damage your system. One of the authors of this document over-" +#~ "clocked his own system for a year, and then the system started aborting " +#~ "the <command>gcc</command> program with an unexpected signal while it was " +#~ "compiling the operating system kernel. Turning the CPU speed back down to " +#~ "its rated value solved the problem." +#~ msgstr "" +#~ "有很多人嘗試過把他們的 90 MHz 的處理器超頻到 100 MHz 使用，以及其他諸如此" +#~ "類的做法。這有時可行，但是這賴於外界的溫度和其他因素，而且超頻可能會損毀您" +#~ "的系統。這份文件的作者之一曾把他的系統超頻使用了有一年，從那以後他在編譯操" +#~ "作業系統核心時，<command>gcc</command> 總是會被意外的訊號中止。後來，把處" +#~ "理器的頻率調回標準速度後，問題迎刃而解。" + +#~ msgid "" +#~ "The <command>gcc</command> compiler is often the first thing to die from " +#~ "bad memory modules (or other hardware problems that change data " +#~ "unpredictably) because it builds huge data structures that it traverses " +#~ "repeatedly. An error in these data structures will cause it to execute an " +#~ "illegal instruction or access a non-existent address. The symptom of this " +#~ "will be <command>gcc</command> dying from an unexpected signal." +#~ msgstr "" +#~ "如果記憶體模組有故障的話 (或者出現其他會使資料發生異變的硬體故障)，" +#~ "<command>gcc</command> 編譯器經常是第一個停止工作的程式。因為它會生成龐大" +#~ "的資料結構，並在記憶體中頻繁移動。一旦這些資料結構中有錯，就會導致程式執行" +#~ "非法指令或者存取不存在的位址空間。症狀就是 <command>gcc</command> 被一個意" +#~ "外的訊號中止執行。" + +#~ msgid "" +#~ "If you do have true-parity RAM and your motherboard can handle it, be " +#~ "sure to enable any BIOS settings that cause the motherboard to interrupt " +#~ "on memory parity errors." +#~ msgstr "" +#~ "如果您配備有真奇偶檢驗的記憶體，而且您的主機板也支援這種記憶體，那麼請一定" +#~ "要在 BIOS 的設定裡開啟相應的選項，好讓主機板在發現奇偶檢驗錯時送出中斷呼" +#~ "叫。" + +#~ msgid "The Turbo Switch" +#~ msgstr "加速 (Turbo) 開關" + +#~ msgid "" +#~ "Many systems have a <emphasis>turbo</emphasis> switch that controls the " +#~ "speed of the CPU. Select the high-speed setting. If your BIOS allows you " +#~ "to disable software control of the turbo switch (or software control of " +#~ "CPU speed), do so and lock the system in high-speed mode. We have one " +#~ "report that on a particular system, while Linux is auto-probing (looking " +#~ "for hardware devices) it can accidentally touch the software control for " +#~ "the turbo switch." +#~ msgstr "" +#~ "有許多系統配有一個 <emphasis>turbo</emphasis> 開關，透過這個開關可以控制處" +#~ "理器的運行速度。請把它調節到``高速''。如果您的 BIOS 能讓您停用讓軟體控制加" +#~ "速開關的功能(或者對軟體對處理器速度的控制)，那麼就請停用它，這會將系統鎖定" +#~ "為高速運行模式。我們曾受到過報告稱，在某特別的系統上， Linux 在自動檢測 " +#~ "(搜尋硬體設備)時，會無意觸動加速開關的軟體控制。" + +#~ msgid "Cyrix CPUs and Floppy Disk Errors" +#~ msgstr "Cyrix 處理器和軟碟錯誤" + +#~ msgid "" +#~ "Many users of Cyrix CPUs have had to disable the cache in their systems " +#~ "during installation, because the floppy disk has errors if they do not. " +#~ "If you have to do this, be sure to re-enable your cache when you are " +#~ "finished with installation, as the system runs <emphasis>much</emphasis> " +#~ "slower with the cache disabled." +#~ msgstr "" +#~ "許多 Cyrix 處理器的使用者在安裝時，必須停用系統的高速快取 (cache)。如果不" +#~ "如此，就會發生軟碟錯誤。如果您停用了高速快取，請在安裝完成後重新開啟它。因" +#~ "為如果您繼續停用，系統會變慢<emphasis>很多</emphasis>。" + +#~ msgid "" +#~ "We don't think this is necessarily the fault of the Cyrix CPU. It may be " +#~ "something that Linux can work around. We'll continue to look into the " +#~ "problem. For the technically curious, we suspect a problem with the cache " +#~ "being invalid after a switch from 16-bit to 32-bit code." +#~ msgstr "" +#~ "我們並不認為這一定是 Cyrix 處理器的過錯。Linux 或許能想辦法避免它。我們將" +#~ "繼續 關注這個問題。基於技術上的好奇，我們猜測這可能是系統從 16 位元切換到 " +#~ "32 位元模式時，導致高速快取失效造成的。" + +#~ msgid "Peripheral Hardware Settings" +#~ msgstr "周邊硬體的設置" + +#~ msgid "" +#~ "You may have to change some settings or jumpers on your computer's " +#~ "peripheral cards. Some cards have setup menus, while others rely on " +#~ "jumpers. This document cannot hope to provide complete information on " +#~ "every hardware device; what it hopes to provide is useful tips." +#~ msgstr "" +#~ "您也許必須得修改您周邊設備卡上的一些設定或跳線。有的卡有設定選單，而另一些" +#~ "則使用跳線。本文件無意為您提供所有硬體設備的全面資料，只不過希望能提供一些" +#~ "有用的提示。" + +#~ msgid "" +#~ "If any cards provide <quote>mapped memory</quote>, the memory should be " +#~ "mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 " +#~ "megabyte) or at an address at least 1 megabyte greater than the total " +#~ "amount of RAM in your system." +#~ msgstr "" +#~ "如果有周邊卡提供了<quote>記憶體映射</quote> (mapped memory)，那麼這塊記憶" +#~ "體應該被映射到介於 0xA0000 和 0xFFFFF (從 640K 到正好 1M) 的某個地方，也可" +#~ "以映射到您系統中總記憶體 1 MB 以後的位址。" + +#~ msgid "More than 64 MB RAM" +#~ msgstr "大於 64 MB 的記憶體" + +#~ msgid "" +#~ "The Linux Kernel cannot always detect what amount of RAM you have. If " +#~ "this is the case please look at <xref linkend=\"boot-parms\"/>." +#~ msgstr "" +#~ "Linux 核心有時不能檢測出您系統中的記憶體大小。如果您遇到這種情況，請參閱 " +#~ "<xref linkend=\"boot-parms\"/>。" + +#~ msgid "" #~ "The very best motherboards support parity RAM and will actually tell you " #~ "if your system has a single-bit error in RAM. Unfortunately, they don't " #~ "have a way to fix the error, thus they generally crash immediately after " |