DOCSLIB.ORG

Microsoft File System General Comments Boot Sector and BPB Boot Sector and BPB Structure FAT Data Structure

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Microsoft File System General Comments Boot Sector and BPB Boot Sector and BPB Structure FAT Data Structure Graduate Institute of Electronics Engineering, NTU MMiiccrroossoofftt FFiillee SSyysstteemm Instructor: Chia-Tsun Wu. 11/25/2004 ACCESS IC LAB ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU OOuuttlliinnee Types of File System Principles of File System Microsoft File System General Comments Boot Sector and BPB Boot Sector and BPB Structure FAT Data Structure LAB P2 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU TTyyppeess ooff FFiilleeSSyysstteemm DOS FAT 12/16/32, VFAT High Performance FileSystem (HPFS) New Technology FileSystem (NTFS) Extended filesystems (Ext, Ext2, Ext3) Macintosh Hierarchical Filesystem - HFS ISO 9660 - CD-ROM filesystem P3 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU OOtthheerr ffiilleessyysstteemmss ADFS - Acorn Disc File System NSS - Novell Storage Services AFFS - Amiga fast filesystem ODS - On Disk Structure filesystem BeFS - BeOS filesystem QNX filesystem BFS - UnixWare Boot Filesystem Reiser filesystem CrosStor filesystem RFS (CD-ROM Filesystem) DTFS - Desktop filesystem RomFS - Rom filesystem EFS - Enhanced filesystem (Linux) SFS - Secure filesystem EFS - Extent filesystem (IRIX) Spiralog filesystem (OpenVMS) FFS - BSD Fast filesystem System V and derived filesystems GPFS - General Parallel Filesystem Text - (Philips' CD-ROM Filesystem) HFS - HP-UX Hi performance filesystem UDF - Universal Disk Format (DVD-ROM HTFS - High throughput filesystem filesystem) LFS - Linux log structured filesystem UFS JFS - Journaled filesystem (HP-UX, AIX, V7 Filesystem OS/2 5, Linux) VxFS - Veritas filesystem (HP-UX, SCO MFS - Macintosh filesystem UnixWare, Solaris) Minix filesystem XFS - Extended filesystem (IRIX) NWFS - Novell NetWare filesystem Xia FS P4 Graduate Institute of Electronics Engineering, NTU FFiillee--SSyysstteemm SSttrruuccttuurree ACCESS IC LAB ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU IInnttrroodduuccttiioonn File structure Logical storage unit Collection of related information File system resides on secondary storage (disks) File system organized into layers File control block storage structure consisting of information about a file Ownership, permissions, and location of the file content I/O transfers between memory and disk are performed in units of blocks (one more more sectors) P6 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU LLaayyeerreedd FFiillee SSyysstteemm P7 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU LLaayyeerreedd FFiillee SSyysstteemm ((CCoonntt..)) I/O control device drivers and interrupt handlers Transfer information between main memory and disk system Retrieve block 123 HW-specific instructions Basic file system Issue generic commands to device driver to read and write physical blocks on the disk Physical block: drive 1, cylinder 73, track 2, sector 10 P8 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU LLaayyeerreedd FFiillee SSyysstteemm ((CCoonntt..)) File-organization module Know about files, their logical blocks, and physical blocks Translate logical blocks to physical blocks (similar to VM) Logical blocks: 0 N Free-space manager Blocks allocation Logical file system manage metadata information Metadata: file-system structure, excluding the actual file contents Manage the directory structure via file control blocks (FCB) P9 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU LLaayyeerreedd FFiillee SSyysstteemm ((CCoonntt..)) Why Layered file system? All the advantages of the layered approach File system standard: UFS, FAT FAT32, NTFS Duplication of code is minimized for different file system standard Usually I/O control and the basic file system code can be used by multiple file system formats. P10 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU AA TTyyppiiccaall FFCCBB P11 Graduate Institute of Electronics Engineering, NTU FFiillee SSyysstteemm IImmpplleemmeennttaattiioonn ACCESS IC LAB ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU OOnn--DDiisskk SSttrruuccttuurreess Boot control block: information needed by the system to boot an OS from that partition UFS: boot block; NTFS: partition boot sector Partition control block: partition details No. of blocks, size of the blocks, free-block count and free- block pointers, free FCB count and FCB pointers UFS: superblock; NTFS: Master File Table A directory structure is used to organize the files File control block: many of the file s details File permissions, ownership, size, location of the data blocks UFS: inode; NTFS: within the Master File Table P13 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU IInn--MMeemmoorryy SSttrruuccttuurreess An in-memory partition table containing information about each mounted partition An in-memory directory structure that holds the directory information of recently accessed directories The system-wide open-file table (Chapter 11) The per-process open-file table (Chapter 11) Caching information so that no need to retrieve the information every time from the disk P14 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU IInn--MMeemmoorryy FFiillee--SSyysstteemm SSttrruuccttuurreess File Open File Read P15 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU VViirrttuuaall FFiillee SSyysstteemmss Virtual File Systems (VFS) provide an object-oriented way of implementing file systems VFS separates file-system-generic operations from their implementation by defining a clean VFS interface VFS allows the same system call interface (the API) to be used for different types of file systems VFS is based on a file-representation structure, called a vnode, that contains a numerical designator for a network-wide unique file The API is to the VFS interface, rather than any specific type of file system P16 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU SScchheemmaattiicc VViieeww ooff VViirrttuuaall FFiillee SSyysstteemm Open, read, write P17 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU DDiirreeccttoorryy IImmpplleemmeennttaattiioonn Linear list of file names with pointer to the data blocks Simple to program Time-consuming to execute linear search to find a particular entry Cache and sorted list may help Hash Table linear list with hash data structure Decreases directory search time Collisions situations where two file names hash to the same location Fixed size and the dependence of the hash function on that size P18 Graduate Institute of Electronics Engineering, NTU AAllllooccaattiioonn MMeetthhooddss How to allocate space to files so that disk space is utilized effectively and files can be accessed quickly ACCESS IC LAB ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU CCoonnttiigguuoouuss AAllllooccaattiioonn A file occupies a set of contiguous blocks on disk Only starting block (block #) and length (number of blocks) are required in the directory entry (FCB) Fast -- Minimal seek time and head movement Random access any block within the file Similar to dynamic storage-allocation problem External fragmentation may need compaction Files are difficult to grow Find a larger hole and copy the file to the new space P20 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU CCoonnttiigguuoouuss AAllllooccaattiioonn ((CCoonntt..)) P21 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU EExxtteenntt--BBaasseedd SSyysstteemmss Many newer file systems (I.e. Veritas File System) use a modified contiguous allocation scheme Extent-based file systems allocate disk blocks in extents An extent is a contiguous block of disks. Extents are allocated for file allocation. A file consists of one or more extents. Integrate contiguous allocation and linked allocation (see later) P22 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU LLiinnkkeedd AAllllooccaattiioonn Each file is a linked list of disk blocks Blocks may be scattered anywhere on the disk Directory contains a pointer to the first and last blocks Each block contains a pointer to the next block Advantages No external fragmentation Easy to grow Any free block is OK Disadvantages Effectively for only sequential-access file Space required for the pointers Reliability What if the pointers are lost P23 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU LLiinnkkeedd AAllllooccaattiioonn ((CCoonntt..)) block = pointer data P24 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU LLiinnkkeedd AAllllooccaattiioonn ((CCoonntt..)) Solution for spaces for pointers Collect blocks into clusters, and allocate the clusters than blocks ( Allocate Cluster, Block) Fewer disk head seeks and decreases the space needed for block allocation and free-list management Internal fragmentation Solution for reliability Double linked list or store the filename and relative block number in each block More overhead for each file P25 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU LLiinnkkeedd AAllllooccaattiioonn ((CCoonntt..)) FAT (File Allocation Table) OS/2, MS-DOS The table has one entry for each disk block and is indexed by block number Similar to the linked list Contain the block number Pointer of the next block in the file FAT Significant number of disk Data Block head seeks One for FAT, one for data Improved by caching FAT Random access time is improved P26 ACCESS IC LAB Graduate Institute of Electronics Engineering, NTU IInnddeexxeedd AAllllooccaattiioonn Bring all pointers together into the index block An array of disk-block addresses The
Load more

Recommended publications
  • Active@ UNDELETE Documentation
    Active @ UNDELETE Users Guide | Contents | 2 Contents Legal Statement.........................................................................................................5 Active@ UNDELETE Overview............................................................................. 6 Getting Started with Active@ UNDELETE.......................................................... 7 Active@ UNDELETE Views And Windows...................................................................................................... 7 Recovery Explorer View.......................................................................................................................... 8 Logical Drive Scan Result View..............................................................................................................9 Physical Device Scan View......................................................................................................................9 Search Results View...............................................................................................................................11 File Organizer view................................................................................................................................ 12 Application Log...................................................................................................................................... 13 Welcome View........................................................................................................................................14 Using
    [Show full text]
  • Membrane: Operating System Support for Restartable File Systems Swaminathan Sundararaman, Sriram Subramanian, Abhishek Rajimwale, Andrea C
    Membrane: Operating System Support for Restartable File Systems Swaminathan Sundararaman, Sriram Subramanian, Abhishek Rajimwale, Andrea C. Arpaci-Dusseau, Remzi H. Arpaci-Dusseau, Michael M. Swift Computer Sciences Department, University of Wisconsin, Madison Abstract and most complex code bases in the kernel. Further, We introduce Membrane, a set of changes to the oper- file systems are still under active development, and new ating system to support restartable file systems. Mem- ones are introduced quite frequently. For example, Linux brane allows an operating system to tolerate a broad has many established file systems, including ext2 [34], class of file system failures and does so while remain- ext3 [35], reiserfs [27], and still there is great interest in ing transparent to running applications; upon failure, the next-generation file systems such as Linux ext4 and btrfs. file system restarts, its state is restored, and pending ap- Thus, file systems are large, complex, and under develop- plication requests are serviced as if no failure had oc- ment, the perfect storm for numerous bugs to arise. curred. Membrane provides transparent recovery through Because of the likely presence of flaws in their imple- a lightweight logging and checkpoint infrastructure, and mentation, it is critical to consider how to recover from includes novel techniques to improve performance and file system crashes as well. Unfortunately, we cannot di- correctness of its fault-anticipation and recovery machin- rectly apply previous work from the device-driver litera- ery. We tested Membrane with ext2, ext3, and VFAT. ture to improving file-system fault recovery. File systems, Through experimentation, we show that Membrane in- unlike device drivers, are extremely stateful, as they man- duces little performance overhead and can tolerate a wide age vast amounts of both in-memory and persistent data; range of file system crashes.
    [Show full text]
  • [JUMP FLOPPY Bios PARAMETER BLOCK—\20
    US 20020026571A1 (19) United States (12) Patent Application Publication (10) Pub. No.: US 2002/0026571 A1 Rickey (43) Pub. Date: Feb. 28, 2002 (54) DUAL USE MASTER BOOT RECORD comprising: a computer usable medium including at least one partition area and a boot sector, With the computer (76) Inventor: Albert E. Rickey, Lake Forest, CA usable medium having computer readable program code (Us) means embodied therein, comprising: ?rst computer read able code means ?xed in the boot sector including a ?rst Correspondence Address: BIOS parameter block for setting parameters for the medium IRELL & MANELLA LLP if inserted in a ?oppy drive of the computer; and second 840 NEWPORT CENTER DRIVE SUITE 400 computer readable code means ?xed in the boot sector NEWPORT BEACH, CA 92660 (US) comprising a Partition Table for organizing the medium to include at least one partition and for designating an active (21) Appl. No.: 09/960,181 partition. In a further embodiment of the invention, the article of manufacture includes: third computer readable (22) Filed: Sep. 20, 2001 code means ?xed in the active partition area on the computer readable medium and including a second BIOS parameter Related US. Application Data block, and DOS boot record code for locating operating system ?les, loading the operating system ?les into the (63) Continuation of application No. 09/163,359, ?led on memory of the computer and causing the computer to Sep. 30, 1998, noW Pat. No. 6,308,264. execute them; and fourth computer readable code means ?xed in the boot sector comprising a master boot record code Publication Classi?cation for loading into the memory of the computer the third computer readable code means comprising the second BIOS (51) Int.
    [Show full text]
  • Reference Modification Error in Cobol
    Reference Modification Error In Cobol Bartholomeus freeze-dries her Burnley when, she objurgates it atilt. Luke still brutalize prehistorically while rosaceous Dannie aphorizing that luncheonettes. When Vernor splashes his exobiologists bronzing not histrionically enough, is Efram attrite? The content following a Kubernetes template file. Work during data items. Those advice are consolidated, transformed and made sure for the mining and online processing. For post, if internal programs A and B are agile in a containing program and A calls B and B cancels A, this message will be issued. Charles Phillips to demonstrate his displeasure. The starting position itself must man a positive integer less than one equal possess the saw of characters in the reference modified function result. Always some need me give when in quotes. Cobol reference an error will open a cobol reference modification error in. The MOVE command transfers data beyond one specimen of storage to another. Various numeric intrinsic functions are also mentioned. Is there capital available version of the rpg programming language available secure the PC? Qualification, reference modification, and subscripting or indexing allow blood and unambiguous references to that resource. Writer was slated to be shown at the bass strings should be. Handle this may be sorted and a precision floating point in sequential data transfer be from attacks in virtually present before performing a reference modification starting position were a statement? What strength the difference between index and subscript? The sum nor the leftmost character position and does length must not made the total length form the character item. Shown at or of cobol specification was slated to newspaper to get rid once the way.
    [Show full text]
  • Netinfo 2009-06-11 Netinfo 2009-06-11
    Netinfo 2009-06-11 Netinfo 2009-06-11 Microsoft släppte 2009-06-09 tio uppdateringar som täpper till 31 stycken säkerhetshål i bland annat Windows, Internet Explorer, Word, Excel, Windows Search. 18 av buggfixarna är märkta som kritiska och elva av dem är märkta som viktiga, uppdateringarna finns för både servrar och arbetsstationer. Säkerhetsuppdateringarna finns tillgängliga på Windows Update. Den viktigaste säkerhetsuppdateringen av de som släpptes är den för Internet Explorer 8. Netinfo 2009-06-11 Security Updates available for Adobe Reader and Acrobat Release date: June 9, 2009 Affected software versions Adobe Reader 9.1.1 and earlier versions Adobe Acrobat Standard, Pro, and Pro Extended 9.1.1 and earlier versions Severity rating Adobe categorizes this as a critical update and recommends that users apply the update for their product installations. These vulnerabilities would cause the application to crash and could potentially allow an attacker to take control of the affected system. Netinfo 2009-06-11 SystemRescueCd Description: SystemRescueCd is a Linux system on a bootable CD-ROM for repairing your system and recovering your data after a crash. It aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the partitions of the hard disk. It contains a lot of system tools (parted, partimage, fstools, ...) and basic tools (editors, midnight commander, network tools). It is very easy to use: just boot the CDROM. The kernel supports most of the important file systems (ext2/ext3/ext4, reiserfs, reiser4, btrfs, xfs, jfs, vfat, ntfs, iso9660), as well as network filesystems (samba and nfs).
    [Show full text]
  • Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO
    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO..........................................................................................................................................1 Martin Hinner < [email protected]>, http://martin.hinner.info............................................................1 1. Introduction..........................................................................................................................................1 2. Volumes...............................................................................................................................................1 3. DOS FAT 12/16/32, VFAT.................................................................................................................2 4. High Performance FileSystem (HPFS)................................................................................................2 5. New Technology FileSystem (NTFS).................................................................................................2 6. Extended filesystems (Ext, Ext2, Ext3)...............................................................................................2 7. Macintosh Hierarchical Filesystem − HFS..........................................................................................3 8. ISO 9660 − CD−ROM filesystem.......................................................................................................3 9. Other filesystems.................................................................................................................................3
    [Show full text]
  • Process Scheduling
    PROCESS SCHEDULING ANIRUDH JAYAKUMAR LAST TIME • Build a customized Linux Kernel from source • System call implementation • Interrupts and Interrupt Handlers TODAY’S SESSION • Process Management • Process Scheduling PROCESSES • “ a program in execution” • An active program with related resources (instructions and data) • Short lived ( “pwd” executed from terminal) or long-lived (SSH service running as a background process) • A.K.A tasks – the kernel’s point of view • Fundamental abstraction in Unix THREADS • Objects of activity within the process • One or more threads within a process • Asynchronous execution • Each thread includes a unique PC, process stack, and set of processor registers • Kernel schedules individual threads, not processes • tasks are Linux threads (a.k.a kernel threads) TASK REPRESENTATION • The kernel maintains info about each process in a process descriptor, of type task_struct • See include/linux/sched.h • Each task descriptor contains info such as run-state of process, address space, list of open files, process priority etc • The kernel stores the list of processes in a circular doubly linked list called the task list. TASK LIST • struct list_head tasks; • init the "mother of all processes” – statically allocated • extern struct task_struct init_task; • for_each_process() - iterates over the entire task list • next_task() - returns the next task in the list PROCESS STATE • TASK_RUNNING: running or on a run-queue waiting to run • TASK_INTERRUPTIBLE: sleeping, waiting for some event to happen; awakes prematurely if it receives a signal • TASK_UNINTERRUPTIBLE: identical to TASK_INTERRUPTIBLE except it ignores signals • TASK_ZOMBIE: The task has terminated, but its parent has not yet issued a wait4(). The task's process descriptor must remain in case the parent wants to access it.
    [Show full text]
  • Wikipedia: Design of the FAT File System
    Design of the FAT file system A FAT file system is a specific type of computer file system architecture and FAT a family of industry-standard file systems utilizing it. Developer(s) Microsoft, SCP, IBM, [3] The FAT file system is a legacy file system which is simple and robust. It Compaq, Digital offers good performance even in very light-weight implementations, but Research, Novell, cannot deliver the same performance, reliability and scalability as some Caldera modern file systems. It is, however, supported for compatibility reasons by Full name File Allocation Table: nearly all currently developed operating systems for personal computers and FAT12 (12- many home computers, mobile devices and embedded systems, and thus is a bit version), well suited format for data exchange between computers and devices of almost FAT16 (16- any type and age from 1981 through the present. bit versions), Originally designed in 1977 for use on floppy disks, FAT was soon adapted and FAT32 (32-bit version used almost universally on hard disks throughout the DOS and Windows 9x with 28 bits used), eras for two decades. Today, FAT file systems are still commonly found on exFAT (64- floppy disks, USB sticks, flash and other solid-state memory cards and bit versions) modules, and many portable and embedded devices. DCF implements FAT as Introduced 1977 (Standalone the standard file system for digital cameras since 1998.[4] FAT is also utilized Disk BASIC-80) for the EFI system partition (partition type 0xEF) in the boot stage of EFI- FAT12: August 1980 compliant computers. (SCP QDOS) FAT16: August 1984 For floppy disks, FAT has been standardized as ECMA-107[5] and (IBM PC DOS 3.0) ISO/IEC 9293:1994[6] (superseding ISO 9293:1987[7]).
    [Show full text]
  • HP Decnet-Plus for Openvms Decdts Management
    HP DECnet-Plus for OpenVMS DECdts Management Part Number: BA406-90003 January 2005 This manual introduces HP DECnet-Plus Distributed Time Service (DECdts) concepts and describes how to manage the software and system clocks. Revision/Update Information: This manual supersedes DECnet-Plus DECdts Management (AA-PHELC-TE). Operating Systems: OpenVMS I64 Version 8.2 OpenVMS Alpha Version 8.2 Software Version: HP DECnet-Plus for OpenVMS Version 8.2 HP DECnet-Plus Distributed Time Service Version 2.0 Hewlett-Packard Company Palo Alto, California © Copyright 2005 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group. Printed in the US Contents Preface ............................................................ vii 1 Introduction to the HP DECnet-Plus Distributed Time Service 1.1 DECdts Advantages . ........................................ 1–2 1.1.1 Applications Support ...................................... 1–2 1.1.2 External Time-Provider Support ............................
    [Show full text]
  • Dose-Adjusted Epoch and Rituximab for the Treatment of Double
    Dose-Adjusted Epoch and Rituximab for the treatment of double expressor and double hit diffuse large B-cell lymphoma: impact of TP53 mutations on clinical outcome by Anna Dodero, Anna Guidetti, Fabrizio Marino, Alessandra Tucci, Francesco Barretta, Alessandro Re, Monica Balzarotti, Cristiana Carniti, Chiara Monfrini, Annalisa Chiappella, Antonello Cabras, Fabio Facchetti, Martina Pennisi, Daoud Rahal, Valentina Monti, Liliana Devizzi, Rosalba Miceli, Federica Cocito, Lucia Farina, Francesca Ricci, Giuseppe Rossi, Carmelo Carlo-Stella, and Paolo Corradini Haematologica. 2021; Jul 22. doi: 10.3324/haematol.2021.278638 [Epub ahead of print] Received: February 26, 2021. Accepted: July 13, 2021. Citation: Anna Dodero, Anna Guidetti, Fabrizio Marino, Alessandra Tucci, Francesco Barretta, Alessandro Re, Monica Balzarotti, Cristiana Carniti, Chiara Monfrini, Annalisa Chiappella, Antonello Cabras, Fabio Facchetti, Martina Pennisi, Daoud Rahal, Valentina Monti, Liliana Devizzi, Rosalba Miceli, Federica Cocito, Lucia Farina, Francesca Ricci, Giuseppe Rossi, Carmelo Carlo-Stella, and Paolo Corradini. Dose-Adjusted Epoch and Rituximab for the treatment of double expressor and double hit d fuse large B-cell lymphoma: impact of TP53 mutations on clinical outcome. Publisher's Disclaimer. E-publishing ahead of print is increasingly important for the rapid dissemination of science. Haematologica is, therefore, E-publishing PDF files of an early version of manuscripts that have completed a regular peer review and have been accepted for publication. E-publishing of this PDF file has been approved by the authors. After having E-published Ahead of Print, manuscripts will then undergo technical and English editing, typesetting, proof correction and be presented for the authors' final approval; the final version of the manuscript will then appear in a regular issue of the journal.
    [Show full text]
  • GOTOHELL.DLL: Software Dependencies and The
    GOTOHELL.DLL Software Dependencies and the Maintenance of Microsoft Windows Stephanie Dick Daniel Volmar Harvard University Presented at “The Maintainers: A Conference” Stephens Institute of Technology, Hoboken, NJ April 9, 2016 Abstract Software never stands alone, but exists always in relation to the other soft- ware that enables it, the hardware that runs it, and the communities who make, own, and maintain it. Here we consider a phenomenon called “DLL hell,” a case in which those relationships broke down, endemic the to Mi- crosoft Windows platform in the mid-to-late 1990s. Software applications often failed because they required specific dynamic-link libraries (DLLs), which other applications may have overwritten with their own preferred ver- sions. We will excavate “DLL hell” for insight into the experience of modern computing, which emerged from the complex ecosystem of manufacturers, developers, and users who collectively held the Windows platform together. Furthermore, we propose that in producing Windows, Microsoft had to balance a unique and formidable tension between customer expectations and investor demands. Every day, millions of people rely on software that assumes Windows will behave a certain way, even if that behavior happens to be outdated, inconvenient, or just plain broken, leaving Microsoft “on the hook” for the uses or abuses that others make of its platform. Bound so tightly to its legacy, Windows had to maintain the old in order to pro- mote the new, and DLL hell highlights just how difficult this could be. We proceed in two phases: first, exploring the history of software componenti- zation in order to explain its implementation on the Windows architecture; and second, defining the problem and surveying the official and informal means with which IT professionals managed their unruly Windows systems, with special attention paid to the contested distinction between a flaw on the designer’s part and a lack of discipline within the using community.
    [Show full text]
  • Netware 6 Server Management CHAPTER 3
    04 9814 ch03.qxd 8/19/04 9:32 AM Page 165 CHAPTER 3 NetWare 6 Server Management CHAPTER 3 This chapter covers the following testing objectives for Novell Course 3004: Novell Network Management: . Use NetWare Remote Manager . Identify What iMonitor Is and How to Use It . Use iMonitor to Diagnose and Repair eDirectory Problems . Set Up and Configure NSS . Monitor, Manage, and Rebuild NSS Storage Space . Set Up SMS for SBCON and NWBACK32 . Back Up Data with SBCON and NWBACK32 . Restore Data with SBCON and NWBACK32 Novell is directing the construction of the world’s central information super- highway with the help of you, me, and thousands of other electronic transit workers (orange vest optional). NetWare 6 further revolutionizes Novell’s oneNet strategy with the introduction of Web-enabled administration tools, highly scalable networking protocols, and multiprocessor support. Implementing these components makes your job easier and provides your users with more reliable network access. Welcome to anytime, anywhere advanced administration via NetWare 6. As a network administrator, it’s your responsibility to focus on the NetWare 6 network to ensure that it stays fine-tuned and in peak condition. In Chapter 1, “NetWare 6 Installation,” and Chapter 2, “NetWare 6 Upgrade and Migration,” we began our NetWare 6 CNE journey by building the cor- nerstone of your network—the NetWare 6 server. Now it’s time to super- charge the network. 04 9814 ch03.qxd 8/19/04 9:32 AM Page 166 166 PART I Novell Network Management for NetWare 6 This chapter focuses on three key areas related to managing your NetWare 6 server: .
    [Show full text]