DE19654766A1 - Different communication protocols network terminal - has processor responsive to first and at least second personalities for processing one of first and third sets of instructions - Google Patents

Abstract

The terminal (12) includes a first personality for providing responses to first and second sets of instructions supplied by a first host (10) system in accordance with the communications protocol associated with that first host system. At least a second personality is used for providing responses to third and fourth sets of instructions supplied by a second host system (16) in accordance with the communications protocol associated with that second host system. At least one of the host systems provides windowing information. A processor is responsive to the first and at least the second personalities for processing one of the first and third sets of instructions. The processor also emulates one of the second and fourth sets of instructions, to provide to the associated host system responses compatible with the communications protocol associated with that host system. A switching device is used for identifying the host system to which the terminal is currently connected.

Description

The present invention relates generally to a method ren and a device for displaying information a terminal or at a workstation and in particular on a method and apparatus for formatting and displaying len information on a terminal, on a graphic User interface, such as the Microsoft Windows® User environment, including the user programs in it Surroundings.

Graphical user interfaces, such as the Microsoft Windows® Operating environment, represent the most widespread and worldwide most sold application software. Such environments are particularly preferred because they are easy to use are, offer uniform user interfaces, a high Display quality and for many other reasons.

However, these user environments require expanded Ar workstations and microcomputers such as Personalcom computer (PC). These workstations and microcomputers are though flexible, but cause difficulties in terms of Security, reliability, ease of use and are complex. In contrast, data terminals are compared to Microcomputers are known for their benefits of better security and for their ease of use and for making them more common wise are cheaper; however, these terminals are more common wise with the most used graphical user interfaces compatible. Those terminals that are in the X environment work, offer limited graphical User interface capabilities under UNIX®, however, are expensive and require a large amount of storage space and are among those common Windows® environments are not compatible.

Another known option is the so-called plate-free PC system ("diskless PCS"). However, the diskless PCS suffers  among some shortcomings. In most cases it shows the diskless PCS that ar in a "client-server" environment is preparing application program information by the user downloaded from the server, and then this application running locally. This requires from the diskless PC too at least one, whatever kind of equipment, for each this version also makes this possible. In the usual way today Environment this can be a memory of more than eight megabytes, require a strong processor, etc., which makes the individual diskless PC again becomes very expensive. After all, that's plat tenless PCS little secure and can be extensive administration make necessary.

The Windows® NT operating system represents a robust one Network client / server environment and at the same time offers com compatibility with the application program level of the common Windows® environment. However, the NT operating system was designed for PC clients and not designed for terminals. This leads to the NT clients in turn have to be robust and therefore expensive. In addition, Windows® NT is for the "client-server" environment and not designed for a "multiuser" environment. That recently from Citrix Systems, Inc. featured WinFrame® operating modes the Windows® NT operating system by expanding into one Multi-user environment, while previous versions of WinFrame® needed PCS clients instead of terminals.

There is therefore still the task of an inexpensive ter making it available that works reliably, easily use and is safe and the user program information mations in a Multiuser Windows® operating environment can.

The present invention offers an elegant solution to the To overcome disadvantages of the prior art by using a inexpensive terminal for displaying with a window environment compatible user software becomes available.  

In particular, the invention provides a display terminal that in is able to run in a multiuser system with an application ser ver to communicate. This creates secure access too the Windows® applications in the workplace. In a con an application server in the form of a any computer on which the WinFra me® operating system is running. The WinFrame® operating system from Citrix Systems, Inc. closes the Windows® NT operating system and additional enhancements that include a display known as ICA-3 Implement protocol and multiuser capabilities.

In one embodiment, the terminal builds on one Hardware architecture with the INTEL® X86 processor line. In addition, the terminal has only a limited main memory and is basically not designed to suit local modern needs application programs such as word processing programs, graphics pro programs or database programs or other popular programs running, not even Windows® or DOS operation system itself. This is how a terminal differs according to the present invention basically from the known X-Terminal or the diskless PCS or other PC systems, who work in a client-server environment.

It is important that the new hardware architecture is not based on the usual IBM PC / AT bus and the firmware (which in software stored in a ROM) within the terminal neither on the PC / AT BIOS standard nor on PC-compatible plat operating systems. The terminal firmware implemented Network access extensions using the application server are compatible, again z. B. available from Citrix Systems ICA-3 extensions. It will be both a high resolution Screen provided for ease of use of the offers a black and white image with many grayscale or color, as well as the typing and typing for a Windows® environment Output devices such as mouse, keyboard, touch screen and other input and output facilities.  

In addition, there is a network interface that works with the Application server over conventional R5232 connections, ether net connections, wireless connections, ISDN, fiber optics, AC connection modems, cables, or otherwise communicates. As soon as the connection to the server is established, this shows Terminal the Windows® NT or Windows 95® environment finally any application programs running on the server can be executed and on which the user at the terminal can access. In an exemplary arrangement, this represents Terminal to the user essentially the same as a we considerably more expensive, less secure and more difficult to use the personal computer. As a result, the present Erfin numerous features normally found with a multiuser system be associated, while at the same time many noteworthy features are presented that for a Client-server environment are typical.

A feature of the present invention is the ability in work independently of clients within the Windows® environment. In this way, a user defines with a system according to and its operating environment of the present invention Environment follows him or her through the whole system. One user can therefore log into a terminal, define an environment kidney and then log into another terminal. The second terminal will then automatically display the environment that the user has defined on the first terminal.

In addition to the ability to view application program information display, the terminal has according to the present inven via a setting mode, which the user possible to configure a variety of operating modes of the terminal figure.

To be able to operate terminals according to the present invention from the servers running WinFrame® running to follow orders sent is special Terminal operating system has been developed using a conventional  les PC operating system either emulated or otherwise answered the calls. The terminal operating system closes a boot block to initialize and shutdown the system start, which is followed by a kernel, which additional driver and command software loads, including a modifi graced WinFrame® client codes. The execution of the modified The WinFrame® client closes the establishment of a connection to an application server.

In addition to the ability to store application information in a This Microsoft Windows® environment offers Invention also the ability to work with other servers or Host computers on which operating systems other than Windows® run to communicate by other resident terminal emula tion or characteristics are included with the possible by simply pressing a button between the different Switch characteristic data back and forth.

Another feature of the present invention is that Implementation of a graphical user interface for the Configuration of a terminal and others to be solved locally Tasks. In particular, the graphical interface provides a Plenty of windows available and every window allows a new configuration of one or more terminal IDs characters or other local tasks. Are in every window the choices arranged in groups in this Windows can be configured. This choosing or this Choices that the user can make use of are displayed or are indicated by a "pull down" - or a similar menu can be displayed. Different data structures belong to different types of groups or choices ten.

Another feature of the present invention is inclusion of the terminal operating system in a short-term memory, one "Flash memory". This flash memory can be used in different ways Ways to be updated, including communication  through a suitable interface, such as a parallel or serial port, or a network adapter as soon as the terminal is in a predetermined status.

It is therefore one of the advantages of the present invention To make available a terminal that can represent information by an application server by running a popular Application program operating under the Microsoft Windows® NT system environment was created.

It also includes a terminal configuration system a graphical user interface for configuration to create the terminal operating parameters.

It also includes a terminal for displaying An to provide application program information which a client per sonalcomputer in a client-server network environment emu liert.

A terminal will also be available, which is desirable Features typically associated with a multiuser computer exercise, combined with the desirable features, that are usually associated with a client-server environment.

It is part of the invention to use a terminal operating system have what communications with a window operating system environment while allowing a PC / AT BIOS and PC DOS different standard is used.

However, the invention also includes a device and a method for a quick and appropriate update of the Terminal operating system.

After all, there should be several resident characteristics for one terminal be available by quickly switching between the various characteristics, without expansion cards be replaced or the terminal disconnected from the mains  got to.

Further details, features and advantages of the present Invention result from the following description of the drawing mentions.

Show it:

Fig. 1 is a schematic illustration of a general voltage Anord an application server and a terminal according to the present invention,

Fig. 2 is a block diagram of an architecture of the new sys tem,

Fig. 3 is a block diagram showing the construction of the control ASIC in FIG. 2,

Fig. 4 is a flowchart for the process of steps in a terminal,

Fig. 5 is a simplified block diagram of the setup GUI interface between a machine and the rest of the system,

Fig. 6 is a block diagram of the flow of a connection establishment between the terminal assembly and application servers,

FIG. 7A is a screen layout according to the present invention, and

Fig. 7B1-7B3 data structures.

In Fig. 1 is a simplified system is shown according to the principle of the present invention. A single application server 10 is bidirectionally connected to one or more terminals 12 via a suitable network or other communication line 14 . This communication line can consist of an RS232 line, an AC line modem or an Ethernet connection, for example a twisted pair or a coaxial cable or another suitable connection, for example a fiber optic. In a satisfactory arrangement, which is mentioned here as an example in test operation, the application server with the WINDOWS® NT operating system is equipped with suitable extensions, e.g. B. operated by CITRIX offered Winframe® OS. The CITRIX remote WINDOWS protocol or extensions include both the ICA 3.0 protocol and improvements that ensure real multi-user capability within the WINDOWS® NT environment. In such a configuration, the application server 10 may be one on an INTEL Pentium® or a '486 processor or other similar processors, such as a DEC Alpha or MIPS processor, or an interconnection of multiple processors in conjunction with a suitable one RAM capacity, act based on the personal computer. In one embodiment, server 10 has sixteen megabytes of RAM for Winframe® OS, plus 1-8 megabytes of RAM per concurrent user, depending on which application is running for the individual user.

In other suitable exemplary embodiments, the application server 10 can also communicate with other servers, for example with a NetWare file server 16 , a UNIX® host 18 , other personal computers 20 or even an Internet gateway 22 . Via other connections, such as a router or other communication servers 24 , the application server 10 can also communicate with computers 26 working behind it or via other devices also with other remote selectable users 28 .

Further details of the hardware architecture of a terminal he follow from Fig. 2. A CPU 100, typically a Prozes sor of the X86 family or as in one embodiment, a 80386CXSA or a '486SXLC microprocessor receives the clock and reset signals from a logic clock and reset circuit 102 . The CPU 100 communicates with the other logic circuits via an address bus 105 , a data bus 106 and a CTRL bus 108 . It is important that these bus connections are typically not compatible with the IBM PC / AT standard or with another PC standard, since the invention is intended to avoid many, if not all, of the shortcomings that otherwise occur with personal computers when they work in a network environment.

In particular, the address bus 105 runs from the CPU 100 both to a control ASIC 110 (user-specific IC 110 ) and to a flash memory area 112 and a VGA controller 114 . The data bus 106 likewise communicates with the control ASIC 110 , the VGA controller 114 and a memory arrangement 116 . The CTRL bus 108 similarly applies control signals to the ASIC 110 and the VGA controller 114 . Various logic circuits 118 apply CONFIG, IDCS and DIAGCS to the ASIC 110 .

The ASIC 110 communicates with the memory arrangement 116 via a DMA bus 120 and also with the flash memory 112 via a PD bus 122 . The PD bus 122 also provides communication between the ASIC 110 and the flash memory 112 , a serial I / O and a parallel controller 124 , a keyboard and mouse controller 126 and a LAN (= Local Area Network) ) Controller 128 . In addition, the ASIC applies an FCS signal (test signal) to the flash memory 112 , provides RAS, CAS and WE signals for the memory arrangement 116 and for COM1, COM2 and PPCS signals for the SIO controller 124 . Furthermore, the ASIC 110 applies a KBCS signal to the keyboard / mouse controller 126 and applies a NETCS signal to the LAN controller 128 . Finally, the ASIC 110 outputs a speaker enable signal SPEN to a speaker 130 .

The CPU 100 also communicates with the SIO controller 124 , the keyboard / mouse controller 126, and the LAN controller 128 over part of the bus 105 . In addition, the ASIC 110 provides the SIO controller 124 with hardware interrupts INTA, INTB, INTP and the KB / MS controller 126 with hardware interrupts KBINT and MSINT and the LAN controller 128 with a hardware interrupt NINT.

The memory area 116 typically consists of a DRAM memory, although other types of memory in modified embodiments can also be used. However, the size of the DRAM in the range 116 , which is required for the operation of the terminal, in contrast to the modern personal computer, is typically in the range from 512 kilobytes to four megabytes. In an exemplary embodiment, only 23 address lines and one byte select line are used, which can limit the memory capacity to 16 megabytes. In other embodiments, different memory sizes can be used.

In one embodiment, the control ASIC 110 has function blocks for bus control, for DRAM control (here typically in fast page mode with mutual offset), for a system timer, for a loudspeaker timer and an I / O controller. The control ASIC may also be implemented as a gate array or other highly integrated circuit, which will be described in more detail below in connection with FIG. 3.

In one application example, it has proven sufficient to keep the flash memory 112 in the order of 512 kilobytes; however, other applications could require sizes up to five megabytes or more. In the preferred embodiment, the area 112 is shown as flash memory, in other embodiments, but without leaving the functionality of the present invention, this area could also consist of an EPROM or an SRAM or other comparable memory units.

SIO controller 124 communicates with COM1, COM2, and printer (or parallel) ports 132 , 134, and 136 , respectively. The SIO / parallel controller 124 can be a commercially available 16 552 module, such as that offered by the Startech company. The keyboard / mouse controller 126 similarly communicates with a keyboard 138 and a mouse 140 , while the LAN controller, which is not required in all embodiments, communicates with a LAN interface 142 . In a prototype, the keyboard / mouse controller 126 consisted of a standard keyboard controller, while the keyboard and mouse conform to the PS / 2 standard, although at least in some embodiments, the keyboard controller can be modified to accommodate a four-wire keyboard interface as described in U.S. Patent 4,706,068. Finally, the LAN controller can consist of any suitable network interface controller and conform to any possible network standard, including 10BaseT, 10Base2 or others. The network interface may have a 512 kilobyte memory or larger for additional code storage.

The video and graphics controller 114 is operatively connected to a second memory area 144 to store video and graphic information that is passed to a monitor 146 via an MPS 148 . The video controller 114 can be, for example, a Cirrus 5429 chip with internal RAMDAC and can have a video memory of the order of one megabyte in order to enable high-resolution graphics representations, which at least correspond to the video graphics array standard. It will be apparent to any person skilled in the art that the total memory requirements are significantly smaller than those required for a personal computer of comparable capacity to run WINDOWS® application programs. A silence signal 150 can be provided by the ASIC 110 . Various methods of implementing a quiescent signal can be used. For example, in a black and white version of the present invention, a signal to the power supply for the monitor can be provided, which switches off the video signal and reduces the power consumption which is necessary for the operation of the monitor. In a color version, the synchronization signal can be manipulated in accordance with the VESA standard in order to power down the monitor. It will be apparent to those skilled in the art that many functions, including the CPU, can be combined in one or more integrated VLSI components, such as an ASIC, gate arrays or other components.

It is a particular feature of the hardware according to the present invention that the terminal operating system, which is stored in the flash memory 112 , can be updated by a variety of methods, including communication via a suitable interface, such as the parallel Interface 136 or serial interfaces 132 or 134 or a network adapter, such as LAN interface 142 . In a preferred embodiment, the flash memory can be updated by communication with the host system when the terminal is in a predetermined state, such as e.g. B. by inserting a feedback loop connector, a suitable key sequence or other suitable means. In such an arrangement, the downloading into the terminal's storage system takes place while communication with the host computer is still permitted. The host computer then provides updated operating features via the communication link either to the DRAM 116 of the terminal or directly to the flash memory 112 . Thereafter, if necessary, the updated operating system information is stored in the flash memory 112 and the terminal returns to the normal operating state in which the download is turned off.

Under normal circumstances, a system according to FIG. 2 starts the operation after a reset by starting the execution of the boot code which is stored in the flash memory area 112 . The flash memory area 112 may be arranged in two memory areas, both of which are accessed at a predetermined address of the CPU memory space, for example C00000-DFFFFF and E00000-FFFFFF, while the rest of the memory space is intended for many of those shown in Table 1 resulting normal PC functions. It will be appreciated that in a preferred embodiment the video / graphics memory addresses are shifted eight megabytes beyond the normal PC memory addresses. In this embodiment, the VGA chip can be used in a "compatible" mode (ie, the linear address mode is off), so that the VGA chip only applies to a frame buffer at A0000h-AFFFFh (in graphics mode) or at B0000h-B7FFFh (for MGA mode) or at B8000h-B8FFFh (for CGA mode), and that these addresses are shifted to 8A0000h-8AFFFFh, etc. The addresses are shifted to allow memory area 0 DRAM to be contiguous remain, while at the same time (and as will be explained in more detail below) an emulation of the normal PC functions is enabled which is sufficient to display a WINDOWS® application program information.

Table 1

Memory area 0 can be arranged in a 16 kilobyte boot block in the upper address area, for example with FFC000H-FFFFFFH, followed by two 8 kilobyte parameter blocks and further followed by a large number of main blocks down to the address F80000H (for a 512 kilobyte -Design) or down to F00000H (if there is a 1 megabyte design) or to E00000H (if there is a 2 megabyte design). The main blocks of memory are typically set up as a file system. The memory area 1 of the flash memory is typically assigned to a file system device and can range from the addresses DFFFFFH down to C00000H.

The ASIC 110 is explained in more detail below with reference to FIG. 3. A clock buffer 160 receives a CLK50 signal and applies clock signals to the logic RESET SYNC circuit 162 , to the logic DRAM control circuit 164, and to the logic timing circuit 166 . An (INT) buffer 168 receives INTP, INTA, INTB, MSINT, KBINT and NINT signals. The INT buffer 168 applies a variety of signals to the logic interrupt control circuit 170 which receives a control signal from the CPU control input buffer 172 and a timer control signal from the logic timer control circuit 166 and generates an INTR output signal which is applied to the CPU . CPU control input buffer 172 also applies a control signal to logic cycle control circuit 174 , which in turn applies a control signal to DRAM controller 164 . The DRAM control circuit 164 receives an update signal from the timer control circuit 166 ; the timer control circuit 166 also generates the enable signal SPEN for the speaker.

In a preferred embodiment, logic interrupt control circuit 170 is not compatible with device 8259; likewise, the system timer or timer control circuit 166 is not compatible with device 8254 and operates at a higher frequency than an 8254 compatible device. As a result, some of the higher frequency interrupts sent by the logic timer control circuit are masked in the kernel, but others are allowed through to approximate the normal time between interrupts on average. The higher frequency thus enables standard PC functionalities to be emulated, even though the time between interrupts emulated at lower (standard) frequency cannot be uniform.

The ASIC 110 also includes a CPU address input buffer 176 which receives BE0, BE1 and A1-A23 signals and applies an output signal to a DRAM memory address multiplexer "Mux 178 " and at the same time to a logical Mem / IO -Chip selection control circuit 180 . The logic Mem / IO chip selection control circuit 180 produces a variety of output signals including FLASHCSO (FCSO) and FLASHCS1 (FCS1) signals, and others that will be apparent from the drawing. The ASIC 110 also receives signals DO-15 from the data bus 106 and applies them to the CPU data input buffer 182 . Buffer 182 applies data to a Bdata output buffer and buffer 184 , which generates an output signal BDO-15. Buffer 182 also applies data to a power supply control circuit 186 which generates SLEEP and PWRDWN signals.

The signals BDO-15 can also apply data to the Bdata input buffer 188 , which in turn routes this data to the CPU data output buffer 190 . The logic interrupt control circuit 170 also applies signals to the buffer 190 . A configuration register 192 provides a configuration signal (for example one for hardware configuration, e.g. how much flash memory and / or DRAM memory is required, or a configuration from the monitor power supply or from a plug-in card, e.g. a network card), which is applied to the CPU data output buffer, which can create data on bus 106 to the CPU.

Referring to Fig. 4, the key elements may be the terminal operating system to be better understood. From the foregoing it appears that the hardware according to the present invention is not compatible with a standard AT bus standard design. Instead, the present invention relies on firmware to prepare the necessary BIOS services for the upper software layers. In a preferred embodiment, the firmware is designed to run in virtual 8086 mode, with AT-compatible hardware components, such as the interrupt controllers and timers, which are emulated as densely as possible in software. While in one embodiment a standard keyboard controller is used, in the case where a non-standard controller is used the interface to such a device would be additionally emulated. Signals, e.g. B. input and output signals to and at the ports of such hardware components are intercepted to enable the emulation. Furthermore, the memory management features of the processor could be released under the control of an emulated A20 gate to simulate the image rotation that normally occurs in hardware at one megabyte.

According to FIG. 4, the terminal operating system starts processing Abar a boot block 300, followed by loading a kernel 305th Kernel 305 provides many of the interception and redeployment functions of the present invention, as discussed in more detail below. After the kernel 305 has ended , the IO.SYS code 310 is loaded. The COMMAND.COM code 315 is loaded next, followed by execution commands stored in an AUTOEXEC.BAT file. The AUTOEXEC.BAT file can include, for example, keyboard and mouse drivers, although these two drivers are not required in every state, and a VGA XMS driver. It can also include other optional codes, such as triggering a self-test sequence that is in progress, if suitable conditions exist. In a preferred embodiment, a feedback loop connector is inserted into a communication port, which causes the self-test sequence to run.

EXEC.COM code 325 is then loaded. At this point, and depending on the implementation, the system will either enter setup mode, or user commands can either enter setup mode or load a network connection code. In one embodiment, the system enters a setup mode to obtain current configuration data and continues to load the network connection code.

If the implementation allows the user to select and if the setup mode has been selected by the user, the EXEC.COM 325 branches to run the SETUP or GUI 330 . If the setup mode has not been activated, the EXEC.COM 325 helps to load and unload network drivers at 335 and starts processing the network connection code 340 (again ICA, twisted wire, com or other network). In a preferred embodiment, the network connection code contains a substantially modified version of the WinFrame for DOS clients, the standard version of which is available from Citrix Systems, Inc.

Referring to Fig. 5, the cooperation of the terminal operating system and the hardware architecture can be better understood. The bottom layer shown in FIG. 5 is the input / output system and the hardware layer 400 . The next higher layer is the driver 402 layer, while the top layer is the application layer 404 .

When turned on, the power-up and init tests 406 are executed in the hardware layer as part of the boot block 300 . The power-up and init tests 406 are carried out partly by the flash memory system 112 and partly by the RAM 116 . When the power-on self-tests are complete, the terminal continues with the boot sequence generally described above in connection with Fig. 4, including the remainder in boot block 300 , an AUTOEXEC sequence 408, and the COMMAND.COM se quenz as previously referred to as 315 . Both the AUTOEXEC and COMMAND.COM files are stored in the flash memory.

After the COMMAND.COM sequence of the terminal is executed, this causes the AUTOEXEC file to be loaded. AUTOEXEC in turn causes EXEC.COM 325 to be loaded. As noted above, the EXEC.COM sequence 325 can branch into either a setup module 330 or a network connection module 340 . Setup module 330 is run at initial installation or at any time thereafter when terminal operating parameters require variation or change. The setup module 330 receives information from one or more setup data files 418 and starts the GUI engine 420 . The GUI machine 420 in turn communicates with a keyboard driver 422 , a mouse driver 424 and the file and memory driver 426 of the terminal operating system. In addition, the GUI machine 420 also communicates with the video input and output system 428 , which in turn applies data to the video controller 430 , which can be based, for example, on a Cirrus 5429 graphics processor, for a video display during the setup sequence to create. The setup sequence is described in more detail with reference to FIG. 5.

The keyboard driver 422 in turn communicates with the keyboard controller hardware 432 , which can be, for example, a conventional PS / 2 keyboard input / output system, a universal serial bus interface and, at least in some versions, also a four-wire keyboard interface. as described in the aforementioned U.S. Patent 4,706,068. In the same way, mouse driver 424 typically also communicates with mouse input and output system 434 at appropriate times. During all of these operations, the flash file and memory service portions 426 of the terminal operating system are typically extracted from the flash and RAM memory.

As stated clearly in connection with FIG. 5, allows the setup procedure to specify the configuration information on the terminal users, including those para meters such as the network interface and related Configurati details, language, color, or other parameters. Once these parameters are specified, the data is stored in the connection data files 440 .

At this point, the user is ready to exit Terminal Setup Module 414 and return to EXEC.COM. If allowed to continue, EXEC.COM process 412 may be branched 416 into the network connection module. The network connection module 340 begins by retrieving the data stored in the connection data file 440 and the command line of the connection module, which tells the application server how to connect to the rest of the driver and hardware layers of the terminal. In particular, the network connection module communicates with the keyboard driver 422 , the mouse driver 424 , the video input / output system 428 and the file and storage service part 426 of the terminal operating system. In addition, the network connection module also connects a hardware-configured serial interface 442 and, in some versions, also a hardware-network interface 444 . Network drivers 444 , in one embodiment, are out of RAM 116 , but may also be out of flash memory 112 . The serial interface 442 can be a conventional RS232 interface, but also another form of a serial connection, such as the universal serial bus or USB.

The operation of the GUI machine 420 , as shown in FIG. 5 and how it runs during the setup module of the terminal 12 , is described in more detail with reference to FIG. 6. The GUI machine only works during setup mode and provides a rudimentary, graphical user interface during the configuration operation.

As already mentioned in connection with the description of FIG. 5, the operation according to FIG. 6 starts when the setup sequence is called during the boot phase of the terminal. This setup sequence can be called up by a sequence of keystrokes or in any other suitable manner. The setup sequence starts with a call to the setup code 502 , which in turn obtains information from the setup data file 418 . The setup data file 418 identifies the various configuration options available in the terminal. The setup code 502 communicates bidirectionally with a RAM structure 504 and also causes existing connection information to be written from the connection data file 440 into the RAM structure 504 . The GUI engine 420 also communicates bidirectionally with the RAM structure to set and display current information in an arrangement described below as areas, groups, and selections. In addition, a hardware interface 506 provides video information to the video controller 430 while responding to the information received by the user via the mouse 260 or the keyboard 250 .

The setup code allows the user to go through a plurality of configuration menus for the operating characteristics of the terminal, such as. B. the language to be displayed on the terminal, the type of network connection, etc. FIG. 7A shows a representation of a setup screen as it is used in the configuration mode of the terminal. In a preferred embodiment, the setup screens are shown graphically. When the user cycles through these configuration screens, the configuration data can be selectively updated by the user using the keyboard and mouse. The updated data is retained in RAM structure 504 before it is written to connection data files 436 . However, in a currently preferred embodiment, certain data can be updated dynamically while other data is not updated until the setup sequence is complete. Upon completion of the setup sequence, including the writing of any remaining configuration data to the connection data files 436 , the setup sequence ends and returns to EXEC.COM 325 to initiate the network connection module 340 shown in FIG. 5.

Back again to FIG. 7A; there the entire window in which the files appear is referred to here as area 600 . Within each area 600 are one or more groups 610 , and each group 610 has one or more selections 620 . Thus, in the example of FIG. 7A, the "communications" group includes the choices of Serial Port, TCP / IP, SPX and IPX, each associated with a region 630 that indicates that this selection has been made or selected .

With reference to Fig. 7B1-7B3 associated with the con figurations software data structures are illustrated. In particular, a list of area pointers is found in AREA_LIST 700 . The structures pointed to by AREA_LIST include limits, size, titles and groups as they are assigned to all areas as defined in the setup process. As previously noted, each area appears as a window on the screen. In addition, all areas that are currently displayed are displayed in DISP_AREA_LIST 702 . In an exemplary embodiment, the first area listed is displayed as the floor area and the last area displayed is the top displayed area. In an exemplary embodiment, overlap of windows is permitted, although overlap is not necessarily required in all embodiments.

704 denotes the data structure for GROUP_LIST, which lists all groups that were defined in the SETUP process in all areas that were found in AREA_LIST 700 . As previously mentioned, each area contains one or more groups. An optional data structure 706 for a STRING_LIST can also be provided, and a FILE_LIST 708 is provided as a directory for "bitmap" images that can be used in many states in the various areas, groups and selections.

The structure of AREA_LIST results from 710 . It includes a block for an area ID 712 , a pointer to the next area 714 , a pointer to the previous area 716 and a structure pointer 718 . The structure pointer 718 associated with each area ID 712 points to an area structure 715 , which includes area ID 712 along with an ABS_X entry 720 and an ABS_Y entry 722 , by the position of that area with respect to the upper left corner of the screen mes specify (in a preferred embodiment of the inven tion). The area structure 715 further includes a ROWS entry 724 and a COLUMNS entry 726 , which together specify the size of the area. A FLAGS entry 728 specifies whether a border extends around the area. A TITLE_POSITION entry 730 and a TITLE_BAR entry 732 specify the text of the title and its arrangement within the title line of the area concerned, while a MAX_STR_LEN entry 734 specifies the maximum number of characters for the title.

In addition, the area structure 715 contains an entry 736 for the number of groups within a certain area. An AREA_MPTR entry 738 specifies the "hot spot" of the mouse pointer within the area, while an entry DEF_BUTTON 740 specifies which button within the area specifies the default. The standard button is activated when the "Enter" key is pressed. A CAN_BUTTON entry 742 specifies the "Cancel" button, which is activated when the "ESC" key is pressed. Finally, a list of pointers is specified at 744 A- 744 N, one for each group belonging to the area. Each group pointer 744 points to an associated group structure block 764 , as set forth below. A "hot key" list can also be defined for the area.

The structure of DISP_AREA_LIST shown at 748 is essentially identical to the structure of AREA_LIST 700 and contains blocks for the area ID, the next area, the previous area and structure pointer. As with AREA_LIST 700 , DISP_AREA_LIST 748 also points to area structure 715 . A similar structure is shown for GROUP_LIST 704 at 750 and includes a group ID 752 , a pointer to the next group 754 , a pointer to a previous group 756, and a group structure pointer 758 . A similar structure can also be provided for the optional STRING_LIST 706 , and it can have a string (string) ID 760 , a pointer to the next string 762 , a pointer to the previous string 764 and a string structure pointer 766 .

It will come back to the group structure pointer 758 again. This points to the group structure block 746 and contains the group ID 752 , a PARENT_SELECT_ID entry 780 in order to identify the selection which, as soon as it is activated, automatically rolls up this group, a HOTSPOT_COUNT entry 782 in order to determine the number of mouse Identify "hot spots" within the group and also GSTART_X 784 and GSTARTY 786 entries to determine the relative location of the group within the area. In a preferred embodiment, both the location of the group and the selection are specified with respect to the upper left corner of the area containing them; but other relationships that appear acceptable can also be defined, e.g. B. specifying the location of a selection relative to the location of its group. The most important thing is to ensure that all features of an area maintain their position within the area when the area is moved.

The group structure block 746 also includes ROWS and COLUMNS entries 788 and 790 , respectively, to determine the size of the group, as well as a GFLAGS entry 792 , to define the outline of the group. In addition, a QUICK_KEY_POSITION entry 794 and a QUICK_KEY_STROKES entry 796 can be specified for "hot key" combinations that are assigned to the group.

Furthermore and similar to the area structure, entries for title position 798 , group label 800 and MAX_STR_LEN 802 can be provided. In addition, a NUM_OF_SELECTS entry 804 is provided to identify the number of selections contained in a group. Next, an entry 806 for AID_ATTACH is provided as a back reference to area ID 712 to which the special group belongs. The AID_ATTACH entry 806 is not required in all cases, but at least improves the execution in some states. Finally, a list of pointer entries 808 A through 808 N each point to a selected structure that is associated with the particular group. As explained in more detail below, a variety of selection structures can be associated with each group, but some elements are common to the different types. Therefore, the first pointer 808 A points to a SELECT_COMMON structure block 810 . Returning to the area structure block 715 , the standard button entry 740 and the "CANCEL" button entry 742 also point to the common selection structure block 810 .

The SELECT_COMMON structure block 810 contains a selection ID entry 812 , an entry 814 which gives a back reference to the group ID, a REL_X and REL_Y entry 816 or 818 together with ROWS and COLS entries 820 or 822 to determine the location and to specify the size of the selection, a QUICK_KEY_POS and a QUICK_KEY_CHR entry 824 and 826 , respectively, to specify the "hot key" combinations associated with the selection, a MAX_STR_LEN entry 828, and a selection string 830 around the to specify the maximum size and title of the selection, and an SFLAGS entry 832 to specify the properties of the selection.

A SELECT_TYPE entry 834 is also provided. As previously discussed, various types of selections are available, and reference is made to FIG. 7A. The different types of selections that are available within a group depend on the type of data required for this step of configuring the terminal. In some examples, the selection is just pressing a button (buttons 640 ); in other examples, the selection is to enable and disable a feature, such as a test block (see 650 in Figure 7A); in other examples, one of several selections must be made, as illustrated by the "Communication" 660 and "Serial Port" 670 groups in FIG. 7A. According to further examples, an image can be selected, while for other special text must be selected. In some examples, fields must be completed ( 680 in Figure 7A), while in others one of several fields must be completed. Although these types of selections have been implemented in an exemplary embodiment, the list is by no means to be considered complete and, of course, other selections from the technical teaching given here can also be easily implemented.

For a selection "Fill", cursor start and cursor end entries 836 and 838 are provided, together with a "First Displayed" entry 840 for identifying the character from which the character string is to be displayed. In addition, both a LABEL_REL_X entry 842 and a LABEL_REL_Y entry 844 and a LABEL_STR entry 846 are provided.

Entries of NUM_OF_SEL_ROWS 848 and NUM_OF_SEL_COLS 850 are provided for a selection type "one of many". Entries are also provided for the number of options 852 and the "default" option 854 , as well as a quick key pointer 856 and a flag pointer 858 to identify the number of options that are active. Finally, there is a SEL_STR_SIZE 860 .

For an "image" type of selection, only one entry is required for file ID 708 and an image pointer 862 must be specified.

For a "field" type of selection there is a "child group" ID entry 864 together with a child group (= offshoot group) pointer which points to a group structure of the type shown with the group structure block 746 . The branch group is called up automatically as soon as the parent selection is activated and one of a group of fields is selected.

For a "List of Strings" selection, entries for the number of options 868 , the maximum length of the option title (or MAX_OP_LEN) 870 , an entry 872 for the horizontal display offset, an entry 874 for the vertical display offset, together with an X-label position 878 and a Y-label position 880 . Finally, a label string 882 and an entry 884 are provided for the size of the string of the selection.

Returning to AREA_MPTR entry 738 , the mouse pointer "hot spot" is specified by a structure that includes an area ID entry 900 , a group ID entry 902 and a selection ID 904 . In addition, an option selection type 906 is provided which specifies the type of selection with which a special "hot spot" is associated. There are also back references entries 908 and 910 for the group ID within the range and the selection ID within the group. Furthermore, four entries 912 A-D specify both the upper left X and Y positions and the lower right X and Y positions for the mouse display point ("hot spot"), together with an entry 914 for a mouse identifier ("flag"), which causes the mouse display point to be activated as soon as the correct menu is displayed. In addition to the viewpoints just described, additional viewpoints are provided at the beginning and end of each display list to allow scrolling, and the like are found in the title bar area of an area so that the area window can be moved.

In addition to the aforementioned structures, a data structure is also provided in order to retain the currently selected entries from the various selection options. The current data structure block is shown at 950 and contains an entry 952 for the number of areas currently defined by the SETUP; entry 954 indicates how many image files are defined; Entries 956 and 958 indicate how many groups and selections have been defined, an entry 960 is used to assign a predetermined maximum number of selections. In an exemplary embodiment, the maximum number of selections is assigned in blocks of ten.

Additional entries 962 and 964 are provided for the number of pixels per column or row, as well as an entry for the font 966 , an area focus entry 968 , a group focus entry 970 and a string focus entry 972 . There is also a mouse focus entry 974 for specifying the display point. OFOCUS and TFOCUS entries 976 and 978 can also be provided in order to specify the selected selection options and selection types with a keyboard focus. Still further there are IFOCUS and JFOCUS entries 980 and 982 for the "hot spot" entries 908 and 910 from the mouse structure block described above. Finally, a menu entry 986 specifies the identification of the current menu focus, together with entries 988 and 990 for defining the area and group frames, together with an OFLAGS entry for specifying the mouse modes.

The information specifying the current status of the selections is located in an ACTIVE SELECT structure 1000 . Each structure includes a button entry 1002 , an STFLAGS or selection common FLAGS entry 1004, and an active entry that stores the current status of all selections from which this data can be made available for the SETUP code.

In a preferred embodiment, an event queue structure 1010 can also be fed in to record keystrokes or mouse movements in an event queue.

As stated earlier, it is a key feature of the present the invention that the operating system of the terminal Invention not with a standard PC / AT BIOS or DOS is compatible. Nevertheless, it is necessary that the terminal loading drive system supports certain functions to the ability Display application files in a multi-user environment keep, like when communicating with a CITRIX client or other supported emulations. You can have a list with Set up standard IO.SYS and BIOS.SYS functions, which of the present invention are supported; for the specialist it is clear that not all standard BIOS or DOS functions must be included. Some functions won't supported. Other features are only partially supported. This is how the function 36h (Get Disk Free Space) becomes disk space) is therefore only partially supported, because a flash memory instead of a hard disk (= hard disk) is used. Function 33h (Get / Set System Va lue) (= determine / set system value) in this respect depending on supports the function and the flag, but the "Control-Bre ak "function is not supported. In the same way the functions 2Ah to 2Dh (the Get / Set Date / Time, i.e. le / set date / time, functions) only partially supported, because no real-time hardware in the terminal of the present invention is available. Only the "Get Time" radio tion is supported so that it can be used to measure the duration of Events can be used without the absolute time to play.

In addition, the flash file system is in a preferred embodiment Form of the invention in several single directory drives partitioned. However, the flash file system is in contrast to conventional disk file systems no division into clusters or sectors. Files in any drive or par tition grow from bottom to top in the partition, while the  Directory entries grow from top to bottom. Data will saved continuously without fragmentation. The directory nis entries that are sixteen in a preferred embodiment Bytes long generally correspond to a DOS directory wear; however, items that are normally reserved would be defined to allow a file from the Flash instead of running from the DRAM. This excludes the Start address of the file in Flash as well as the return image segment of the file in the DOS address space.

File deletion is more conventional than deletion DOS files are largely similar, but differ in important ones Details. When a file is deleted in the present invention the first byte in the directory entry is set to 0 instead of E5h. This step is done without deletion a flash block. Subsequent files are then in the next registered available space. However, if for one the following file does not have enough space, the flash block for the deleted file is deleted and unused deleted files are written back into the flash block where the deleted file was kept. How nice previously mentioned, file fragmentation is at least in some Embodiments are not allowed.

The flash file system supports conventional DIR, TYPE and DEL commands, supports a new "DEBUGMSG" command for Er generation of a DEBUG message and also supports program execution guided tours through batch files. The file system also supports the AUTOEXEC.BAT file and also loading and executing * .EXE and * .COM files and Int 21h and Int 27h. However supports the file system in at least some embodiments, not the CONFIG.SYS file or .SYS device driver. Likewise under the file system does not support the batch file commands (except Pro program execution), I / O redirections, pipes or interrupts 20h (End program), 22h (end address), 23h (Ctrl-Break Leave address), 24h (critical errors settlement vector), 25 h (Absolute Disk Read), 26h (Absolute Disk Write) and 2Fh  (Multiplex interrupt).

From the foregoing it is clear that while a selected group of the standard BIOS and DOS functions are emulated or otherwise supported by the terminal operating system of the present invention, a very significant number of the standard BIOS and DOS functions are not supported . In addition, even those BIOS and DOS functions that are supported cannot be carried out under standard AT compatible hardware. Instead, the portion of the terminal operating system, referred to in FIG. 4 as "boot block" 300 and "kernel" 305 , establishes the ability to emulate these functions.

The service functions supported by boot block 300 include: GET FLASH DRIVE SIZE, which queries flash memory 438 for the drive size; READ FLASH DRIVE for reading data from flash memory 438 ; WRITE FLASH DRIVE for writing data into flash memory 438 ; GET FLASH DRIVE BLOCK SIZE to query the block size of the memory 438 ; ERASE FLASH DRIVE BLOCK to erase data from memory 438 ; WARM REBOOT is used in the manufacturer test to repeatedly loop through the switch-on diagnosis, but is not used in normal operation; GET BOOT BLOCK DATE to query the data of the boot block; CLEAR KEYBOARD CONTROLLER I / O BIT is used to control components that are connected to the keyboard controller; and finally SET KEYBOARD CONTROLLER I / O BIT to set the keyboard controller.

The operation of the kernel 305 will now be described in detail. The kernel essentially comprises three service functions. The first is an "ACTIVE VIDEO INT 10h" function, which activates the normal int 10h functions for video services. Interrupt int 10h is initially intercepted by kernel 305 to suppress the display of text mode messages from the various device drivers as they are loaded. After the drivers are all loaded and the terminal goes into graphics mode, the ACTIVE VIDEO INT 10h function is called to reset the normal int 10h operation. In addition, the kernel 305 includes a second function, the "SET POWER DOWN TIME", which can set various power saving functions (such as "ENERGY STAR compliance") and a time delay to activate these functions. Finally, kernel 305 includes a "PROCESS DOS INTERRUPTS" function which can be called from the boot block or other parts of kernel 305 whenever it is necessary to execute pending DOS interrupts which require real time processing in a DOS environment . The most frequently executed interrupts in this function are mouse and keyboard interrupts, although timer, serial, parallel and network interrupts also occur. The capture by this function prevents, for example, that mouse and keyboard interrupts remain switched off for a longer period - whereby long enough for a user, for example, there may be a delay of one second between the movement of the mouse and the subsequent movement of the cursor - or to clear the keyboard controller output when it is necessary to send a command to the keyboard controller.

Because the hardware of the present invention is not PC / AT Stan dard corresponds and the firmware neither the conventional PC / AT BIOS still corresponds to DOS, but the whole system does so is laid to allow the user a conventional Seeing WINDOWS® display in front of you and interacting with it, need some conventional hardware interrupts and related Calls are managed by the present invention. In In a preferred embodiment, such interrupts and Calls with the terminal firmware are handled, either by Emulation or by modifying the appropriate response the incoming signal. These responses are de below Waisted described using the kernel.

The kernel puts the processor in a virtual 8086 mode and sets up various tables as they are used to capture  I / O's on the various ports are necessary. After an access generates a process interruption on a selected port, becomes this instruction that creates this interrupt has broken it down so that the kernel can process it correctly to to emulate a PC compatibility, which ver the transmission various groups of characteristics (so-called "personalities"). Because a whole subroutine for every I / O instruction captured must be processed, the I / O instruction is not so executed quickly, so that the interception of I / O's on little Ports is limited as possible. In some examples all or only part of an I / O port only as far (with inter rupts) interrupted as required for AT compatibility is. Based on the fact that it is intended that the most preferred embodiment of the present invention CITRIX WinFrame feature group is to be emphasized that other feature groups for the use of the terminal of the present invention can be implemented. In some For examples, the terminal of the present invention can be found in Stores have diverse groups of features, the term nal can be connected to many hosts under different operating systems, and therefore such different ones Characteristic groups expect. The user or others can then be able to choose from among these feature groups and by a "hot key" or a keyboard sequence, the Kernel of the present invention then the corresponding characteristics calls data from the memory and a communication with the appropriate host.

The I / O ports used by the kernel to create an AT com compatibility are:

20h (the command port of an AT-compatible interrupt controller) - Only the "end of interrupt" command is emulated, which on End of each interrupt execution program is issued so more interrupts of the same or lower priority occur can. The kernel also emulates the normal operation of a PC compatible interrupt controller, as far as these interrupts  blocked of equal or lower priority until the "end of the interrupt "command is received.

21h (The mask register of the AT-compatible interrupt control lers) - Is emulated.

40h-43h (access to an AT-compatible 8354 system timer) - The ports are not emulated, but intercepted because of some write to AT-based drivers in these ports. Since the In terrupt mask register according to a preferred embodiment of the present invention is set to port 40h not captured enrollments with the interrupt mask registers of the present invention collide.

61h (One control port for different applications in one AT architecture) - A speaker control bit is emulated to it to enable the speaker to be turned on and off.

A0h (The command port of a second interrupt controller one AT-compatible computer) - As with port 20h, the "end of the Interrupts "command emulated.

A1h (The mask register for the second interrupt controller (similar to port 21h)) - Is emulated.

2F8h to 2FFh (A standard address for a second AT com patible serial port) - These ports are on 5F0h to 5FEh offset, the port addresses for the second serial port one preferred embodiment of the invention. The new port range (5F0 to 5FE) includes only "even" addresses. In one at playful embodiment, "byte swapping" is not in the has been implemented and therefore can only be "even" bytes one of the eight-bit SIO component can be accessed. Indeed can also implement "BYTE swapping" if necessary will.

378h to 37Fh (A standard address for an AT compatible  parallel port) - Is converted to 6F0h to 6FEh, which the Port addresses for the parallel port of an example off are leadership form of the invention.

3F8h to 3FFh (a standard address for a first AT-com patible serial port) - Are implemented at 7F0h to 7FEh, which includes the port addresses for the first serial port playful embodiment of the invention.

So far the preferred embodiments of the invention there are numerous modifications and similar solutions that are not based on the revelation content of the Lead invention out. The invention is therefore in no way up the described embodiments are limited.

Claims (5)

1. Terminal for displaying application program information in a window environment, characterized by
Processing steps that are not fully compatible with a personal computer BIOS or disk operating system (DOS = Disk Operating System), but are adapted for receiving window information supplied by programs that are on a remote application server run as well
by a display device for displaying the window information. 2. A terminal adapted for communication with a host selected from a plurality of host systems, each of the host systems using a different communication protocol, comprising:
a first feature group for providing responses to a first and a second set of instructions, which are provided by a first host system according to the communication protocol belonging to the first host system, at least a second feature group for providing responses to a third and a fourth set of instructions provided by a second host system in accordance with the communication protocol associated with the second host system, at least one of the host systems providing window information, further comprising processor devices that point to the first and at least the second Feature group for processing one of the first and third set of instructions and for emulating one of the second and fourth set of instructions, for providing responses to the associated host system that are compatible with the communication protocol associated with that host system, and
Switching devices for identifying the host system to which the terminal is currently connected and for selecting the appropriate one of the first and at least the second group of features for communications with the identified host system. 3. A method of updating operational characteristics of a terminal, comprising the following steps:
Making a flash memory available for storing operating characteristics,
Providing a communication link to a host for receiving updated operational characteristics,
Establishing a first operating state during which at least a predetermined part of the flash memory can be written while the communication with the host is maintained,
Downloading the updated operating characteristics from the host to the terminal while the terminal is in the first operating state,
Writing the updated operating characteristics into the flash memory while the terminal is in the first operating state, and
Establishing a second operating state during which data is not written to the predetermined part of the flash memory. 4. Terminal for displaying - in the Microsoft WINDOWS® operating environment - application program information provided by a host system on which a Microsoft WINDOWS® operating system is running
an interface device for receiving display information from the application server for an application program running on the application server,
Processing devices that are not fully compatible with the personal computer BIOS or disk operating systems and are incapable of executing the application program locally and are responsive to the interface devices, either for emulating or processing instructions provided by programs that run on a remote application server to provide responses to the host system that are compatible with those expected from the host system, and
Display devices responsive to the processing devices to display the window information. 5. Procedure for configuring a terminal with a display for communication with a host system, with the following procedure steps:
Producing at least one bitmap area within a region of the display,
Establish at least one bit-mapped group within the area, and
Establish at least one bitmapped selection within the group, with each selection being accompanied by one or more choices.