Search

This paper proposes a new approach, called file concealer (FC), to conceal files in a computer system. FC modifies metadata about a file in NTFS (New Technology File System) to hide the file. Unlike traditional hooking methods which can be easily detected by antivirus software, experimental results show that it is difficult for antivirus software to detect the files hidden by FC. Moreover, to enhance the concealment capability of FC, FC also rearranges the order of some data sectors of a hidden file. As a result, even if another person finds the original sectors used by the hidden file, it is difficult for him to recover the original content of the hidden file. Experimental results show that even data recovery tools cannot restore the content of a hidden file. All information that is required to restore a hidden file is stored in a file, called recovery file hereafter. When a user uses FC to hide a file, the user can specify any file as a host file, such as an image file, to which the recovery file will be appended. As a result, the user can easily restore a hidden file; however, it is difficult for other person to detect or restore the hidden file and the related recovery file.

According to the intelligence of the malicious code to extract the executable file in physical memory is emerging as an import researh issue. In previous physical memory studies on ex ecutable file extraction which is targeting running files, they are not extracted as same as original file saved in disc. Therefore, we need a method that can extract files as same as original one saved in disc and also can analyze file-information loaded in physical memory.In this paper, we provide a method that executable file extract ion by analyzing information of Windows kernel file object. Also we analyze the characteristic of physical memory loaded fi le data from the experiment and we demonstrate superiority because the suggested method can effectively extract more of or iginal file data than the existing method.Keywords: Physical Memory Forensic, File Mapped Data, File Object I.서 론 최근 디지털 포렌식 연구에서는 하드디스크를 이 접수일(2014년 8월 6일), 수정일(2014년 9월 11일) 게재확정일(2014년 9월 12일)†주저자, k-dupe@nate.com‡교신저자, hhu@ensec.re.kr(Corresponding author)

File Allocation Table (FAT)file system is the most common file system used in embedded devices such as smart phones, digital cameras, smart TVs, tablets, etc. Typically these embedded devices use Solid State Drives (SSD) as storage devices. The ExFAT file system is future file system for embedded devices and it is optimal for SSDs. This paper discourses the methodologies for Geotagging as a file system metadata instead of file data in FAT and ExFAT file systems. The designed methodologies of this paper adheresthe compatibility with the FAT file system specification and existing ExFAT file system implementations. Keywords Cluster, Contiguous, ExFAT, EXIF, FAT, File system, Flash memories, GPS, MMC, Multimedia, Micro SD, NAND, NOR, SSD,Storage, Video, XMP. 1. INTRODUCTION The Multimedia Cards (MMC) [1]/ Secure Digital (SD) [2] / Micro SD cards are composed of NOR and/or NAND flash memories [3]. The NOR and NAND flash memories are also called as “Solid State Drives”. The Flash memories are default choice of any embedded device as they are low-priced, smaller size and higher storage capacity.The FAT [4] file system is the widely adopted file system in SSDs. The multi-media applications such as video imaging, audio/video playback and recording uses FAT file system for storing and retrieving the data of the multimedia files. The first version of FAT file system was FAT12 by Microsoft Corporation, later it was extended as FAT16 and further as FAT32 to support higher storage capacity. The FAT file system was initially developed to use on floppy disks and Hard Disk Drive (HDD) s. Since most of the operating systems of Personal Computer (PC) s such as Windows, Linux, Mac OS, etc. implement the FAT file system, this file system has become a default and world-wide compatible storage format for embedded devices. Usually the device with the implementation of FAT is recognized as removable storage media in a PC. Even though FAT file system does not define flash management techniques such as Wear-Levelling and Bad Block management [4], the embedded devices implements this file system along with the dedicated flash block management algorithms. In FAT File system, the storage device is represented as group of linear clusters. A cluster is basic unit of data storage in FAT file system and it is a group of blocks or sectors of storage device. In FAT file system, the file or directory is a linked list of the clusters. The File Allocation Table stores the status of all available clusters of the device; Status of a cluster can be either allocated as part of file/directory data or free or reserved. An every entry of File Allocation Table indicates the status of corresponding cluster. The FAT file system specification limits the maximum supported storage size to 32 GB. But, the maximum size supported by FAT32 implementation is 128 GB. But, today the flash storage cards of more than 32 GB are available in market. The ExFAT [5] [6] file system is developed, by Microsoft Corporation, as successor of FAT32 file system. This file system is optimally designed to support large size flash storage cards with higher read and write performance. The maximum storage size supported by ExFAT file system in 128 peta bytes (PB). Global PositioningSystem (GPS) based positioning [7][8]is the positioning technique commonly used inSmartphones. Most of Smartphone contains the GPS receiver which continuously receives the signals from the satellites. These satellite signals contain the exacttime of the message sent, and the location information. The GPS receiver usesthe received signals of four or more satellites to determine the current position based on trilateration.Many smart phones uses the multiple sensors improve the accuracy of the GPS position [9]. In Android based mobile phones, Location Manger [10] can be used for the Geotagging of multimedia files. The eXtensible Metadata Platform (XMP) [11] and Exchangeable image file format (EXIF) [12] are the formats used to store the geographical coordinates and other related information in multimedia and Portable Document Format (PDF) files. In both XMP and EXIF formats, the Geographical data is always placed as multimedia file data. Due to this, file need to be opened and read operation is required to retrieve the geographical location of the file. This paper designs the techniques to place the geographical data of the file as attribute of the file instead of user data of the file. In FAT and ExFAT file systems, the attribute of the file contains the file name, size in bytes, date and time of creation and last write. The attribute of the file is referred as Meta data of the file. This paper includes the geographical data to the attribute of the file/directory by following methodologies. i) Geotagging with Reserved Sectors of FAT and ExFAT file systems. ii) Geotagging with Reserved Clusters of FAT file systems. The files created/updated with above techniques adheres the compatibility with the existing FAT and ExFAT file system implementations and specifications. This means, files created with Geographical data as attributes are accessible for read and write operations in other FAT and ExFAT file system implementations without Geotagging facility. The Geotagging methodologies described in this paper stores the geographical

log file shows the behavior of user when they access the website. It is in text format and automatically generated by web server whenever user accesses the website. Entry of particular web page with date, time, cs-method, cs-uri-stem and other information is generated automatically in text file for every access of web page. Web Usage Mining is different mining technique apply on weblog file to discover the different pattern which is useful for efficient design of website, performance enhancement of server etc. Mining of web log file consist of three steps Data Preprocessing, Pattern Discovery and Pattern Analysis. Data preprocessing task convert the web log file in database by applying data extraction, data storage and data cleaning technique. In existing technique data extraction from the log file is perform line by line and store in multidimensional array and then extracted data field will be store in database and then data cleaning is performed. In this research paper, a new technique is being proposed for Data Preprocessing of web log using Microsoft Excel. The experimental results show that the proposed new technique using Microsoft excel file is an effective compare to existing technique.

Because the Excel file is often edited, the data blocks stored in the hard disk which make up the Excel file is often not continuous. Discontinuous storage fragmented files, deleted or formatted, with the current data recovery software to restore the effect is very poor, often file recovery, but can not open or is garbled. Therefore it makes sense to study an effective recovery method to recover Excel fragmented files. Based on "Laura" file format, first introduced the Windows platform fragmented files, and then given an Excel file fragmentation recognition method, final based on debris identify given Excel file fragmentation restructuring.

Based on the analysis of the structure of the 3DS file, this paper uses recursive method to collect content of 3DS file and designs the data structure to save them. Then, reading and drawing principle for 3DS file is studied by DirectX 11. Finally, the system for reading and drawing 3DS file is designed and implemented based on DirectX11 in VS2010, and achieves better results.

This paper discusses about types of file structures in Linux, points out that EXT2 is the most commonly used file system in Linux, analyzes the disk layout, index point and directory structure of EXT2, and studies the method to access files in EXT2 by name, which makes the access faster and more efficient.

This chapter describes the details of SCION configuration files. All SCION configuration files are represented in JSON [42] format.

operating system, various objects are existed which are graphically shown to the users on his/her operating system. Each object has a security attributes that identifies its access control list. This list has an entry for each system user with access privileges. Reading the files (or all the files in a directory), writing the file or files and execute the file or files (if it is an executable file, or program) are most common privileges included. Thus, an Access Control List (ACL) is a table that tells a computer which user has to given the access rights for a particular system object, such as a file directory or individual file. Each operating system uses the access control list but in different manner. Linux operating system is based on the POSIX ACL and Windows O/S (Microsoft Windows NT/2000) is based on the ACL. This paper presents the analysis of Linux POSIX ACL and the Windows ACL, based on the various parameters.

When theft of a physical item occurs it is detectable by the fact that the object is missing, however, when the theft of a digital item occurs it can go unnoticed as exact replicas can be created. The original file is left intact but valuable information has been absconded. One of the challenges facing digital forensic examiners is detecting when files have been copied off of a computer system in some fashion. While certain methods do leave residual evidence behind, CD Burning has long been held as a copying method that cannot be identified. Through testing of the burning process and close examination of the New Technology File System (NTFS), artifacts from the master file table in the various versions of Microsoft Windows, markers have been found that are associated with copying or “burning” files to CD or DVD. Potential evidence that was once overlooked may now be detectable.

FastDu is a file system service that tracks file system changes by intercepting file system calls to maintain directory summaries, which play important roles in both storage administration and improvement of user experiences for some applications. In most circumstances, directory summaries are independently harvested by applications via traversing the file system hierarchy and calling stat () on every file in each directory. For large file systems, this brute-force traverse-based approach can take many hours to complete, even if only a small percentage of the files have changed. This paper describes FastDu, which uses a pre-built database to store harvested directory summaries, and tracks the file system changes by intercepting file system calls, so that new harvesting is restricted to the small subset of directories that contain modified files. Tests using FastDu show that this approach reduces the time needed to get a directory summary by one or two orders of magnitude with almost negligible penalty to application-aware file system performance.

ARM is the newest 32-bite RISC microprocessor. Its high performance, low power consumption and flexible extension make ARM particularly suitable for designing embedded system. Therefore, the realization of the FAT16 file system with ARM can satisfy the demand of file storage in embedded system. This article descripts the simple realization of FAT16 file system with ARM 7.

HFS+ file system is a file system of the Mac OS. In order to achieve data manipulation of the file system based on the Windows OS for further computer forensics, not only do we introduce the principle and structure of HFS+ file system, but also propose a efficient method to analyze the file system. Research contains the exploration of the file system and program implementation to analyze the file system.

This paper designs file security function on Windows O.S. Whenever you use Windows O.S, you need to protect some file data. This paper designs these security protection functions. This paper proposes two security functions on Windows O.S. One is file security. The other is directory access protection. To check the proposed functions well, I experiment the above functions on the Windows O.S. By this experiment, I confirmed that the proposed function worked well. The Computer is inevitable thing in our life. The most important thing in computer system is file management. It is very important to keep file safe. Safe file management has become important technology as increasing use of computer system. This paper designs file and directory security in Windows O.S. Windows O.S is used in the world-wide computer system. The important files should be kept safe in Windows O.S. This paper designs file and directory protection function in Windows O.S. The function suggested in this paper is composed of the file security and the indicated directory protection. The suggested file security function is storing encrypting file using encryption algorithm so that cannot access it by unpermitted people. The encrypted file is read by decrypting it. This is designed and implemented user friendly interface. This paper experiments encryption and decryption function of the proposed program normally. I experiment also decrypt or not in case of incorrect password. This paper has also directory protection function in Windows O.S. I design directory access control of Windows O.S. The suggested directory access control function protects directory access from unpermitted people by directory access permission. I experiment also the suggested directory access. I confirmed the suggested directory access is working well. This paper is composed of chapter 5. Chapter 2 is related research, Chapter 3 is designed Windows O.S security function. Chapter 4 is experiment and evaluation. Chapter 5 is conclusion.

In Windows operating systems, a long file name (VFAT entry) may or may not be generated for a file name which is short (8.3). For recent versions of Windows this depends upon the capitalization of the name and extension. A description of when and how this is done is given. The forensics implications of this are discussed.

A style sheet file for use in the EndNote citation software. This file has been tested with versions X4 to X7.

Files missing in file system often results in serious consequences. To solve this problem on Microsoft Windows, the file recovery solutions in FAT32 was proposed. File system structure in FAT32 was introduced. The specific processes of DBR recovery in FAT32 were illustrated. On the basis of file storage features in FAT32, an available recovery scheme about the deleted files was analyzed and proposed.

The File Allocation Table (FAT) file system is widely used file system in tablet personal computers, mobile phones, digital cameras and other embedded devices for data storage and multi-media applications such as video imaging, audio/video playback and recording. The FAT file system is not power fail-safe. This means that, the uncontrolled power loss or abrupt removal of storage device from computer/embedded system causes the file system corruption. The TFAT (Transaction safe FAT) file system is an extension of FAT file system to provide power fail-safe feature to the FAT file system. This paper explores the design methodologies of cluster allocation algorithms of TFAT file system by conducting various combinations of file system operations in Windows CE (Compact Embedded) 6.0 Operating System (OS). This paper also records the performance bench-marking of TFAT file system in comparison with FAT File system.

In this research, we designed and implemented Real-World File System (RWFS), which can manage files as if we can put them onto or pick them up from the places of the real world. RWFS regards the places of the real world as directories of the file system by associating a directory with a place. We create directories called Real-World Directory (RWD) which forms a hierarchical structure to reflect the natural property of places. In addition to the conventional access rights of read, write, and execute as implemented in other file systems, RWFS accommodates utilizing location information of the target user in access rights; RWFS can decide whether or not the user can access to a particular file or directory based on the user's location. Therefore, accessible files for a user change depending on the user's location. This mechanism enables creating information that can be read or written by users who physically stay at a particular place. We evaluated this system by measuring turnaround time to operate the file system together with simulation.

In the era of Big Data, one single directory can contain tens of thousands or even millions of files. Directory update methods employed by traditional POSIX-compliant file systems do not adapt well to wide-area network and could lead to large amount of unnecessary bandwidth consumption due to their full cache invalidation approaches. In traditional file systems, if there is a small fraction of changes in a directory (e.g. Renaming a file), the whole cache of the directory metadata must be discarded and a new copy will be obtained from server, resulting in poor performance in low bandwidth environment. In this paper, we propose a directory metadata update strategy, which partitions metadata into blocks, and only transfers modified block(s) over the network to reduce transmission time. We implement a proof-of-concept prototype using the FUSE user space file system to verify the effectiveness of our approach. Results show that for a directory with directory entries size of 5MB, update time for small changes in a directory can be roughly reduced by a factor of 20.

We collect and analyze a snapshot of data from 10,568 file systems of 4801 Windows personal computers in a commercial environment. The file systems contain 140 million files totaling 10.5 TB of data. We develop analytical approximations for distributions of file size, file age, file functional lifetime, directory size, and directory depth, and we compare them to previously derived distributions. We find that file and directory sizes are fairly consistent across file systems, but file lifetimes vary widely and are significantly affected by the job function of the user. Larger files tend to be composed of blocks sized in powers of two, which noticeably affects their size distribution. File-name extensions are strongly correlated with file sizes, and extension popularity varies with user job function. On average, file systems are only half full.

You can use the BlackBerry 10 device’s file system in order to store your application’s data and share files with other apps running on the device. This appendix gives you an overview of your application’s home directory’s structure and the corresponding directory permissions.

The Network File System (NFS) is one of the most popular remote file system protocols for accessing directories and files over the network. If NFS mount point has thousands of files (e.g. a directory containing 5000 files), there is a significant performance drop in directory browsing (traverse, open(), stat() and read()) time as compared to local file system browsing (traverse, open(), stat() and read()) time. In order to reduce the file browsing time in the NFS with single client system, this paper presents the modification of a conventional NFS protocol usage with multiple client systems. Experimental results show the proposed implementation gives 44.6% performance improvement over a conventional one.

In this paper we propose a new dynamic access control method for the computer system with frequently inserted, deleted and updated users/files. Our method, based on the concepts of the access control matrix, key-lock-pair, time stamp and Chinese remainder theorem, associates each user with a user key and a user lock and each file with a file key and a file lock. Our method can achieve the following four goals. 1.(1) By a simple modulo operation on the keys and locks of the user and the file, we can reveal the access right of a user to a file. 2.(2) When a user/file is added to the computer system, we only assign a key and a lock to the user/file without affecting the keys and locks of the other users/files in the system. 3.(3) When a user/file is deleted from the computer system, we simply erase the entry of the user/file in the computer system. 4.(4) When the access right of a user to a file is updated, we merely modify the key and lock of the user or the file without affecting the keys and locks of the other users/ files in the system. The main contribution of our method is that the action of inserting, deleting a user/file, or updating the access right of a user to a file can be done by modifying only one key and one lock, which could not be achieved simultaneously before.

In this chapter you will be introduced to the statistical program Facets and learn how to create and run a specifications file using an SPSS data set.

In today's supercomputer, most file systems provide scalable I/O bandwidth. But these systems cannot concurrent creation of millions to billions of files in a single directory. Toward exascale-era, we propose scalable metadata management method by using many metadata servers. Directory entry and inode are distributed by using consistent hashing. Directory entry and inode are stored as same MDS as possible. In many case, two request of lookup dentry and inode are merged into one request. In evaluation, our file system throughput is more than 490,000 file creates per second on 64 metadata servers and 2048 clients. Concurrent file creation time of 40 million is 42 second in a single directory.

An accessible implementation of MAC for file access is proposed. Instead of traditional but unfamiliar MAC aware tools such as secure-OSs, the security enforcement mechanism of our proposal is FSG (file server group) which is structured so that they reflect a security policy of the organization. Using ordinal file servers, it is accessible to the most of commercial office environment. We also propose the use of FCA (formal concept analysis), a technology for knowledge extraction, to derive the structure of FSG for information flow enforcement. An advantage of use of FCA is that it directly produces configuration parameters such as access points of users as the knowledge extracted from organizational security policy. The configuration of the file server group is easy to understand, and the management cost of FSG is lower than that of the ordinary flat structured file servers.

The directory management is an essential part of the file systems. The carefully designed directory's internal structures can have major impact on the performance. The modern file systems tend to support millions of files per directory and the file name indexing is a milestone. Two main approaches exist -- b-trees and hashing. The current paper proposes a modification of the b-tree which combines the features of both. It is presented the modification -- the so-called bh-tree and an approach to index and maintain the file names in a directory. The aim is fast and parallelizable management of the indexed file names.

The introduction of Jumplists in Windows 7 was an important feature from a forensic examiners viewpoint. Jumplist configuration files can provide the examiner with a wealth of information relating to file access and in particular: dates/times, Volume GUIDs and unique file object IDs relating to those files. Some of the information in the Jumplist could be used to build a more precise timeline relating to system and file usage. In this article, we analyse the structure of a Jumplist configuration file and in particular a record from a Jumplist configuration file and highlight some of the important entries therein.

By analyzing the basic principles of file encrypting system, the essay mainly research and implement the transparent encrypting file system which is based on the filter driver in the kernel driver layer. With the help of this system, not only a certain type of file can be encrypted, but the specified file or folder can also be encrypted easily and efficiently. The system applies shared memory, windows massage mechanism, I/O driver technology and the other technology to implement information synchronization and data communication between the user model and kernel made. Compared with other encrypting technologies, the file system filter driver which is based on the transparent file encrypting technology has overcome the shortcomings of several other technologies. Because it is much more closer to the kernel, it can effectively intercept any file operation. The experiment results show that the interception efficiency is higher than other file encrypting system. Besides , the system's performance is much more security and reliable.

The Knowledge File System (KFS) is a smart virtual file system that sits between the operating system and the file system. Its primary functionality is to automatically organize files in a transparent and seamless manner so as to facilitate easy retrieval. Think of the KFS as a personal assistant, who can file every one of you documents into multiple appropriate folders, so that when it comes time for you to retrieve a file, you can easily find it among any of the folders that are likely to contain it. Technically, KFS analyzes each file and hard links (which are simply pointers to a physical file on POSIX file systems) it to multiple destination directories (categories). The actual classification can be based on a combination of file content analysis, file usage analysis, and manually configured rules. Since the KFS organizes files using the familiar file/folder metaphor, it enjoys 3 key advantages against desktop search based solutions such as Google’s Desktop Search, namely 1) usability, 2) portability, and 3) compatibility. The KFS has been prototyped using the FUSE (File system in User space) framework on Linux. Apache Lucerne was used to provide traditional desktop search capability in the KFS. A machine learning text classifier was used as the KFS content classifier, complimenting the customizable rule-based KFS classification framework. Lastly, an embedded database is used to log all file access to support file-usage classification.

In some situation, it's necessary to store a whole folder into a database and provide random access to any file in it. This paper puts forward a new method to store a folder as a whole and access its file randomly in a database based on the integration of BLOB, Stream and Serialization technology. First, the folder is packed up, resulting in a file stream and a directory structure object. Then, the directory structure object is serialized to a directory structure stream. Finally, the file stream and directory structure stream are saved as BLOB data in a database respectively. When reading from the database, we first read the directory structure BLOB data as a stream, and deserialize it to the directory structure object. Then, with the information in the directory structure object, we can choose which file to access and ascertain its location and size in the folder's file BLOB data. Finally, we read the corresponding data section out of the database and realize the random access of a file.

Two file-based methods can be employed for distributing RemoteApp programs to users. The first is to create a Windows Installer package file (.msi), which can then be distributed and installed in a manner like traditional locally installed programs. The second is to create a Remote Desktop Protocol file (.rdp) that launches the remote application without the need to perform an install. Terminal Services allows for the easy creation of a Windows Installer package file, commonly referred to as an .msi file. This method installs the RemoteApp to appear like a conventional local installation. The method is chosen by users who want to make the virtualization aspect of the RemoteApp program nearly invisible to end users. Once the .msi file is created, one can distribute it to an enterprise via existing distribution methods, such as Microsoft System Center Configuration Manager or through an Active Directory Group Policy Object. Terminal Services has its own file type for running a RemoteApp program that Windows recognizes and treats appropriately. The file type is .rdp, which stands for Remote Desktop Protocol. This is a standalone executable that can be accessed from a simple file share or dropped on a client PC.

Nowadays more and more applications require file systems to efficiently maintain million or more files. How to provide high access performance with such a huge number of files and such large directories is a big challenge for cluster file systems. Limited by static directory structures, existing file systems will be prohibitively inefficient for this use. To address this problem, we present a scalable and adaptive metadata management system which aims to maintain a trillion files efficiently. Firstly, our system exploits an adaptive two-level directory partitioning based on extendible hashing to manage very large directories. Secondly, our system utilizes fine-grained parallel processing within a directory and greatly improves performance of file creation or deletion. Thirdly, our system uses multiple-layered metadata cache management which improves memory utilization on the servers. And finally, our system uses a dynamic loadbalance mechanism based on consistent hashing which enables our system to scale up and down easily.Our performance results on 32 metadata servers show that our user-level prototype implementation can create more than 74 thousand files per second and can get more than 270 thousand files' attributes per second in a single directory with 100 million files. Moreover, it delivers a peak throughput of more than 60 thousand file creates/second in a single directory with 1 billion files.

This chapter will take you on a tour of the Snow Leopard file system to discover what items exist in what folders and why (and also what you can and shouldn’t change and why). We’ll cover in depth The overall file structure of Snow Leopard Your personal Home folder and its contents The top-level folders, including the System folder, the Library folder, and the Applications folder Other common folders Hidden folders

So far, every project we’ve talked about has had all its source code crammed into its main.m file. The main() function and all the @interface and @implementation sections for our classes are piled into the same file. That structure’s fine for small programs and quick hacks, but it doesn’t scale to larger projects. As your program gets bigger, you’ll have a ponderous file to scroll through, making it harder to find stuff. Back in your school days (assuming you’re finished with them), you didn’t put every term paper into the same word processing document (assuming you had word processors). You kept each paper in its own document, with a descriptive name. Likewise, it’s a good idea to split your program’s source code into multiple files, and you can give each one a helpful name. Compartmentalizing your program into smaller files gives you a chance to find important bits of code more quickly, and it helps others get a quick overview when they look at your project. Putting your code in multiple files also makes sending the source for an interesting class to a friend easier: you just pack up a couple of files rather than your entire project. In this chapter, we’ll discuss strategies and ideas for keeping various bits of your program in separate files.

Identifying file type by file extension is fallible. Another magic bytes method for these files, which have similar header information, such as the common-used MS Office OLE file, may not distinguish one type from another. In this paper, an efficiently classification method for the common OLE files was proposed. In order to overcome the shortcoming of the original N-gram analysis technique which can not easily tell ambiguous file types apart, the N-gram analysis and the vector space model were combined together to identify the common OLE files. The characteristic items were extracted from the most frequency byte values of each file class, and then the cosine value of two vectors was used to catalogue ambiguous file types. The experiment results demonstrate that our mechanism is effective in identifying the office OLE files, and obtain better performance than the common n-gram method.

Parallel file systems are widely used in clusters to provide high performance I/O. However, most of the existing parallel file systems are based on UNIX-like operating systems. We use the Microsoft .NET framework to implement a parallel file system for Windows. We also implement a file system driver to support existing applications written with Win32 APIs. In addition, a preliminary MPI-IO library is also developed. Applications using MPI-IO could achieve the best performance using our parallel file system, while the existing binaries could benefit from the system driver without any modifications. In this paper, the design and implementation of our system are described. File system performance using our preliminary MPI-IO library and system driver is also evaluated. The results show that the performance is scalable and limited by the network bandwidth.

XML is the predominant format for representing structured information inside documents, but it stops at the level of files. This makes it hard to use XML-oriented tools to process information which is scattered over multiple documents within a file system. File System XML (FSX) and its content integration provides a unified view of file system structure and content. FSX's adaptors map file contents to XML, which means that any file format can be integrated with an XML view in the integrated view of the file system.

This chapter focuses on what drivers do and how they work with Microsoft Windows and with Remote Installation Services. The starting point for adding driver support to Remote Installation Services image is to identify the hardware devices for which one needs to add support. One way of identifying computer devices is to perform a standard, manual CD-based Microsoft Windows installation on the computer, and then just see what happens. One can then identify the unsupported devices appearing as being unavailable devices in the Microsoft Windows Device Manager. An easier way to work around identifying unknown devices is to simply turn on the computer and start it up with its preinstalled operating system. A driver basically consists of two files: the system information file (.inf), the actual driver binary file (.sys). Other files might be included in a driver build, but the system information file and driver binary file are really the most important files. The system information file is essentially a text file.