Ref: 99960022
Title: 3+Version 1.5 and 1.3.1 Release Notes 4703-01 & 3369-01
Date: 05-31-89

Copyright 3Com Corporation, 1991.  All rights reserved.


(PageMaker is a registered trademark of Aldus Corporation.)

.BR;3+ Version 1.5
.BR;Part Number  4703-01
.BR;5/31/89
.BR;Administrator's Release Notes

.BR;3+ Version 1.3.1
.BR;Part Number  3369-01
.BR;5/31/89

This document provides information related to the 3+ version
1.5 network software.  Read this information carefully before
installing or using 3+.  This set of release notes is divided into
the following sections:

.BR;Server Installation and Configuration
.BR;General Information
.BR;3Com Servers (3S/400 and 3S/200 series)
.BR;PC Servers
.BR;3+NetDOS
.BR;3+Backup
.BR;3+ for Macintosh Users
.BR;3+ for PC Users

The abbreviated titles for the guides that the release notes
reference are:

 - 3Server386 3Server386 Guide
 - Admin 3+ AdministratorUs Guide
 - Install 3+ Installation and Setup Guide
 - NetDOS 3+NetDOS Installation Guide
 - Install 3Server3 and 3Server386 Quick Installation
   Guide
 - Start 3+Start Supplement for the 3S/400
 - TokenLink TokenLink Installation Guide


.H1;Server Installation and Configuration
.BR;The following release notes describe server installation and
configuration information and are divided into sections.  These
sections are:

 - General server-notes that apply to both 3Com and PC
   servers.

 - 3Com server-notes that discuss information specific to
   3Com servers.

 - PC server-notes that discuss information specific to PC
   servers.

General Server Installation and Configuration
The following notes describe installation and configuration
information that applies to servers in general, both 3Com and
PC.  For information specific to dedicated 3Com or PC
servers, see the appropriate notes later in this section.

.BR;Installing 3+ 1.5 on a 3+ 1.3.1 or Earlier Server
.BR;To install 3+ 1.5 on a server that already contains an earlier
version of 3+, you must back up the server to tape or diskette,
reformat the disk, install 3+ 1.5, and then restore your
application programs and data files from tape or diskette.  Do
not attempt to load 3+ 1.5 over an earlier version of 3+
without performing these steps.  If you have a 3Server3
without a cache card, you may have to retune some of the
services.

.BR;Disabling the 3+NetConnect Service
.BR;The 3+NetConnect service cannot be disabled with the 3OPT
program, as you can with other services.  If you wish to
remove the service, you may do so with the 3INS program.

.BR;Checking the 3+NetConnect Network Number
.BR;After installing the 3+NetConnect service in 3Com or PC
servers, be sure to run 3OPT and check that the NetConnect
network number is not zero or blank, with no value specified.
If this is the case, enter a network number that is unique to the
network.  Details on choosing and entering a network number
can be found in the 3+ Installation and Setup Guide.

.BR;1.5 Server Using Both Ethernet and LocalTalk
.BR;If a 3+ 1.5 server has Ethernet and a secondary LocalTalk via
NetConnect, 3Com recommends that you set the following
values to the same setting.  The default setting is 8.  The
parameters are:

 - The LocalTalk driver buffers (-b).  This parameter is part
   of the 2APPLE.SYS or 2APPLE38.SYS line in the
   server's CONFIG.SYS file.

 - The 3+Share receive buffers set with 3OPT.

 - The 3+NetConnect receive buffers set with 3OPT.

If you choose not to follow this recommendation, you should
review the number of LocalTalk buffers (-b) in the server's
CONFIG.SYS file.  This number must equal the number of
3+NetConnect buffers.  This value must be equal to or greater
than the number of 3+Share receive buffers.

If parameters are not set to the same value, reliability problems
on the server can result.  This is especially true when there is
heavy server access on LocalTalk.

The Ethernet hold-back buffers (-h) parameter is a part of the
ETH3.SYS or ETH386.SYS line in the server's
CONFIG.SYS file.  This parameter should be set to a value
greater than or equal to the 3+NetConnect receive buffers.
Other services such as Backup, Start, Route, Remote, and
high-speed serial printers also need -h buffers.

.BR;Installing LocalTalk and 3+Route
.BR;When installing both LocalTalk NetConnect and  3+Route, the
number of receive buffers is changed to 4.  This value should
be reset to 8 using the 3OPT program.  To change this value,
do the following:

1. Start the 3OPT program with the server in the
  off-line mode.

See the 3+ Network Tuning Guide for instructions.

2. From the 3OPT Main Menu screen, select the
   NetConnect and Route option by highlighting it
   with the selection bar and typing 'C'.

3. Select the Allocate Buffers option.

4. Change the receive buffers to 8, and then press
[Ctrl]+A twice to save the changed values.

5. At the 3OPT Main Menu, type 'S' to save the
   configuration.

6. Type 'Q' to quit the 3OPT program.

You may now reboot the server.

.BR;Setting 3+Share Receive and Transmit Buffers
.BR;The number of receive and transmit buffers for 3+Share have
been set low to accommodate LocalTalk NetConnect and its
parameter settings while preserving data integrity.  For servers
not running LocalTalk NetConnect, you can increase
performance by running the 3OPT server tuning program.

The following are optimal values for each type of server when
not running LocalTalk NetConnect.

.BR;Server Type Receive Transmit
.BR;PC server   4   5
.BR;3S/200 12 14
.BR;3S/400 20 28

Follow these steps to change the buffers:

1. Start the 3OPT program with the server in the
   off-line mode.

See the 3+ Network Tuning Guide for instructions.

2. From the 3OPT Main Menu screen, select the
   Share option by highlighting it with the selection bar and typing
   'C'.

3. Change the appropriate values as listed above.

4. Press [Ctrl]+A twice to save the current
   values.

5. At the 3OPT Main Menu, type 'S' to save the
   configuration.

6. Type 'Q' to quit the 3OPT program.

   You may now reboot the server.

.BR;Using Nonalphabetic Characters with Name and 3+Share
.BR;Using certain nonalphabetic characters in user and share folder
names can result in irregular handling of folders and user
names.  For example, if a cent sign or a yen symbol are
entered as part of a user name, and another name is added with
a different symbol in the relative location, (fred and fred),
the name service will interpret the fred$ as a duplicate of fred
and refuse to add it.

In other cases, if a shared folder is created that has a name
containing one of the problematic international characters, and
a user tries to link to the folder, a new folder will be created
that does not contain the folders and files of the original.  For
example, if the file revenue is created as a shared file, the
user would actually link to a file called revenue.  The folder
revenue would not contain the files found in revenue, and the
user would have no way of accessing the files and folders
found in revenue.

.BR;Installing Internal Modems on a Token Ring Network
.BR;If you install an internal modem in a server, set the modem
switch to COM2.  This sets the modem to use interrupt level
3.  If you have any other adapters using this interrupt, either
reconfigure them or remove them.  (Three is the default
interrupt setting for 3Com's Ethernet and Token Ring
adapters, but  does not conflict with the Ethernet on the
3Server3 and 3Server386 motherboard.)

.BR;Mixing Hayes and Microcom Modems
.BR;If your server has a Microcom modem configured in SX
mode, only PCs or other servers that are using Microcom
modems in SX mode can communicate with each other.

If you need to use Hayes and Microcom modems on the same
network, you may configure your Microcom AX1200 or
AX2400 for Hayes compatibility rather than SX mode.  See
Appendix B of the 3+ Installation and Setup Guide for detailed
information.

.BR;Changing the Baud Rate on a Microcom Modem
.BR;To adjust the baud rate on a Microcom modem, change the
modem's rear switches to the desired baud rate and then reset
the modem.  If it fails to hang up correctly after this procedure,
follow the directions in the Microcom manual to change the
modem back to its default settings.  Then adjust the rear
switches once again and reset the modem.  If the modem is
installed on a server, run the 3INS program and adjust the port
settings to the new baud rate; then reset the server.

.BR;Supported 3+NetConnect Configurations
.BR;The following combinations of adapters for primary and
secondary networks are the only configurations supported
with 3+NetConnect on the three types of servers.

3Server3

.BR;Without any Board
.BR;Primary Secondary
.BR;Ethernet on motherboard LocalTalk on motherboard


.BR;With Token Connection Board
.BR;Primary Secondary
.BR;Ethernet on motherboard Token Connection Board
.BR;Ethernet on motherboard LocalTalk on Token Connection Board
.BR;Token Connection Board LocalTalk on Token Connection Board
.BR;Token Connection Board Ethernet on motherboard

.BR;With Port Expansion Board
.BR;Primary Secondary
.BR;Ethernet on motherboard LocalTalk on Port Expansion Board

3Server386

.BR;Primary Secondary
.BR;Ethernet on motherboard EtherLink
 EtherLink II
 TokenLink
 TokenLink Plus*
 LocalTalk on motherboard
 TokenLink Ethernet on motherboard
 TokenLink
 TokenLink Plus*
 LocalTalk on motherboard
 *  Must use DMA = 5

PC Server

Primary Secondary
EtherLink II  EtherLink
 EtherLink II
 EtherLink Plus
 TokenLink
 TokenLink Plus*
 Apple LocalTalk PC card
EtherLink Plus  EtherLink
 EtherLink II
 EtherLink Plus
 TokenLink
 TokenLink Plus*
 Apple LocalTalk PC card
TokenLink Plus EtherLink
 EtherLink II
 EtherLink Plus
 TokenLink
 TokenLink Plus*
 Apple LocalTalk PC card
EtherLink/MC EtherLink/MC
*  Must use DMA = 5

.BR;3+NetConnect, 3+Route, and 3+Remote
.BR;Parameters
.BR;Check all 3+NetConnect, 3+Route, and 3+Remote parameters
using 3OPT to make sure that they are set to non-zero values.
These values should be unique to the primary network.

.H1;3Com Server Installation and Configuration
The following notes discuss installation and configuration
information specific to 3Com servers.  For general server
information or for information specific to PC servers, see the
appropriate notes in this section.

.BR;3Server3 with Locator
.BR;A 3Server3 with the Locator service may hang if you reset it at
the same time as you reset a netstation that uses the full
implementation of NetBIOS.  The server will stop, and the
message Loading Locator or Loading Share will
appear on the LCD.  To remedy the problem, turn off or reset
the netstation.

.BR;New Single Port Switch
.BR;A new parameter has been added to the APPLE.SYS and
APPLE386.SYS drivers for 3Com 3S/20x and 3S/40x
servers.  If your server has nothing connected to the serial
ports, you can increase the efficiency of LocalTalk by using
this parameter.  To implement this single port switch, modify
the appropriate line in the server's CONFIG.SYS file as
follows:

2apple.sys /s

or

2apple38.sys /s

.BR;Reinstallation on a 3S/200 Server Without a Cache Card
.BR;The reinstallation software assumes the presence of a cache
card (memory expansion card) on the 3S/200 server.  If you
install 3+Backup and you do not have this card, the number of
buffers for CIOSYS will be far too large to fit into main
memory.

To avoid this problem without adding a cache card to the
server, run the 3OPT program and reduce the number of
CIOSYS disk drive buffer pools to a manageable level, usually
about 16.

For optimal network performance, it is recommended that a
cache card be installed in the server.

.BR;Location of the Network Number on 3Com Servers with a Tape Drive
.BR;QInstall, pp. 2-17, 3-15
.BR;Install, p. 6-3
.BR;If you purchased a 3Server3 or 3Server386 with a tape drive
(models 3S/201, 3S/202, 3S/401, or 3S/402), the network
number for the server is found on the 3+ System Tape
included with the unit.  You may be required to enter this
number when you install the unit.

The instructions in the 3Server3 and 3Server386 Quick
Installation Guide and the 3+ Installation and Setup Guide
refer you to the 3+Share/Server Name diskette for the number,
but this disk is not included with servers containing a tape
drive.

.BR;The 3+Start Supplement for the 3S/400 Start
.BR;The 3+Start Supplement for the 3S/400 now applies to 3S/200
servers as well.

.BR;Quick Installation on a Token Ring Network
.BR;Running the Quick Installation program on a server connected
to a token ring network may produce one of the following
error messages on the server's LCD at the end of the
procedure:

Interrupt - F  (on a 3Server3)

or

.BR;Sync ILoop Test
.BR;Failed   (on a 3Server386)

The error message may also appear when you reset the server
from a netstation, such as after running SETUP.  To recover
from the error, reset the server.  It will start up and operate
normally.

Repartitioning the Hard Disk on a 3Server3 or 3Server386
If you repartition the hard disk or disk expansion unit, and
install 3+ 1.5 software on the 3Server3 or 3Server386, you
must run the 3OPT program to save the new CIOSYS values.
Otherwise, the server will display the error message
Interrupt - 6 on the LCD.  To save the new CIOSYS
values, do the following:

1. Start the 3OPT program with the server in the
off-line mode.

See the 3+ Network Tuning Guide for instructions.

2. From the 3OPT Main Menu screen, select the
CIOSYS option by highlighting it with the
selection bar and typing 'C'.

3. With the CIOSYS menu on the screen, press
[Ctrl]+A to save the current values.  Check
CIOSYS disk drive buffer pools to verify
parameters.

No changes should be required, but it is a good idea to
check to make sure there is memory left and that  all disk
drive buffer pools contain at least eight buffers.

4. At the 3OPT Main Menu, type 'S' for Save.

You may now reset the server for normal operation.

.BR;Serial Ports COM2 and COM3 on a 3Server386
.BR;If you connect a LocalTalk network to a 3Server386 via
3+NetConnect, serial ports COM2 and COM3 on the server
cannot be used.  If you need additional serial ports, you can
install a serial adapter board (for example, the AST*  FourPort
XN serial board).  Be sure not to configure the new ports as
COM2 and COM3.

.BR;Serial Ports COM4 and COM5 on a 3Server3
.BR;If you connect a LocalTalk network to a 3Server3 that has a
Port Expansion Board, serial ports COM4 and COM5 on the
server cannot be used.

.BR;Naming a Server with International Characters
.BR;The LCD on the 3Server3 and 3Server386 is not designed to
display international characters.  Consequently, 3Com
recommends that you use only the English alphabet (A
through Z) and/or numbers when naming the server.  If you
do use international characters, the LCD will either not display
the name or will display the name incorrectly.  However, this
will not affect the operation of the server.

.H1;PC Server Installation and Configuration
The following notes discuss installation and configuration
information specific to PC servers.  For general server
information or for information specific to 3Com servers, see
the appropriate notes in this section.

.BR;LocalTalk as a Secondary Network for PC Servers
.BR;The 1.5 release of 3+ supports LocalTalk secondary networks
on 286/386 PC/AT servers using AT buses.  An Apple
LocalTalk PC adapter board (formerly called the AppleTalk PC
adapter board) is required.  The Apple LocalTalk PC board is
supported only in a dedicated server platform, not in a PC
netstation running on LocalTalk.

NOTE:  Only AppleShare PC version 1.2 software can be
used with this adapter board on a 3+ network.  The drivers
necessary to support a LocalTalk adapter in a PC server are
contained on the AppleShare PC disk.  Make sure to use the
version 1.2 documentation that accompanies the software.
This software and documentation can be purchased from your
Apple reseller.  Software and documentation shipped earlier
with the LocalTalk PC adapter board will not work with
3+Share software.

To install the AppleShare PC software, follow these steps:

1. Make a note of the switch and jumper settings
for adapter boards in the PC you will use as a server.

Adjustments may need to be made to the LocalTalk PC
adapter board or other adapter boards in the system to
avoid conflicts.  Refer to the documentation you received
with each adapter board for information on how to adjust
the switches and jumpers.

2. Install 3+Share, 3+Share for Macintosh, and
3+NetConnect on the PC server.

Follow the instructions in the 3+ Installation and Setup
Guide to install 3+Share, 3+Share for Macintosh, and
3+NetConnect.  When configuring 3+NetConnect, select
LocalTalk as the secondary network.

3. From the DOS prompt on the server, copy
C:\AUTOEXEC.BAT to C:\AUTOEXEC.3CM.

To copy the file, type

copy c:\autoexec.bat c:\autoexec.3cm

and press [Return].

The installation program provided with the AppleShare
PC software will modify the AUTOEXEC.BAT file.
You will restore the original AUTOEXEC.BAT file
(now saved as AUTOEXEC.3CM) later in this
procedure.

4. Create a subdirectory called APPLE in the
3PLUS directory on drive C:.

To create the subdirectory, type

md c:\3plus\apple

and press [Return].

This new subdirectory will be used during the
AppleShare PC software installation.

5. Insert the AppleShare PC diskette containing
the installation program into drive A:, make A:
the current drive, and run the INSTALL program.

.BR;After inserting the correct diskette, type
.BR;a:
.BR;install

Follow the instructions displayed on the screen.  No
optional features will be used on the server, so select the
default values when prompted.

6. Indicate where to install the software.

When prompted for a location to install the software, type

c:\3plus\apple

and press [Return].

The AppleShare PC software will be installed in the directory you
created in step 4.

7. When the installation process is complete, you must copy some of
the installed files to the 3plus directory.

To copy the files, type

.BR;copy c:\3plus\apple\lsl.com c:\3plus
.BR;copy c:\3plus\apple\ltalkp.com c:\3plus
.BR;copy c:\3plus\apple\atalk.com c:\3plus
.BR;copy c:\3plus\apple\net.cfg c:\3plus


NOTE:  Future versions of AppleShare PC software
(beyond version 1.2) may contain the file LTALK.COM.
This file should be compatible with 3+Share and can be
used in place of LTALKP.COM, if desired.  However,
LTALK.COM has not been extensively tested.  If any
problems are encountered when using LTALK.COM,
replace it with LTALKP.COM.

8. Delete the directory C:\3PLUS\APPLE and its
contents.

The files needed by 3+Share have been copied to the
C:\3PLUS directory, so the C:\3PLUS\APPLE directory
and its extra files are no longer needed.  To delete the
directory and its contents, carefully type the following.
Typing errors can cause loss of a directory and its files.

.BR;del c:\3plus\apple\*.*
.BR;rd c:\3plus\apple

9. Restore the original AUTOEXEC.BAT file onto
the modified AUTOEXEC.BAT file, which was
modified by the AppleShare PC software
installation, and delete the temporary
AUTOEXEC.3CM file.

To do this, type

.BR;copy c:\autoexec.3cm c:\autoexec.bat
.BR;del c:\autoexec.3cm


10. Modify the C:\3PLUS\NET.CFG file, adjusting
the MemPool parameter to 2K and making any
DMA and PORT changes required by your
server's hardware configuration.

The file C:\3PLUS\NET.CFG, created by the
AppleShare PC software installation program, is a text
file that provides configuration information to the
AppleShare PC software. The default NET.CFG file
should look similar to this:

 LocalTalk only NET.CFG

 NET.CFG Configuration file for the
 Link Support Layer and drivers

 Link Support
 Buffers 8 603
 MemPool 19k

Protocol AppleTalk
 Default LTALK$

Link Driver LTALK$
 DMA  #1   1
 PORT #1 240 8
 Node Address 49

The values in this default file are designed for use with
an AppleShare PC user netstation.  A 3Com 3+Share PC
server requires only 2K for the MemPool.  Use a text
editor (either EDLIN from a DOS system disk, or MED
from the APPS directory on a 3+Share server) to change
the MemPool parameter from 19K to 2K.

Refer to the notes you made in step 1 regarding the
switch and jumper settings in the server PC.  Using the
text editor, change the DMA and PORT settings as
necessary to conform to the system's hardware
configuration.

If you installed LTALKP.COM in step 7, the switch
settings for interrupt do not need to be set because
LTALKP.COM does not use the interrupt.  If you
installed LTALK.COM from a version of AppleShare
PC later than 1.2, however, the interrupt switch settings
do need to be set because LTALK.COM uses the
interrupt.  Refer to Apple documentation for more
information.

EXAMPLE:  The following NET.CFG file is for a
Compaq 386/20 server with an EtherLink II adapter
board set to the factory defaults.  Notice the change in
the MemPool parameter and the DMA address.

  LocalTalk only NET.CFG

  NET.CFG Configuration file for the
  Link Support Layer and drivers

  Link Support
  Buffers 8 603
  MemPool 2k

Protocol AppleTalk
  Default LTALK$

Link Driver LTALK$
  DMA  #1   3
  PORT #1 240 8
  Node Address 49

In this configuration, testing has shown that the
LocalTalk PC adapter card can be configured with
switches 2, 4, 6, and 8 in the ON position.

NOTE:  Increasing the Link Support Buffers above 8
on a fast PC (such as a Compaq 386/20) does not
significantly improve performance.  On a slower PC,
increasing the Link Support Buffers may improve
performance.  Such buffer use is not  included in the
memory usage amounts displayed with 3OPT.  Extra
memory should be reserved.

11. Reset the PC server.

When you reset the PC server, two informational screens
will be presented.  The first screen provides general
information on the NET.CFG file and a warning about
parameter and board conflicts.  The second screen
displays the NET.CFG file with the current settings.
After this screen, you will see messages indicating that
the AppleShare PC software is being loaded and the
AppleShare PC adapter board is being initialized.

NOTE:  If there is a conflict between adapter boards in
the system, the software may stop loading at this point.
If this occurs, recheck the adapter board switch and
jumper settings and modify the C:\3PLUS\NET.CFG
file as necessary to resolve the conflict.  The NET.CFG
file must be modified from DOS.  To exit the startup
screen and return to DOS, press [Ctrl]+C.  Once the
conflicts have been resolved, reset the server.

You can now access your 3+Share server from Macintosh
netstations via LocalTalk cable.

.BR;New ETH523.SYS Driver Parameter
.BR;An optional parameter for EtherLink/MC adapters in PC
servers has been added for the ETH523.SYS and
2ETH523.SYS drivers.  To use the parameter, modify the
appropriate DEVICE= line of the CONFIG.SYS file as
follows:

.BR;device=eth23.sys /slot:3
.BR;device=2eth523.sys /slot:4

where 3 is the number of the Micro Channel slot where the
EtherLink/MC adapter board is installed.  Valid slots values
are 1 through 8.

If there is more than one EtherLink/MC adapter board in a
system, this parameter allows you to specify which adapter
board will be used by ETH523.SYS as the primary adapter,
and which will be used by 2ETH523.SYS as the secondary
adapter.

When no slot is specified, the  drivers will search all available
microchannel slots, beginning with slot 1, and will use the
first EtherLink/MC adapter board found as the primary adapter
and the second as the secondary adapter.

If an invalid slot or a slot that does not contain an enabled
EtherLink/MC adapter board is specified, the parameter is
ignored and the available microchannel slots are searched just
as if no parameter had been specified.

This new parameter is useful when:

 - The primary adapter in a 3+NetConnect server is in a
   higher numbered slot than the secondary adapter.

 - The secondary adapter in a 3+NetConnect server is an
   EtherLink/MC adapter board but the primary adapter is a
   different type of adapter board.  In this case, if you did
   not specify slots for the primary and secondary adapters,
   the EtherLink/MC adapter board would be used as the
   primary adapter and the software would assume that
   there was no secondary adapter.

 - You want to specify which adapter board is referenced
   by the ETH523.SYS or 2ETH523.SYS driver.

.BR;TokenLink Plus Adapter in all PC Servers
.BR;For best performance and reliability, 3Com recommends the
TokenLink Plus adapter, rather than the standard TokenLink
card, for all PC servers on a token ring network.

.BR;EtherLink Adapter in a PC Server
.BR;For best performance and reliability, the EtherLink II or
EtherLink Plus adapter, rather than the standard EtherLink
board, is recommended for all PC servers on an Ethernet
network.  This recommendation is particularly important if
you have Macintosh computers on the Ethernet network that
will be accessing the server frequently.

.BR;3ComEMM Memory Management Program
.BR;Install, p. 13-6
.BR;The following items discuss the 3Com EMM Memory
Management Program:

The LIM 4.0 driver that you received with this release of
3+ is the only LIM  driver that is fully supported.  This
driver is supported only on PC 386-based computers
adapted as network servers.

The effectiveness of the 3ComEMM memory
management program on a PC 386-based server may be
jeopardized by certain types of video cards in the server.
Some video cards require more memory than others; the
more memory required by the card, the less memory
available for 3ComEMM to allocate to 3+ services.  To
optimize the services loaded into high memory on these
systems, 3Com recommends that you use a
monochrome card and monitor with a PC 386 server.

If you intend to use a PS/2 Model 80 computer with an
IBM Fixed Disk Adapter as a server, ask your 3Com
reseller for the special version of the 3ComEMM
program.  The standard version of 3ComEMM is not
supported on a FDC-based PS/2.  If you are uncertain as
to the type of disk adapter in the unit, use the Reference
Disk included with the computer to view the system
configuration.

.BR;3ComEMM Program on a Honeywell 386 Computer
.BR;The 3ComEMM memory management program is not
supported on a Honeywell 386-based computer with a token
ring adapter.

.BR;STATUS.LOG File on a PC Server
.BR;The following error messages are inserted in a PC server's
STATUS.LOG file every time you turn on or reset the unit:

.BR;Could not init power fail driver
.BR;Power fail initialization failed

These messages are associated with a 3+ feature that is
supported on the 3Server386 only.  They do not indicate a
problem with the PC server and no action is required.

.BR;Communications with a PC Server
.BR;If netstations are unable to communicate with a new PC server
even though the server started up properly, check to see that
the settings on the network adapter in the server match the
settings in its CONFIG.SYS file.  For instructions on the
network adapter settings, refer to the adapter guide.  For
instructions on the CONFIG.SYS file, refer to the 3+Administrator
Guide.

.BR;Loading Extra Services on a 386 PC Server
.BR;By properly configuring a 386 PC server, space can be made
to load one additional service.  For example, 3+Name,
3+Share, 3+Mail, and Macintosh services can be loaded
simultaneously.  This is true only for 386 PC servers, and will
not work for 286 based PC servers.  This does not apply to
dedicated 3Com servers such as the 3S/400.

To configure a 386 PC server for maximum capacity, you
need:

 - Either a monochrome (non-graphics) video adapter
   requiring 4K memory or a CGA adapter requiring 16K
   memory.

 - A minimum of one megabyte of memory available.

Along with these requirements, you must answer yes when
prompted about 3ComEMM support during the installation
procedure .

.BR;CIOSYS Buffer Pool Allocation on PC Servers
.BR;If your PC server has disk partitions with different cluster
sizes, the buffer values need to be updated following
reinstallation.  Follow these steps to update buffer values:

1. Start the 3OPT program with the server in the
off-line mode.

 See the 3+ Network Tuning Guide for instructions.

2. From the 3OPT Main Menu screen, select the
CIOSYS option by highlighting it with the
selection bar and typing 'C'.

3. Select the CIOSYS buffers option.

4. Check  the parameters for each disk drive
buffer pool.

Each disk drive buffer pool must have no less than 8
buffers per pool.  Sixteen is preferable if the server has
sufficient  memory.  Change the values for any buffer
pool that does not meet this requirement.

5. Press [Ctrl]+A twice to save the changed
values.

6. At the 3OPT Main Menu, type 'S' to save the
configuration.

7.  Type 'Q' to quit the 3OPT program.

    You may now reboot the server.

.H1;3+NetDOS
NOTE:  The 3+NetDOS program comes standard with the
3Server3 and 3Server386 and is available as an option for PC
servers.

.BR;Checking Out an MS-DOS License
.BR;NetDOS, pp. 2-3, 2-6
.BR;The reference to the MS-DOS Supplemental Diskette in the
3+NetDOS Installation Guide should read 3+NetDOS
Supplemental Diskette.

.BR;Inserting a Blank, Formatted
.BR;Diskette
.BR;NetDOS, p. 2.6
.BR;When you insert the newly formatted diskette into the drive,
check to be sure that the diskette is not write-protected and that
it is properly inserted in the drive.  If 3+NetDOS encounters a
problem with the diskette, you may have to repeat the procedure.

.BR;Storing all System Files on One 3-1/2-Inch Disk
.BR;NetDOS, p. 2-7
.BR;When you check out a 3-1/2-inch system disk with
3+NetDOS, all of the system files can be placed on one disk
rather than two.  To do so, press [Return] without changing
disk when 3+NetDOS prompts you for the second diskette.

.BR;Creating Long Directory Paths
.BR;Do not create paths over 63 characters in length.  Paths longer
than this can cause problems for some MS-DOS utilities, such
as XCOPY.

.BR;Mixing Different Versions of MS-DOS
.BR;Do not mix different versions of MS-DOS.  For example,
using MS-DOS 3.2 utilities on a netstation booted with MS-
DOS 3.3 will result in the error message:

Incorrect DOS version

.BR;Recovering from an Error
.BR;If 3+NetDOS experiences an error when you check out a
license (e.g., a faulty disk drive), select the abort option and
repeat the procedure.  If the number of available licenses is
reduced by 1 even though you aborted the operation, edit the
NETDOS.USR file in the 3+NetDOS directory with a word
processor or text editor and increase the"Available Licenses"
line by 1.

.H1;3+Backup
.BR;Restoring Partition C: of a Server
.BR;When restoring files to partition C: of an installed 3+Share
server without reformatting the partition first, 3Com
recommends that you restore individual directories rather than
the entire partition.  Otherwise, 3+ network server files could
be overwritten with earlier versions and cause problems for
users.

.BR;Backup Disk Space Considerations
.BR;When backing up 3+ 1.5 software, be sure to have at least 1/2
MB of disk space free in partition C: on the server beyond
what is needed for tape logs.  The 1.5 restore process creates
temporary files in the C:\3PLUS\3BACKUP directory that
require this disk space.

Tape logs can require five MB or more of disk space if you
have large amounts to backup.  Be sure you have enough
room in partition C: to accommodate such large files.

.BR;Off-line Backup Caution
.BR;When performing an off-line backup, if a message is displayed
indicating that a directory is corrupted or has bad attributes,
ignore the warning and continue the backup.  In an earlier
release, the archive attribute was set by CIOSYS for
directories when modification dates were changed by 3+ for
Macintosh.  This was fixed in 3+ version 1.3.1.  However,
directories created prior to 1.3.1 may cause off-line backup to
display a warning.

You can avoid these messages by following these steps:

1. Create a new folder next to the problem folder.

2. Open the problem folder and select all of the
contents.

3. Drag the contents into the new folder.

4. Put the name of the problem folder on the
clipboard.

5. Confirm that the problem folder is empty and
delete it.

6. Paste the name in the clipboard over the new
folder name.

You cannot perform these steps using a PC.  Complete
Macintosh files cannot be copied using the DOS Copy
command.

.BR;Backing Up and Restoring the
.BR;\3PLUS\3BACKUP Directory
.BR;Off-line backup and restore ignores the \3PLUS\3BACKUP
directory on a server.  This directory includes the file
AUTOTIMS, which contains the automatic backup schedule
for 3+Backup on the server.  To ensure that the directory is
properly backed up and restored in off-line mode, create a new
directory and copy the contents of \3PLUS\3BACKUP to the
new directory before doing a backup.  Be sure to allow
enough disk space in partition C: for log and temporary files.

.BR;Backup and Restore Log
.BR;Backup and restore now produce an enhanced log that includes
Macintosh file and folder names with corresponding DOS file
directory names for every directory that contains Macintosh
information.  The Macintosh names are in the logs with
Macintosh ASCII character codes.

If you are using a PC-based system to view a log, some
characters in the Macintosh name column may not be
represented because of differences in the IBM and the
Macintosh Extended ASCII character sets.  If it is important to
find a file with a name containing characters unique to the
Macintosh character set, view the log from a Macintosh text
editor.

.H1;3+ for Macintosh Users
This section contains notes that discuss 3+ for Macintosh
configuration, remote access, and printing.

.BR;Printing from PageMaker 3.0
.BR;PageMaker 3.0 will not download the Aldus Prep file if it
senses that it is printing to a network spooler.  To print in
PageMaker 3.0, the user must do one of the following:

1.   Use only the Apple driver when printing.

2.   Use the Aldus driver, but turn on the check
box to download the Aldus Prep file
temporarily.

To access this option, hold down the [Option] key while
clicking the OK button in the print dialog box.


NOTE:  This has been recommended for previous
versions of PageMaker, but is now mandatory for
printing in PageMaker 3.0.

.BR;Minimal Startup Disk Configurations
.BR;Macintosh programs that are init resources must be installed on
your startup disk; they cannot be run from the Home Folder
after switch launching.

To free space on your Macintosh startup disk, you can remove
the following files from your startup disk and copy them into
the System Folder in your network Home Folder.

.BR;MultiFinder
.BR;Mouse
.BR;Keyboard
.BR;DA Handler
.BR;3+ Icon Giver

The recommended minimum files for a Macintosh startup disk
are:

.BR;System (containing only those system fonts that cannot be
.BR;deleted using Font/DA Mover)
.BR;Chooser
.BR;Control Panel
.BR;Finder
.BR;3+File
.BR;3+Print
.BR;3+Prep (this will be created when you save your startup configuration)
.BR;General
.BR;EtherTalk or EtherLink/SE, and Network
.BR; (only if you are using Ethernet)
.BR;Other Init resources as space allows
.BR; (such as SoundMaster or Suitcase)
.BR;NetSwitch or NetSwitch MF

.BR;Accessing the Network via a Modem Connection
.BR;A LocalTalk connection is capable of transmitting data 120
times faster than a 2400 baud modem connection.  This
difference in speed creates limitations in the performance of
any network connection over a modem.  Using a 9600 baud or
faster modem will result in a noticeable difference in
performance.  3Com recommends you use at least a 2400
baud modem.

You should not open an application residing on a network
server across a modem connection.  Access over a modem
connection is better suited to small file transfers or the sending
or receiving of mail using 3+Mail.  In most instances, copying
a document from a remote network server to a local disk,
modifying it and then copying it back to the remote server is
faster than attempting to modify it directly across a modem
connection.

If you are using third party dial-in software that makes the
modem connection via the Control Panel, you should make the
connection before you attempt to log into 3+.  You must not
have booted with the EtherLink AppleTalk device chosen
before chosing a Dial-up AppleTalk device in the Control
Panel's network control panel.

If you are linking to 3+ volumes across a modem connection,
do not use MultiFinder.  MultiFinder polls all mounted
volumes on frequently, resulting in poor performance.
Finder, on the other hand, polls volumes less often.   Since the
communications link is unreliable, you may see a message box
saying that "the file server is not responding. RetryingI"
You should check to see if your modem connection is up.  If it
is, you should wait a few minutes to see if the client software
can reestablish the session with the server.

When running 3+NetAccess or 3+Mail you may occasionally
see messages stating that the Name server or the Mail server is
not responding.  In this situation, you should check to see if
your modem link is up and retry the operation.

Unlink volumes before you hang up the modem or power off
the Macintosh.  You can unlink volumes by logging off or by
dragging the volume icons into the trash.  If you fail to do so,
you may be unable to link to your folders the next time you
attempt to do so.

If you are using an AppleTalk bridging or routing product,
you must upgrade all 3+ servers that will be used to
communicate with 3+ 1.5.  If you need to communicate
through a 3+NetConnect node that is running 3+ version
1.3.1, you should replace the IDP.SYS file on that node with
the IDP.SYS file from the 3+ 1.5 3+Installation #3 diskette.

.H1;3+ for PC Users
This section contains notes that discuss installation,
configuration, console connections, 3+Menus, and NetBIOS
for PC users.

.BR;Creating the First PC Netstation
.BR;Startup Disk
.BR;Install, p.10-4
.BR;The procedure for creating a netstation startup diskette is
incorrect if you installed a PC server.  The procedure instructs
you to use the Quick Installation Workstation diskette for a
new network.  However, this diskette is not included in the
PC server version of 3+Share 1.5 (3C2000H).
Consequently, to make your first  PC netstation startup disk
on a PC server, use the following procedure.

1. After you install the 3+ software on the PC
server the server menu will appear:

 1. Start up as a dedicated server.
 2. Start as a workstation
 3. Run the 3INS program
 4. Run the 3OPT program
 5. Exit to DOS

This is the server menu for a dedicated PC server.  If
you designated the PC as a concurrent server, the menu
will include an additional option for running the server in
the concurrent mode.

2. Select option 5, Exit to DOS.

3. Change to drive C:.

4. Change to the \APPS subdirectory with the
DOS CD command:

To change directories, type

   cd \apps

5. Perform the MAKEDISK procedure.

Refer to the 3+ Installation and Setup Guide for
information on the MAKEDISK procedure.  You may
run the MAKEDISK program as many times as
necessary to create your  startup disks.

6. Reset the server and wait for the server menu
to appear.

7. Select the option to start the PC as a network
server.

Future PC startup disks can be created by following the
procedure in Chapter 10 of the 3+ Installation and Setup
Guide.

.BR;The Canadian/French Keyboard
.BR;A PC netstation with a Canadian/French keyboard must use
the French software driver.  The Canadian/French software
driver is not supported by 3+.

.BR;Compaq Portable or Deskpro Computers
.BR;For proper operation, a Compaq 8088-based Portable or
8086-based Deskpro requires ROM Revision J.  To find out
what Compaq ROM you have:

1. Start your Compaq using the Compaq
diagnostics diskette.

2. Type

   test

   and press [Return].

3. Choose option 5, ROMREV.

The version of your ROM is displayed.  ROM upgrades
are available from your Compaq dealer.

.BR;Number of DOS Volumes
.BR;3Server386, pp. 5-30, 5-41 to 5-49
.BR;If you have five or more 150 MB disk drives attached to the
3Server386 and each contains the default format of 512 bytes
per sector and 4 sectors per cluster, the system will have more
than the maximum allowable number of DOS volumes.  Up to
24 volumes are allowed (one each for drives C: through Z:).
When you display the configuration through the 3DISK386
"Show DOS volumes" option, any volumes after the 24th
(drive Z:) are listed as question marks (?).

When five or more disk drives are attached to the 3Server386,
or the number of DOS volumes exceeds 24, format one or
more disk drives to have fewer, larger volumes than the
defaults create.

Attempting to reset the 3Server386 when more than 24
volumes are defined halts the server and one of the following
messages appears on the LCD:

Disk <SCSI ID/logical unit number> error
code: 0302 <volume> 00

Disk <SCSI ID/logical unit number> error
code: 0303 <volume> 00

Disk <SCSI ID/logical unit number> error
code: 0304 <volume> 00

.BR;New SENDMSG Command
.BR;This command sends messages from user to user.

Format
SENDMSG

Parameters
None

Remarks
The SENDMSG command allows you to send messages to
other users on the network.  When you send a message with
SENDMSG, the message is instantly displayed on the
recipient's screen, regardless of the application program the
recipient is running.

When you enter the SENDMSG command at any DOS
prompt, the message form is displayed.

NOTE:  If your form contains two destination fields,
Broadcast Destination and Directed Destination, you are a user
with network administrator capability.  An administrator's
message form is slightly different than a user's form.  Refer to
the 3+Share Administrator's Guide for instructions.

The fields for this command are:

Default Domain:  Contains the name of your default
domain.  This field cannot be changed.  If you intend to send a
message to someone who is not a part of your default domain,
you need to enter the correct domain in the destination field.

Default Organization:  Contains the name of your default
organization.  This field cannot be changed.  As with the
default domain, you need to enter the correct organization in
the destination field if you intend to send the message to
someone who is not a part of your default organization.

Priority Level:  Sets the priority level of the message.  The
value can be from 0 to 9 with 0 the highest priority.  Priority
levels 0 through 2 are typically reserved for use by the
Network Administrator.  Only network administrators can
assign a priority level of 0 to a message.

Users can use the priority level to ignore or screen out
messages from other users and the network administrator.  For
example, a user can configure the netstation to ignore
messages with priority levels of 3 to 9 and display only those
with a priority of 0 through 2.  This prevents the user from
being interrupted by unnecessary messages.

Message Destination:  You enter in this field the
destination of your message.  The destination is the name of a
user, group, or domain.  For example, to send a message to
user John Smith you enter:

John Smith

If the user is not a member of your default domain or
organization, the correct domain and organization must be
entered along with the name.  (Your default domain and
organization are displayed at the top of the form.)  For
example, to send a message to user John Smith in the Sales
domain, enter:

John Smith:Sales

To send a message to all the users of a domain, enter the name
of the domain preceded by an asterisk (*).  For example,
entering the following command in the Directed Destination
field sends your message to all users in the Sales domain.

*:Sales

You can also send your message to all the members of a
group, such as a mail group.  This entry in the Message
Destination field distributes your message to everyone in the
docstaff group in the Sales domain.

docstaff:sales

Message Field:  This is the field where you enter your
message.  A message can be up to two lines, with 74
characters per line.  Special characters (for example, %, +, =)
are allowed.

.BR;Receiving a Message
.BR;When you receive a message from another user, it looks like
this on your screen:

You clear the message from the screen by typing C for clear.
The message disappears and you can resume work.  You
cannot continue with your work until the message is cleared
from the screen.

You can also clear the message but keep it in the computer's
memory, possibly to recall it later, with the [Esc] key.  When
you press [Esc], the message disappears but remains in
memory.  To recall the message, you press the hot key, which
is a combination of three keys.  The default hot key
combination is [Alt]+[Left Shift]+[R].

You can adjust two features of the message program when a
message is on the screen.  The first is the netstation beep.  If
you do not want your netstation to beep every time a message
arrives, type the letter B.  This toggles the netstation beep on
and off.  If you turn it off, the netstation will not beep until
you either turn off or reset your netstation, at which time the
beep is turned on again.  If you want to permanently turn off
the beep, refer to the 3+ Administrator's Guide.

The second feature is referred to as the AUTO feature.  When
AUTO is turned on, a message from another user
automatically appears on your screen.  This is the default.  If
you turn the feature off by typing the letter A, a received
message remains hidden until you display it with the hot key.
As with the netstation beep, this continues until you turn off or
reset your netstation, at which time the AUTO feature is turned
on again.  3Com recommends that you do not turn off both the
netstation beep and the AUTO feature; otherwise you will have
no way of knowing when you have received a message.

Changes to the message program are made with the
RECVMSG command.  For details on the RECVMSG
command, see your network administrator.

.BR;Using a Compaq 386/20 for a Console Connection to a 3Com 3S/200
Server
.BR;When using a Compaq 386/20 (or a similar fast PC) as a
console connection to a 3Com 3S/200 server, you may
occasionally lose the connection.  If this occurs, use a slower
PC to establish the console connection.  If another PC is not
available, edit the server's CONFIG.SYS file on the System
Software diskette #1, changing the PRO.SYS line as follows:

For Ethernet networks:

device = c:\3drivers\pro.sys 20 4 4

For Token Ring networks:

device = c:\3drivers\pro.sys 14 2 8

.BR;3C with TokenLink
.BR;TokenLink, p. 4-5
.BR;When you use a 3C connection from a netstation with a
TokenLink adapter board installed in a 16-bit expansion slot,
you must edit the CONFIG.SYS file on the netstation startup
disk.  Change the default DMA channel setting of 1 to 3 to
make the 3C connection work properly.  If you copy files
from the disk to the server using a netstation containing a
TokenLink board that is using DMA channel 1, the copied
files will be incomplete or damaged.  (The files on the diskette
will be unharmed.)

NOTE: If the TokenLink board is installed in an 8-bit
expansion slot, no special action is necessary.

Use a text editor to change the following statement in the
CONFIG.SYS file of the netstation startup diskette:

device=tok603.sys ,, 3

This statement keeps the TokenLink board's default values
intact for the interrupt level (3) and I/O base address (300), but
changes the DMA channel setting to 3.  See the TokenLink
Installation Guide for more information on setting 3+ software
for this board.

CAUTION: Before resetting the netstation with the updated
CONFIG.SYS file, make sure no other expansion board
installed in the netstation uses DMA channel 3.  If there is
such a board installed, either use a netstation that has no
conflicting expansion board (and change the first netstation's
CONFIG.SYS file back to its previous state);  or remove the
conflicting board when using the CONFIG.SYS file that
specifies DMA channel 3 for the TokenLink board.

.BR;Listing Users Linked to a Printer
.BR;Admin, p. 4-4
.BR;The List Users Linked to a Printer menu selection produces an
error message:

***Unknown value: \LASERJET /LINK

and does not produce the desired list.  To see the list, modify
the form by typing the printer name after the server name on
the same line, and deleting the second line.  This is not a
permanent solution.

If you use this selection frequently, change the task item form
following instructions in Chapter 5 of the 3+Menus Reference
Guide.  Put the server and printer names on the same line.

.BR;Restoring from 3+Menus
.BR;If a directory or partition contains 3+Menus, do not attempt to
restore the directory or partition while someone is accessing
3+Menus.  Data is not endangered, but the process will hang.

.BR;NetBIOS Name Conflict Detected
.BR;To minimize phone charges when using 3+ Remote PC,
NetBIOS defers phone dialing until the latest possible time.
Unless a NetBIOS application requires a specific netstation
name, leave the SETNAME parameters in the
AUTOEXEC.BAT file as $$3COM$$.  Otherwise, when the
deferred phone connection is finally attempted, NetBIOS may
display a Name conflict detected message.

SETNAME normally requires access to the Locator when the
netstation boots.  3Com uses a proprietary form of the ADD
NAME command that does not access the Locator (and thereby
check for the uniqueness of the netstation's name) until some
other access is required.  This ensures that 3+Remote users do
not incur phone charges by just starting up their machines.
The message Name conflict detected may be
displayed if the name specified by SETNAME is not unique.
To avoid this problem, make sure your local or remote
netstation has a unique name by always using the default
$$3COM$$ name (which uses the network adapter address as
the station name).

.BR;NetBIOS /C Switch
.BR;Unless you are running only 3+ services, use the /C  switch
on the NetBIOS line of the AUTOEXEC.BAT file.  NetBIOS
assumes that timeout errors on SEND and RECEIVE, as well
as Locator operations that do not complete, are the result of
physical network problems.

To avoid terminating sessions because of such problems,
NetBIOS displays one of the following message:

Network Retrying ...

Locator Not Responding

You can wait for the network problem to go away or you can
return the timeout error to the application immediately by
pressing [Ctrl]+[Break].

When a NetBIOS application relies on getting these timeout
errors as a normal part of its operation, using the NetBIOS /C
switch returns the timeout error to the application immediately
without displaying a message.

.BR;NetBIOS /M Switch
.BR;The IBM Asynchronous Communications Server and the IBM
PC LAN programs require the NetBIOS /M switch.  Other
applications may require the use of the NetBIOS /M to run
properly in the 3+ environment.

.BR;3+Route on Token Ring
.BR;When running 3+Route on a token ring network, you may
occasionally experience loss of modem connections.  This
typically occurs on COM2 or COM3 while operating under
heavy loads and at rates of 9600 baud or higher.  If this
occurs, move the high speed modem to COM1 or to an
asynchronous I/O port on an expansion board.

.BR;Token Ring "B" Drivers for a 3+Open Network
.BR;There are a new series of "B" drivers for all token ring
products running on 3Com software.  Their purpose is to
eliminate addressing incompatibilities for 3+Open and mixed
3+ and 3+Open systems.  They are:

 - TOK603B.SYS    - for the 3C603 board (IR4)
 - TOK1060B.SYS   - for the RIB/CRIB board on 3Servers
 - TOK605B.SYS    - for the 3C605 board (IR3)
 - TOKIBMB.SYS    - for the IBM series of Token Ring
                    boards

Space on the 5-1/4-inch diskettes is at a premium, and some of
these drivers could not fit on all assigned diskettes and have
been placed on other diskettes.  Consult the list below for the
location of additional drivers on other diskettes..This is not a
problem on 3-1/2-inch disks.

 - TOK603B.SYS  3+Installation #2, 3+System Software
   for 3S400 #2
 - TOK1060B.SYS 3+Installation #2, 3+System Software
   for 3S200 #2
 - TOK605B.SYS 3+Installation #2
 - TOKIBMB.SYS 3+Installation #2

NOTE:  When operating in a mixed 3+ and 3+Open network
on token ring cable, all 3+ TOK drivers must be the "B"
version.  Edit the CONFIG.SYS files on the affected PCs to
show this change and copy the appropriate "B" driver into the
directory indicated in the CONFIG.SYSD file.

* Hayes is a registered trademark of Hayes Microcomputer Products,
Incorporated.
* Microcom is a trademark of Microcom Corporation.
* PageMaker is a registered trademark of Aldus Corporation.
* AST is a trademark of AST Research Incorporated.
