home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
netdor0.zip
/
READ.ME
< prev
Wrap
Text File
|
1996-04-04
|
9KB
|
250 lines
IBM NetDoor 1.0 (Level IP20073) - Installation
------------ -----===****===----- ------------
You are about to install IBM NetDoor on
this workstation. NetDoor will not
install if you are not running supported
versions of OS/2 and OS/2 networking
software. Supported versions are listed
below, with minimum service levels given in
parentheses. You can use the OS/2 SYSLEVEL
command to determine what components are
installed and at what service level.
Supported Configurations for NetDoor Clients:
=============================================
OS/2 2.0 (6055) + LR 3.0
OS/2 2.0 (6055) + TCP/IP 1.2.1 (34109)
+ NFS (32132)
OS/2 2.0 (6055) + TCP/IP 2.0 + NFS
OS/2 2.1 + LR 3.0
OS/2 2.1 + LR 4.0
OS/2 2.1 + TCP/IP 1.2.1 (34109)
+ NFS (32132)
OS/2 2.1 + TCP/IP 2.0 + NFS
OS/2 2.11+ LR 3.0
OS/2 2.11+ LR 4.0
OS/2 2.11 + TCP/IP 2.0 + NFS
OS/2 Warp + LR 3.0
OS/2 Warp + LR 4.0
OS/2 Warp + TCP/IP 2.0 + NFS
To complete the initialization, you will
need to supply the following information:
o A local drive and directory where
NetDoor will be installed. The amount
of local disk space required for a
NetDoor client is less than 1MB.
Anyway, at time installation is issued
2MB disk space is required.
NOTE: If you are using BootManager to
run multiple instances of OS/2 from
different partitions, you will need to
use separate NetDoor local directories
for each.
o A free drive letter, to be used for
accessing the NetDoor server on the
network.
o The names of the NetDoor servers to
which you have access.
Online help is available at each step of
the installation by selecting the Help
button or by pressing the F1 key. You can
cancel the installation at any time by
pressing the Exit button.
------------------- -----===****===----- -------------------
IBM NetDoor 1.0 (Level IP20073) - Administrative Information
You are about to install IBM NetDoor on
this server. NetDoor will not install if
you are not running a supported version of
OS/2 and the networking software. See
below for the list of supported
configurations.
Supported Configurations for NetDoor Servers:
=============================================
OS/2 2.0 (6055) + LS 3.0
OS/2 2.0 (6055) + TCP/IP 1.2.1 (34109)
+ NFS (32132)
OS/2 2.0 (6055) + TCP/IP 2.0 + NFS
OS/2 2.1 + LS 3.0
OS/2 2.1 + LS 4.0
OS/2 2.1 + TCP/IP 1.2.1 (34109)
+ NFS (32132)
OS/2 2.1 + TCP/IP 2.0 + NFS
OS/2 2.11 + LS 3.0
OS/2 2.11 + LS 4.0
OS/2 2.11 + TCP/IP 2.0 + NFS
OS/2 Warp + LS 3.0
OS/2 Warp + LS 4.0
OS/2 Warp + TCP/IP 2.0 + NFS
Modifying the Behavior of the Installation
==========================================
The installation profile \SETUP\INSTALL.PRO
controls the customization of the install
process on a global basis. See the
comments in that file for details.
Running the Installation
========================
To start the installation on a client
workstation, run INSTALL from diskette 1.
To start the installation on a server, run
INSTALL /SRV. Only diskette 1 is needed to
install a client. The remaining disks are
for servers only.
If you are using LAN Server and are
installing a NetDoor server, you will need
to be logged on to the domain with an
Administrator userid before the installation
can proceed.
To install a NetDoor Server, with the image,
you need a minimum of 40MB space free on one
hard disk partition. If you are reinstalling
NetDoor and need to free some disk space to
allow the installation to proceed, use the
OS/2 Drives object to delete the old COUIMAGE
directory.
The installation log file is
\OS2\INSTALL\NETDOOR.LOG. The response file
generated for the installation is
\OS2\INSTALL\COUINST.RSP. When reporting
problems with the installation, please provide
these two files.
There have been instances where OS/2 runs very
slowly after multiple installations. The
problem appears to exist only on OS/2 2.0,
and seems to be related to recreating the
NetDoor objects repeatedly. To fix this,
you will probably need to reinstall OS/2,
although cleaning the INI file might work.
This problem has not been seen on 2.1.
Troubleshooting
===============
The installation keeps a detailed record if
its progress in \OS2\INSTALL\NETDOOR.LOG.
If an error occurs during the installation
and the cause is not apparent, the log file
may provide additional information. In
particular, the install uses CID return
codes, which are not very specific. To
more closely identify the cause of the
error, the install also writes an extended
return code to the log file. The possible
return codes and extended return codes that
may appear are as follows:
RC Ext Description
===== === ====================================================
0000x --- Okay (successful program termination)
FE??x --- Okay (successful program termination).
0800x Data resource not found.
100 RXUTILS.DLL could not be initialized.
101 COUENV.DLL could not be initialized.
102 Response file does not exist.
0812x Data path not found.
300 Couldn't read master (access method undefined)
301 Couldn't read master, NETBIOS
302 Couldn't read master, NFS (not exported)
303 Couldn't read master, NFS (NFSD not running)
304 Couldn't read master, NFS (no free drives)
305 Couldn't read master, NFS (file not found)
306 Couldn't read master, NFS (program(s) not found)
0816x Product not configured
--- Installation DLLs could not be unpacked, or
RXUTILS.DLL could not be initialized.
400 Entry not found in SERVERS file.
401 SERVERS entry for image server missing :ID/:NFS tag.
402 Unexpected error searching SERVERS file.
403 COUENV version check returned an error (OS2.INI bad?).
404 Unexpected access method.
1200x Storage medium exception (I/O error).
1204x Device not ready.
1208x Not enough disk space.
1600x Incorrect program invocation.
--- Could not write to specified log file.
501 Missing response file name.
1604x Unexpected condition.
--- REXX not installed.
200 Incomplete response file
201 Non-zero return code from ITL
202 Server role not defined in response file.
203 TCP/IP support programs not found.
204 NAMEFIND not found.
205 Required TCP/IP ETC directory not found.
997 Unexpected program error (untrapped).
999 Unexpected Program error (trapped).
In the event of a problem with the
installation, be sure and provide the log
file for analysis.
Removing NetDoor Installation from Servers
=========================================
To remove NetDoor installation from servers refer to
IBM NetDoor Administrator's Guide (SH19-5023-01),
chapter 3.
In the case of Lan Server 4.0 the files IBMLAN.INI and
PROTOCOL.INI are not modified by NetDoor installation
and no backup copy of these two files is created.
In this case the steps described in the second paragraph
of point 3 of 'Removing the NetDoor Product' should not
be performed.
Documentation
=============
Product documentation will be available
from Mechanicsburg as follows:
IBM Network Door/2
User's Guide SH19-5022
Administrator's Guide SH19-5023
Progamming Guide SH19-5024
User's Guide Windows Clients SH19-4059
These will also be avaialable on the
NetDoor image in BookManager READ/2
format.
Example of Installation from a Network Alias
============================================
The installation can be run from a
redirected drive. Create a publicly
accessible alias on a server, and copy the
installation diskettes to that alias. Use
the XCOPY command to do this:
XCOPY A:\*.* \\server\alias\*.* /S
Repeat the command for each installation
diskette. INSTALL can then be run from the
alias just as it would from diskettes.