From 7b45786a24ade38b26b02b5c0ce612a890d10b50 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Mon, 25 Dec 2006 20:08:46 +0000 Subject: -Fix broken closing tag - Remove references to deleted sections --- en/boot-installer/trouble.xml | 2 +- en/preparing/pre-install-bios-setup.xml | 11 ----------- en/using-d-i/modules/x86/lilo-installer.xml | 3 +-- 3 files changed, 2 insertions(+), 14 deletions(-) (limited to 'en') diff --git a/en/boot-installer/trouble.xml b/en/boot-installer/trouble.xml index d9abbe447..9fa9b6e10 100644 --- a/en/boot-installer/trouble.xml +++ b/en/boot-installer/trouble.xml @@ -414,7 +414,7 @@ custom kernel later (see ). If you get through the initial boot phase but cannot complete the install, -the menu option Save debug logs may be helpful. +the menu option Save debug logs may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml index 03be8cd7b..224b66f8f 100644 --- a/en/preparing/pre-install-bios-setup.xml +++ b/en/preparing/pre-install-bios-setup.xml @@ -56,17 +56,6 @@ FIXME: more description of this needed. -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 -. - - - 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. diff --git a/en/using-d-i/modules/x86/lilo-installer.xml b/en/using-d-i/modules/x86/lilo-installer.xml index 9b2ead402..87053e2bf 100644 --- a/en/using-d-i/modules/x86/lilo-installer.xml +++ b/en/using-d-i/modules/x86/lilo-installer.xml @@ -63,8 +63,7 @@ If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the fdisk /mbr command to reinstall the MS-DOS master boot record — however, this means that you'll need to use -some other way to get back into Debian! For more information on this -please read . +some other way to get back into Debian! -- cgit v1.2.3