Ref: 99960009
Title: 3+Open LAN Manager Version 1.0 Rel. Notes 4814-01
Date: 02-08-89

Copyright 3Com Corporation, 1991.  All rights reserved.


Part Number 4814-01
2/8/89
3+Open LAN Manager Version 1.0 Release Notes 1

.H1;Welcome

This introductory section provides some basic information about this
release notice and about how to take advantage of the information
contained in it.  The 3+Open LAN Manager Release Note is an integral
part of the 3+Open LAN Manager documentation.  If you have not done so
already, you should find the 3+Open Documentaion Roadmap that came
with the product.  This foldout card will guide you through the
documents required to install and use 3+Open LAN Manager.

.H1;Purpose
This release notice is intended to be read by the system administrator
prior to installation of the product, and also is intended for future
reference.

The release notice has 11 sections with valuable information about the
product.  The first 4 sections contain information you need before you
can install the system and should be read carefully:

Welcome
Hardware Requirements
Before Installing 3+Open LAN Manager 1.0
Installation and Setup Notes
The next 4 sections contain additional information about configuring
the system for specific environments, and should be read if applicable
to your configuration:

Performance Notes
3+ Compatibility Notes
IBM Application Notes
3Com DOS Maximizer/386 Notes
The remainder of the release notice contains information about
problems that may be encountered with the system, and should be read
carefully before using the system:

Software Developer Notes
Network Administration Notes
General Notes

.H1;Hardware Requirements

.H2;Disk and RAM Requirements
The following table lists the disk and RAM requirements for installing
3+Open LAN Manager Advanced System:

Machine Disk Drive RAM

 PC or PS/2Server 8 MB 4 MB
 3Server 12 MB 4 MB
 OS/2 Netstation 2 MB 2.5 MB
 DOS Netstation 360K 640K
 DOS Netstation with 3Com DOS
 Maximizer/386 1.2 MB 1 MB

.H2;Supported Adapter/Protocol Configurations
The following table shows the adapter/protocol combinations supported
in this release.
 DLC/NetBEUI Protocols
 OS/2 OS/2 DOS
 Adapter Server Netstation Netstation

 3Com 3Station
 3Com 3Server
 EtherLink (3C501)
 EtherLink Plus (3C505)
 EtherLink Plus with LPO
 EtherLink II (3C503)
 EtherLink/MC (3C523)
 TokenLink (3C603)
 TokenLink Plus (3C605)
 TokenLink Plus with LPO
 IBM Token Ring 1, 2, /A

 XNS Protocols
 OS/2 OS/2 DOS
 Adapter Server Netstation Netstation

 3Com 3Station
 3Com 3Server
 EtherLink (3C501)
 EtherLink Plus (3C505)
 EtherLink Plus with LPO
 EtherLink II (3C503)
 EtherLink/MC (3C523)
 TokenLink (3C603)
 TokenLink Plus (3C605)
 TokenLink Plus with LPO
 IBM Token Ring 1, 2, /A

.H2;Supported Server and Netstation Platforms
3+Open LAN Manager supports the 3Com 3Server (3Server386 and
386Upgrade) dedicated server platforms, and the 3Com 3Station
netstation platform.  In addition, common PC and PS/2 server and
netstation platforms are supported.  For more information about 3Com
3Servers, refer to 3+Open for 3Servers Installation and Setup Guide
which is included with the 3Server version of 3+Open LAN Manager.  For
more information about supported PC and PS/2 server and netstation
platforms, refer to the 3+Open LAN Manager Installation and Setup
Guide which is included with the Entry and Advanced versions of 3+Open
LAN Manager.

.H2;3Server Hardware Requirements
The 3Com 3Server is supported by this release for use as an 3+Open LAN
Manager Server.  As with all 3+Open servers, it must be configured
with 4 MB of memory.  In addition, the 3Server must be at the
following minimum hardware revision levels:

Component Revision

Motherboard part number 3600-01 or higher (Units shipped after 7/1/88
have updated part)  Motherboard ROM revision 1.33 or higher (units
shipped after 4/1/88 have updated part) Memory Expansion part number
4327-01 or higher (MEB units shipped after 12/1/88 are correct)

If your 3Server does not meet these, contact your 3Com authorized
reseller for instructions.

.H2;Configuring Communication Drivers on 3Servers
During the 3Server installation, the INSTAID program installs
communications drivers which are different depending on whether you
have a 3Server386, 386Upgrade, Port Expansion Board (PEB), Token
Connect Board (TCB), or AST Four Port expansion cards.
Communications ports are supported on the 3Server differently
depending on whether you have a 3Server386 or a 386Upgrade:

3Server386
Device Name Description

 COM1 Motherboard ASYNCH port
 COM2 IBM-compatible serial/parallel plug-in card
 COM3 & COM4 Motherboard SYNCH A&B ports
 COM5 to COM8 First AST Four Port card
 COM9 to COMC Second AST Four Port card

If you are using AST Four Port serial cards, there are command line
parameters that must be added to the CONFG.OS2 file.  First, choose an
Interrupt Request (IRQ) setting for each card.  You may use IRQ's 3
through 7, and if there are two cards they may both use the same
number.  In general the optimal choice is to use IRQ 5.  Make sure
there is no conflict between the IRQ number(s) for the AST cards and
other devices on the system, such as an IBM-compatible serial/parallel
card.  If there is only one AST card, make an entry of the form:

device=\os2\com01s.sys  /i:n

where n is the IRQ number.  If there are two AST cards, the entry will
be of the form:

device=\os2\com01s.sys  /I:n,m

where n is the IRQ number of the first card and m is the IRQ number of
the second card.

The first (or only) AST card must be configured to run at base address
1A0 (hex) and the second card must be configured to run at 2A0 (hex).
Refer to the AST Four Port installation manual for instructions on
configuring the AST cards to the correct base address and IRQ
settings.
386Upgrade without PEB or TCB
Device Name Description

 COM1 Motherboard ASYNCH port
 COM2 not assigned
 COM3 & COM4 Motherboard SYNCH A&B

386Upgrade with PEB
Device Name Description

 COM1 Motherboard ASYNCH port
 COM2 & COM3 Motherboard SYNCH A&B ports
 COM4 & COM5 PEB SYNCH S4&S5
 COM6 & COM7 PEB ASYNCH S2&S3
386Upgrade with TCB
 Device Name Description

 COM1 Motherboard ASYNCH port
 COM2 & COM3 Motherboard SYNCH A&B ports
 COM4 & COM5 TCB SYNCH S4&S5

If you change your 386Upgrade hardware configuration after installing
3+Open LAN Manager, you must run the INSTAID program again to install
the correct communications drivers.  The INSTAID program is located in
the C:\OS2\INSTALL directory.

.H2;Configuring an EtherLink/MC Adapter Card
The default value of the Interrupt Request parameter (IRQ) is set to 7
on the EtherLink/MC for some revisions of the IBM PS/2 machines.  The
correct value is 3, and may be set using the IBM PS/2 Reference
Diskette.  If the value is not set correctly,
the software will report error NET2186 during system initialization.


.H2;Configuring an EtherLink Plus or TokenLink Plus Adapter Card
To support the Link Plus Optimizer (LPO) onboard protocol processing,
EtherLink Plus and TokenLink Plus network cards require 256K of
onboard memory.  Currently, the cards come with 256K of memory
soldered on the board.  Revisions shipped prior to Oc
tober 1987 came with 128K and require the addition of four (64K by 4)
18-pin, 150 nanosecond DRAM chips (120 nanosecond chips may be
substituted).  Memory upgrade kits are available through 3Com
resellers as 3Com product number 3C505-B-128K.

These cards must be inserted into a 16-bit PC bus slot.  This may
require changing the interrupt, I/O base address, and DMA channel
settings (especially if the card has previously been in an 8-bit
slot). The recommended settings are listed here:

Setting Value

 Interrupt  3
 I/O base address 300
 DMA channel 5

Be sure to check that these settings do not interfere with other
peripheral or memory cards that you may have installed in your
machine.

Refer to the manual for your EtherLink Plus or TokenLink Plus for
installation instructions and additional information.

.H1;Before Installing 3+Open LAN Manager 1.0

Before you begin the installation process make backup copies of each
diskette (using the DISKCOPY utility), label each disk, and use the
backups for the installation process.  Write-protect all of the backup
3+Open installation disks except OS/2 Installation (this disk writes
back to itself during the installation process.)

.H2;Differences Between PC or PS/2 and 3Server Installation
The software provided for PC or PS/2 platforms is distributed on
diskettes and is installed as described in the 3+Open Documentation
Set (OS/2 for server) and 3+Open LAN Manager Installation and Setup
Guide (LAN Manager for server and netstations).

The software provided for 3Com 3Server platforms is distributed on
tape and is installed as described in the 3+Open for 3Servers
Installation and Setup Guide (OS/2 for server and LAN Manager for
server and netstations).

.H2;Pre-Release Software
There have been a number of changes and additions to this product from
various SDK and Beta versions of 3+Open LAN Manager from 3Com and OS/2
LAN Manager from Microsoft and other vendors.  Due to these software
changes, it is highly recommended that you perform a complete
installation of the 3+Open LAN Manager 1.0, beginning with
reformatting of the server hard disk drive.


.H2;Compaq DOS 3.31 Disk Format Incompatible With OS/2
PETS:  3645
.BR;The hard disk format created with the Compaq DOS 3.31 is not
compatible with OS/2.  If you have a disk formatted this way and you
are installing OS/2:

 Save the data on the disk (by copying to alternate media, such as
diskette).
 Remove all hard disk partitions using Compaq DOS 3.31 FDISK.
 Boot under OS/2 (OS/2 Installation diskette in drive A:.)
 Create new hard disk partitions using the OS/2 FDISK.
 Reformat using the OS/2 FORMAT.

.H2;Upgrading from Entry System to Advanced System Software
If you are upgrading your server from 3+Open LAN Manager Entry System
to 3+Open LAN Manager Advanced System (or changing from Advanced to
Entry System), you must remove the existing software on the server
before installing the new software.  Remove the software by selecting
the Remove LAN Manager software option from the Installation and Setup
program.

.H2;Building 360K DOS Boot Diskettes
PETS:  feature
.BR;Some DOS Netstation installations may fail due to disk size
limitations of a 360K disk.  If this problem is found, we recommend
using a 720K or 1.2MB disk drive.

.H1;Installation and Setup Notes
.H2;Checking for Overlayed Drive IDs
After your 3+Open installation to an OS/2 server, OS/2 netstation, or
DOS netstation is complete, check to be sure that no NET USE commands
in the STARTUP.CMD ( for OS/2) or AUTOEXEC.BAT (for DOS) file overlays
a disk partition on your hard disk.

For example if you had an E: partition on your hard drive, the
command:

net use e: \\server\os2apps

would attempt to overlay it.  To avoid this situation, edit to
appropriate file to change the E: in the NET USE command to another
letter (such as G:).

.H2;Using Netstation Utility Diskette to Install from 3Server
When following the instructions in the section Installing LAN Manager
onto the Netstation (page 4-10) in the 3+Open for 3Servers
Installation and Setup Guide, you must login (using netJlogon) to the
server after booting from the diskette and prior to
doing a NET USE to the server.

.H2;PC Servers Using OS/2 DOS Compatibility Mode
The 3+Open OS/2 Installation and Setup program sets up servers to
operate in OS/2 protected mode only.  Compatibility mode (also known
as DOS environment and as 3.x box) is used to run DOS applications
under OS/2.  To turn the compatibility mode on, use a text editor and
change the CONFIG.SYS file using the following steps:

1. Change line 17 of the file to protectonly=no.

The line currently reads protectonly=yes.

2. Restart the server hardware.

The server now restarts with the compatibility mode turned on.

.H2;Creating Generic DOS Netstation Diskettes
The 3+Open Installation and Setup Program can create DOS netstation
startup diskettes which can be customized for individual network
users.  In many network environments,it may be useful to generate
generic netstation startup diskettes.  These diskettes can be used in
any netstation on the LAN because they prompt for required
information.To create a generic DOS netstation startup diskette:

1. Follow the instructions in the 3+Open LAN Manager Installation and
Setup Guide creating a DOS netstation diskette.

2. To edit the AUTOEXEC.BAT file remove the (DOS environment
variables) HOME_SERVER= and HOME_SERVER_SECURITY.

The resulting DOS netstation diskette provides a generic logon and
network access.  All necessary information will be prompted for by the
logon process.

.H2;Logging on With a DOS Netstation Diskette
When the NET LOGON command is issued from the AUTOEXEC.BAT file, a
program called DLMLOGON is automatically started.  This program
validates the user name and password and initiates communication with
the network.  The DLMLOGON program does the following:

Prompts for a user name.

Looks for a DOS environment variable called HOME_SERVER.  If
HOME_SERVER does not exist, the DLMLOGON program prompts for the name
of the home server and sets the HOME_SERVER environment variable
accordingly.

Looks for the DOS environment variable called HOME_SERVER_SECURITY.
If the HOME_SERVER_SECURITY environment variable is not set, the
DLMLOGON program prompts the user for the type of security used at
their home server. (Valid responses are U for U
ser or S for Share.)

If user security is specified, the DLMLOGON program also asks for the
user's password.  In user security mode a link to the user's home
server is made using the user name and password to force a validation
of the user name and password.  If the user has provided valid
information and the server to which they are linking has them listed
with a valid account, drive H: on their local netstation is linked to
the USERDIRS shared directory.

If the administrator has not created an account on the server for the
user, the user logon is not allowed and an "Access denied" message
displays at the user's netstation.  If the user supplies an invalid
password, an "Invalid password" message is displayed.


.H2;Using IBM OS/2 1.1 Standard Edition (SE)
The 3+Open LAN Manager 1.0 is designed for installation on OS/2 1.0
(either the OS/2 included with this package for the server, or various
vendors versions of OS/2 1.0).  For server or netstation installation
of OS/2 1.1 SE, some additional steps are
required.

There are some restrictions with OS/2 1.1.  Only IBM's Standard
Edition (SE) of OS/2 1.1 is supported, and only on netstations.  IBM
OS/2 1.1 EE and other vendors versions of OS/2 1.1 have not yet been
tested with 3+Open LAN Manager.  IBM OS/2 1.1 SE is supported on AT,
AT clone and PS/2 netstations with the following adapter/protocol
combinations:

OS/2 Netstations with IBM OS/2 1.1 SE
DLC/
Adapter XNS NetBEUI

 3Com 3Station
 3Com 3Server
 EtherLink (3C501)
 EtherLink Plus (3C505)
 EtherLink Plus with LPO
 EtherLink II (3C503)
 EtherLink/MC (3C523)
 TokenLink (3C603)
 TokenLink Plus (3C605)
 TokenLink Plus with LPO
 IBM Token Ring
 IBM Token Ring 2
 IBM Token Ring /A

To install 3+Open LAN Manager with OS/2 1.1 SE, follow these steps.
You will need a text editor for modifying files described below:

1. Install IBM OS/2 1.1 SE on the server or netstation as documented
by IBM.

2. Install 3+Open LAN Manager as described in the 3+Open LAN Manager
Installation and Setup Guide or 3+Open for 3Servers Installation and
Setup Guide.

NOTE:  Do not reboot the server or netstation at this time.

3. Edit the CONFIG.SYS file in the root directory of your OS/2 boot
partition to make the following three changes.

Find the LIBPATH= line in the file.  Move the first directory path
 from between the '=' and the ';' to the end of the line.  For
 example, change:

 LIBPATH=C:\3open\os2wksta\lanman\netlib;.;C:\OS2\DLL;C:\;
 to
 LIBPATH=.;C:\OS2\DLL;C:\;C:\3open\os2wksta\lanman\netlib;

Remove the Named Pipes driver NAMPIPE.SYS from the bottom of the file.
Remove the invocation from the bottom of the LM block.  The line to be
removed will look something like:

DEVICE=C:\3OPEN\OS2WKSTA\LANMAN\NETPROG\NAMPIPE.SYS
/I:C:\3OPEN\OS2WKSTA\LANMAN

If there are lines which begin with SET PATH= and SET DPATH= in the
CONFIG.SYS file, then these should be modified to include the network
programs.  This path is suffixed with LANMAN\NETPROG and can be found
at the bottom of the STARTUP.CMD file, which should be in the same
directory as the CONFIG.SYS file.  For example, the bottom of the
STARTUP.CMD file will look something like:

 @REM **LM** ==================== OS/2 LAN MANAGER ===========
 @REM ======================= Do not modify this block =======
 @REM **LM** <LMPROG|C:\3OPEN\OS2WKSTA\LANMAN\NETPROG>
 path c:\3open\os2wksta\lanman\netprog;%PATH%
 @REM **LM** <LMPROG|C:\3OPEN\OS2WKSTA\LANMAN\NETPROG>
 @REM **LM** =================================================

and the CONFIG.SYS file will have the two lines:

 SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;
 SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;

 In this case, the two lines in the CONFIG.SYS file should be modified
 to include the path that was contained in the STARTUP.CMD file:
 SET PATH=C:\3open\os2wksta\lanman\netprog;C:\OS2;
 C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;
 SET DPATH=C:\3open\os2wksta\lanman\netprog;C:\OS2;
 C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;

4. Edit the STARTUP.CMD file and add the following line at the very
end of the file.

EXIT

This will cause the startup screen to clear and exit to the
Presentation Manager screen when initialization is complete.

5. Reboot your system.  It should now be a 3+Open OS/2 netstation or
server.

.H1;Performance Notes
.H2;OS/2 Disk Caching
PETS:  none
.BR;The OS/2 supplied with this release includes disk caching as an
option.  The installation of OS/2 turns caching on as the default.
The caching can be tuned to suit your network requirements.  You
should refer to the Update to Microsoft OS/2 Setup Guide for LAN
Manager Servers for detailed information on caching.  If you do
customize your caching parameters you should note that using the
NETSETUP program to do a modify will reset caching parameters to their
defaults.

.H2;OS/2 Cache Program Requires LAN Manager Installation
PETS:  3862
.BR;The cache program included with OS/2 in this release and installed by
the OS/2 installation requires LAN Manager to be installed with the
NETSETUP program before it will execute.  If OS/2 is installed and
restarted prior to the installation of LAN Manager, an error will
occur when the cache program is invoked during startup.  If this
happens, ignore the error and install LAN Manager.

.H1;3+ Compatibility Notes

3+ and 3+Open networks can operate and coexist together.  Refer to
Managing Combined Networks: 3+Open and 3+ for detailed information on
this subject.

.H2;Using MS-DOS Manager to Access 3+ Servers
The 3+Open MS-DOS Manager requires that links to 3+ servers be to
share names which conform to the 3+Open NetBIOS naming conventions.
This means that share names must be of the form:

\\finance_server\apps

Links to 3+ share names which are invalid NetBIOS names will not be
recognizable by the MS-DOS Manager and no files will be accessible
from the MS-DOS Manager program.  Examples of valid 3+ share names
which are not valid 3+Open NetBIOS names are:

\\3Server\mkt\apps
\\Pubs Lab Server:SPD:3Com\

.H2;3+MENUS Program
The 3+Menus program versions 1.3.1 and earlier require an update to
ensure compatibility with 3+Open.  If a DOS workstation has links open
to a 3+Open server, 3+Menus hangs the netstation if run.  An updated
version of this program has been included with this release, and is
located in the \APPS\DOSAPPS directory on the server.

.H2;3F & 3P LINK /DIR
The 3F and 3P programs included with 3+Share versions 1.3.1 and
earlier will report an internal error in a directory listing if a link
to a 3+Open server has been made with the NET USE command.  Updated
versions of these programs have been included with this release, and
are located in the \APPS\DOSAPPS directory on the server.  The 3F2 and
3P2 programs included with 3+ for OS/2 netstations do not have this
problem.

.H2;Token Ring Network Upgrade
The 3+Open Token Ring drivers follow an IEEE addressing standard which
differs from 3+ drivers.  Because of this, a combined 3+Open and 3+
Token Ring network will not interoperate unless 3+ netstations and
servers upgrade to drivers which are compatible and conform to the
IEEE standards.  The 3+Open drivers do conform to the IEEE standard
and are in the \3OPEN\DOSWKSTA\LANMAN\DRIVERS directory.  These
drivers will also work with 3+ and should be used to upgrade your 3+
netstations and servers.

The drivers have a letter B at the end and are:

.BR;TOK603B.SYS
.BR;TOK605B.SYS
.BR;TOK1060B.SYS
.BR;TOKIBMB.SYS

To upgrade your 3+ computers with the new drivers, copy the new driver
to the appropriate directory of the computer's boot volume and then
modify the CONFIG.SYS file to replace the old file name entry, such
as:

TOK603.SYS

with a B version, such as:

TOK603B.SYS

.H2;3+Name Service
PETS:  4006
.BR;3+Open Servers must have server names which are not registered as
server names or aliases with the 3+Name service.  If a server name
conflict exists, then OS/2 and DOS netstations will be unable to log
in or link to the 3+Open server.  When selecting a name for a 3+Open
server, use a name which is not already present in the 3+ Name
service.  If you are upgrading a 3+Share server to 3+Open, be sure to
delete its 3+Name service entry.

.H1;IBM Application Notes
Some of the following notes suggest changes to the file PROTOCOL.INI.
This file is located on the DOS boot disk as follows:

\3OPEN\DOSWKSTA\LANMAN\DRIVERS\PROTOCOL.INI

.H2;IBM LAN Manager Program
When using the 3Com DOS Netstation DLC protocol with the IBM LAN
Manager Program, the SAPS parameter in the DLC section of the
PROTOCOL.INI file must be set to 254:

[DLC]
.BR;SAPS = 254

.H2;IBM 3270 Emulation Program
When using DOS DLC with the IBM 3270 Emulation Program the interrupt
level used on any 3Com EtherLink and TokenLink adapter cards must be
set to 2.

The IBM 3270 Emulation Program V3.0 with DLC Token Ring host
connection through a 3174 controller does not function properly in
this release.

.H2;IBM PC Network Program 1.3
IBM's PC Network Program 1.3 and the 3Com DOS DLC can run on a 640K
machine with either Base or Extended services.  DLC should be
configured in the following way:

[DLC]
.BR;STATIONS = 32
.BR;SAPS = 32

The NET START command in AUTOEXEC.BAT of the PC Network Program 1.3
should contain the following parameters:

/CAC:0  /RQB:512  /REQ:2  /PC1:128  /PC2:128  /PC3:128  /USN:1

If Extended services is to provide Remote IPL support, then the
machine should be dedicated due to memory limitations.

.H1;3Com DOS Maximizer/386 Notes
PETS:  39836, 3971, 4003
.BR;The 3+Open LAN Manager Installation and Setup program installs the
3Com DOS Maximizer/386 using parameters which are designed to work for
the widest range of combinations of hardware.  The program is highly
configurable, and a technical reference containing tuning information
is provided in 4 text files included with this release.  These files
are installed on the server as:

.BR;\3OPEN\DOSDRV\3COMEMM\README.LOD
.BR;\3OPEN\DOSDRV\3COMEMM\README.EMM
.BR;\3OPEN\DOSDRV\3COMEMM\XBIOS.DOC
.BR;\3OPEN\DOSDRV\3COMEMM\ULTIMATE.DOC

Some of the following notes suggest changes to the files CONFIG.SYS or
PROTOCOL.INI.  These files are created by the Installation and Setup
program on the DOS netstation boot disk as follows:

.BR;\CONFIG.SYS
.BR;\3OPEN\DOSWKSTA\LANMAN\DRIVERS\PROTOCOL.INI

.H2;Programs Using High Memory
PETS:  4036
.BR;The DOS Maximizer/386 program is incompatible with programs which use
all of high memory themselves.  This includes programs such as MS
Windows 2.1 and MS Windows 386 1.0.

.H2;CONFIG.SYS Entry Format
PETS:  4036The DOS Maximizer/386 program requires that there be
.BR;exactly one space between each parameter entry in the CONFIG.SYS file.
If there is more than one space, the remainder of the line will be
ignored.

.H2;Conflicts with Memory Mapped Devices
The 3Com DOS Maximizer/386 software does not know the location of the
memory mapped I/O address space used by any add on devices, including
3Com network adapter cards.  Because of this, the Installation and
Setup program will always reserve the most frequently used memory
mapped locations, C000 to C600, for memory mapped devices.  If this is
not the location used by your hardware, you must specify the address
space to the 3Com memory saving software by editing the CONFIG.SYS
file.

After installation, enter the proper start and length of the memory
I/O addressing space of the adapter card in question using the RAM
keyword. In the case of multiple cards conflicting with the memory
saving software more than one RAM keyword should be used. The address
parameter values should be entered in paragraph numbers.

The 3Com DOS Maximizer is designed to avoid conflicts with memory
mapped devices by setting various parameters.  The parameters are
listed below for each adapter (the applicable protocol is specified to
the right of the adapter name).  For example, the IBM Token ring
adapter requires one particular setting when run with XNS, and another
setting when run with DLC.  Take care that you are following the
correct procedure listed for both your adapter card and the protocol
running on your workstation

The lines below identify which CONFIG.SYS/ lines must be modified.
The line itself is installed by NETSETUP.  Only the parameter changes
indicated need to be made manually.

.H2;3Com TokenLink Adapter
If this adapter is used in a 16 bit slot, the driver must be loaded so
it uses DMACHANNEL 0.  This is done by adding or changing the
DMACHANNEL= entry in the TokenLink section of the PROTOCOL.INI file:

.BR;[TokenLink]
.BR;drivername=TLNK$
.BR;dmachannel=0
.BR;There is no change required if a TokenLink adapter is installed in an
8 bit slot.

.H2;IBM Token Ring Adapter
If any IBM Token Ring adapter is used then the 3COMEMM.SYS RAM=, EMS=,
and ROM= (PS/2 only) entries in CONFIG.SYS must be changed or added
according to the following table:

XNS Protocols DLC Protocols

.BR;IBM Token Ring Adapter ram=C800-D600 ram=C800-D000
.BR;ems=0 ems=0
.BR;IBM Token Ring Adapter 2 ram=C800-D600 ram=C800-D000
.BR;ems=0 ems=0
.BR;IBM Token Ring Adapter /A ram=D800-DC00 ram=D800-DC00
.BR;ems=0 ems=0
.BR;rom=CC00-CE00 rom=CC00-CE00

For example, with an IBM Token Ring 2 adapter and the DLC protocols,
the CONFIG.SYS entries would be:

DEVICE=\3OPEN\DOSWKSTA\LANMAN\DRIVERS\3comemm.sys ram=c800-d000
ems=0

With an IBM Token Ring /A adapter and the DLC protocols, the
CONFIG.SYS entries would be:

DEVICE=\3OPEN\DOSWKSTA\LANMAN\DRIVERS\3comemm.sys ram=d800-dc00
ems=0 rom=cc00-ce00

If these values do not work correctly on PS/2 computers with the IBM
Token Ring Adapter /A, you may have to boot the reference diskette for
the PS/2, examine the ROM and RAM addresses, and round up those values
to the nearest paragraph.  For example if the ROM address is found to
be CC000-CDFFF the value used in the CONFIG.SYS line for 3COMEMM.SYS
becomes:

DEVICE=\3OPEN\DOSWKSTA\LANMAN\DRIVERS\3comemm.sys ram=D800-DC00
ems=0 rom=CC00-CE00

.H2;3Com EtherLink Plus Adapter
The combination of 3COMEMM.SYS and adapter-based protocols is not
supported in this release.  However, this should not pose a memory
space problem because the adapter-based protocols leave most of the
workstation memory available.

.H2;3Com EtherLink II Adapter Configured with Memory Mapping
Some combinations of video display cards and the EtherLink II can
produce address conflicts.  These will be observed by getting the
messages "Locator not responding (XNS)" and "network name not found
(DLC)" after NETLOGON.  To fix this problem, change the memory address
jumper on the EtherLink II to the DISABLE position.  Note that other
circumstances may also produce the same messages.

.H1;Software Developer Notes
.H2;NetWkstaSetUid API Change
PETS:  Microsoft Release Notice #2
.BR;The netwkstasetuid API was changed to not allow a servername
parameter.  The value must be NULL.

.H2;Named Pipes With Multiple Threads
PETS:  Microsoft Release Notice #15
.BR;If a process does a DosBufReset in one thread and a DosAsyncRead in
another thread on named pipes it could get blocked in the file system
forever.  The process must assure that the DosBufReset is serialized
across the threads if the DosBufReset is being issued on a named pipe.

.H1;Network Administration Notes
.H2;Using 3+Open LAN Manager in a NETMAP Environment
PETS:  none
.BR;If the 3+Open LAN Manager OS/2 Server is installed in a network with
NETMAP Network Management protocols and the 3Com Network Control
System (NCS), then the NETMAP.OS2 driver included in this release
should be installed on the OS/2 server.  This is done by adding the
following entry to CONFIG.SYS after the other network driver entries:

DEVICE=\3OPEN\SERVER\LANMAN\DRIVERS\Netmap.os2  /N:servername

where servername is the name you wish to have registered with NCS
(normally this would be the server name given when installing 3+Open
LAN Manager).

.H2;User Shares Ending in $
PETS:  Microsoft Release Notice #3
.BR;Net Profile or NetProfileSave() will not save user shares that end in
a $.  Therefore, you should not create shares that end in a $.

.H2;Logging of Server Out of Resources Errors
PETS:  Microsoft Release Notice #9
.BR;When the server runs out resources (i.e. NUMBIGBUF) it will log the
error only once.  If you stop and restart the server this does not get
reset.  You must stop and restart the workstation to get the logging
reset.

.H2;NET ADMIN Error Messages Missing
PETS:  Microsoft Release Notice #10
.BR;If you use NET ADMIN program prior to starting the workstation, the
help (F1 key) will fail with a "cannot find help file" message.  You
need to do a NET START WORKSTATION before entering NET ADMIN to get
the help commands to work.

.H2;NET ADMIN Sharing of COMM devices
PETS:  Microsoft Release Notice #12
.BR;The NET ADMIN program does not share COMM devices correctly.  It
creates the share without permissions, where in fact it should create
it with all permissions.  The workaround is to create the share from
the command line, or to use NET ADMIN to set the permissions on the
share after creating the share.

.H2;NET ADMIN User Count
PETS:  3949
.BR;The NET ADMIN program does not include administrators in its user
count.

.H2;NET ADMIN Error Count
PETS:  3806
.BR;When a log file is reset, the error count is not reset to 0, causing
the error count not to agree with the number of entries in the log
file.

.H2;DOS Netstations Auto Reconnection
PETS:  4114,  4132
.BR;If the administrator deletes a session or removes a share name, and
then restores the share, DOS netstations may be unable to reconnect
automatically.  In this case the user will have to do a NET USE to
restore the link.

.H1;General Notes
.H2;IBM PS/2 Model 80 ESDI Controller Problem
PETS:  3685
.BR;Some older versions of the PS/2 Model 80 computers with ESDI disk
controllers have a data corruption problem which occurs under heavy
load.  The problem is fixed by updating the firmware on the board.  If
you are having problems with a PS/2 which has
an ESDI controller, contact your dealer or IBM support (1-800-IBM-
PROD) for a firmware upgrade.

.H2;OS/2 DOS Compatibility Mode
Some versions of vendor OS/2 have stability problems while running in
the DOS compatibility mode.  This may occur while running some
applications.

.H2;MS-DOS Net Popup
PETS:  # 3513,3516,3657,4029,3653,3713,3785
.BR;DOS messenger handles only one message at a time so if a message is
displayed on screen no more messages will be received until the
current message is removed.  The sender gets "Can't find named
recipient" error message.  Some applications create an
environment that keeps received messages from popping up.  If you are
getting popup messages when at the DOS prompt but not in certain
applications, it's most likely an incompatibility between the
application and the popup facility.

.H2;MS-DOS Net Popup Video Incompatibilities
PETS:  3513, 3516, 3657, 3783, 4029, 3880
.BR;The MS-DOS Net Popup program included with this release does not work
with some video boards.

.H2;DOS NET Command Failure When Invalid Drives in Path
PETS:  3702
.BR;The NET command will not operate correctly under DOS if invalid drives
in its search path are encountered before it finds its configuration
control file, LANMAN.INI.

.H2;Universal Name Convention (UNC) Names Invalid with Printer
PETS:  3731
.BR;Use of UNC names for redirected printers is not supported in this
release.  Use the NET USE command and the device name:

NET  USE   LPT1:  \\Server\Printername
COPY  file.txt   LPT1:

instead of

COPY  file.txt   \\Server\Printername

.H2;Floppy Drive Access Problems Under OS/2
PETS:  3688
.BR;Some floppy drives have hardware problems under OS/2, especially when
network adapter cards are used with burst mode DMA.  If you are having
problems with the floppy drive on an OS/2 server or netstation, check
the DMA mode of the network adapter and make sure it is not using
burst mode.  Refer to the 3+Open Network System Guide for information
on changing parameters of the supported network adapters.

.H2;Expanded Memory Not Supported
PETS:  4049
.BR;The OS/2 supplied with this release does not recognize expanded
memory.
