3

Using the Network Computer

What next? might be a more appropriate title for this chapter. There really is no single answer to the What next? question. Your network computer is designed to be as flexible as possible so it can be tailored to fit your needs and your computing environment. This tailoring process is performed by your system administrator, with help from the installation and reference manuals that are included with the network computer software.

While it is not possible to explain step-by-step how to get started here, this chapter does provide general information to help you figure out What next? Typically, one of these scenarios occurs:

• A window manager starts automatically.
• A client starts automatically.
• Both a window manager and client start automatically.
• Nothing starts (leaving you to initiate an action).

The sections in this chapter contain information to help you identify what is taking place on your network computer, and what choices you can make. These topics are discussed:

• X Window Software Components
• Getting Unstuck
• Window Managers
• Sessions
• Running Clients
• Locking the Display
• Local Floppy Manager (LFM)

X Window Software Components

Before diving into the details of the possible scenarios, an introduction to some of the common software components and terminology will be helpful.

The X Window System is a windowing system developed to enhance the usability of a host computer by utilizing an X server as a device independent interface between the host computer and your network computer. This means that you can run clients on computers made by different manufacturers, freeing you to focus on your applications without worrying about computer differences. Another advantage is that X is multi-tasking, so multiple applications can run simultaneously in different windows.

The X server is the interface that translates client requests from your network computer to the host computer. It also accepts input data from your mouse and keyboard and generates the appropriate actions.

Windows are bounded areas displayed on your network computer screen that determine how information is presented on the screen. They can contain text or graphics (pictures, graphs, animated sequences) generated by your application programs, such as word processors, or transaction processing software. The X server controls what gets displayed inside each window. Information does not spill over from one window to the next.

A Window Manager is a special program that runs on top of the X server and provides an easy to use interface for you to run and work with your clients. These items include (among others):

• Window title bars
• Scroll bars
• Manipulating windows (sizing, moving, iconifying, closing)

Those are the visible results of using a window manager. The invisible portions may be even more important to you. These items include:

• Managing window communications to make sure the correct window receives the correct information.
• Determining where your mouse pointer is positioned, so it correctly interprets where you want it to read any input you generate.

Session Windows are various types of communication protocols to establish communications between your network computer and one or more host computers.

Clients are applications that run on an X server in a session window. Client means that the application is typically subordinate to the window. If the window is closed, the client also closes.

Getting Unstuck

Occasionally something may go wrong and your network computer or a client may get stuck or hang. Hang means the network computer or the client is not responding to any input coming from you or being transmitted from the host. This is often due to a busy network. There are three recommended ways to attempt to restore communications:

• Reset the X Server.
• Reboot the network computer.
• If the keyboard is also locked up, power off on the network computer.

Resetting the X Server

This is the first method to try:

1. Select Setup from the Client Launcher.
2. Click the Reset Server button.
3. When prompted that this closes existing connections, click the OK button.

The screen is blanked when the reset occurs. It may take a minute or two for the server to reset. Be patient and wait. When the root weave or your login method appears, log back in as usual. Refer to Chapter 2, Operating the Network Computer if you need information on logging in to the computer.

Rebooting the Network Computer

Sometimes rebooting is necessary, even though it adds to the network load. Try Resetting the X server before you reboot.

If Setup does not come up, or if resetting the server did not work, try rebooting the network computer. Press the key sequence: Ctrl-Alt-Delete to reboot the network computer. If the reboot is successful, the boot screen is displayed while your network computer boots. Refer to Chapter 2, Operating the Network Computer for more information on booting.

Powering Off the Logic Module (Base)

Note:

Turning off the power is the last-resort method. Try the other methods first, or call your system administrator for assistance.

If neither resetting the server nor rebooting the network computer works, turn the power off, then on with the power switch on your network computer logic module.

Window Managers

There are many different window managers available, but the concepts are similar. Several examples of window managers are:

• Motif (also called MWM)
• HP VUE (for Hewlett-Packard hosts)
• DECWindows (DEC hosts)
• XpressWare Window Manager (XPWM)

Your system administrator sets up and configures your window manager.

Determining Whether a Window Manager is Running

You can tell if a window manager is running by looking at the borders on an open window. If you do not have an open window, select Setup from the Client Launcher to display the Setup window. If a window manager is running, there is a border around the window, along with a title bar and usually some command buttons. Figure 3-1 illustrates a Telnet window with and without a window manager running.

Figure 3-1 Determining Whether a Window Manager is Running

Starting a Window Manager

If your system administrator configured your environment to automatically start a window manager, skip to the next section, Using a Window Manager.

Your system administrator must configure the window manager on your host computer before it can be used. If your network computer has the local MWM option, you can start it from Client Launcher. If the option does not appear, your network computer does not have it. Contact your system administrator.

To start the local MWM or XPWM from the default Client Launcher:

1. Open the Window Managers submenu.
2. Select MWM or XPWM.

Note:

If MWM is not available, or if you use another window manager, call your system administrator. The command for starting a window manager is specific to your host and configuration.

Using a Window Manager

The examples in this section are based on Motif, a host independent window manager included with your network computer software. Host independent means that it runs on hosts from different operating systems, rather than a proprietary manager such as HP VUE which is intended only for Hewlett-Packard systems. Your windows may look and operate differently from those described here because you are using a different window manager or because your system administrator has customized your MWM settings. Refer to your window manager documentation for more information.

Figure 3-2 shows a typical window and its standard elements. A window usually has command buttons for menu access, and to minimize and maximize the window. Try the various buttons displayed with your windows.

In addition to the window menu and buttons, there are typically pop-up menus that you can access outside of a window. These menus are controlled by various system files. To see if you have these pop-up menus:

1. Position the pointer outside of all windows.
2. Try pressing either the Select or Custom mouse buttons to see if a menu appears. Information on the menu choices would be included in your window manager or host documentation.

Figure 3-2 Elements of a Window

These window manipulations (actions) are described in this section:

• Moving a window
• Resizing a window
• Raising a window
• Lowering a window
• Maximizing a window
• Iconifying a window
• Restoring an icon
• Moving an icon

Figure 3-3 shows how to move a window.

Figure 3-3 Moving a Window

You can move windows from one location to another on the display.

1. Position the pointer within the title bar or border of the window.
2. Drag the pointer. When you begin moving the window, the pointer changes to a cross-arrow pointer and a window outline appears. As you move the pointer, the outline tracks the movement. A small rectangle appears in the center of the screen and displays the x and y coordinates of the window as the window moves.
3. Once the window is in the desired location, release the mouse button. The window appears in the new location and becomes the active window.

Figure 3-4 shows an alternate method for moving or resizing a window: Drag on the Window Menu, release on Move, position the window outline (by moving the mouse), and click a mouse button.

Figure 3-4 Resizing a Window

Many windows can be resized. The corners of the window border let you resize the window in two directions, while the horizontal borders and vertical borders let you resize the window in a single direction.

1. Position the pointer on the window border or resize corner controlling the window side(s) you want to resize. The pointer changes to either an arrow with a corner (for resizing two sides) or to an arrow with a perpendicular bar (for resizing in one direction).
2. Drag the corner or window border in the direction desired. As you resize the window, an image of the moving border(s) tracks the pointer movement.
3. Release the mouse button. The window appears in the new size.

Alternate method: Drag on the Window Menu, release on Size, position the window outline (by moving the mouse), and click a mouse button.

Figure 3-5 shows how to raise a window to the foreground.

Figure 3-5 Raising a Window: Displaying a Window in Foreground

When you want to raise a window; that is, display the window in front of other overlapping windows so you can see the entire window, follow these steps:

1. Position the pointer (cursor) anywhere in the window (except on a command button).
2. Click the Select mouse button. Raising a window automatically makes that window active. Windows cannot be raised from the Window Menu.

Note:

There is an X feature called autoraise. If this feature is configured for your window manager, windows are automatically raised as soon as you position your mouse pointer in the window.

Figure 3-6 shows how to lower a window to the background.

Figure 3-6 Lowering a Window

To place a window behind overlapping windows:

1. Drag on the Window Menu in the window to lower.
2. Release on Lower.

Figure 3-7 shows how to maximize a window.

Figure 3-7 Maximizing a Window

A window can be maximized to take up the entire size of the display. Some clients do not support maximized windows.

1. Click the Maximize button in the window you want to maximize.
2. To return the window to its original size, click the Maximize button again.

Alternate method: Drag on the Window Menu and release on Maximize.

Figure 3-8 shows how to collapse a window down to an icon.

Figure 3-8 Iconifying a Window

Iconifying a window means to collapse it down to an icon, a small graphic representation of the window. This helps you keep multiple windows organized and easy to access. To iconify a window:

Click the Minimize button in the window you want to iconify.

Alternate method: Drag the Window Menu and release on Minimize.

MWM has a client called Icons. If this client is available, it provides a box to hold and sort all of your icons.

Figure 3-9 illustrates how to restore an icon to a window.

Figure 3-9 Restoring an Icon

You can change an icon into a window whenever you want to view the window contents or work in the window. To restore an icon:

Double-click the Select button on the icon you want to restore.

Alternate method: Click the icon once to display a pull-down menu, and then click Restore.

Figure 3-10 demonstrates how to move an icon.

Figure 3-10 Moving an Icon

To move an icon from one location on the display to another:

1. Drag the pointer on the icon you want to move. When you begin moving the icon, the pointer changes to a cross-arrow and an icon outline appears.

As you move the pointer, the outline tracks the movement.

2. Once the icon is in the desired location, release the mouse button. The icon appears in the new location.

Alternate method: Click the icon once to display a pull-down menu, click Move, position the icon outline (by moving the mouse), and click a mouse button.

Starting Sessions

As presented in Logging In to the Network Computer in Chapter 2, there are many different ways to establish communications with one or more host computers. With a network computer you can have multiple sessions open and running simultaneously. For example, you might open a word processor, copy some text from a file, and paste it into window where you are composing some electronic mail. Or, you might open a session into another host to check if a customer order has been shipped. You can do all these kinds of tasks without having to exit any open applications.

Before you start a session, you typically need to know the name or address of the remote host. You can find this out by calling your system administrator.

There are different types of addresses based on the network protocol used at your site. Internet protocol (IP) addresses (128.06.70.01 for example) are used for networks running a protocol called TCP/IP. This is the most common network for hosts running a UNIX operating system. Node numbers (11.10:: for example) are used for networks running a protocol called DECnet. This is the most common network for hosts running a VMS operating system.

There are two easy ways to start a new session from Client Launcher. If you need a refresher on the terminology used in these procedures, refer back to Chapter 1, A New Piece of Hardware. Use one of these methods:

1. Select HostMenu. When the HostMenu client appears, use the mouse to select your host. Refer to Logging In to the Network Computer for details.

Note:

If you logged in with XDMCP, the XDMCP list is not available on HostMenu. Only one XDMCP session can be running.

2. Select a session from the Host Connections submenu:

Telnet (refer to Logging In with Telnet)

Console (refer to The Console Window)

Cterm (refer to Logging In with Cterm)

WinDD (refer to Logging In with the WinDD ICA Client)

Serial Port 0 or 1 (refer to Logging In with Serial Port 0 or 1)

LAT (refer to Logging In with LAT)

Note:

Grayed text indicates an option that is not enabled for your particular network computer. If an option is not listed, it is not available for your network computer model.

Running Clients

Clients refer to applications that your network computer accesses across the network, such as a desktop publishing system, a computer-aided design program, or an on-line transaction processing system. Your network computer can access multiple clients simultaneously.

Your system administrator can set up your login files to automatically start one or more clients each time you login. The other alternative is for you to start the clients you need.

Typically you start clients from a session window or a command menu:

• From a session window, type the command to start your particular client and press Enter. Instructions for starting clients are included with your application documentation.
• If your host computer or window manager has command menus available, there may be menu choices available to automatically start your applications. If so:
• Position the pointer outside of a window.
• For MWM, you would press the Select mouse button and click on your client. For other window managers, follow the instructions for menu and item selection and select the client you want to run.

Refer to the documentation that came with your application for application-specific operation and information.

Locking the Display

You can lock your display and all open windows so that while away from your desk, an unauthorized user cannot access the information on your display. The xlock local client locks the keyboard only, or the keyboard and the display.

1. xlock can be started from the Client Launcher (select Lock Screen) or with xpsh from the command prompt, as shown here:

xpsh -display nc_address:0 xlock -mode n

To determine the network computer address, select Setup from the Client Launcher. Drag on Configuration Summaries and release on TCP/IP (for a UNIX host) or TDEnet (for a VMS host). The address displays as the network computer IP Address or the TDEnet Address.

The -mode n setting is optional. If set to -mode 1, xlock locks the keyboard only. If set to -mode 0, xlock locks the keyboard and the screen. If a -mode setting is not given, xlock locks the keyboard and the screen by default. If you receive a "Command not found" message, have your system administrator add xpsh to your path environment variable and try the xpsh command again.

When xlock is started, the xlock window appears, asking for a password and confirmation. Upon entering the password, a blank screen with a floating lock appears. Pressing a key will prompt for a password. Only the correct password re-activates the screen.

2. At the Password prompt, enter a password and press Enter.
3. At the Retype prompt, enter the password again and press Enter. This verifies you have entered the password correctly. xlock remains in effect until you re-enter the password. The password is valid until you reboot the network computer or reset the server.
4. To unlock the display or keyboard, press any key for the xlock window. At the Password prompt, enter the password.

Note:

If you forget your password, you must reboot the network computer or reset the server to unlock the display or keyboard.

Local Floppy Manager Client for UNIX Hosts

The Local Floppy Manager (LFM) client provides a Graphical User Interface (GUI) for copying files between the local floppy drive attached to the network computer via the parallel interface and a UNIX host server. The GUI provides a point and click operation. The LFM client is available with NCBridge version 3.2 or higher.

The LFM client is compatible with both the current network computer product and earlier NCs and X terminals. The compatible platforms are XP117C, XP119C, XP119M, XP200, XP350, XP400, NC200, NC400, and NC900 series products.

To start the LFM on a network computer, ensure that the floppy drive is connected to the parallel port of the network computer and powered up. Once done, then type these commands at the command-line prompt for an NC900 series product:

xpsh -display <ipaddr>:0 lfm.900

Example: xpsh -display 134.6.5.12:0 lfm.900

To start the LFM client on an XP series unit, type the following:

xpsh -display <ipaddr>:0 lfm.350

Example: xpsh -display 134.6.7.14:0 lfm.350

Once the client is properly executed, the local NC console window should indicate that the following files, lfm.xxx and fdDrv.xxx, have been loaded. The file name extensions (.xxx) vary according to the NC model, as shown in Table 3-1.

Table 3-1 File Extensions For NC Models

Platform	File Name Extension (.xxx)
NC900 series	.900
NC200 and NC400 series	.500
XP330 series	.330
All other XP series	.350

Also, the LFM Client Screen, shown in Figure 3-11, should appear after the LFM client executes.

Figure 3-11 Local Floppy Manager Client Screen

For more information, see the floppy disk section in the Field Kit Installation Guide.