Update of POT and PO files for the manual

1 files changed, 97 insertions, 97 deletions

diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot
index e5288c2dc..66d64f370 100644
--- a/po/pot/preparing.pot
+++ b/po/pot/preparing.pot
@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2006-08-07 22:39+0000\n"
+"POT-Creation-Date: 2006-08-16 18:10+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -1329,325 +1329,325 @@ msgid "This section will walk you through pre-installation hardware setup, if an
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1429
+#: preparing.xml:1434
 #, no-c-format
 msgid "Invoking the BIOS Set-Up Menu"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1431
+#: preparing.xml:1436
 #, no-c-format
 msgid "BIOS provides the basic functions needed to boot your machine to allow your operating system to access your hardware. Your system probably provides a BIOS set-up menu, which is used to configure the BIOS. Before installing, you <emphasis>must</emphasis> ensure that your BIOS is setup correctly; not doing so can lead to intermittent crashes or an inability to install Debian."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1440
+#: preparing.xml:1445
 #, no-c-format
 msgid "The rest of this section is lifted from the <ulink url=\"&url-pc-hw-faq;\"></ulink>, answering the question, <quote>How do I enter the CMOS configuration menu?</quote>. How you access the BIOS (or <quote>CMOS</quote>) configuration menu depends on who wrote your BIOS software:"
 msgstr ""
 
 #. Tag: term
-#: preparing.xml:1454
+#: preparing.xml:1459
 #, no-c-format
 msgid "AMI BIOS"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1455
+#: preparing.xml:1460
 #, no-c-format
 msgid "<keycap>Delete</keycap> key during the POST (power on self test)"
 msgstr ""
 
 #. Tag: term
-#: preparing.xml:1463
+#: preparing.xml:1468
 #, no-c-format
 msgid "Award BIOS"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1464
+#: preparing.xml:1469
 #, no-c-format
 msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo>, or <keycap>Delete</keycap> key during the POST"
 msgstr ""
 
 #. Tag: term
-#: preparing.xml:1473
+#: preparing.xml:1478
 #, no-c-format
 msgid "DTK BIOS"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1474
+#: preparing.xml:1479
 #, no-c-format
 msgid "<keycap>Esc</keycap> key during the POST"
 msgstr ""
 
 #. Tag: term
-#: preparing.xml:1481
+#: preparing.xml:1486
 #, no-c-format
 msgid "IBM PS/2 BIOS"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1482
+#: preparing.xml:1487
 #, no-c-format
 msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> </keycombo> after <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap> </keycombo>"
 msgstr ""
 
 #. Tag: term
-#: preparing.xml:1496
+#: preparing.xml:1501
 #, no-c-format
 msgid "Phoenix BIOS"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1497
+#: preparing.xml:1502
 #, no-c-format
 msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo> or <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> </keycombo> or <keycap>F1</keycap>"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1513
+#: preparing.xml:1518
 #, no-c-format
 msgid "Information on invoking other BIOS routines can be found in <ulink url=\"&url-invoking-bios-info;\"></ulink>."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1518
+#: preparing.xml:1523
 #, no-c-format
 msgid "Some &arch-title; machines don't have a CMOS configuration menu in the BIOS. They require a software CMOS setup program. If you don't have the Installation and/or Diagnostics diskette for your machine, you can try using a shareware/freeware program. Try looking in <ulink url=\"&url-simtel;\"></ulink>."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1529 preparing.xml:1873
+#: preparing.xml:1534 preparing.xml:1878
 #, no-c-format
 msgid "Boot Device Selection"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1531
+#: preparing.xml:1536
 #, no-c-format
 msgid "Many BIOS set-up menus allow you to select the devices that will be used to bootstrap the system. Set this to look for a bootable operating system on <filename>A:</filename> (the first floppy disk), then optionally the first CD-ROM device (possibly appearing as <filename>D:</filename> or <filename>E:</filename>), and then from <filename>C:</filename> (the first hard disk). This setting enables you to boot from either a floppy disk or a CD-ROM, which are the two most common boot devices used to install Debian."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1542
+#: preparing.xml:1547
 #, no-c-format
 msgid "If you have a newer SCSI controller and you have a CD-ROM device attached to it, you are usually able to boot from the CD-ROM. All you have to do is enable booting from a CD-ROM in the SCSI-BIOS of your controller."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1549
+#: preparing.xml:1554
 #, no-c-format
 msgid "Another popular option is to boot from a USB storage device (also called a USB memory stick or USB key). Some BIOSes can boot directly from a USB storage device, but some cannot. You may need to configure your BIOS to boot from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to get it to boot from the USB device."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1557
+#: preparing.xml:1562
 #, no-c-format
 msgid "Here are some details about how to set the boot order. Remember to reset the boot order after Linux is installed, so that you restart your machine from the hard drive."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1566
+#: preparing.xml:1571
 #, no-c-format
 msgid "Changing the Boot Order on IDE Computers"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1569
+#: preparing.xml:1574
 #, no-c-format
 msgid "As your computer starts, press the keys to enter the BIOS utility. Often, it is the <keycap>Delete</keycap> key. However, consult the hardware documentation for the exact keystrokes."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1576
+#: preparing.xml:1581
 #, no-c-format
 msgid "Find the boot sequence in the setup utility. Its location depends on your BIOS, but you are looking for a field that lists drives."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1581
+#: preparing.xml:1586
 #, no-c-format
 msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1586
+#: preparing.xml:1591
 #, no-c-format
 msgid "C is the hard drive, and A is the floppy drive."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1592
+#: preparing.xml:1597
 #, no-c-format
 msgid "Change the boot sequence setting so that the CD-ROM or the floppy is first. Usually, the <keycap>Page Up</keycap> or <keycap>Page Down</keycap> keys cycle through the possible choices."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1600
+#: preparing.xml:1605
 #, no-c-format
 msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1610
+#: preparing.xml:1615
 #, no-c-format
 msgid "Changing the Boot Order on SCSI Computers"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1614
+#: preparing.xml:1619
 #, no-c-format
 msgid "As your computer starts, press the keys to enter the SCSI setup utility."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1619
+#: preparing.xml:1624
 #, no-c-format
 msgid "You can start the SCSI setup utility after the memory check and the message about how to start the BIOS utility displays when you start your computer."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1625
+#: preparing.xml:1630
 #, no-c-format
 msgid "The keystrokes you need depend on the utility. Often, it is <keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. However, consult your hardware documentation for the exact keystrokes."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1633
+#: preparing.xml:1638
 #, no-c-format
 msgid "Find the utility for changing the boot order."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1638
+#: preparing.xml:1643
 #, no-c-format
 msgid "Set the utility so that the SCSI ID of the CD drive is first on the list."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1644
+#: preparing.xml:1649
 #, no-c-format
 msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer. Often, you must press <keycap>F10</keycap>."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1658
+#: preparing.xml:1663
 #, no-c-format
 msgid "Miscellaneous BIOS Settings"
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1660
+#: preparing.xml:1665
 #, no-c-format
 msgid "CD-ROM Settings"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1661
+#: preparing.xml:1666
 #, no-c-format
 msgid "Some BIOS systems (such as Award BIOS) allow you to automatically set the CD speed. You should avoid that, and instead set it to, say, the lowest speed. If you get <userinput>seek failed</userinput> error messages, this may be your problem."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1671
+#: preparing.xml:1676
 #, no-c-format
 msgid "Extended vs. Expanded Memory"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1672
+#: preparing.xml:1677
 #, no-c-format
 msgid "If your system provides both ex<emphasis>ten</emphasis>ded and ex<emphasis>pan</emphasis>ded memory, set it so that there is as much extended and as little expanded memory as possible. Linux requires extended memory and cannot use expanded memory."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1682
+#: preparing.xml:1687
 #, no-c-format
 msgid "Virus Protection"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1683
+#: preparing.xml:1688
 #, no-c-format
 msgid "Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/Linux. These aren't compatible with GNU/Linux; moreover, due to the file system permissions and protected memory of the Linux kernel, viruses are almost unheard of<footnote> <para> After installation you can enable Boot Sector protection if you want. This offers no additional security in Linux but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up. </para> </footnote>."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1704
+#: preparing.xml:1709
 #, no-c-format
 msgid "Shadow RAM"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1705
+#: preparing.xml:1710
 #, no-c-format
 msgid "Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS caching. You may see settings for <quote>Video BIOS Shadow</quote>, <quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. Linux does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with Linux access to hardware devices."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1722
+#: preparing.xml:1727
 #, no-c-format
 msgid "Memory Hole"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1723
+#: preparing.xml:1728
 #, no-c-format
 msgid "If your BIOS offers something like <quote>15&ndash;16 MB Memory Hole</quote>, please disable that. Linux expects to find memory there if you have that much RAM."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1729
+#: preparing.xml:1734
 #, no-c-format
 msgid "We have a report of an Intel Endeavor motherboard on which there is an option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. This had two settings: <quote>Disabled</quote> and <quote>1 Megabyte</quote>. Set it to <quote>1 Megabyte</quote>. When disabled, the installation floppy was not read correctly, and the system eventually crashed. At this writing we don't understand what's going on with this particular device &mdash; it just worked with that setting and not without it."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1745
+#: preparing.xml:1750
 #, no-c-format
 msgid "Advanced Power Management"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1746
+#: preparing.xml:1751
 #, no-c-format
 msgid "If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. Linux can take over control of these modes, and can do a better job of power-management than the BIOS."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1764
+#: preparing.xml:1769
 #, no-c-format
 msgid "Firmware Revisions and Existing OS Setup"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1766
+#: preparing.xml:1771
 #, no-c-format
 msgid "&arch-title; machines are generally self-configuring and do not require firmware configuration. However, you should make sure that you have the appropriate ROM and system patches. On the Macintosh, MacOS version >= 7.1 is recommended because version 7.0.1 contains a bug in the video drivers preventing the boot loader from deactivating the video interrupts, resulting in a boot hang. On the BVM VMEbus systems you should make sure you are using BVMBug revision G or higher boot ROMs. The BVMBug boot ROMs do not come as standard on the BVM systems but are available from BVM on request free of charge."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1789
+#: preparing.xml:1794
 #, no-c-format
 msgid "Invoking OpenFirmware"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1790
+#: preparing.xml:1795
 #, no-c-format
 msgid "There is normally no need to set up the BIOS (called OpenFirmware) on &arch-title; systems. PReP and CHRP are equipped with OpenFirmware, but unfortunately, the means you use to invoke it vary from manufacturer to manufacturer. You'll have to consult the hardware documentation which came with your machine."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1798
+#: preparing.xml:1803
 #, no-c-format
 msgid "On &arch-title; Macintoshes, you invoke OpenFirmware with <keycombo><keycap>Command</keycap> <keycap>option</keycap> <keycap>O</keycap> <keycap>F</keycap></keycombo> while booting. Generally it will check for these keystrokes after the chime, but the exact timing varies from model to model. See <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> for more hints."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1807
+#: preparing.xml:1812
 #, no-c-format
 msgid ""
       "The OpenFirmware prompt looks like this: <informalexample><screen>\n"
@@ -1657,43 +1657,43 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1820
+#: preparing.xml:1825
 #, no-c-format
 msgid "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, is broken. These machines will most likely not be able to boot from the hard drive unless the firmware is patched. A firmware patch is included in the <application>System Disk 2.3.1</application> utility, available from Apple at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin\"></ulink>. After unpacking the utility in MacOS, and launching it, select the <guibutton>Save button</guibutton> to have the firmware patches installed to nvram."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1840
+#: preparing.xml:1845
 #, no-c-format
 msgid "Invoking OpenBoot"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1842
+#: preparing.xml:1847
 #, no-c-format
 msgid "OpenBoot provides the basic functions needed to boot the &arch-title; architecture. This is rather similar in function to the BIOS in the x86 architecture, although much nicer. The Sun boot PROMs have a built-in forth interpreter which lets you do quite a number of things with your machine, such as diagnostics and simple scripts."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1850
+#: preparing.xml:1855
 #, no-c-format
 msgid "To get to the boot prompt you need to hold down the <keycap>Stop</keycap> key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the <keycap>A</keycap> key. The boot PROM will give you a prompt, either <userinput>ok</userinput> or <userinput>&gt;</userinput>. It is preferred to have the <userinput>ok</userinput> prompt. So if you get the old style prompt, hit the <keycap>n</keycap> key to get the new style prompt."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1862
+#: preparing.xml:1867
 #, no-c-format
 msgid "If you are using a serial console, send a break to the machine. With Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type <userinput>%~break</userinput>. Consult the documentation of your terminal emulator if you are using a different program."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1875
+#: preparing.xml:1880
 #, no-c-format
 msgid "You can use OpenBoot to boot from specific devices, and also to change your default boot device. However, you need to know some details about how OpenBoot names devices; it's considerably different from Linux device naming, described in <xref linkend=\"device-names\"/>. Also, the command will vary a bit, depending on what version of OpenBoot you have. More information about OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1885
+#: preparing.xml:1890
 #, no-c-format
 msgid ""
       "Typically, with newer revisions, you can use OpenBoot devices such as <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, <quote>disk</quote>, or <quote>disk2</quote>. These have the obvious meanings; the <quote>net</quote> device is for booting from the network. Additionally, the device name can specify a particular partition of a disk, such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot device names have the form <informalexample> <screen>\n"
@@ -1704,7 +1704,7 @@ msgid ""
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1908
+#: preparing.xml:1913
 #, no-c-format
 msgid ""
       "To boot from a specific device, use the command <userinput>boot <replaceable>device</replaceable></userinput>. You can set this behavior as the default using the <userinput>setenv</userinput> command. However, the name of the variable to set changed between OpenBoot revisions. In OpenBoot 1.x, use the command <userinput>setenv boot-from <replaceable>device</replaceable></userinput>. In later revisions of OpenBoot, use the command <userinput>setenv boot-device <replaceable>device</replaceable></userinput>. Note, this is also configurable using the <command>eeprom</command> command on Solaris, or modifying the appropriate files in <filename>/proc/openprom/options/</filename>, for example under Linux: <informalexample><screen>\n"
@@ -1713,205 +1713,205 @@ msgid ""
 msgstr ""
 
 #. Tag: screen
-#: preparing.xml:1927
+#: preparing.xml:1932
 #, no-c-format
 msgid "eeprom boot-device=disk1:1"
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1937
+#: preparing.xml:1942
 #, no-c-format
 msgid "BIOS Setup"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1938
+#: preparing.xml:1943
 #, no-c-format
 msgid "In order to install &debian; on a &arch-title; or zSeries machine you have first boot a kernel into the system. The boot mechanism of this platform is inherently different to other ones, especially from PC-like systems: there are no floppy devices available at all. You will notice another big difference while you work with this platform: most (if not all) of the time you will work remote, with the help of some client session software like telnet, or a browser. This is due to that special system architecture where the 3215/3270 console is line-based instead of character-based."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1950
+#: preparing.xml:1955
 #, no-c-format
 msgid "Linux on this platform runs either natively on the bare machine, in a so-called LPAR (Logical Partition) or in a virtual machine supplied by the VM system. You can use a boot tape on all of those systems; you may use some other boot media, too, but those may not be generally available. For example, you can use the virtual card reader of a virtual machine, or boot from the HMC (Hardware Management Console) of an LPAR if the HMC and this option is available for you."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1960
+#: preparing.xml:1965
 #, no-c-format
 msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of Debian-specific data is needed and where do you find them. Based on both sources of information you have to prepare your machine and the installation medium and to perform a boot from it. When you see the welcome message in your client session join this document again for the Debian-specific installation steps."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1977
+#: preparing.xml:1982
 #, no-c-format
 msgid "Native and LPAR installations"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1978
+#: preparing.xml:1983
 #, no-c-format
 msgid "Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up an LPAR for Linux."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:1992
+#: preparing.xml:1997
 #, no-c-format
 msgid "Installation as a VM guest"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:1994
+#: preparing.xml:1999
 #, no-c-format
 msgid "Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> Redbook on how to set up a VM guest for running Linux."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2004
+#: preparing.xml:2009
 #, no-c-format
 msgid "You need to copy all the files from the <filename>generic</filename> sub-directory to your CMS disk. Be sure to transfer <filename>kernel.debian</filename> and <filename>initrd.debian</filename> in binary mode with a fixed record length of 80 characters."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:2016
+#: preparing.xml:2021
 #, no-c-format
 msgid "Setting up an installation server"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2018
+#: preparing.xml:2023
 #, no-c-format
 msgid "If you don't have a connection to the Internet (either directly or via a web proxy) you need to create a local installation server that can be accessed from your S/390. This server keeps all the packages you want to install and must make them available using NFS, HTTP or FTP."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2026
+#: preparing.xml:2031
 #, no-c-format
 msgid "The installation server needs to copy the exact directory structure from any &debian; mirror, but only the s390 and architecture-independent files are required. You can also copy the contents of all installation CDs into such a directory tree."
 msgstr ""
 
 #. Tag: emphasis
-#: preparing.xml:2035
+#: preparing.xml:2040
 #, no-c-format
 msgid "FIXME: more information needed &mdash; from a Redbook?"
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:2041
+#: preparing.xml:2046
 #, no-c-format
 msgid "Hardware Issues to Watch Out For"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2042
+#: 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 ""
 
 #. Tag: para
-#: preparing.xml:2052
+#: 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 ""
 
 #. Tag: para
-#: preparing.xml:2062
+#: preparing.xml:2067
 #, no-c-format
 msgid "Atari TT RAM boards are notorious for RAM problems under Linux; if you encounter any strange problems, try running at least the kernel in ST-RAM. Amiga users may need to exclude RAM using a booter memfile. <phrase condition=\"FIXME\"><emphasis> FIXME: more description of this needed. </emphasis></phrase>"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2074
+#: preparing.xml:2079
 #, no-c-format
 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 they tell you about the bad RAM. Still, it's better to be told you have bad memory than to have it silently insert errors in your data. Thus, the best systems have motherboards that support parity and true-parity memory modules; see <xref linkend=\"Parity-RAM\"/>."
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2085
+#: preparing.xml:2090
 #, 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 ""
 
 #. Tag: title
-#: preparing.xml:2093
+#: preparing.xml:2098
 #, no-c-format
 msgid "The Turbo Switch"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2094
+#: preparing.xml:2099
 #, 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 ""
 
 #. Tag: title
-#: preparing.xml:2107
+#: preparing.xml:2112
 #, no-c-format
 msgid "Cyrix CPUs and Floppy Disk Errors"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2108
+#: preparing.xml:2113
 #, 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 ""
 
 #. Tag: para
-#: preparing.xml:2116
+#: preparing.xml:2121
 #, 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 ""
 
 #. Tag: title
-#: preparing.xml:2126
+#: preparing.xml:2131
 #, no-c-format
 msgid "Peripheral Hardware Settings"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2127
+#: preparing.xml:2132
 #, 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:2134
+#: preparing.xml:2139
 #, 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 ""
 
 #. Tag: title
-#: preparing.xml:2145
+#: preparing.xml:2150
 #, no-c-format
 msgid "USB BIOS support and keyboards"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2146
+#: preparing.xml:2151
 #, no-c-format
 msgid "If you have no AT-style keyboard and only a USB model, you may need to enable legacy AT keyboard emulation in your BIOS setup. Only do this if the installation system fails to use your keyboard in USB mode. Conversely, for some systems (especially laptops) you may need to disable legacy USB support if your keyboard does not respond. Consult your main board manual and look in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB keyboard support</quote> options."
 msgstr ""
 
 #. Tag: title
-#: preparing.xml:2159
+#: preparing.xml:2164
 #, no-c-format
 msgid "More than 64 MB RAM"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2160
+#: preparing.xml:2165
 #, 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 ""
 
 #. Tag: title
-#: preparing.xml:2169
+#: preparing.xml:2174
 #, no-c-format
 msgid "Display visibility on OldWorld Powermacs"
 msgstr ""
 
 #. Tag: para
-#: preparing.xml:2170
+#: preparing.xml:2175
 #, no-c-format
 msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver but possibly others as well, may not produce a colormap with reliably results in visible output under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>."
 msgstr ""