Ref: 20570005
Title: Netware386 for 3Server Release Notes
Date:  5/3/91

Copyright 3Com Corporation, 1991.  All rights reserved.

NETWARE 386 for the 3Server
Network Server Installation and
Setup Guide Release Note

These release notes contain new or changed information for Netware 386
on your 3Server Network Server Installation and Setup Guide.  Please
read these release notes before you install Netware 386 on your
3Server.

INSTALLATION REMINDERS

The following sections contain important information for installing
and using Netware386 on your 3Server network server.

BEFORE INSTALLATION

The following information describes additional hardware features or
setup considerations.

NOTE:  If you have a 3Server server with an expansion unit and a
configuration with more than two hard disk drives, a WD33C93A SCSI
controller chip must be on the SCSI plus card in your system.  Call
3Com technical services Return Material Authorization (RMA) for
information.

The list of adapters in the "Hardware Requirements" section of Chapter 1
now includes the following supported configurations:

PRIMARY NETWORK ADAPTERS

NOTE:  The IBM Token-Ring Network 16/4 adapter with the 1990 BIOS
currently is not supported on the 3Server network server for Netware
386.

On-board Ethernet
IBM Token-Ring Network 16/4
IBM Token-Ring Adapter II

SECONDARY ADAPTERS (when using on-board Ethernet as the primary adapter)

IBM Token-Ring Network 16/4
IBM Token-Ring Adapter II

INTERNAL BRIDGING ADAPTERS

Two Etherlink Plus
Two IBM Token-Ring II
Two IBM Token-Ring Network 16/4

NOTE:  When performing a floppy diskette installation, copy the
3C505.LAN file for this adapter from the 3Server Utility for Netware 386
diskette's DRIVERS directory.

The 3Server network server has a single parallel port, a standard
asynchronous serial port, a non-standard synchronous serial port, and a
LocalTalk port.  Netware 386 does not support the non-standard
synchronous serial port, COM2 (3+) COM3 (3+Open), or the LocalTalk port.

When using secondary adapters that use server memory space set the
server's base memory to 768KB for Token-Ring and Arcnet.

Use the interrupt 3 and 6 settings for token ring adapters.  Interrupts
2 and 7 are not available.

When formatting the server's hard disk drives for disk mirroring, the
secondary drive must contain a bootable DOS partition.  The 3DISK386
program will ask if the drive will be bootable.  Type Y(es) and continue
with the 3DISK386 formatting procedures described in the Netware 386 for
the 3Server Network Server Installation and Setup Guide or the 3Server
Software Utility Guide.

NOTE:  This disk mirroring process is not disk duplexing.  Two SCSI host
adapters are not supported on the 3Server.

If you are installing Netware 386 from diskette onto more than one
server from the workstation's hard disk, use the MKSUBS.BAT file located
on the Netstation Utility for Netware 386 diskette to create a client
hard disk image of the Netware 386 system diskettes.  Copy this batch
file to drive C on the client.  You can then run the batch file from the
client's C drive.

DURING INSTALLATION

When installing Netware 386 on the server, make sure you do the
following actions:

If you are using a token ring adapter, be sure to run SETTOK.BAT before
rebooting the server.

When editing the AUTOEXEC.NCF file, make the following checks before
saving the file:

In the Editing Netware 386 Configuration Files section, change the
AUTOEXEC.NCF parameter reference in Tables 3-1 and 4-1 from Mount=All to
Mount All.  Also make this change in step 5 of this section.

You must enter a password on the 'load remote' parameter line.  If you
do not enter a password, the remote connection will not become active,
and you will not be able to see the server from the Rconsole Program.

Make sure that the 'Load 3cnsetm 12' parameter is placed after the
'load 3cnlcd' parameter.  If this is not done, the load 3cnsetm 12 time
display parameter will not work.

Each 3Server network server must have a different default internal
network number.  If the network number is not unique for each server,
internal bridging will not function.

AFTER INSTALLATION

The following information will help you run Netware 386 on your server:

After installing the Netware 386, on your server, you must set the
server's mode switch to SERVER mode when you reset the server.

When you are configuring Netware 386, edit the C:\STARTUP.SRV file, not
the STARTUP.NCF file.  If you do not take this action, parameters will
be lost when the server is restarted.

3Server network servers use the C:\NW386\AUTOEXEC.NCF file to define the
network number when they boot in "Local" maintenance mode.  Edit the
C:\NW386\AUTOEXEC.NCF to use the network number entered in the
SYS:SYSTEM\AUTOEXEC.NCF file.

SECONDARY ADAPTERS

This section provides information for using token ring adapters with the
3Server network server and Netware 386.

The IBM Token-Ring Network 16/4 adapter with the 1990 BIOS currently is
not supported on 3Server Network server for Netware 386.

When loading TOKEN.LAN, be sure to use the port argument for bridge
configurations.  The following is an example of AUTOEXEC.NCF file
parameter settings for Internal Bridging.  In this example, different
packet definitions are being used (FRAME=<parameter>).

file server name 3S600
ipx internal net 123BBB
LOAD TOKEN PORT=A20 NAME=LAN100 MEM=D4000 FRAME=TOKEN-RING
LOAD TOKEN PORT=A24 NAME=LAN300 MEM=D8000 FRAME=TOKEN-RING
BIND IPX TO LAN100 NET=100
BIND IPX TO LAN200 NET=300
LOAD REMOTE 3COM
LOAD RSPX
LOAD 3CNNMI
LOAD 3CNLCD
MOUNT ALL

When loading 3C505.LAN,be sure to use the port argument for bridge
configurations.  The following is an example of AUTOEXEC.NCF file
parameter settings for internal bridging.  In this example different
packet definitions are being used (FRAME=<parameter>).

file server name 3S500
ipx internal net 123AAA
LOAD 3C505 NAME=LAN100 PORT=300 DMA=7 INT=3 FRAME=ETHERNET_802.3
LOAD 3C505 NAME=LAN200 PORT=310 DMA=5 INT=5 FRAME=ETHERNET_802.3
LOAD 3C505 NAME=LAN300 PORT=300 DMA=7 INT=3 FRAME=ETHERNET_II
LOAD 3C505 NAME=LAN400 PORT=310 DMA=5 INT=5 FRAME=ETHERNET_II
BIND IPX TO LAN100 NET=100
BIND IPX TO LAN200 NET=200
BIND IPX TO LAN300 NET=300
BIND IPX TO LAN400 NET=400
LOAD REMOTE 3COM
LOAD RSPX
LOAD 3CNNMI
LOAD 3CNLCD
MOUNT ALL

OPERATING INFORMATION

This section provides information about running Netware 386 on the
3Server.

When configuring the 3Server network server as a print server using
Novell's Print Server version 1.2, the following restrictions apply:

If you load the PSERVER.NLM parameter from your AUTOEXEC.NCF file, and
you have assigned the print server a password, PSERVER will not run.
The console will pause and printing will not start until a password is
entered.

If you want the print server to run, use Rconsole and enter the
password.  If you have not assigned a password protection for your print
server, the printer will print without pausing when you run PSERVER.

If you are using the ARCserve backup/restore product from Cheyenne
Software,Inc with the 3Server, you must install the ARCserve program to
the server from your workstation's local hard disk drive.  Refer to your
ARCserve User Guide for installation instructions.

Netware file time-stamps on the 3Server server may be offset by one hour
on some files.  The time offset does not affect server operation.

TROUBLESHOOTING

Make the following changes to Appendix A

In the Startup Problems section add the following after step 8.

At the Rconsole prompt, load the disk driver by typing:
:Load 3cndisk [Return]

At the Rconsole prompt, load the installation and configuration file to
view your AUTOEXEC.NCF file by typing:
:Load Install [Return]

In the Operating Problems section add the following after step 8.

At the Rconsole prompt, load the disk driver by typing:
:Load 3cndisk [Return]

At the Rconsole prompt, load the installation and configuration file to
view your Autoexec.NCF file by typing:
:Load Install [Return]
