Ref: 99980168
Title: 3+OS/2 Netstation S/W Release Note number 4641-00
Date: 03-31-88

Copyright 3Com Corporation, 1991.  All rights reserved.

3+ OS/2 Netstation Software Release Notes
Developers Release Note number 4641-00

This document contains important information about 3+ OS/2
Netstation Software.  Read these notes, and then refer to 3+
OS/2 Netstation User Guide, before you install and use the
software.

This document is divided into five sections:

.BR;Network Adapter Card Requirements
.BR;Installing the Software
.BR;Printing
.BR;Netstations Connected to a Token Ring
.BR;Messages

The abbreviated title, User, refers to the 3+ OS/2 Netstation
User Guide.

.H1;Network Adapter Card Requirements

Use only 3Com EtherLink Plus or TokenLink
Plus Card with 3+ OS/2 Netstation Software

User, p 1-2.

Only the 3Com EtherLink Plus (3C505) and TokenLink
Plus (3C605) network adapter cards are supported for this
Developer's Release of 3+ OS/2 Netstation Software.
Both cards are intelligent and have an Intel 80186
processor.  (This processor is a one inch square chip
located near the center of the board.)

To distinguish between the cards, examine the end plate
that screws into the back panel of the PC.  The EtherLink
Plus card has two connectors on its end plate, a coaxial
BNC and a 15 pin D-series connector.  The TokenLink
Plus card has only a 9 pin D-Series connector on its end
plate.

256 Kilobytes (KB) of Memory Required

User, p 1-2

To support onboard protocol processing, 256 KB of
memory is required on the network card.  All TokenLink
Plus cards have been shipped with this amount of memory
already installed.  EtherLink Plus cards shipped October
1987 or later also come with 256 KB of memory installed.
Pre-October 1987 versions of EtherLink Plus were
shipped with only 128 KB.  If you have an older version
of the EtherLink Plus and have not already upgraded it to
256 KB, you need to do so before you can run 3+ OS/2
Netstation Software.  Add four 18-pin, 64 KB-by-4, 150
nanosecond DRAM chips (120 nanosecond chips may be
substituted).  Memory upgrade kits are available through
3Com resellers as product  number 3C505-B-128KB.
Refer to the EtherLink Plus Installation Guide for
installation instructions.

Install Network Adapter Card in 16-bit AT Bus Slot

User, p. 1-2

Install your 3Com EtherLink Plus or TokenLink Plus
network card in a 16-bit AT 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).  Refer to the EtherLink Plus
Installation Guide or the TokenLink Plus Installation
Guide for installation instructions.

Check Interrupt, I/O Base Address, and DMA
Channel settings

User, p 1-2

The recommended settings for the EtherLink Plus and
TokenLink Plus cards are:

.BR;Interrupt = 3
.BR;I/O base address = 300 hex
.BR;DMA channel = 5

Verify that these settings do not interfere with settings
other peripheral or memory cards that you may have
installed in your machine. Refer to the EtherLink Plus
Installation Guide or the TokenLink Plus Installation
Guide for installation instructions and allowable jumper
settings for use with 16-bit slots.

The Locator Service

User, p. 1-3

The 3Com NetBIOS protocol software which is
downloaded onto the intelligent network card by 3+
OS/2 Netstation Software requires the presence of the
3Com Locator Service on the local network.  The service
is an optimized central naming service.  It is best to run
the Locator Service on one of your 3Com 3+ network
servers such as a 3Server or PC server.

If the Locator Service is not currently running on any of
your 3+ network servers, install it (preferably on the
server that is running the 3+Name service).  You install
the Locator Service using the server's installation and
configuration program.  The Locator Service should be
running on one and only one machine on the local
network.

If you do not have the Locator Service software (for
example, the software is not customarily sold for
Macintosh-only networks, where NetBIOS is not
needed), please contact your reseller for help.

.H1;Installing the Software

Reinstalling 3+ OS/2 Netstation Software

User, p. 1-4

To install the developer's release of 3+ OS/2 Netstation
Software over an earlier version of the software do the
following:

1. In a text editor modify your
STARTUP.CMD batch file by making the
NETINIT or NET START RDR line into a
REMark.

When you display the file with a text editor, you
should find one (but not both) of these lines near
the top of the file.  If you cannot find either line but
do see the line CALL 3COMINIT.CMD, make it
into a remark.

Type the characters REM at the beginning of the
line to make it into a non-executing remark.


2. Restart your netstation.

 Ignore startup messages pertaining to 3+ OS/2
Netstation Software.  The software will not start
until you install it again.

3. Install 3+ OS/2 Netstation Software as
explained in Chapter 1 of the 3+ OS/2
Netstation User Guide.

To re-install the developer's release of 3+ OS/2
Netstation Software do the following:

1. Use a text editor to convert the CALL
   3COMINIT.CMD line in your
   STARTUP.CMD file into a remark.

The CALL 3COMINIT.CMD line is near the top of
the file.  Type the characters REM at the beginning
of the line to make it into a non-executing remark.

2. Restart your netstation.

Ignore startup messages pertaining to 3+ OS/2
Netstation Software.  The software will not start
until you install it again.


3. Install 3+ OS/2 Netstation Software as
explained in Chapter 1 of the 3+ OS/2
Netstation User Guide.


Installing Microsoft LAN Manager and 3+ OS/2
Netstation Software on Same Netstation

User, p. 1-4

If you wish to install the Microsoft LAN Manager and
the 3+ OS/2 Netstation Software on the same netstation,
observe the following:

Always install the 3+ OS/2 Netstation Software after
you install the Microsoft LAN Manager.

Be sure you are using a version of the LAN Manager
released in March 1988 or later.

.H1;Printing

Printing from the DOS Environment

User, p. 2-11

There are MS-DOS applications which permit printing
while in the application.  Several of these applications,
including WordStar and PE2, spool to the linked 3+
printer correctly but then cause the DOS environment to
hang when you exit them.  Although OS/2 sessions
remain functional, you have to reboot in order to restore
the DOS environment to operation.

If you are using such an application, print to a text file,
and then use the system COPY command to print the file
on a linked printer.


Printing from the OS/2 Environment with the
System COPY Command

User, p. 2-11

Do NOT use the following system commands or their
variants in an OS/2 session:

COPY filename PRN:

COPY *.* LPT1:

If you do, one of the following messages will be
displayed:

SYS0112:  There is not enough space on the
disk.  0 file(s) copied.

The network has a data fault.

You can use COPY from the DOS environment.

to print to a linked printer
Unlinking the PRN: Device:

User, p. 2-11

The PRN: (LPT1:) device is not treated the same as the
other LPT devices (LPT2:, LPT3:, and so on).  When a
netstation user unlinks the PRN: device without relinking
it, the printer connection still appears active to the 3+
server.  This only presents a problem if the administrator
needs to UNSHARE this printer.  When the netstation
logs out, the printer link is broken and the printer
becomes available for unsharing.


.H1;Netstations Connected to a Token Ring

Your token ring netstation must be properly connected to
the token ring network before it is booted.  Otherwise, it
will generate a system trap 000D when it is booted.

Also, trap 000D can occur when the maximum number
of Network Control Blocks (NCBs) configured for the
TokenRing Plus adapter card has been exceeded by the
NetBIOS user.  To eliminate this problem, increase the
value of the /N parameter in the
PROGRAM=C:\path\NBA.EXE line of the LDR.CFG
file.  This file is located in the \LANMAN\MINDS
directory.

.H1;Messages
User, p A-1

*** Locator not responding.

Meaning The computer name in the LANMAN.INI file has
more than 15 characters.  For example

 computername =

 VERY_LONG_COMPUTER_NAME

Action Shorten the name.

Meaning There are older, unsupported entries present in
LANMAN.INI, such as

 wrkcomment =
 wrkhidden = yes
 wrkannounce = 60
 wrkanncdelta = 3000

Action Make these entries into comments out by
beginning them with a semicolon, or  delete them
altogether.  They will only be present if older
versions of the LANMAN.INI file has been
installed on the workstation.

*** Locator not responding, or
*** Error 2184 loading the Redirector..

Meaning The version of LAN Manager installed on your
netstation is dated 1/23/88 or earlier.

Action Make the following line into a comment by
typing a semicolon in front of it:

 ;wrkservices = messenger,popup


*** Sharename not found.

Meaning  The sharename does not exist.

The sharename exists but is too long.

Action  Select a different sharename.

Shorten the sharename until the error disappears.
