DOCSLIB.ORG

Accessing Windows Applications from Unix and Vice Versa

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Accessing Windows Applications from Unix and Vice Versa 50-20-42 DATA COMMUNICATIONS MANAGEMENT ACCESSING WINDOWS APPLICATIONS FROM UNIX AND VICE VERSA Raj Rajagopal INSIDE Accessing Windows Applications from an X-Station, Coexistence Options, Windows in an X-Station, Accessing Windows Applications, Accessing UNIX Applications from Windows Desktops, Emulators Migrating from one environment to another takes planning, resources and, most importantly, time (except in very trivial cases). This implies that even if eventually migrating to another environment, one still has to deal with coexistence among environments in the interim. In many com- panies it would make good business sense not to migrate legacy systems at all. Instead, it may be better to develop new systems in the desired en- vironment and phase out the legacy applications. The data created by the legacy applications is important and one must ensure that data can be ac- cessed from a new environment. Coexistence considerations are very im- portant in this case. Coexistence between Windows PAYOFF IDEA NT, UNIX, and NetWare deals with a Some users want applications they develop in number of related issues. One may one environment to execute in other environ- need to access Windows applications ments with very little change. With this approach, they can continue to develop applications with from a UNIX machine or need to ac- the confidence that they will execute in another cess UNIX applications from Win- environment even if the environments change in dows desktops. One may prefer to the future. In applications that can run in both have the same type of desktop (Òan Windows NT and UNIX, this can be accomplished enterprise desktopÓ) for all users and in several ways: be able to access different environ- •use APIs — there are three flavors of this ap- ments. One may also need to emulate proach one environment within another. •layered APIs that reside on top of native APIs It may also be necessary to access •layered APIs plus extensions •emulated APIs services such as file and print servic- •use Win32 and port to UNIX es in heterogeneous environments. A •use POSIX and port to Win32 Auerbach Publications © 1999 CRC Press LLC EXHIBIT 1 — Heterogeneous Client Interconnectivity It may also be necessary to access services such as file and print ser- vices in heterogeneous environments. A set of interoperability products exists to enable clients attached to one type of server (e.g., UNIX, Net- Ware, and Windows NT) to have transparent access to services from oth- er servers and mainframes, as shown in Exhibit 1. As mentioned earlier, access to the data available in another environ- ment is very important and heterogeneous file access is needed. ACCESSING WINDOWS APPLICATIONS FROM AN X-STATION The previous article discussed the different options for porting or migrat- ing applications between environments. There are situations where port- ing would make good business sense. There are other situations where the best business option would be to leave applications running in one environment and access these applications from other environments. There are many organizations that have existing UNIX applications that are satisfactory. They are also using Windows desktops, primarily for of- fice needs. An important requirement is to access the Windows office ap- plications from the same X-stations that are already accessing the UNIX applications. An X-station includes X-terminals, UNIX workstations, and any device capable of performing a similar function. Organizations can provide access to different environments and appli- cations by providing separate systems on users’ desks or arrange a shared pool of machines. There are other options that provide access to applications executing in different environments from the same desktop. These are called coex- istence options. Using coexistence options, different applications are ac- cessed in multiple windows on the same desktop, transparently, to the user. Coexistence options may avoid the necessity to port applications, but keep in mind that there are subtle end-user differences between the user interface used in UNIX and that used in Windows. These differences could become an annoying factor for a user to deal with, particularly if the user has to switch back and forth between Windows and UNIX ap- plications often. Another potential problem is the lack of some Windows functionality, such as OLE and Clipboard, when these functions are not supported by the coexistence solution provider. COEXISTENCE OPTIONS There are several ways in which applications in different heterogeneous environments can coexist. These include: • In an environment where X-stations or X-terminals are already con- nected to different applications, Windows applications can be added to the X-station. Examples of this coexistence approach include WinDD from Tektronix, X Connection from ConnectSoft, and Win- Center from Network Computing Devices. Adding Windows applica- tions to an X-station is covered in this article. • Just as Windows can be added to an existing X-station, an X-server can be added to a PC that may already be running Windows applica- tions to access non-Windows applications. Examples of this coexist- ence approach include DESQview/X from Quarterdeck, and eXceed from Hummingbird Communications. X-server on Windows is cov- ered later in this article. • To cater to the needs of desktops capable of working in heteroge- neous environments, some vendors have developed machines with features useful for operating in heterogeneous environments. Such features include different connectivity options to connect to different networks. Examples of this coexistence approach include Personal Workstations from Digital, which are multi-client desktops. • There are emulation solutions that permit an executable developed in one environment to run on another through emulation. The emu- lation solutions interface between the application executable and the operating environment. Examples of emulation solutions include Windows Binary Application Interface (WABI), SoftWindows from In- signia, and MERGE from Locus Computing. • In some instances, the applications and users’ access are fine, but an individual may want to access the data across environments. There are solutions that permit applications to have file access in heteroge- neous networked environments. Examples of networked file access EXHIBIT 2 — Windows in an X-Station solutions include BW-Connect NFS, Chameleon 32 NFS, and PC-In- terface, and PC-NFS from Intergraph. WINDOWS IN AN X-STATION An overview of how a Windows application can be added to an existing X-station is shown in Exhibit 2. The X-station may already be attached to an IBM mainframe applica- tion using a 3270 emulation window, to a VAX application, and to a UNIX application as an X-server. The Windows application is enabled as another window on the X-station and the new window is controlled by an application server running the Windows application. How Do X-Stations Support Windows Applications? A simplified, conceptual view of how X-stations support Windows Appli- cations is shown in Exhibit 3. The Windows application performs its application processing and in- vokes the operating system for end-user display services. Typically, the display is physically attached to the same machine on which the applica- tion runs but that need not always be the case. The X-station vendors provide a server piece and a client piece that comes in between the Windows application and the display and interfac- es between the two. The client passes user responses, such as keystrokes and mouse clicks, to the server which passes them to the Windows ap- EXHIBIT 3 — X-Station Support for Windows Applications plication. The Windows application responds to the user input just as it normally would. The application server sends the output from the Windows application back to the client. The user sees the regular Windows application screens. The protocols used for the exchange between the application server and the client is the X Windows protocol or the intelligent console architecture (ICA) protocol. The connection between the application server and the client could be LANs (if it local), intranets, or even the Internet. Do not confuse the X-station approach with keeping applications on a file server and loading them locally for execution. With X-stations, the Windows applications run on an NT server which has been modified to add multi-user support, and not locally. Note on protocols: the X Windows protocol is the industry standard protocol for communication between a client and an X-server. Use of X protocol permits the use of any device that follows the protocol. The ICA is similar to the X Window protocol. ICA is a proprietary protocol devel- oped by Citrix Systems. Citrix has licensed this protocol to some vendors (e.g., Tektronix and Network Computing Devices). Microsoft recently announced that it will include ICA support in future versions of Windows 95 and NT, and, potentially, in Internet Explorer. By using the ICA protocol, vendors have been able to provide more func- tionality and faster responses than the X Window protocol. The ICA pro- tocol transmits less data. However, some graphics-rich and multimedia applications do not run well with ICA. ICA supports only 256 colors. X- stations vendors typically offer a choice of protocols between which the user can alternate. Considerations in Using the X-Station Approach If one is a manager trying to decide if an X-station approach is right for your business, here are some advantages and disadvantages to consider. Advantages of the X-Station Approach. • Using an X-station approach may be able to provide access to Win- dows applications, such as office applications and e-mail, without having to buy a PC and Windows for every user. • It is easier to administer Windows applications usage since the actual Windows application is installed only on one machine (the applica- tion server). It is also easier to control usage and availability of the Windows applications.
Load more

Recommended publications
  • THINC: a Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices
    THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the Graduate School of Arts and Sciences COLUMBIA UNIVERSITY 2011 c 2011 Ricardo A. Baratto This work may be used in accordance with Creative Commons, Attribution-NonCommercial-NoDerivs License. For more information about that license, see http://creativecommons.org/licenses/by-nc-nd/3.0/. For other uses, please contact the author. ABSTRACT THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto THINC is a new virtual and remote display architecture for desktop computing. It has been designed to address the limitations and performance shortcomings of existing remote display technology, and to provide a building block around which novel desktop architectures can be built. THINC is architected around the notion of a virtual display device driver, a software-only component that behaves like a traditional device driver, but instead of managing specific hardware, enables desktop input and output to be intercepted, manipulated, and redirected at will. On top of this architecture, THINC introduces a simple, low-level, device-independent representation of display changes, and a number of novel optimizations and techniques to perform efficient interception and redirection of display output. This dissertation presents the design and implementation of THINC. It also intro- duces a number of novel systems which build upon THINC's architecture to provide new and improved desktop computing services. The contributions of this dissertation are as follows: • A high performance remote display system for LAN and WAN environments.
    [Show full text]
  • Solaris 10 807 Release Notes
    Solaris 10 8/07 Release Notes Oracle Corporation 500 Oracle Parkway Redwood City, CA 94065 U.S.A. Part No: 820–1259–13 August 2007 Copyright © 2008, 2011, Oracle and/or its affiliates. All rights reserved. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract,and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]
  • Why Os/2 Failed: Business Mistakes Compounded by Memory Prices
    Mountain Plains Journal of Business and Economics Volume 10 Issue 1 Article 4 Date Published: 10-1-2009 Why Os/2 Failed: Business Mistakes Compounded By Memory Prices Eric G. Swedin Weber State University Davis Follow this and additional works at: https://openspaces.unk.edu/mpjbt Part of the Business Commons Recommended Citation Swedin, E. G. (2009). Why Os/2 Failed: Business Mistakes Compounded By Memory Prices. Mountain Plains Journal of Business and Economics, 10(1). Retrieved from https://openspaces.unk.edu/mpjbt/ vol10/iss1/4 This Case Study is brought to you for free and open access by OpenSPACES@UNK: Scholarship, Preservation, and Creative Endeavors. It has been accepted for inclusion in Mountain Plains Journal of Business and Economics by an authorized editor of OpenSPACES@UNK: Scholarship, Preservation, and Creative Endeavors. For more information, please contact [email protected]. 36 WHY OS/2 FAILED: BUSINESS MISTAKES COMPOUNDED BY MEMORY PRICES ERIC G. SWEDIN WEBER STATE UNIVERSITY DAVIS ABSTRACT In 2006, IBM ended their support of OS/2, closing the book on an ambitious effort to create a modern operating system for the personal computer. IBM and Microsoft released the OS/2 operating system in December 1987 to replace the primitive DOS with a more sophisticated, preemptive multitasking operating system for personal computers. This article argues that OS/2 failed because of the U.S.-Japan Semiconductor Trade Agreement of 1986, subsequent accusations of DRAM chip dumping by the United States, and the resulting tariffs on Japanese memory chips, led to a memory chip shortage that drove up memory prices.
    [Show full text]
  • Operating Systems: – Kinds of Systems – Common Desktop Systems – User Interaction – Manage the Processor – Manage Memory
    Technology In Action © 2008 Prentice-Hall, Inc. 1 Technology In Action Chapter 5 Using System Software: The Operating System, Utility Programs, and File Management © 2008 Prentice-Hall, Inc. 2 Topics • System software • Operating systems: – Kinds of systems – Common desktop systems – User interaction – Manage the processor – Manage memory © 2008 Prentice-Hall, Inc. 3 Topics • Operating systems: – Manage hardware – Interact with application software – Start the computer – Keep the computer organized • Desktop and windows features • Utility programs © 2008 Prentice-Hall, Inc. 4 System Software Operating systems System utilities • Control computer • Programs that perform functions: computer housekeeping – Hardware tasks: – Memory – Manage system resources – Improve efficiency – Application programs – Virus prevention – System maintenance • Provide user interface © 2008 Prentice-Hall, Inc. 5 Operating System Categories • Four categories: – Real-Time (RTOS) – Single-User, Single-Task – Single-User, Multitask – Multiuser © 2008 Prentice-Hall, Inc. 6 Real-Time Operating Systems • Systems with a specific purpose and a certain result • Uses include: – Industrial machines – Robotic equipment – Automobiles – Video game consoles – Home appliances © 2008 Prentice-Hall, Inc. 7 Single-User Operating Systems Single-task systems Multitask systems • Perform one task at a time • Perform simultaneous tasks • PDAs: • Windows – Pocket PC • MAC OS – Palm OS • Linux – Windows Mobile • MS-DOS © 2008 Prentice-Hall, Inc. 8 Multiuser Operating Systems • Known as network operating systems • Allow access to the computer system by more than one user • Manage user requests • Systems include: – UNIX – Novell Netware – Windows Server 2003 © 2008 Prentice-Hall, Inc. 9 Desktop Operating Systems • Operating system combined with the processor is known as a platform – Microsoft Windows / Intel – Apple Macintosh / Motorola • Desktop operating systems include: – Microsoft Windows – MAC OS – UNIX – Linux © 2008 Prentice-Hall, Inc.
    [Show full text]
  • Iii Novell Client for DOS and Windows 3.1X ...Ix
    Novell Client for DOS and Windows 3.1x ..........................................ix ...............................................................................................................ix ...........................................................................................................1 ......................................................................................................2 ..................................................................................................................2 ......................................................................................................3 NetWare/IP ......................................................................................................3 ......................................................................................................4 IPX/IP ...............................................................................................................4 IP ...................................................................................5 IP ...............................................................................5 ......................................................................................................6 ..................................................................................................................6 !...................................................................................................6 "#$%&............................................................................................7
    [Show full text]
  • DR DOS for the Zfx86
    DR DOS for the ZFx86 Cost Effective, Reliable, Rapid Deployment of Embedded Systems w DR DOS on the ZFx86 gets products to market quickly at the lowest development and ownership cost. w Thousands of compatible applications, drivers and utilities available free or at minimal cost. w Full documentation available. DR DOS 7.03 Key Features of DR DOS Online Manual - DRDOS is supplied with a complete The ideal embedded DOS system, online manual that contains detailed information about all designed for out-of-the-box of the features of the operating system including the basic implementation into ROM or Flash commands, and the advanced utilities. It also has online ROM with tools and associated help available for all its commands. documents available in the DRDOS Memory Management - Memory management features OEM Documentation Kit. include a set of device drivers and commands that enable w 100% MS-DOS 6.22 compatible.. you to manage memory efficiently and make as much memory as possible available to your applications. w Comprehensive DOS utility set DOS Protected Mode Services - DOS Protected Mode w Multitasking, with API for developers Services (DPMS) interface allows specially-implemented w DPMS memory manager in addition to DPMI device drivers and TSRs to operate in extended memory. w Stacker disk compression This makes more memory within the first megabyte w NWCACHE - disk caching program available to applications and other conventionally-written drivers and TSRs. Both Stacker* (the disk compression w EMM386 memory manager program), and NWCACHE (the disk cache) use DPMS. w DOS Protected Mode Services (DPMS) Disk Compression - The disk compression component w Multitasking enables you to store more information by compressing the w DR-DOS provides a full multitasking environment data.
    [Show full text]
  • Microsoft Plays Hardball: Use of Exclusionary Pricing and Technical
    Antitrust Bulletin, XL:2, Summer 1995, 265-315 MICROSOFT PLAYS HARDBALL: The Use of Exclusionary Pricing and Technical Incompatibility to Maintain Monopoly Power in Markets for Operating System Software† by KENNETH C. BASEMAN* FREDERICK R. WARREN-BOULTON* and GLENN A. WOROCH** May 1995 ___________________ * Principals, MiCRA: Microeconomic Consulting and Research Associates, Inc., Washington, DC. ** University of California, Berkeley. † Forthcoming, Antitrust Bulletin, June 1995. We would like to express our appreciation for helpful comments and other assistance to Sturge Sobin, Linnet Harlan, Paul Dennis and the participants at the Columbia Business School's Institute for Tele-Information's Seminar on Sustaining Competition in Network Industries through Regulating and Pricing Access, especially Janusz Ordover and Bobby Willig. TABLE OF CONTENTS I. INTRODUCTION AND SUMMARY ................................... 1 II. BACKGROUND .................................................... 3 A. THE MARKET FOR PERSONAL COMPUTER OPERATING SYSTEMS ............................................................ 3 TABLE: NEW SHIPMENTS OF PERSONAL COMPUTER OPERATING SYSTEMS .............................................. 8 B. MICROSOFT'S PRACTICES ..................................... 9 III. FIRST-DEGREE PRICE DISCRIMINATION vs. INEFFICIENT SUBSTITUTION ................................................... 15 A. FIRST-DEGREE PRICE DISCRIMINATION ........................ 16 B. INEFFICIENT SUBSTITUTION ................................. 20 IV. ANTIFRAUD AND ANTIPIRACY
    [Show full text]
  • Building an out of the Box Raspberry Pi Modular Synthesizer J¨Urgenreuter
    Case Study: Building an Out Of The Box Raspberry Pi Modular Synthesizer J¨urgenReuter Karlsruhe, Germany, reuter [email protected] Abstract Headless Synth Modules The idea is simple and obvious: Take some Rasp- berry Pi computing units, each as a reusable syn- VCO VCA thesizer module. Connect them via a network. Con- nect a notebook or PC to control and monitor them. Start playing on your virtual analog modular syn- thesizer. However, is existing Linux audio software sufficiently mature to implement this vision out of Network the box? We investigate how far we get in building such a synthesizer, what existing software to choose with focus on networking, analyse what limits we Control Host hit and what features still need to be implemented (Synth GUI & to make our vision become reality. Configuration) Keywords Raspberry Pi, Virtual Anolog Modular Synthesizer, Figure 1: The Vision Distributed Networked Audio proach of a network of RPis reveals several ad- 1 The Vision vantages: The popular Raspberry Pi (or, shortly, RPi )[Raspberry Pi Foundation, 2014b] is a • Dedicated System. The RPis are solely small, cheap, yet powerful, computing unit with used for synthesis. The OS, residing on many I/O jacks with Linux/ARMv6 available an SD card, can be tailored to this pur- as operating system (OS). It is predestinated pose. Many services are irrelevant for head- for building networks of collaborative modules, less mode or use in a synthesizer and thus with each RPi taking over the role of a synthe- need not be installed, thus saving space sizer module with dedicated function as e.g.
    [Show full text]
  • Mai Mult a Minha Cultural Mini
    MAIMULT A MINHA US010063202B2CULTURAL MINI (12 ) United States Patent ( 10 ) Patent No. : US 10 ,063 , 202 B2 Kallai et al. (45 ) Date of Patent: Aug. 28 , 2018 ( 54 ) INTELLIGENTLY MODIFYING THE GAIN ( 56 ) References Cited PARAMETER OF A PLAYBACK DEVICE U . S . PATENT DOCUMENTS (71 ) Applicant : Sonos, Inc ., Santa Barbara , CA (US ) 3 ,956 ,591 A 5 / 1976 Gates , Jr. 4 , 105 ,974 A 8 / 1978 Rogers (72 ) Inventors : Christopher Kallai, Santa Barbara , CA D260 , 764 S 9 / 1981 Castagna et al . (US ) ; Mike Chamness , Gloucester, MA 4 ,296 ,278 A 10 / 1981 Cullison et al . (US ) ; Michael Darrell Andrew 4 , 306 , 114 A 12 / 1981 Callahan 4 , 382 , 158 A 5 / 1983 Ohshita et al . Ericson , Santa Barbara , CA (US ) 4 , 509 , 211 A 4 / 1985 Robbins D279 ,779 S 7 / 1985 Taylor ( 73 ) Assignee : SONOS, INC . , Santa Barbara , CA (US ) 4 ,530 ,091 A 7 / 1985 Crockett ( * ) Notice : Subject to any disclaimer , the term of this ( Continued ) patent is extended or adjusted under 35 U . S . C . 154 (b ) by 0 days . FOREIGN PATENT DOCUMENTS CA 2320451 A1 3 / 2001 ( 21) Appl. No. : 15 /670 , 769 CN 1598767 A 3 /2005 (22 ) Filed : Aug . 7 , 2017 ( Continued ) (65 ) ) Prior Publication Data OTHER PUBLICATIONS US 2017 /0346459 A1 Nov . 30 , 2017 “ 884 + Automatic Matrix Mixer Control System ,” Ivie Technolo gies, Inc. , 2000 , pp . 1 - 4 . Related U . S . Application Data (Continued ) (63 ) Continuation of application No . 13 /458 ,558 , filed on Apr. 27 , 2012 , now Pat. No . 9 ,729 , 115 . Primary Examiner — James Mooney (51 ) Int. Cl. HOZG 3 / 00 ( 2006 .
    [Show full text]
  • Real-Time Audio Servers on BSD Unix Derivatives
    Juha Erkkilä Real-Time Audio Servers on BSD Unix Derivatives Master's Thesis in Information Technology June 17, 2005 University of Jyväskylä Department of Mathematical Information Technology Jyväskylä Author: Juha Erkkilä Contact information: [email protected].fi Title: Real-Time Audio Servers on BSD Unix Derivatives Työn nimi: Reaaliaikaiset äänipalvelinsovellukset BSD Unix -johdannaisjärjestelmissä Project: Master's Thesis in Information Technology Page count: 146 Abstract: This paper covers real-time and interprocess communication features of 4.4BSD Unix derived operating systems, and especially their applicability for real- time audio servers. The research ground of bringing real-time properties to tradi- tional Unix operating systems (such as 4.4BSD) is covered. Included are some design ideas used in BSD-variants, such as using multithreaded kernels, and schedulers that can provide real-time guarantees to processes. Factors affecting the design of real- time audio servers are considered, especially the suitability of various interprocess communication facilities as mechanisms to pass audio data between applications. To test these mechanisms on a real operating system, an audio server and a client utilizing these techniques is written and tested on an OpenBSD operating system. The performance of the audio server and OpenBSD is analyzed, with attempts to identify some bottlenecks of real-time operation in the OpenBSD system. Suomenkielinen tiivistelmä: Tämä tutkielma kattaa reaaliaikaisuus- ja prosessien väliset kommunikaatio-ominaisuudet, keskittyen 4.4BSD Unix -johdannaisiin käyt- töjärjestelmiin, ja erityisesti siihen kuinka hyvin nämä soveltuvat reaaliaikaisille äänipalvelinsovelluksille. Tutkimusalueeseen sisältyy reaaliaikaisuusominaisuuk- sien tuominen perinteisiin Unix-käyttöjärjestelmiin (kuten 4.4BSD:hen). Mukana on suunnitteluideoita, joita on käytetty joissakin BSD-varianteissa, kuten säikeis- tetyt kernelit, ja skedulerit, jotka voivat tarjota reaaliaikaisuustakeita prosesseille.
    [Show full text]
  • Remote Command-Line Interface Installation and Reference Guide
    Remote Command-Line Interface Installation and Reference Guide Update 2 and later for ESX Server 3.5, ESX Server 3i version 3.5, VirtualCenter 2.5 Remote Command-Line Interface Installation and Reference Guide Remote Command-Line Interface Installation and Reference Guide Revision: 20090313 Item: EN-000082-01 You can find the most up-to-date technical documentation on our Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] © 2007–2009 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware, the VMware “boxes” logo and design, Virtual SMP and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents About This Book 5 Product Naming Conventions 5 1 Remote CLI Installation and Execution 9 List of Available Commands 10 Using the VMware Remote CLI 12 Installing and Executing Remote CLI Commands on Linux 13 Unpacking and Installing the Remote CLI Package 13 Executing Remote CLI Commands 14 Uninstalling the Remote CLI Package 15 Installing and Executing Remote CLI Commands on Windows 15 Installing
    [Show full text]
  • AIX Version 4.3 Differences Guide
    AIX Version 4.3 Differences Guide Richard Cutler, Zhu Li, Armin Roell International Technical Support Organization http://www.redbooks.ibm.com SG24-2014-01 International Technical Support Organization SG24-2014-01 AIX Version 4.3 Differences Guide December 1998 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix A, “Special Notices” on page 305. Second Edition (December 1998) This edition applies to AIX Version 4 Release 3, program number 5765-C34 and subsequent releases. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. JN9B Building 045 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1998. All rights reserved Note to U.S Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Figures . .xv Tables . xvii Preface . xix How this Redbook is Organized . xix The Team That Wrote This Redbook . xix Comments Welcome . xxi Chapter 1. Hardware Announcements . .1 1.1 RS/6000 7017 Enterprise Server Model S70 Advanced. .1 1.1.1 System Highlights . .1 1.1.2 I/O Drawer Specification . .2 1.2 RS/6000 43P 7043 Model 150 . .3 1.3 RS/6000 43P 7043 Model 260 . .4 1.4 GXT3000P PCI Graphics Accelerator . .6 1.5 Gigabit Ethernet-SX PCI Adapter .
    [Show full text]