home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IBM Presents OS/2 Software Hits 1995
/
OS-2_SW_HITS_2ND_EDITION_1995.ISO
/
i17
/
wsos21.exe
/
NLS
/
ENGLISH
/
INSTALL.HLP
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1994-09-14
|
21KB
|
836 lines
ΓòÉΓòÉΓòÉ 1. NetWare Client Installation Overview ΓòÉΓòÉΓòÉ
NetWare Client Installation Overview
Welcome to the Novell NetWare installation program.
NETWARE CLIENT FOR OS/2
NetWare Client for OS/2 workstation software enables OS/2 workstations to
access NetWare servers. After you install NetWare Client for OS/2, you can
connect to a NetWare network and perform basic network tasks.
o Supports both NetWare 3 and NetWare 4 servers
o Offers Remote Program Load (RPL) workstation access
o Supports DOS/MS Windows global and private sessions
o Supports VLM Boot DOS Session
o Supports ODINSUP
NETWARE SERVER FOR OS/2
NetWare Server for OS/2 provides device drivers that allow the NetWare 4
server software to run on an OS/2 computer. NetWare Server for OS/2 runs as a
parallel operating system to OS/2. Processing time is split between OS/2 and
NetWare. You can set up the OS/2 side of the computer as an application
server, an application client, or both.
NetWare Server for OS/2 is also compatible with computers using IBM Extended
Services.
ΓòÉΓòÉΓòÉ 2. Installation ΓòÉΓòÉΓòÉ
Installation
Select this menu to view Installation options for NetWare Client for OS/2 and
NetWare Server for OS/2.
ΓòÉΓòÉΓòÉ 3. Requester on Workstation ΓòÉΓòÉΓòÉ
Requester on Workstation
Select this option to install NetWare Client for OS/2 software on this
workstation.
ΓòÉΓòÉΓòÉ 4. Remote workstations ΓòÉΓòÉΓòÉ
Remote workstations
Select this option to install set up a workstation for Remote Program Load
(RPL).
ΓòÉΓòÉΓòÉ 5. NetWare Server for OS/2 ΓòÉΓòÉΓòÉ
NetWare Server for OS/2
Select this option to complete a custom installion of NetWare Server for OS/2
on this workstation.
ΓòÉΓòÉΓòÉ 6. Simplified NetWare Server for OS/2 ΓòÉΓòÉΓòÉ
Simplified NetWare Server for OS/2
Select this option for a simplified installation of NetWare Server for OS/2 on
this workstation.
ΓòÉΓòÉΓòÉ 7. Upgrade NetWare Server for OS/2 ΓòÉΓòÉΓòÉ
Upgrade NetWare Server for OS/2
Select this option to upgrade your current version of NetWare Server for OS/2
on this workstation.
ΓòÉΓòÉΓòÉ 8. Configuration ΓòÉΓòÉΓòÉ
Configuration
Select this menu for NetWare configuration options.
ΓòÉΓòÉΓòÉ 9. Configure this workstation ΓòÉΓòÉΓòÉ
Configure this workstation
Select this option to edit the NET.CFG file for this workstation.
ΓòÉΓòÉΓòÉ 10. Configure remote workstation ΓòÉΓòÉΓòÉ
Configure remote workstation
Select this option to edit the NET.CFG file for workstations using Remote
Program Load (RPL).
ΓòÉΓòÉΓòÉ 11. VLM Boot Setup ΓòÉΓòÉΓòÉ
VLM Boot Setup
Select this option to setup VLM Boot.
ΓòÉΓòÉΓòÉ 12. Utilities ΓòÉΓòÉΓòÉ
Utilities
Select this option to set up additional utilities.
ΓòÉΓòÉΓòÉ 13. ODINSUP ΓòÉΓòÉΓòÉ
ODINSUP
Select this option to set up ODINSUP.
ΓòÉΓòÉΓòÉ 14. ReadMe ΓòÉΓòÉΓòÉ
ReadMe
Select this menu to select a ReadMe file.
ΓòÉΓòÉΓòÉ 15. NetWare Client for OS/2 ReadMe ΓòÉΓòÉΓòÉ
NetWare Client for OS/2 ReadMe
Select this option to view the ReadMe file for this version of NetWare Client
for OS/2 software.
ΓòÉΓòÉΓòÉ 16. ReadMe NetWare Server for OS/2 ΓòÉΓòÉΓòÉ
ReadMe NetWare Server for OS/2
Select this option to view the ReadMe file for this version of NetWare Server
for OS/2.
ΓòÉΓòÉΓòÉ 17. Help Extended Help ΓòÉΓòÉΓòÉ
Help Extended Help
Select this option to display overview information about NetWare installation
and configuration.
ΓòÉΓòÉΓòÉ 18. Help for Help ΓòÉΓòÉΓòÉ
Help for Help
Select this option to display how to get help.
ΓòÉΓòÉΓòÉ 19. Help for NetWare Client for OS/2 Installation ΓòÉΓòÉΓòÉ
NetWare Client for OS/2 Installation
Before installing NetWare Client for OS/2, make sure that
* The workstation is cabled to the network
* You know what kind of network board is in the workstation
If you want a full NetWare Client for OS/2 installation, choose the first
option--Edit the CONFIG.SYS and Copy All Requester files.
If NetWare Client for OS/2 is already installed and you want to change your
selections for ODI driver, DOS/MS Windows support, or protocol support, choose
the second option--Only Edit the CONFIG.SYS.
If NetWare Client for OS/2 is already installed and you want to update your
NetWare Client for OS/2 files without changing your selections, choose the
third option--Only Copy Requester Files.
If NetWare Client for OS/2 is already installed and you want to update your ODI
driver files without changing your selections, choose the fourth option--Only
Copy ODI Driver Files.
ΓòÉΓòÉΓòÉ 20. Help for Selecting the Source Drive ΓòÉΓòÉΓòÉ
Source Drive For Installation
Make sure the source drive shown is where you want to install from. If it is
not, type a new drive letter.
If you are installing from a network drive, be sure that you have copied all
NetWare Client for OS/2 diskettes to that network drive.
The network drive must have exactly the same directories as are found on the
NetWare Client for OS/2 diskettes.
ΓòÉΓòÉΓòÉ 21. Help for Specifying the Target Directory ΓòÉΓòÉΓòÉ
Set Target Directory
By default, NetWare Client for OS/2 files and NetWare for OS/2 driver files are
copied to the \NETWARE directory on your boot drive. Type a new drive and
directory name to change the default.
NOTE: If you will be installing files for remote workstations from this
workstation, copy the files to the default directory. The default directory
must be on a bootable C: drive.
Make sure the source drive shown is the one you want to copy from. If it is
not, type a new drive letter.
If you are installing from a network drive, the network drive must have the
same subdirectories as the NetWare Client for OS/2 diskettes.
ΓòÉΓòÉΓòÉ 22. Help for Selecting ODI LAN Drivers to Copy ΓòÉΓòÉΓòÉ
Choose the ODI LAN Driver
Type (or choose from the list of drivers) the driver for the network board in
the workstation. Choose the arrow at the right of the Driver entry field to
display a list of driver files found in the source drive. If you put a new
diskette in the source drive and then choose the arrow, an updated list of
drivers appears.
If the name of the driver does not appear in the list, you must type it in.
For example, if you have an NE2000 board, type or choose from the list:
NE2000.SYS
NOTE: Be sure to have the correct driver diskette available. You will be asked
to insert it in a drive later in the install.
ΓòÉΓòÉΓòÉ 23. Help for Adding DOS and Windows Support to the CONFIG.SYS File ΓòÉΓòÉΓòÉ
Choose NetWare Support for DOS and Windows Applications
Choose IPX support for virtual sessions to be ON or OFF. If you choose OFF, you
will not be able to use the NetWare network from a DOS or MS Windows sessions.
If you choose ON, see the NetWare Client for OS/2 manual for information on
setting up DOS and MS Windows sessions after exiting the installation program.
Select one of the options:
Private support - All DOS and MS Windows sessions have their own logins to a
NetWare server. OS/2 sessions share another login.
Global support - All DOS, MS Windows, and OS/2 sessions share a single login to
a NetWare server.
No support - NetWare support disabled for all DOS and MS Windows sessions.
ΓòÉΓòÉΓòÉ 24. Help for Adding Optional Protocols to the CONFIG.SYS File ΓòÉΓòÉΓòÉ
Choose Optional Protocols
This screen allows you to choose the following optional protocols:
SPX support - Load SPX if you are going to run TLI. SPX is also required for
some NetWare printing utilities (such as NPRINTER), Named Pipes, or
applications that use the SPX protocol (such as the NetWare Services Manager
for OS/2).
NetBIOS - Choose this box if you want to use applications that use the NetWare
NetBIOS protocol. For information about using NetWare NetBIOS with IBM NetBIOS,
see the NetWare Client for OS/2 manual.
Remote Named Pipes - Use this protocol if this machine will function as a Named
Pipes application server or client.
If you select "client and server" support, you must type in a unique machine
name (1 to 16 characters).
ΓòÉΓòÉΓòÉ 25. Help for Saving the CONFIG.SYS File ΓòÉΓòÉΓòÉ
Save Changes to CONFIG.SYS
The changes you have made will be saved to the CONFIG.SYS file in the root of
your boot drive.
NOTE: Your previous CONFIG.SYS is saved as CONFIG.BAK.
To save the changes to a different file, type a new drive letter, directory
name, or filename. If you save the file with a name other than CONFIG.SYS, the
system will not use your changes when booting.
ΓòÉΓòÉΓòÉ 26. Help for Saving the AUTOEXEC.BAT file ΓòÉΓòÉΓòÉ
Suggested Default Settings to AUTOEXEC.BAT
Checking these two boxes will modify your DOS AUTOEXEC.BAT file so that it will
automatically load TBMI2.COM and NETX.EXE whenever you start a DOS or MS
Windows session.
TBMI2.COM is required by any MS Windows application that uses IPX/SPX to
directly access the network. Application such as E-Mail packages may require
TBMI2.COM to be loaded.
NETX.EXE is required for all DOS and MS Windows sessions to access the network
in both Global and Private modes.
If no AUTOEXEC.BAT file exists, you have the option of having this
installation program create one for you.
If you want your existing AUTOEXEC.BAT file saved under a different filename,
enter the filename you want to save it as.
NOTE: You must also change your DOS_LASTDRIVE setting in each DOS and WIN-OS/2
command prompt on your desktop to equal the last local drive you have in your
machine.
ΓòÉΓòÉΓòÉ 27. Help for Copying the NetWare Client for OS/2 Files ΓòÉΓòÉΓòÉ
Copy NetWare Client for OS/2 Files
Note the location where the files will be copied. If you choose Copy, all files
are copied.
If you do not want to copy files to this location, choose Cancel.
ΓòÉΓòÉΓòÉ 28. Help for Copying ODI LAN Driver Files ΓòÉΓòÉΓòÉ
Copy ODI LAN Driver Files
The ODI driver currently loaded in your CONFIG.SYS file is shown. If you have
not edited the CONFIG.SYS file, you might not have a default driver.
This screen allows you to copy either just the default ODI driver or all ODI
drivers in the source drive.
ΓòÉΓòÉΓòÉ 29. Help for Uncopied Drivers ΓòÉΓòÉΓòÉ
Drivers Not Updated
This box displays the drivers that exist in your server directory that were not
updated during the upgrade process.
ΓòÉΓòÉΓòÉ 30. Help for VLM Boot Setup ΓòÉΓòÉΓòÉ
VLM Boot Setup
VLM Boot makes it possible to have a DOS kernel running on an OS/2 workstation.
This allows you to effectively run NWADMIN for DOS and MS Windows.
PREREQUISITES
- You must use OS/2 version 2.11 to run VLM Boot.
- You must install NetWare Client for OS/2 before you can install VLM Boot.
- You must have a copy of the VLMBOOT diskette.
- The source drive must be a floppy drive.
PROCEDURE
1. Enter the source floppy drive letter or accept the default. Select OK.
2. The AUTOEXEC.BAT and CONFIG.SYS files on the VLMBOOT floppy diskette and the
AUTOEXEC.BAT on the OS/2 boot drive will be modified. Select OK.
3. Insert the VLMBOOT diskette into the appropriate floppy drive. Select OK.
ΓòÉΓòÉΓòÉ 31. Help for Creating a NetWare VLM Boot Image File ΓòÉΓòÉΓòÉ
Create a NetWare VLM Boot Image File
PROCEDURE
1. Select "Create a NetWare VLM Boot image file" check box.
2. Enter the source floppy drive letter or accept the default. Select OK.
3. A NetWare VLM Boot image file will be created.
To Use the NetWare VLM Boot Image File
1. If you just finished installing NetWare Client for OS/2 and VLM Boot, reboot
your workstation.
2. From the OS/2 Desktop, open the "Novell" folder.
3. From the "Novell" folder, select the "VLMBOOT" icon.
4. An actual DOS kernel now resides on your OS/2 workstation and your
workstation is connected to the network.
ΓòÉΓòÉΓòÉ 32. Help for Copying OS/2 Files for Remote Workstation Installation ΓòÉΓòÉΓòÉ
Remote Workstation Installation
Workstations that don't have hard disks can boot remotely with the remote
program load (RPL) files.
To remote boot a workstation you must copy the OS/2 and RPL files to one or
more NetWare servers. To determine which file servers need these files you must
know what type of BOOT PROM is installed on the remote workstations.
If the BOOT PROM is the older style these files must be copied to each server
on the local network which will respond to a get nearest server request. If
the BOOT PROM is the new enhanced style only servers running RPL.NLM need these
files.
You should also define each remote workstation and username on each server. You
can do these steps separately.
Because all files on your C: drive are copied from the hard disk on this
workstation, be sure the root of the C: drive contains only files you want
copied to the network. OS/2 must be installed on the C: drive on this
workstation.
NOTE: You must install remote files and define workstations on ALL servers
connected to the workstations' local network.
ΓòÉΓòÉΓòÉ 33. Help for Copying RPL Files ΓòÉΓòÉΓòÉ
Copy RPL Files
Select this option for copying the remote boot files to the servers you
specified.
Remote boot workstations need these files to gain initial access to the
network.
See the NetWare Client for OS/2 manual for more information about what files
are copied.
ΓòÉΓòÉΓòÉ 34. Help for Copying OS/2 Files ΓòÉΓòÉΓòÉ
Copy OS/2 Files
WARNING!!! You are about to copy all files on the C: drive to each of the file
servers you have selected.
* Be sure all unneeded files have been deleted from this drive. The OS/2
system files can use 30 MB or more disk space. Unneeded files will use up even
more disk space.
* Be sure NetWare Client for OS/2 files were installed to the default
C:\NETWARE directory.
If you want to copy the files to each server you've selected, choose "OK" and
continue with the installation procedure.
If you don't want to copy the files, choose "OK" and then "Cancel."
ΓòÉΓòÉΓòÉ 35. Help for Selecting the Type of BOOT PROM in the Target Workstation ΓòÉΓòÉΓòÉ
Select the Type of BOOT PROM in the Target Workstation
Choose the type of Boot PROM in the workstation which will be remote booting.
There are two types of Boot PROMs.
One is the old PROMs found in older NE1000, NE2000, and NE2 cards. These PROMs
have an embedded dedicated IPX driver in them and use the GetNearestServer call
to locate the remote boot file server.
The other is the new enhanced Boot PROMs. Boot PROMs found on IBM network cards
and newer Novell cards have this type. If you are unsure contact your card
manufacturer. These PROMs have an embedded ODI driver in them and use IBM's
FindFrame technology to locate the remote boot file server. Only file servers
running RPL.NLM respond to the FindFrame requests.
ΓòÉΓòÉΓòÉ 36. Help for Adding Remote Boot Workstation ΓòÉΓòÉΓòÉ
Add Remote Boot Workstation
NOTE: You can move this help window to another location on your screen.
In each field select or type the options explained below.
Setup THIS machine as a remote boot workstation. Choosing this option fills in
the network and node address fields of this workstation if you use the Older
Style Boot PROM. Only the node address field fills in if you use the New
Enhanced Boot PROM.
Setup ANOTHER machine as a remote boot workstation. If you choose the Older
Style Boot PROM, you must fill in the Node Address field if the workstation is
on the same network, or both the Network and Node Address fields if the
workstation is on another network. If you use the New Enhanced Boot PROM, you
only need to fill in the Node Address field.
Network Address. Type the network address of the workstation that will boot
remotely.
Node Address. Type the node address of the workstation that will boot remotely.
Driver. Select the remote boot driver which matches the network board in the
workstation that will be booted remotely.
Remote workstations are easier to manage if they all use the same kind of
network board. See the NetWare Client for OS/2 manual for more information
about managing remote workstations.
NOTE: If your remote workstations use IBM Ethernet network boards, token ring
network boards, or New Enhanced Boot PROMS, you must load a special NLM on each
server. Follow the instructions in the NetWare Client for OS/2 manual.
UserName. Type the username of the person using the remote workstation. Each
remote workstation must have a username associated with it.
After exiting this installation program, make sure each user you specify here
has an account with the necessary rights on the appropriate server. See the
NetWare Client for OS/2 manual.
Logical Name (optional). Type a logical name. You must use a logical name
anytime you have a user who will need to be defined on more than one physical
workstation. For example, if user BETH has a workstation in her office and a
workstation in the lab and both need to boot remotely, you need to define a
logical name for BETH at each physical workstation. That way, BETH in the
office might be defined to node address BBB231333451 and BETH in the lab might
be defined to EEEE334215A4.
ΓòÉΓòÉΓòÉ 37. Help for Adding a Remote Boot Workstation ΓòÉΓòÉΓòÉ
Add Remote Boot Workstation
NOTE: You can move this help window to another location on your screen.
In each field select or type the options explained below.
Setup THIS machine as a remote boot workstation. Choosing this option fills in
the network and node address fields of this workstation if you use the Older
Style Boot PROM. Only the node address field fills in if you use the New
Enhanced Boot PROM.
Setup ANOTHER machine as a remote boot workstation. If you choose the Older
Style Boot PROM, you must fill in the Node Address field if the workstation is
on the same network, or both the Network and Node Address fields if the
workstation is on another network. If you use the New Enhanced Boot PROM, you
only need to fill in the Node Address field.
Network Address. Type the network address of the workstation that will boot
remotely.
Node Address. Type the node address of the workstation that will boot remotely.
Driver. Select the remote boot driver which matches the network board in the
workstation that will be booted remotely.
Remote workstations are easier to manage if they all use the same kind of
network board. See the NetWare Client for OS/2 manual for more information
about managing remote workstations.
NOTE: If your remote workstations use IBM Ethernet network boards, token ring
network boards, or New Enhanced Boot PROMS, you must load a special .NLM on
each server. Follow the instructions in the NetWare Client for OS/2 manual.
UserName. Type the username of the person using the remote workstation. Each
remote workstation must have a username associated with it.
After exiting this installation program, make sure each user you specify here
has an account with the necessary rights on the appropriate server. See the
NetWare Client for OS/2 manual.
Logical Name (optional). Type a logical name. You must use a logical name
anytime you have a user who will need to be defined on more than one physical
workstation. For example, if user BETH has a workstation in her office and a
workstation in the lab and both need to boot remotely, you need to define a
logical name for BETH at each physical workstation. That way, BETH in the
office might be defined to node address BBB231333451 and BETH in the lab might
be defined to EEEE334215A4.
ΓòÉΓòÉΓòÉ 38. Help for Selecting File Servers ΓòÉΓòÉΓòÉ
Select 1 or More File Servers
The server list displays the servers you are connected to and to which you
have Supervisor object rights to the NetWare Server object (or Supervisor or
Supervisor equivalence on a NetWare 3 server).
To select or deselect servers from the list, click on the server name. To
select multiple servers, click on each server name.
To attach to file servers not in the list, choose Attach.
NOTE: If you are installing NetWare Client for OS/2 for workstations that boot
remotely, you must install the remote boot files on all servers connected to
the workstations' local networks.
ΓòÉΓòÉΓòÉ 39. Help for Attaching to a NetWare File Server ΓòÉΓòÉΓòÉ
Attach to a NetWare File Server
To attach, click on the arrow to the right of the text entry field and select a
server name. Then type the username and password.
For NetWare 4 servers, delete "Supervisor" and type a new username that has
Supervisor object rights to the NetWare server. Then type the password.
For NetWare 3 servers, type the Supervisor password. To attach with Supervisor
equivalence, delete "Supervisor" and type a Supervisor-equivalent username and
password.
ΓòÉΓòÉΓòÉ 40. Help for NetWare Server for OS/2 Installation ΓòÉΓòÉΓòÉ
NetWare Server for OS/2 Installation
The NetWare Server for OS/2 server files and the NetWare 4 server files must be
copied to the same directory.
This installation procedure sets a variable so that the default location in the
NetWare 4 installation is \NWSERVER.
The NetWare Server for OS/2 hardware 'Driver Files' must be copied to the same
directory as the NetWare Client for OS/2 files (if you have the NetWare Client
installed). By default, this is the \NETWARE directory.
Choose "Copy" to start copying the files to the target directories. "Cancel"
will quit the NetWare Server for OS/2 installation process.
ΓòÉΓòÉΓòÉ 41. Help for Network Board Sharing Options ΓòÉΓòÉΓòÉ
Network Board Sharing Options
Use this dialog box to indicate your workstation and NetWare Server for OS/2
setup.
If you are using only IPX/SPX protocols, check the box marked "IPX/SPX
Communication Protocols."
If you are using IBM communication products such as Database Manager,
Communication Manager, LanServer, or Extended Services, check the box marked
"IBM Communication Products that use IBM Protocols (Netbios, etc.)." These
products use a nonrouting protocol that needs a special driver loaded on
NetWare Server for OS/2.
If NetWare Server for OS/2 has at least one token ring board, select the button
marked "Token Ring, With or Without Other Topologies," otherwise select the
button marked "Ethernet or Other Non-Token Ring Topology."
For example, if your computer is a client and server using IBM protocols and
applications on a token ring network, choose "IBM communication products that
use IBM protocols (Netbios, etc.)" and "Token-Ring, With or Without Other
Topologies."
Using the choices you make in this box, the installation program determines the
best solution for network board sharing.
ΓòÉΓòÉΓòÉ 42. Help for Entering Installation Information ΓòÉΓòÉΓòÉ
Enter Installation Information
Type the server name in the box provided. Be sure to write down the server name
for future reference.
Accept the randomly generated IPX internal network number, or delete the number
and enter your own unique IPX internal network number. You cannot assign a
network number of "0" or "FFFFFFFF". Be sure to write down the IPX internal
network number for future reference.
The default country code, code page, and keyboard mapping should be displayed.
If these defaults are incorrect, click on the scroll arrow and select the
correct information. For more information about country code, code page, and
keyboard mapping, refer to your OS/2 manual.
The filename format refers to the valid character set usable in a filename. DOS
Filename Format is the filename format used by DOS, which accepts all standard
keyboard characters. NetWare Filename Format is an extension of the DOS
Filename Format; it allows certain foreign characters (for example, the accent
and umlaut characters) to be used.
Under most circumstances, you will want to choose DOS Filename Format. This
will give you compatibility with DOS.
Choose "OK" when you have named the server, entered an IPX internal network
number, and have verified the country code, code page, and keyboard mapping.
ΓòÉΓòÉΓòÉ 43. Help for Server Information ΓòÉΓòÉΓòÉ
Enter Installation Information
Type the server name in the box provided. Be sure to write down the server name
for future reference.
Accept the randomly generated IPX internal network number, or delete the number
and enter your own unique IPX internal network number. You cannot assign a
network number of "0" or "FFFFFFFF". Be sure to write down the IPX internal
network number for future reference.
The default country code, code page, and keyboard mapping should be displayed.
If these defaults are incorrect, click on the scroll arrow and select the
correct information. For more information about country code, code page, and
keyboard mapping, refer to your OS/2 manual.
The filename format refers to the valid character set usable in a filename. DOS
Filename Format is the filename format used by DOS, which accepts all standard
keyboard characters. NetWare Filename Format is an extension of the DOS
Filename Format; it allows certain foreign characters (for example, the accent
and umlaut characters) to be used.
Under most circumstances, you will want to choose DOS Filename Format. This
will give you compatibility with DOS.
Choose "OK" when you have named the server, entered an IPX internal network
number, and have verified the country code, code page, and keyboard mapping.
ΓòÉΓòÉΓòÉ 44. Help for Adapter Type ΓòÉΓòÉΓòÉ
Adapter Type
Each adapter has a certain frame type (for example, Token-Ring, Ethernet,
FDDI, etc.). Only these frame types work with ODINSUP. If a driver has a
different frame type, it cannot be used in the ODINSUP process.
List of Frame Types and LAN Drivers
Frame type LAN driver
Ethernet 802.3 NE1000, NE2000, NE2100, NE2, NE2-32, 3C501, 3C503, 3C505,
3C523, EXOS205, EXOS215, ODINSUP
Ethernet 802.2 NE1000, NE2000, NE2100, NE2, NE2-32, 3C501, 3C503,
EXOS205, EXOS215, ODINSUP, LANSUP
Ethernet II NE1000, NE2000, NE2100, NE2, NE2-32, 3C501, 3C503, 3C505,
3C523, EXOS205, EXOS215, ODINSUP
Ethernet SNAP NE1000, NE2000, NE2100, NE2, NE2-32, 3C501, 3C503,
EXOS205, EXOS215, ODINSUP, LANSUP
Token ring ODINSUP, TOKEN, LANSUP
Token ring SNAP ODINSUP, TOKEN, LANSUP
IBM PCN2 802.2 PCN2, PCN2L, LANSUP
IBM PCN2 SNAP PCN2, PCN2L, LANSUP
Novell RX-NET TRXNET, TRXNET2
ΓòÉΓòÉΓòÉ 45. Help for ODINSUP Setup Box ΓòÉΓòÉΓòÉ
ODINSUP Setup Box
This dialog box allows you to select NDIS drivers to be removed from your IBM
application. It also allows you to select the ODI drivers that will replace the
NDIS drivers.
Select an NDIS driver and an ODI driver from the lists. Then click on "Replace
NDIS." The two drivers appear in the Current Configuration field.
After you select all the NDIS and ODI drivers you want to use, click on "OK."
Once the NDIS drivers are replaced by ODI drivers, IBM communication
information is passed to the ODI drivers instead of the NDIS drivers through
another driver called ODINSUP.
ΓòÉΓòÉΓòÉ 46. Help for ODINSUP Configuration Files ΓòÉΓòÉΓòÉ
ODINSUP Configuration Files
This dialog box displays the default paths to the PROTOCOL.INI, NET.CFG, and
CONFIG.SYS files. If these paths are incorrect (if you placed the files in
another path), enter the correct path next to each filename.
ΓòÉΓòÉΓòÉ 47. Help for Sharing a Network Board Between Client and Server ΓòÉΓòÉΓòÉ
Share NetWork Board Between Client and Server
If you want NetWare Client for OS/2 to communicate with NetWare Server for
OS/2, you need to share a network board between the client and server.
If there is only one network board in the computer, NetWare Server for OS/2
will control it. The only way NetWare Client for OS/2 can use the network board
is by sharing it with the server.
Network board sharing is accomplished when a special sharing LAN driver
(LANSHARE.SYS, TOKENSHR.SYS, or TOKENLNK.SYS) is loaded in NetWare Client for
OS/2, and when a the LAN driver for the installed board and a sharing LAN
driver are loaded in NetWare Server for OS/2.
ΓòÉΓòÉΓòÉ 48. Help for Specifying the NET.CFG File ΓòÉΓòÉΓòÉ
Help for Specifying the NET.CFG File
The NET.CFG file stores configuration information for NetWare Client for OS/2,
the ODI drivers, the protocols, and NetWare Server for OS/2.
Choose "Edit" to edit or create the NET.CFG file.
NOTE: The directory containing the NET.CFG file must be found in DPATH in your
CONFIG.SYS file. If you type a directory other than the root, that directory
will be added to DPATH in your CONFIG.SYS file.
For details about configuring remote workstations, see the NetWare Client for
OS/2 manual.
ΓòÉΓòÉΓòÉ 49. Help for Specifying the NET.CFG File ΓòÉΓòÉΓòÉ
Help for Specifying the NET.CFG File
The NET.CFG file stores configuration information for NetWare Client for OS/2,
the ODI drivers, the protocols, and NetWare Server for OS/2.
Choose "Edit" to edit or create the NET.CFG file.
NOTE: The directory containing the NET.CFG file must be found in DPATH in your
CONFIG.SYS file. If you type a directory other than the root, that directory
will be added to DPATH in your CONFIG.SYS file.
For details about configuring remote workstations, see the NetWare Client for
OS/2 manual.