Showing papers on "Windows NT published in 2003"

The Integrated Networks Model: Explaining Resource Allocations in Network Markets

Abstract: The last decade has witnessed a shift from a focus on the value created by a single firm and product to an examination of the value created by networks of firms (or product ecosystems) in which assets are comingled with external entities. The authors examine these market-based assets in the context of network markets and propose an Integrated Networks model in which three types of networks—user, complements, and producer—add value or enhance the attractiveness of the associated focal product. The authors empirically test the proposed model by surveying information technology professionals on their resource allocation decisions regarding the Unix and Windows NT operating systems. The findings suggest that the value added by these three networks is significantly and positively associated with resources allocated by business customers to competing products. The results also show that the three networks mediate the relationship between stand-alone product performance and resource allocation.

Control Techniques and Programming Issues for Time Delayed Internet Based Teleoperation

Abstract: This article focuses on Internet-based real time control, such as remote bilateral teleoperation. In such applications, it is required that the control loop be closed through a time delayed network. This paper focuses on two control strategies (based on wave variables and a time forward observer), bandwidth issues, and some related programming details. Experimental results of bilateral teleoperation via the Internet between Atlanta and Tokyo are given. The system used is a two-degree-of-freedom haptic interface, bilaterally coupled to a simulation (implemented on a windows NT based computer) of a similar system.

Using Samba

Abstract: From the Publisher: Using Samba, which has been officially adopted by the Samba Team and is under the GNU Free Documentation License (FDL), is a comprehensive guide to Samba administration. The current edition focuses on Samba 2.2 and covers the most important features of 3.0, which was under development as this book went to print. Samba is a cross-platform triumph: it turns a Unix or Linux system into a file and print server for Microsoft Windows network clients. Samba is so robust, flexible, fast, and secure that many people are choosing it over Windows NT/2000/XP for their file and print services. Samba is also free software, licensed under the GNU General Public License. This book will help you make file and print sharing as robust, powerful, and efficient as possible. The authors delve into the internals of the Windows activities and protocols to an unprecedented degree, explaining the strengths and weaknesses of each feature in Windows domains and in Samba itself. Using Samba takes you from basic installation and configuration -- on both the client and server side, for a wide range of systems -- to subtle details of security, cross-platform compatibility, and resource discovery that make the difference between whether a user sees the folder they expect or a cryptic error message. The range of this book knows few bounds. Wondering how to integrate Samba's authentication with that of a Windows PDC? How to get Samba to serve Microsoft Dfs shares? How to share files on Mac OS X? These and a dozen other issues of interest to system administrators are covered. A whole chapter is dedicated to troubleshooting. Whether you're playing on one note or a full three-octave range, on your personal computer or an enterprise network, Using Samba will give you an efficient and secure server.

Inside Windows Storage: Server Storage Technologies for Windows 2000, Windows Server 2003 and Beyond

Abstract: From the Book: Gordon Moore, Intel's co-founder once observed that the density of transistors per square inch was doubling every year. Subsequently, the pace dropped a little and the doubling was perceived to be once every 18 months instead of once every 12 months. According to industry analysts, the enterprise storage industry is still beating Moore's law in its growth. One estimate is that in the next few years, more data will be generated than what was ever created from the entire dawn of known history! Regardless of the exact role, one must concede that Windows servers have an important role to play in the enterprise storage industry. Knowledge of the storage aspects of the Windows operating system will prove to be invaluable in this situation. This book is a humble attempt to meet this perceived need. A word or two about the conventions used in this book would be helpful. The book uses the phrases "Windows NT" and "Windows Server family" interchangeably. Both are used when some feature that is common across all of Windows NT 4.0, Windows 2000 and Windows Server 2003 are being discussed. When needed, a particular version of the operating system is mentioned e.g. Windows 2000 or Windows Server 2003 and these refer to particular versions of the operating system rather than the operating system in a generic sense. This book has been written for the person somewhat conversant with computers systems and the IT industry that is looking to further his/her knowledge about the storage industry in general and Windows NT architecture details as they apply to storage devices. To be clear, this book is about enterprise storage, and consumer storage details are described cursorily, if at all. The bookattempts to strike a balance between catering to the software professional who knows nothing about storage and the professional somewhat conversant with storage, but looking for some good insights of Windows NT storage architecture. If the reader comes away with just one idea after reading this book, that idea is intended to be a deep appreciation of the steady acceleration of enterprise storage related features that each succeeding release of the Windows NT operating system has and will bring to market. This book attempts to strike a balance between the following aspects: Making information available on a timely basis. Providing detailed information and respecting intellectual property rights. The book covers a number of Software Development Kits (SDKs) that are only available under a Non Disclosure Agreement (NDA) basis. Hence the coverage of these has been necessarily limited to what is already publicly available information. The author has erred on the side of caution and preferred to provide only that information the author is certain is publicly available, but has added value to this often cryptic and difficult to locate information by providing the necessary explanations. Provide information on upcoming Windows NT releases and not just "stale" information about the past Windows NT releases. Such forward looking information is necessary in order to appreciate the clear focus Microsoft has devoted to enterprise storage in the Windows NT operating system. The obvious risk is that plans are subject to change. The book clearly mentions when some particular aspect is related to forthcoming Windows NT releases. A word of caution is in order book makes some forwarding looking statements in the form of expected features in forthcoming releases of the Windows NT operating systems. Microsoft has repeatedly made it clear that the only guaranteed way of identifying features in an operating system release is after the actual release. No matter what is said at trade shows, seminars, etc. there is no guarantee that some features tentatively discussed will ever ship, let alone ship with a particular version of the operating system. Hence the forward looking statements in this book are a best guess and should be treated as such. No material plans of any kind should be based upon these guesses. Any reader who does not appreciate the "Safe Harbor Statement" nature of the previous two paragraphs is highly encouraged to study (and not just read) them again. About This Book The book begins with an overview of Windows NT architecture including the Windows NT I/O sub system and storage driver architectures. This chapter is an attempt to condense the vast amount of information purveyed in the excellent books "Inside Windows NT" (Microsoft Press) and is intended for the reader that does not have the time available to peruse the book in its entirety. Chapter 2 describes Direct Attached Storage which was historically the first choice for storage. Chapter 3 describes Network Attached Storage which was the next major mile stone in enterprise storage. The Windows NT network stack is explained in detail, from the point of view of the storage professional. Chapter 4 describes Fibre Channel Storage Area Networks, a technology that is perceived to be now rapidly maturing and still holding its own in the face of upcoming new technology in the form of IP SCSI and Infiniband Chapter 5 covers the basics of backup/restore and the new Volume Shadow Copy Service (also popularly referred to as snapshots) in Windows Server 2003. Chapter 6 covers file systems and disk virtualization with particular reference to Windows NT. The chapter also discusses cluster file systems. Chapter 7 discusses storage management in general and the various storage management solutions as they apply to Windows NT. Chapter 8 covers new technologies in storage particularly IP Storage (which attempts to meld storage and IP networks) as well as Infiniband. Chapter 9 discusses Windows Server 2003 and Windows 2000 natively supported solutions to provide high availability services (including fail over, fail back, as well as load balancing) using multi ported dual HBAs in a Windows NT server. The chapter also discusses more mundane high availability and performance solutions such as RAID. While the rest of this book is organized into chapters based upon technologies, Chapter 10 is organized by Windows NT releases. Irrespective of what storage technology is being discussed, Chapter 10 traces the storage features as they appeared in Windows NT 4.0, Windows 2000 and expected features in Windows Server 2003 server and beyond. So read on, and I hope, enjoy.

Network simulation experiments manual

Abstract: The lab exercises contained in the "Network Simulation Experiments Manual" are based on the OPNET simulator (v. 9), a network simulation tool that was originally developed at M.I.T. It provides networking professionals with the option of implementing experiments from their homes or workplaces and the lab manual comes with directions for downloading the free easy-to-install software (special version to this book only - see system requirements below). These labs run through simulations closely tied to the material in the text so that you can visualize the discussions covering core network topologies. Various scenarios are presented within each topology, and review questions and a lab report exercise accompany each lab experiment. The experiments also follows the organization of "Computer Networks, Third Edition", by Larry Peterson and Bruce Davie. System requirements for using the OPNET IT Guru Academic Edition release 9.1 : Intel Pentium III, 4 or compatible (500 MHz or better); 256 MB RAM; 400 MB disk space; Display: 1024 x 768 or higher resolution, 256 or more colors; and, The English language version of the following operating systems are supported - Microsoft Windows NT (Service Pack 3, 5, or 6a), Windows 2000 (Service Pack 1 and 2 are supported but not required), and Windows XP (Service Pack 1 is required). It is written by an instructor who has used OPNET simulation tools in his classroom for numerous demonstrations and real-world scenarios. This title features software download based on an award-winning product made by OPNET Technologies, Inc., whose software is used by thousands of commercial and government organizations worldwide, and by over 500 universities. It includes useful experimentation for professionals in the workplace who are interested in learning & demonstrating the capability of evaluating different commercial networking products, i.e., Cisco routers. It covers the core networking topologies and includes assignments on the ethernet, token rings, ATM, Switched LANs, Network Design, RIP, TCP, Queuing Disciplines, QoS, etc. Instructors can download the solutions manual to the exercises in the "Network Simulation Experiments Manual" by clicking on the 'Instructors' resource link in the upper right corner of the screen and searching for author 'Aboelela'.

Method and system for central management of a computer network

Abstract: A method and system for central management of plural network clients interfaced with a network host, each network client automatically calling a login routine (20) and a start-up routine (22) associated with initiation of a login script at the network client. Configuration and start-up management can be based upon an operating system determination with several different operating systems, such as Windows 95 and Windows NT, deployed across the network. The login routine (20) can install the start-up routine (22) on the network client at login, allowing the start-up routine(22) to direct the network client to install predetermined local utilities and to load predetermined network utilities. An associated launch manager (24) can establish launch manager values to allow a network user to individualize his network client within constraints defined by computing standards established through the login routine.

User Pro ling for Intrusion Detection in Windows NT

Abstract: In User Pro ling, we observe the normal behavior of computer users and from this, seek to automatically learn models that characterize this behavior. Then for a new session, these models are used to either authenticate the login name, or to identify a malicious insider. A related problem is Program Pro ling, in which models for normal activity of an application program are learned, then used to identify attacks. This is a somewhat easier problem because humans do not come with "specs", so compared to programs, our behavior is in nitely less predictable. In fact, a certain level of anomalous activity in human behavior is inevitable and must be taken into account. Most if not all published work on this subject has used command line activity as its data source, collected on a Unix system. In this environment there are multiple ways to do most things, leaving much room for individual expression, yet even so the reported results have been less than stellar. Now consider today's point and click world, where command line activity is virtually nonexistent. Even worse, the Windows suite of interlinked applications provides a "path of least resistance", with the result that people look more alike than ever. Add to this the fact that much of the activity occurring on a host, especially if it's networked, is generated by the operating system and not user related. This requires massive ltering, but how to it accurately can be far from obvious. These considerations underscore the inherent di culty of the problem. For nearly two years we have been monitoring real users doing their daily work on an operational Windows NT network. This talk will describe the data we collect and methods we have used to analyze it, and present results obtained to date.

A multi-platform programming interface for protocol development

Abstract: We present a programming interface, called PICA, which aims to reduce the production cycle duration for communication protocols. It offers a user-friendly API that is very intuitive and that covers the major necessities which these protocols may have. Since most research is done in the Linux operating system, it also aims to reduce very significantly the time required to port a protocol implementation to other platforms like Windows NT or Windows CE by providing source code compatibility. We estimated the efficiency of our library and found that the overhead introduced is very small.

DRMonitor - a distributed resource monitoring system

Abstract: DRMonitor is a system for monitoring usage of computing resources of networked heterogeneous (Linux and Windows NT's derived) personal computers. DRMonitor is aimed to serve resource-monitoring applications and to assist load-balancing policies by providing performance and load data about each monitored machine included in the system. Through a reduced set of primitives, applications can periodically receive updated information about system usage. The paper describes available primitives, discusses some internal aspects of the monitoring system, and presents monitoring results of a classroom with 10 personal computers.

A distributed multipurpose mail guard

Abstract: We describe a mechanism for incorporating a mail guard mechanism together with automatic, mandatory, and fully transparent digital signatures and encryption for message traffic embedded into the operating system of individual network nodes. By intercepting all inbound and outbound network traffic and analyzing for pertinent information using generalized Buchi automata, the guard mechanism can enforce the application of (centralized) mail security policies without requiring any support from mail clients. An implementation based on modular modifications to the Microsoft Windows NT/2000/XP family of operating systems and OpenPGP-based messaging is described.

Watch out, Tiger Woods![golf playing robot]

Abstract: This article describes the development of an autonomous robotic system for playing mini-golf. The system was designed and built to serve as a demonstration of robotic application for engineering students. The system was built using a Yasakawa robot fitted with two arms. The software was developed to control the machine using the C++ language. Standard C++ libraries were used in addition to communication libraries provided by the Yasakawa Corporation. The current configuration works with Microsoft Windows NT and an Ethernet environment. This article describes the hardware and software design aspects of this machine.

Updating and Revision of the European Tsunami Catalogue

Abstract: The first catalogue of the European tsunamis was built in the frame of the EU Projects called GITEC, and GITEC-TWO. The catalogue was implemented as a FoxPro 2.5 database, and it can be fully used on PC with Windows 3.1 or with the first versions of Windows 95. In the present work, we describe the new version of the database that has been totally rebuilt within the Visual FoxPro 6.0 DBMS environment in order to make it suitable for the operating systems currently on the market (i.e. Windows 98, Windows 2000, Windows NT, etc.). The general structure of the previous data base version is preserved. The catalogue is accessible through a main screen containing a) functional buttons to perform the basic inquiry, and browser actions, and b) parametric, and textual data concerning a specific event that can be selected by the user. The data base has been enriched by including new tsunami entries, as the result of revision of historical sources, and by adding a new category of data, namely graphical data, such as digitised tide-gauge records, photos, relevant maps, etc., that form a special section accessible from the main screen. Moreover, the auxiliary data base of the references has been updated by introducing all the contributions, such as papers, and scientific studies that have been published in the last years.

Inside Windows Server 2003

Abstract: From the Book: The release of a new version of an operating system always brings up lots of questions. Is it worth the time and trouble to upgrade? What are the potential problems? How do I prepare for testing and evaluation and maybe for deployment? These decisions are especially complex in this situation because Windows.NET is not a revolutionary change from Windows 2000. Instead, it incorporates hundreds of improvements, large and small, that you'll need to evaluate, both separately and as a whole, to justify an upgrade. Windows.NET also represents the first time in the history of Microsoft's NT-based product line that the desktop code has been released separately from the server code. By the time.NET server products reach the market, XP will have been available for over a year. To deploy.NET servers, then, you'll need to know how to manage a complex mix of Windows.NET and Windows 2000 and NT servers accessed by any one of a half-dozen Windows clients, not to mention a wide variety of third-party clients. This book is designed to lead you through the complexities of a full Windows.NET deployment in a mixed operating environment. It starts with installing a single server and moves in logical progression through upgrading additional servers, installing hardware, handling name resolution, deploying and integrating Windows.NET DNS, installing and configuring Active Directory, and making.NET-based resources available to authorized clients, both on the local network and across the Internet. The release of Windows.NET also represents a milestone because Microsoft has finally gotten truly fanatical about security, so this book pays special attention to the new security features. Each chapteris constructed to present design principles first, followed by process descriptions that help you identify interoperability issues, and finally the procedures you'll need to install and configure the Windows.NET features covered by the chapter. Each chapter starts off with a list of new features in Windows.NET along with any significant improvements to features carried over from Windows 2000. Experienced Windows 2000 designers and administrators can use this list as a checklist to guide their evaluations. My approach to presenting process details for Windows.NET features reflects my background as a Naval nuclear power plant operator. In the nuclear program, it's not enough to know how to operate a piece of equipment. You have to know the principles behind each element of the equipment's design, how the equipment integrates into the plant as a whole, and how the equipment will affect plant operations if it fails in a variety of circumstances. I was fortunate because this experience allowed me to see how a team of operators, each with an encyclopedic knowledge of the equipment under his control, can keep complex systems running smoothly and even make the job seem easy. I hope to contribute something to your knowledge of Windows.NET so that you can build the same kind of team in your IT organization. Who Should Read This Book Any IT professional who designs, manages, or works with Windows technology should evaluate the features in Windows.NET. This book will help you with that evaluation. If you plan on installing one or more special-function Windows.NET servers, or upgrading to Windows.NET Active Directory, this book will show you how to prepare for the deployment and how to troubleshoot problems that might crop up along the way. If you have already migrated, or are in the process of migrating, to Windows 2000 and you want to know if.NET has any advantages for you, the New Features checklist at the beginning of each chapter will help guide you to the items you need for your evaluation. At a macro level, I was particularly impressed with the attention to security at all levels, especially IIS, and the improvements to Windows DNS, Active Directory replication, trust relationships between forests, the new Active Directory Migration Tool (ADMT), the integrated Resultant Set of Policy (RSoP) tools for group policy management, and the significant new features in terminal services, the Encrypting File System (EFS), Public Key Infrastructure (PKI), and the Distributed File System (Dfs). I would also call to your attention the overall improvement in performance, stability, and memory handling. It takes time and money to upgrade a large infrastructure, but with Windows.NET, you will be rewarded with a system that is fast, and handy to manage, and delivers benefits to your users in the form of speed and convenience. Who This Book Is Not For I've made the assumption throughout the book that you have experience with Windows NT servers and classic NT domains. If you have an IT background with other operating systems, and you prefer diving into the deep end of the pool when you approach a new subject, I think you'll find sufficient background explanations and references to help guide you through all but the most arcane subject areas. If you are just setting out to learn about Windows and networking technologies, this is not a good place to start. Because this is a book about.NET servers, if you are primarily concerned with deploying and managing desktops, you may want to check out one of the many books on Windows XP. If you want to know how the server-side features in Windows.NET interoperate with XP and Windows 2000 clients so you can effectively troubleshoot features such as folder redirection, offline files, group policies, resource sharing, name resolution, remote user access, certificate enrollment, EFS, and smart cards, you'll find plenty of details here. If you are primarily interested in certification on Windows.NET, most of the information you need to pass the exams is here but you may not find it arranged in a way that is conducive to exam preparation. If you want the hands-on experience to go with the paper on the wall, I think you'll benefit from the deployment format of this book as you prepare for the exams. Because of space limitations, this book does not cover the many new features of Internet Information Services (IIS) 6.0 or all the myriad aspects of application-mode terminal services. It also does not cover the interoperability features for Novell NetWare and Novell Directory Services (NDS), Services for Macintosh (SFM), or Services for Unix (SFU). Chapter 11, "Understanding Network Access Security and Kerberos," contains details of Windows.NET Kerberos interoperability with UNIX-based MITv5 Kerberos. Conventions This book uses the following typographical conventions:A new term is set in italics the first time it is introducedmd for example, Microsoft defines a site as an area of reliable, high-speed network communications. Paths for files, Active Directory objects, Registry keys and values, and group policy settings are set in fixed fontmd for example, the Hosts file is located in the \Windows\System32\Drivers\Etc folder, and DNS zone configuration information is stored in the Registry under HKLM Software Microsoft Windows NT CurrentVersion DNS Server Zones. Screen elements that are clicked, selected/deselected, checked/unchecked, opened/closed, or called out for specific attention are set in a fixed-pitch fontmdfor example, click Add to open the Add Standalone Snap-In window; or, deselect the Bridge All Site Links option to remove global transitive bridging for site links. Menu items are set in small capsmd for example, right-click the My Network Places icon and select PROPERTIES from the flyout menu. Names of graphical utilities and command-line utilities with specialized consoles are shown with an initial capital lettermd for example, the Certificates console allows you to view your personal certificates, and objects representing disabled domain controllers are removed using Ntdsutil.

What Do I Need

Abstract: The computing system used by Pixar to render their film Monsters Inc., had over 3000 Sun SPARC CPUs, and is one of the most powerful clusters in existence. Just to purchase software licences for such a system would cost over $1 million. At the other end of the scale, however, most of the images in this book have been rendered using Angel on a 66 MHz 486 with 32 Mb of RAM running Windows NT, and a P133 with 40 Mb of RAM running Linux. A faster machine will reduce the time you have to wait, and more expensive software may generate a better-looking image, but the rendering process is otherwise identical. The information in this book applies equally to all the renderers, except where noted.

User-level implementation of checkpointing for multithreaded applications on Windows NT

Abstract: The existing user-level checkpointing schemes support only a certain portion of multithreaded programs on the Windows operating system, which are based on single-threaded programs. This paper focuses on studying a checkpointing scheme to support inter-thread synchronization and quantitative variation of threads for multithreaded processes. Unlike other proposed schemes, in which a thread is suspended by another thread at checkpointing, our checkpointing scheme employs a strategy by which a thread suspends itself. Therefore, it is free of nondeterminacy of thread suspension point, thereby ensuring correct rollback recovery. Our checkpointing scheme supports also various synchronization objects such as Mutex, CriticalSection and Event, as well as Semaphore, WaitableTimer and Thread.

WinNTGen : Creation of a Windows NT 5.0+ network traffic generator

Abstract: Citable URI: http://hdl.handle.net/1721.1/29667 Other Contributors: Massachusetts Institute of Technology. Dept. of Electrical Engineering and Computer Science. Advisor: Robert K. Cunningham. Department: Massachusetts Institute of Technology. Dept. of Electrical Engineering and Computer Science. Publisher: Massachusetts Institute of Technology Date Issued: 2003 Abstract: The Lincoln Adaptable Real Time Information Assurance Testbed (LARIAT) project is the first fully automatable network testbed for the evaluation of information assurance (IA) technologies. It allows researchers to easily set up experiments that evaluate the accuracy of host-based and network-based intrusion detection systems (IDSs). Initially, the network traffic it could produce used UNIX services and protocols as implemented for the Linux and Solaris platforms. However, due to the widespread deployment of Windows-based systems in production environments, it is necessary to include Windowsbased traffic when testing IA systems in order to provide a comprehensive evaluation. This thesis describes WinNTGen, a Windows network traffic generation system that integrates into the existing LARIAT framework and enables it to produce Windows-based network traffic. To do this, WinNTGen simulates the actions of a user controlling applications that in turn use network resources. This frees WinNTGen from the need to re-implement network protocols and allows it to operate at a higher level of abstraction. WinNTGen controls applications via loadable libraries that encapsulate the manner in which a typical user interacts with a particular application. The statistical parameters that specify the behavior of a user with each application are derived from real users' behavioral data as they interacted with each application. The system is flexible and extensible so that different versions of the same application as well as additional applications can be controlled by modifying and adding libraries. Finally, the reality and the throughput of the network traffic produced by the WinNTGen system are evaluated. Description: Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2003.; Includes bibliographical references (leaves 65-67). URI: http://hdl.handle.net/1721.1/29667

Implementing the "Just-enough Privilege" Security Model

Abstract: This paper discusses some of the challenges associated with migrating a large, widely distributed Windows NT environment with widespread administrative access for the application and server support personnel to a native Windows 2000 environment which embraces the philosophy of the "Just-enough privilege" (JeP) security model to complete assigned job responsibilities. I'll define the concept of Just-enough Privilege within the scope of this migration, briefly describe the old environment, outline some perceived benefits of moving to this security model, discuss the challenges and roadblocks of implementing the JeP Security model, and provide some real-life examples of how to limit widespread administrative authority on Windows 2000 servers for tasks that are commonly perceived to require administrative privileges to complete. This paper depicts experiences with migrating from a Windows NT environment, but the strategies discussed to implement JeP can be applied to an existing Windows 2000 environment which doesn't enforce the JeP philosophy. Definition of JeP At a high level, it is pretty obvious that the Just-enough Privilege (JeP) Security Model is nothing more than another name for the principle of "least-privileged" access. In fact, throughout most of this implementation, it was called the least- privileged security model and it still is within some areas of the organization. The prevailing thought to rename the strategy at a high level is an attempt to eliminate the negative connotations associated with the word "least", and replace it with the more positive connotations associated with the phrase "Just-enough". To some, I'm sure it sounds like nothing more than semantics and nitpicking, is the glass half-empty or half-full? But as you will find out as you read on, one crucial aspect of a successful implementation of JeP is executive sponsorship. Without executive sponsorship, you will not implement JeP in your organization. Lessons learned through this implementation have demonstrated that this minor upgrade in semantics will lead to a smoother overall acceptance of JeP at all organizational levels.

A Robotic Real-time Control System with Open Architecture Based on Windows NT

Abstract: An open architecture industrial robotic control system based on Windows NT was developed to overcome the limitations of the special architectures adopted by traditional industrial robots. This robotic control system, whose architecture is single CPU structure, can run at general industrial computers. Owing to Windows NT operation system and RTX real time extension environment, the control system has friendly graphic user interface as well as good real time performance. Due to the three layer hierarchical architecture and modularization of the system software, in which the modules can communicate with each other through the unified interfaces, the control system is open and extensible. Furthermore, the interfaces in the system can be added or removed easily through the interface configuration subsystem. To promote the application of the robot system, C language is used as the basic programming language of the robot system. A serial of robot programming API is provided to make users develop their own robot applications easily and flexibly.

“Bond”: An Agents-Based Fault Injector for Windows NT

Abstract: The goal of this chapter is to present BOND, a Software Fault Injection tool able to simulate abnormal behavior of a computer system running Windows NT 4.0/2000 Operating System. The Fault Injector is based on interposition techniques, which guarantees a low impact on the execution of the target program, and allows the injection of Commercial off-the-Shelf software programs. BOND allows performing both statistical and deterministic Fault Injection experiments, trading-off between overhead and precision of the obtained results. Moreover, the tool is capable of injecting faults into different locations, at any level of the application context (code and data sections, stack, heap, processor’s registers, system calls...). A complete set of experimental results on different application programs demonstrates the effectiveness and the flexibility of the tool.

Creating Database Web Applications with PHP and ASP

Abstract: From the Publisher: If you want to add more power and functionality to your Web sites, add some database applications like a powerful shopping cart or a fun quiz game. Such applications make your site more dynamic, allow you to gather information, and provide customized experiences for your visitors. Creating Database Web Applications with PHP and ASP teaches beginning and intermediate designers the fundamentals of creating complex Web applications. By covering both open source (PHP/MySQL) and proprietary tools (Microsoft ASP and Access), readers gain insight to the strengths and weaknesses of each. In addition, they learn how to work with both sets of tools and determine which works best for their projects. Practical examples, including a shopping cart and quiz show, are used to teach the basic concepts behind creating and testing database code. Every example is also provided in both PHP and ASP for easy comparison and use. With the knowledge and experience gained here, beginners will learn the fundamental concepts behind these two technologies, while more experienced developers will learn which technology works best for their specific needs. Exercises, questions, and projects are included with each chapter. Whom this book is for: * Students learning how to create databases for Web applications (some knowledge of HTML and JavaScript is assumed) * Beginner or intermediate Web designers who want to learn how to add database applications to their sites using either PHP or ASP tools Topic Highlights: * Basic Web technologies (HTML and JavaScript) * Client-side versus server-side programming * Database design and planning * SQL fundamentals * Form handling * Passing information using query strings * Cookies and session variables * Validating user input using regular expressions On the CD! * Code Samples - Contains all the code for examples in the book * Projects - Contains all the code for the projects and applications in the book, including a shopping cart, quiz show, and state capital game * Images - Contains color versions of all the images in the book by chapter for easy reference SYSTEM REQUIREMENTS: PC: The PHP and ASP files can be created using any ASCII/TEXT editor, such as NotePad on any Windows System. To create an Access database you need Microsoft Access. The files must be run on a computer that has a Web server such as IIS. Appendix A shows you how to set up IIS, MySQL, and PHP on a Windows XP Professional system. The files have been tested in the following 3 environments: a remote server running Windows NT, Apache, MySQL, and PHP; a local computer running Windows 98, Personal Web Server, MySQL, and PHP; and a local computer running Windows XP Professional, IIS, MySQL, and PHP. ABOUT THE AUTHOR: Jeanine Meyer, Mt. Kisco, NY, has a Ph.D. in computer science from New York University. She is currently an Associate Professor at Purchase College, SUNY, where she teaches computer science and New Media courses including Programming Games and Creating Databases for Web Applications. She is also the co-author of Multimedia in the Classroom and Programming Games using Visual Basic.

DIVERSI 2.1: New version of a program package for calculating diversity and related statistics

Abstract: The recent version of DIVERSI program package runs on IBM-PC compatible machines with DOS operating system or a buisness system which includes DOS client (such as WINDOWS NT, 2000, XP). All routines work with dbase data files. The program calculates diversity indices and their confidence intervals, the significance of diversity differences, index sensitivity and fit some abundance models to actual data. Quadratic entropy and members of the ESS and NESS similarity index family are also included. Hardware requirements, data file operations and examples are provided in a User's Guide. An example of calculating quadratic entropy is presented.

Performance evaluation of a framework for distributed real-time driving simulation applications using windows® based pcs

Abstract: This paper describes how the ever-decreasing cost of personal computers (PCs) has made them attractive platforms on top of which to design and implement driving simulators. Combined with the rapid advancement of processor power and the availability of powerful graphics cards, driving simulators built exclusively on commodity PCs are feasible and becoming commonplace. Furthermore, networking using affordable Ethernet hardware makes it possible to combine the power of multiple PCs and provide systems with aggregate capabilities that were unheard of only a few years ago. Related to the applicability and performance of these systems is the choice of operating system. The choices include dedicated real-time operating systems, Linux, and Windows ® NT/2000/XP, all of which have their respective advantages and disadvantages. Of primary concern is the degree of determinism afforded by each of these choices, as well as the availability and cost of development tools. This paper provides an architectural framework that supports distributed real-time systems, with special emphasis on driving simulation applications built on top of commodity PCs with focus on the applicability of PC hardware Windows NT ® and later. Detailed performance figures are provided for determinism of the system, both in stand-alone as well as distributed modes.

Fine-grained integration of Oberon into Windows using pluggable objects

Abstract: The ETH Oberon System has been implemented in two fundamentally different ways: as native operating system and as an application running on top of another operating system. The embedded versions of Oberon are typically implemented as full screen applications, which are poorly integrated in their host environment. On the on hand, this approach has the advantage of maintaining the look–and–feel of a native Oberon implementation. On the other hand, developers of Oberon software would sometimes want to reuse it or make it available on a fine–grained level as part of commercial applications. In this thesis, a generic solution to this problem using a software component approach is presented. Visual and non–visual Oberon components — ranging from simple gadgets such as buttons, to complex containers such as desktops — are subject to be plugged into foreign contexts of different kinds, e.g. web pages, spreadsheets, etc. Such pluggable objects are able to cooperate and communicate with their context and with other components using technologies like in–place activation, scripting, automation, clipboard, drag–and–drop, persistency, etc. Although the implementation described in this thesis is specific to the Windows platform, most of the fundamental ideas can easily be adopted for other platforms.

Access control method for security in Window NT circumstance

Abstract: PURPOSE: An access controlling method is provided to perform an active access control, not a simple integration management, in a security policy by using a stub, to analyze intercepted parameters and to control the right offered by the Windows NT. CONSTITUTION: A power is switched on and a computer is bootstrapped(S10). A CPU of the computer replaces the physical address of a kernel function, managed by the Windows, with an address, offered by a stub, and stores the physical address at a defined area(S20). The CPU calls the stub and then the kernel function stored at the address replaced by the stub if a kernel function is transmitted to a kernel in an application program(S30). The CPU collects parameters for enabling the transmitted function call to call a real function, and transmits the parameters to the stub(S40). The CPU separates the parameters, needed for an access control, among the transmitted parameters, and compares the separated parameters with a defined security policy(S50). Then, the CPU checks whether an executed function violates the policy(S60). If the executed function violates the policy, the CPU stores an access rejection specification at a log(S70), and generates a warning message along a defined path(S80). Otherwise, the CPU performs the task of the application program by calling the function to be originally executed(S90). The CPU turns over the control function, owned by the stub, to a system(S100), and stops an access operation for the security(S110).

Design and Implementation of Process Checkpoint System NTckpt Based on Windows NT

Abstract: Checkpoint is an important technology to save and rollback the state of processes, and it is widely used in the fields, such as software fault tolerance, rollback debugging and process migration. This paper introduces the mechanism of process on Windows NT, and emphasizes on the implementation of NTckpt, a checkpointing and restore tool. The NTckpt tool introduces a method of restoring data region allocated dynamically, which can correctly restore private data region of the processes.

Strategies for managing the execution of unauthorized programs on a university computer network

Abstract: Universities are constantly plagued by the installation of unauthorized programs on university computer networks. These programs cause maintenance problems, consume disk space and network bandwidth, and expose the university to potential legal liability due to potential copyright violations. This paper outlines several easy to implement methods to stop the execution of unauthorized programs on computers using Windows NT based computers.

The Analysis of PE Format in Windows2000 and Its Application

Abstract: Portable Executable (PE) file format is introduced in Windows NT operating system,and is now frequently used in Windows 2000.This article has a full analysis of the individual components in PE,from its file header to its various sections and their headers.In addition, there is an example following the analysis to introduce the way of utilizing the PE file format.