<p>Jag har under en period motsvarande 10 veckor på heltid utvecklat ett grafiskt konfigurations-verktyg för konfiguration av ftp-servern ioFTPD [4]. ioFTPD är en relativt ny ftp-server för Windows som är resurssnål och högpresterande [4]. ioFTPD utvecklas av iniCom Networks [4] som även utvecklar den kända ftp-klienten FlashFXP [4].</p><p>Idén till att utveckla ett grafiskt konfigurationsprogram kom till eftersom det inte fanns några grafiska verktyg för vare sig konfiguration eller övervakning av servern. Eftersom det inte fanns något användarvänligt grafiskt konfigurationsverktyg var användaren tvungen att editera ioFTPD:s konfigurationsfil manuellt. Manuell editering av en så stor fil gör det lätt att införa fel.</p><p>Mina delmål var att skapa tre grafiska applikationer för att hjälpa till att konfigurera och övervaka ioFTPD-servern.</p><p>• Ett grafiskt konfigurationsverktyg</p><p>• Ett övervakningsprogram</p><p>• En vfs-editor för skapande och redigering av det virtuella filsystemet</p><p>Huvudmålet var att implementera det grafiska konfigurationsverktyget, vilket jag gjorde. Jag är nöjd med slutprodukten även om det finns detaljer som kan förbättras.</p><p>Under projektets gång har jag bland annat förbättrat mina kunskaper i C++ och Win32-programmering, samt att jag insett vikten av att göra en genomtänkt design innan man påbörjar implementationen.</p> / <p>I have, during a period of ten weeks, full time, developed a configuration utility, featuring a graphical user interface for the configuration of the ftp server ioFTPD [4]. ioFTPD is a relatively new high performance and resource efficient ftp daemon [4] for Windows. ioFTPD is developed by iniCom Networks [4], who also develop the popular ftp client FlashFXP. [4]</p><p>Because ioFTPD lacks graphical applications for the configuration and monitoring, the idea to develop a graphical configuration utility arose. Since there was no user friendly graphical configuration utility, the user manually had to edit ioFPTD's configuration file. Manually editing such a big file could easily result in error introduction.</p><p>My goals were to develop three graphical applications to aid in the configuration and monitoring of the ioFTDP server.</p><p>• A graphical configuration utility</p><p>• A monitoring application</p><p>• A vfs-editor to aid in the creation and editing of the virtual file system</p><p>The main goal was to implement the graphical configuration utility, which I did. I'm satisfied with the result even though there are details that could be improved.</p><p>During the project I have improved my knowledge with C++ and programming</p><p>with the Windows API. I've also realized the importance of doing a thoroughly thought through design before one starts the implementation.</p>

Jag har under en period motsvarande 10 veckor på heltid utvecklat ett grafiskt konfigurations-verktyg för konfiguration av ftp-servern ioFTPD [4]. ioFTPD är en relativt ny ftp-server för Windows som är resurssnål och högpresterande [4]. ioFTPD utvecklas av iniCom Networks [4] som även utvecklar den kända ftp-klienten FlashFXP [4]. Idén till att utveckla ett grafiskt konfigurationsprogram kom till eftersom det inte fanns några grafiska verktyg för vare sig konfiguration eller övervakning av servern. Eftersom det inte fanns något användarvänligt grafiskt konfigurationsverktyg var användaren tvungen att editera ioFTPD:s konfigurationsfil manuellt. Manuell editering av en så stor fil gör det lätt att införa fel. Mina delmål var att skapa tre grafiska applikationer för att hjälpa till att konfigurera och övervaka ioFTPD-servern. • Ett grafiskt konfigurationsverktyg • Ett övervakningsprogram • En vfs-editor för skapande och redigering av det virtuella filsystemet Huvudmålet var att implementera det grafiska konfigurationsverktyget, vilket jag gjorde. Jag är nöjd med slutprodukten även om det finns detaljer som kan förbättras. Under projektets gång har jag bland annat förbättrat mina kunskaper i C++ och Win32-programmering, samt att jag insett vikten av att göra en genomtänkt design innan man påbörjar implementationen. / I have, during a period of ten weeks, full time, developed a configuration utility, featuring a graphical user interface for the configuration of the ftp server ioFTPD [4]. ioFTPD is a relatively new high performance and resource efficient ftp daemon [4] for Windows. ioFTPD is developed by iniCom Networks [4], who also develop the popular ftp client FlashFXP. [4] Because ioFTPD lacks graphical applications for the configuration and monitoring, the idea to develop a graphical configuration utility arose. Since there was no user friendly graphical configuration utility, the user manually had to edit ioFPTD's configuration file. Manually editing such a big file could easily result in error introduction. My goals were to develop three graphical applications to aid in the configuration and monitoring of the ioFTDP server. • A graphical configuration utility • A monitoring application • A vfs-editor to aid in the creation and editing of the virtual file system The main goal was to implement the graphical configuration utility, which I did. I'm satisfied with the result even though there are details that could be improved. During the project I have improved my knowledge with C++ and programming with the Windows API. I've also realized the importance of doing a thoroughly thought through design before one starts the implementation.

In order for an agent to be considered both an interface agent and autonomous, it follows that there must be some part of the interface that the agent must operate in an autonomous fashion. The user must be able to directly observe autonomous actions of the agent and the agent must be able to observe actions taken autonomously by the user in the interface The ability of a software agent to operate the same interface operated by the human user, and the ability of a software agent to act independently of, and concurrently with, the human user will become increasingly important characteristics of human-computer interaction. Agents will observe what human users do when they interact with interfaces, and provide assistance by manipulating the interface themselves, while the user is thinking or performing other operations. Increasingly, applications will be designed to be operated simultaneously by users and their agents [1]. This study is motivated by the need to solve a problem of human resource optimization in the first year informatics practical course as presented by the R.A.U. Standard Bank Academy for Information Technology. The major aim being the development of a prototype system capable of automatically grading first year Microsoft Visual Basic.Net applications. The prototype system will ultimately render assistants obsolete in the grading process and free the assistants to help students with problems related to the informatics course. Developing the envisaged prototype requires much preliminary reading on artificial intelligence and its applications, more specifically autonomous interface agent architecture. Case-based reasoning and machine learning has been identified as having great potential and applicability in the development and implementation of the envisaged prototype and for this reason these topics will provide a foundation on which to build this dissertation. / Ehlers, E.M., Prof.

There are several timing mechanisms on presently available commercial operating systems. Two operating system platforms that immediately come to mind are the Microsoft Windows environment (the WIN32 platform) and its UNIX-based counterpart, Linux (with its POSIX standard). The timing mechanisms under these operating systems are adequate for use in conventional multimedia applications currently run on these platforms. However, the requirements of such applications are not as stringent within a real-time environment. The goal of this dissertation was to determine if it would be possible to find a workaround for applications where current timing mechanisms in the WIN32 and POSIX environments do not meet the requirements of real-time. Before a proposed workaround is presented, a clarification is given as to what is meant by the notion of a timer. Attention is also given to the fact that its accuracy is quantified in terms of its resolution. It is acknowledged that real-time extensions to both the Windows and Linux operating systems exist. However, it was decided to find a solution without such assistance. Real-time is also defined and sub-classified into hard- and soft real-time, differentiating environments that have precise constraints (hard real-time) on timing as opposed to environments where demands on accuracy and efficiency are less stringent (soft real-time). The timer that was ultimately implemented had to conform to the latter form of real-time. This dissertation therefore aims to provide a solution in a soft real-time environment. The current timing mechanisms are discussed and their performance is quantified. Their deficiency in measuring a reliable periodic interval of 1 ms is highlighted. From this qualification of timers stems the requirements for the soft real-timer timer. The areas in which improvement is sought are stated. The design and implementation of a soft real-time timer that meets these requirements is presented and its performance at various frequencies is quantified. A comparison is given between the timer and the existing timing mechanisms as well as comparison between its implementation under both Windows and Linux. Additionally, the viability of the proposed timer compared to a proven hard real-time timer is presented. Finally it is recognised that a timer would not be useful if it was not effective in a practical environment. Consequently, the timer’s performance under the same load that it would experience in a practical soft real-time environment is investigated as well. The dissertation concludes with a discussion on the compatibility of this timer with expected advances in future Central Processing Unit (CPU) technologies. / Dissertation (MSc (Computer Science))--University of Pretoria, 2007. / Computer Science / MSc / unrestricted

Ever since we were children the phrase "In case of an emergency, walk, DON'T run, to the nearest exit" has been drilled into our heads. How to evacuate a large number of people from a given area as quickly and safely as possible has been a question of great importance since the first congregation of man; a question that has yet to be optimally answered. There have been many attempts at finding an answer and many more yet to be made. In light of recent world events, 9/11 for instance, the need for a better answer is apparent. While finding a solution to this problem is the end objective, the goal of this thesis is to develop an application or tool that will aid in the search of an answer to this problem. There are several aspects of traditional evacuation plans that make them inherently suboptimal. First among these is that they are static by nature. When a building is designed, there is some care taken in analyzing its floor plan and finding an optimal evacuation route for everyone. These plans are made under several assumptions and with the obvious constant that they cannot be modified during the actual emergency. Yes, it is possible for such a plan to actually end up being the optimal plan during any given evacuation, but the likelihood of this being the case is most definitely less then 100%. There are many reasons for this. The most obvious is this: the situation that the plan is trying to solve is a very dynamic one. People will not be where they should be or in the quantities that the static plan was prepared for. Many of them will probably not know what they should do in an emergency and so most likely will follow any large group of people, like lemmings. Finally, most situations that require the evacuation of a building or area occur because all or part of the building has become, or is becoming, unsafe. It is impossible for a static evacuation plan to take into account the way a fire or poisonous gas is spreading, or the state of the structural stability of the building. What is needed during a crisis is an artificially intelligent and dynamic evacuation system that is capable of (1) analyzing the state of the building and its occupants, (2) coming up with a plan to get everyone out as fast as possible, and (3) directing all occupants along the best exit routes. Furthermore, the system should be able to modify its plan as the evacuation progresses. This application is intended to provide researchers in this area the means to quickly and accurately simulate different evacuation theories and ideas. That being the case, it will have powerful graphical capabilities, thus allowing the researchers to easily see the real-time results of their work. It will be able to use diverse modeling techniques in order to handle the many different ways of approaching this problem. It will provide a simple way for equations and mathematical models to be entered which can affect the behavior of most aspects of the world being simulated. This work is in conjunction with, and closely tied to, Dr Pushkin Kachroo's research on this same topic. The application is designed so that future developers can quickly add to and modify its design to meet their specifications. It is not the goal of this work to provide an application that directly solves the optimal evacuation problem, or one that inherently simulates everything perfectly. It is the job of the researchers using this application to define the specific physics equations and models for each component of the simulation. This application provides an easy way to add these definitions into the simulation calculations. In brief, this Escape Simulator is a client server application. All of the graphics and human interaction are handled client side using Win32 and Direct3D. The actual simulation world calculations are handled server side, and both the client and server communicate via DirectPlay. The algorithm being used to model the objects and world by the server will be completely configurable. In fact, everything in the world, including the world physics, will be completely modifiable. Though the researchers will need to write the necessary pluggins that to define the actual models and algorithms used by the agents, objects, and world, ultimately this will give them much more power and flexibility. It will also allow for third parties to develop libraries of commonly used algorithms and resources that the researchers can use. This research was supported in part from the National Science Foundation through grant no. CMS-0428196 with Dr. S. C. Liu as the Program Director. This support is gratefully acknowledged. Any opinion, findings, and conclusions or recommendations expressed in this study are those of the writer and do not necessarily reflect the views of the National Science Foundation. / Master of Science

Main topic of this thesis is Win32 application programming interface and symbolic instructions programming language. It can be divided into four parts. First part sums the basics of 32-bit programming in symbolic instructions language in Windows. Second part describes the Win32 resources for computer intercommunication. Third part presents, describes and comments selected problems in symbolic instructions language.Last part covers a creation of an example application. This application and its parts will be the content of computer exercises in VUT Brno FEEC subject Počítače a jejich periferie.

International Telemetering Conference Proceedings / October 25-28, 1999 / Riviera Hotel and Convention Center, Las Vegas, Nevada / Upgrading or replacing production systems is always a very resource-consuming task, in particular if the systems being replaced are quite specialized, such as those serving any Flight Test Ground Station. In the recent past a large number of Ground Station systems were based in Digital’s VAX/VMS architecture. The computer industry then expanded very fast and by 1990 realtime PCM data processing systems totally dependent on hardware and software designed for IBM-PC compatible micro-computers were becoming available. A complete system replacement in a typical Ground Station can take from one to several years to become a reality. It depends on how complex the original system is, how complex the resulting system needs to be, how much resources are available to support the operation, how soon the organization needs it, etc. This paper intends to review the main concerns encountered during the replacement of a typical VAX/VMS-based by an Intel-Windows NT-based Ground Station. It covers the transition from original requirements to totally new requirements, from mini-computers to micro-computers, from DMA to high-speed LAN data transfers, while conserving some key architectural features. This 8-month development effort will expand EMBRAER’s capability in acquiring, processing and archiving PCM data in the next few years at a lower cost, while preserving compatibility with old legacy flight test data.