Browse Prior Art Database

Enable Remote Full Screen Interface for a Thin Client

IP.com Disclosure Number: IPCOM000104627D
Original Publication Date: 1993-May-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 2 page(s) / 40K

Publishing Venue

IBM

Related People

Herrick, TR: AUTHOR [+4]

Abstract

The current version of Local Area Network (LAN) Server* does not provide the capability to run the Full Screen Interface (FSI) remotely from a domain controller or an additional server. The design changes described in this disclosure will enable FSI to run remotely from a domain controller or another server. A workstation which does not install the FSI component of Lan Server, a Thin Client, can save nearly 2.5 megabytes of disk space. The FSI code changes, which are described below, will enable users logged on at a Thin Client to run FSI remotely by accessing the FSI files from the domain controller or another remote server.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 81% of the total text.

Enable Remote Full Screen Interface for a Thin Client

      The current version of Local Area Network (LAN) Server* does
not provide the capability to run the Full Screen Interface (FSI)
remotely from a domain controller or an additional server.  The
design changes described in this disclosure will enable FSI to run
remotely from a domain controller or another server.  A workstation
which does not install the FSI component of Lan Server, a Thin
Client, can save nearly 2.5 megabytes of disk space.  The FSI code
changes, which are described below, will enable users logged on at a
Thin Client to run FSI remotely by accessing the FSI files from the
domain controller or another remote server.

      The current version of the FSI code assumes that all the FSI
files (executables and panel libraries) exist locally in the
\IBMLAN\NETPROG directory.  The full path name of the the local
\IBMLAN\NETPROG directory is used to access the FSI files.

      Instead of obtaining the local lanroot (\IBMLAN), search for
the FSI file in the PATH environment variable if it is an "exe" file
and in the DPATH environment variable if it is a "lib" file.  If the
search is successful, use that directory to access the FSI file.  The
directory found in the PATH or DPATH environment can be either local
or remote.  With the above changes to the FSI code, users at OS/2
Requesters, who do not have the full-screen interface files on their
workstation, can run the full-screen interface as...