Ref: 08740004
Title: 3S/400 Administrator's Release Notes
Date:  07/15/88

Copyright 3Com Corporation, 1991.  All rights reserved.

.br;3S/400 Administrator's Release Notes   1
.br;3+ Version 1.3
.br;Part Number  3369-00
.br;12/18/87

This document provides information related to the system 3S/400
including hardware, system-level software, and 3+ version 1.3 network
software.  Read this information carefully (particularly if you have a
token ring network) before using your 3S/400.


This set of release notes is divided into ten sections:

_ Installation and Configuration
_ Administration
_ Remote Console
_ Disk Configuration
_ 3+Backup
_ 3+File and 3+Print
_ 3+Mail
_ 3+Menus
_ NetBios
_ NetDOS
_ 3+Route and 3+Remote

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

3Server 3Server386 Guide
Admin 3+ Administrator_s Guide
Mail 3+Mail User Guide
Menus 3+Menus Reference Guide
MMinder 3+MailMinder
NBSup NetBIOS Supplement
Remote 3+Remote User Guide
TokenLink TokenLink Installation Guide
Tuning 3+ Network Tuning Guide
User 3+Share User Guide

Installation and Configuration

3+Share Receive Buffers
Tuning, p. 8-13
 The value of the 3+Share Receive Buffers parameter as shipped is 20,
 not 23.


Changing the Baud Rate on a Microcom Modem

To adjust the baud rate on a Microcom modem, change the rear switches
and reset the modem.  If the modem 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 repeat the
earlier step of adjusting the rear switches and resetting the modem.

Fatal Process Error

If you are using EtherTerm and get the message :

Fatal process error

change the number of processes on the device=pro.sys line of the
netstation_s CONFIG.SYS file to at least 10.


Installing Internal Modems on a Token Ring Network

When 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.  (This is the default interrupt setting for 3Com's
Ethernet and Token Ring adapters, but this does not conflict with the
Ethernet on the server's motherboard.)

Once set, this modem appears as a COM4 option in your 3+Route,
3+Remote, or 3+Print checker, similar to an IBM AT card.
Installing on a Token Ring Network On a token ring network, when
rebooting the server from a netstation, the server may halt while the
message:

SYNC ILOOP TEST

displays on the LCD.  To continue, press the reset button on the
server and it will boot normally.  A netstation can initiate a server
reboot in two cases: 1) at the end of the Quick Install process, and
2) after running SETUP using a 3C connection.


I/O Request Blocks
Tuning, p. 7-14
The value of the CIOSYS I/O Request Blocks parameter as shipped is
64, not 32.


Login Library Parameter
.br;Tuning, p. 14-2

The login library manager (LGL.SYS) -mx parameter lets you set the
maximum number of entries for the login library.  The allowable range
is from 4 to 64 entries.  The default is 8 entries for a netstation
and 32 entries for a server.  Each entry requires 88 bytes.

The following example sets the -mx parameter to 12:

 device=lgl.sys -m12

Each time you issue a 3F LINK, 3F DIR, 3P LINK, 3P DIR, or 3N ASSIGN
command, an entry is made in the login library.  If the number of
entries exceeds the maximum set by the -mx command, the manager
displays the message:

 Internal error

Duplicate entries are not counted, and you can clear all entries in
the current login library by starting the netstation again.

When you reset the number of entries, you must also change the
NetBIOS /s parameter (see the NetBios Supplement, Chapter 3 for
details).  You also need to change the MSREDIR /s and MSREDIR /l
parameters (see the 3+ Network Tuning Guide p. 17-3 and 1
7-4 for details).


Supported 3+NetConnect Configurations

The following combinations of adapters for primary and secondary
networks are the only configurations supported with 3+NetConnect on
the 3S/400.

   Primary Secondary Comments
   Ethernet on EtherLink
   Motherboard EtherLink II
   TokenLink
   TokenLink Plus Must use DMA = 5
   TokenLink Ethernet on Motherboard
   TokenLink
   TokenLink Plus Must use DMA = 5


3+ for Macintosh

3+ for Macintosh is not supported in 3+ version 1.3 and therefore
should not be installed on a 3S/400.



Token Ring Adapters

The TokenLink adapter is supported on the 3S/400, but the TokenLink
Plus is not, except as a secondary network adapter for 3+NetConnect.


Administration Release Notes

Compaq Portable or Deskpro Computers

For proper operation, a Compaq Portable or Deskpro requires ROM
Revision J.  To find out what Compaq ROMs you have:

.br;1. Start your Compaq using the Compaq diagnostics
diskette.
.br;2. Type test and press [Return].
.br;3. Choose option 5, ROMREV.

The version of your ROMs is displayed.

(ROM upgrades are available only from your Compaq dealer.)


Internal Error
.br;User, p. A-15
.br;The message:

Internal error

means you have exceeded the maximum number of entries established for
the Login Library Manager.  Each time you give a 3F LINK, 3F DIR, 3P
LINK, 3P DIR, or 3N ASSIGN command, an entry is made in the Login
Library (the default is eight and duplicate entries are not counted).

Tuning, p. 14-2
.br;If a user regularly needs more than eight entries, adjust the number
of entries allowed by changing the -m  parameter.  For information
about the -m parameter, see Login Library Parameter in these release
notes.  (To remove all current Login Library entries, reboot the
netstation.)


LGL Not Loaded
.br;Can't Access 3Com Process Manager
.br;User, p. A-16
 If the error messages:

 LGL Not Loaded
  or
 Can't Access 3Com Process Manager

appear after formatting a diskette, list the diskette's directory
using the DOS DIR command.  You should then be able to continue.


Saving LASTBOOT Information
.br;3Server, p. 5-13
 Each time you run LASTBOOT, current information is displayed on the
 screen and is not saved.  To save LASTBOOT information, redirect the
 output to a file.  This is the recommended way to use LASTBOOT, since
 once it is run, the information it provides is no longer available.

 LASTBOOT >filename



Too Many Redirections
.br;User, p. A-31
 The message:

 Too many redirections

 indicates that you have used more links than you are allowed for your
 netstation.  Increase the number of NetBIOS and MSREDIR sessions for
 your netstation.


Remote Console

3C Connection
.br;3Server386, p. 5-2
 If you see the message:

 CON:INIT ERROR

on the LCD after entering the 3C START command, reboot your
netstation and the 3Server386, then reenter the command.  This
message appears when the 3+ login command is run before the 3C START
command.


3C with TokenLink
.br;TokenLink, p. 4-5
.br;When you use 3C from a netstation with a TokenLink adapter board
installed in a 16-bit expansion slot, you must edit the CONFIG.SYS
file of the netstation startup diskette.  Change the default DMA
channel setting of 1 to 3 to make the 3C connection work properly.
If you copy files from diskette 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 restarting 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.



3S/400 Administrator's Release Notes   1
.br;3+ Version 1.3
.br;Part Number  3369-00
.br;12/18/87

Disk Configuration

.br;3DISK386 Soft Format
.br;3Server, p. 5-47
.br;Do not enter non-numeric characters in response to the prompts
displayed during the "Write new DOS volumes (soft format)" operation.
Doing so halts 3DISK386.  Either accept the default value by pressing
[Return], or enter one of the numbers displayed in the prompt.


.br;Number of DOS Volumes
.br;3Server, p. 5-26 and 5-41 through 5-44
.br;If you have five or more 150MB 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.  (See 3Server,
p. 42 for details.)

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

.br;Disk <SCSI ID/logical unit number> error
.br;code: 0302 <volume> 00 OR
.br;code: 0303 <volume> 00 OR
.br;code: 0304 <volume> 00

.br;CIOSYS Configuration
.br;3Server, p. 2-28, 5-28
.br;Tuning, p. 7-3
.br;After adding a disk drive to the 3S/400 and updating the system
software configuration through 3DISK386, you must update the CIOSYS
configuration using the 3OPT program.  Since a correct CIOSYS
configuration is essential for good network performance, the
procedure for updating CIOSYS is repeated here.


.br;1. Create a 3C console connection, if you have not
already.

See "3C:  The Network Console Program" in
Chapter 5 of the 3Server386 Guide for instructions
on using 3C.

2. From drive C: run the 3+ tuning program, 3OPT,
to change the CIOSYS configuration to include the
new disk drive.

From the server's DOS prompt type:

C>>3OPT [Return]

When the 3OPT main menu appears, use the arrow
keys to highlight the CIOSYS menu item.  Then
select "Change" from the options at the top of the
screen.

3. From the CIOSYS Configuration menu, choose
"Select Network Drives."

.br;Select a Function
.br;1. Select network drives
.br;2. Adjust CIOSYS parameters
.br;3. Adjust CIOSYS buffer pools

The CIOSYS Configuration screen is displayed
showing the drive you just added as a "local"
drive.  This means that 3+ does not recognize the
drive as being part of the network.


CIOSYS Configuration Ver. 1.3

       NET/  PHYS        NET/  PHYS  EMS to be used by
 DRIVE LOCAL DRIVE DRIVE LOCAL DRIVE CIOSYS 1024

 C     N     1                       EMS available
 D     N     1                       (in K)  1024
 E     N     1
 F     N     1
 G     N     1
 H     L     **
 I     L     **
 J     L     **
 K     L     **
 L     L     **

 To make the new drive a network drive, type an N over each L in the
NET/LOCAL column.  Then type a plus sign (+) over the values in the
PHYS DRIVE column to assign the next highest physical drive number to
the new disk drive.  This is important for
getting the best performance from your 3S/400.  If you leave PHYS
DRIVE at the default value of 1 for the second through sixth disk
drives, network performance will suffer significantly.


 The CIOSYS Configuration screen should now look something like this:

 CIOSYS Configuration Ver. 1.3

       NET/  PHYS        NET/  PHYS  EMS to be used by
 DRIVE LOCAL DRIVE DRIVE LOCAL DRIVE CIOSYS 1024

 C     N     1                       EMS available
 D     N     1                       (in K)  1024
 E     N     1
 F     N     1
 G     N     1
 H     N     2
 I     N     2
 J     N     2
 K     N     2
 L     N     2


 NOTE:  The physical drive number and the SCSI ID number are
unrelated.  Make sure the value under PHYS DRIVE reflects the number
of the last physical disk drive you attached to the 3Server386.


4. Save the new CIOSYS configuration.

Press [Ctrl]+[A] to accept the values on the
CIOSYS Configuration screen.  When the initial
CIOSYS menu appears, press [Ctrl]+[A] again to
confirm that you want to save the new CIOSYS
configuration.  At the 3OPT main menu, select
"Save" and then "Quit" to exit 3OPT.

For more information on the 3OPT program, see the 3+ Network Tuning
Guide.



3+Backup

File Names Beginning with LCD
.br;You cannot back up or restore filenames beginning with "LCD" using
off-line backup.  LCD is a reserved DOS device driver.


Tape Cartridge Capacity and Tape Drive Capacity Setting
Admin, p. 6-57, 3+Messages, p. T-5
 An error message:

 ***Tape drive error; software error

 appears if the tape cartridge capacity does not match the tape drive
capacity.  For example, if you use a 120 megabyte tape cartridge and
the tape drive is set for 150 megabytes, the error message appears.

 To correct this, make sure that your tape cartridge and tape drive
capacities are equal.  Use a tape cartridge with the correct capacity,
or change the tape drive capacity in the CONFIG.SYS file (default is
150 megabytes).

 If this does not correct the situation, there may be a hardware
problem.  Contact your 3Com reseller.


3+ File and Print

3P QSTAT Command
.br;User, p. 9-17
.br;The 3P QSTAT command lists the files in a printer_s queue.  When
QSTAT lists these files, the status line indicates the condition of
each file, as follows:

 Intercept:  You have not finished sending data to the queue.  This
condition occurs when you use the 3P SET/HOLD option, when you are
printing from an application and you have not yet pressed
[Ctrl]+[Alt]+[Prtsc], or when you are printing from an ap
plication that does not send a DOS CLOSE command (and you have not
exited the application).  Exiting an application automatically sends a
DOS CLOSE command.

 Deferred:  Your job has been sent to the queue, but you specified
that the printing of the job should be delayed with the  3P SET /DEFER
command.

 Waiting:  Your job has been sent to the queue, but another job has a
higher priority.  Your job will print when those with a higher
priority finish.

 Printing:  Your job is currently printing.

 Print error:  An error has occurred at the printer.  This message
usually means the printer is out of paper or off-line.

 File error:  The server is out of disk space for the print queue
files.


.br;UNSHARE Command
.br;User, p. 7-19
.br;The 3F UNSHARE command deletes only the specified sharename, not the
directory assigned to the sharename, as the 3+Share User Guide states.
(To delete an empty directory, use the DOS RMDIR command.)



.br;Using a New Style IBM Keyboard
.br;User, p. 5-
.br;If you are using an IBM keyboard that does not have [Prtsc] and [*]
on the same key, close print spool files by pressing [Ctrl]+ Alt]+[*]
(where [*] is the key directly above the [9] on the numeric keypad).


3+Mail (Version 1.2.1)

.br;Attachments
.br;Mail, p. 2-8, 5-4
 You can add up to 25 attachments to a message.


.br;Can't find <addressee>...
.br;Mail, p.C-6
.br;The message:

 Can't find  <addressee>  But  domain  <domain:org> is a Remote Domain
...

 means you have tried to send a message to a user who cannot be found
in the local Name service.  The domain specified, however, does exist
in the local Name service.

 To send the message anyway, type a Y and the 3+Mail server attempts
to deliver the message to the remote domain:organization.   If the
user cannot be found on the remote network, the mail server returns
the  message as undelivered mail.

 To avoid this prompt when sending mail to users in remote domains,
use the /NP parameter when running the mail program (for example,
MAIL E: /NP).


.br;Color Graphics
.br;Mail, p.3-4
.br;3+Mail version 1.2.1 supports color on color graphics and enhanced
color graphics systems.  To display mail in color, type:

 MAIL <inbox location> /DISPLAYTYPE=x

 where x is B, D, or E.  Each of these letters represents a different
color combination, as shown on the next page.

_

Filing Mail Messages to Multiple Floppy Diskettes
Mail, p. 6-5
 When filing mail messages to a netstation with a single diskette
drive, do not simply insert a new diskette into the same drive and
continue filing messages (for example when the first diskette fills
up).  Doing so results in  false directory inform
ation on the new diskette and makes its files inaccessible.  If you
want to file messages to another diskette, use the following steps:

.br;1. Exit 3+Mail.
.br;2. Remove the current diskette.
.br;3. Insert a formatted diskette.
.br;4. Use the DOS DIR command to list the directory of
the new diskette.
.br;5. Run 3+Mail again.

You can now file messages to the new diskette.

If your netstation has two diskette drives and you are running mail
from a network drive, you can safely file messages to two diskettes by
placing one in drive A and one in drive B:.


Running 3+Mail from  a Dual Floppy System
.br;Mail, p. A-2
.br;If you want to run 3+Mail locally using dual floppy drives, insert
the diskette containing the MAIL.EXE program in drive A: and a
formatted diskette in drive B.  With drive A: as your current drive,
type the command A>MAIL B: to start the 3+Mail pro
gram.  Do not  file mail to the diskette containing the MAIL.EXE
program or you may lose files and directories.


.br;Using 3+MailMinder
.br;MMinder, p. 1-4
.br;The 3+MailMinder program is now included on the 3+Mail user diskette.
To display 3+MailMinder in color, start it with with the command:

 MMinder /color=on



 3+Menus

.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.


NetBIOS

.br;3C Connection
.br;NBSup, p. 2-10
.br;When making a 3C connection to a server that does not have a Locator,
use a netstation startup diskette created with the standard 3+
configuration (not one created with the full NetBIOS option).

NetBIOS netstation diskettes require that a Locator exist when they
start up.  If the server does not have a Locator, a netstation
diskette created with the full NetBIOS option will not start up.


.br;COMMANDS (NCBs)
.br;NBSup, p. 3-9
.br;The default setting for the NCBs should be 32.



Locator not responding
.br;NBSup, p. 4-8

If the node running the Locator loses power or is shut off (and if
the Locator is not running on the Name server),  NetBIOS continues to
function normally (for example, links to networked resources are
unaffected) until it tries to access the absent Locator.  When the
access fails, NetBIOS displays the message:

 Locator not responding.

The SETNAME command (in your netstation AUTOEXEC.BAT file) requires a
functioning Locator, so do not start your netstation if a Locator is
not available.

The first Locator activated automatically detects the appearance of
other Locators that try to appear on the network and ignores them.
When a netstation with another locator tries to boot,  it senses the
that there is already a locator on the network, and terminates its
boot process immediately.  (This avoids the problem of a network
having duplicate Locators with inconsistent name databases.)

(For programmatic reference, NetBIOS continues to function normally
without a Locator as long as no ADD NAME, ADD GROUP NAME, DELETE
NAME, CALL NCBs, or SEND DATAGRAM commands are used.)



.br;NetBIOS /C Switch
.br;NBSup, p. 3-12
.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 the
message:

.br;Network Retrying ...
.br;or
.br;Locator Not Responding
.br;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].

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


.br;NetBIOS /M Switch
.br;NBSup, p. 3-13, 4-6
.br;The IBM Asynchronous Communications Server and the IBM PC LAN
programs require the /M switch.


.br;NetBIOS and the Locator
.br;NBSup, p. C-4
.br;References to the 3Com Session Interface in step 9, should be
references to the interrupt interface.


.br;NBSup, p. 4-1
.br;The Locator, in addition to acting as a centralized name server for
NetBIOS, informs its client netstations when another machine running
NetBIOS has gone off-line (for example, someone rebooting the
netstation).  When a machine goes off-line, the Locator terminates
its sessions.  To let the Locator detect when a machine goes off-
line, each NetBIOS machine periodically sends a heartbeat message to
the Locator.  If the Locator does not receive a heartbeat from a
given machine every 30 seconds (every 20 minutes for remote PCs), the
Locator assumes the machine has gone off-line and informs the other
netstations when it responds to their heartbeats. (Sessions
established through 3F are not subject to termination via this
heartbeat mechanism.) For NetBIOS to send heartbeats, the timer
interrupt must not be disabled.  Two common conditions that disable
the timer interrupt are:

 _ A local printer that is off-line while the CPU
   is trying to print.
 _ A program debugger that disables interrupts when
   it is active.

Either of these conditions cause the Locator to think that the
machine is off-line and thus terminate its NetBIOS sessions.  You can
avoid disabling the timer interrupt by calculating a new (and longer)
interval and patching this new interval into NetBIOS.EXE, as
explained in the following steps:

1. Choose a new interval (in seconds).  The initial
value for the interval is 15 seconds.  (The Locator
gives a grace period by automatically doubling this
value.)   Keep in mind that the new interval must
be long enough to handle the maximum time that
the interrupts will be disabled, but not so long that
it creates a problem for other netstations.
(Netstations will not be able to end sessions
established with your machine until the timeout
interval has elapsed.)

2. Convert the number to timer ticks by dividing it by
.055.

3. Convert the resulting number to hexadecimal.

The following steps assume the use of IBM_s Debug program to patch
the new interval into NetBIOS.EXE:

.br;1. C>copy netbios.exe netbios.sav
.br;2. C>ren netbios.exe netbios.new
.br;3. C>debug
.br;4. -N netbios.new
.br;5. -L
.br;6. -E cs:49CA
.br;7. -11 xx  01 yy
.br;(the last two digits of the hex number you
computed above become xx  and the first two digits
become yy.)
.br;8. -W
.br;9. -Q
.br;10.  C>ren netbios.new netbios.exe


.br;NetBIOS Processes
.br;NBSup, p. 3-10
.br;The default setting for the NetBIOS Processes should be 2.


.br;NetBIOS Sessions
.br;NBSup, p. 3-9
.br;The default setting for the NetBIOS Sessions should be 32.

.br;Shutting Down the Server
.br;Using the full NetBIOS to execute a 3F shutdown causes NetBIOS to
display:

 Share server not responding
  or
 Transmission error

but properly shuts down the server.


NetDOS

.br;DOS Utilities
.br;The MS-DOS 3.3 utilities FC.EXE and VDISK.SYS were inadvertently
omitted from this release of NetDOS.  The utilities are available
with the optional 3+NetDOS package.


3+Route and 3+Remote

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


.br;Mixing Hayes and Microcom Modems
.br;When you use a Microcom mode in SX mode, you must have one on both the
originating and answering systems.  That is, 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 interchangeably, 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.
