home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
NTSCFG.ZIP
/
README.TXT
< prev
Wrap
Text File
|
1992-10-30
|
3KB
|
75 lines
HISTORY
When IBM developed OS/2 2.0, the network connection changed to follow more
standardized approach. The new standard allows the NIC (Network Interface
Card) manufacture to provide device driver for their card that will 'plug'
into network layer. On the other end, it allows network protocols to 'plug'
into the network card services through a common access point so they do not
have to write card specific pieces. Two standards emerged. They are NDIS
(Network Driver Interface Specification) and ODI (Open Data-Link Interface).
NDIS came from Microsoft and 3COM. ODI was Novell's counter to the NDIS
standard. Both are Medium Access Control (MAC) interfaces.
By using this new philosophy, it is theoritical possible to easily change
NIC cards or add new protocols to OS/2. Because the tools are not yet
available, ease is still theoretical. Do not dispair, there is hope for
the future.
CONSIDERATIONS:
Here is a list of considerations, observations, recommendations, and
restrictions. They may be some that are not covered as configuration for
OS/2 2.0 is not yet a science. It is still in the voodoo stages.
You will need both the Netware Requester for OS/2 2.0 and either
the OS/2 LAN Server 2.0 Requester or OS/2 Extended Services V1.0 or
higher (there will also be OS/2 Network Transport Services, NTS/2, in
the future) to have both NetBIOS and Netware communications.
The common name for the IBM portion of the network communication piece
is LAPS. This stands for LAN Adapter and Protocol Support.
The Netware Server MUST be 3.X or higher. You cannot reliably attach to
a 286 server.
There must be a Netware Server with the OS/2 utilities on the local ring.
If one is not available on a local ring, the connection may fail at
unpredictable intervals. Experiments with the Preferred Server accessed
through a bridge with a local Netware server have not been done.
The OS/2 2.0 Netware requester will work with the old OS/2 1.3 Netware
utilities.
You cannot use the new requester's utility installation procedure to
install the OS/2 1.3 utilities for Netware.
Unless every application you plan to run is off the server, a 120M hard
drive as the recommend minimum hard drive on a network attached workstation
(non-RIPL).
12M is the recommended RAM for a network attached workstation.
Netware for OS/2 does not have search drives like DOS. Include any drive
mappings on the workstation in the CONFIG.SYS. There are advantages to
this, as you can path out data paths (DPATH), etc.
You will need the Supervisor Password for your server to successfully
install the Server Utilities (creates new directories and copy files on
SYS directory).
The order of the protocol statements in the CONFIG.SYS is not just
important, some of them are critical.
The Netware utilities appear to create a new user definition in the \MAIL
directory of the server. Rights and user names may be carried over, but
login scripts and the system login script are not.
A REXX command file can be created to autorun the login procedure similar
to the scripts placed in a DOS AUTOEXEC.BAT. A program object of the
login command file can then be placed in the Startup Folder.
Netware will present the Netware login drive as L:\OS2.
This configuration has not been tested with an Ethernet card or TCP/IP.