lostecho/oldlinux-files
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add directory study

Browse Source
This commit is contained in:
gohigh
2024-02-19 00:25:23 -05:00
parent b1306b38b1
commit f3774e2f8c
4001 changed files with 2285787 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

81
study/sabre/os/articles/DiskandDiscDrives/...htm Normal file
View File

@@ -0,0 +1,81 @@
<html><head><title>OSRC: The Operating System Resource Center </title></head>
<body BGCOLOR=#FFFFFF TEXT=#000000 LINK=#0000FF VLINK=#0000FF ALINK=#107010>
<center>
<font size=2>the</font><br>
<font face='Verdana,Helvetica' size=7><b>Operating System</b></font><br>
<font size=2>resource center</font>
</center><p><TABLE WIDTH='100%'>
<TR>
<TD VALIGN=TOP WIDTH='50%'>
<hr size=1><CENTER><FONT SIZE=6>...Software...</FONT></CENTER><hr size=1>
<ol><font size=-1><font size=+2><li><a href="../TheBootProcess/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/TheBootProcess/">The Boot Process</a></font>
<ul>Boot sectors, bootable CD-ROMs, examples..</ul>
<font size=+2><li><a href="../Partitions/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/Partitions/">Partitions</a></font>
<ul>Partition Table Layout, Partition IDs..</ul>
<font size=+2><li><a href="../FileSystems/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/FileSystems/">File Systems</a></font>
<ul>EXT/[23], Reiser, Joliet, FAT32, HPFS..</ul>
<font size=+2><li><a href="../MemoryManagement/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/MemoryManagement/">Memory Management</a></font>
<ul>EMS, XMS + Techniques..</ul>
<font size=+2><li><a href="../ProtectedMode/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/ProtectedMode/">Protected Mode</a></font>
<ul>VCPI, DPMI, GEMMIS, VDS, VOODOO, etc..</ul>
<font size=+2><li><a href="../ExecutableFileFormats/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/ExecutableFileFormats/">Executable File Formats</a></font>
<ul>.com, .exe, .lib, .obj, a.out, ELF, LE, PE..</ul>
<font size=+2><li><a href="../PlugandPlaySpecs/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/PlugandPlaySpecs/">Plug and Play Specs</a></font>
<ul>BIOS, Serial, Parrellel, ISA, Firewire..</ul>
<font size=+2><li><a href="../DeviceDriverInterfaces/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/DeviceDriverInterfaces/">Device Driver Interfaces</a></font>
<ul>Uniform Driver Interface, linux drivers..</ul>
<font size=+2><li><a href="../MiscellaneousSoftware/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/MiscellaneousSoftware/">Miscellaneous Software</a></font>
<ul>OS FAQ, overall design, VM design, threads..</ul>
</font></ol></TD>
<TD VALIGN=TOP WIDTH='50%'>
<hr size=1><CENTER><FONT SIZE=6>...Hardware...</FONT></CENTER><hr size=1>
<ol><font size=-1><font size=+2><li><a href="../ProcessorArchitecture/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/ProcessorArchitecture/">Processor Architecture</a></font>
<ul>IA64, MMX, 3D-Now!, KNI, copro, optimization..</ul>
<font size=+2><li><a href="../InterconnectBuses/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/InterconnectBuses/">Interconnect Buses</a></font>
<ul>ATA-2,3, Floppy, PCI, AGP, USB, SCSI, FC-AL..</ul>
<font size=+2><li><a href="index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/DiskandDiscDrives/">Disk and Disc Drives</a></font>
<ul>Floppys, Hard Drive Ports, CHS, CD-ROM..</ul>
<font size=+2><li><a href="../HumanInterfaceDevices/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/HumanInterfaceDevices/">Human Interface Devices</a></font>
<ul>Keyboard, Mouse, Joystick, Gamepad..</ul>
<font size=+2><li><a href="../SoundDevices/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/SoundDevices/">Sound Devices</a></font>
<ul>SB, SB16, GUS, PAS, PC-Speaker, MIDI, OPL..</ul>
<font size=+2><li><a href="../CommunicationDevices/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/CommunicationDevices/">Communication Devices</a></font>
<ul>Serial, Parallel [SPP, EPP, ECP]..</ul>
<font size=+2><li><a href="../NetworkingDevices/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/NetworkingDevices/">Networking Devices</a></font>
<ul>NE2000..</ul>
<font size=+2><li><a href="../MiscellaneousDevices/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/MiscellaneousDevices/">Miscellaneous Devices</a></font>
<ul>PIC, PIT, DMA, RTC, ..</ul>
<font size=+2><li><a href="../OtherHardware/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/OtherHardware/">Other Hardware</a></font>
<ul>Legos, ATX, NetPC's..</ul>
</font></ol></TD>
</tr></table>
<hr>
<Font size=+1 Face=Verdana>7/15/2002 Update:</font><p><ul>
Well our upgrade officially did not go well at all. Apache 2.0.x hates PHP and
our new hard drive crashed and did all kinds of bad things. Nondot is back up
and running on it's old drive, and OSRC seems to be working again. Sorry for
the interruption, thanks for all of those who let me know! :)<p>
-<a href="mailto:sabre@nondot.org">Chris</a>
</ul><hr>
<TABLE ALIGN=RIGHT BORDER=0><TR><TD><center>
Copyright &copy; 1995-2002 <i><a href='mailto:sabre@nondot.org'>Chris Lattner</a></i><br>
This page last modified:11/20/01<br>View <a href="../../../../sabre" tppabs="http://www.nondot.org/sabre">the rest</a> of this site...<br>
</center></TD></TR></TABLE>
<font size=-1>
[about] [faq]
[<a href="../../Updates/index.htm" tppabs="http://www.nondot.org/~sabre/os/Updates/">updates</a>]
[<a href="../../Stats/index.htm" tppabs="http://www.nondot.org/~sabre/os/Stats/">stats</a>]
[<a href="../../AuthorRecognition.html" tppabs="http://www.nondot.org/~sabre/os/AuthorRecognition.html">author recognition</a>]
[<a href="../../submit/index.htm" tppabs="http://www.nondot.org/~sabre/os/submit/">contributing</a>]
[<a href="../PendingQueue/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/PendingQueue/">pending submissions</a>]
[feedback]
[<a href='mailto:sabre@nondot.org'>email</a>]
[<a href="../index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/">up</a>]
</font><p>
<font size=-1>
<font color=#FF0000>(new!)</font> sections have been updated in the last week...
<font color=#808000>(recent)</font> sections have been updated in the last two weeks...<br>
</font>

88
study/sabre/os/articles/DiskandDiscDrives/index.htm Normal file
View File

@@ -0,0 +1,88 @@
<html><head><title>OSRC: Disk and Disc Drives </title></head>
<body BGCOLOR=#FFFFFF TEXT=#000000 LINK=#0000FF VLINK=#0000FF ALINK=#107010>
<center><font face=Verdana size=7><b>Disk and Disc Drives</b></font></center><blockquote>Floppys, Hard Drive Ports, CHS, CD-ROM..</blockquote><table width="100%" cellpadding=0 cellspacing=0 border=0>
<tr><td width="33%" align=left></td>
<td width='33%' align=center></td>
<td width='33%' align=right><font size=2>[<a href="...htm" tppabs="http://www.nondot.org/~sabre/os/articles/DiskandDiscDrives/..">Up</a>]</font></td></tr>
</table><hr><p><ul><DL>
<DT><font size=+1>Hard Drives:</font><br>
<ul><DL>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/IDE-tech.html" tppabs="http://www.nondot.org/sabre/os/files/Disk/IDE-tech.html">IDE - Hardware Reference &amp; Information Document</a></font> - by <a href='mailto:ivopola@emco.co.nz'>Alex T. Ivopol</a><br>
<DD>This document gives a lot of details about accessing and manipulating IDE disks directly, as an operating system would have to do. This document is heartily recommended for those who do not want to use the BIOS through VM86 mode. :)<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/HD_PORTS.asm" tppabs="http://www.nondot.org/sabre/os/files/Disk/HD_PORTS.asm">Reading the harddisk using ports</a></font> - by qark<br>
<DD>This file describes the IO ports that are available on an IDE disk, as well as some example code to go with it. The sample code demonstrates reading and writing to the disk...<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/IDEHDC.asm" tppabs="http://www.nondot.org/sabre/os/files/Disk/IDEHDC.asm">Direct disk I/O module for IDE disk controllers</a></font> - by Alan Martin<br>
<DD>This code example demonstrates direct IDE disk control, using the IO ports. This code does not use interrupts to drive the disk, but instead polls for the data. Also included is this <a href="../../../../sabre/os/files/Disk/HDTEST.asm" tppabs="http://www.nondot.org/sabre/os/files/Disk/HDTEST.asm">test program</a>.<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/CHSTranslation.txt" tppabs="http://www.nondot.org/sabre/os/files/Disk/CHSTranslation.txt">How It Works -- CHS Translation</a></font> - by <a href='mailto:landis@sugs.tware.com'>Hale Landis</a><br>
<DD>"Why is an understanding of how a BIOS works so important? The basic reason is that the information returned by INT 13H AH=08H is used by FDISK, it is used in the partition table entries within a partition record (like the Master Boot Record) that are created by FDISK, and it is used by the small boot program that FDISK places into the Master Boot Record. The information returned by INT 13H AH=08H is in cylinder/head/sector (CHS) format -- it is not in LBA format. The boot processing done by your computer's BIOS (INT 19H and INT 13H) is all CHS based."<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/IDEInterrogate.zip" tppabs="http://www.nondot.org/sabre/os/files/Disk/IDEInterrogate.zip">IDE Interrogator</a></font> - by <a href='mailto:dcm@mincom.oz.au'>Doug Merrett</a><br>
<DD>"This program will interrogate an IDE hard drive and display the resulting details in a 'quick and dirty' fashion. This was knocked together one night after managing to get my hands on an IDE Hard Drive Technical Manual." Includes source code and a binary.<p>
<DT><font size=+1>General Hard Disk Information:</font><br>
<ul><DL>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/HDTECH01.txt" tppabs="http://www.nondot.org/sabre/os/files/Disk/HDTECH01.txt">Technicians' Guide to Hard Disks (ch 1)</a></font> - by Nicholas Majors<br>
<DD>"This booklet (now electronic) is published as a service of Data Recovery Labs. Its purpose is to provide the fundamental knowledge of concepts and terminology that is necessary to deal with the complexities of hard disk subsystems. It is not a technical reference guide and should not replace original documentation made available by manufacturers."<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/HDTECH02.txt" tppabs="http://www.nondot.org/sabre/os/files/Disk/HDTECH02.txt">Technicians' Guide to Hard Disks (ch 2)</a></font> - by Nicholas Majors<br>
<DD>"Before we consider how to install, configure and maintain hard drives, we need a basic understanding of drive construction and design concepts. This chapter examines in some detail the parts and functional components of hard drive subsystems."<p>
</DL></ul>
</DL></ul>
<DT><font size=+1>CD-ROM Drives:</font><br>
<ul><DL>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/CDROM.txt" tppabs="http://www.nondot.org/sabre/os/files/Disk/CDROM.txt">CD-ROM Technical Summary</a></font> - by Andy Poggio<br>
<DD>"This summary describes how information is encoded on Compact Disc (CD) beginning with the physical pits and going up through higher levels of data encoding to the structured multimedia information that is possible with programs like HyperCard. This discussion is much broader than any single standards document, e.g. the CD-Audio Red Book, while omitting much of the detail needed only by drive manufacturers."<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/MSCDEX21.txt" tppabs="http://www.nondot.org/sabre/os/files/Disk/MSCDEX21.txt">Microsoft MS-DOS CD-ROM Extensions 2.1</a></font> - by Microsoft Corp.<br>
<DD>"The Microsoft MS-DOS CD-ROM Extensions are an extension to the MS-DOS operating system which permit reading CD-ROM disks which conform to both the High Sierra May 28th format and the ISO-9660 version of the High Sierra format. The CD-ROM disc appears just like a magnetic disk to the user and to applications software, ensuring compatibility with current software."<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/cdromfaq.txt" tppabs="http://www.nondot.org/sabre/os/files/Disk/cdromfaq.txt">CD-ROM programming FAQ Version 1.0</a></font> - by <a href='mailto:marcj@nando.net'>Marcus W. Johnson</a><br>
<DD>This document describes how to control a CD-ROM drive under DOS with the MSCDEX driver.<p>
<DT><font size=+1><a href="../../../../sabre/os/files/FileSystems/Information_Specification_for_Bootable_CD-ROM.pdf" tppabs="http://www.nondot.org/sabre/os/files/FileSystems/Information_Specification_for_Bootable_CD-ROM.pdf">Information Specification for Bootable CD-ROMs</a></font> - by <a href='mailto:curtis_stevens@bannet.ptltd.com'>SFF Committee</a><br>
<DD>"This document defines how CD-ROM manufacturers can package several
floppy and hard disk images on a single piece of media with the ability to
catalog these images and selectively boot from any single image."<p>
</DL></ul>
<DT><font size=+1>Floppy Drives:</font><br>
<ul><DL>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/82077AA_FloppyControllerDatasheet.pdf" tppabs="http://www.nondot.org/sabre/os/files/Disk/82077AA_FloppyControllerDatasheet.pdf">Floppy Drive Controller Data Sheet</a></font> - by Intel Corp<br>
<DD>This is the official datasheet from Intel for the 82077AA single chip floppy disk controller chip.<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/FLOPPY.TXT" tppabs="http://www.nondot.org/sabre/os/files/Disk/FLOPPY.TXT">The 8272A Floppy Disk Controller</a></font><br>
<DD>This document details the IO port interface exposed by the common 8272A Floppy controller. Virtually every PC has one of this in it, virtually every OS supports em...<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/FloppySerialNumbers.txt" tppabs="http://www.nondot.org/sabre/os/files/Disk/FloppySerialNumbers.txt">Calculating Serial Numbers for Floppy's</a></font> - by 'Ray'<br>
<DD>This is a short document that describes how DOS assigns volume serial numbers when formatting disks...<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/FloppyMediaIDs.txt" tppabs="http://www.nondot.org/sabre/os/files/Disk/FloppyMediaIDs.txt">Floppy Media Type ID's</a></font> - by <a href='mailto:raster@indirect.com'>Raster</a><br>
<DD>Listing of the BIOS media ID codes for various floppy drive types and sizes.<p>
</DL></ul>
<DT><font size=+1>Misc Topics:</font><br>
<ul><DL>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/DeviceBaySpecsV0.90.pdf" tppabs="http://www.nondot.org/sabre/os/files/Disk/DeviceBaySpecsV0.90.pdf">Device Bay Specification v0.90</a></font> - by Compaq, Intel &amp; Microsoft<br>
<DD>"Device Bay is an industry specification defining a mechanism for easily adding and upgrading PC peripheral devices without opening the chassis. The Device Bay specification applies to all classes of computers, explicitly including desktop, mobile, home and server computers. This specification defines characteristics of both peripheral devices and system bays."<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/MediaStatusNotificationSpecForSCSIandATAPIDevicesV0.1.html" tppabs="http://www.nondot.org/sabre/os/files/Disk/MediaStatusNotificationSpecForSCSIandATAPIDevicesV0.1.html">Media Status Notification Support Spec for SCSI and ATAPI Devices v0.1</a></font> - by Microsoft Corp.<br>
<DD>"A major shortcoming of removable media devices on PC platforms is their inability to report to the host when the user attempts to eject the medium. Currently most removable media devices just eject the medium when the user presses the Eject button, and potentially any data the operating system has not saved to the device is lost. Various volume tracking and locking schemes reduce this risk, but do not eliminate it. Ideally, devices will have a means of communicating to the host that the user wants to eject the medium or has inserted a new medium.<P>This specification defines a protocol for providing this function for SCSI ATA and ATAPI devices. The support is enabled using a new SCSI command, ENABLE MEDIA STATUS, and the media status is retrieved using a new SCSI ATA command, GET MEDIA STATUS."<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/DOSSector2PhysicalSector.txt" tppabs="http://www.nondot.org/sabre/os/files/Disk/DOSSector2PhysicalSector.txt">Converting between DOS and Physical Sector ID's</a></font> - by <a href='mailto:dkrull@prairienet.org'>Don Krull</a><br>
<DD>This email message describes how to convert a DOS sector number into a BIOS sector number, taking into account the geometry of the disk.<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/SecureDeletion.html" tppabs="http://www.nondot.org/sabre/os/files/Disk/SecureDeletion.html">Secure Deletion of Data from Magnetic and Solid-State Memory</a></font> - by <a href='mailto:pgut001@cs.auckland.ac.nz'>Peter Gutmann</a><br>
<DD>"With the use of increasingly sophisticated encryption systems, an attacker wishing to gain access to sensitive data is forced to look elsewhere for information. One avenue of attack is the recovery of supposedly erased data from magnetic media or random-access memory. This paper covers some of the methods available to recover erased data and presents schemes to make this recovery significantly more difficult." - Paper includes many references.<p>
<DT><font size=+1><a href="../../../../sabre/os/files/Disk/The_Design_of_Large-Scale,_Do-It-Yourself_RAIDs.pdf" tppabs="http://www.nondot.org/sabre/os/files/Disk/The_Design_of_Large-Scale,_Do-It-Yourself_RAIDs.pdf">The Design of Large-Scale, Do-It-Yourself RAIDs</a></font> - by <a href='mailto:patterson@cs.berkeley.edu'>Satoshi Asami, Nisha Talagala, Thomas Anderson, Ken Lutz, and David Patterson</a><br>
<DD>"In this paper we explore the design of 'Do-It-Yourself' RAIDs: RAID systems that can assembled by the end user from commercially available disks, enclosures, cables, racks, computers, and networks. We quantitatively
evaluate the tradeoffs in cost, performance, and reliability of these DIY-RAID systems."<p>
</DL></ul>
</DL></ul>
<hr>
<TABLE ALIGN=RIGHT BORDER=0><TR><TD><center>
Copyright &copy; 1995-2002 <i><a href='mailto:sabre@nondot.org'>Chris Lattner</a></i><br>
This page last modified:11/04/03<br><a href="...htm" tppabs="http://www.nondot.org/~sabre/os/articles/DiskandDiscDrives/..">Go up a level</a><br>
</center></TD></TR></TABLE>
<font size=-1>
[about] [faq]
[<a href="../../Updates/index.htm" tppabs="http://www.nondot.org/~sabre/os/Updates/">updates</a>]
[<a href="../../Stats/index.htm" tppabs="http://www.nondot.org/~sabre/os/Stats/">stats</a>]
[<a href="../../AuthorRecognition.html" tppabs="http://www.nondot.org/~sabre/os/AuthorRecognition.html">author recognition</a>]
[<a href="../../submit/index.htm" tppabs="http://www.nondot.org/~sabre/os/submit/">contributing</a>]
[<a href="../PendingQueue/index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/PendingQueue/">pending submissions</a>]
[feedback]
[<a href='mailto:sabre@nondot.org'>email</a>]
[<a href="../index.htm" tppabs="http://www.nondot.org/~sabre/os/articles/">up</a>]
</font><p>
<font size=-1>
<font color=#FF0000>(new!)</font> sections have been updated in the last week...
<font color=#808000>(recent)</font> sections have been updated in the last two weeks...<br>
</font>

88
study/sabre/os/articles/DiskandDiscDrives/index.html Normal file
View File

@@ -0,0 +1,88 @@
<html><head><title>OSRC: Disk and Disc Drives </title></head>
<body BGCOLOR=#FFFFFF TEXT=#000000 LINK=#0000FF VLINK=#0000FF ALINK=#107010>
<center><font face=Verdana size=7><b>Disk and Disc Drives</b></font></center><blockquote>Floppys, Hard Drive Ports, CHS, CD-ROM..</blockquote><table width="100%" cellpadding=0 cellspacing=0 border=0>
<tr><td width="33%" align=left></td>
<td width='33%' align=center></td>
<td width='33%' align=right><font size=2>[<a href='..'>Up</a>]</font></td></tr>
</table><hr><p><ul><DL>
<DT><font size=+1>Hard Drives:</font><br>
<ul><DL>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/IDE-tech.html'>IDE - Hardware Reference &amp; Information Document</a></font> - by <a href='mailto:ivopola@emco.co.nz'>Alex T. Ivopol</a><br>
<DD>This document gives a lot of details about accessing and manipulating IDE disks directly, as an operating system would have to do. This document is heartily recommended for those who do not want to use the BIOS through VM86 mode. :)<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/HD_PORTS.asm'>Reading the harddisk using ports</a></font> - by qark<br>
<DD>This file describes the IO ports that are available on an IDE disk, as well as some example code to go with it. The sample code demonstrates reading and writing to the disk...<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/IDEHDC.asm'>Direct disk I/O module for IDE disk controllers</a></font> - by Alan Martin<br>
<DD>This code example demonstrates direct IDE disk control, using the IO ports. This code does not use interrupts to drive the disk, but instead polls for the data. Also included is this <a href="/sabre/os/files/Disk/HDTEST.asm">test program</a>.<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/CHSTranslation.txt'>How It Works -- CHS Translation</a></font> - by <a href='mailto:landis@sugs.tware.com'>Hale Landis</a><br>
<DD>"Why is an understanding of how a BIOS works so important? The basic reason is that the information returned by INT 13H AH=08H is used by FDISK, it is used in the partition table entries within a partition record (like the Master Boot Record) that are created by FDISK, and it is used by the small boot program that FDISK places into the Master Boot Record. The information returned by INT 13H AH=08H is in cylinder/head/sector (CHS) format -- it is not in LBA format. The boot processing done by your computer's BIOS (INT 19H and INT 13H) is all CHS based."<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/IDEInterrogate.zip'>IDE Interrogator</a></font> - by <a href='mailto:dcm@mincom.oz.au'>Doug Merrett</a><br>
<DD>"This program will interrogate an IDE hard drive and display the resulting details in a 'quick and dirty' fashion. This was knocked together one night after managing to get my hands on an IDE Hard Drive Technical Manual." Includes source code and a binary.<p>
<DT><font size=+1>General Hard Disk Information:</font><br>
<ul><DL>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/HDTECH01.txt'>Technicians' Guide to Hard Disks (ch 1)</a></font> - by Nicholas Majors<br>
<DD>"This booklet (now electronic) is published as a service of Data Recovery Labs. Its purpose is to provide the fundamental knowledge of concepts and terminology that is necessary to deal with the complexities of hard disk subsystems. It is not a technical reference guide and should not replace original documentation made available by manufacturers."<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/HDTECH02.txt'>Technicians' Guide to Hard Disks (ch 2)</a></font> - by Nicholas Majors<br>
<DD>"Before we consider how to install, configure and maintain hard drives, we need a basic understanding of drive construction and design concepts. This chapter examines in some detail the parts and functional components of hard drive subsystems."<p>
</DL></ul>
</DL></ul>
<DT><font size=+1>CD-ROM Drives:</font><br>
<ul><DL>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/CDROM.txt'>CD-ROM Technical Summary</a></font> - by Andy Poggio<br>
<DD>"This summary describes how information is encoded on Compact Disc (CD) beginning with the physical pits and going up through higher levels of data encoding to the structured multimedia information that is possible with programs like HyperCard. This discussion is much broader than any single standards document, e.g. the CD-Audio Red Book, while omitting much of the detail needed only by drive manufacturers."<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/MSCDEX21.txt'>Microsoft MS-DOS CD-ROM Extensions 2.1</a></font> - by Microsoft Corp.<br>
<DD>"The Microsoft MS-DOS CD-ROM Extensions are an extension to the MS-DOS operating system which permit reading CD-ROM disks which conform to both the High Sierra May 28th format and the ISO-9660 version of the High Sierra format. The CD-ROM disc appears just like a magnetic disk to the user and to applications software, ensuring compatibility with current software."<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/cdromfaq.txt'>CD-ROM programming FAQ Version 1.0</a></font> - by <a href='mailto:marcj@nando.net'>Marcus W. Johnson</a><br>
<DD>This document describes how to control a CD-ROM drive under DOS with the MSCDEX driver.<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/FileSystems/Information_Specification_for_Bootable_CD-ROM.pdf'>Information Specification for Bootable CD-ROMs</a></font> - by <a href='mailto:curtis_stevens@bannet.ptltd.com'>SFF Committee</a><br>
<DD>"This document defines how CD-ROM manufacturers can package several
floppy and hard disk images on a single piece of media with the ability to
catalog these images and selectively boot from any single image."<p>
</DL></ul>
<DT><font size=+1>Floppy Drives:</font><br>
<ul><DL>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/82077AA_FloppyControllerDatasheet.pdf'>Floppy Drive Controller Data Sheet</a></font> - by Intel Corp<br>
<DD>This is the official datasheet from Intel for the 82077AA single chip floppy disk controller chip.<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/FLOPPY.TXT'>The 8272A Floppy Disk Controller</a></font><br>
<DD>This document details the IO port interface exposed by the common 8272A Floppy controller. Virtually every PC has one of this in it, virtually every OS supports em...<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/FloppySerialNumbers.txt'>Calculating Serial Numbers for Floppy's</a></font> - by 'Ray'<br>
<DD>This is a short document that describes how DOS assigns volume serial numbers when formatting disks...<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/FloppyMediaIDs.txt'>Floppy Media Type ID's</a></font> - by <a href='mailto:raster@indirect.com'>Raster</a><br>
<DD>Listing of the BIOS media ID codes for various floppy drive types and sizes.<p>
</DL></ul>
<DT><font size=+1>Misc Topics:</font><br>
<ul><DL>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/DeviceBaySpecsV0.90.pdf'>Device Bay Specification v0.90</a></font> - by Compaq, Intel &amp; Microsoft<br>
<DD>"Device Bay is an industry specification defining a mechanism for easily adding and upgrading PC peripheral devices without opening the chassis. The Device Bay specification applies to all classes of computers, explicitly including desktop, mobile, home and server computers. This specification defines characteristics of both peripheral devices and system bays."<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/MediaStatusNotificationSpecForSCSIandATAPIDevicesV0.1.html'>Media Status Notification Support Spec for SCSI and ATAPI Devices v0.1</a></font> - by Microsoft Corp.<br>
<DD>"A major shortcoming of removable media devices on PC platforms is their inability to report to the host when the user attempts to eject the medium. Currently most removable media devices just eject the medium when the user presses the Eject button, and potentially any data the operating system has not saved to the device is lost. Various volume tracking and locking schemes reduce this risk, but do not eliminate it. Ideally, devices will have a means of communicating to the host that the user wants to eject the medium or has inserted a new medium.<P>This specification defines a protocol for providing this function for SCSI ATA and ATAPI devices. The support is enabled using a new SCSI command, ENABLE MEDIA STATUS, and the media status is retrieved using a new SCSI ATA command, GET MEDIA STATUS."<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/DOSSector2PhysicalSector.txt'>Converting between DOS and Physical Sector ID's</a></font> - by <a href='mailto:dkrull@prairienet.org'>Don Krull</a><br>
<DD>This email message describes how to convert a DOS sector number into a BIOS sector number, taking into account the geometry of the disk.<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/SecureDeletion.html'>Secure Deletion of Data from Magnetic and Solid-State Memory</a></font> - by <a href='mailto:pgut001@cs.auckland.ac.nz'>Peter Gutmann</a><br>
<DD>"With the use of increasingly sophisticated encryption systems, an attacker wishing to gain access to sensitive data is forced to look elsewhere for information. One avenue of attack is the recovery of supposedly erased data from magnetic media or random-access memory. This paper covers some of the methods available to recover erased data and presents schemes to make this recovery significantly more difficult." - Paper includes many references.<p>
<DT><font size=+1><a href='http://www.nondot.org/sabre/os/files/Disk/The_Design_of_Large-Scale,_Do-It-Yourself_RAIDs.pdf'>The Design of Large-Scale, Do-It-Yourself RAIDs</a></font> - by <a href='mailto:patterson@cs.berkeley.edu'>Satoshi Asami, Nisha Talagala, Thomas Anderson, Ken Lutz, and David Patterson</a><br>
<DD>"In this paper we explore the design of 'Do-It-Yourself' RAIDs: RAID systems that can assembled by the end user from commercially available disks, enclosures, cables, racks, computers, and networks. We quantitatively
evaluate the tradeoffs in cost, performance, and reliability of these DIY-RAID systems."<p>
</DL></ul>
</DL></ul>
<hr>
<TABLE ALIGN=RIGHT BORDER=0><TR><TD><center>
Copyright &copy; 1995-2002 <i><a href='mailto:sabre@nondot.org'>Chris Lattner</a></i><br>
This page last modified:11/05/03<br><a href='..'>Go up a level</a><br>
</center></TD></TR></TABLE>
<font size=-1>
[about] [faq]
[<a href='/sabre/os/articles/../Updates/'>updates</a>]
[<a href='/sabre/os/articles/../Stats/'>stats</a>]
[<a href='/sabre/os/articles/../AuthorRecognition.html'>author recognition</a>]
[<a href='/sabre/os/articles/../submit/'>contributing</a>]
[<a href='/sabre/os/articles/PendingQueue/'>pending submissions</a>]
[feedback]
[<a href='mailto:sabre@nondot.org'>email</a>]
[<a href='../'>up</a>]
</font><p>
<font size=-1>
<font color=#FF0000>(new!)</font> sections have been updated in the last week...
<font color=#808000>(recent)</font> sections have been updated in the last two weeks...<br>
</font>