home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IBM Presents OS/2 Software Hits 1995
/
OS-2_SW_HITS_2ND_EDITION_1995.ISO
/
i17
/
ndwin1.dsk
/
READMEW.1ST
< prev
next >
Wrap
Text File
|
1994-12-17
|
25KB
|
661 lines
*************************************************************************
* Welcome to NetDoor for Windows release 1.0 *
*************************************************************************
*************************************************************************
* This level of code is equivalent to NetDoor CSD level IP20073 *
*************************************************************************
This file includes all the requirements to set up a NetDoor client
workstation, and describes how to install NetDoor on a client workstation
and how to remove the NetDoor installation from a client workstation.
==================================
Hardware and Software Requirements
==================================
NetDoor supports Windows Version 3.1 clients running on systems with an
80286 (*) or more advanced processor.
At least a 15 MHz processor speed is recommended.
At run time NetDoor requires less than 3MB of disk space on the client
and imposes no special memory requirements. At installation time
4MB of free disk space are required.
The only special hardware required is a network adapter.
A Token Ring 16/4 adapter or Token Ring Bus Master adapter is recommended;
the Token Ring/A adapter can also be used if 4MB token ring service is
available.
The minimum hardware requirements for a client include:
- 80286 processor (*)
- 3MB hard disk space
- 4MB random access memory for Windows 3.1
- Any adapter supported by DOS LAN Requester 3.0
The minimum software requirements for a client include:
- DOS 4.0 or higher
- Windows Version 3.1
- LAN Server 3.0 DOS Requester (minimum service level IPX7045),,
or LAN Server 4.0 DOS Services (with APAR IC08906).
(*) Installing on 80286 requires special considerations. See the
section 'Special considerations to Install on 80286' at the
bottom of this file.
=============================
NetDoor Installation Overview
=============================
You can use one of three methods to install NetDoor.
This section provides an overview of these methods and the requirements
for each.
The three methods are:
- Installing from the product diskettes
- Installing from a code server
- Installing using a software distribution manager product
The second and third methods are for remote installations.
Installing from Diskettes
-------------------------
This is the most commonly used method.
It requires you to insert the diskettes as instructed.
This method can be either interactive or noninteractive:
- In interactive mode the installation requires you to
answer questions as prompted.
- In noninteractive mode the installation is driven by a
response file, which contains the answers to all of the questions
that the installation needs.
This file can be generated in advance on any computer by your NetDoor
administrator.
With the response file you need to be present only to initiate the
installation, insert diskettes, and restart your workstation
when the installation is complete; no questions are
asked while the installation is running.
Upon completion of the installation, a group icon labeled
'NetDoor', and a group icon labeled 'NetDoor StartUp'
are added to the desktop of your workstation.
For more information about this method of installation, read
'Installing NetDoor from Product Diskettes.'
Installing from a Code Server
-----------------------------
You can use this method only if you have access to a
'code server.'
A code server is a workstation that contains the NetDoor
diskette image to be used during the installation.
The diskette image must be loaded on the code server to a predefined
directory structure by the NetDoor administrator.
Diskettes are not required at your workstation to perform the
installation.
This method can be either interactive or noninteractive.
- In interactive mode the installation works just as it
would if you were installing from diskette: it asks questions
which must be answered before the installation can begin.
- In noninteractive mode the installation is driven by a
response file, which contains the answers to all of the questions
that the installation needs.
This file can be generated in advance on any computer by your NetDoor
administrator.
With the response file you need to be present only to initiate the
installation and restart your workstation
when the installation is complete; no questions are
asked while the installation is running.
Upon completion of the installation, a group icon labeled
'NetDoor,' and a group icon labeled 'NetDoor StartUp'
are added to the desktop of your workstation.
For more information about this method of installation, read
'Installing NetDoor from a Code Server.'
Installing Using a Software Distribution Manager Product
--------------------------------------------------------
This method refers to installation initiated from a
remote system without requiring that anyone be at the system
being installed.
NetDoor complies with IBM's configuration, installation, and distribution
(CID) architecture, which provides for unattended, remote installation
of programs and applications.
The installation is started by a program known as a software
distribution manager, such as NetView* Distribution Manager/2.
For more information about this type of installation,
ask your NetDoor administrator.
For installations on 80286 processors see the section 'Special
considerations to Install on 80286' at the bottom of this file.
================
Before You Begin
================
Before you install NetDoor, ensure that:
- The system has the required hardware as described
in 'Client Requirements.'
- The operating system and network software are installed
at the correct service levels (see 'Client Requirements').
The NetDoor installation program does not allow installation
to proceed if the required levels are not installed.
- You have the following information, which can be obtained from
your NetDoor administrator:
User ID This is the name you specify when you log on
the NetDoor network.
LAN Server controls access to network resources
with user ID and passwords.
Password This is the secret word you specify when
you log on the NetDoor network.
LAN Server controls access to network resources
with user ID and passwords.
NetDoor domains These are the NetDoor domains that
Open NetDoor will assume as default
values to connect to the network.
- Verify that both the operating system and the network software
are functional.
The NetDoor installation cannot complete successfully if
the operating system or the network software is not running properly.
If problems occur, correct them before attempting to install
NetDoor.
=========================================
Installing NetDoor from Product Diskettes
=========================================
This section discusses the steps necessary to install NetDoor from
the product diskettes. In this section, 'A:' stands for
the diskette drive from which NetDoor is being installed.
To install a NetDoor client from diskette, you need the first NetDoor
installation diskette.
If you know the preliminary information, start the installation as
follows:
1. Place NetDoor installation diskette number 1 in your diskette drive.
2. If Windows is already started, follow these steps:
a. Switch to the Program Manager (or File Manager) window by
clicking on it or by using Task list.
b. From the 'File' pull-down menu, click on the
'Run' command. The 'Run' dialog box appears.
c. In the 'Command line' box, type the command:
A:\INSTALL
The section 'Using the Install Command' describes the parameters
you can specify.
If Windows is not started yet, from the MS-DOS** prompt type the
command:
WIN A:\INSTALL
The section 'Using the Install Command' describes the parameters
you can specify.
3. Click on the 'OK' button or press Enter.
4. Read the panels and answer the questions that appear.
You can view on-line help for every panel by clicking on the
'Help' button or by pressing the F1 key.
5. When the installation is complete, a message is displayed
with the installation return code.
If the installation was not successful, see the installation log
files.
If you did not specify the /L1 and L3 parameters when you entered the
INSTALL command, see the default log file stored in the file
x:\WINDOWS\NETDOOR.LOG, where x:\WINDOWS is the drive
and the directory in which you installed Windows.
Otherwise, see the log files you specified with the /L1 and /L3
parameters.
6. Exit the installation program by clicking on 'Exit.'
7. Customize your installation as described in 'Customizing Your
Installation.'
8. Shut down and restart your computer to make the changes effective:
a. From the 'File' pull-down menu, select the 'Exit' command.
b. When the MS-DOS command prompt is displayed, press Ctrl+Alt+Del.
The 'NetDoor' icon and the 'NetDoor StartUp' icon are added to your
desktop.
If you are installing in interactive mode, the answers you entered
to all of the questions that the installation asked you are stored
in the x:\WINDOWS\COUINSTW.RSP response file, where x:\WINDOWS
is the drive and path in which you installed Windows.
NOTE:
After you restart your workstation, select the 'READ ME'
icon from the NetDoor group icon on your desktop to read the latest
information and news about NetDoor.
To start working with the NetDoor product, see the on-line NetDoor
User's Guide for Windows.
=====================================
Installing NetDoor from a Code Server
=====================================
You may need to contact your NetDoor administrator before
installing a NetDoor client to find out the following information:
- Alias name where the diskette image is stored.
You need read and execute access to this alias on the code server.
- Server name.
- The fully qualified path name of the response file
(if you are installing NetDoor noninteractively).
- Note that, on 80286, due to the use of conventional memory
done by Windows, the installation from a code server might
not be possible. See the section "Special considerations
to install on a 80286" for details.
If you know this information, start the installation as follows:
1. From an MS-DOS prompt, access the network (if not accessed),
by typing:
NET START
NOTE: This command is optional. The network is automatically
accessed when you execute the next step.
2. Access the alias directory, by typing:
NET USE devicename \\servername\aliasdir
3. If Windows is not started yet, type:
WIN 'devicename':\INSTALL
where 'devicename' is the drive you specified.
If Windows is already started, follow these steps:
a. Switch to the Program Manager (or File Manager) window by
clicking on it or by using Task list.
b. From the 'File' pull-down menu, click on the 'Run' command.
The 'Run' dialog box appears.
c. In the 'Command line' box, type the command:
'devicename':\INSTALL
where 'devicename' is the drive you specified.
The NetDoor installation log file is stored in the file
x:\WINDOWS\NETDOOR.LOG where 'x:\WINDOWS' is the drive and path
in which you installed Windows.
To specify a different log file, see 'Using the Install Command'.
It describes all the parameters you can specify with the INSTALL
command.
4. Click on the 'OK' button or press Enter.
5. Read the panels and answer the questions that appear.
You can view on-line help for every panel by clicking on the
'Help' button or by pressing the F1 key.
6. When the installation is complete, a message is displayed
with the installation return code.
If the installation was not successful, see the installation log
files you specified with the /L1 and /L3 parameters.
7. Customize your installation as described in 'Customizing Your
Installation'.
8. Exit the installation program by clicking on 'Exit'.
9. Shut down and restart your computer to make the changes effective:
a. From the 'File' pull-down menu, select the 'Exit' command.
b. When the MS-DOS command prompt is displayed, press Ctrl+Alt+Del.
The 'NetDoor' icon and the 'NetDoor StartUp' icon are added
to your desktop.
If you are installing in interactive mode, the answers you entered
to all of the questions that the installation asked you are stored
in the x:\WINDOWS\COUINSTW.RSP response file, where x:\WINDOWS
is the drive and path where you installed Windows.
NOTE:
After you restart your workstation, select the 'READ ME'
icon from the NetDoor group icon on your desktop, to read the latest
information and news about NetDoor.
To start working with the NetDoor product, see the on-line
NetDoor User's Guide for Windows.
========================================
Installing NetDoor Using a Response File
========================================
You can install NetDoor using a response file if you are
installing from either product diskettes or a code server.
If you are installing from the product diskettes, you only need to
initiate the installation and to insert diskettes when required.
If you are installing from a code server, you only need to initiate the
installation procedure.
The response file, prepared by the NetDoor administrator, contains
all the keywords or installation variables that are needed by the
NetDoor installation processing.
To use a response file, the file must be available on a disk or
on an attached network alias before you begin installation.
NetDoor provides a sample response file, on the client installation
diskette number 1, in the 'a:\COUWINSTW.RSP' file, where 'a:' is
your diskette drive.
Follow the instructions in 'Installing NetDoor from Product Diskettes' or
'Installing NetDoor from a Code Server,' but when you start the
installation program, add the parameters to specify the path and
name of the response file.
For example, if you are installing a system from remote drive Z
and you have a response file SYSTEM1.RSP on a diskette in drive A,
type the command:
Z:\INSTALL /A:I /C:Z:\NETDOOR.ICF /R:A:\SYSTEM1.RSP /X /L1:C:\NETD.LOG
The installation messages are recorded in the NETD.LOG file on your C
disk.
=========================
Using the Install Command
=========================
Use 'install' to install NetDoor from the product diskettes
or from a code server.
The syntax of the 'install' command is:
>>-install -+-----------------------------------------+--+---------------+--->
! ! ! !
+--/A:I--/C:catalog--/R:responsefile--/X--+ +--/L1:logfile--+
>-----------+-------------------+---+-------------------+------------------><
! ! ! !
+--/L2:historyfile--+ +--/L3:netdlogfile--+
where:
/A The action you want to perform:
I Install
D Delete
When you specify this parameter the main window of the
installation is not displayed.
If you do not use it, the installation starts normally
with all windows displayed.
/C:catalog Specifies the location of the catalog file NETDOOR.ICF.
you must specify the drive name and directory location
of the catalog file. For example:
/C:A:\NETDOOR.ICF
if you are installing from diskette, or:
/C:devicename:\NETDOOR.ICF
if you are installing from a code server, and
'devicename' is the drive you used to access the
NetDoor image on the code server.
/R:responsefile The drive, path, and file name of the specific
response file. An example is:
/R:D:\XYZ\RESPONSE.DAT
NetDoor provides a response file, on the client
installation diskette number 1, in the COUWINSTW.RSP
file.
/X Specifies that the action is noninteractive.
If you do not specify information needed for the action
to complete, an error occurs. When you specify this
option, no progress indication is shown and all error
messages are logged in the default log file.
If you do not specify this option, you are prompted
for any information that the installation requires.
/L1:logfile The full path name of the file that contains all the
installation messages.
This file is a good source for problem determination.
/L2:history_log The drive, path, and file name of the history log file
that contains all the installation log messages.
This file contains a record of everything the
installation process does and is a source for problem
determination.
If you do not specify this parameter, no history
log is maintained.
/L3:netdlogfile The full path name of the file that contains all the
NetDoor installation messages.
If you do not specify the /L3: parameter, the
default log file is x:\WINDOWS\NETDOOR.LOG, where
x:\WINDOWS is the drive and the directory in which
you installed Windows.
Invoking the 'install' command without specifying any parameter,
you start an interactive installation.
=============================
Customizing Your Installation
=============================
DOS Lan Requester 3.0
---------------------
The NetDoor installation procedure checks if the
DOS Lan Requester 3.0 is properly installed and customized.
If needed, it sets some parameters in the DOSLAN.INI as follows:
- /NVS:7
- /NMS:7
- /NDB:3
- /API
The NVS parameter must be greater than or equal to the largest number of
servers in any domain where you are defined.
NetDoor sets this parameter to seven.
Increase it if you have access to a domain with more than seven servers.
The NMS parameter value must be at least equal to the NVS value.
The old INI file is saved as DOSLAN.COU in the same directory.
DOS Lan Services 4.0
--------------------
No check or setting is performed by NetDoor installation procedure
on DLS 4.0 customization.
=========================
Installation Return Codes
=========================
The following table lists the return codes you may have installing
the NetDoor program. A brief description for each message is also
provided. More details could be found in the NetDoor installation
log file.
-----------------------------------------------------------------------
RC Description
-----------------------------------------------------------------------
00 00 Successful program termination
Reboot and do not invoke again
08 00 Data resource not found
08 04 Data resource access denied because
already in use
08 08 Data resource access denied because
missing authorization
08 12 Data path not found
08 16 Product not configured
12 00 Storage medium exception (I/O error)
12 04 Device not ready
12 08 Not enough disk space
16 00 Incorrect program invocation
16 04 Unexpected condition
FE 00 Successful program termination.
Reboot and do not invoke again
FE 04 Successful program termination but
warning messages logged.
Reboot and do not invoke again
FE 08 Successful program termination but
error messages logged.
Reboot and do not invoke again
FE 12 Successful program termination but
severe error messages logged.
Reboot and do not invoke again
FF xx Successful program termination
warning messages logged.
Reboot with callback.
=================================
Removing the NetDoor Installation
=================================
You can remove the &prod installation using the product diskettes,
or a code server.
Using Diskettes
---------------
To remove the installation using diskettes, perform the steps
described in the section "Installing NetDoor from Product diskettes",
but when you start the installation program, add the parameter /A:D
as in the following example:
A:\INSTALL /A:D
where 'A:' is your diskette drive. The removal procedure creates a log
file. To specify the name of the log file, type, instead of the previous
command:
A:INSTALL /A:D /L1:logfile
where logfile is in the form drive:\path\filename.
Using a Code Server
-------------------
To remove the installation using a code server, perform the steps
described in the section :hdref refid=code.,
but when you start the installation program, add the parameter /A:D
as in the following example:
x:\INSTALL /A:D
where 'x' is the drive you specified to access the directory
on the code server.
The deinstallation procedure creates a log file.
To specify the name of the log file, type,
instead of the previous command:
x:INSTALL /A:D /L1:logfile
where logfile is in the form drive:\path\filename.
==========================================
Special considerations to Install on 80286
==========================================
Due to the large use of conventional memory done by Windows on 80286,
in general, before running the NetDoor installation procedure on this
processor, you should ensure that no other programs are running.
In particular we recommend not to start the DOS LAN Services
program.
A failing installation due to lack of memory can be evidenced by
returning a General Protection Fault (GPF) in the EPFINST module.
The NetDoor installation will end with the EPFIE187 message
indicating a return code of 0006 in the L1 log file.
This means that the system does not have enough memory
to complete the installation.
If this happens the following considerations can applied:
- In general, an interactive installation uses less memory than
an installation with response file.
- If you want to perform an installation with response file you can
reduce to the minimum the parameter list for the INSTALL command
(default values are available for the other parameters), i.e.
use the following command:
A:\INSTALL /A:I /R:A:\SYSTEM1.RSP /X /L1:C:\NETD.LOG
where A:\SYSTEM1.RSP is your customized response file.
- If the problem persists check if any program is holding the
DOS conventional memory by issuing the DOS command 'MEM /D'.
In addition to the above, if you are installing using a Software
Distribution Manager product (such as NetView DM/2), you
must first run the NetDoor installation program and then the
NETCIDRC program, that is on the installation diskette number 1.