Inhaltsverzeichnis
Rick GerberTenAsys Corp.rick.gerber@tenasys.com(503) 615-1528P.O. Box 7249, Beaverton, OR 97007-7249
Definition of a Real-Time OS
Applications for Real-Time and Windows 2000/NT
Requirements of a Real-Time System
Soft Real-Time versus Hard Real-Time
Where is Windows 2000/NT Robust?
What are Windows 2000/NT’s Real-Time Weaknesses?
Requirements for aReal-Time Windows Extension
Options for Real-Time Windows 2000/NT/NTE Environments
Provide a Win32 Wrapper Around an RTOS
Loosely-Couple Unrelated RTOS with Windows 2000/NT
Modify the Windows 2000/NT Kernel and/or the HAL
Complement Windows 2000/NT With a Real-Time Kernel
INtime System Architecture
Development Status
INtime Architectural Overview
INtime Architectural Overview (continued)
OSEM: Operating SystemEncapsulation Mechanism
Typical Flow of Control
INtime Memory Protection
Protection from “Blue Screen” Crashes
User-Mode is Best Place forReliable Real-Time Programs
INtime Development Environment
INtime Application Debugging
Real-Time Application Programming Interface
Key New Features in v2.1
Closer Integrationwith Windows 2000/NT/NTE
Real-Time Environment Improvements and Additions
C++ Language Support forReal-Time Applications
File System I/O for Real-Time Applications
Network I/O for Real-Time Applications
INtime Topologies
Distributed INtime System
Remote Distributed INtime Real-Time Nodes
Distributed Real-Time Nodes
Windows Embedded NT 4.0 (NTE) Support
iRMX Compatibility with Intime 2.1
iRMX Compatibility with Intime 2.1
Benefits of Real-Time Windows 2000/NT/NTE
|