From bc869e469b8f561181b3d08aea6ec38507797f4d Mon Sep 17 00:00:00 2001 From: aaron <> Date: Tue, 17 Apr 2001 20:11:20 +0000 Subject: [PATCH] Spelling, typos, etc; mpech@prosoft.org.lv --- src/etc/etc.i386/INSTALL.ata | 8 ++++---- src/etc/etc.i386/INSTALL.chs | 19 +++++++++---------- src/etc/etc.i386/INSTALL.dbr | 8 ++++---- src/etc/etc.i386/INSTALL.linux | 10 +++++----- src/etc/etc.i386/INSTALL.mbr | 2 +- src/etc/etc.i386/INSTALL.os2br | 2 +- src/etc/etc.i386/INSTALL.pt | 2 +- 7 files changed, 25 insertions(+), 26 deletions(-) diff --git a/src/etc/etc.i386/INSTALL.ata b/src/etc/etc.i386/INSTALL.ata index ee2695b9..0df3427b 100644 --- a/src/etc/etc.i386/INSTALL.ata +++ b/src/etc/etc.i386/INSTALL.ata @@ -103,7 +103,7 @@ ATA-3 ! There is much discussion going on concerning merging ATA-3 with ATAPI. This will require some kind of "command overlap" - capability. The details of this are consumming much of the + capability. The details of this are consuming much of the meeting time. ATAPI or ATA Packet Interface @@ -553,7 +553,7 @@ Basic Questions general it is impossible for an ATA-1 host adapter to violate the specifications of an ATA-2 device. It is possible for an ATA-2 host adapter to violate the timing specifications of an - ATA-1 device but this is not common. Hoever, host adapter + ATA-1 device but this is not common. However, host adapter hardware design errors or software driver bugs can cause such a problem. The result will be corrupted data read or written to the ATA-1 device. @@ -733,7 +733,7 @@ Basic Questions Be careful when looking at the table below -- the data rate is the data transfer rate achieved while transfering the sector - or block or sectors. It is an "instantanous" data rate. The + or block or sectors. It is an "instantaneous" data rate. The overall data transfer rate for a command includes many time consuming events such as the amount of time the host requires to process an interrupt. Note that on many fast ATA drives @@ -741,7 +741,7 @@ Basic Questions frequently greater than the time required to transfer the sector of block of sectors for that interrupt! It is not uncommon for the host overhead to reduce the data rate to 1/2 - or 1/3 of the instantanous rate shown here. + or 1/3 of the instantaneous rate shown here. The ATA PIO modes are defined as follows: diff --git a/src/etc/etc.i386/INSTALL.chs b/src/etc/etc.i386/INSTALL.chs index 5091f260..99c4c1de 100644 --- a/src/etc/etc.i386/INSTALL.chs +++ b/src/etc/etc.i386/INSTALL.chs @@ -42,13 +42,13 @@ problem". Read this so that you understand the possible data integrity problem that a WD EIDE type BIOS creates. Any BIOS that has a "LBA mode" in the BIOS setup could be a WD EIDE BIOS. Be very -careful and NEVER chage the "LBA mode" setting after you have +careful and NEVER change the "LBA mode" setting after you have partitioned and installed your software. History ------- -Changes between this version and the preceeding version are +Changes between this version and the preceding version are marked by "!" at left margin of the first line of a changed or new paragraph. @@ -67,7 +67,7 @@ Version 1 -- First attempt to classify the BIOS types and Definitions ----------- -* 528MB - The maximun drive capacity that is supported by 1024 +* 528MB - The maximum drive capacity that is supported by 1024 cylinders, 16 heads and 63 sectors (1024x16x63x512). This is the limit for CHS addressing in the original IBM PC/XT and IBM PC/AT INT 13H BIOS. @@ -295,7 +295,7 @@ must support. +--> to -----------------+---> device LBA (LBA) -* A really new BIOS may also support the AH=4xH in addtion to +* A really new BIOS may also support the AH=4xH in addition to the older AH\0xH calls. This BIOS must support all possible combinations of CHS and LBA at both the INT 13H and ATA interfaces: @@ -332,7 +332,7 @@ The following explains what is widely accepted as the An ATA disk must implement both CHS and LBA addressing and must at any given time support only one P-CHS at the device -interface. And, the drive must maintain a strick relationship +interface. And, the drive must maintain a strict relationship between the sector addressing in CHS mode and LBA mode. Quoting the ATA-2 document: @@ -694,11 +694,10 @@ BIOS Type 6 such as host adapter addresses, DMA support, LBA support, etc, in the Phoenix defined "FDPT Extension" table. - Phoenix says this this BIOS need not support the INT 13H - AH=4xH read/write calls but this BIOS is really an - extension/enhancement of the original IBM/MS BIOS so most - implementations will probably support the full set of INT 13H - AH=4xH calls. + Phoenix says this BIOS need not support the INT 13H AH=4xH + read/write calls but this BIOS is really an extension/enhancement + of the original IBM/MS BIOS so most implementations will probably + support the full set of INT 13H AH=4xH calls. Support issues: Currently undefined is how such a BIOS should respond to INT 13H AH=08H calls for a drive that is >8GB. diff --git a/src/etc/etc.i386/INSTALL.dbr b/src/etc/etc.i386/INSTALL.dbr index 1f0b5fce..52340f1e 100644 --- a/src/etc/etc.i386/INSTALL.dbr +++ b/src/etc/etc.i386/INSTALL.dbr @@ -22,7 +22,7 @@ DOS FLOPPY DISK BOOT SECTOR This article is a disassembly of a floppy disk boot sector for a DOS floppy. The boot sector of a floppy disk is located at cylinder 0, head 0, sector 1. This sector is created by a floppy -disk formating program, such as the DOS FORMAT program. The boot +disk formatting program, such as the DOS FORMAT program. The boot sector of a FAT hard disk partition has a similar layout and function. Basically a bootable FAT hard disk partition looks like a big floppy during the early stages of the system's boot @@ -246,11 +246,11 @@ Now pay attention here... 0000:7C70 CD13 INT 13 do diskette reset call 0000:7C72 7279 JB TALK jmp if any error - Detemine the starting sector address of + Determine the starting sector address of the root directory as an LBA. 0000:7C74 33C0 XOR AX,AX AX is now zero -0000:7C76 3906137C CMP [7C13],AX number sectros zero? +0000:7C76 3906137C CMP [7C13],AX number sectors zero? 0000:7C7A 7408 JZ SMALL_DISK yes 0000:7C7C 8B0E137C MOV CX,[7C13] number of sectors 0000:7C80 890E207C MOV [7C20],CX save in huge num sects @@ -388,7 +388,7 @@ Now pay attention here... 0000:7D53 0AC0 OR AL,AL end of message? 0000:7D55 7429 JZ RETURN jmp if yes 0000:7D57 B40E MOV AH,0E display one character -0000:7D59 BB0700 MOV BX,0007 video attrbiutes +0000:7D59 BB0700 MOV BX,0007 video attributes 0000:7D5C CD10 INT 10 display one character 0000:7D5E EBF2 JMP MSG_LOOP do again diff --git a/src/etc/etc.i386/INSTALL.linux b/src/etc/etc.i386/INSTALL.linux index 40fab8f3..2400a9ad 100644 --- a/src/etc/etc.i386/INSTALL.linux +++ b/src/etc/etc.i386/INSTALL.linux @@ -1,4 +1,4 @@ -$OpenBSD: INSTALL.linux,v 1.8 2000/05/17 09:51:28 espie Exp $ +$OpenBSD: INSTALL.linux,v 1.9 2001/04/17 20:11:20 aaron Exp $ Linux + OpenBSD: it's possible @@ -26,7 +26,7 @@ If you want to grab space from a Windows/DOS partition, use fips. Fips20 knows all about FAT32, so windows 95 is no longer a problem. Other sources of information, especially concerning other BSD systems, -must be taken with a healthy does of scepticism. OpenBSD definitely +must be taken with a healthy does of skepticism. OpenBSD definitely differs: - disklabels can hold up to 16 partitions, - type is A6, not A5, @@ -132,7 +132,7 @@ Older flavors of linux fdisk won't recognize a6 as OpenBSD. As you can see, my linux setup is very small. I have enough to check how things such as gcc work on linux, but my machine is definitely an -OpenBSD developper's box. +OpenBSD developer's box. Get the display to sectors with u, and jot down the corresponding information as well: @@ -395,7 +395,7 @@ hda15 > - the disklabel is detected early, but handled later. - disklabel handling should remove duplicates: all partitions that are present as both MBR and disklabel partition should get removed silently. (this does -not seem to work as advertized presently). +not seem to work as advertised presently). - the remaining partitions are checked for consistency. and here is my linux fstab: @@ -435,7 +435,7 @@ netscape to tell it was run from a Linux box, when it is used under OpenBSD. Some programs, for instance maple, do depend on uname answering `Linux'. -For maple, this is straigthforward: you just have to fudge +For maple, this is straightforward: you just have to fudge /usr/local/maple/bin/maple.system.type to check OpenBSD in the same class with Linux. diff --git a/src/etc/etc.i386/INSTALL.mbr b/src/etc/etc.i386/INSTALL.mbr index 24123e63..7a3cea7e 100644 --- a/src/etc/etc.i386/INSTALL.mbr +++ b/src/etc/etc.i386/INSTALL.mbr @@ -67,7 +67,7 @@ Here is a summary of what this thing does: data to determine the drive being booted from and the location of the partition on the disk. - If no active partition table enty is found, ROM BASIC is + If no active partition table entry is found, ROM BASIC is entered via INT 18. All other errors cause a system hang, see label HANG. diff --git a/src/etc/etc.i386/INSTALL.os2br b/src/etc/etc.i386/INSTALL.os2br index 6f243869..71ba1a98 100644 --- a/src/etc/etc.i386/INSTALL.os2br +++ b/src/etc/etc.i386/INSTALL.os2br @@ -429,7 +429,7 @@ Additional data areas. 0000:7D84 F7260B00 MUL WORD PTR [000B] multiply by sector size 0000:7D88 03F8 ADD DI,AX add to memory address 0000:7D8A 5A POP DX restore upper part of LBA -0000:7D8B 58 POP AX resotre lower part of LBA +0000:7D8B 58 POP AX restore lower part of LBA 0000:7D8C 03C3 ADD AX,BX add number of sector just 0000:7D8E 83D200 ADC DX,+00 read to LBA 0000:7D91 2ACB SUB CL,BL decr requested num of sect diff --git a/src/etc/etc.i386/INSTALL.pt b/src/etc/etc.i386/INSTALL.pt index 9cc21328..7642a6bc 100644 --- a/src/etc/etc.i386/INSTALL.pt +++ b/src/etc/etc.i386/INSTALL.pt @@ -248,7 +248,7 @@ another DOS FAT: Or in more detail ('n' is the highest cylinder, head or sector -number number allowed in the indicated field of the CHS)... +number allowed in the indicated field of the CHS)... +-------------------------------------+